Page 10 of 16
Re: ALDL ECU's
Posted: Mon May 11, 2015 2:20 pm
by Tazzi
VL400 wrote:No, there are A/D values and converted values.
A/D are the raw counts, or filtered counts (to reduce noise on the sample). Coolant voltage from the A/D is X / 51.2
Then you may also get the converted value from the ECU - ie linearised coolant that you use the (X * 0.75) - 40 with.
Another example is throttle position, you get a 0-5V value of the voltage read by the ECU (maybe is 0.6V for closed throttle to 4V for 100%) that you use X / 51.2 to get a voltage from the A/D counts, this is the TPS A/D or TPS voltage item. The ECU then scales this so that the learnt range (say 0.6V to 4V for closed to WOT) to cover 0-100%, being an 8bit item so you can use X / 2.56 to get a 0-100% reading when converting the TPS % item. Two differernt items for different tasks in the ECU.
There are multiple RAM locations for sensor reading. Take coolant as an example, there will be a raw reading of the A/D, a filtered A/D, a linearised value, a filtered linearised value, a non-defaulted value, a defaulted value (what gets substituted/used when a fault occurs). There are then others for special parts of the code, like the last reading, the startup coolant reading .... and so on
Alright.. Im assuming what I had before then was probably correct.
Yeah that does make sense then. Since different bytes in the ALDL stream correspond to the raw/filtered counts value and linearised value. Two completely different bytes.
That should be it I think for the initial build.
Re: ALDL ECU's
Posted: Wed May 13, 2015 9:33 pm
by Tazzi
I think Iv finally got it to a point Im happy with
For anyone that wants to have a test just let me know!
On all vehicles with a heartbeat, the frames/s is around 4 to 5. This is less than tunerpro but thats cause it does not disable any vehicle communication.
Vehicles without a heartbeat.. it runs at full pelt.
*Edit
As always, seems all antivirus will flag it as bad, as the software is brand new and also the licensing protection.
Re: ALDL ECU's
Posted: Thu May 14, 2015 10:08 am
by Tazzi
What Im mainly after testing is that all the gauges work correct! . And if the displayed values seem ok!
The Freeze Data is also of interest. Primarily on VR as thats the one Im most unsure about. Hopefully my crash course learning about A/D with VL has taught me something!
*Edit
Looking good so far! Currently AED is being used on:
-4 VY V6
-2 VX V6
-1 SC VX
-2 VT V6
-1 VR (waiting to here back on this)
Re: ALDL ECU's
Posted: Thu May 14, 2015 1:11 pm
by VL400
Other than being flagged by everything as a virus, it installed ok. Can you send me a serial number?
Re: ALDL ECU's
Posted: Thu May 14, 2015 2:51 pm
by Tazzi
VL400 wrote:Other than being flagged by everything as a virus, it installed ok. Can you send me a serial number?
Yeah, I know. It shits me that it does that. Only buggers off if I remove all embedded resources and licensing.
Will send on through.
Re: ALDL ECU's
Posted: Thu May 14, 2015 5:26 pm
by VL400
Got the serials thanks. Had to be connected to the web to load them? Installed and just testing on the bench for now, works well
The frames/sec calc must be a bit out as I noticed things were a bit jumpy, and the data LEDs on the ALDL interface were flickering more than normal. Scoped it and looks like this on the left, on the right is logging engine and trans using TunerPro...
Looks like a 200ms pause between the frames, might be able to fine tune some delays if you are looking for silence?
I couldnt get it to connect to a VR manual though...
Edit: Freeze frame works, but got a code 31 logged as unknown. This is "Theft deterrent input missing"
Re: ALDL ECU's
Posted: Thu May 14, 2015 5:59 pm
by Tazzi
VL400 wrote:Got the serials thanks. Had to be connected to the web to load them? Installed and just testing on the bench for now, works well
The frames/sec calc must be a bit out as I noticed things were a bit jumpy, and the data LEDs on the ALDL interface were flickering more than normal. Scoped it and looks like this on the left, on the right is logging engine and trans using TunerPro...
ALDL Log.jpg
Looks like a 200ms pause between the frames, might be able to fine tune some delays if you are looking for silence?
I couldnt get it to connect to a VR manual though...
error.png
Edit: Freeze frame works, but got a code 31 logged as unknown. This is "Theft deterrent input missing"
AED opens/closes the comport everytime if goes to send/receive data, could that explain that?
And I noticed the frames/s being jumpy on my VY V6 as well.. as it calculates the frames/s for both engine data and transmission data frames. I might do the entire frames/s calculation over both of the frames for a more smooth reading
Not sure why it wouldnt connect to the VR manual.. Ill have to double check what happened there or make a more "detailed" error message to describe why its not happy. My bet is the frame received was shorter than expected which set it off possible.
hmmmmm...
Will also check if I do have code 31 logged. Will check that now
Oh, and I also dont have the gauges/displays running on a separate thread. Just noticed I had that commented out why testing!
Re: ALDL ECU's
Posted: Thu May 14, 2015 6:03 pm
by Tazzi
I just checked in the VR definition files...
Looks like Iv made a mistake, Iv assumed the VR Auto 'engine' data is the same as the VR Manuals 'engine' data.
On the Auto, DTC 32 = Theft Deterrent Input Missing
On the Manual, DTC 31 = Theft Deterrent Input Missing
So theres problem number one for the VR!
I assume there is probably another reason why the engine data isnt working for the VR manual... Ill look at that next
Re: ALDL ECU's
Posted: Thu May 14, 2015 6:13 pm
by Tazzi
Just had someone else let me know that his VT V6 errored after reading engine data for about 5mins.
I previously had the checksum check disabled going to re-enable this and see if this makes a big difference! It may be that the application is grabbing the wrong data!
Re: ALDL ECU's
Posted: Thu May 14, 2015 6:20 pm
by VL400
The speed might improve by not closing/opening the port, would need to experiment there. The data rate should really be over both the frames as your wanting to know the rate an item is received - say RPM from the engine frame, with the current setup logging engine and trans its about 3Hz but its possible to get close to 6Hz with no delays.
What also got me thinking was the 4-5Hz on VT and later when looking at the heartbeat, the heartbeat only occurs every 300ms so the best you can get on them is really 3.3Hz getting one frame sent/received in the spare bus time. Logging both engine and trans you are down to around 1.6Hz.
On VR (and VS V8 series 1 and 2) Auto and manual engine data is the same, mode 1 message 0. Same data and size. I can connect to a VR manual ECU by selecting auto, the trans frame is just blank data.
There is no code 32, both VR auto and manual are code 31 for the missing VATS signal.