Update: May 20, 2013

[joecar]

V8 S&T, BBx: reading Options.txt file seems to wipe out custom units (it wipes out the selected custom units and the factor/offset).

[joecar]

Reading BBx config from V2 causes access violations:

first this one:

---------------------------
Error
---------------------------
Access violation at address 0082EC3A in module 'EFILive_ScanAndTune.exe'. Read of address 00000000
---------------------------
OK
---------------------------

and then several of these:

---------------------------
EFILive Scan and Tune
---------------------------
Access violation at address 0040B2E6 in module 'EFILive_ScanAndTune.exe'. Write of address 00826168.
---------------------------
OK
---------------------------

[joecar]

Paul,

The V2 readiness states now have their formatting all jumbled up.


2.7.41.

When viewing the readiness monitors on the V2 LCD, the formatting is jumbled up (strange characters, labels repeated in column fashion).

When viewing Freeze Frames on the V2 LCD, it looks like that any whitespace characters are replaced with either up-arrow or down-arrow characters (this was actually happening previously a long time ago).


When reading all diagnostics to file, the file content looks good, see attached.

In the freeze frame data, the field labelled <0002> appears to be the DTC.

[joecar]

EE: see time/date box:

[Blacky]

Reading BBx config from V2 causes access violations:

first this one:


and then several of these:

Do you still have the Options.txt file on the V2 that is causing the problem?
Can you copy it from V2 using Explorer and send it to me.

Cahnces are its an older format Options.txt file and the newer software is barfing on some of the old formatting.
If I can get hold of the file I can see which formatting is causing the problem.

Regards
Paul

[Blacky]

V8 S&T, BBx: reading Options.txt file seems to wipe out custom units (it wipes out the selected custom units and the factor/offset).

Thanks Joe,

The BBX window is incorrectly saving the custom units like this:
"Y:::°F:1:1.800000:32.000000:N"
it should have been like this:
Y::°F:1:1.800000:32.000000:N
i.e. one less colon between Y and °F.

Fixed in next update.

Regards
Paul

[Blacky]

Reading BBx config from V2 causes access violations:

first this one:


and then several of these:

Thanks Joe,
Fixed in next update.
Paul

[Blacky]

EE: see time/date box:

I can't control the spaces, its a Windows date format thing. Not sure why/how it changed. It is changed on my system here as well.
I've made the field larger until I can figure out where the spaces are coming from.

Regards
Paul

[Blacky]

When viewing the readiness monitors on the V2 LCD, the formatting is jumbled up (strange characters, labels repeated in column fashion).

Fixed in next update.

When viewing Freeze Frames on the V2 LCD, it looks like that any whitespace characters are replaced with either up-arrow or down-arrow characters (this was actually happening previously a long time ago).

I can't reproduce what you describe. I do remember something similar a long time ago.
Can you give me more exact steps on trying to reproduce it.

When reading all diagnostics to file, the file content looks good, see attached.

In the freeze frame data, the field labelled <0002> appears to be the DTC.

Yes PID PRN=$0002 is the DTC that caused the freeze frame to be stored.
Anytime a freeze frame stores a PID that EFILive has not defined for the target controller, then it is displayed as <xxxx> where xxxx is the PID's PRN (Parameter Reference Number).

It is defined for the E38, it is not defined for the LS1. I presume you're seeing <0002> when viewing LS1 freeze frames.
I'll add it into all controller that it is missing from.

Regards
Paul

[shay]

Thanks
I tried it's not work.
In the Device Manager I think the Drivers looks good

The device name in the USB list is not correct. It says "USB Serial Converter". That is not FlashScan. The entry for FlashScan will show as "EFILive FlashScan V2".
The driver that you have highlighted is for another device using the same FTDI chipset. It may even be for FlashScan but using the generic (USB serial converter) drivers instead of the EFILive supplied customized D2XX drivers.

I recommend uninstalling the FTDI drivers like this:

Disconnect EFILive
Run the program: \Program Files\EFILive\Drivers\Utilities\Remove FDTI USB Drivers\CDMuninstallerGUI.exe
Enter the Vendor ID as 0403 and the Product ID as E4A0, then click [Add].
Enter the Vendor ID as 0403 and the Product ID as E4A1, then click [Add].
Enter the Vendor ID as 0403 and the Product ID as E4A2, then click [Add].
Enter the Vendor ID as 0403 and the Product ID as E4A3, then click [Add].
Then click [Remove Devices].

Then reconnect EFILive and when the "Installing USB drivers" balloon appears in the system tray, click on it and select "Skip obtaining drivers from Windows update".

Then go into the device manager and locate FlashScan. It will probably be highlighted with a yellow tag indicating it doesn't have a driver. It may not even be in the USB section.
Right click on it and select install (or update) drivers. Choose to locate the drivers yourself and navigate to the folder:
\Program Files\EFILive\Drivers\EFILive\Win-XP-Vista-7-8 and click [Install] or [Ok]

Regards
Paul[/QUOTE]

Thanks

I got message Failed to remove device.
I try to install the Drivers via update drivers from USB Serial Converter I use link Program Files\EFILive\Drivers\EFILive\Win-XP-Vista-7-8
Its not work.
I try to Skip obtaining drivers without success

Thanks
shay
I work with XP 32
Thanks
shay