BB Logging beta update: April 07, 2008

[joecar]

FUELSYS logged correct value ok on V2, but scantool shows value "unknown" thru-out.

FTC is ok.

Scantool still shows [Manual] for LS1B_A logs from V2.

The scantool sees FUELSYS as a selected pid, but displays it's value as "unknown" flat across.

[Blacky]

The LED's don't seem to do what the the alarm bits specify, altho the alarm sounds ok.

Have you got the LED status set to "Alarm" instead of "Status" or "Off"?
You can change it in the config settings in FlashScan.

Regards
Paul

[bballer182]

There is no recovery if EFILive_Explorer cannot see the FlashScan unit.

Please send it back to Fish Tuning to be reprogrammed manually.
Contact details for Fish Tuning are on our resellers web page.

Regards
Paul

Crap, that's what i was afraid of.

[joecar]

Have you got the LED status set to "Alarm" instead of "Status" or "Off"?
You can change it in the config settings in FlashScan.

Regards
Paul

Ah, I'll try that, thanks.

[joecar]

Looks like the file system is requesting two sectors be updated. I will increase the timeout to 10 seconds.

Regards
Paul

I reformatted both file systems and now I don't get the error when setting the date/time.

[mr.prick]

why doesn`t the V2 control panel work any more?
it was easier to calibrate the AD inputs when you
could see the voltage through the software.
now the only way to do it is through the V2 itself and
that seems to be a bit difficult when you cant see
the voltage in real time.
before the control panel was animated.
this is just a general complaint with the software not a bug.
also while i`m complaining, it would be nice to scan though
the V2 and the software at the same time.

[Blacky]

why doesn`t the V2 control panel work any more?
it was easier to calibrate the AD inputs when you
could see the voltage through the software.
now the only way to do it is through the V2 itself and
that seems to be a bit difficult when you cant see
the voltage in real time.
before the control panel was animated.
this is just a general complaint with the software not a bug.
also while i`m complaining, it would be nice to scan though
the V2 and the software at the same time.

Just haven't updated it to work with the new firmware yet.
It will get done.
Paul

[Tordne]

Did you change the connection (cable type) in the Scan Tool to be the V2.5 FlashScan interface? Perhaps also disable the cable auto detection.

[Lennart]

For me everything worked out rather smooth, but while BB logging my LLY the PID GM.TP is not logged even though it is included in the options.ini
I also had to remove the Allison PIDs from the options.ini for the V2 to start logging frames. Before it was just toggeling between 0 for all values and the actual value without increasing the frame counter.
This might have been caused by the large number of PIDs I log.

[Blacky]

I have fixed a number of connection/detection issues in the latest update. Hopefully I can release it by Sunday night.

Please try again with the new software to see if those problems are resolved.

Regards
Paul