Greetings. I am running IFCT on a 3.2 on Arduino 1.8.8. I am talking to a KDE DirectESC (an Electronic Speed Controller, or ESC) over the CAN bus. I can query the state of the ESC using CAN, and I do so.
My app is simple: write a CAN packet which queries some trivial state on the ESC, call delay(2), then read, if it's available, the response.
My CANalyst-II CAN bus analyzer tells me that when I send the query, the ESC responds pretty much immediately (the time stamps in the analyzer are supplied by the analyzer and not by Windows). Oddly, the very first response from the ESC is not seen by the Teensy. The rest of the responses are. When I say "seen", I mean that the ISR function in the IFCT source does not see the response (I know because I have mod'd the ISR to capture the data packets which are collected by the ISR).
Why wouldn't all packets sent to the 3.2 be seen by IFCT?
Thanks.
My app is simple: write a CAN packet which queries some trivial state on the ESC, call delay(2), then read, if it's available, the response.
My CANalyst-II CAN bus analyzer tells me that when I send the query, the ESC responds pretty much immediately (the time stamps in the analyzer are supplied by the analyzer and not by Windows). Oddly, the very first response from the ESC is not seen by the Teensy. The rest of the responses are. When I say "seen", I mean that the ISR function in the IFCT source does not see the response (I know because I have mod'd the ISR to capture the data packets which are collected by the ISR).
Why wouldn't all packets sent to the 3.2 be seen by IFCT?
Thanks.