BB Logging beta update: May 03, 2008

[Blacky]

When I did that it displayed both Vin/OS as "Unknown".

I hope the problem is as simple as this...

I can reproduce the problem you are seeing if I connect FlashScan to the vehicle *before* the ignition is switched on.
You should always turn on the ignition first, then connect FlashScan to the vehicle, then to the laptop (if you want to use a laptop).

That is because as soon as FlashScan is powered up it attempts to detect the coms protocol and available modules in the vehicle. If the ignition is off the modules do not respond to FlashScan and so FlashScan does not know what modules are available.

However, once the ignition is switched on, FlashScan should re-analyze the protocols and modules. It is not doing that correctly. I will fix that problem. Meanwhile, try turning on the ignition before connecting (i.e. powering up) FlashScan.

Regards
Paul

[405HP_Z06]

405,

V2 BBL does not provide calc pids [at the moment]...

Calc pids can be added in later when viewing the log in the scantool (you select the calc pids you want [PIDs tab], and then you save the file).

Pids ending in _M are _DMA pids (e.g. DYNCYLAIR_DMA [in the scantool] corresponds to DYNCYLAIR_M [in V2 BBL]...)

Thanks Joecar! Trying to get used to EFILive after so many years of HPT. I know the BBL is still beta here, but it's much easier in HPT. I look forward to working with EFI, much nicer in many other respects.

[JR-CRUZN-C5]

Paul -

Once "stable" BBL is out - Recommended Drag Strip BBL procedure would be to NOT plug the V2 into the OBDII cable UNTIL right before the car is pulled into the Burn Out Box because the ignition will be turned on and off numerous times while moving up in the staging lanes! Unless someone breaks or the starter shuts things down the ignition pretty much stays on from the Burn Out until the end of the race. On the V1 I would start BBL right before the burnout box and have it set to shutoff after 1 minute - this is on TEST runs only when the driver has control over the staging proceedure.

JR

[Ninety8C5]

I hope the problem is as simple as this...

I can reproduce the problem you are seeing if I connect FlashScan to the vehicle *before* the ignition is switched on.
You should always turn on the ignition first, then connect FlashScan to the vehicle, then to the laptop (if you want to use a laptop).

Regards
Paul

With the ignition on the V2 gets the correct VIN, but the OS is still "Unknown". I sent you the trace files via email.

[joecar]

Thanks Joecar! Trying to get used to EFILive after so many years of HPT. I know the BBL is still beta here, but it's much easier in HPT. I look forward to working with EFI, much nicer in many other respects.

405,

No worries.

I know, changing to different software/hardware can try one's patience...

V1 BBL was pretty easy... gui interface... but no controls on the V1 (only start/stop);

It seems to me that V2 BBL will be similar but with more controls on the V2...
I think the current manual process will get replaced by a gui [am I right Paul...?].

Hey, glad you could be here... I find there's always something new to learn...

Cheers,
Joe

[Blacky]

Paul -

Once "stable" BBL is out - Recommended Drag Strip BBL procedure would be to NOT plug the V2 into the OBDII cable UNTIL right before the car is pulled into the Burn Out Box because the ignition will be turned on and off numerous times while moving up in the staging lanes! Unless someone breaks or the starter shuts things down the ignition pretty much stays on from the Burn Out until the end of the race. On the V1 I would start BBL right before the burnout box and have it set to shutoff after 1 minute - this is on TEST runs only when the driver has control over the staging proceedure.

JR

For FlashScan V2, once the bugs are ironed out it won't matter if the ignition is turned on/off while logging, or before or after FlashScan is plugged in. But until then, your suggestion is a very good one.

Regards
Paul

[Blacky]

I think the current manual process will get replaced by a gui [am I right Paul...?].

Yes.

Regards
Paul

[Blacky]

Trace file on the way email titled "Beta Test 98 Vette (19980400) DMA PIDs".

Also seeing same results as ScarabEpic22 in Tune Tool Flash & Cal counter.

Thanks for the trace file. It pinpointed the problem nicely.
I have reproduced the exact problem here and fixed it.

For your info...
The 97/98 PCMs did not have an operating system number so EFILive "fakes" one. The operating systems are faked based on information extracted from the VIN.
The 3 possible fake operating system numbers are:
19970200 1997 C5
19980100 1998 Camaro
19980200 1998 C5

When the tuning tool reads out the contents of the PCM, it can dig deeper into the operating system and extract information not available to the scan tool. The extra information allows the tuning tool to identify 2 extra variants of the 19980100 and 19980200 operating systems:
19980300
19980400

That is why in the tuning tool you may see 19980100 or 19980200 or 19980300 or 19980400, but in the scan tool you will only see 19980100 or 19980200.

Regards
Paul

[Ninety8C5]

Thanks for the trace file. It pinpointed the problem nicely.
I have reproduced the exact problem here and fixed it.

I'm glad the trace files helped. Can't wait to check out the fix.

For your info...
The 97/98 PCMs did not have an operating system number so EFILive "fakes" one. The operating systems are faked based on information extracted from the VIN.
The 3 possible fake operating system numbers are:
19970200 1997 C5
19980100 1998 Camaro
19980200 1998 C5

When the tuning tool reads out the contents of the PCM, it can dig deeper into the operating system and extract information not available to the scan tool. The extra information allows the tuning tool to identify 2 extra variants of the 19980100 and 19980200 operating systems:
19980300
19980400

That is why in the tuning tool you may see 19980100 or 19980200 or 19980300 or 19980400, but in the scan tool you will only see 19980100 or 19980200.

Regards
Paul

The only cal files I've seen are the 19980100, 19980200 and 19980400. I had no ides that the other two existed as they did not show up in any of the downloads.

[oztracktuning]

I used it successfully logging in our Nitro Champs meet in Sydney. With my 1290005 op system it didnt matter if i turned the key off etc. I have nice logs of all the runs and it made it very convenient to take the sd card to the laptop - tweak the tune and then flash using roadrunner.