BB Logging beta update: March 26, 2008

[Blacky]

I deleted WO2ST1 and WO2ST2 from Options.ini, I re-logged, and now the scantool correctly displays the log (see attached)...

Altho the scantool shows [Manual].

Also, in Options.ini I replaced AFR with EQIVRATIO, and during logging V2 shows EQIVRATIO units as "V";
it's units should be "EQ" or nothing.... can I change this...?

Yes, you can change it by adding an entry to the *PCU section in Options.ini. Use 1.0 for the factor and 0.0 for the offset since the value should be ok, just the units text needs changing.
Then select "Custom" units display in FlashScan. While logging, "Enter" toggles between Cutom and Metric units.

You can do that for any PID. Using the correct values for factor and offset you can change any PID to be displayed in any custom units that you would like.

I have fixed the units for the next release.

Regards
Paul

[joecar]

Paul,

I was reading thru the files LS1B_A_PIDs.txt and LS1B_M_PIDs.txt and
I noticed that SW1 appears twice instead of SW1 and SW2...
I noticed that V2 shows only SW1.

Cheers,
Joe

[Ninety8C5]

Also, in Options.ini I replaced AFR with EQIVRATIO, and during logging V2 shows EQIVRATIO units as "V";
it's units should be "EQ" or nothing.... can I change this...?

In LS1B_M_PIDs.txt and LS1B_A_PIDs.txt 'EQIVRATIO [2] Equivalence Ratio (V)'. Couldn't the (V) be changed to (AFR) or ()?

[Blacky]

In LS1B_M_PIDs.txt and LS1B_A_PIDs.txt 'EQIVRATIO [2] Equivalence Ratio (V)'. Couldn't the (V) be changed to (AFR) or ()?

See post #41 above.
Regards
Paul

[joecar]

In LS1B_M_PIDs.txt and LS1B_A_PIDs.txt 'EQIVRATIO [2] Equivalence Ratio (V)'. Couldn't the (V) be changed to (AFR) or ()?

The .txt files appear to me to be after the fact (and they don't get loaded onto the V2 is a giveaway) for documentive/verification purposes.

[Blacky]

The .txt files appear to me to be after the fact (and they don't get loaded onto the V2 is a giveaway) for documentive/verification purposes.

True, but the text files are generated by the same process that generates the *.pmm files and should contain the exact same data that is in the *.pmm files. So if the units are wrong in the text files then they will be wrong in the *.pmm files.

(Except the previous beta release where there was a bug in the program that generated the text files and some of the units were shown incorrectly in the text file when they were correct in the *.pmm files. There's an exception to every rule.)

Regards
Paul

[joecar]

True, but the text files are generated by the same process that generates the *.pmm files and should contain the exact same data that is in the *.pmm files.

Oh, similar in concept to a compiler/assembler output listing.

[Blacky]

Oh, similar in concept to a compiler/assembler output listing.

Yes.

[Chuck CoW]

It is a lot more stable than the early releases, I recommend holding off until we figure out the last few niggly problems. Should be about 2 weeks.

Regards
Paul

Does this mean that we can't/shouldn't try the serial wideband stuff until the next update if we're using it for production work?????

Paul, could I test the BBL/serial WB firmware on my spare V2 and not install it on the V2 with all the STREAMS and just use it for logging???

Right now, my analog inputs 1 & 2 on my main V2 are fried and I currently take both V2s in the car...one for logging and one for flashing.....

Would it be safe to test it on the "logging" V2 so as not to put myself out of business????

I really wanna try this!
Chuck CoW

[joecar]

Chuck, I would still wait.