pierremolinaro
commented
5 months ago Hello Bryan,
I have forgotten this function in the documentation, it is available for CANFD.
Do you use CAN FD frame with bit rate switch ? If not, the timing constraints are the same as CAN 2.0B, even if you use CAN FD frame without bit rate switch. So the Transmit EC should have the same behaviour as in CAN 2.0B.
If yes :
- what is the CAN FD transceiver you use ?
- check the data bit rate decomposition ; it is tricky, but bit rate switching requires the sample point to be as close as possible on all CAN FD controllers. If your network contains only Teensy 4.x with the same ACAN_T4 settings, of course it is ok, the sample points are equal. If you have different controllers, this should be checked. The function dataSamplePointFromBitStart returns the value in per-cent.
Best Regards,
Pierre
Le 6 avr. 2024 à 17:36, Bryan Miller @.***> a écrit :
Pierre,
I've been using the library for a while now and had been using ACAN_T4::can3.transmitErrorCounter() in my code. Since I upgraded to the current version, I'm getting a lot of Transmit EC: 97 in my logs. This log entry represents the error code from the previously mentioned function call immediately after a ACAN_T4::can3.tryToSendReturnStatusFD() call. I wasn't getting any error codes from the previous version of the library. I looked in the manual and didn't see a reference to this function call in the CANFD section, only the CAN 2.0B section. Is this call valid in CANFD?
Thanks, Bryan
— Reply to this email directly, view it on GitHub https://github.com/pierremolinaro/acan-t4/issues/9, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEWKZVCCIU4Z6NN67B67TQLY4AI6ZAVCNFSM6AAAAABF2Q4QFWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZDSMRZHA4DQMI. You are receiving this because you are subscribed to this thread.
syrinxtech
Pierre,
I've been using the library for a while now and had been using
ACAN_T4::can3.transmitErrorCounter()in my code. Since I upgraded to the current version, I'm getting a lot of Transmit EC: 97 in my logs. This log entry represents the error code from the previously mentioned function call immediately after aACAN_T4::can3.tryToSendReturnStatusFD()call. I wasn't getting any error codes from the previous version of the library. I looked in the manual and didn't see a reference to this function call in the CANFD section, only the CAN 2.0B section. Is this call valid in CANFD?One more thing, any idea what the number represents? It's not the same all the time. It seems to start at some number, count down for a number of packets, then disappear, only to reappear later with a different starting number.
Thanks, Bryan