[basti335i]

Originally Posted by Terry @ BMS

Average will compute using the lowest one at the moment. Which may or may not be the best way to handle it. One option would be to truly take the "Average" of all cylinders. Since the autotuning algorithms were based off cyl1 data only we'll need to reevaluate. Lots of logs using map 5 and the 2-6 timing enabled would speed that process along.

Here are my first Map5 cyl loggin with 30% E85 and *********

[Luke0818]

Originally Posted by GetSomeE92

I'm noticing Cylinder 5 to be the noisier cylinder as well. Not sure what that means, though, as the car still pulls hard.

Yep. All the logs, cylinder 5 is the most noisy for me. I don't know if it is the noise from the pvc valve or what.

[CHECKERED]

Questions

What overall improvements can we expect?

Do you need a back end flash to run this new firmware?

If one already has a back end flash, wasn’t it already monitoring all cylinders? If yes, was it just not relaying this information to the JB4? I was under the impression that all flash based tunes were monitoring individual cylinder, is this not the case with BB flash?

Will there be any improved meth integration; say boost additive will be cut due to a single cylinder knock?

[GetSomeE92]

Originally Posted by CHECKERED

Questions

What overall improvements can we expect?

Do you need a back end flash to run this new firmware?

If one already has a back end flash, wasn’t it already monitoring all cylinders? If yes, was it just not relaying this information to the JB4? I was under the impression that all flash based tunes were monitoring individual cylinder, is this not the case with BB flash?

Will there be any improved meth integration; say boost additive will be cut due to a single cylinder knock?

A flash merely adjusts the parameters in the ECU, and the ECU monitors ignition and pulls timing if knock is detected. The JB4 used to only monitor ignition timing on cylinder 1. This was the value it reported in the logs and, I'm guessing, used for the auto-tuning functions. Now you can log all 6 cylinder ignition values and this will help with fine tuning the car as you can have a more complete picture of the health/happiness of the engine while running a particular set of tuning parameters.

I would imagine that the new ability to log the ignition timing in all 6 cylinders will lead to changes in the auto-tuning logic and the safety features built into the JB4.

[basti335i]

Today i make another raw timing log and you can see all cyl knock is a good thing..

But i found out that cyl 6 don´t read data
I tested CPS on 1 (i8a0s timing corrections) and only Shows me cyl 1

[Terry @ BMS]

Originally Posted by basti335i

Today i make another raw timing log and you can see all cyl knock is a good thing..

But i found out that cyl 6 don´t read data
I tested CPS on 1 (i8a0s timing corrections) and only Shows me cyl 1

That is odd on cyl6. Try with the latest version we posted.

[FL335]

Will this work on the 335is(ILAOS)?

[Terry @ BMS]

It should. Try it!

[TUN3D]

Terry, is the "BETA" JB4 G5 ISO 28 firmware on THIS post the same as on the "N54 G5 ISO Firmware & Notes" post (http://www.n54tech.com/forums/showthread.php?t=17441)?

[Terry @ BMS]

Yes

[AWil335i]

I'm I8A0S and cyl 4 seems to be the noisiest for me. I've swapped injectors, plugs and coils and nothing seems to make a difference. Could try a compression test or valve cleaning but I'm not sure that's going to help.

Anyone else seeing it on 4?

[Fmonteiro444]

I'm having the same issue with cyl 4

[musc]

Originally Posted by FL335

Will this work on the 335is(ILAOS)?

Yes works fine. Set CPS_7000 to 6 and make sure you have the latest 28hex and JB4 interface.

[Terry @ BMS]

w00t!

[Kish2604]

Originally Posted by Vorsprung_CJB

When I run the setup.exe for the new interface it says 'Not a valid win32 application' so I just ran the manifest directly to install it. It said .Net 4.0 was required so I installed that and updated it. Was able to install and run the application and connect to the JB4, but if I tried to run the update firmware it gives an exception. There is an option to continue but I didn't want to try it and risk a bad FW load. The older interface now gets the same error as well even though it is .Net 2.0 based. This is an older WinXP laptop I use for JB4 and coding.

Edit: Nevermind I guess, the latest regular interface does this too. I guess I was running an even older one. Must be a PC problem.

I seem to be in the same boat.... Have .net 4.0 loaded on my NetBook running windows xp and it won't launch the installer with the same error...

[v8bait]

Originally Posted by CHECKERED

Questions

What overall improvements can we expect?

Do you need a back end flash to run this new firmware?

If one already has a back end flash, wasn’t it already monitoring all cylinders? If yes, was it just not relaying this information to the JB4? I was under the impression that all flash based tunes were monitoring individual cylinder, is this not the case with BB flash?

Will there be any improved meth integration; say boost additive will be cut due to a single cylinder knock?

The car is always monitoring knock on all cylinders, the jb4 just was never able to see that information or log it before. But yes all flashes, even stock, monitor this data, now you get to see it and adjust your overall tune in response.

It's beneficial for those with octane deficiency, like those on pump without meth or E85 who wish to really optimize their tune. As for single corrections, I wouldn't get to upset about a single correction. The sensors will pick up engine noises and all kinds of things and you'll get small corrections, it's when you get multiple corrections that you have an issue imo.

[CHECKERED]

Originally Posted by v8bait

The car is always monitoring knock on all cylinders, the jb4 just was never able to see that information or log it before. But yes all flashes, even stock, monitor this data, now you get to see it and adjust your overall tune in response.

thanks, good to know

are we done with beta testing?

[Vorsprung_CJB]

Originally Posted by Kish2604

I seem to be in the same boat.... Have .net 4.0 loaded on my NetBook running windows xp and it won't launch the installer with the same error...

It looks like Terry compiled the setup.exe and possibly the rest of the app in 64-bit now. I borrowed my 64-bit work laptop and it installed and ran perfectly using the setup.exe. I can get it installed on the old XP one using the other method but it crashes in the firmware update menu, it might work fine for just logging though, will have to test some time.

[scotte30m3]

Originally Posted by basti335i

...I tested CPS on 1 (i8a0s timing corrections) and only Shows me cyl 1

I tested the same thing and could not log all cylinders. Only cylinder 1. Is this expected or is there another change I need to make?

Thanks in Advance,

-Scott

[Terry @ BMS]

Timing would be cps7000 = 4 for i8a0s.

[themyst]

Will this firmware work for those using the Cobb BMS flash? I've been out of the loop so long!

[Terry @ BMS]

Yes!!

[scotte30m3]

Originally Posted by Terry @ BMS

Timing would be cps7000 = 4 for i8a0s.

Does this mean we can't log on all 6 when timing correction is enabled?x

[Terry @ BMS]

The first post has the setup options

[Kish2604]

Will this interface work on older g4 integrated boards?

Also any chance of making it 32 bit compatible?