FieldServer SlotServer PS56-BAS Series Instruction sheet

A Sierra Monitor Company
APPLICABILITY & EFFECTIVITY
This manual provides instructions for the following FieldServer products:
Description
PS56-BAS-xxx
PS56-FIR-xxx
PS56-PRO-407
The instructions are effective for the above as of September 2012
SlotServer Configuration Manual
Kernel Version:
1.04
Document Revision:
5

SlotServer Configuration Manual Table of Contents
ProSoft Technology, Inc. is the exclusive provider of FieldServer SlotServers.
For Technical Support call +1 661.716.5100
TABLE OF CONTENTS
1Introduction ................................................................................................................................................... 4
1.1 About this Product.........................................................................................................................................4
1.2 Required Configuration for the SlotServer ....................................................................................................4
2Steps for implementation of a SlotServer Project........................................................................................... 5
2.1 Install the FieldServer Utilities .......................................................................................................................5
2.2 Load the SlotServer Configuration into the SlotServer..................................................................................5
2.3 Program the ControlLogix CPU to communicate with the SlotServer. ..........................................................5
2.4 Commission the third party network.............................................................................................................5
3Configuring the CPU interface to the SlotServer............................................................................................. 6
3.1 CPU interface Description..............................................................................................................................6
3.2 Data Array Parameters ..................................................................................................................................6
3.3 Configuring the SlotServer as a Logix I/O Server ...........................................................................................7
3.4 Client Side Connection Parameters ...............................................................................................................7
3.5 Client Side Node Parameters .........................................................................................................................7
3.6 Client Side Map Descriptor Parameters.........................................................................................................8
3.6.1 SlotServer Specific Map Descriptor Parameters.....................................................................................8
3.6.2 Driver Specific Map Descriptor Parameters ...........................................................................................8
3.6.3 Map Descriptor Example........................................................................................................................9
4Programming the ControlLogix CPU for a small SlotServer Interface............................................................ 10
4.1 Step 1: Establish an RSLogix project ............................................................................................................10
4.2 Step 2: Add and configure the SlotServer as an IO Module.........................................................................10
4.3 Step 3: Write Ladder Program to get Input Data from Data Arrays ............................................................12
4.4 Step 4: Write Ladder Program to Send Output Data to Data Arrays ...........................................................15
4.5 Step 5: Download the RSLogix Program and Run ........................................................................................15
4.6 Step 6: Set up the third party connection....................................................................................................15
5Programming the ControlLogix CPU for larger SlotServer Interfaces ............................................................ 16
5.1 Multiple Input Data Arrays ..........................................................................................................................16
5.2 Accessing Multiple Output Data Arrays.......................................................................................................16
5.3 Loading Data_Array Values from the FieldServer’s Non-Volatile Memory .................................................18
6Timing Parameters ....................................................................................................................................... 19
Appendix A. Useful Features................................................................................................................................ 21
Appendix A.1. How to obtain Node Status from the SlotServer..............................................................................21
Appendix B. Troubleshooting............................................................................................................................... 22
Appendix A.1. SlotServer block number [ 0 ] out of range! .....................................................................................22
Appendix A.2. Driver Error screen returns “Illegal Protocol” Error. ........................................................................22
Appendix A.3. SlotServer output image data transfer stops after a few hours when keeping RSWho open to
browse the rack. ......................................................................................................................................................22
Appendix C. Vendor Information ......................................................................................................................... 23
Appendix A.4. SlotServer in Remote Allen Bradley Racks .......................................................................................23
Appendix A.5. Installing SlotServer on a Remote Rack using CNB Cards.................................................................23
Appendix A.5.1. RSLogix configuration.............................................................................................................23
Appendix A.5.2. RSNetWorx configuration ......................................................................................................24
Appendix A.5.3. Testing....................................................................................................................................25
Appendix A.5.4. Connection limitations -Controlling the SlotServer using ControlNet ....................................26
Appendix A.6. Dealing with ControlLogix RPI Settings ............................................................................................27
Appendix A.7. Rules for Naming Logix driver Data Arrays.......................................................................................27

SlotServer Configuration Manual Table of Contents
ProSoft Technology, Inc. is the exclusive provider of FieldServer SlotServers.
For Technical Support call +1 661.716.5100
Appendix D. Reference ........................................................................................................................................ 30
Appendix A.8. Description of Data Transfer Process ...............................................................................................30
Appendix A.9. The IO image header ........................................................................................................................32
Appendix A.10. Available Data Types for Data Arrays .............................................................................................32
Appendix A.11. Permissible Values for Configuration File Variables.......................................................................33
Appendix A.11.1. Common Information ...........................................................................................................33
Appendix A.11.2. Data Arrays ..........................................................................................................................33
Appendix A.11.3. Data Array Function .............................................................................................................34
Appendix A.11.4. Connections/ Adapters.........................................................................................................35
Appendix A.11.5. Nodes ...................................................................................................................................35
Appendix A.11.6. Map Descriptors ...................................................................................................................37

SlotServer Configuration Manual Page 4 of 37
ProSoft Technology, Inc. is the exclusive provider of FieldServer SlotServers.
For Technical Support call +1 661.716.5100
INTRODUCTION
1
1.1 About this Product
The SlotServer Configuration Manual provides the information necessary to configure the SlotServer, allowing an
Allen Bradley ControlLogix platform to pass data between a ControlLogix 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.
When configured in remote rack applications, the SlotServer does not support the use of EN2T-A cards, but is
compatible with EN2T-B cards.
The SlotServer Start-up guide covers information for installing the SlotServer; the Configuration Manual provides
information on configuring the module to transfer data with the CPU on the ControlLogix 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.
1.2 Required Configuration for the SlotServer
To achieve data transfer between CPU tags and the SlotServer third party protocols, it is necessary to write and
load a configuration into the SlotServer that tells the SlotServer how to map the ControlLogix 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 3. The appropriate driver manual supplement will describe how to map the data in and out of
the Data Arrays for the relevant protocol.
The SlotServer configuration manual details basic and advanced techniques for the configuration of the SlotServer,
and it is strongly advised that this manual is read before attempting to write the SlotServer Configuration.
FieldServer Technologies provides SlotServer configuration services if the user does not wish to perform the
configuration themselves.

SlotServer Configuration Manual Page 5 of 37
ProSoft Technology, Inc. is the exclusive provider of FieldServer SlotServers.
For Technical Support call +1 661.716.5100
STEPS FOR IMPLEMENTATION OF A SLOTSERVER PROJECT
2
2.1 Install the FieldServer Utilities
Refer to the Start-up guide for further information..
2.2 Load the SlotServer Configuration into the SlotServer
Refer to the SlotServer Start-up Guide for information on the FieldServer Graphic User Interface (FS-GUI).
2.3 Program the ControlLogix CPU to communicate with the SlotServer.
The sections that follow highlight a few examples on how this is done.
2.4 Commission the third party network.
Refer to standard commissioning guidelines for the protocol in question.

SlotServer Configuration Manual Page 6 of 37
ProSoft Technology, Inc. is the exclusive provider of FieldServer SlotServers.
For Technical Support call +1 661.716.5100
CONFIGURING THE CPU INTERFACE TO THE SLOTSERVER
3
3.1 CPU interface Description
The SlotServer Data Images (Data Arrays) share data between the ControlLogix CPU tags (using the backplane for
communication) and the FieldServer Logix driver. To map the Logix 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 ControlLogix CPU. The SlotServer presently
works with ENBT Ethernet cards, but not EN2F. When configured in remote rack applications, the SlotServer does
not support the use of EN2T-A cards, but is compatible with EN2T-B cards.
Max Nodes Supported
SlotServer Mode
Nodes
Comments
Server
1
Only one IO image connection supported
// Common Information
FieldServer
Title
, System_Station_Address
SlotServer Server v1.03d
, 1
3.2 Data Array Parameters
The configuration file tells the SlotServer about its interfaces, and the routing of data required. In order to enable
the SlotServer for Logix 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_Length
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:
Real 1-120
Uint 1-244
Sint 1-492
Dint - 1-120
Example
// Data Arrays
Data_Arrays
Data_Array_Name
,Data_Array_Format
,Data_Array_Length
TestOut_1
, UInt16
, 244
TestOut_2
, UInt16
, 244
TestIn_1
, UInt16
,244
TestIn_2
, UInt16
, 244

SlotServer Configuration Manual Page 7 of 37
ProSoft Technology, Inc. is the exclusive provider of FieldServer SlotServers.
For Technical Support call +1 661.716.5100
3.3 Configuring the SlotServer as a Logix I/O Server
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 Logix 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.
3.4 Client Side Connection Parameters
Section Title
Connections
Column Title
Function
Legal Values
Adapter
Adapter Name
ControlNet
Example
// Server Side Connections
Connections
Adapter
ControlNet
3.5 Client Side Node Parameters
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
Logix_SS
Example
// Server Side Nodes
Nodes
Node_Name
, Node_ID
, Protocol
SlotServer_CPU
, 1
, Logix_SS

SlotServer Configuration Manual Page 8 of 37
ProSoft Technology, Inc. is the exclusive provider of FieldServer SlotServers.
For Technical Support call +1 661.716.5100
3.6 Client Side Map Descriptor Parameters
3.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
Function
Function of Server Map Descriptor
WRBC-to write into Input Image Data buffer
RDBC-to read from Output Image Data buffer
3.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 RSLogix to add the module
INT (16-bit integer)
SINT (8-bit signed)
DINT (32-bit double)
REAL (32-bit float)
DA_Name_Start1
Name of Data Array to include in
IO image data
One of the Data Array names from Section 3.2. Data
Arrays must be named as follows:
DaName_x where x is a positive integer value e.g.
DaName_1
DA_Count
Number of Data Arrays to
include in IO image data
1-2002
Scan_Interval
Rate at which IO image data is
updated.
Use twice the rate of RPI,
e.g.: RPI = 0.4s, Scan_Interval=0.2s
1
Refer to Appendix C.4 for information specific to naming Logix driver Data Arrays.
2
The update rate decreases as the number of blocks go up. For 25 blocks the update rate is 25*RPI = 25*0.1 = 2.5 seconds.

SlotServer Configuration Manual Page 9 of 37
ProSoft Technology, Inc. is the exclusive provider of FieldServer SlotServers.
For Technical Support call +1 661.716.5100
3.6.3 Map Descriptor Example
Only two Map Descriptors are permitted, one to transfer data to the Logix CPU and one to accept data from the Logix CPU.
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name
, Scan_Interval
, Function
, Node_Name
, IO_Data_Type
, DA_Name_Start3
, DA_Count
Input_BP_Image
, 0s
, Wrbc
, SlotServer_CPU
, Int
, TestOut_1
, 2
Output_BP_Image
, 0s
, Rdbc
, SlotServer_CPU
, Int
, TestIn_1
, 2
3
Refer to Appendix C.4 for information specific to naming Logix driver Data Arrays.

SlotServer Configuration Manual Page 10 of 37
ProSoft Technology, Inc. is the exclusive provider of FieldServer SlotServers.
For Technical Support call +1 661.716.5100
PROGRAMMING THE CONTROLLOGIX CPU FOR A SMALL SLOTSERVER INTERFACE
4
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 LonWorks as the example
3rd Party Protocol. A hardcoded template filled with Lon variables is created. Each item uses a different amount of
bytes and the total adds up to 104 Lon 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.
4.1 Step 1: Establish an RSLogix project
4
Use File/New to create a new project or File/Open to open an existing project.
4.2 Step 2: Add and configure the Slot Server as an IO Module
Right-click on I/O Configuration and select “New Module”.
Choose the 1756-MODULE
4
Your Controller may be of a different type to the one shown in the example.
Select the slot number in the
rack where the Controller
resides.

SlotServer Configuration Manual Page 11 of 37
ProSoft Technology, Inc. is the exclusive provider of FieldServer SlotServers.
For Technical Support call +1 661.716.5100
Choose the 1756-
MODULE
Select the Slot number in the rack
where the SlotServer resides
Click Next

SlotServer Configuration Manual Page 12 of 37
ProSoft Technology, Inc. is the exclusive provider of FieldServer SlotServers.
For Technical Support call +1 661.716.5100
4.3 Step 3: Write Ladder Program to get Input Data from Data Arrays
Add a CPS (Synchronous Copy File) Ladder 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
Create the Destination Tag by
right clicking on Destination
and choosing New Tag.
Choose a RPI of 100.0 ms. This is the rate at
which the I/O image data will be transferred

SlotServer Configuration Manual Page 13 of 37
ProSoft Technology, Inc. is the exclusive provider of FieldServer SlotServers.
For Technical Support call +1 661.716.5100
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 LonWorks Data from the InData_Copy Tag to a new Controller
Tag, called Lon_In_01. Also create the Tag by right clicking on Destination and choosing New Tag. The New Tag
must be of type REAL and a dimension of 76.
Create a Controller Tag of Type
REAL, dimension 80 for the
Destination

SlotServer Configuration Manual Page 14 of 37
ProSoft Technology, Inc. is the exclusive provider of FieldServer SlotServers.
For Technical Support call +1 661.716.5100
Below is the final ladder program to access data from LonWorks 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.

SlotServer Configuration Manual Page 15 of 37
ProSoft Technology, Inc. is the exclusive provider of FieldServer SlotServers.
For Technical Support call +1 661.716.5100
4.4 Step 4: Write Ladder Program to Send Output Data to Data Arrays
This step demonstrates how to write data to the Data Array Out[0]
Create a Controller Tag called Lon_Out_01 of type REAL[80].
Add a new rung to the Ladder program and add a MOV element to move a block number value of 1 into
Lon_Out_01[2].
Finally add a CPS (Synchronous Copy File) element to copy the full Lon_Out_01 tag into the Output Image Tag.
The LonWorks Data are present from Lon_Out_01[4] to Lon_Out_01[79]
You can create a User Defined Data Type to replace the type of Lon_Out_01 mapping the points to LonWorks 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.
4.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.
4.6 Step 6: Set up the third party connection
In this example, this step would involve binding the LonWorks variables using a LonWorks Network Manager.

SlotServer Configuration Manual Page 16 of 37
ProSoft Technology, Inc. is the exclusive provider of FieldServer SlotServers.
For Technical Support call +1 661.716.5100
PROGRAMMING THE CONTROLLOGIX CPU FOR LARGER SLOTSERVER INTERFACES
5
The previous example is for accessing only one Data Array. The following steps describe how to access multiple
Data Arrays.
5.1 Multiple Input Data Arrays
In this example, we access SlotServer Arrays In[1] and In[2] by de-multiplexing them out of the Local In buffer using
the block number in the header information.]. We simply add to the existing ladder program as shown in the
Quickstart example. Add a branch after the CPS element that copies the input image Tag and copy and paste EQU
and CPS elements from the first rung. Create a new Input Tag for Lon_In_02 of type REAL and dimension 76.
Finally, remember to set the EQU Source B value to 2 to scan for incoming data from the second In Array, which is
recognized by a value of 2 in InData_Copy[2].
See the ladder program below how to add InData_Copy[2].
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 LonWorks Function Block.
5.2 Accessing Multiple Output Data Arrays
To access more output Data Arrays it is necessary to create a Multiplexer in Ladder. The Flash drive supplied with
the product includes an ACD file with an example of multiplexing use.
The basic steps include:
Create a Counter which counts up every 100ms.
Place the counter value into the Lon_Out_xx Tag at offset 2.
Copy the whole Tag into the output Data Image Tag for transferring to the LonWorks network.
The example program following shows an output counter that can count up to 25 which allows the transfer of data
into 25 Output Function Blocks. Only 2 rungs are shown to transfer data for blocks 1 and 2. Add more rungs with
more Lon_Out_xx tags to transfer data to other output Function Blocks.
It is possible to add up to 65535 blocks. The update rate decreases as the number of blocks goes up. For 25 blocks
the update rate is 25*RPI = 25*0.1 = 2.5 seconds.
The upcount may be restricted to a certain value, e.g.2 by changing the Preset value of the CTU element.

SlotServer Configuration Manual Page 17 of 37
ProSoft Technology, Inc. is the exclusive provider of FieldServer SlotServers.
For Technical Support call +1 661.716.5100
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.

SlotServer Configuration Manual Page 18 of 37
ProSoft Technology, Inc. is the exclusive provider of FieldServer SlotServers.
For Technical Support call +1 661.716.5100
5.3 Loading Data_Array Values from the FieldServer’s Non -Volatile Memory
If the value in the Data Array changes, the FieldServer can be configured to save this changed value to its Non-
Volatile Memory up to 3 times a minute using the DA_Function_After_Store Parameter. On startup the value will
be loaded from the Non-Volatile Memory into the Data Array. This value will only be stored 3 times a minute, so if
more writes than that are done, the values will be stored in the Data Array, but not to the Non-Volatile Memory.
Storing this value has performance impacts, so care must be taken to store this value only if needed.
There is a limit to the number of values that can be stored from a single data array:
UINT32: 9
FLOAT: 9
SINT32: 9
UINT16: 19
SINT16: 19
BYTE: 39
Example
Data_Arrays
Data_Array_Name
, Data_Format
, Data_Array_Length
, DA_Function_After_Store
DA_NV_UINT32
, UINT32
, 1
, Non_Volatile

SlotServer Configuration Manual Page 19 of 37
ProSoft Technology, Inc. is the exclusive provider of FieldServer SlotServers.
For Technical Support call +1 661.716.5100
TIMING PARAMETERS
6
Under normal operation, the FieldServer will send a poll request to a Server device and that device will reply with a
response. The amount of time between successive poll requests is called the Scan_Interval. The time between
receiving a response from a Server device and the next poll request is called the Poll_Delay.
If the FieldServer sends a poll request, and the Server device does not send a response, it is considered a timeout.
The time the FieldServer waits before declaring a timeout can be adjusted by the Timeout parameter. If a timeout
occurs, then the FieldServer will retry the poll request a few times (number of times tried is specified by the retries
parameter). The interval between retries is specified by the Retry_Interval. The FieldServer will send poll
requests at the end of each Retry_Interval. Once the specified numbers of Retries have been sent, the FieldServer
will mark the Node offline. Once a Node has been marked offline, it will wait for a period specified by
Recovery_Interval before sending another poll request.
Once the communications have been re-established, the FieldServer will wait for a period called Probation_Delay,
before marking the Node as online.
Note 1: The Ic_Timeout parameter monitors the time between characters in a response. If the time exceeds the
Ic_Timeout, the response is discarded and is considered a Timeout.
Note 2: All parameters in bold above are configurable. See table below for where they are configured, and what
the defaults will be if they are not configured.
Parameter
Default Value
Where Used
Scan_Interval
2 seconds
Map Descriptor, Node, Connection
Poll_Delay
0.05 seconds
Connection
Timeout
2 seconds
Map Descriptor, Node, Connection
Retry_Interval
10 seconds
Node
Retries
3 times
Node
Recovery_Interval
30 seconds
Node
Probation_Delay
1 minute
Node
Ic_Timeout
0.5 seconds
Map Descriptor, Node, Connection
Note 3: A non-response from the remote Server device causes a Timeout. The driver does nothing until a response
is received or the timeout period has expired. Thus if a connection has two Nodes and one Node is producing
Timeouts this will have the effect of slowing down communication for the other Node in the sense that the driver
does nothing while the timeout timer is counting up to its setpoint. Once there is a timeout on one Node, the
driver will not retry any Map Descriptors on that Node until the Retry_Interval has expired. Thus during the
Retry_Interval the other Node will get 100% of the service.

SlotServer Configuration Manual Page 20 of 37
ProSoft Technology, Inc. is the exclusive provider of FieldServer SlotServers.
For Technical Support call +1 661.716.5100
FieldServer Server Device
Poll
Response
Scan-Interval
Poll-Delay
Poll
Response
Poll
Timeout
Retry-interval
Poll
Poll
Recovery-Interval
Status: Node Online
Status: Node Offline
Poll
Response
Poll
Response
Poll
Response
Probation -Delay
Status: Node Online
Time
Retries
Figure I - SlotServer Timing Diagram