You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed during vehicle testing that the default build doesn't seem to have the AF in bypass, or something else is wrong in code.
When I plugged it in and turned the car on, I expected the VI to turn on and the CAN activity light to turn blue. I expected it to stay powered on while the was running. I would not expect to be able to read CAN messages via USB until I configured it to passthrough these messages.
Instead, it powered up by with a red CAN activity light (no activity detected). Every 5 seconds it tried to go sleep, but then woke up immediately. While it was awake, I was able to set the AF bypass on via USB, and then the CAN activity light went blue.
It seems like the CAN AF is configured to accept messages, otherwise it should not wake the VI up. However that doesn't seem to be noticed in code. I'll have to check and see if the AF bypass config field of the CanBus struct is getting out of sync with the actual AF status.
The text was updated successfully, but these errors were encountered:
I noticed during vehicle testing that the default build doesn't seem to have the AF in bypass, or something else is wrong in code.
When I plugged it in and turned the car on, I expected the VI to turn on and the CAN activity light to turn blue. I expected it to stay powered on while the was running. I would not expect to be able to read CAN messages via USB until I configured it to passthrough these messages.
Instead, it powered up by with a red CAN activity light (no activity detected). Every 5 seconds it tried to go sleep, but then woke up immediately. While it was awake, I was able to set the AF bypass on via USB, and then the CAN activity light went blue.
It seems like the CAN AF is configured to accept messages, otherwise it should not wake the VI up. However that doesn't seem to be noticed in code. I'll have to check and see if the AF bypass config field of the CanBus struct is getting out of sync with the actual AF status.
The text was updated successfully, but these errors were encountered: