Editing Configuration Files - SMC Sierra Monitor QuickServer 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
Adapter , Protocol
N1 , Modbus/TCP
Adapter definition applies to defining network and
FieldServer connections (such as PROFIBUS).
//==========================================================
//
// Server Side Nodes
//
Nodes
Node_Name , Node_ID
MBP_Srv_11 , 11
A Node name for reference by the
Map Descriptors.
//==============================================================
//
// Server Side Map Descriptors
//
Map_Descriptors
Map_Descriptor_Name , Data_Array_Name , Data_Array_Offset , Function , Node_Name
SMD_DI_01 , DA_DI_01
SMD_DO_01 , DA_DO_01
3.3

Editing Configuration Files

The configuration file is in comma-delimited format where entries within a line are separated by commas
and the end of a line is indicated by an entry without a comma. This file can be edited using spreadsheet
programs or any text editor.
It is recommended that the CONFIG.CSV file be backed up before editing. Once edited, the file can be
saved and uploaded in the Graphic User Interface (see FieldServer GUI Manual for details).
Refer to Appendix C.4
specified values may be used - other values may affect FieldServer performance or functioning.
Not all parameters are compulsory for every driver (see the related driver manual for details). The bold
legal value is the value that will be used if the parameter is not specified.
Not all variables need be defined for every configuration. Depending on the protocol and configuration,
some variables might not be necessary. More detailed information is located in the relevant Driver
Manual, including settings specific to the drivers being used for a particular application.
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. Refer to Section
Since the FieldServer is a Server here, this is the ID of
the FieldServer (virtual) Node. The FieldServer can
represent multiple Virtual Node_ID's in most protocols.
, Protocol
, Modbus/TCP
, 0
, 0
for the parameters that are usually filled out in the configuration file. Only the
6.3 for more information on Dynamic Parameters.
Page 12 of 86
FieldServer Configuration Manual
The protocol for the network
connected to this port.
, Passive , MBP_Srv_11 , 10001
, Passive , MBP_Srv_11 , 00001
, Address , Length
, 200
, 200