CAN bus adapter troubleshooting
This page covers the adapter status indicator, a Peak adapter that needs its driver, a CAN to Ethernet bridge that Auto Discovery does not find, and the bit rate that every device on a CAN bus must share. The adapters are listed on CAN bus adapters.
Adapter status
Once the adapter is added to the Profile, a coloured status indicator appears in the sidebar next to the device name. Green is the state of a working adapter.
| Colour | Meaning |
|---|---|
| Green | Good: the adapter is connected and data is arriving. |
| Amber | Warning: the adapter is connected but no data is arriving. |
| Red | Error: the Profinity System Logs have the details. |
| Grey | Not applicable: the adapter is not connected. |
If the indicator is amber, check that the bit rate matches the bus, that the bus is terminated and that another device is transmitting. If it is red, read the Profinity System Logs, then check the Peak driver, the IP address and port of a TCP bridge or the interface name of a SocketCAN adapter.
If a Peak adapter is not found
The Peak CAN to USB Adapter needs the Peak driver installed on the machine that runs Profinity, as set out in CAN bus adapters. Without the driver, the adapter does not appear in the Discovered category, and an adapter already in the Profile shows a red status with the message "The Peak driver is not installed. Install the latest Peak drivers from the Peak website, then restart Profinity."
Install the latest driver from the Peak System website, confirm with the Peak tools that the adapter works, then restart Profinity. Peak updates its driver often, and an out-of-date driver also stops the adapter connecting, so update the driver if the adapter is plugged in and still shows red. On Linux, a Peak adapter appears as a SocketCAN interface instead, so use the SocketCAN adapter and no Peak driver is needed.
If a CAN to Ethernet bridge is not found
Profinity discovers a CAN to Ethernet bridge from the UDP heartbeat datagrams that the bridge sends periodically (refer to Bridge Heartbeat). If the bridge does not appear in the Discovered category, check the following:
- The bridge and the PC are on the same subnet, because Auto Discovery does not work across subnets. Across subnets, add the bridge manually with its IP address and the TCP protocol.
- Any firewall allows UDP and TCP port 4876 for the bridge. For SocketCANd, the firewall must allow UDP port 42000 for discovery and TCP port 29536 (or the configured Port) for the connection.
- A WiFi router passes broadcast UDP.
The bridge documentation covers further troubleshooting: the CAN to Ethernet bridges, the Quickstart, the Supported Network Setups and Common Problems and Solutions.
Set the same bit rate on every CAN device
Every device on the CAN bus, including the adapter that connects Profinity, must operate at the same bit rate to communicate. Prohelion devices ship with a factory default of 500 kbit/s, which is also the default of the bridge, the Peak adapter and the CANdapter in Profinity. Prohelion devices support 1 Mbit/s and 500, 250, 125, 100 and 50 kbit/s, so a device changed from the default constrains the rest of the network. The CAN to Ethernet bridge does not terminate the bus, so terminate the CAN bus with 120 ohm resistors at each end (refer to the bridge DB9 connector datasheet).
For the parameters of each adapter, refer to CAN bus adapter settings.