AEM Infinity CAN channel mapping script
So the first CAN bus. That seems to correlate with the '0' you have in the script as well - you must be using the default script, as-is.
As you can see, the script seems to show that it's not receiving any data at all.
You might want to double check the connections and the settings in the AEM system to verify it's broadcasting correctly.
It also looks like it's setting the baud rate to 500K - is termination is enabled? How about if termination is disabled?
Are the AEM and the RCP the only two devices on that CAN bus?
You said you had a separate script that was correctly mapping the data - does that still work?
As you can see, the script seems to show that it's not receiving any data at all.
You might want to double check the connections and the settings in the AEM system to verify it's broadcasting correctly.
It also looks like it's setting the baud rate to 500K - is termination is enabled? How about if termination is disabled?
Are the AEM and the RCP the only two devices on that CAN bus?
You said you had a separate script that was correctly mapping the data - does that still work?
Termination was enabled
AEM and RCP are directly tied together and the only thing on the CAN network
The script I used was this one:
https://wiki.autosportlabs.com/AEM_Infinity_6H
I reset the firmware, then loaded the script for the AEM and the can channels in the script work again, with both termination enabled and disabled.
AEM and RCP are directly tied together and the only thing on the CAN network
The script I used was this one:
https://wiki.autosportlabs.com/AEM_Infinity_6H
I reset the firmware, then loaded the script for the AEM and the can channels in the script work again, with both termination enabled and disabled.
- Attachments
-
- Capture.JPG (85.72 KiB) Viewed 4061 times
well not sure how to explain it but it all works, except steering.. which may just be an issue with the way the OEM BMW steering angle sensor is with the AEM.
I reset firmware, then ran known good script and those few channels started.
Then i tried to turn on the custom channels but the overlapping channels were making the data fluctuate badly.
I the reloaded the firmware, made sure to clear script and turned on all my custom channels again... and boom. They all showed up and are working.
Not sure how, but I will take it.
I reset firmware, then ran known good script and those few channels started.
Then i tried to turn on the custom channels but the overlapping channels were making the data fluctuate badly.
I the reloaded the firmware, made sure to clear script and turned on all my custom channels again... and boom. They all showed up and are working.
Not sure how, but I will take it.
- Attachments
-
- Capture.JPG (118.38 KiB) Viewed 4060 times
LOL, makes it easier to visualise.
So, i hooked the laptop up to AEM, and opened thier tuning software and was able to verify that AEM in fact can see the stock steering senor and it is working.
Here are the screenshots from AEM, in the PDF it lists it as a 2 bit data length with 2 offset in the table. This says it is a 24bit offset with length 16. I tried using the bit mode enabled to selsct the 24(16) for the steering angle sensor but got nothing. Do i need a mask or othr offset for this type of data?
So, i hooked the laptop up to AEM, and opened thier tuning software and was able to verify that AEM in fact can see the stock steering senor and it is working.
Here are the screenshots from AEM, in the PDF it lists it as a 2 bit data length with 2 offset in the table. This says it is a 24bit offset with length 16. I tried using the bit mode enabled to selsct the 24(16) for the steering angle sensor but got nothing. Do i need a mask or othr offset for this type of data?
- Attachments
-
- AEM1.jpg (215.38 KiB) Viewed 4047 times
-
- AEM2.jpg (160.11 KiB) Viewed 4047 times
-
- AEM3.jpg (195.3 KiB) Viewed 4047 times