Diagnosis in the Application CANopen State You can interrogate the state of a local CANopen slave in two different ways in the application: <name in device tree>.State property ( 3S CANopenDevice libr
Diagnosis in the User Interface Device tree In online mode, the device tree allows for a pinpointing of a pending diagnosis. Green symbol when the device is OPERATIONAL. Error flag (red triangle): If
Troubleshooting CANopen Local Device (Slave) Problem Possible Solution The CAN bus node is red or has a red exclamation mark. See the general troubleshooting for the CAN bus. The CANopen Device is red
Libraries: Reconfiguration – CANopen Local Device (Slave) 3S CANopenSlave Stack 3S CANopenSafety Slave :
J1939 J1939 is a CAN-based protocol (CAN stands for "Controller Area Network"). It was developed for serial data transmission between electronic control units (ECU) in heavy goods vehicles. The CODESY
General The J1939 Manager is inserted in the device tree below the CAN bus node. It provides the J1939 parameter groups and signal database. The ECUs are inserted below the J1939 Manager. The Scan Dev
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: J1939-ECU – P2P RX Signals This dialog is available for local ECUs only. It shows all PGs (parameter groups) that should be received by other ECUs. In this dialog, individual groups can be activa
Dialog: Data Layout Editor Graphical representation of the data layout of a parameter group The position of the data area is displayed graphically in a different color for each signal. Overlapping are
Functions Reconfiguration – J1939 With the "Reconfiguration" function, you can dynamically adapt a J1939 configuration at application runtime which was initially downloaded to the controller. With the
