User Guide AnyBus NetTool for DeviceNet

Transcription

1 User Guide AnyBus NetTool for DeviceNet Rev HMS Industrial Networks Germany Japan Sweden U.S.A sales-ge@hms-networks.com sales-jp@hms-networks.com sales@hms-networks.com sales-us@hms-networks.com

2

3 Table of Contents Table of Contents Preface Chapter 1 Chapter 2 Chapter 3 About This Manual How To Use This Manual... P-1 Important user information... P-1 Related Documentation... P-1 Revision list... P-1 Conventions used in this manual... P-2 Support... P-2 About the AnyBus NetTool for DeviceNet Features Package Contents Important Note Hardware DeviceNet Adapter Overview DIN-Rail Installation Connections, Cables etc Software System Requirements Installation Tasks Create a New Network Installing an.eds File (Electronic Data Sheet) Adding a Device to a Network Go Online Changing MacID Edit Device Properties Scan List Table Scan List Table Slave I/O Configuration Scan List Table I/O Mapping Scan List Diagnostics Multiple Scanners/Masters in One Network...3-8

4 Preface About This Manual How To Use This Manual This manual provides an overview of the AnyBus NetTool for DeviceNet configuration software. The reader of this document is expected to have basic knowledge in the DeviceNet fieldbus system, and communication systems in general. Important user information The data and illustrations found in this document are not binding. We reserve the right to modify our products in line with our policy of continuous product development. The information in this document is subject to change without notice and should not be considered as a commitment by HMS Industrial Networks AB. HMS Industrial Networks AB assumes no responsibility for any errors that may appear in this document. There are many applications of this product. Those responsible for the use of this device must ensure that all the necessary steps have been taken to verify that the application meets all performance and safety requirements including any applicable laws, regulations, codes, and standards. AnyBus is a registered trademark of HMS Industrial Networks AB. All other trademarks are the property of their respective holders. Related Documentation Document name Author Revision list Revision Date Author Chapter Description - - KrH/HMS All Created (Online help) PeP/HMS All Transferred to Framemaker

5 About This Manual P-2 Conventions used in this manual The following conventions are used throughout this manual: Numbered lists provide sequential steps Bulleted lists provide information, not procedural steps The term module is used when referring to the AnyBus module The term application is used when referring to the hardware that is connected to the AnyBus Application Connector Hexadecimal values are written in the format NNNNh, where NNNN is the hexadecimal value. Support HMS Sweden Tel: +46 (0) Fax: +46 (0) Online: HMS America Tel: Fax: Online: HMS Germany Tel: Fax: Online: HMS Japan Tel: Fax: Online:

6 Chapter 1 About the AnyBus NetTool for DeviceNet The AnyBus NetTool for DeviceNet is a comprehensive DeviceNet Configuration Tool that allows configuration and maintenance of a DeviceNet Network. Setup functions include full Scanner configuration and DeviceNet slave configuration. The AnyBus NetTool-DN software works with Scanners based on the Rockwell scanner toolkit firmware and lets users configure, manage and troubleshoot any DeviceNet network or network component on a DeviceNet network. The AnyBus NetTool for DeviceNet consists of a Windows 32-bit graphical network configuration software and a DIN rail mountable adapter that connects a PC via RS232 to the DeviceNet network. The configuration tool includes all necessary software and a hardware to configure, manage and troubleshoot a DeviceNet network. Features Easy to use Interface Multiple Networks simultaneously Click and configure On-line and Off-line configuration On line help system Package Contents The AnyBus NetTool for DeviceNet package contains the following items: DeviceNet adapter AnyBus NetTool for DeviceNet software CD Cable, RJ45<>Dsub9 PE Cable Power Plug (Pluggable Screw Connector) Important Note AnyBus NetTool for DeviceNet requires Electronic Datasheet (.EDS) files for all devices in the network. Parameter Data Objects are not supported. Slaves that require this functionality will not work.

7 Chapter 2 Hardware DeviceNet Adapter Overview Bottom View Configuration Port (RS232) The configuration port should be connected a free COM port on a PC. Power Connector Apply 24V DC on this connector. Polarity is printed on the pluggable screw terminal (included in the package) Protective Earth (Optional) This connector can be used to connect the module to protective earth. Front View V - CanL Shield CanH V + A1 Module Status A2 TM RS232 Interface NetTOOL Network Status DeviceNet Connector This connector is used for DeviceNet connectivity. Status Indicators These LEDs provides run time status and error indications. Led Indication A1 Activity 1 A2 Activity 2 Module Status Standard DeviceNet Module Status indicaiton Network Status Standard DeviceNet Network Status indication DIN-Rail Installation 2 1 Snap On Snap Off

8 Hardware 2-2 Connections, Cables etc. Configuration Cable Power Plug PE Cable Connect the PC cable (Dsub9<>modular) between the device and a free COM port on the PC. 2. Connect the DeviceNet adapter to the DeviceNet network 3. Apply 24V DC to the power connector of the DeviceNet adapter. The polarity is printed on the supplied pluggable screw connector. 4. Optionally, connect the DeviceNet adapter to protective earth using the supplied PE cable

9 Chapter 3 Software System Requirements Hardware Pentium class CPU 24 MB of RAM or more VGA adapter (256-colour 800 x 600) CD-Rom drive A pointing device (i.e. a mouse) A compatible DeviceNet adapter (included in package) Software 10 MB of free space on the hard drive Windows 98/ME/NT/XP/2000 Internet Explorer 4.01 SP1 or higher Installation There are two different ways of installing the AnyBus NetTool for DeviceNet software; either via the supplied CD ROM, or via the HMS website AnyBus NetTool for DeviceNet software CD ROM Run setup.exe and follow the on screen instructions From website Download the self-extracting.exe-file and run it.

10 Tasks 3-2 Tasks Create a New Network Select File -> New NetWork in the main menu: The following dialog will appear. Give the new Network a name. Installing an.eds File (Electronic Data Sheet) To install an.eds-file (Electronic Data Sheet), perform the following steps: 1. Enter the DeviceNet Hardware View 2. Right-click the mouse 3. Select Add a new device to database Or in the tools menu in the main menu select Install EDS Files When a Device does not have a corresponding.eds-file installed in the database it will appear with a question-mark as shown in the picture below. To enable configuration of such a device one must register a.eds file for it. Select the device and right-click the mouse and select Device->Register EDS-File

11 Tasks 3-3 Adding a Device to a Network Select a device in the hardware view and drag it to the actual network with the mouse and then drop it. When the device is dropped the following dialog will appear. Select the correct MacId for the device and click OK. Note: It is only possible to add a device when the network is in the off line mode.

12 Tasks 3-4 Go Online Select the network that should go online. Right-click the mouse select Net- Work->Configure Driver or the main menu Tools->Configure Driver In the Driver Selection dialog select the hardware you want to use. Configure the attributes for access to the hardware and the DeviceNet network attributes. Click Go Online to go online. Wait a few seconds while the network is being scanned. The following dialog will appear: Any additional (non-configured) devices will be added automatically. Configured but physically nonexistent devices will be indicated with a red cross.

13 Tasks 3-5 Changing MacID Select the device and right-click the mouse. In the pop-up menu select Device->Change NodeAddress The following dialog will appear. Select the new MacId and click OK. Edit Device Properties Double-click the device and the following dialog will pop up: When all the attributes have been configured they can be saved to a file or downloaded to the device by pressing the Download button.

14 Tasks 3-6 Scan List Table 1. Select a scanner in a network 2. Right-click the mouse and select properties or simply double-click the device The above window will appear, this window is built up of the following components: Following the last polled message, the scan interval occurs. The scan interval allocates time for other devices to access the network and slower poll responses to be processed. A scanner will not begin another scan cycle until the scan interval completes. This is the ratio of foreground to background poll. The range of valid values is from 1 to 32,000.Devices can be polled on every I/O scan or they can be polled less frequently Whether a particular device will be polled in the foreground or in the background is determined by its Poll Rate parameter on the Edit I/O Parameters dialog box, which is accessed from the Scan List page. The poll ratio sets the frequency of poll I/O messages to a device in relation to the number of I/O scans. For example, if the poll ratio is set to 10, the scanner will poll the selected devices once every 11 I/O-scans. In the Available list are the devices which are not added to the scan list table but are present in the network. In the Added list are the devices that are added to or owned by the scanner. Those devices are or can be mapped into the memory tables of the scanner. Select a device in the Available list and press this button to configure the Slave device I/O and adding it to the scan list table. Select a device in the Added list to remove a device from the scan list table and I/O mapping. See the Scan list table slave I/O conf.

15 Tasks 3-7 Scan List Table Slave I/O Configuration The window below is shown when a device is added to the scan list table or when the Edit Slave button in the Scan list View is pressed. Note: If a device is mapped into the scanners memory an then edited the mapping will be removed. The strobe I/O message, which is 8 bytes in length, is broadcast by the scanner to all devices on the network. Each of the bits corresponds to one of the node addresses. Each device on the network that supports strobe I/O messages, responds by placing its input data, which can be as many as 8 bytes per device, on the network. The poll I/O message, which can be a maximum of 255 bytes in length, is sent by the scanner to a specific I/O device on the network. What happens when the I/O device receives the message, depends on the content of the message. When the message is a request for input data, the device responds by sending the requested input data to the scanner via another poll I/O message, which can also be up to 255 bytes in length. When the message contains output data, the output data is written to memory within the device. The change-of-state I/O message, which can be a maximum of 255 bytes in length, is sent by an I/O device to the scanner whenever the state of the input data changes or, in some cases, at a user-configurable heart beat rate. The cyclic I/O message, which can be a maximum of 255 bytes in length, is sent by an I/O device to the scanner at a user-configurable rate. Heart Beat rate is the background production interval for the change-of-state connection. The range of valid values is from 3 times the value of the Ack Timeout to 32,000 milliseconds. Ack Time is the amount of time that a producing node will wait for an acknowledgement (ACK) from the consuming node before it re-sends the data. The range of valid values is from 0 to 10,000 milliseconds. Inhibit Time: This is the new data production inhibit time and it is only valid with a change-of-state connection. The range of valid values is from 0 to 32,000 milliseconds. This parameter is useful for slowing down a node with analog data that is rapidly changing, this could be speed feedback from a inverter.even if the node has a new value to send, it will not send it until this amount of time has passed since the data last changed. Identity Verification Keys are criteria that you can use to verify that the devices actually connected to the network are the devices that were expected. The choices available are: Vendor Id Product Type Product Code For each device in the scanlist, check this box if you want it to be included in the scan list table's I/O cycle.

16 Tasks 3-8 Scan List Table I/O Mapping When the Map button is pressed the I/O will be mapped from the first free position after WordOffSet + BitOffSet where all the data can be mapped in one chunk. Note: For the changes to take effect the scan list must be down loaded from the scan list view. Scan List Diagnostics The scanlist diagnostic is available when the network is online. By pressing the Update button it is possible to verify that the scan list configuration matches the network devices. The scanners mode, if it is in programming mode or in run mode is also shown in this view. Multiple Scanners/Masters in One Network If there are multiple active scanners in the network make sure that each slave is mapped into only one scan list. There is no function in this software to ensure this.

17