Table of Contents
Advertisement
Advertisement
Table of Contents
Related Manuals for SMC Sierra Monitor QuickServer
Summary of Contents for SMC Sierra Monitor QuickServer
-
Page 1: Configuration Manual
FieldServer Configuration Manual This manual provides instructions for the following products: Description FS-B35 Series FieldServer QuickServer FieldServer APPLICABILITY & EFFECTIVITY Effective for all systems manufactured after May 2018. Document Revision: 2.D T18050... -
Page 2: Technical Support
FieldServer Configuration Manual Technical Support Please call us for any technical support needs related to the FieldServer product. Sierra Monitor Corporation 1991 Tarob Court Milpitas, CA 95035 Website: www.sierramonitor.com U.S. Support Information: +1 408 964-4443 +1 800 727-4377 Email: support@sierramonitor.com EMEA Support Information: +44 2033 1813 41 Email:... -
Page 3: Table Of Contents
FieldServer Configuration Manual TABLE OF CONTENTS FieldServer Concepts .......................... 7 Introduction ............................. 7 Application ............................7 Terminology ............................ 8 1.3.1 Nodes ............................8 1.3.2 Clients and Servers ......................... 8 Overall Operation Philosophy ......................9 Getting Started – Basic Configuration..................... 10 Configuration File Overview ...................... - Page 4 FieldServer Configuration Manual 5.2.9.3 Table String Composition ..................... 32 5.2.10 Conditional Moves ......................... 32 Conditional Moves – Example 1 ................... 33 5.2.10.1 Conditional Moves – Example 2 ................... 33 5.2.10.2 Mathematical Functions ........................ 34 5.3.1 Math Function as a Moves Function ..................34 5.3.2 Standalone Math ........................
- Page 5 FieldServer Configuration Manual Port Expander Mode – PEX Mode ....................57 How Port Expansion Works ......................57 Advantages of Port Expander Mode..................... 57 Limitations of Port Expander Mode ....................57 Port Expander Write Options ......................57 Handling of Successive Writes to the Same Point ............... 58 Port Expansion Configuration .......................
- Page 6 FieldServer Configuration Manual LIST OF FIGURES Figure 1: Client/Server ..........................8 Figure 2: FieldServer Operation Theory ....................... 9 Figure 3: DSW32 Interface Screen ......................13 Figure 4: DSW32 Error Screen with Driver Versions .................. 14 Figure 5: Typical Network Architecture ....................... 16 Figure 6: Grouping Data Process .......................
-
Page 7: Fieldserver Concepts
FieldServer Configuration Manual FIELDSERVER CONCEPTS Introduction The FieldServer functions as a gateway enabling different devices utilizing different protocols to interface with each other. The FieldServer solves communication and protocol conversion problems and improves response times in distributed data acquisition and control systems. The extensive driver library available from Sierra Monitor provides a wide range of interoperability solutions. -
Page 8: Terminology
FieldServer Configuration Manual Terminology 1.3.1 Nodes The devices communicating with the FieldServer may be referred to as “Stations”, “Nodes”, “RTU’s”, “DCS’s”, “Workstations”, “SCADA Systems”, “MMI’s”, “Field Devices”, etc. To prevent confusion these devices are always referred to as Nodes in this manual. Similarly, “Device Address”, “Station Address”, “Station ID”... -
Page 9: Overall Operation Philosophy
FieldServer Configuration Manual OVERALL OPERATION PHILOSOPHY The FieldServer functions as a bridge between two or more different Nodes (see Figure 2). The information is gathered by the Client side of the FieldServer from the Server Nodes via a Serial Port, Ethernet port or plug-in card. -
Page 10: Getting Started - Basic Configuration
FieldServer Configuration Manual GETTING STARTED – BASIC CONFIGURATION Configuration File Overview The default driver configuration file (CONFIG.CSV) for any driver combination ordered is loaded into the FieldServer and can be retrieved using the Graphical User Interface Utility (see the FieldServer FS-GUI Manual for more details). - Page 11 FieldServer Configuration Manual The Client Side Connections Section contains the parameters that describe the nature of the physical connection to the Server Nodes. //========================================================== Client Side Connections Connections Port , Baud , Parity , Data_Bits , Stop_Bits , Protocol , Poll_Delay , 9600 , None , Modbus_RTU...
-
Page 12: Editing Configuration Files
FieldServer Configuration Manual The Server Side Sections are functionally the same as their Client Side equivalents, except that Server parameters are being defined. /========================================================== Server Side Connections Connections The protocol for the network Adapter , Protocol connected to this port. , Modbus/TCP Adapter definition applies to defining network and FieldServer connections (such as PROFIBUS). -
Page 13: Testing Configuration Files With Dsw32.Exe
FieldServer Configuration Manual Testing Configuration Files with DSW32.EXE DSW32.exe is a program that simulates the FieldServer on the PC and can be used for testing edited configuration files before transferring them back to the FieldServer. This file can be obtained by calling technical support. -
Page 14: Additional Worthwhile Dsw32 Checks
FieldServer Configuration Manual NOTE: A number of "System Overrun" errors may occur in this screen. They are caused as a result of the simulation, and will not cause any problems on the FieldServer. None of these messages are errors. Config and system errors will have a “banner”... -
Page 15: Map Descriptor Functions
FieldServer Configuration Manual MAP DESCRIPTOR FUNCTIONS Map Descriptor functions determine how data is mapped between Data Arrays and the corresponding driver data points. The choice of function used is critical in ensuring that the right relationship is established with the device being communicated with. The most important decision to make when choosing a function is whether the function needs to be active or passive. -
Page 16: Working With Passive Client - Passive Server Applications
FieldServer Configuration Manual 4.2.2.1 Working with Passive Client – Passive Server Applications Data Server Client Typical Properties Map Descriptor function used for both protocols A and B is “passive”. FieldServer is non-intrusive into both networks, and responds to queries and commands only. -
Page 17: Active Map Descriptor Functions
FieldServer Configuration Manual Active Map Descriptor Functions A Responsible Map Descriptor is a Map Descriptor that inherently monitors the quality of the data that it is mapping and can be recognized by the “Function” parameter field. The following are all Responsible Map Descriptors. -
Page 18: Active Read Discovery On Startup (Ards)
FieldServer Configuration Manual 4.3.1.7 Active Read Discovery on Startup (ARDS) This function is used for discovering known Modbus RTU devices. A register(s) will be read and if a known value is received, a profile configuration will be loaded. Discovery based on Modbus Register: Map_Descriptors Map_Descriptor_Name , Data_Array_Name... -
Page 19: Active Write On Trigger (Awt)
FieldServer Configuration Manual 4.3.2.6 Active Write on Trigger (AWT) This function is used to affect a single data write per trigger. As with the WRBX function, the write only occurs when the Data Array is updated. In this case the updated data is not used to form the write, but updating the Data Array triggers a read of a Secondary Data Array which contains the data to be served in the write. -
Page 20: Data Manipulation Features
FieldServer Configuration Manual DATA MANIPULATION FE ATURES The features described in this section may or may not be needed depending on the application where the FieldServer is implemented. If the application calls for straight passing of data without modification through the FieldServer, then the features in this section will probably not be useful. Moves The Moves function permits data to be moved from one Data Array to another. -
Page 21: Simple Moves
FieldServer Configuration Manual 5.1.1 Simple Moves The simplest move involves the transfer of data without any format or protocol changes. Whenever the Source Data Array is updated (not necessarily changed) the Target Data Array will be updated. 5.1.1.1 Simple Move Example A move is reversible, meaning Data_Arrays data can move from Target_DA to... -
Page 22: Special Application - Grouping Data
FieldServer Configuration Manual 5.1.1.2 Special Application – Grouping Data The location of data in Data Arrays on the FieldServer is determined by corresponding Map Descriptors. Should a Client poll the FieldServer for data spanning more than one Map Descriptor, the FieldServer will not know which Map Descriptor to use. -
Page 23: Special Application - Separating Responsible Map Descriptors
FieldServer Configuration Manual 5.1.1.3 Special Application – Separating Responsible Map Descriptors Responsible Map Descriptors are active Map Descriptors that control the Communications (see Section 4). Two Responsible Map Descriptors cannot share the same Data Array Offset due to monitoring functions present in the kernel (refer to Section for more information). -
Page 24: Function Moves - Type Casting
FieldServer Configuration Manual Function Moves – Type Casting It is often necessary to manipulate incoming data to create the necessary outgoing data by either joining smaller data types to create a larger data type, or splitting larger data types to deliver smaller data types. An example of this is Modbus, where two 16 bit registers are used to transfer a 32 bit floating point value. -
Page 25: Converting Two Integers To A Float
FieldServer Configuration Manual 5.2.2 Converting Two Integers to a Float Data_Arrays Data_Array_Name , Data_Format , Data_Array_Length Source_DA , Uint16 , 200 Target_DA , Float , 200 Moves Function , Source_Data_Array , Source_Offset , Target_Data_Array , Target_Offset , Length Join_Float , Source_DA , Target_DA , 40 Length refers to the data type referenced in the Function. -
Page 26: Example 1 - Simple Bit Extraction
FieldServer Configuration Manual Parameter Function The function extracts bits out of the source Data_Array Registers at the Data Array offset specified. The bits are placed into the destination array in sequence. Only one bit is Bit_Extract allocated per offset. If the source array is of Bit Data Array type, a straight move is performed. -
Page 27: Example 3 - Extracting Bit Groups
FieldServer Configuration Manual 5.2.6 Example 3 – Extracting Bit Groups The following example extracts 3 bits from the second byte of a 32-bit register and places them into a byte register on their own. The Bit_Offset keyword is used here to achieve this: Data_Arrays Data_Array_Name , Data_Format , Data_Array_Length Source_DA... -
Page 28: Bit Extraction Example Configuration
FieldServer Configuration Manual A single packed bit integer with a value of 1034 signifies a blown rectifier fuse, a hardware shutdown, and a battery discharge (sum of the values for the corresponding events). The value “1034” has no meaning as such, but when the integer is “unpacked” the individual data bits communicate the required information. -
Page 29: Task Moves
FieldServer Configuration Manual 5.2.8 Task Moves If a Task_Name is defined the move will become a repetitive task and the data will be updated on a regular basis. The time between updates can be set using the Scan_Interval parameter. If the Scan_Interval parameter is set the Task_Name parameter must be set. -
Page 30: Match-Pattern
FieldServer Configuration Manual 5.2.9 Match-Pattern The match pattern move is used at run time to move a customized single value based on combinations of values in a Data Array as compared with preloaded customized criteria. • The user builds a table of patterns (strings of tokens separated by “-“) each linked to a particular location in a target Data Array. -
Page 31: Table Of Patterns Configuration Example
FieldServer Configuration Manual 5.2.9.1 Table of Patterns Configuration Example Section Title Offset_Table Column Title Function Legal Values Offset_Table_Name Provide name for Offset Table. Up to 32 alphanumeric characters. A unique value that will be stored if the Table_Index_Value 1-16 pattern matches. The pattern: “–“... -
Page 32: Conditional Moves
FieldServer Configuration Manual 5.2.9.3 Table String Composition Source Data Array Source Data Array Build Pattern Description Values Format 55 15 0 255 Byte 37-0F-00-FF Two Hex Characters. 555 15 0 -2550 INT, UINT16, UINT32 555-15-0--2550 Just as decimal values. 55.12-15.12-0.00- Requires period 55.12 15.123 0 255... -
Page 33: Conditional Moves - Example 1
FieldServer Configuration Manual 5.2.10.1 Conditional Moves – Example 1 In this example, the user needs to move the data from one of two source locations based on the status of bit 1 or 2 of the conditional Data Array. If bit 1 is high, then the data from Source_1 will be moved. If bit 2 is high, the Data from Source_2 will be moved. -
Page 34: Mathematical Functions
FieldServer Configuration Manual Mathematical Functions Mathematical functions implement subset of math functions of Data Array values. Some single-operator functions can be incorporated into Moves, but Multi-operator/operand functions must be defined in the Math block. The length of the move defines the number of input operands. The following table shows the Mathematics functions and their text representation: Operator Mathematics... -
Page 35: Standalone Math
FieldServer Configuration Manual 5.3.2 Standalone Math The Math definition allows up to four source data locations, up to four Math operations, and one output data location. Operands are kept on a “stack” and are operated on in the sequence in which they have been defined. -
Page 36: Optional Parameters
FieldServer Configuration Manual 5.3.4 Optional Parameters Legal Parameter Description Values Specifies the number of consecutive source Data Array values from all defined source Data Arrays (for example, DAI1 through DAI4) to be Length* positive operated on and to store a result at consecutive target locations, starting integer at the respective offsets. -
Page 37: Logic
FieldServer Configuration Manual Logic Logic functions implement Boolean functions (True/False statements) of bit Data Array values. Single- operator logic can be incorporated into Moves, but Multi-operator/operand logic must be defined in the Logic block. 5.4.1 Logic as a Moves Function The length of the Move defines the number of input operands. -
Page 38: Scaling
FieldServer Configuration Manual Scaling When writing a configuration file for the FieldServer, it may be required for the FieldServer to scale data before passing it on to the receiving devices. This can be accomplished in three different places in the FieldServer configuration: •... -
Page 39: Scaling Using Moves
FieldServer Configuration Manual 5.5.2 Scaling Using Moves It is also possible to scale values while moving data between Data Arrays. Doing the scaling this way often provides more visibility as it is then possible to view both scaled and unscaled data in the Data Arrays. -
Page 40: Preloading Data Arrays With Initial Values
FieldServer Configuration Manual Preloading Data Arrays with Initial Values 5.6.1 Introduction Preloads provide a technique which allows parts of one or more Data Arrays to be initialized to specified values. The Preloads are defined in a configuration file and loaded once when the configuration file is loaded as the FieldServer starts. -
Page 41: Limitations And Operational Considerations
FieldServer Configuration Manual 5.6.3 Limitations and Operational Considerations • Each Data Array location to be preloaded requires its own preload line in the configuration file. • The value specified must be compatible with the format of the Data Array – for example, Integer arrays cannot be preloaded with numbers that contain fractions. -
Page 42: Example 3: Load A Value - Negative Numbers
FieldServer Configuration Manual 5.6.6 Example 3: Load a Value – Negative Numbers Only SINT16, SINT32 and FLOAT formatted Data Arrays can store negative numbers. The Preload_Data_Format must also be specified with one of those formats. Preload_Data_Format must be cast so that the sign is preserved and then stored in a Data Array whose format can support negative numbers. -
Page 43: Example 6: Load A Value - Strings (2)
FieldServer Configuration Manual 5.6.9 Example 6: Load a Value – Strings (2) Data_Arrays Data_Array_Name , Data_Format , Data_Array_Length DA_1 , Uint32 , 20 Preloads Data_Array_Name , Preload_Data_Value , Preload_Data_Format , Preload_Data_Index DA_1 , ABCD , String The value found in the 1st element of the Data Array will be 0x4241 (Ascii value of A) and the value found in the 2nd element will be 0x4443 (Ascii value of B). -
Page 44: Loading Data_Array Values From The Fieldserver's Non-Volatile Memory
FieldServer Configuration Manual 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. -
Page 45: Node Management
FieldServer Configuration Manual NODE MANAGEMENT Data Array Functions 6.1.1 Node Status Function The Node Status Function is a Data Array function which provides the communication status between the FieldServer and the actively mapped Nodes. The online status of a particular Node is indicated in the Node Status Data Array. -
Page 46: Alias_Node_Id - Example
FieldServer Configuration Manual 6.1.3 Alias_Node_ID – Example A Data Array has been defined to report the status of the Nodes in the configuration using the Alias_Node_ID. Each Node that has been allocated an Alias_Node_ID will have the corresponding bit in the Data Array set/unset based on the Node’s status. -
Page 47: Node_Online_Bits
FieldServer Configuration Manual 6.1.4 Node_Online_Bits This Data Array function allows the user to specify Nodes and Subnets for which communication status is required. Typical Data Array Parameters are: Section Title Data_Arrays Column Title Function Legal Values Up to 15 Data_Array_Name Provide name for Data Array. -
Page 48: Connection Parameters
FieldServer Configuration Manual Connection Parameters 6.2.1 Node_Retire_Delay When a FieldServer is started up, it polls all Nodes. Nodes that respond within the specified timeout period (seconds) will be marked online. Nodes failing to respond within the timeout period will be repeatedly polled for the length of time specified in the Node_Retire_Delay parameter (seconds). -
Page 49: Node Inactivity Timeout
FieldServer Configuration Manual 6.3.2 Node Inactivity Timeout This parameter can be used with Passive Client drivers to let the FieldServer mark the node offline, should no messages be received in the set time period. Normal node recovery will take place and the node will go online once messages are received again. -
Page 50: Setup Dynamic Parameters
FieldServer Configuration Manual SETUP DYNAMIC PARAMETERS Most FieldServer parameters are specified in a configuration file and are fixed. A growing number, however, may be changed dynamically using values found in Data Arrays. We call these Dynamic Parameters. The following parameters can be dynamically configured. Parameter Section Title Notes... -
Page 51: Diagram 2 - Dynamic Server Side Node_Id
FieldServer Configuration Manual 7.1.1.2 Diagram 2 – Dynamic Server Side Node_ID It is possible to control the Node_ID of the Server Node by including a special task in the Configuration file that watches the value of a single element of a Data Array. When the value is updated then this task takes the value and replaces the Node_ID of a designated Node so that its new Node_ID is the value found in the Data Array. -
Page 52: Map Descriptor Parameters Specific To Dynamic Parameters
FieldServer Configuration Manual 7.1.2 Map Descriptor Parameters Specific to Dynamic Parameters Section Title Map_Descriptors Column Title Function Legal Values Change_Node_ID Function Function of Client Map Descriptor. Change_System_Node_ID Change_System_MAC_Addr One of the Node names specified as Name of the Object that will be described in Appendix C.4.5, or the Bridge... -
Page 53: Dynamic Parameters
FieldServer Configuration Manual 7.1.3 Dynamic Parameters Section Title Dynamic_Parameters Column Title Function Legal Values Load_csv, Load_csv_with_parameter, Function Function to load profile. Load_profile Parameter Parameter to load profile. DA_Offset Name of Data Array from which the One of the Data_Array_Names specified Data_Array_Name parameter value is taken. -
Page 54: Examples
FieldServer Configuration Manual 7.1.6 Examples 7.1.6.1 Example 1 – Dynamic Allocation of Node ID The parameter value is taken from the specified Data Array and Data Array Offset, and is used to modify the parameter specified under Function of the object (example: Node) specified under Descriptor_Name, subject to the limits set by Low_Limit and High_Limit. -
Page 55: Example 4 - Dynamic Allocation Of The Connection Baud Rate
FieldServer Configuration Manual 7.1.6.4 Example 4 – Dynamic Allocation of the Connection Baud Rate The Baud Rate on a connection can be dynamically changed from a Data Array Value by one of the following methods. Method 1: Using pre-mapped Data Array values to Baud Rates By defining the Data Array format as Baud, a responsible Map Descriptor can be used to dynamically change the Baud Rate on the associated connection. -
Page 56: Error Messages
FieldServer Configuration Manual 7.1.7 Error Messages Message Description DynParam:#1 Err. Validation impossible. Lo=%f Hi=%f The low validation value is greater than the high value. Desc=%s" This message is printed when evaluating a Dynamic parameters task DynParam:#2 Err. where the function = ‘Change_Node_ID’. The maximum length of the DescName=%s too long. -
Page 57: Port Expander Mode - Pex Mode
FieldServer Configuration Manual PORT EXPANDER MODE – PEX MODE Under certain conditions the FieldServer can be configured in a Port Expander Mode where statically configured Map Descriptors are not required to retrieve data from a Server Node. How Port Expansion Works When the FieldServer receives a poll from the Client Node, it scans its internal tables looking for a Map Descriptor that matches the poll. -
Page 58: Handling Of Successive Writes To The Same Point
FieldServer Configuration Manual Handling of Successive Writes to the Same Point When multiple successive port expansion writes to the same point occur, there is a potential build-up of pending write transactions in the FieldServer, since the Server side may receive write transactions at a faster speed than they are completed on the Client side (depending on the speeds of the respective protocols). -
Page 59: Timing Parameters
FieldServer Configuration Manual TIMING PARAMETERS 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. -
Page 60: Figure 12: Fieldserver Timing Diagram
FieldServer Configuration Manual FieldServer Server Device Poll Scan-Interval Response Poll-Delay Poll Response Status: Node Online Poll Timeout Retry-interval Poll Retries Poll Status: Node Offline Recovery-Interval Poll Response Poll Probation -Delay Response Poll Response Status: Node Online Time Figure 12: FieldServer Timing Diagram Page 60 of 86... -
Page 61: Line Drive Parameters
If the time set is too short, the FieldServer’s message will be truncated. For P1-P2 or R2 on the RS-232 QuickServer, the Line_Drive parameters default to 0. Line Drive is implemented on FieldServers using the RTS (Request to send) line on the RS-232 connection. -
Page 62: Figure 13: Timing Diagram
FieldServer Configuration Manual The first two are examples of what is termed TX squelch, received by the transmitting port at the end of a message; the last two are examples of RX squelch, received by the receiving port at the end of a message. -
Page 63: Setting Parameter Values
FieldServer Configuration Manual 9.2.1 Setting Parameter Values It is important to prevent the squelch suppression times from overlapping with valid data and interfering with proper communication. The following connection parameters can be configured for the FieldServer: Turnaround_delay This is the time the Server takes to initiate a response after having received a poll. The Client connection must have a Squelch_Timer_Tx value less than the turnaround delay. -
Page 64: Use Of Ssl/Tls For Secure Connection
FieldServer Configuration Manual 10 USE OF SSL/TLS FOR SECURE CONNECTION SSL/TLS (Secure Sockets Layer/Transport Layer Security) is a security technology for establishing an encrypted connection between a server and a client. This allows the secure transfer of data across untrusted networks. These functions are supported on the following: FS-QS-1010 or FS-QS-1210 with a serial number starting with 14 or later (indicating the year it shipped). -
Page 65: Limiting Client Access
FieldServer Configuration Manual 10.1.2 Limiting Client Access In addition to TLS_Port parameter also add Validate_Client_Cert in the connections section of the configuration file and set it to “Yes”. Connections Adapter , Protocol , TLS_Port , Validate_Client_Cert , Modbus/TCP , 1502 , Yes The configuration above sets the FieldServer to request and verify a client’s certificate against its internal authority file before accepting connection. -
Page 66: Certificate Validation Options
FieldServer Configuration Manual 10.1.3 Certificate Validation Options If connections must be limited to only a particular domain (vendor devices), include Check_Remote_Host to specify the domain/host name. Connections Adapter , Protocol , TLS_Port , Validate_Client_Cert , Cert_Authority_File , Check_Remote_Host , Modbus/TCP , 1502 , Yes , my_authorized_clients.pem , SMC The configuration above tells the FieldServer to only accept connections that have the correct certification... -
Page 67: Configuring Fieldserver As Ssl/Tls Client
FieldServer Configuration Manual 10.2 Configuring FieldServer as SSL/TLS Client The following Node configurations set the FieldServer to open a secure Modbus/TCP connection to Server at IP Address 10.11.12.13 on port 1502. 10.2.1 Simple Secure Client Configuration Add Remote_Node_TLS_Port parameter in the nodes section of the configuration file and set to a port number between 1 –... -
Page 68: Appendix A. Useful Features
FieldServer Configuration Manual Appendix A. Useful Features Using Comments Configuration file comments are either lines or line segments that start with “//”. These allow notation within the code for reference or organization. See Examples below. Nodes // Main building Node Node_Name , Node_ID , Protocol... -
Page 69: Appendix A.3. Disabling The Client Side Of A Configuration
FieldServer Configuration Manual Disabling the Client Side of a Configuration Set up the Modbus Server side Data_Arrays Data_Array_Name , Data_Format , Data_Array_Length DA_DO_01 , Bit Connections Port , Baud , Parity , Data_Bits , Stop_Bits , Protocol , 9600 , None , 8 , Modbus_RTU Nodes Node_Name... -
Page 70: Appendix A.4. Disabling Statistics Display
FieldServer Configuration Manual Disabling Statistics Display For large configurations with many Map Descriptors there is a possibility that the FieldServer will run out of memory before the entire configuration file is loaded. In order to conserve memory, it is possible to disable the collection of per Map Descriptor statistics. -
Page 71: Appendix B. Troubleshooting
FieldServer Configuration Manual Appendix B. Troubleshooting Moves Performance Suppose we need to read 1000 points from a PLC and transfer it to another data array, there are several ways to do it using moves. The table below shows the impact on the time it takes to complete the moves using different configuration methods: Memory Locations Performance Degrade... -
Page 72: Appendix C. Reference
FieldServer Configuration Manual Appendix C. Reference Working with the Driver Manuals Appendix C.1.1. Introduction The purpose of the Driver Manual is to provide driver specific configuration information. When drivers are installed in the FieldServer the specific combination is assigned a Driver Configuration Code (DCC). The DCC covers the combination of drivers listed on the cover. -
Page 73: Appendix C.3. Available Data Types For Data Arrays
FieldServer Configuration Manual Available Data Types for Data Arrays To facilitate the choice of data type, each of the data types available are described below. Data Format Description Format used to store Floating Point Analog values (Example: temperature, Float volts). Each point in the array represents one 32 bit Floating Point value. Format for storing Binary Data. -
Page 74: Appendix C.4.1. Common Information
FieldServer Configuration Manual Appendix C.4.1. Common Information Section Title FieldServer Column Title Function Legal Values Title Allows user to specify the title of the FieldServer. Title Text When poll block caching is used, data previously polled and stored in an Cache_Age;... -
Page 75: Appendix C.4.2. Data Arrays
FieldServer Configuration Manual Appendix C.4.2. Data Arrays Section Title Data_Arrays Column Title Function Legal Values Data_Array_Name Up to 15 Alpha Numeric Provides name for Data Array. (DA_Name) Characters. INT16, INT32, or BYTE; Specifies size of source value when scaling Data_Format Provides Data Format. -
Page 76: Appendix C.4.4. Connections/Adapters
FieldServer Configuration Manual Keyword Description Dev_Msg_Rates Same as above, except counting messages not errors. Dev_Error_Percentage Percentage of messages generating errors over the past hour. Provides the communication status between the FieldServer and the actively mapped Nodes. Refer to Node_Status Section 6.1.1. Where 2 nodes have the same Node_ID or Node_ID’s are longer than 255, each Node can be assigned Alias_Node_Status an Alias_Node_ID which can be used to provide Node Status. -
Page 77: Appendix C.4.5. Nodes
FieldServer Configuration Manual The length of the queue can be configured if blocking mode is set. Blocking will occur when there is no more space on the Write_Queue. Write_Queue_Size* Non-negative integer, 0 If size=0 every successive write is blocked. A message will be displayed when blocking occurs, except if the Queue_Size=0. - Page 78 FieldServer Configuration Manual Host_Name* Specifies the host name of the remote device. Any valid host name Specifies how many sequential errors must occur before marking a data buffer and poll block bad, and marking a device offline. The FieldServer will poll the device and if it receives no Retries* response will retry polling the device the number of times Count default 3...
- Page 79 FieldServer Configuration Manual If this parameter is defined, when a Client Node goes offline, Clear_Data_Array, No_Action, - Node_Offline_Action* all Data Array values of Map Descriptors defined on this Node will be set to zero. Remote_IP_Address* The remote IP Address used by this node. Required for protocols that use it Specified in the configuration file as the PLC_Type.
-
Page 80: Appendix C.4.6. Map Descriptors
FieldServer Configuration Manual Appendix C.4.6. Map Descriptors Section Title Map Descriptors Column Title Function Legal Values Map_Descriptor_Name Used to identify a Map Descriptor by name. Up to 32 Alpha Numeric Characters Data_Array_Name The name of the Data Array where information will be stored to One of the Data Array names as (DA_Name) and retrieved from by the Map Descriptor. -
Page 81: Appendix C.5. Valid Characters For Common Fields In Configuration Files
FieldServer Configuration Manual Valid Characters for Common Fields in Configuration Files ASCII Code Char Comment ASCII Code Char Comment [space] ‘ 38 & 39 _ [underscore], < > Page 81 of 86... -
Page 82: Appendix C.6. Kernel Error Messages And Descriptions
FieldServer Configuration Manual Kernel Error Messages and Descriptions Error Description Action 10003 A write to a Data Array exceeds the available space. Check Map Descriptor Offset, length. 10004 A write to a Byte/FloatData Array exceeds the available space. 10005 A range of data exceeds the length of a BYTE Data Array. Check Map Descriptor Offset, length, count. - Page 83 FieldServer Configuration Manual Error Description Action A move was defined, and a write occurred to the target Data 10055 Array, but cannot transfer to the Source Data Array because no Responsible Active Map Descriptor is defined. A move was defined, and a write occurred to the target Data Array, but cannot transfer to the Source Data Array because the 10056 Node associated with the Responsible Active Map Descriptor is...
- Page 84 FieldServer Configuration Manual Error Description Action In the BACnet driver, the OPTION_LIST specified caused the 10125 packet buffer to be exceeded. As a result the packet buffer was truncated. The BACnet driver received a request for a This is not reported in the current release of the BACnet 10126 read_property_multiple with multiple objects.
-
Page 85: Appendix C.7. Networking Glossary Of Terms
FieldServer Configuration Manual Error Description Action Use the event's panel, module and device numbers to define a Map Descriptor with Node_Name = panel. Example: For message: DRIVER-> CER : No mapdesc for panel 2, module 15, device 4, Create a mapdesc that will map to an address of15*256 + 4 = 3844, since there are always 256 devices per module Cerberus. - Page 86 FieldServer Configuration Manual Term Description The Internet is a collection of over 2, 000 packet-switched networks located all over the world, all linked using Internet the TCP/IP protocol. It links many university, government and research sites. Internet Protocol (IP) IP is part of the TCP/IP suite. It is a session layer protocol that governs packet forwarding. Interoperability is the ability of one manufacturer’s computer equipment to operate alongside, communicate Interoperability with, and exchange information with another vendor’s dissimilar computer equipment.
Need help?
Do you have a question about the QuickServer and is the answer not in the manual?
Questions and answers