PDA

View Full Version : ALDLDroid with 6.5TD Engine run time parameter


hightekkrednek
06-11-2022, 10:34 PM
Good afternoon.. as partly stated in the title i have a 1995 6.5td and am using ALDLDroid on Android 10. This app is great! The only item so far that I have tried using that hasn't worked in my situation is the "Engine Runtime" parameter, it always reads "25.50". Now, I am assuming that should read how long the engine has been running since last start.. but, I could be wrong and it may just be the variable for some other setting. I was curious if anyone might know about this? I have asked Sebastien but he felt it may be adx file related and that someone here or on dieselplace might have a better understanding of this issue on the 6.5td platform, so here I am first. Thank you

Dennis
kur4o
06-11-2022, 10:42 PM
25.5 converts to ff/10 in hex. It should be 16 bit counter, seems the adx is set up incorrectly. Post the adx, it may be something obvious, or the pcm might not support that parameter stream.
hightekkrednek
06-11-2022, 11:31 PM
25.5 converts to ff/10 in hex. It should be 16 bit counter, seems the adx is set up incorrectly. Post the adx, it may be something obvious, or the pcm might not support that parameter stream.

adx attached


Also, here are two similar pieces but I am not sure what MSB or LSB is yet nor is it the option I used here.. just mentioning it incase someone knows and can tell me.



<ADXBITMASK id="455" idhash="0xCD4F47BB" title="ENGINE RUN TIME(MSB)">
<parentcmdidhash>0xE68E9C55</parentcmdidhash>
<ALARMONSET color="0x000000FF" />
<ALARMONNOTSET color="0x0000FF00" />
<packetoffset>0x37</packetoffset>
<bitop>AND</bitop>
</ADXBITMASK>


<ADXBITMASK id="456" idhash="0xCD4F441B" title="ENGINE RUN TIME(LSB)">
<desc>SECS=N*.1</desc>
<parentcmdidhash>0xE68E9C55</parentcmdidhash>
<ALARMONSET color="0x000000FF" />
<ALARMONNOTSET color="0x0000FF00" />
<packetoffset>0x38</packetoffset>
<bitop>AND</bitop>
</ADXBITMASK>


Thank you
kur4o
06-11-2022, 11:55 PM
It was set as 8bit stream, I changed it to 16bit and remove alarm limits and removed decimals so it shows full seconds.

Hope it works now.
hightekkrednek
06-12-2022, 01:40 AM
Thank you! I will test this within the hour and see if that fixes it.
hightekkrednek
06-12-2022, 02:42 PM
Got it moved over lastnight but it remained a 0 for the 45 minute drive I had.
kur4o
06-12-2022, 10:21 PM
It could be a pcm issue, It may need some debugging and a disassembly to figure what is wrong with that parameter.