CAN_trouble.plecs (452.3 KB) I used CAN communication in my model with the previous PLECS 4.9 version and never experienced sudden disconnections. However, after I upgraded PLECS to version 5.0, the exact same model keeps suffering from sudden CAN communication disconnections, which in turn trigger the PWM protection configured in my software.
I had to revert back to version 4.9. The CAN communication issue is much improved in 4.9, yet occasional sudden disconnections still occur.
Could you please advise what causes this problem? Did PLECS 5.0 make any adjustments to CAN communication functionality? Or is there non-standard or problematic design in my CAN communication model itself?
In addition, the following warning messages keep popping up repeatedly in my CAN communication software:
System 47-0024 CAN 1: The filter for the NACK error frames has been enabled!
System 47-0025 CAN 1: The filter for the NACK error frames has been disabled!
System 47-0024 CAN 1: The filter for the NACK error frames has been enabled!
System 47-0025 CAN 1: The filter for the NACK error frames has been disabled!
Hi yuhangzhou, could you clarify the TI TSP versions you are using for the model run in:
As shown in the figure, the version of the TI C2000 support package I use in both PLECS 4.9 and PLECS 5.0 is 1.10.5.
Hi yuhangzhou,
I’m only able to provide support for the latest version of the TSP, so I would recommend upgrading to the most recent release. You can download and install it by clicking the download icon next to the TSP version in your screenshot, or directly from our website:
Additionally, your model is quite complex, so the best way to narrow down the issue is to simplify the setup. Since you are encountering difficulties with the CAN module, I recommend starting with the PLECS demo model “Simple CAN Model”, which is included in the TI TSP package. You can find it in the demo model browser under:
TI C2000 Target Support Demos > Connectivity
The demo model documentation provides guidance on how to set up the hardware. Since TI LaunchPads only include a single CAN transceiver, you will need two boards to communicate with each other.
Alternatively, you can use a CAN monitor (for example, a Kvaser interface with CAN King) to observe messages on the bus. It is also possible to run the test with a single TI board, but you will still need another active node on the bus (such as a CAN monitor) to prevent the bus from entering a shutoff state.
Hope this helps!
