General In CODESYS , a CANopen Local Device is a slave device that you insert in the device tree of a project directly below a CAN bus node. As a result, the CODESYS runtime acts as a CANopen Slave. (
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: CANopen Local Device – General Table 17 . General Node-ID The node number identifies the CANopen Slave as unique (value range: 1...127). Device profile The device profile that is to implement the
Tab: CANopen Local Device – Object Directory This dialog is available only in the device editor of a CANopen device of version V3.5.6.0 or higher. It shows all objects of the object directory and thei
Tab: CANopen Local Device – PDOs Object: CANopen Remote Device, CANopen Local Device This dialog is available in the device editor of a CANopen Local Slave of version V3.5.6.0 or higher. It shows all
Tab: CANopen Safety Slave – SRDOs The tab is used for displaying the SRDOs and the experts in addition to the definition of the safety-related data objects (SRDOs). A maximum of 64 SRDOs is possible i
Tab: CANopen – Safety Slave – I/O Mapping Object: CANopen Safety Device (Slave) The tab corresponds to the CANopen Safety Slave – SRDOs tab, except that all mappings of the SRDO (all safety mappings)
Functions CANopen Safety CANopen Safety is released as a European standard (EN 50325-5). This means that data can be transmitted via CAN networks which meet the requirements for SIL3 applications. Thi
CANopen Diagnosis The chapter describes the diagnosis options offered by the CANopen protocol. CANopen State A CANopen network consists of a NMT master (network management) and NMT slaves. In this cas
