Auto upgrade from build 72 to build 81 kills serial wideband.

[mr.prick]

Plug in one of the AD inputs and see if you get serial WBO2 to display.
My issue is passthru showing incorrect data or no data with out one of the AD plugged in.
If someone wants to configure my options.txt to show AD volts and serial WBO2 in BBL
then you will see the difference between BBL and passthru.Options.txt
This is definitely a bug in build 82, 81 worked fine.


My apologies for suggesting the OP to update.

[Blacky]

Make sure your FlashScan device is running firmware 2.06.06 or later
Regards
Paul

[swingtan]

So are you saying there are issues with AD WB as well as Serial?

I just did 2 logs, one on build 82 and one on build 67 ( the only other old version I currently have ). As has already been indicated, 82 does not display correct WB data while 67 works fine. I also tried opening the B82 log in the B67 Scantool and the data was exactly the same. So the issue is with the actual recording of WB data, not the display of the data. It is not WB brand specific either, as I tested using a TE and others have used a PLX.

With B82, there was no change from the car being off, not started for 16hours and then starting the car. This should have given the largest change in WB signal, from almost free air to 2:1 starting mixture. The logged data didn't change at all.

Logs are attached.

Simon.

[Blacky]

Is the correct wideband type selected in the FlashScan Setup menu?
Regards
Paul

[swingtan]

Blacky,

I just swapped an old version of "obdiiV7.dll" in to the current working dir and passthrough WB logging works again. I think there is a misconfiguration in the setup data for that file that is reading the wrong data from the USB frames ( big guess I know ).

Here's a log I just did, only swapping....

odbiiV7.dll ver: 7.5.5.82 Modified: Monday, 2 March 2009, 20:12:04

with

odbiiV7.dll ver: 7.5.4.66 Modified: Friday, 8 August 2008, 16:13:32

Simon.

EDIT: This may break a lot of other stuff as this DLL appears to control how data is read from the USB frames. I wouldn't go swapping files around unless Blacky gives the OK first. I only did this as a trouble shooting exercise.

[Blacky]

Can you do the same thing with build 82 and build 66, only this time as well as saving the log files, can you also generate and save an error report after each 5-10 second log?
Please exit and restart the scan tool software just prior to starting each log, that way the error reports will be cleared before you start.

The error trace will show me the exact data being sent by FlashScan, which I will attempt to match up with the data in the *.efi log files. That way I may be able to find out which data EFILive is "seeing" instead of the correct wide band data.

Thanks
Paul

[Blacky]

You can try this version of the V2.06.06 firmware with the build 82 release. I've kept the firmware version number the same so you can revert back to the release V2.06.06 if required.

After programming, the firmware date should show as March 01, 2009.
The released V2.06.06 firmware has a date of Dec 14, 2008.

Regards
Paul

[Blacky]

Ok, I think I have found the problem. The diff command was my friend I compared the source code from build 81 to build 82...

In the change from build 81 to build 82 there was a code change in the routine that extracted the external data from the buffer:

Original code: ExternalPID_Index*16
New code: ExternalPID_Index*sizeof(WORD)

Time for me to go back to programming 101... :(
Sorry for the screw-up, I'll get a new release posted tonight.
Anyone care to post what the code should have been changed to?

I still don't understand why it is working here... but I will get to the bottom of it.

Regards
Paul

[Blacky]

I still don't understand why it is working here... but I will get to the bottom of it.

Hmmm, I was running build 60 on the machine I was testing on - I thought it had the latest build 82...

Its not been a good day so far...

Regards
Paul

[Blacky]

Hmmm, I was running build 60 on the machine I was testing on - I thought it had the latest build 82...

Its not been a good day so far...

Regards
Paul

The development environment was pointing to build 60 as the host application when testing the obdiiv7.dll - instead of build 82. Unfortunately, build 60 was the build that was regression tested prior to releasing build 82, so build 82 never got tested before release.

Attached is an updated obdiiv7.dll (still called build 82) that should fix the external PIDs and serial wideband PIDs problem.
Just copy it into the V7.5 folder, overwriting the original build 82 version.

I'll release an official and tested update tonight (it will be build 83).

Regards
Paul