RomRaider

I will have to agree with Cloudforce that 0xFA8F on 0110AD is part of the fac_ron_ad 98/91 blending factor and that's the value returned by the 0B 93 command.

It's a word variable in both MS42 and MS43 and is used to blend the 98/91 ignition tables.
When the factor is increased/decreased it's used as a word variable but when it's used to blend the 98/91 tables the low byte is not used, probably because they didn't need the extra resolution when performing the blending.

The reason why the MS42 0B 93 command does not return a word value could be to save space as only the high byte is used when blending.

If we have a look in Tool32 the MS43 0B 93 command is labeled as fac_ron_ad with a conversion formula of X * 0.00001526

Whatever the parameter is called, it is used with the RON related ignition tables.


Once a name and conversion is agreed upon I can update the official definition.

I think it would be nice to display it as a percentage.

Byte value: 100/255 * X
Word value: 100/65535 * X

dschultz: update in version >327

Just curious but is there an error in the intake air temp conversion? Its currently reading 29.2c but its 5c outside.

No. If your engine is warm, it affects the IAT quite drastically while car is not moving. Or if your engine is cold, then your IAT is broken.

I was trying to read knock adaptations from EU E38 728iA running AD software today.
First try was with Pazi's v5 logger and v35 beta1 ECU definitions - logger showed it is not possible to retrieve adaptation data (it told me to check connection to the car and if ignition is on...). Those files at least work for logging purposes.
Second try was with 323toslow's v3 logger and v0.36.323toslow ECU definitions - logger had serious issues with connection to the ECU and even if it connected had been dying silently (I did not have a chance to try to read adaptations).
The only combination which was able to read adaptation values (but knock adaptation were showed incorrectly - part of them was -48 even after clearing adaptations with INPA) was Pazi's v6 logger and 323toslow's v0.36.323toslow ECU definitions.
I will check later which exact software the ECU was running (I do not have access to my laptop now) but I would like to ask if those results are normal or something is wrong with my setup?

That is really odd. Next time you get a chance, clear your rr_system.log file out and then try to view knock adaptions with the logger def and ecu def files that are in my AD knock thread, then post up the contents of your rr_system.log file afterward. If you clear your adaptions, make sure the car is running after clearing, before you try to read the knock adaptions.

Maybe CA sw version? Don't remember if any logger file is edited so that the CA uses same addresses as C6 as it should. Well I did edit But I have been way too busy to post anything here....

For sure I will do it.


It was AD. Unfortunately I am away so I am not able to check exact software number because I do not have my laptop with me.

EDIT:
Please find attached log from LTV reading.

I don't think this is related to reading the LTV, but maybe to an improperly initialized connection through one of the J2534 drivers you have on your system. RR Logger should ignore these if there's no J2534 device connected and only use the COM port, which it started to. But then an access violation error occurred in 'C:\Program Files (x86)\ABRITES\Software for ID 171037\PassThru\AbrPT32.dll' and killed the Java VM.

Try stopping the existing connection with the DME (use the Disconnect button), then start the LTV read (press F6). There might be a conflict between two threads and J2534.

New logger def v330 with RON factor replacing knock global E24 (LTV will still label it Knk Gbl).
Please let me know how it works.

LTV reading doesn't work very well:


Seems that the storagetype is int8 when it should be uint8

Thanks

I noticed something about MS42.

o2 config 0, one precat no post cat sensors. If I do not have the o2 plugged in I cannot view LTV (Error)

When I plug it in and clear adaptions, LTV works perfect.

So it seems when fuel adaption is disabled by hardware, we cannot access the knock tables/fuel trims.

Not an issue for me now that I know, but had me confused for a while. Maybe someone else has hit the same issue.

I have noticed that also. You can't read LTV in bench setup