canbus-integrationlisted

# CANBus Integration ## Overview Use this skill for embedded CAN bus libraries and CANBus-Triple style projects. CAN failures are often physical-layer, bit-timing, termination, transceiver, or filter problems before they are application protocol problems. ## When To Use Use this skill when: - The user mentions CAN, CANBus-Triple, MCP2515, SocketCAN, CANopen, J1939, UDS, OBD-II, ISO-TP, or automotive messages. - Frames are missing, bus-off occurs, IDs are wrong, filters reject messages, or bit timing is unreliable. - The task involves adapting a CAN example project or Arduino-style CAN platform to another board. Do not use this skill when the target is only a generic UART/SPI issue with no CAN layer. ## First Questions Ask for: - CAN controller/transceiver and board, such as internal CAN, FDCAN, MCP2515, or CANBus-Triple. - Bus speed, oscillator frequency, sample point, and whether CAN FD is involved. - Wiring, termination, transceiver voltage, and whether another known-good node is present. - Frame IDs, standard/extended format, filters, masks, and expected traffic. - Library/project source and current error counters, bus state, or capture. ## Integration Checklist 1. Verify physical layer. Confirm CANH/CANL wiring, 120-ohm termination, common ground, transceiver enable/standby, and voltage compatibility. 1. Confirm bit timing. Controller clock, prescaler, segments, sample point, and bus speed must match the network. 1. Start with listen or loopback. Use