BB Logging beta update: April 14, 2008

[Blacky]

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.
...
Any chance of including something in the next update?
Simon.

Can someone check my math on this:

Given this:

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

I want to calculate λ*1000, does the following math work?

if (λ16 < 36864)
λ = (λ16*8.192) + 500 (Edit, should be: λ = (λ16/8.192) + 500)
else
λ = 5000 + ((λ16 - 36864 )*7.8125 )

Regards
Paul

[ringram]

Ok I do still have the corrupted log from yesterday. Its attached.
It should have been like 5mb+ but its tiny and busted.

[Blacky]

Ok I do still have the corrupted log from yesterday. Its attached.
It should have been like 5mb+ but its tiny and busted.

Strange, it has written the frame count back into the file as 38,344 frames, but not the data.
Did you save that file to an SD card or to the internal flash memory?
Either way, I would recommend (re)formatting whichever device it was meant to be saved to, just in case there is a FAT file system problem.

Regards
Paul

[ringram]

Yes its an SD card, I did another run today fine. I formatted it loads of times first on flashscan then using the efi_explorer.

Ill run a checkdsk on it etc. Will let you know if it happens again.

Found the DMA pid logging problem :( Looking forward to the fix for that.

[Lennart]

Todays experiences:
started the truck, drove out of the garage and started logging.
After frame #13 the logging froze up. Cancelled out of it and tried again. Next time it logged 3314 frames before it froze. After that it refused to log and I got Error $0185....even when trying to create a trace file.
Then switched to internal memory in hopes to be able to write the trace file there.....did not work either.
The memory information on the SD card using V2 said 1142kb used.
Using the EFILive_Explorer I get error $0183 when trying to acces the scan files.
Read the content of the SD-Card: All files gone except for a file called : "Ù<ÉMSDOS.5.0" with a size of 0kb.

[Blacky]

Todays experiences:
started the truck, drove out of the garage and started logging.
After frame #13 the logging froze up. Cancelled out of it and tried again. Next time it logged 3314 frames before it froze. After that it refused to log and I got Error $0185....even when trying to create a trace file.
Then switched to internal memory in hopes to be able to write the trace file there.....did not work either.
The memory information on the SD card using V2 said 1142kb used.
Using the EFILive_Explorer I get error $0183 when trying to acces the scan files.
Read the content of the SD-Card: All files gone except for a file called : "Ù<ÉMSDOS.5.0" with a size of 0kb.

What version and date of firmware in FlashScan are you using?
Regards
Paul

[swingtan]

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

Hi Ross,

I tried the DVT control of final spark timing and was able to get as far at 10.0' of retard before the error. as soon as I went to 10.1' I got an error " DVT: Commanded spark retard too high." ( screen shot attached ). Reducing the commanded spark retard returned normal operation, as can be seen in the image.

Simon.

[Blacky]

Hi Ross,

I tried the DVT control of final spark timing and was able to get as far at 10.0' of retard before the error. as soon as I went to 10.1' I got an error " DVT: Commanded spark retard too high." ( screen shot attached ). Reducing the commanded spark retard returned normal operation, as can be seen in the image.

Simon.

There is a setting in the ECM that determines the maximum spark retard for bidi controls, {B5144}.

Regards:
Paul

[swingtan]

There is a setting in the ECM that determines the maximum spark retard for bidi controls, {B5144}.

Regards:
Paul

Thanks... I hadn't seen that one

[GMPX]

Thanks Paul, I forgot about that exact calibration, but I had a feeling there was that in there.
I think to save the confusion and annoyance of it dropping out I might change the limit to 10 degrees. On all the E38 / E67 files I checked that appears to be the common limit defined in B5144.

Cheers,
Ross