Vehicle CAN data can be used in MaxxECU for trigger certain functions, or log data if CAN ID are known.
A CAN analyzer must be used to "sniff" vehicle CAN, if the CAN ID/data are not known, example of a good and simple CAN analyzer: www.cananalyser.co.uk/
For more information regarding CAN bus: wikipedia.org/wiki/CAN_bus
CAN input value
Enable or disables this function.
Specifies which CAN bus to use (more than one CAN bus is only available in MaxxECU PRO).
CAN message ID
Message ID (decimal value) to be used.
Byte offset to use. Example: second byte, offset = 1.
Big-endian and little-endian are terms that describe the order in which a sequence of bytes are stored in computer memory.
•Big-endian is an order in which the "big end" (most significant value in the sequence) is stored first (at the lowest storage address).
•Little-endian is an order in which the "little end" (least significant value in the sequence) is stored first.
•Signed variables, such as signed integers will allow you to represent numbers both in the positive and negative ranges.
•Unsigned variables, such as unsigned integers, will only allow you to represent positive numbers.
Value = 0.1*(Indata+Offset)*Multiplier/Divider
Offset to use in the conversion formula.
Multiplier to use in the conversion formula.
Divider to use in the conversion formula.
Note: see below current value top check your final value to be used in MaxxECU.
Name of the converted value. Visible in MTune.
Unit for the converted value. Visible in MTune.
Value will be visible in RealTime Data --> User CAN inputs.
Can be used in MaxxECU as any other RealTime value for conditions or warning. For example it can be used to read GPS SPEED from CAN and use as a wheelspeed input.
The final value after all conversion, this value is to be used in MaxxECU.
Note: 0x430 is hexadecimal and it's the same as decimal value 1072.
A display from a CAN analyzer on a Ford Mustang 2011, ID 0x430 (hexadecimal) is highlighted and in this example we pay attention
to the sixth byte (D6) which has default value of 0x10 (hexadecimal).
Same CAN analyzer output on this Ford Mustang, but right now the Traction/EPS button is pressed. ID 0x430 (hexadecimal) and D6
value was now changed to 0x90 (hexadecimal).
Conclusion: When press and hold the Traction button, CAN ID 0x430, D6 byte is changed from 0x10 to 0x90.
Red arrow: Enter the decimal value which we will use as input 0x430(hex) = 1072(dec).
Blue arrow: Since the data we are looking for is in the sixth byte (D6) we will enter a byte ofset of 5 (skip the bytes before and just pay attention to the D6).
Green arrows: Indicated the converted value from vehicle CAN when Traction button is untouched, which can be used in MaxxECU for controlling functions
Green arrows: Indicates the converted value from vehicle CAN when Traction button is pressed.
In the above example the Ford Mustang Traction button only change value on the CAN when pressed, therefore we will use an internal output to take use of a
Another Internal output is used to disable the Traction control feature (which is active all the time in the Traction control settings). Pay attention to the Inverted output since we
trigger the internal function Disable Traction control.
Note: This was just a simple example of what can be made using the User CAN input function, a lot of more advanced functions can be made.