Has anyone seen this where the RPM CAN message from an AEM Infinity 5 times out as soon as the engine is running? My AEM Dash which is also over the network recieves RPM with no issues. With ignition on engine off the timeout counter is normal. As soon as the engine is running the timout flag turns on and there is no CAN signal. I'm using the preconfigured CAN inputs fromt Hardwire and the RPM is the only signal that times out, all other CAN inputs continue sneding data. I verified that the AEM's published CAN protocol matches what I have and it does. This is the only signal that times out. The only reason I need RPM is to signal my Electric Water pump to turn on when engine is running. A quick fix will be to put the water pump on the same trigger as fuel pumps but that doesn't explain why its not working. TIA
That fixed it. Thanks for the help with that!
Hi Joel, I have spotted a couple of problems with what you have posted.
A problem with the configuration software on V111 is that the filter numbers do not update when you retrieve the config. This means that all of the filter numbers are set to 1 which is incorrect. Please load the CAN Config in again to reset these value. A software fix will come in V112.
The second problem is see if that you have the Compound CAN Message filter enabled on this output. You have the value set to 0, so when the RPM is at zero, the message passes through the filter and you get the proper value. As soon as the engine starts (RPM>0) , the message no longer passes through the message filter so the CAN Input times out. Please just disable the CAN input message filter and try again.