ProSoft Technology PS-QS-1x10-0781 - Manual (Page 74)

FieldServer Configuration Manual Page 74 of 90
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262-2299 Fax: (408) 262-2269 Toll Free: (888) 509-1970 email: [email protected]
Appendix B.3. 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
Float
Format used to store Floating Point Analog values. (e.g. temperature, volts). Each point
in the array represents one 32 bit Floating Point value.
Bit Format for storing Binary Data. Each point in the array represents one bit.
Byte Format for storing Bytes of data. Each point in the Array represents one Byte.
SInt16 – Signed 16 bit
Integer.
Range: -32768 to 32767, discrete. Each point in the array represents one integer.
Uint16 – Unsigned 16
bit Integer.
Range: 0 to 65 535, discrete. Each point in the array represents one integer.
SInt32 – Signed 32 bit
Integer Range: -2147483648 to 2147483647, discrete. Each point in the array represents one
integer.
Uint32 – Unsigned 32
bit Integer
Range: 0 to 4294967295, discrete. Each point in the array represents one integer.
In transferring data points from one protocol to another via the Data Arrays in the FieldServer, the integrity of the
data format is retained. E.g. if a point representing a bit data type is transferred into a Data Array of type Float,
the value will be a 32 bit floating point value that will only take on the values of 0 and 1. If this is transferred to an
integer point in another protocol, the value will still only ever take on the values of 0 and 1 despite the type
conversions. This can be overcome using Moves – refer to Section 5.2
Appendix B.4. Permissible Values for Configuration File Variables
Default and acceptable values for the different variables defined in the configuration file. Default values are
indicated in bold. Timing parameters are listed in seconds (0.003 would represent three milliseconds)
While this list contains acceptable variables for the FieldServer, some are not suitable for all configurations,
depending on the drivers used. Please see the Driver Manual for complete information regarding acceptable
variable values for specific drivers.