2 Driver Scope of Supply ................................................................................................................................... 3
2.1Supplied by FieldServer Technologies for this driver ..................................................................................... 3
2.2Additional files Required for the Driver ......................................................................................................... 3
2.3Provided by the Supplier of 3rd Party Equipment .......................................................................................... 3
2.3.1 Required 3rd Party Software ................................................................................................................... 3
2.3.2 Required 3rd Party Configuration ........................................................................................................... 3
Appendix A. Useful Features ................................................................................................................................ 10
Appendix A.1. ControlNet X30 LED indicators ......................................................................................................... 10
Appendix B. Vendor Information ......................................................................................................................... 11
Appendix B.1. Using RSNetWorx Version 1.06 with PLC-5 scanner ......................................................................... 11
Appendix B.2. Using RSLogix 5000 for network configuration ................................................................................ 11
Appendix C. Reference ......................................................................................................................................... 13
Appendix C.1. Setting the FieldServer’s ControlNet MAC ID ................................................................................... 13
Appendix C.2. Using the Network Access Port ........................................................................................................ 13
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
The FieldServer can only emulate one ControlNet Slave station
FieldServer Technologies PART #
Description
X30-ControlNet
Anybus ControlNet Card
Filename
Comments
Config.csv1
Template loaded if no custom configuration ordered, otherwise Custom configuration loaded.
ControlNet
eds file
Required for working with Rockwell’s RSNetworx Tool. Supplied with the FieldServer and also
available via the following link: http://www.fieldserver.com/techsupport/utility/utility.php
1 CONTROLNET X30 DESCRIPTION
The FieldServer ControlNet X30 driver can be used to emulate a single slave station on a ControlNet network.
ControlNet scanners can open a connection of up to 450 Bytes in each direction to the FieldServer. Data transfers
are via Scheduled Communication and therefore the FieldServer has to be scheduled on the ControlNet network
using a Network Configuration Tool such as RSNetWorx or RSLogix. The minimum supported network update time
(NUT) is 5 ms. Connection to the ControlNet network is via two standard BNC connector ports. The connection
may be to either one or both of the ControlNet ports. A connection to both ports provides dual redundant
operation. A Network Access Port (NAP) is also provided for the temporary connection of a Network Configuration
Tool.
Max Nodes Supported
2 DRIVER SCOPE OF SUP PLY
2.1 Sup plied by Fiel dSer v e r Techno lo gies for this driver
2.2 Additional files Required for the Driver
2.3 Provide d by the Supplier of 3
2.3.1 Required 3
RSNetWorx, RSLogix or another Network Scheduling Tool.
2.3.2 Required 3
rd
Party So ftware
rd
Party Co nfigurat ion
rd
Party Eq uipm e nt
Connection to a properly terminated ControlNet network.
1
Always Loaded By FieldServer Technologies
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
The FieldServer is connected to the ControlNet network as shown in the connection drawing below.
3.1 Hardware Connection Tips / Hints
Use the recommended network cable and terminators as specified by the ControlNet network organization and/or
the manufacturer of your network equipment.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
5 CONFIGURING THE FIELDSERVER AS A CONTROL NET SERVER
For a detailed discussion on FieldServer configuration, please refer to the FieldServer Configuration Manual. The
information that follows describes how to expand upon the factory defaults provided in the configuration files
included with the FieldServer (See “.csv” files dupplied with the FieldServer).
This section documents and describes the parameters necessary for configuring the FieldServer to communicate
with a ControlNet Client/Scanner.
The configuration file tells the FieldServer about its interfaces and the routing of data required. In order to enable
the FieldServer for ControlNet communications, the driver independent FieldServer buffers need to be declared in
the “Data Arrays” section, the FieldServer virtual node(s) needs to be declared in the “Server Side Nodes” section,
and the data to be provided to the clients needs to be mapped in the “Server Side Map Descriptors” section.
Details on how to do this can be found below.
Note that in the tables, * indicates an optional parameter, with the bold legal value being the default.
5.1 Contro lNet Settings
Note:
The ControlNet MAC ID can also be set via the two rotary switches on the side of the FieldServer. These switches
should be set to zero or to the same value as System_Station_Address in the configuration file. Alternatively the
System_Station_Address parameter should be eliminated from the configuration file. Failing to do so, will cause a
warning LED to flash although the MAC ID from the configuration file will still be used.
Example
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Appendix B.1. Using RSNetWorx Version 1.06 with PLC-5 scanner
The Anybus ControlNet module is not supported for versions earlier than 1.06.
Ensure all nodes are physically connected and start RSNetworx. Go online (check the Go online box) - all connected nodes should appear on the screen. Right click on the PLC5 node and choose ControlNet configuration. The program now launches the Map Editing
Tool used to set up data mapping in the PLC-5 processor.
Right click on the line that contains the Anybus ControlNet module (in the current version of RSNetworx
displayed as Any-BusDT) and choose Insert device connection.
When the line changes to blue, the connection size in, connection size out and to which address in the PLC the
data shall be mapped should be entered. The data is mapped to the Integer area (N-area). For example, 50
bytes in each direction can be mapped so now 25 words in and 25 words out can be chosen.
Save the configuration, switch the PLC key to run and the data is transferred to/from the PLC data table at the
specified address.
Appendix B.2. Using RSLogix 5000 for network configuration
RSLogix is a programming and configuration tool from Rockwell automation. The information included in this
section is based on an entry in the Rockwell Automation Support Library and can be accessed at:
RSLogix 5000 Version 2.25 and higher versions have a generic profile called CONTROLNET-MODULE which is
applicable to devices that connect directly to ControlNet, such as the 1203-CN1 communications card with a
Rockwell drive or a Schneider Momentum I/O device. The Anybus ControlNet card also uses this profile. All
Anybus ControlNet-enabled I/O will use the same assembly instance numbers, but the data size will change
depending on the application and must be relayed to the end user. The ControlNet module does not use
configuration data so the length should be left at zero, though a non-zero number nust be entered for the
assembly instance. The following list provides information on the settings for the CONTROLNET-MODULE profile
with AnyBus-S enabled devices.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
1. The ControlNet module uses a ControlNet 32-bit run/idle header, so the actual data from the module will
always start with word 2 (the third word) of the data. The first 2 words, at 16 bits each, are the ControlNet
run/idle header. To mask off the run/idle header for clarity, create a user defined type with 2 members HEADER, type DINT; and DATA, type INT with ‘input assembly size - 2’. Copy the data from the actual input tag
to a tag of this structure, and then reference the structure's DATA member using the element numbers in your
documentation.
2. There will always be a configuration tag of type AB:ControlNet_MODULE:C:0 created for this module, which
has one member called Data, of type SINT[400]. This SINT[400] tag is created regardless of the configuration
size, which can range from 0 to 400 bytes (SINTs). Since a data size of zero is specified, no data will be sent to
the module.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Appendix C.1. Setting the FieldServer’s ControlNet MAC ID
The MAC ID can be set in the FieldServer’s CSV file using the System_Station_Address, (refer to Section 5.1), or it
can be set with the two rotary switches as indicated on the connection diagram. The left switch selects the left
decimal digit and the right switch the right decimal digit of the MAC ID.
Note that the software setting with the System_Station_Address overrides the hardware setting with the rotary
switches. Set the rotary switches to zero or to the same value as in the System_Station_Address to prevent the
warning LED from flashing. A mismatch will still result in the software setting being used.
Appendix C.2. Using the Network Access Port
The Network Access Port (NAP) should only be used temporarily to connect a network configuration tool. It must
not be used to connect to the main ControlNet network.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com