advertisement
15
Fisher ROC Serial Driver Help
Address Descriptions
ROC addresses are divided first by Point Type, Logical Address, and then by Parameter Index within the Point
Type. The general format is T-L.P, where: l l l
T: The Point Type.
L: The Logical Address.
P: The Parameter Index.
Parameters are blocked together on Point Type and Logical Address to a size up to 236 bytes. Some parameters are broken down into individual bits. Those parameters are addressed as T-L.P:B, where: l B: The Bit Offset.
For example, the address 1-50.3:2 indicates the following: l l l l
Point Type: 1
Logical Address: 50
Parameter: 3
Bit Offset: 2
For a detailed listing of all point type parameters, access, data type, length, and description, refer to the ROC device's ROC Protocol User Manual. For more information on ROC addressing, select a link from the list below.
Logical / Point Number Details
ROC Point Types
The availability of point types varies by model and by how the particular unit is equipped. Points may be Physical
I/O or Internal I/O.
Physical I/O Points
Physical I/O points are one of Discrete Inputs (type 1), Discrete Outputs (type 2), Analog Inputs (type 3), Analog
Outputs (type 4) and Pulse Inputs (type 5). The logical address for physical I/O points is based on their position in the unit, known as Point Number. There are four slots for each rack. The I/O field is not typically fully populated.
Note: Rack and slot are ROC nomenclature; however, many ROC devices have no physical racks or slots.
Logical addresses are calculated from the Point Number reference. For information on reconciling the Point
Number to the Logical Address, refer to the table below.
ROCLINK Point Number
A1-A16
B1-B16
C1-C16
D1-D16
E1-E16
...
Server Logical Address
0-15
16-31
32-47
48-63
64-79
...
For example, an I/O Point with ROCLINK 800 Point Number "A5" would be Logical Address "4". An I/O Point with
ROCLINK 800 Point Number "C5" would be Logical Address "36" by the function A + B + C5 (or 15+16+5=36).
Internal I/O Points
Internal I/O points consist of PID settings, system flags, communications parameters and other internal information. The internal I/O logical address begins at 0 for each point type. A ROC unit may have one or several of a given internal point type. Each point type has a specific set of parameters. ROC drivers have no array types.
Point Type Tables
ROC Point Types for ROC300-Series
ROC Point Types for FloBoss 100-Series, FloBoss 407, and FloBoss 500-Series
www. kepware.com
Fisher ROC Serial Driver Help
ROC Point Types for ROC300-Series
For a detailed listing of all point type parameters' access, data type, length and description, refer to the device's
ROC Protocol User Manual.
Point
Types
Description
44
49
50
56
57
59
35
36
37
38
39
40
41
42
4
5
6
7
9
0
1
2
3
Configurable Opcode
Discrete Inputs (DI)
Discrete Outputs (DO)
Analog Inputs (AI)
Analog Outputs (AO)
Pulse Inputs (PI)
Proportional, Integral and Derivative (PID) Control
American Gas Association (AGA) Flow Parameters
Local Display Panel
10
11
12
13
14
15
16
17
AGA Flow Values
Tank Parameters
ROC Clock
System Flags
Communication Ports
System Variables (ROC Information)
Function Sequence Table (FST) Parameters
Soft Points
18
19
20
AI Calibration
Database Setup
ROC Tasks
21 Information for User Defined Points
22-31 User Defined Points
32 User Defined Typically Modem Config for COM1
33
34
User Defined Typically Modem Config for LOI and COM2
User Defined Typically Modbus Config for COM1
User Defined Typically Function Config for COM1
User Defined Typically Host Config for COM1
User Defined Typically Modbus Config for LOI and COM2
User Defined Typically Function Config for LOI and COM2
User Defined Typically Host Config for COM1
Multi-Variable Sensor (MVS) Parameters
AGA Run Parameters
Extra Run Parameters
Power Control
Upload to Disk
Download to ROC
AI Calibration
Keypad / Logon Security Parameters
Program Flash Control Parameters
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
ROC300-
Series
ROCPAC
Yes
Yes
Yes
Yes
No
No
No
No
No
No
Yes
Yes
Yes
Yes
Yes
No
No
No
ROC300-Series
FlashPAC
No
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes*
Yes
Yes
*Added via a user program.
ROC Point Types for FloBoss 100-Series, FloBoss 407, and FloBoss 500-Series
Point Types Description
0
1
2
Configurable Opcode
Discrete Inputs
Discrete Outputs
FloBoss
100-Series
Yes
Yes
Yes
FloBoss
407-Series
Yes
Yes
Yes
FloBoss
500-Series
Yes
Yes
Yes
16 www. kepware.com
17
33
34
35
36
37
8
10
12
13
14
15
16
17
19
20
3
4
5
6
7
21
22-23
24
25–31
32
38
53
54
55
56
57
58
59
60-77
80
85
44
45
46
47
48
49
50
52
39
40
41
42
43
Analog Inputs
Analog Outputs
Pulse Inputs
PID Control*
AGA Flow Parameters*
History Parameters
AGA Flow Values*
ROC Clock
System Flags
Communication Ports
System Variables (ROC Information)
FST Parameters
Soft Points
Database Setup
ROC Tasks
Diagnostics
Information for User Defined Points
User Defined Points
Reserved
User Defined Points
User Defined – Typically Modem Config for
COM1
User Defined – Typically Modem Config for LOI and COM2
User Defined – Typically Modbus Config for
COM1
User Defined – Typically Function Config for
COM1
User Defined – Typically Host Config for COM1
User Defined – Typically Modbus Config for LOI and COM2
User Defined: Typically Function Config for LOI and COM2
User Defined – Typically Host Config for COM1
Multi-Variable Sensor (MVS) Parameters
AGA Run Parameters*
Extra Run Parameters*
User Lists
Power Control
Meter Calibration and Sampler
Meter Configuration Parameters
Meter Flow Values
PID Control Parameters
Upload to Disk
Download to ROC
Battery Parameters
Modbus Configuration Parameters
Modbus Function Tables
Modbus Special Function Table
AI Calibration
Keypad / Logon Security Parameters
Revision Information
Program Flash Control Parameters
SAM User Defined Parameters
Enhanced Communication (ECM) Parameters
HART Parameters
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
Yes
No
N/A.
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
Yes
Yes
Yes
Yes
Yes
Fisher ROC Serial Driver Help
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
No
N/A.
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
Yes
Yes
No
Yes
No
No
No
Yes
No
No
No
No
No
No
No
Yes
Yes
Yes
Yes
Yes
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
No
N/A.
No
No
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
Yes
Yes
Yes
Yes
Yes
No
No
Yes
No
No
Yes
Yes
Yes www. kepware.com
Fisher ROC Serial Driver Help
18
98
117
118
120
121
86
88
89
93
94
122
Extended History Parameters
BLM User Lists
Chart User List Parameters
License Key Information Parameters
User C Program Parameters
Extended Soft Point Parameters
Modbus Configuration Parameters
Modbus Register Mapping Parameters
Modbus Master Modem Configuration
Modbus Master Polling Table Configuration
Parameters
DS800 Configuration Parameters
Yes
Yes
Yes
Yes
Yes
Yes**
Yes
Yes
Yes
Yes
Yes
No
No
No
No
No
No
No
No
No
No
No
*FloBoss 100-Series and FloBoss 500-Series Backward Compatibility.
**This point type is only supported by FloBoss 107.
ROC Point Types for RegFlo
3
4
8
13
Point Types Description
0
1
2
Configurable Opcode
Discrete Inputs
Discrete Outputs
Analog Inputs
Analog Outputs
History Parameters
System Flags
14
15
Communication Ports
System Variables
57
80
81
84
Point Types
17
19
56
86
NA.
Description
Soft Points.
Database Setup.
AI Calibration.
Keypad / Logon Parameters.
Regulator Parameters.
Logic Alarm Parameters.
User Discrete Values.
Extended History Parameters.
NA.
No
No
No
No
No
No
No
No
No
No
No
Logical / Point Number Details
Within each point type, individual points are referenced by a Logical Number or a Point Number. The point numbers used by ROC protocol for point types 1 to 5 are based on a physical input or output (I/O) with a rack and module location. All other point types use a Logical Number, and are numbered in sequence.
Physical Point Numbers 0 to 69
For point types 1 through 5, there are point numbers for the field I/O and for the diagnostic inputs. They are as follows: l l
Point Numbers 0 to 63 are assigned to field I/O (built-in or modular, 64 maximum). For example, if there were ten I/O modules in a ROC364, they would be points 0 through 9. The ROC I/O point database would reference these points by rack and module location, such as A1 through A10.
Point Numbers 64 to 69 are assigned to the diagnostic (system) I/O. For example, the five diagnostic points in a ROC364 would be 64 through 68. The ROC I/O point database would reference these points by rack and module (namely, E1 to E5).
Logical Point Numbers 0 to 127
For all other point types (0 and 6–59), the point number is 0 to x, where x is one less than the total number of points that exist for that point type. For example, the four MVS points in a FloBoss 407 would be logical numbers
0 through 3.
Note: All parameters are 0-based for each point type.
User-Defined Point Types
User-Defined Points (UDP) make user program data available to ROCLINK and OPC clients. They are generally used for configuration purposes. When creating a User-Defined Point in the server, the server Configuration will always set the data type to Default. The data type will later be read live from the device.
Important: Users must reinitialize the server after upgrading the user program on a device; otherwise, the server will not be able to access the new points available in the upgraded user program.
www. kepware.com
19
Fisher ROC Serial Driver Help
Supported Device Models
All FloBoss 100 Series devices.
Supported User-Defined Point Range
22 to 23
25 to 39
178 to 189
Troubleshooting
To avoid potential issues, users should do the following: l l l
Verify that the point type is within the supported UDP range.
Verify that the point type exists in one of the user programs installed on the device.
Check the Event Log for the following error message, which will occur if the server fails to parse the UDP
configuration: Unable to parse the User-Defined Point configuration information for point type
'<point type>' on device '<device name>' .
Bit Assignments
The graphic below shows a sample bit assignment. The bits in each byte are numbered 0 to 7, right to left, with
Bit 7 shown the furthest to the left. A 1 in any bit indicates that it is active or enabled.
www. kepware.com
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement
Table of contents
- 2 Table of Contents
- 5 Fisher ROC Serial Driver Help
- 5 Overview
- 6 Channel Setup
- 7 Device Setup
- 7 Tag Import Settings
- 8 Address Specification
- 9 Operator Identification
- 10 EFM Meters
- 13 Data Types Description
- 14 Automatic Tag Database Generation
- 15 Address Descriptions
- 15 ROC Point Types
- 18 Logical / Point Number Details
- 18 User-Defined Point Types
- 19 Bit Assignments
- 20 Error Descriptions
- 21 Error Reasons
- 21 Address Validation
- 21 Address '<address>' is out of range for the specified device or register
- 22 Data Type '<type>' is not valid for device address '<address>'
- 22 Device address '<address>' contains a syntax error
- 22 Device address '<address>' is not supported by model '<model name>'
- 22 Device address '<address>' is Read Only
- 22 Missing address
- 22 Automatic Tag Database Generation Error Messages
- 23 Error importing CSV tag record <record number>: Address '<Address>' is out of...
- 23 Unable to generate a tag database for device '<device>'. Reason: <Error Reason>
- 23 Unable to generate a tag database for device '<device>'. Reason: Auto tag gen...
- 24 Unable to generate a tag database for device '<device>'. Reason: Error while ...
- 24 Unable to generate a tag database for device '<device>'. Reason: Error while ...
- 24 Unable to generate a tag database for device '<device>'. Reason: Failed to op...
- 24 Unable to generate a tag database for device '<device>'. Reason: Import file ...
- 24 Unable to generate a tag database for device '<device>'. Reason: Input file i...
- 25 Unable to generate a tag database for device '<device>'. Reason: Input file n...
- 25 Unable to generate a tag database for device '<device>'. Reason: Low memory r...
- 25 Unable to generate a tag database for device '<device>'. Reason: ROC system f...
- 25 Unable to generate a tag database for device '<device>'. Reason: System DB fi...
- 26 Device Specific Messages
- 26 '<Device Name>' - Failed to read EFM pointer file. <Extended Error>
- 26 '<Device Name>' - Failed to write EFM pointer file. <Extended Error>
- 27 Block read for point type <point type>, logical address <logical address>, pa...
- 27 Device '<device>' responded with error. (Tag '<tag address>')-Details: '<erro...
- 27 Failed to obtain data block for PointType = <point type>, Logical Address = <...
- 28 Failed to write data for PointType = '<point type>', Logical Address = '<addr...
- 28 Operator identification failed for device '<device name>'. <Error Reason>
- 28 Read for point type <point type>, logical address <logical address>, paramete...
- 28 ROC initialization error: Unable to read general configuration
- 29 ROC initialization error: Unable to retrieve I/O map
- 29 Serialization of EFM data to temporary file '<file name>' failed. Reason: '<f...
- 29 The username or password supplied was not accepted. Error = 6
- 29 The username or password supplied was not accepted. Error = 63
- 30 Time synchronization with device '<device name>' failed. <Error Reason>
- 30 Write for the following tags of device <device name> failed: <tag list>. <Err...
- 30 Write request rejected on Read Only item reference '<channel name>' '<device ...
- 30 Device Status Messages
- 30 Device '<device name>' is not responding
- 31 EFM '<type>' upload failed for device '<device>'. <Reason>
- 31 Resetting the EFM cache for device '<device>'
- 31 Serial Communications
- 31 Communications error on '<channel name>' [<error mask>]
- 32 COMn does not exist
- 32 COMn is in use by another application
- 32 Error opening COMn
- 32 Unable to set comm parameters on COMn
- 32 User-Defined Point Error Messages
- 33 Block read for point type '<point type>', logical address '<logical address>'...
- 33 Read for point type '<point type>', logical address '<logical address>', para...
- 33 Unable to load User-Defined Point configuration for point type <point type>, ...
- 33 Unable to parse the User-Defined Point configuration information for point ty...
- 33 User-Defined Point Configuration upload for point type '<point type>', logica...
- 34 ROC Error Codes
- 36 Index