Diagnosis Control devices can independently send diagnostic messages (DM). The most important diagnostic messages are DM1 and DM2. DM1 contains a list of the currently active diagnostic trouble codes

Diagnosis in the Application ECU State The ECU state of a device can be interrogated in the application in three different ways: <name in device tree>.State property ( IoDrvJ1939 library) <name in dev

Diagnosis in the User Interface Device tree In online mode, the device tree allows for an exact pinpointing of a pending diagnosis. Error flag (red triangle): Hard error, such as an incorrect/missing

Troubleshooting J1939 Problem Possible Solution The CAN bus node is red or has a red exclamation mark. See the general troubleshooting for the CAN bus. The J1939 Manager is red or has a red exclamatio

Libraries: J1939 IoDrvJ1939 :

CODESYS CANbus CODESYS supports the following CAN-based fieldbuses: CANopen J1939 For more general information on fieldbus support in  CODESYS , see: fieldbus support CANopen CANopen is a protocol whi

Configuration Tip See the general description for information about the following tabs of the device editor. Tab: <device name> I/O Mapping Tab: <device name> IEC Objects Tab: <device name> Parameters

Tab: CANbus – NetX Configuration As an alternative to the general CAN bus node, the CAN bus node (NetX) can be added to the device tree in the case of a NetX fieldbus. The NetX configuration dialog is

Functions CAN RAW CODESYS provides the capability of sending and receiving CAN messages via the application. No devices are required in the device tree to do this. The access can also be executed para

Diagnosis This chapter describes the general diagnosis in the case of CAN problems – regardless of the used fieldbus stack. Most problems are traced back to incorrect wiring or faulty bus device or CA