[Terry @ BMS]

Hey guys,

We'll use this thread to post the latest JB3 interface and firmware (mapping) files as we have them. As time allows I'll also discuss how to use the interface, what each field means, etc.

To fully use 2.0 you need a G3 board, the 2.0 firmware loaded on it, and a JB3 tuning cable.

To order a JB3 tuning cable or upgrade to a G3 board click here.

To order an firmware update chip for your existing G3 board click here. Also see the "how to swap chips" PDF at the bottom of this post.

To figure out whether or not you already have a G3 board click here.

Those of you using the older burner kit to upgrade your JB3 can download the drivers for the burner here.

Some more detailed software and data logging directions here.

Download 7/4 beta firmware and interface here.



2/19 Some 2.0 dyno results.

*** READ ME ***
1) Map numbering is the same as 1.4. Map 1 defaults as a low boost map but can also be turned in to a custom map using the user interface.
2) "lean cruise" is disabled pending more testing. We will bring it back in upcoming beta versions.
3) A G3 board is suggested for the new firmware although it will function on a G2 board.
4) To do logging, firmware updates, tuning, etc, a G3 board and tuning cable are required.
5) 2.0 is not compatible with the BMS tuning gauge. If you leave the gauge plugged in it *should* still show boost/IAT but map switching will not function.
6) For heavily modified cars suggested throttle gain is 20, for tune only cars 40. Throttle gain should be set such that response is to your liking with minimal boost overshoot. Too high of a setting will result in throttle closure and unstable boost. Email in CSV logs if there are any questions.
7) Manual transmission bogfix Holds more boost through aggressive high RPM shifts. To enable and test this feature set bogfix to 100%. The gas pedal must be fully released during a fast shift for bogfix to engage.
8) Cold start mode. Allows the JB3 to always start in map 0 and switch on the fly to your performance map when pressing the gas pedal down over a user selected value. To disable leave setting at 0. A setting of 60 means you will need to push the gas pedal down 60% when driving around to trigger the on the fly map switch.
9) Fuel pressure safety. Set to 0 to disable or set to the minimum allowable WOT fuel pressure before the JB3 reverts to the stock map. A setting of 10 is a good starting point for those that want to use the feature.
10) Map 1 lagfix setting is now global for any map where lagfix is enabled. Some users find smoother low throttle performance with a lower setting. Feel free to play with it.
11) If you need help email at terry@burgertuning.com. Support request posts in this thread or on the forum will be ignored/deleted. It's simply not productive for us to attempt to help you over the forum.

Known bugs:
None!

****************************************
****************************************
Datalogging directions:
To being recording click “file” “connect” to establish communications with the JB3. If you fail to connect, ensure you’ve selected the appropriate communications port under settings.

If the RPM and other signals are moving around below you are recording. If you have stopped recording for any reason and want to restart or reset a log you can click “data logging” “start”. The interface will store up to 5000 data points. If you have samples / second set to 10 under settings this will yield a maximum of around 8 minutes of recording time per log.

At the conclusion of your runs/log, click “data logging” “stop and display” to stop recording and plot the datalog. Parameters can be added or removed from the display by clicking the “add” button next to each. If you want to save the log for later, or email to BMS, click “data logging” “export” “csv” and save the file. You can click “data logging” “open CSV” to study the log at a later time. All parameters will be always saved in the CSV regardless of your viewing settings.

Use the “data logging” “X Axis” menu to adjust the scaling or filter out non-WOT activity. With longer logs and slower computers scrolling through the display can be slow, so limiting viewable data to near WOT activity only can be a time saver.

Logable Parameters:

1) Pre-Boost. Boost pressure as measured before the throttle body. Generally will match manifold boost pressure like one might read from a mechanical boost gauge except in cases where the throttle body is not fully open. Such as during DTC intervention or loss of traction, sudden shifts, letting off the throttle at the end of a run, and over target conditions where the ECU throttle safety is kicking in. During these conditions pre-boost will spike up prior to the diverter valves opening. Scale is 0-20psi along the left of the chart.
2) RPM. Engine speed in revolutions per minute. Will roughly match your dash tachometer. Scale is 0-7000RPM along the right of the chart.
3) IAT. Air intake temperature post intercooler in degrees Fahrenheit. Scale is 0-20 = 0-200 degrees F along the left axis.
4) TPS. Throttle position / gas pedal sensor, 0% = idle, 100% = wide open throttle. Scale is 0-10 = 0-100% along the left axis.
5) MAP. Currently selected performance map. You can use the drop down to change maps while logging is active.
6) Fuel. Amount of fuel enrichment being added. Scale is 10-20 = 0-100% along left axis.
7) ECU PSI. The amount of boost the ECU is observing, generally 6-8psi during WOT activity. Used as the process variable for the PWM PID controller. Scale is 0-20psi along the left axis.
8) PID PSI. The minimum ECU PSI allowable for the given conditions. Above this value less PWM is required and below this target more PWM is required. Scale is 0-20psi along the left axis. It is normal for ECU PSI to float high above PID PSI under certain conditions such as part throttle indicating the JB3 does not need to supplement PWM at that time. As ECU PSI falls below PID PSI the JB3 must increase PWM to sustain target boost levels.
9) PWM. The boost solenoid/duty cycle/wastegate offset. Higher values indicate more wastegate closure initiated by the JB3 and lower values indicate less wastegate closure. This value is determined by the PID controller which is driven off ECU PSI and PID PSI and influenced by parameters under user adjustment.
10) Clock. An internal variable used by BMS with no significance to end users.
11) Timer. An internal variable used by BMS with no significance to end users.


****************************************
****************************************
User Adjustment Notes:
Not all fields are currently in use/enabled. Refer to beta firmware notes as needed.

Tuning Setup: Allows map specific tuning adjustments. Currently only map 1 is available to be modified/customized. The settings under tuning will reflect map 1 no matter what map is actually selected. But they will only take effect if map 1 is selected unless otherwise noted.

Torque: Boost < 4500 rpm.
Power: Boost > 4500 added on top of torque setting.
Fuel: Amount of fuel enrichment over stock under boost. 0 = stock air/fuel ratios.
IAT Decay: Boost taper based on air intake temperature. 0 = no decay, 8 = map 7 levels.
Lagfix: Controls the default wastegate position during cruise. In the beta firmware, lagfix maps are set to 100, and non-lagfix maps are set to 0.
Bogfix: Controls the value of PWM during sudden manual shifts. Higher values hold more PWM, and thus more boost through the shift, but may make shifting feel abrupt or notchy. Set to 0 in beta maps.
Boost Limit: The maximum allowable boost before reverting to map 0. Boost must be exceeded for ~500ms during WOT to trigger a map change to 0.
Lean Cruise: Enables a feature that leans out air/fuel ratios during sustained cruising/off boost conditions, resulting in an additional 2-3mpg, at the expense of low throttle torque and emissions. Currently disabled.

Global Settings: These settings take effect regardless of map selected, and are generally related to boost target modeling, or the "PSI PID" loggable parameter. All fields establish minimums that the JB3 then adds barometric, ambient temperature, and time under boost calculations to arrive at final values. As a general rule you should not change them unless directed to by BMS technical support.

Min Target: Minimum allowable ECU observed target at 2000rpm.
Max Target: Minimum allowable ECU observed target at 5000rpm.
Taper: The rate of ECU observed target decay from 5800rpm to redline.
Min PWM: The lowest allowable PWM when pre-boost > 5psi.
PID Gain: A general field for adjusting the PID response. For tuning nerds I and D are a function of P so you scale the entire system with this field.
Throttle Gain: Controls the resistance to positive boost swings. Too low of a setting results in sluggish boost response, but too aggressive can lead to boost overshoot and spikes during spool up and shifts. Generally 20-40 works well in most cases.
Disable Pedal Map: Enables/Disables gas pedal mapping. If you never want to use gas pedal map switching and only plan to change maps via an external device or laptop, set to 1.
Future Use: General testing field with values changing with each firmware version. Leave it at 0.

Informational / Read Only: Values for reference only, can not be changed directly
Ambient Voltage: Barometric pressure reflected in a voltage format.
Firmware Ver: Version of firmware (HEX) file currently loaded.
Interface Ver: Version of the interface software currently loaded.

[Terry @ BMS]

Screen shot of the 3/16 interface and default 3/22 firmware settings.

Also included is a sheet showing the constant values of each map for those who want to make a custom map 1.

JB3 2.0 Map Guide

Map 0:
-- Disables JB3, all signals pass through

Map 1:
-- Low boost map, boost levels of 11-13psi depending on mods and weather
-- Self adapts to modifications like intake, downpipes, exhaust, etc
-- 91 octane RM2 or higher required. The higher the octane, the more power.
-- Can be changed to a customized map in 2.0 interface

Map 2:
-- Performance map, boost levels of 12-14psi depending on mods and weather
-- Self adapts to modifications like intake, downpipes, exhaust, etc
-- 91 octane RM2 or greater required. The higher the octane, the more power.

Map 3:
-- Identical to map 2 with additional low end response (aka lagfix)

Map 4:
-- Hotter Performance map, boost levels of 13-15psi depending on mods
and weather
-- Self adapts to modifications like intake, downpipes, exhaust, etc
-- 93 octane RM2 or greater required. The higher the octane, the more power.

Map 5:
-- Identical to map 4 with additional low end response (aka lagfix)

Map 6:
-- Designed to optimize bolt on performance
-- 93 octane RM2 or greater required. The higher the octane, the more power.
-- Richer midrange air/fuel ratios to sustain additional torque
-- May trigger hidden tuner detection codes. Purchase a Bavarian
Technic cable from BMS to scan for and delete any hidden codes before service.

Map 7:
-- Identical to map 6 with additional low end response (aka lagfix)

Map 8:
-- Race map
-- 97 octane RM2 or greater required. The higher the octane, the more power.
-- Modifications like intake, downpipes, and intercooler strongly suggested
-- Lagfix enabled
-- May trigger tuner detection codes

Map 9:
-- More aggressive race map
-- 100 octane RM2 or greater required. The higher the octane, the more power.
-- Intake, downpipes, and intercooler required
-- Lagfix enabled
-- May trigger tuner detection codes

Map 10-13:
-- Extended race maps. Each 1/2psi more than the previous. For use with modified JB3 boards only

[ace008]

If we had the interface from the 1/16/10 files, and have loaded the 1/22/10 map, do we need to reinstall the interface as well? If we do, do we need to uninstall the old interface?

[Terry @ BMS]

Originally Posted by ace008

If we had the interface from the 1/16/10 files, and have loaded the 1/22/10 map, do we need to reinstall the interface as well? If we do, do we need to uninstall the old interface?

No, the interfaces and firmwares are interchangeable unless specifically noted. This interface works with the 1/16 and earlier firmware.

One of the changes is we're not going to call the .HEX files "maps" anymore. Too confusing. They are now called firmware versions, and maps are the tuning map 1-9 that you select.

[5soko]

Downloaded it and was palying around with it, very cool! Great job Terry, this is really amazing and seems really easy to use. Cant wait to start datalogging to see how my car is running!

Alot of questions on how and what to use, but im sure that will be covered soon. Since i wont be using the custom mapping, i will only be using the map changing and datalogging.

[335ievo]

Agreed, the interface is awesome.

Has anyone with windows vista had problems with the JB3 interface crashing? It seems like after 5 min. windows says the application has stopped working and it crashes. Also, it always happens whenever I try to datalog. Anyone experience the same kind of problems?

-Frank

[Terry @ BMS]

Originally Posted by 335ievo

Agreed, the interface is awesome.

Has anyone with windows vista had problems with the JB3 interface crashing? It seems like after 5 min. windows says the application has stopped working and it crashes. Also, it always happens whenever I try to datalog. Anyone experience the same kind of problems?

-Frank

Been working fine on all of our computers (Xp, Vista, Windows 7, etc), and not many reports of customer issues. But any time you have customer provided hardware you run the risk of those headaches. One good option is to pickup a little $299 Acer1 mini laptop from Costco or Best Buy. They work great and even fit in the glove box. I do all my tuning on one.

[hotrod182]

Originally Posted by 335ievo

Agreed, the interface is awesome.

Has anyone with windows vista had problems with the JB3 interface crashing? It seems like after 5 min. windows says the application has stopped working and it crashes. Also, it always happens whenever I try to datalog. Anyone experience the same kind of problems?

-Frank

Okay. down loaded the interface okay on the laptop.

Speaking of program crashing...I continually have my BT program throw up warnings saying if I want to continue, it may have errors, etc. Is the new BT program the solution for this?

[Terry @ BMS]

Make sure you update to the latest BT, some of the older ones conflicted with the JB3 USB drivers.

[Terry @ BMS]

1/24 firmware emailed.

[clifton23]

Originally Posted by Terry @ BMS

1/24 firmware emailed.

[Alessandro]

Originally Posted by Terry @ BMS

1/24 firmware emailed.

i did

[Terry @ BMS]

Hmm I wonder what I would do if I was supposed to get an email, but didn't get one?

[Terry @ BMS]

Added a short writeup of the user adjustment screen. Will do same for the logging screen next week.

[CBR335]

For the nerds out there like me that stay up way too late:

http://en.wikipedia.org/wiki/PID_controller

This can help put you to sleep and help you understand the basics of tuning.

[Former_Boosted_IS]

Originally Posted by Terry @ BMS

Been working fine on all of our computers (Xp, Vista, Windows 7, etc), and not many reports of customer issues. But any time you have customer provided hardware you run the risk of those headaches. One good option is to pickup a little $299 Acer1 mini laptop from Costco or Best Buy. They work great and even fit in the glove box. I do all my tuning on one.

Terry, are you satisfied that you logging rate is sufficient on that computer? If so, I am just going to go ahead and buy one.

[JPSlick]

Not that I'm messing with anything on 2.0 Yet.... But with the Bog Fix

Bogfix: Controls the value of PWM during sudden manual shifts. Higher values hold more PWM, and thus more boost through the shift, but may make shifting feel abrupt or notchy. Set to 0 in beta maps

Where is it currently set at in theory on 1.4 Map 7?

when I do a quick 3-4 shift, it bogs. Sounds like I would need to make it more aggressive? Or is that a boost over-shooting problem and not a bogfix issue?

[Terry @ BMS]

Originally Posted by Former_Boosted_IS

Terry, are you satisfied that you logging rate is sufficient on that computer? If so, I am just going to go ahead and buy one.

Seems more than fast enough to me. In testing I was able to manage 20/samples second with it. The slow down is in the charting on the JB3 software side. Plan to speed that up at some point.

[Terry @ BMS]

Originally Posted by JPSlick

Not that I'm messing with anything on 2.0 Yet.... But with the Bog Fix


Where is it currently set at in theory on 1.4 Map 7?

when I do a quick 3-4 shift, it bogs. Sounds like I would need to make it more aggressive? Or is that a boost over-shooting problem and not a bogfix issue?

It's set low in all maps, similar to how its set in 1.4. I disconnected the field in the latest firmware to avoid anyone playing with it until we made a few additional adjustments. If you get a box during shifts its not related to that setting. Do a few logs and we can analyze for you.

[JPSlick]

Originally Posted by Terry @ BMS

It's set low in all maps, similar to how its set in 1.4. I disconnected the field in the latest firmware to avoid anyone playing with it until we made a few additional adjustments. If you get a box during shifts its not related to that setting. Do a few logs and we can analyze for you.

Soon as I get my car out of storage

Might have been the generation 1 board and that resistor that wasnt present? or was the issue from the Gen 1 board that part throttle hesitation?

[Terry @ BMS]

Any one of 100s of possible issues. We don't speculate at this point in the game, we analyze logs.

[JPSlick]

Originally Posted by Terry @ BMS

Any one of 100s of possible issues. We don't speculate at this point in the game, we analyze logs.

Its hard to log a WOT redline 3-4 shift when you have to break 100 MPH in order to do so.

I'll just call Laloosh to run me, that will give me incentive to break the speed limit

[piele_bps]

Originally Posted by Terry @ BMS

It's set low in all maps, similar to how its set in 1.4. I disconnected the field in the latest firmware to avoid anyone playing with it until we made a few additional adjustments. If you get a box during shifts its not related to that setting. Do a few logs and we can analyze for you.

I have those bogs, especially when shfting 3-4. Why is set low on 1.4 ? Especially on map 7.

[Terry @ BMS]

Originally Posted by piele_bps

I have those bogs, especially when shfting 3-4. Why is set low on 1.4 ? Especially on map 7.

Same as last guy. Send logs and we can evaluate your actual situation.

[piele_bps]

Thanks for the answer. I don't really have that cable and 2.0 to do the logs. I am only 1.4, which is so great, except the bogs.

P.S.: waiting for the 2.0 !