BB Logging beta update: April 14, 2008

Quote:

---

Originally Posted by ringram

Had an issue where a log file was corrupt and only 2kb in size. It should have been around 8-9Mb.

Also quick Q. I edited the config.ini file and added "ECM, AFRATIO_DMA", "ECM, E38.AFRATIO_M" and some other combinations but couldnt get it to list up the data in flashscan, it still just showed the default PIDs.

What am I doing wrong? (I put this under the *PSL_LS2 section which looked right for the E38.)

Other than that all is well. It would be good if you could indicate a default pid selection in the .ini file so you didnt have to manually select it each time. Kind of go straight to record..

---

Did you name the file Config.ini or Options.ini. FlashScan will ignore any file called Config.ini and continue to look at Options.ini.
I presume you used Options.ini and just made a typo in this thread.
The PID you need to select is the only permutation you probably did not try: AFRATIO_M
Note: The SAE., GM., E38. and E67. prefixes are not used in black box logging. And the _DMA suffixes have been changed to _M.
(Edit: Looks like you fixed it before I got done typing...)

The default PID selection will happen, I've been meaning to implement that for a while now. It will have two settings:
1. It can be set up to always load a defined PID selection.
or
2. It can be set up to always load the most recently used PID selection. The second option requires that FlashScan writes to the Config.dat file each time a PID selection is made. That takes an extra 1-2 seconds when selecting PIDs.

Regards
Paul

Quote:

---

Originally Posted by ringram

Had an issue where a log file was corrupt and only 2kb in size. It should have been around 8-9Mb.

---

Can you send the log file to me please? [email protected]
Regards
Paul

Quote:

---

Originally Posted by ringram

Other than that all is well. It would be good if you could indicate a default pid selection in the .ini file so you didnt have to manually select it each time. Kind of go straight to record..

---

I just re-order the PID selections in options.ini so my "default" is the first on the list. Then after connecting the V2 to the vehicle, I just hit <OK> 3 times to start logging.

Simon.

Hi thanks guys, I edited my post about the time Paul replied. I spied the E38.txt pid list and figured that out. As for the log file. Sadly I deleted it. If it happens again I will send it. It was about 1.5 hours of driving so perhaps that had something to do with it.

Yeah I meant options.ini Too much IT work makes me see config.ini everywhere.

swingtan I have chopped the list to 2 options.. might even drop the other to make that easier, thanks. OLSD in the E38 tomorrow :)

Also BTW: DVT Idle speed doesnt work, normal speed cause about 1500rpm to happen, you can go as low as you want and it only goes to the normal idle speed. I went down into the 300's and it was still around 800rpm.

Hi Guys,

I have been playing with a TechEdge 2J1 WB unit and attempting to get the serial connection working with the V2. After some initial work to match everything up I was able to detect the controller and receive serial data from the 2J1. the data however is rather interesting....

After speaking with Peter from TechEdge and reading the details of the unit, I think we need a new protocol set up for the current units ( or perhaps a change to the current V2.0 one ). It seems that the data supplied in the serial protocol changed mid to late 2007 from a 12 bit DAC value, to a Lambda-16 value. details as follows....

http://wbo2.com/2a0/logger.htm

Quote:

---

Bytes 6 & 7 This is λ-16 (originally Raw Wideband ADC value). In 2007 these two bytes have been redefined to be λ-16 which is fully described here. Originally it was a 12 bit value (0 to 4095) that is applied to the DAC (Digital to Analogue converter) and represents the voltage in mVolts produced by the DAC. The DAC is followed by a amplifier with a gain of 1.00 (for newer version 3 units) or 1.22059(=(68+15)/68 for older version 2 units). Note that the WBlin value is looked up in the WB unit's EE PROM tables using the pump current (Ipx) as index.

---

the conversion data is.....

http://wbo2.com/sw/lambda-16.htm

Quote:

---

Lambda-16 is an unsigned 16 bit number representing lambda (λ). For simplicity and to preserve accuracy across the possible range of Lambda, Lambda-16 is a dual-slope transfer function covering the ranges :
Lambda = 0.5 → 5.0 (normal usage range of unleaded AFR = 7.35 to AFR = 73.5)
Lambda = 5.0 → free-air (useful for non-tuning wideband applications)

Lambda (λ) is converted to Lambda-16 (λ16) as follows
If (λ < 5.0)
λ16 = ( λ - 0.5 ) * 8192
else
λ16 = 36864 + (( λ - 5.0 ) * 128)

Lambda-16 is converted to Lambda as follows:
if (λ16 < 36864)
λ = ( λ16 / 8192 ) + 0.5
else
λ = 5.0 + ((λ16 - 36864 ) / 128)

Note that AFR is directly related to λ, and λ16, by

AFR = λ * AFRstoich
AFR = (( λ16 / 8192 ) + 0.5 ) * AFRstoich (for the useful vehicle tuning range)

Where AFRstoich is the AFR value at stoich for the fuel used (14.7 for unleaded).

---

Any chance of including something in the next update?

Simon.

Quote:

---

Originally Posted by ringram

Also BTW: DVT Idle speed doesnt work, normal speed cause about 1500rpm to happen, you can go as low as you want and it only goes to the normal idle speed. I went down into the 300's and it was still around 800rpm.

---

I noticed this as well, E38 specific. Also found that "Spark Retard From Final Spark" worked for small changes, but if you tried to push it too far, the spark just went back to the commanded levels.

Simon

Having trouble with my SD card. In the file system page -> F1, F2, F3 are not working. Card info gives $0414, Free Space gives "space unknown!" and Format says "card not formatted, please reformat card before using"

Quote:

---

Originally Posted by swingtan

I noticed this as well, E38 specific. Also found that "Spark Retard From Final Spark" worked for small changes, but if you tried to push it too far, the spark just went back to the commanded levels.

Simon

---

If the changes stopped happening the ECM should have sent back an error, you should have seen this at the top of the DVT control screen. Did you notice anything?

There may very well be a retard limit in the ECM, I think from memory the calculation can work out to 256 degrees!, but that is just silly, so the limits you see in the DVT controls are what we put in place, if you can get some idea of where the ECM ignores the value that would be very helpful.

Cheers,
Ross

Quote:

---

Originally Posted by bballer182

Having trouble with my SD card. In the file system page -> F1, F2, F3 are not working. Card info gives $0414, Free Space gives "space unknown!" and Format says "card not formatted, please reformat card before using"

---

Just to verify that the card is ok, can you read and or format the card in a PC SD card reader?

Do you have a different card you can try in FlashScan to make sure its not FlashScan that is faulty? If it was a fault in FlashScan, the most likely cause would be a fault in the SD card holder where the pins do not contact properly.

What happens if you press on the SD card to hold it an extra mm into the socket while formatting it? Does that make any difference?

Lastly, some MMC cards do not work in FlashScan, make sure you are using a true SD card and not an old style MMC card. SD cards should say "SD" on them somewhere.

Regards
Paul

Quote:

---

Originally Posted by Blacky

Just to verify that the card is ok, can you read and or format the card in a PC SD card reader?

Do you have a different card you can try in FlashScan to make sure its not FlashScan that is faulty? If it was a fault in FlashScan, the most likely cause would be a fault in the SD card holder where the pins do not contact properly.

What happens if you press on the SD card to hold it an extra mm into the socket while formatting it? Does that make any difference?

Lastly, some MMC cards do not work in FlashScan, make sure you are using a true SD card and not an old style MMC card. SD cards should say "SD" on them somewhere.

Regards
Paul

---

Weird, the SD card was working in my laptop, but not in the FS. I tried a micro SD with adapter in the FS and that one worked. Swapped in the one for the FS and it works fine now. Before i tried swapping, i tried pushing it in the extra mm, removing and replacing, removing and powering down then powering back up and replacing. So i don't know whats going on, everything works fine; just formatted.