...
Bit designator is optional and only valid for byte and integer type parameters. Returns the value of the zero based bit specified. Valid .Bit field value depends upon the number of bits in the parameter. Items that specify a bit field are read only.
Examples: P2:8, 395.Value:16, 45:0
Type designator is optional and usually not needed if the parameter specified is in the driver’s internal item lookup tables. These tables are used to validate the number of the parameter and determine data type. The type field is provided so that parameter items can be created as needed in the event the lookup tables are incorrect, incomplete, or new parameters are added in the future. Using a type specifier overrides the internal lookup tables. The type specified is the type of the parameter on the controller, not necessarily the data type of the OPC item in client software.
Examples: 1665/F, P3P20/TS, P9/W:4
Type Designator | Parameter Type | Data Type |
/M | String | String |
/A | Display | String |
/B | Byte | Byte |
/C | Signed Byte | Short Integer |
/W | Unsigned Short Integer | Unsigned Short Integer |
/S | Signed Short Integer | Signed Short Integer |
/L | Long Integer | Unsigned Long Integer |
/F | Floating Point | 32 bit Floating Point |
/T | Time | Unsigned Long Integer – “hhmmss” |
/TM | Time | String – “hh:mm:ss” |
/TS | Time | Unsigned Long Integer - number of seconds |
/D | Date | Unsigned Long Integer – “yymmdd” |
/DM | Date | String – “yy/mm/dd” |
/X | Command | Unsigned Short Integer |
/R | All | Raw ASCII string of parameter value |
By default, time and date parameters are returned as unsigned long integers in the format “hhmmss” and “yymmdd”. If a delimited string type item is desired, specify the data types as “/TS” TM” for time and “/DS” DM” for date. This will return string data in the formats “hh:mm:ss” and “yy/mm/dd”. Use “/TS” to treat time parameters as number of seconds.
| Info |
|---|
The :Bit and /Type specifiers can occur in either order but must be after the .Field specifier, if present. |
...