FieldServer FS-RA-CLX-BAS User manual

Applicability and Effectivity
FieldServer Technologies
A Sierra Monitor Corporation Company
1991 Tarob Court, Milpitas, California 95035 US
Phone: [phone]
Toll Free: [phone]
Fax: [phone]
Email: [e-mail]
Web Site: www.fieldserver.com
SlotServer Instruction Manual
PPLIC BILITY & EFFECTIVITY
This manual provides instructions for the following FieldServer products:
Description
FS-RA-C X-BAS
FS-RA-C X-FIR
FS-RA-C X-PRO
The instructions are effective for the above as of January 2006
Instruction Manual Part Number: T17011
Rev. A3.

FS-R -CLX_SlotServer_Instruction_Manual_(T17011) Table of Contents
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
T BLE OF CONTENTS
1. INTRODUCTION............................................................................................................. 4
1.1. About this product...................................................................................................... 4
2. PRE-ST RTUP CHECKLIST.......................................................................................... 5
2.1. Accessories supplied with the SlotServer................................................................... 5
2.2. Third party components (not supplied by FieldServer Technologies) ......................... 5
2.3. Required configuration for the SlotServer................................................................... 5
3. STEPS FOR IMPLEMENT TION OF SLOTSERVER PROJECT ............................... 6
3.1. Read the SlotServer Instruction Manual..................................................................... 6
3.2. Install the SlotServer in a Control ogix Rack. ............................................................ 6
3.3. Write the SlotServer configuration.............................................................................. 6
3.4. Install the FieldServer Utilities.................................................................................... 6
3.5. oad the SlotServer Configuration into the SlotServer ............................................... 6
3.6. Program the Control ogix CPU to communicate with the SlotServer. ........................ 6
3.7. Commission the third party network. .......................................................................... 6
4. SLOTSERVER INST LL TION ..................................................................................... 7
4.1. SlotServer Ports and Displays.................................................................................... 7
4.2. Inside Cover Door abel ............................................................................................ 9
4.3. Technical Specifications............................................................................................. 9
5. SLOTSERVER TOPOLOGY..........................................................................................10
6. CONFIGURING THE CPU INTERF CE TO THE SLOTSERVER .................................11
6.1. CPU interface Description.........................................................................................11
6.2. Configuring the SlotServer as a ogix I/O Server......................................................11
6.3. Data Arrays/Descriptors............................................................................................11
6.4. Server Side Connection Descriptors .........................................................................12
6.5. Server Side Node Descriptors...................................................................................12
6.6. Server Side Map Descriptors ....................................................................................13
6.6.1. SlotServer Specific Map Descriptor Parameters ....................................................13
6.6.2. Driver Specific Map Descriptor Parameters ...........................................................13
6.6.3. Map Descriptors Example......................................................................................14
7. PROGR MMING THE CONTROLLOGIX CPU FOR SM LL SLOTSERVER
INTERF CE .............................................................................................................................15
7.1. Step 1: Establish an RS ogix project ........................................................................15
7.2. Step 2: Add and configure the SlotServer as an IO Module ......................................16
7.3. Step 3: Write adder Program to get Input Data from Data Arrays............................17
7.4. Step 4: Write adder Program to Send Output Data to Data Arrays..........................20
7.5. Step 5: Download the RS ogix Program and Run.....................................................20
7.6. Step 6: Set up the third party connection ..................................................................20
8. PROGR MMING THE CONTROLLOGIX CPU FOR L RGER SLOTSERVER
INTERF CES...........................................................................................................................21
8.1. Multiple Input Data Arrays.........................................................................................21
8.2. Accessing Multiple Output Data Arrays .....................................................................21
PPENDIX . DV NCED TOPICS.....................................................................................23
Appendix A.1. Description of Data Transfer Process...........................................................23
Appendix A.2. The IO image header ...................................................................................25
Appendix A.3. How to obtain Node Status from the SlotServer ...........................................25

FS-R -CLX_SlotServer_Instruction_Manual_(T17011) Table of Contents
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
Appendix A.4. Dealing with Control ogix RPI Settings........................................................26
Appendix A.5. Installing SlotServer on a Remote Rack using CNB Cards...........................27
Appendix A.5.1. Hard are and Soft are requirements....................................................27
Appendix A.5.2. Setup .....................................................................................................27
Appendix A.5.3. RSLogix configuration............................................................................27
Appendix A.5.4. RSNetWorx configuration ......................................................................28
Appendix A.5.5. Testing...................................................................................................29
Appendix A.5.6. Connection limitations -Controlling the SlotServer using ControlNet ......30
Appendix A.6. Rules for Naming ogix driver Data Arrays ..................................................31
PPENDIX B. TROUBLESHOOTING TIPS ..........................................................................33
Appendix B.1. Things to check when communications fail. .................................................33

FS-R -CLX_SlotServer_Instruction_Manual_(T17011) Page 4 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
1. Introduction
1.1. bout this product
The SlotServer Instruction Manual provides the information necessary to configure the
SlotServer, allowing an Allen Bradley Control ogix platform to pass data between a
Control ogix CPU and other third party communications protocols supported by the
SlotServer. The SlotServer uses implicit communications between the CPU and the
SlotServer and is consequently treated as an I/O Server in RSLogix.
The SlotServer Instruction Manual covers information for installing the SlotServer, and
configuring the module to transfer data with the CPU on the Control ogix Rack. Depending
on the SlotServer Module ordered, supplementary driver manuals are provided for
information on how to configure the third party protocols residing in the SlotServer.

FS-R -CLX_SlotServer_Instruction_Manual_(T17011) Page 5 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
2. Pre-Startup checklist
2.1. ccessories supplied with the SlotServer
Please verify that the following components were supplied with the SlotServer module:
FieldServer Technologies
P RT # Description
2-way combi-comb connector for onWorks port
Software CD
CAT-5 Direct Ethernet Cable
Documentation Binder
2.2. Third party components (not supplied by FieldServer Technologies)
The following components will need to be procured as a minimum for achieving Control ogix
integration. Ensure that these are available before commencing with commissioning
Part # Description
AB1756-Ax Control ogix Rack
AB1756- 55/ 61 Control ogix CPU
AB1756-PA7x Control ogix PSU
9324-R D300ENE RS OGIX 5000
2.3. Required configuration for the SlotServer
To achieve data transfer between CPU tags and the SlotServer third party protocols, it will
be necessary to write and load a configuration into the SlotServer that tells the SlotServer
how to map the Control ogix Tags to the required protocol addresses. This configuration is
written in a Comma Separated Variable (csv) file, and any text editor or spreadsheet
program that supports csv format can be used for this purpose. FieldServer Technologies
provides an example configuration file so that the configuration does not need to be written
from scratch. Configuration parameters needed to exchange data between the CPU and
the SlotServer data images (Data Arrays) are presented in Section 6. The appropriate
driver manual supplement will describe how to map the data in and out of the Data Arrays
for the relevant protocol.
The FieldServer configuration manual details basic and advanced techniques for the
configuration of the SlotServer Manual, and it is strongly advised that this manual is read
before attempting to write the SlotServer Configuration.
Note: FieldServer Technologies provides SlotServer configuration services if the user does
not wish to perform the configuration themselves.

FS-R -CLX_SlotServer_Instruction_Manual_(T17011) Page 6 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
3. Steps for implementation of a SlotServer Project
3.1. Read the SlotServer Instruction Manual
This provides guidelines for getting started with the SlotServer, and is very useful for first
time implementation of a SlotServer application.
3.2. Install the SlotServer in a ControlLogix Rack.
Refer to Section 4 for information on installation.
3.3. Write the SlotServer configuration.
• Refer to the FieldServer configuration manual for instruction on writing a FieldServer
configuration.
• Refer to Section 6 for assistance on managing the ogix driver Parameters
• Refer to the desired protocol driver supplement for assistance on managing the protocol
parameters.
3.4. Install the FieldServer Utilities
Insert the supplied Utilities CD into the CD drive of the PC to be used for configuration and
follow the install instructions.
3.5. Load the SlotServer Configuration into the SlotServer
Refer to the FieldServer Utilities manual for information on the FieldServer Remote User
Interface.
3.6. Program the ControlLogix CPU to communicate with the SlotServer.
The sections that follow highlight a few examples on how this is done.
3.7. Commission the third party network.
Refer to standard commissioning guidelines for the protocol in question.

FS-R -CLX_SlotServer_Instruction_Manual_(T17011) Page 7 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
4. SlotServer Installation
The SlotServer plugs directly into the AB1756 Control ogix rack. Take note of the slot number
used for the SlotServer as this will be needed when configuring the I/O in the RS ogix software.
4.1. SlotServer Ports and Displays
Note that there are several hardware ports available on the SlotServer card, but that this
SlotServer model only makes use of a select few. The ports and displays of interest are as
shown in the diagram below:
Scrolling Display
This will Display an OK status when the SlotServer has powered up successfully.
Card Status Indicators:
The Comm and OK lights will indicate green when the SlotServer has powered up
successfully. The Sys indicator will indicate green if the external nodes are all
communicating properly; and red otherwise.
Service Pin
To be used for commissioning the SlotServer into a onWorks network
Scrolling display shows card messages
Card Status Indicators show general card
status
Service Pin for onWorks Commissioning
Communications Status ED’s show status of
communications and card software.
TP/FT10 onWorks Connection
Ethernet Port. Used for configuration and
Ethernet Protocols.
RS-485 Port. Specify as R1 in the
configuration.

FS-R -CLX_SlotServer_Instruction_Manual_(T17011) Page 8 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
Communications Status LED’s
Run
Node Off
Sys Err
onSvc
Conf Err
Com Err
Rx Tx
10/100
Act
LED Description
Run
When the SlotServer is powered up, this light will start flashing after approximately 2
minutes. If this light does not flash, it is an indication that the firmware is not running,
and that the SlotServer will not be operating.
LonSvc This light will flash when the card’s Neuron chip is unconfigured, and will extinguish
when the SlotServer has been commissioned into a Network.
NodeOff This light indicates that a device bound to the SlotServer on the onWorks network is
not communicating. Use the onWorks Network Manager to troubleshoot the problem.
Conf Err
This light indicates an error in the configuration of the card. Since this model is shipped
pre-configured, this light should never come on unless the card configuration is
tampered with
Sys Err
This light indicates that an unexpected operation state occurred. The light can be reset
by cycling power to the card. If the error re-occurs persistently, then contact
FieldServer Technical support for assistance with troubleshooting after setting up the
trade port as shown in Appendix A.
Com Err This light indicates that a communication error occurred. Use the onWorks Network
Manager to troubleshoot the problem, or refer to Appendix B.1.
RS-485
(R1)
These lights are related to the RS-485 serial ports provided on the FieldServer. The
Rx (Receive) light will flash red if the FieldServer is receiving data. The Tx (Transmit)
light will flash red if the FieldServer is sending data. (Note that due to the nature of 2-
wire RS-485 the Rx light will flash every time the Tx light flashes too). The frequency of
the flashing is directly related to the frequency of data transfer.
Ethernet
Lights
(N1,N2)
These lights are related to the two Ethernet network ports provided on the FieldServer.
The 10/100 light will be green if the physical connection to the network hub is running
at 100 MBits/s. If the light is off, the connection is running at 10 MBits/s. The ct
(Activity) light will indicate activity on the network. The frequency of flashing is directly
related to the network activity. It does not necessarily mean data is being received by
the FieldServer. Note that Ethernet Port N2 supports 10 or 100 MBits/s, whereas N1
only supports 10 MBits/s

FS-R -CLX_SlotServer_Instruction_Manual_(T17011) Page 9 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
TP/FT10 LonWorks connection
This two wire connection is polarity insensitive and can be multi-dropped into a onWorks
Network.
Ethernet Port
The Ethernet port can be used for configuration and troubleshooting, as well as for Protocols
that require an Ethernet connection. Use standard Ethernet cables for this connection.
RS-485 Port
This is a standard 2-wire RS-485 port. Specify as R1 in the configuration.
4.2. Inside Cover Door Label
A label has been provided on the inside of the cover door for the User to document
important or useful configuration parameters used. In particular, special provision has been
made to document the Ethernet port IP parameters, as well as the onWorks DSN
(Domain/Subnet/Node) allocated by the Network Manager. These fields are there to be
utilized at the User’s discretion.
4.3. Technical Specifications
Slot width 1
BackPlane Current oad 0.6A
Operating Temperature 0-60 Deg C (32-140 Deg F)
Storage Temperature -40 – 85 Deg C (-40 – 185 Deg F)
Humidity 5-95% (Non-Condensing)
Allen Bradley Platform: Control ogix 1756 Rack
onWorks Connection type: TP/FT-10
Ethernet port 10/100 MB/sec.
RS-485 port 2-wire, half duplex.
Approvals
1
U 60950-1:2003
CAN/CSA-C22.2 No.60950-1-03
1
Refer to Error! Reference source not found. to view Certificates.

FS-R -CLX_SlotServer_Instruction_Manual_(T17011) Page 10 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
5. SlotServer Topology
The SlotServer connection varies based on the protocol being used. Refer to the appropriate
driver supplement for more details. The diagram in section 4.1 shows the ports available on the
SlotServer for each of the protocols.

FS-R -CLX_SlotServer_Instruction_Manual_(T17011) Page 11 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
6. Configuring the CPU interface to the SlotServer
6.1. CPU interface Description
The SlotServer Data Images (Data Arrays) share data with the Control ogix CPU tags using
the backplane for communication and the FieldServer ogix driver. To map the ogix Driver,
the Driver needs to be configured in the SlotServer Configuration. The information that
follows details the configuration parameters that can be used for this driver. The driver can
only act as an I/O Server (Adapter) to a Control- ogix CPU.
Max Nodes Supported
SlotServer Mode Nodes Comments
Server 1 Only one IO image connection supported
6.2. Configuring the SlotServer as a Logix I/O Server
For a detailed discussion on SlotServer 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 SlotServer (See “.csv”
sample files provided with the SlotServer).
The configuration file tells the SlotServer about its interfaces, and the routing of data
required. In order to enable the SlotServer for ogix communications, the driver
independent SlotServer buffers need to be declared in the “Data Arrays” section, the
SlotServer 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.
6.3. Data rrays/Descriptors
The configuration file tells the SlotServer about its interfaces, and the routing of data
required. In order to enable the SlotServer for ogix communications, the driver
independent SlotServer buffers need to be declared in the “Data Arrays” section.
Section Title
Data_Arrays
Column Title Function Legal Values
Data_Array_Name Provide name for Data Array Up to 15 alphanumeric
characters
Data_Array_Format
Provide data format. Each Data Array
can only take on one format.
Float, Bit, UInt16, SInt16,
Packed_Bit, Byte,
Packed_Byte,
Swapped_Byte
Data_Array_ ength
Number of Data Objects. Must be
larger than the data storage area
required by the Map Descriptors for
the data being placed in this array.
For IO_Data_Type:
REA 1-120
INT 1-244
SINT 1-492
DINT 1-120

FS-R -CLX_SlotServer_Instruction_Manual_(T17011) Page 12 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
Example
// Data Arrays
Data_Arrays
Data_Array_Name, Data_Array_Format, Data_Array_ ength
In_1, Float, 76
In_2, Float, 76
Out_1, Float, 76
Out_2, Float, 76
6.4. Server Side Connection Descriptors
Section Title
Connections
Column Title Function Legal Values
Adapter Adapter Name ControlNet
Example
// Server Side Connections
Connections
Adapter
ControlNet
6.5. Server Side Node Descriptors
Section Title
Nodes
Column Title Function Legal Values
Node_Name Provide name for node Up to 32 alphanumeric
characters
Node_ID Virtual Node ID 0-15
Protocol Specify protocol used ogix_SS
Timeout IO image connection timeout 0.5s
Retry_Interval Time to retry node online status 0.1s
Recovery_Interval Interval to recover node to
online status 0.5s
Example
// Server Side Nodes
Nodes
Node_Name, Node_ID, Protocol, Timeout, Retry_Interval, Recovery_Interval
SlotServer_CPU, 11, ogix_SS, 0.5s, 0.1s, 0.5s

FS-R -CLX_SlotServer_Instruction_Manual_(T17011) Page 13 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
6.6. Server Side Map Descriptors
6.6.1. SlotServer Specific Map Descriptor Parameters
Column Title Function Legal Values
Map_Descriptor_Name Name of this Map
Descriptor
Up to 32 alphanumeric
characters
Scan_Interval Rate at which IO image
data is updated
Use twice the rate used in
RS ogix e.g. 0.2s
Function Function of Server Map
Descriptor
WRBC - to write into Input
Image Data buffer
RDBC - to read from Output
Image Data buffer
6.6.2. Driver Specific Map Descriptor Parameters
Column Title Function Legal Values
Node_Name Name of Node to fetch data
from
One of the node names
specified in “Client Node
Descriptor” above
IO_Data_Type Data type of IO image
Use same as used in
RS ogix to add the module
INT (16-bit integer)
SINT (8-bit signed)
DINT (32-bit double)
REA (32-bit float)
DA_Name_Start
2
Name of Data Array to
include in IO image data
One of the Data Array
names from “Data Array”
section above. Data Arrays
must be named as follows:
DaName_x where x is a
value e.g. DaName_1
DA_Count Number of Data Arrays to
include in IO image data 1-200
Protocol_Type_ID
Custom Value transferred in
IO image to indicate
protocol of IO image data
0 - value permitted by
IO_Data_Type
3
e.g. 0 - 65535 for INT
2
Refer to Appendix A.6 for information specific to naming ogics driver Data Arrays.
3
T he update rate decreases as the number of blocks go up. For 25 blocks we have an update rate of
25*RPI = 25*0.1 = 2.5 seconds.

FS-R -CLX_SlotServer_Instruction_Manual_(T17011) Page 14 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [email protected]
6.6.3. Map Descriptors Example
Only two Map Descriptors are allowed, one to transfer data to the ogix CPU and one to accept data from the ogix CPU. // Server Side Map Descriptors Map_Descriptors Map_Descriptor_Name,
Scan_Interval,
Function,
Node_Name, IO_Data_Type, DA_Name_Start
4
,
DA_Count,
Protocol_Type_ID
Input_BP_Image, 0.2s, WRBC, SlotServer_CPU,
REA , In_1, 2, 0
Output_BP_Image, 0.2s, RDBC, SlotServer_CPU,
REA , Out_1, 2, 0
The following Data Arrays section must exist for the above Map Descriptors: // Data Arrays Data_Arrays Data_Array_Name, Data_Format, Data_Array_ ength In_1, Float, 76 In_2, Float, 76 Out_1, Float, 76 Out_2, Float, 76 4
Refer to Appendix A.6 for information specific to naming ogics driver Data Arrays.
The data format should be chosen to allow no loss of resolution with the chosen IO_Data_Type of the Map Descriptor, e.g. don’t use integer here if you intend transferring float data.
See the Data Arrays section for the maximum Data Array lengths allowed per IO_Data_Type chosen on the Map Descriptor.

FS-R -CLX_SlotServer_Instruction_Manual_(T17011) Page 15 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
7. Programming the ControlLogix CPU for a small SlotServer Interface
The discussion that follows describes the basic steps to set up and test the system for
transferring data between CPU tags and the SlotServer using the I/O image method. The quick
Start example uses onWorks as the example 3
rd
Party Protocol. A hardcoded template is filled
with on variables is created. Each item uses a different amount of bytes and the total adds up
to 104 on Network Variables. This limit of 104 does not apply when using customized data
items – the actual limit is 496 bytes. Refer to the Advanced Project to access more than 104
Network Variables.
7.1. Step 1: Establish an RSLogix project
5
• Use File/New to create a new project or File/Open to open an existing project.
5
Your Controller may be of a different type to the one shown in the example.
Ensure that this is the slot
number in the rack where
your Controller resides.

FS-R -CLX_SlotServer_Instruction_Manual_(T17011) Page 16 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
7.2. Step 2: dd and configure the SlotServer as an IO Module
• Right-click on I/O Configuration and select “New Module”.
• Choose the 1756-MODU E
Choose the
1756-MODU E
Be sure to choose the correct
Slot number in the rack where
your Slot
Server
reside
Click Next and choose a RPI of 100 ms.
This is the rate at which the I/O image data
will be transferred

FS-R -CLX_SlotServer_Instruction_Manual_(T17011) Page 17 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
7.3. Step 3: Write Ladder Program to get Input Data from Data rrays
• Add a CPS (Synchronous Copy File) adder element to synchronize the incoming Data
from the Input Data Arrays. Use the Input Image Data as Source.
Click Finish to complete the Module Properties setup
You can create the
Destination Tag by right
clicking on Destination and
choosing New Tag.

FS-R -CLX_SlotServer_Instruction_Manual_(T17011) Page 18 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
• Add an EQU (Compare if equal) ladder element to check when the first Data Array has been
received. The block number is at offset 2 of the input image.
• Finally, add another CPS ladder element to copy the onWorks Data from the InData_Copy
Tag to a new Controller Tag, called on_In_01. Also create the Tag by right clicking on
Destination and choosing New Tag. The New Tag must be of type REA and a dimension of
76.
Create a Controller Tag of
Type REA , dimension of 80
for the Destination

FS-R -CLX_SlotServer_Instruction_Manual_(T17011) Page 19 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
Below is the final ladder program to access data from onWorks Function Block In[0]
Very Important Note!
It is very important to first make a synchronous copy of the input image data before using it. If
this is not done, the input data cannot be guaranteed to be from a specific SlotServer Data
Array.

FS-R -CLX_SlotServer_Instruction_Manual_(T17011) Page 20 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
7.4. Step 4: Write Ladder Program to Send Output Data to Data rrays
This step demonstrates how to write data to the Data Array Out[0]
• Create a Controller Tag called on_Out_01 of type REA [80].
• Add a new rung to the adder program and add a MOV element to move a block number
value of 1 into on_Out_01[2].
• Finally add a CPS (Synchronous Copy File) element to copy the full on_Out_01 tag into
the Output Image Tag.
The onWorks Data are present from on_Out_01[4] to on_Out_01[79]
You can create a User Defined Data Type to replace the type of on_Out_01 mapping the
points to onWorks point names.
Very Important Note!
It is very important to only update all the data of the Output Image Tag once using a
Synchronous File Copy element. It is not permissible to update the block number into the
Output Image Tag and then the data as this will cause an asynchronous transfer of data.
7.5. Step 5: Download the RSLogix Program and Run
Use the Who Active or Communications Path directly to Download and Run the Program on
the Controller / CPU.
7.6. Step 6: Set up the third party connection
In this example, this step would involve binding the onWorks variables using a onWorks
Network Manager..