Fisher ROC Serial Driver Help © 2014 Kepware Technologies
Fisher ROC Serial Driver Help 2 Table of Contents Table of Contents 2 Fisher ROC Serial Driver Help 5 Overview 5 Channel Setup 6 Device Setup 7 Tag Import Settings 7 Address Specification 8 Operator Identification 9 10 EFM Meters Data Types Description 13 Automatic Tag Database Generation 14 Address Descriptions 15 ROC Point Types 15 Logical / Point Number Details 18 User-Defined Point Types 18 Bit Assignments 19 Error Descriptions 20 Error Reasons 21 Address Validation
Fisher ROC Serial Driver Help 3 found Unable to generate a tag database for device ''. Reason: System DB file not found 25 26 Device Specific Messages '' - Failed to read EFM pointer file. 26 '' - Failed to write EFM pointer file. 26 Block read for point type , logical address , parameter range of device failed.
Fisher ROC Serial Driver Help 4 device '' User-Defined Point Configuration upload for point type '', logical address '', parameter number '' of device '' failed. 33 34 ROC Error Codes Index 36 www. kepware.
Fisher ROC Serial Driver Help 5 Fisher ROC Serial Driver Help Help version 1.
Fisher ROC Serial Driver Help 6 Channel Setup Communication Serialization The Fisher ROC Serial Driver supports Communication Serialization, which specifies whether data transmissions should be limited to one channel at a time. For more information, refer to "Channel Properties - Advanced" in the server help file. www. kepware.
Fisher ROC Serial Driver Help 7 Device Setup Supported Devices FloBoss 100 Series FloBoss 407 FloBoss 500 Series ROC 300 Series-ROCPAC ROC 300 Series-FlashPAC RegFlo Supported Protocol Remote Operation Controllers (ROC) Maximum Number of Channels and Devices The maximum number of supported channels is 256. The maximum number of devices supported per channel is 255.
Fisher ROC Serial Driver Help l l 8 Import method: This parameter specifies the import method. Options include Online - from Device and Offline - from Import File. The default setting is Online - from Device. Descriptions of the options are as follows: l Online - From Device: This method automatically creates tags by polling the device for its configuration and I/O data. l Offline - From Import File: This method automatically creates tags from a project file created in ROCLINK 800.
Fisher ROC Serial Driver Help 9 Descriptions of the parameters are as follows: l Device address: This parameter specifies the device number of the remote ROC device. The valid range is 1 to 255. The default setting is 240. l Device group: This parameter specifies the group number of the remote ROC device. The valid range is 1 to 255. The default setting is 240. l Host address: This parameter specifies the ROC unit number of the server. The valid range is 1 to 255. The default setting is 1.
Fisher ROC Serial Driver Help 10 Descriptions of the parameters are as follows: l Username: This parameter specifies the username. Three characters (as set in the device) are required. l Password: When checked, this option specifies that the ROC device has a password defined for the Operator ID. Four numeric characters can be entered. The valid range is 0000 to 9999. The default setting is checked. l Access Level: When checked, this option specifies that the ROC device has defined access levels.
Fisher ROC Serial Driver Help 11 Descriptions of the parameters are as follows: l Non-Meter Events: This parameter specifies how non-meter EFM events will be provided to EFM Exporters. Options include Ignore, Broadcast, and Selected Meters. The default setting is Broadcast. Descriptions of the options are as follows: l Ignore: This option will not send non-meter events to any meters. l Broadcast: This option will send non-meter events to all meters.
Fisher ROC Serial Driver Help 12 Descriptions of the parameters are as follows: l Meter Name: This parameter specifies the meter name. Each meter must be assigned a unique name. The default setting is Meter_1. l Receive Non-Meter Events: When checked, this option enables the meter to receive non-meter events. Note: This option will only be available when the Non-Meter Events parameter is set to Selected Meters. www. kepware.
Fisher ROC Serial Driver Help 13 Data Types Description Data Type Description Boolean Single bit Char Signed 8 bit value bit 0 is the low bit bit 6 is the high bit bit 7 is the sign bit Byte Unsigned 8 bit value bit 0 is the low bit bit 7 is the high bit Short Signed 16 bit value bit 0 is the low bit bit 14 is the high bit bit 15 is the sign bit Word Unsigned 16 bit value bit 0 is the low bit bit 15 is the high bit DWord Unsigned 32 bit value bit 0 is the low bit bit 31 is the high bit Float
Fisher ROC Serial Driver Help 14 Automatic Tag Database Generation This driver makes use of the server's Automatic Tag Database Generation feature. When enabled, this feature will build a list of tags within the server that correspond to the device's data points. Extra tags may be generated that affect the quality of other generated tags. Automatic Tag Database Generation may be configured through the Database Creation tab in Device Properties.
Fisher ROC Serial Driver Help 15 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 T: The Point Type. l L: The Logical Address. l 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.
Fisher ROC Serial Driver Help 16 ROC Point Types for RegFlo 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.
Fisher ROC Serial Driver Help 17 3 Analog Inputs Yes Yes Yes 4 Analog Outputs Yes Yes Yes 5 Pulse Inputs Yes Yes Yes 6 PID Control* Yes Yes Yes 7 AGA Flow Parameters* Yes Yes Yes 8 History Parameters Yes No Yes 10 AGA Flow Values* Yes Yes Yes 12 ROC Clock Yes Yes Yes 13 System Flags Yes Yes Yes 14 Communication Ports Yes Yes Yes 15 System Variables (ROC Information) Yes Yes Yes 16 FST Parameters Yes Yes Yes 17 Soft Points Yes Yes Yes 19 Data
Fisher ROC Serial Driver Help 18 86 Extended History Parameters Yes No No 88 BLM User Lists Yes No No 89 Chart User List Parameters Yes No No 93 License Key Information Parameters Yes No No 94 User C Program Parameters Yes No No 98 Extended Soft Point Parameters Yes** No No 117 Modbus Configuration Parameters Yes No No 118 Modbus Register Mapping Parameters Yes No No 120 Modbus Master Modem Configuration Yes No No 121 Modbus Master Polling Table Configuration
Fisher ROC Serial Driver Help 19 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 Verify that the point type is within the supported UDP range. l Verify that the point type exists in one of the user programs installed on the device.
Fisher ROC Serial Driver Help 20 Error Descriptions The following error/warning messages may be generated. The messages are listed here in alphabetical order.
Fisher ROC Serial Driver Help 21 Communications error on '' [] COMn does not exist COMn is in use by another application Error opening COMn Unable to set comm parameters on COMn User-Defined Point Error Messages Block read for point type '', logical address '', parameter range '' of device '' failed.
Fisher ROC Serial Driver Help 22 Solution: Verify that the address is correct; if it is not, re-enter it in the client application. Data Type '' is not valid for device address '' Error Type: Warning Possible Cause: A tag address that has been specified statically has been assigned an invalid data type. Solution: Modify the requested data type in the client application.
Fisher ROC Serial Driver Help 23 Automatic Tag Database Generation Error Messages Error importing CSV tag record : Address '' is out of range for the specified device or register Unable to generate a tag database for device ''. Reason: Unable to generate a tag database for device ''. Reason: Auto tag generation failed: device is not responding Unable to generate a tag database for device ''.
Fisher ROC Serial Driver Help 24 Unable to generate a tag database for device ''. Reason: Error while reading from import file Error Type: Warning Possible Cause: 1. The tag import file (*.800) is corrupt. 2. The specified file was not created using the ROCLINK 800 software. Solution: 1. Ensure that the project is pointing to the correct import file. 2. Re-create the import file using the ROCLINK 800 software and then re-try the import. Unable to generate a tag database for device ''.
Fisher ROC Serial Driver Help 25 Possible Cause: The import file is corrupt. Solution: In the server project, right-click on the device and then select Properties. Then, open the Tag Import Settings tab to review the settings and check the import file. If necessary, re-export the project file from within ROCLINK800. See Also: Tag Import Settings Automatic Tag Database Generation Unable to generate a tag database for device ''.
Fisher ROC Serial Driver Help 26 The System DB file cannot be found. Solution: Ensure that the System DB file (*.mdw) is present in the location specified in the Tag Import Settings tab of Device Properties. This file must be accessible to the server's Runtime. Device Specific Messages The following error/warning messages may be generated. The messages are listed here in alphabetical order. Device Specific Messages '' - Failed to read EFM pointer file.
Fisher ROC Serial Driver Help 27 Solution: The server will attempt to update the EFM pointer file periodically, in addition to when the server is shutdown. If the pointer file cannot be written, the server will re-poll (uploading all EFM data) during the next EFM poll for meters in the device. Note: For more information, refer to the extended error. Block read for point type , logical address , parameter range of device failed.
Fisher ROC Serial Driver Help 28 Failed to write data for PointType = '', Logical Address = '', Parameter = '' for device ''. Error = '' Error Type: Serious Possible Cause 1. The address is incorrect. 2. The unit does not support the particular address point. 3. The privileges for the logged-in user do not permit this operation. Solution: 1. Consult the ROC error code reference for further information regarding the error code. 2. Correct the address.
Fisher ROC Serial Driver Help 29 See Also: Operator Identification Address Specification ROC initialization error: Unable to retrieve I/O map Error Type: Fatal Possible Cause: Access to the I/O Map has been restricted for the current user. Solution: Check the Operator Identification settings (such as, username, password, and access level) and verify that they are correct. See Also: Operator Identification Serialization of EFM data to temporary file '' failed.
Fisher ROC Serial Driver Help 30 Time synchronization with device '' failed. Error Type: Serious Possible Cause: The error occurred due to the specified Error Reason. Solution: The solution depends on the specified Error Reason. See Also: Error Reasons Write for the following tags of device failed: . Error Type: Serious Possible Cause: The error occurred due to the specified Error Reason.
Fisher ROC Serial Driver Help 31 2. The communication parameters for the serial connection are incorrect. 3. The response from the device took longer to receive than the amount of time specified in the "Request Timeout" device setting. Solution: 1. Verify the cabling between the PC and the device. 2. Verify that the specified communication parameters match those of the device. 3. Increase the Request Timeout setting so that the entire response can be handled.
Fisher ROC Serial Driver Help 32 COMn does not exist Error Type: Fatal Possible Cause: The specified COM port is not present on the target computer. Solution: Verify that the proper COM port has been selected in the Channel Properties. COMn is in use by another application Error Type: Fatal Possible Cause: The serial port assigned to a device is being used by another application. Solution: Verify that the correct port has been assigned to the channel.
Fisher ROC Serial Driver Help 33 Block read for point type '', logical address '', parameter range '' of device '' failed. Parameters are not in the loaded UDP configuration Error Type: Serious Possible Cause: The user program that is associated with the specified parameters has been upgraded to a newer version. Solution: Reinitialize the server in order to gain access to the new parameters available in the upgraded user program.
Fisher ROC Serial Driver Help 34 Solution: The solution depends on the specified Error Reason. See Also: Error Reasons ROC Error Codes Error Codes Returned by Opcode 255 Opcode 255 is an error message indicator that returns an error code. FlashPACs, FloBoss 500-Series, FloBoss 100-Series and RegFlo Models Error Code Description 1 Invalid Opcode request. 2 Invalid Parameter Number. 3 Invalid Logical Number / Point Number. 4 Invalid Point Type. 5 Received too many data bytes.
Fisher ROC Serial Driver Help 35 103 Received less than 4 data bytes. 104 Point type out of range (1-24 are valid). 105 Point does not exist, or invalid parameter. 106 Not enough data bytes received. www. kepware.
Fisher ROC Serial Driver Help 36 Index ' '' - Failed to read EFM pointer file. 26 '' - Failed to write EFM pointer file.
Fisher ROC Serial Driver Help 37 Data Types Description 13 Device '' responded with error. (Tag '') - Details: '' 27 Device address '' contains a syntax error 22 Device address '' is not supported by model '' 22 Device address '' is Read Only 22 Device name '' is not responding 30 Device Setup 7 Device Specific Messages 26 Device Status Messages 30 E EFM '' upload failed for device ''.
Fisher ROC Serial Driver Help 38 O Operator Identification 9 Operator identification failed for device ''. 28 Overview 5 P Point Number Details 18 R Read for point type '', logical address '', parameter number '' of device '' failed. Parameter is not in the loaded UDP configuration 33 Read for point type , logical address , parameter number of device failed.
Fisher ROC Serial Driver Help 39 U Unable to generate a tag database for device ''. Reason: 23 Unable to generate a tag database for device ''. Reason: Auto tag generation failed. Device is not responding 23 Unable to generate a tag database for device ''. Reason: Error while reading from import file 24 Unable to generate a tag database for device ''. Reason: Error while reading from ROC system file 24 Unable to generate a tag database for device ''.
