Page 2
All rights, including those of translation, reserved. No part of this manual may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, micro-filming, recording or otherwise, without the prior written permission of Moeller GmbH, Bonn. Changes: V1.0 V1.01...
SmartWire Startup Guide V1.02 Contents Introduction ...................... 4 System components for motor starters with SmartWire ......5 Connections on the motor starter ..............7 Assembling a motor starter row ..............8 Electrically commissioning SmartWire ............10 SmartWire integration for XC100/200 via Profibus DP........ 12 PLC connection......................12...
SmartWire Startup Guide V1.02 1 Introduction SmartWire enables switching devices to be connected to a PLC without the need for any complex control circuit wiring. The control wiring between the PLC and the switchgear is replaced by the plug-in SmartWire module and pre-assembled connection cables.
SmartWire Startup Guide V1.02 2 System components for motor starters with SmartWire The following pages describe the setup, configuration and function of the SmartWire system using eight Moeller motor starters with the "SWIRE-DIL" SmartWire module for DILM contactors. The motor starters presented here consist of 5 components:...
SmartWire Startup Guide V1.02 3 Connections on the motor starter L1 L2 L3 Incomer wiring (AC load circuit) X1/X2 optional wiring NHI (auxiliary contact for PKZM) X3/X4 for opening the contactor control circuit (Jumpered as standard) Wiring for motor feeder (AC load circuit) The SWIRE-DIL has 4 screw terminals, X1/X2 and X3/X4.
The NHI may have been installed on the PKZ beforehand and the connection cables connected to the terminal X1/X2. All SWIRE-DILs are then interconnected using the SmartWire connection cables. The SWIRE-CAB-008 is recommended for connecting two starters with (DILM7…11 contactors).
Page 9
Ideally, the fieldbus gateway is positioned approx. 10 mm away from the first starter. SWIRE-CAB-015 is recommended as the SmartWire cable. The gateway requires two operating voltages: a) U : used for supplying the gateway and the SmartWire modules. Interface b) U : supply voltage here for the contactors on the motor starter ATTENTION! The power supply must be provided with appropriate fuse protection.
In this example with 8 motor starters and thus also SmartWire modules, the SmartWire gateway will detect the deviation when the first module is checked. This is indicated by the regular flashing of the SmartWire LED on the gateway and on the first SWIRE-DIL. The LEDs of SWIRE-DILs 2-7 flash in pulses.
Page 11
Once this configuration of the gateway has been completed successfully, this is indicated by the permanently lit SWIRE-LED on the gateway and all permanently lit Ready LEDs on the SmartWire modules (apart from the SWIRE-DILs). This means that the actual configuration has been accepted by the gateway and stored internally.
Ensure that the required GSD files are already located in the specified directory for the configuration files before CoDeSys is started. The following GSD files are required for the SmartWire Profibus DP gateway. Moe4D12_Intel V1_5.zip PROFIBUS-DP device data file (GSD) for SWIRE-GW-DP DPV0 slave GSD files for PLCs operating with the Intel data format.
Page 17
SmartWire Startup Guide V1.02 The Profibus DP slave (in this case SWIRE-GW-DP) can then be added to the PLC configuration. The Profibus DP slave address must be added in the DP Parameters tab for the XIOC-NET-DP-M module. In this case 3 is selected.
Page 18
SmartWire line set here does not match the actual configuration, the SWIRE-GW-DP operation will not start up properly. In this example a SmartWire line was set up with 8 motor starters and therefore also 8 SWIRE-DIL modules.
Page 19
SmartWire Startup Guide V1.02 The reference configuration must therefore be set as follows: Each SmartWire module has assigned to it a specific address area for status and control data. A total of 2 bytes is reserved for the SWIRE-DIL module.
Page 20
In the event of a fault on the SmartWire module, this bit is not set in certain cases. The basic function of the module on the SmartWire must therefore be monitored via the Profibus diagnostics.
6.4 Setting for Profibus node monitoring Each Profibus node can monitor the communication from the Profibus master. If, for example, in a running SmartWire system in which some contactors are controlled via the SWIRE-DIL, Profibus is to be disconnected, this is detected in the SWIRE-GW- DP by means of the watchdog functionality.
SmartWire Startup Guide V1.02 6.5 Diagnostics In order to use the diagnostics function, the library xSysDiagLib.lib must be added to the Library Manager beforehand. Two function blocks are available for analyzing the diagnostic data: • xDiag_SystemDiag • xDiag_ModuleDiag Software requirements: •...
Page 23
SmartWire Startup Guide V1.02 VAR_GLOBAL XcSystemDiag : xDIAG_SystemDiag; END_VAR The following instructions cause the cyclical processing of the system diagnostics and the monitoring of the Profibus master module XIOC-NET-DP-M on slot 1 of the XC controller. The diagnostics information is located in array element abyXcModuleInfo[1].
SmartWire Startup Guide V1.02 6.5.2 Profibus DP diagnostics For Profibus diagnostics (in this case for monitoring the XIOC-NET-DP-M Profibus master module described) the xDiag_ModuleDiag function block is used. ATTENTION! The instance of the xDIAG_ModuleDiag FB must also be declared in the "global variables"...
Page 25
SmartWire Startup Guide V1.02 abyExtendedInfo Meaning Profibus DP slave address 1..4 No meaning Length bytes of the device diagnostics * 6, 7 No meaning Byte 1 Profibus standard diagnostics (STATUS 1) bit0: Device not responding bit1: Slave not ready bit2: Divergent configuration...
Page 26
(two per slave) must be monitored. If both are zero, the SmartWire slave is OK. If both bits are 1, a module for example has an electrical fault or is no longer present on the SmartWire bus.
{ DOWNLOAD } It can be run on an XC CPU201-EC256K-8DI-6DO with an XIOC-NET-DP-M Profibus DP master module in slot 1. A SmartWire line of 16 modules (15xSWIRE-DIL and 1xSWIRE-4DI-2DO-R) is configured. All outputs and inputs can be controlled or read via the visualization provided.
{ DOWNLOAD } 7.1 PLC connection The CAN interface is connected via a standard fieldbus cable to the easy223-SWIRE SmartWire gateway. It must be ensured that the bus ends of the CAN connection cable are correctly terminated (each with 120 Ohm EASY-NT-R).
The appropriate eds file must be installed in order for the CAN slave station easy223- SWIRE to be configured in the easy Soft CoDeSys hardware configuration. The eds file for the easy223-SWIRE gateway can be downloaded from the Moeller ftp server at the following path: ftp://ftp.moeller.net/AUTOMATION/DOWNLOAD/...
Page 31
SmartWire Startup Guide V1.02 You can then add the CAN-Slave easy223-SWIRE as a sub element to the CAN master Ensure that the easy223-SWIRE gateway is set to CANopen mode and that the CANopen slave address is set the same as the setting in the easy Soft CoDeSys software.
Page 32
SmartWire Startup Guide V1.02 CANopen address of easy223-SWIRE must be entered here The CAN master provides two methods of monitoring CAN network nodes. Node Guarding and Heartbeat. Bear in mind that only one of the two methods may be selected.
SmartWire Startup Guide V1.02 7.4 Settings for CANopen node monitoring with Node guarding In order to use Node guarding, you must make the following settings. Ensure that no options for the heartbeat settings have been selected. the figure shows a Guard time of 100ms. Selecting a Life Time Factor of 5 means...
SmartWire Startup Guide V1.02 7.5 Settings for the CANopen Heartbeat node monitoring In order to use Heartbeat monitoring, you must make the following settings. Ensure that the option for Node guarding has not been selected. Settings for CANopen slave Selecting Activate heartbeat generation causes the easy223-SWIRE gateway (in this case CANopen slave as producer) to send a Heartbeat telegram on the CAN bus every 100ms.
SmartWire Startup Guide V1.02 7.6 CANopen slave monitoring The easy223-SWIRE gateway can be monitored in the XC200. The data structure pCanOpenNode : ARRAY[0..MAX_NODEINDEX] OF CanOpenNode from the folder CANopen implicit Variables (CONSTANT) can be used for this purpose. Note: The data structure is created automatically by easySoft CoDeSys during compilation.
Page 36
SmartWire Startup Guide V1.02 The status of the easy223-SWIRE gateway on the CAN bus is polled in the structure of the pCanOpenNode[0] array element under the element .nStatus. If the content of the element pCanOpenNode[0].nStatus = 5, this means that the easy223-SWIRE gateway is operational.
Page 37
SmartWire line is not defined for the CANopen solution. The system on the CAN side therefore starts up independently of SmartWire. The possible 4 control bits for each SmartWire module are mapped to a total of 8 bytes which are then sent by PDOs from the CANopen master to the easy223- SWIRE gateway.
Page 38
Details on the status data is already described in the Profibus DP section. Attention. In the CANopen solution, the Life bit is not transferred explicitly. It is "ORed" in the easy223-SWIRE gateway with bit7 (SmartWire slave status bit) so that the user only has to monitor bit7 in the PLC application.
SmartWire Startup Guide V1.02 7.7 Example program for XC200 (SWIRE-XC200-CANopen.pro) An example program SWIRE-XC200-CANopen.pro is available for test commissioning or for carrying out function tests on the SmartWire system. This can be downloaded under the following path: ftp://ftp.moeller.net/SMARTWIRE/English/01_PRODUCT/ 09_APPLICATION_NOTES/SmartWire_CanOpen_XC200/ { DOWNLOAD } It can be run on an XC CPU201-EC256K-8DI-6DO that is already provided with an integrated CAN interface.
Need help?
Do you have a question about the SmartWire and is the answer not in the manual?
Questions and answers