Build 82, WTF?

[mr.prick]

MY last log was 3-1-09, no problems.
Today I attempt to log and find my serial WBO2 reading 200+ AFR
and my AD voltage is off the chart 16v+.
This is in pass thru only BBL shows AFR in sync with Logworks,
and EFILive explorer shows AD voltage correctly.

When I unplug my AD#1 for FP I get not data for serial but,
when I plug in the AD the then serial is visible again.
Also with just 1 AD plugged in I get both AD voltages displayed.
This makes no sense, when was build 82 released? :confused:
This is on 2 different laptops, I am sure there is some kind of confusion
with the software converting serial and AD voltage.
4856

Thanks.

[swingtan]

So it's much like this thread....

http://forum.efilive.com/showthread.php?t=10144

I haven't tried logging the WB since upgrading but I'll give it a go today and see what happens.

Simon

[mr.prick]

LOL
I get values displayed but they are way wrong in passthru.
Also I believe the problem is with build 82, 81 worked fine.
this is only with the AD inputs and serial input.

I am trying to configure my options.txt (http://forum.efilive.com/attachment.php?attachmentid=4857&d=1236376027) to show external PIDS to see the difference.
AD voltage 16v+ would`nt that melt the V2.
AD voltage is not 16v+ I checked with my DMM.

You can see when I unplug the AD`s the serial goes blank.

[Blacky]

The change described as: Fixed bug when pass through logging would fail with response code $4A for no apparent reason.
In this document: http://www.efilive.com/index.php?option=com_content&view=article&id=126:updatesv755&catid=57:updates&Itemid=134
Is most likely the cause of this problem.
I am working on a fix to be released asap.

Regards
Paul

[mr.prick]

I never got that code.
I am attempting to revert to build 80 by overwriting the 7.5 folder.

[Blacky]

Strange, I just tested each of the four A/D 5V inputs, the two 12V inputs, the two thermocouple and both WO2 serial inputs. Everything checks out and the values are displayed as expected. With one exception: Pressing the Backspace key on FlashScan does not cycle correctly through each of the WO2 types. The display shows that it is cycling through each WO2 type, but internally the WO2 type is not changing. However, that won't affect the analog data.

What firmware version do you have in your FlashScan?
I was testing with V2.06.06

Regards
Paul

[joecar]

Paul, what happens if you remove all analog connections and have only the serial AFR cable plugged in...?

[mr.prick]

All info is inn my sig.

This build is all F*@!ed up for me.
I over wrote the scan.exe and the tune.exe and that did not change anything.
Then I overwrote the 7.5 folder with the last build I had saved (80) and that worked,
although a little shaky with RR connection.
If you want to configure my options.txt to show external PIDS
I will get a BBL log so you can see for yourself.

As you can see in the passthru log, AD voltage is crazy.
serial is only visible with AD1 plugged in.

[Blacky]

Paul, what happens if you remove all analog connections and have only the serial AFR cable plugged in...?

With just the serial, the serial data is displayed correctly and the 4 A/Ds read 0.05V each.

I can't fault it right now... :(

I was testing with an LS1 PCM.

Regards
Paul

[mr.prick]

Is overwriting the 7.5 folder with a previous version an ok way to revert?

[Blacky]

Is overwriting the 7.5 folder with a previous version an ok way to revert?

You only need to swap out three files:
EFILive_Scan.exe
EFILIve_Tune.exe
ObdiiV7.dll
You MUST keep them all at the same build number.

Regards
Paul

[Blacky]

Please check out this thread as well. The problems are likely to have a similar cause/solution.
http://forum.efilive.com/showthread.php?p=88827&posted=1#post88827

Can you also try the firmware in that post, thanks.

Paul

[Blacky]

Possible solution...
http://forum.efilive.com/showthread.php?p=88830&posted=1#post88830

Regards
Paul

[mr.prick]

Possible solution...
http://forum.efilive.com/showthread.php?p=88830&posted=1#post88830

Regards
Paul

The obdiiV7.zip fixed it.
Is that newfirmware or altered?

[Blacky]

The firmware I posted is very new and very untested. It has a whole lot of new features which are needed to support standalone reading/flashing.

The obdiiv7.dll is the actual fix for the problem, changing the firmware will not fix the problem. I was at a loss to explain why I was seeing it work so I thought maybe it was the firmware I was using - turns out it was not.

Regards
Paul

[JR-CRUZN-C5]

Guys - My car is going back together NOW. I will be racing again in April. Have not really touched my "stuff" lately.

My current setup is:
V7.5.5 (Build 80)
BB 2.06.02
FW 2.06.06

I have not recvd. any auto downloads in a while.

SHOULD I BE CHANGING ANYTHING???

JR

http://s672.photobucket.com/albums/vv85/itsjr_photos/Burnout1.jpg

[Blacky]

Select the option:
Start->All Programs->EFILive->V7.5->Tools->Checkfor New Update.

Check here first to see what has been updated:
http://www.efilive.com/index.php?option=com_content&view=category&id=57&Itemid=134

The auto update is set to 3:00am Sunday morning by default. I think if you are not connected to the 'net at that time then it won't update automatically.

Regards
Paul


Guys - My car is going back together NOW. I will be racing again in April. Have not really touched my "stuff" lately.

My current setup is:
V7.5.5 (Build 80)
BB 2.06.02
FW 2.06.06

I have not recvd. any auto downloads in a while.

SHOULD I BE CHANGING ANYTHING???

JR

http://boomspeed.com/itsjr/Burnout1.jpg

[mr.prick]

The firmware I posted is very new and very untested. It has a whole lot of new features which are needed to support standalone reading/flashing.

The obdiiv7.dll is the actual fix for the problem, changing the firmware will not fix the problem. I was at a loss to explain why I was seeing it work so I thought maybe it was the firmware I was using - turns out it was not.

Regards
Paul

Not to nag but,
why not completely change the number sequence of the firmware?
To avoid confusion. :hihi:
Was this in the 7.5 update and is it to be used with build 82 and V8 (44)?

By any chance will BBF be usable with the RR?
I know you can`t up/download with RR like you can stock PCM,
just curious.

[Blacky]

Not to nag but,
why not completely change the number sequence of the firmware?
To avoid confusion. :hihi:
Was this in the 7.5 update and is it to be used with build 82 and V8 (44)?
If I increased the version number and you flashed it in and it caused more problems (untested and all), then you would not be able to go back to V2.06.06. I left it at V2.06.06 so you could go back to the real V2.06.06 if required. I did change the date so you could tell it was different to the "real" V2.06.06 once it was flashed into FlashScan.

I did not include the new firmware update with the latest V7.5.5 build 83 update) it has not been tested enough, it is part of the AutoCal beta test suite). Although I mistakenly added some comments to the "waht's new" web page that indicated that the firmware was being updated with that release - my bad.


By any chance will BBF be usable with the RR?
I know you can`t up/download with RR like you can stock PCM,
just curious.
No plans to allow BBF on RR with the first release, but is something that could be supported in future.

Regards
Paul

[mr.prick]

We can`t go backwards with firmware now?
IRC there was a bad firmware that caused connection problems
and I was able to go back.
It was long ago, maybe before the last bootblock update.

[Blacky]

We can`t go backwards with firmware now?
IRC there was a bad firmware that caused connection problems
and I was able to go back.
It was long ago, maybe before the last bootblock update.

When V2.05.xx first came out, it was possible to go back for exactly that reason. But now it is not possible to back to older firmware.

Regards
Paul

[JR-CRUZN-C5]

Guys -

I just updated to V7.5.5 Build 83.

I assume that also covers 81 & 82 as I had 80 in my setup???

JR

[mr.prick]

Guys -

I just updated to V7.5.5 Build 83.

I assume that also covers 81 & 82 as I had 80 in my setup???

JR

You didn't want build 82, did you?
You should be good to go with 83.
I have no complaints so far,
at least with passthru.

I still need my options text fixed
to display ext. and serial.

[joecar]

JR-C-C5,

V7.5 build 83 is good as you have it.

And BB 2.06.02, FW 2.06.06 is good.

[mr.prick]

JR-C-C5,

V7.5 build 83 is good as you have it.

And BB 2.06.02, FW 2.06.06 is good.

Are you referring to the "new" firmware,
beta rename?

[joecar]

No not the new one, the original one.

[joecar]

...
I still need my options text fixed
to display ext. and serial.Post your Options.txt file.

You can set the V2 options to display both the analog pids and the serial pid... that way you don't need to mention them in Options.txt...

Altho, if you want to see analog AFR, you need to enter a line for EXT.AD1/2/3/4 in the conversions section (near bottom of Options.txt)... see my attached (analog AFR = V * 1.0 + 11.0 in my case).

[mr.prick]

Altho, if you want to see analog AFR, you need to enter a line for EXT.AD1/2/3/4 in the conversions section (near bottom of Options.txt)... see my attached (analog AFR = V * 1.0 + 11.0 in my case).

This seems to be what I'm missing.
I want to log AD1/2 and ext.WBO2 with BBL.
4874

[joecar]

This seems to be what I'm missing.
I want to log AD1/2 and ext.WBO2 with BBL.
4874With your Options.txt, to display analog AFR on V2, first do this: dive into the V2 options menu (Options->Setup->Edit Settings) and enable A/D Pids [and Ser Pids while you're there]...

Then when viewing a log-in-progress on the V2 LCD, view EXT.AD1 and press ENTER (to switch to the alternate units).

[mr.prick]

Do I have the conversion right?
Factor = *
Offset = +

[joecar]

Do I have the conversion right?
Factor = *
Offset = +Yes, that is correct.

Your Options.txt defines your analog AFR as V * 3.0 + 7.35 which is correct for standard default (unreprogrammed) LC-1.