Master/Slave functionality supported
An external CANopen configuration tool is used to configure the nodes on the CANopen network. The resulting Concise DCF file is downloaded to the CANopen network master using a CANopen adapter. At the next startup the CANopen master will configure the network. The 1 SI CANopen Module can be configured either as a master or as a slave on the CANopen network.

CANopen Configuration Manager - Included with the 1SCANopen
Any CANopen Configuration Tool can be used to configure the 1 SI CANopen. If you do not have CANopen configuration software, HMS provides a CANopen Configuration Manager, which is included in the price of the 1SICANopen module. It has been fully tested and verified and works only with the 1 SI CANopen Module and the Anybus X-gateway CANopen Master also from HMS.
 

CANopen configuration is made by importing a provided EDS file into the CANopen configuration tool. The EDS file for the 1 SI CANopen Module can be downloaded here. The necessary information for configuring the module into the ET200S Distributed I/O System is present in the SIMATIC Step7 tool and will not have to be downloaded separately in order to perform PLC configuration.

CANopen - USB Interface
To download the CANopen configuration from the CANopen Configuration Manager you need to access the CANopen bus from your PC using a USB - CAN interface. HMS can supply a USB-CAN interface additionally: Order code: 020810-B, if you do not already have this.

After the configuration is finished, the CANopen network configuration can be uploaded to and stored in the Profibus/Profinet PLC or the ET200S I/O System CPU. If the 1 SI CANopen Module has to be replaced by another module, the previously stored configuration can be downloaded to the new module. The communication can then be restarted without any unnecessary delay. The change of modules can be performed with power still on. To perform upload/download of configuration, you need a function block which can be downloaded here.

CANopen Supported Features
• CANopen implementation according to the CANopen specification DS301 rev. 4.2. CANopen Master implementation according to DSP302 (Part 1-5)
• PDO (Process Data Objects) functionality, Push and Pull
• 128 Receive and 128 Transmit PDOs
• SDO Client functionality (Expedite & Segmented Upload/ Download Domain Protocol)
• Configuration possibility via SDOs
• Heartbeat producer/consumer functionality
• Selectable baud rate from 20 kbit/s – 1 Mbit/s
• Supported PDO message types: COS (Change Of State), Cyclic Synchronous, Acyclic Synchronous

CANopen Master Specific
• SDO (Service Data Objects) Server functionality
• NMT (Network Management Telegrams) Master to be able to start-up and monitor the network
• Node guarding - producer/consumer
• Synchronization - producer/consumer
• LSS master functionality

CANopen Slave Specific
• NMT (Network Management Telegrams) Slave state machine
• Node guarding - consumer
• Synchronization - consumer
• LSS slave functionality
• Automatic baud rate detection