Haltech Elite 2500 CAN mapping

thoraxe · Post by **thoraxe** » Thu Dec 21, 2017 12:50 am

After installing the CAN logger: https://wiki.autosportlabs.com/CAN_Bus_logger I do see messages being spit out.

There is also this script: https://wiki.autosportlabs.com/Haltech_PS1000_-_PS2000

But the app itself has the ability to map CAN channels.

Here's the latest Haltech protocol: https://www.dropbox.com/s/n2clv80g1js1s ... s.pdf?dl=0

Apparently the channel IDs in the Haltech book are hex, and converted to decimal they seem to line up with the PS1000 script above.

So, using the app, and for TPS specifically, I am guessing I need:

Channel: TPS
Rate: 50Hz
CAN ID: 864 (360 hex -> 864 decimal)
Offset: 4
Length: 2
Formula: * 0.1
Endian: Big

?

I'm away from the car until tomorrow.

thoraxe · Post by **thoraxe** » Thu Dec 21, 2017 1:07 am

Looking at the Haltech doc again: All 16bit values are signed two's complement

Post by **brentp** » Tue Jan 02, 2018 12:27 am

Not sure if I'm following your post. Does the Haltech script work as is? You have to ensure the script completely replaces what you have in the script window - delete any existing script first.

thoraxe · Post by **thoraxe** » Tue Jan 02, 2018 3:25 pm

I actually didn't try to use the script given that the CAN mapping feature now exists. It seems like you would want to use one or the other and not both.

I was able to use the CAN mapping feature in the app UI to pick and choose the channels I wanted. The only thing to note is that Haltech's protocol is big endian and uses signed values. As long as you check all the right boxes, it does work.

Once I get everything finalized I will upload my config somewhere.

Post by **brentp** » Tue Jan 02, 2018 3:43 pm

Wonderful. if you'd like to upload your mapping here we can double check it and then add it to the mapping presets we're offering for the next version of the app. Thanks for the update!