Disconnect CAN_B (9-pin D-Sub) from any other hardware - incorrectly configured hardware can bring the whole CAN bus down, making it look like a vehicle-side fault when it is not (see NOTE below).
Connect the CAN Breakout Harness as specified in Part 10 of the Hypermotive document 'HE362-105-E User Manual.pdf'. The required dongle is the 'Autonomous Driving Dongle'.
Connect your CAN Analyser to the CAN_B connector of the CAN Breakout Harness.
Set the CAN Analyser hardware to 500kbps bus speed.
Power up the vehicle, and check for the presence of CAN traffic, especially CAN IDs in the range 0x520->0x528.
If traffic is present, power down the vehicle and connect the user CAN hardware, configured for 500kbps.
Power up the vehicle again. If CAN traffic is no longer present, the hardware connected at step 7 should be checked.
NOTE:
Severe bus faults can cause the Vehicle ECU to latch off the CAN bus. There is a level of auto-recovery but if the bus is 'OFF' then a power cycle is required.
Additional:
Ref. step 3, all users of the vehicle need to be aware that the Autonomous Driving Dongle MUST be fitted for correct CAN communications, either directly to the vehicle or via the CAN Breakout Harness.
How to verify the presence of Vehicle ECU CAN
NOTE:
Severe bus faults can cause the Vehicle ECU to latch off the CAN bus. There is a level of auto-recovery but if the bus is 'OFF' then a power cycle is required.
Additional:
Ref. step 3, all users of the vehicle need to be aware that the Autonomous Driving Dongle MUST be fitted for correct CAN communications, either directly to the vehicle or via the CAN Breakout Harness.