Here is the email from Aug 9th:
- Unfortunately we could not reproduce the problem. Could you please let me know:
1.1. Which version of the USB-to-CAN V2 plugin do you use?
1.2. Which version of the VCI driver do you use?
1.3. Which .NET Dll is used? Vcinet2.dll or vcinet4.dll?
- Could you please let me know if you can reproduce the problem with the VCI3.NET-API application from the attachment.
VCI3.NET-Example.zip (1.1 MB)
The application initializes the USB-to-CAN V2 and send CAN messages with ID = 0x100 cyclically. The application checks the status of the CAN controller cyclically and stops/starts the CAN controller when CAN-Bus-Off occurs. I caused CAN-Bus-Off with a short between CAN_H and CAN_L wires for few seconds and the application successfully runs. As the second CAN node I used a CAN-IB600/PCIe CAN interface board with canAnalyser V3 mini that I had to stop/start manually when the CAN controller of the CAN-IB600/PCIe was in the CAN-Bus-Off mode.
- Could you please let me know if the CAN bus is always terminated with two CAN termination resistors?