Home

Fisher ROC Serial Driver Help

1. Delay Accept 0 milliseconds default or adjust using the up down arrows The range is 0 60000 ms Click Next gt Review the configuration in the Summary wizard step If necessary use the lt Back button to return to previous steps to make changes Click Finish gt See Modem Setup on page 23 www kepware com 12 Fisher ROC Serial Driver Help Device Setup Once at least one channel is configured devices using the Remote Operation Controllers ROC protocol can be added for data collection and monitoring The maximum number of devices supported on any one channel is 255 Devices should be added to channels organized based on the channel configuration Adding a Device To add a new device to a channel 1 In the Project View select the channel to contain the new device 2 Select Click to add a device or right click and choose New Device File Edit View Tools Runtime Help 1S A e J MG lan e ES Channel DER Model ID Des Gm Channel2 aes Click to add a device Ga Fisher_ROC_1 3 In the New Device Name wizard step accept the default channel name or enter a name for the new device a 1to 256 characters length Names can not contain periods double quotations or start with an underscore 4 Click Next gt 5 From the Device Model drop down select the correct model for the device www kepware com Fisher ROC Serial Driver Help 13 NO 10 11 12 13 14 15 16
2. Address lt address gt is out of range for the specified device or register 30 Address Descriptions 25 Address Validation 30 Automatic Demotion 15 Automatic Tag Database Generation 17 Automatic Tag Database Generation Error Messages 31 Bit Assignments 29 Block read for point type lt point type gt logical address lt logical address gt parameter range lt start parameter end parameter gt of device lt device name gt failed lt Error reason gt 36 Block read for point type lt point type gt logical address lt logical address gt parameter range lt start parameter end parameter gt of device lt device name gt failed Parameters are not in the loaded UDP configuration 45 Block read for user table lt table number gt location range lt start location gt lt end location gt of device lt device name gt failed Device returned error code lt error code gt 42 Block read for user table lt table number gt location range lt start location gt lt end location gt of device lt device name gt failed Framing error 42 Block read for user table lt table number gt location range lt start location gt lt end location gt of device lt device name gt failed Locations are not configured in the user table 42 C Channel Setup 6 Communication Specification 21 Communications error on lt channel name gt lt error mask gt 40 COMn does not exist 41 COMn is in use by another application 41 D
3. Data type lt type gt is not valid for device address lt address gt 30 Data Types Description 24 Device lt device gt responded with error Tag lt tag address gt Details lt error code gt 36 www kepware com so Fisher ROC Serial Driver Help Device address lt address gt contains a syntax error 30 Device address lt address gt is not supported by model lt model name gt 31 Device address lt address gt is read only 31 Device name lt device name gt is not responding 40 Device Setup 12 Device Specific Messages 34 Device Status Messages 40 EFM lt type gt upload failed for device lt device gt lt Reason gt 40 EFM Meters 22 Error Descriptions 30 Error importing CSV tag record lt record number gt Address lt Address gt is out of range for the specified device or register 32 Error opening COMn 41 Error parsing user table configuration on device lt device name gt User table lt table number gt contains an invalid point type location or parameter in table location lt location address gt 43 Error parsing user table configuration on device lt device name gt User table lt table number gt contains an invalid user defined point type location or parameter in table location lt location address gt 43 Error Reasons 48 F Failed to obtain data block for PointType lt point type gt Logical Address lt address gt Starting Parameter lt starting parameter gt Ending Parameter
4. History Parameters Logic Alarm Parameters System Flags User Discrete Values Communication Ports 86 Extended History Parameters 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 the 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 s 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 Ai through A10 e 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 T 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
5. Theserial connection between the device and the host PCis bad 2 The communication parameters for the serial connection are incorrect Solution 1 Verify the cabling between the PC and the device 2 Verify that the specified communication parameters match those of the device 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 Error opening COMn Error Type Fatal Possible Cause The specified COM port could not be opened due to an internal hardware or software problem on the target computer Solution Verify that the COM port is functional and may be accessed by other Windows applications Unable to set comm parameters on COMn Error Type Fatal Possible Cause The serial parameters for the specified COM port are not valid Solution www kepware com a2 Fisher ROC Serial Driver Help Verify the serial parameters and make any necessary changes User Configurable Table Messages The following messages may be generated The messages are listed here in alphabetical order Block read for user table lt table number gt locat
6. lt point type gt logical address lt address gt parameter lt parameter gt for device lt device gt Error lt error codes llll aaaa0aiii0 i 000rrrrrrrrrrrnre n21 37 Operator identification failed for device lt device name gt lt Error reason gt 37 Read for point type lt point type gt logical address lt logical address gt parameter number lt parameter number gt of device lt device name gt failed lt Error reason gt 37 ROC initialization error Unable to read general configuration 37 ROC initialization error Unable to retrieve I O map e 38 Serialization of EFM data to temporary file lt file name gt failed Reason lt file I O error gt 38 The username or password supplied was not accepted Error sp 38 The username or password supplied was not accepted Error ze 39 Time synchronization with device lt device name gt failed Error reason gt 39 Write for the following tags of device lt device name gt failed lt tag list gt Error reason gt 39 Write request rejected on read only item reference lt channel name gt lt device name gt lt address gt 39 Device Status Messages ine e ar Rh net eb rR A EE E 40 Device lt device name gt is not responding es 40 EFM lt type gt upload failed for device lt device gt lt Reason gt
7. lt table number gt contains43 www kepware com 4 Fisher ROC Serial Driver Help an invalid point type location or parameter in table location lt location address gt Read for user table lt table number gt location lt location address gt of device lt device name gt failed Device returned error code lt error Code 43 Read for user table lt table number gt location lt location address gt of device lt device name gt failed FraminGg BT EE 43 Read for user table lt table number gt location lt location address gt of device lt device name gt failed Location is not configured in the user table 44 User table configuration upload on device lt device name gt failed Device not responding 44 User table configuration upload on device lt device name gt failed Device responded with error code Lerro code pins te ge Eege Den di e ee sane 44 User table configuration upload on device lt device name gt failed Framing error 44 User table configuration upload on device Sdevice name gt failed Internal error 45 User Defined Point Messages 0000000000000000 0000000000000000 000a a aanraai 45 Block read for point type lt point type gt logical address lt logical address gt parameter range lt start parameter end parameter gt of device lt device name gt failed Parameters are not in the loaded UDP configuratia Aanes ES a a a E EE
8. 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 UDP in the server the server Configuration always sets the data type to default The data type is later read live from the device Important Users must reinitialize the server after upgrading the user program on a device otherwise the server cannot access the new points available in the upgraded user program www kepware com Fisher ROC Serial Driver Help 2 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 e Verify that the point type is within the supported UDP range e Ifa client attempts to write to a UDP type when no UDP type tags have been read since the server started the write may fail with a Type Mismatch error Always complete a read on UDP type tags before a write is attempted e Verify that the point type exists in one of the user programs installed on the device e Check the Event Log for the following error message which occurs if the server fails to parse the UDP configuration Unable to parse the user defined point configuration information for point type lt point type gt on device lt device name gt User Table Points User tables also called Opcod
9. 17 18 19 20 21 22 23 The device you are defining uses a device iver that supports more than one model The below shows all supported models Select a model that best describes the device you are defining Click Next gt In the New Device Scan Mode wizard step configure the Scan Mode Click Next gt In the New Device Timing wizard step configure the Timeouts and Timing Click Next gt In the New Device Auto Demotion wizard step configure how communication failure is handled Click Next gt In the New Device Database Creation wizard step configure Automatic Tag Database Generation Click Next gt In the New Device Time Synchronization wizard step configure timezone DST and synchronization Click Next gt In the New Device Tag Import Settings wizard step identify and locate existing files to be included see Tag Import Settings Click Next gt In the New Device Communication Specification wizard step identify the source and destination addresses see Communication Specification Click Next gt In the New Device Operator Identification wizard step configure the authorized user see Operator Identification Click Next gt In the New Device EFM Meters wizard step add or update the meters for this device see EFM Meters www kepware com 14 Fisher ROC Serial Driver Help 24 Click Next gt 25 Inthe New Device Summary wizard step re
10. 2 2 22 40 Resetting the EFM cache for device lt device gt ee eee see 40 Serial Communications 2222222222222222222 222222222222 40 Communications error on lt channel name gt L errormaskzl e cece e eee eee eee eee 40 COMn does not exis EEN 41 COMn is in use by another application 41 Error opening COM Mes tes coco late he tet ean oy ege EE EA shee ce eR 41 Unable to set comm parameters on COMN 41 User Configurable Table Messages 0000000000000000 0000 000a ooon r222 42 Block read for user table lt table number gt location range lt start location gt lt end location gt of device lt device name gt failed Device returned error code lt error Code 42 Block read for user table lt table number gt location range lt start location gt send location gt of device lt device name gt failed Framing error 2 2 2 2 222222222i iii iii 42 Block read for user table lt table number gt location range lt start location gt Send location gt of device lt device name gt failed Locations are not configured in the user table 2 42 Error parsing user table configuration on device lt device name gt User table lt table number gt contains an invalid user defined point type location or parameter in table location lt location address gt 43 Error parsing user table configuration on device lt device name gt User table
11. lt ending parameter gt for device lt device gt Error lt ROC error code gt 36 Failed to write data for point type lt point type gt logical address lt address gt parameter lt parameter gt for device lt device gt Error lt error code gt 37 H Help Contents 5 Missing address 31 Modem Setup 23 O Operator Identification 22 Operator identification failed for device lt device name gt lt Error reason gt 37 Overview 5 www kepware com Fisher ROC Serial Driver Help 51 P Point Number Details 28 R Read for point type lt point type gt logical address lt logical address gt parameter number lt parameter number gt of device lt device name gt failed lt Error reason gt 37 Read for point type lt point type gt logical address lt logical address gt parameter number lt parameter gt of device lt device name gt failed Parameter is not in the loaded UDP configuration 45 Read for user table lt table number gt location lt location address gt of device lt device name gt failed Device returned error code lt error code gt 43 Read for user table lt table number gt location lt location address gt of device lt device name gt failed Framing error 43 Read for user table lt table number gt location lt location address gt of device lt device name gt failed Location is not configured in the user table 44 Resetting the EFM cache for device lt device gt 40 RO
12. network name or the default None Transactions per cycle Enter the target number or accept 1 default Network Mode Select Priority or Load Balanced default 7 Click Next gt 8 In the New Channel Communications wizard step select None COM Port or Ethernet Encapsulation E Connection type Physical medium None Read processing Ignore Physical medium Select the hardware device type to use for data communications or None for an inactive connection TCP IP 9 Configure communication based on the environment and click Next gt 10 In the New Channel Connection Behavior wizard step select Close connection when idle to reduce traffic and specify the number of seconds before the connection is terminated www kepware com Fisher ROC Serial Driver Help 9 Report communications errors to have any port emors posted to the event log Close connection when idle to force the serial ion to close when not in use The idle interval in can be specified in the edit box below _ Report communications errors 11 Click Next gt 12 Inthe New Channel Write Optimizations wizard step configure channel writes Writing only the latest value can affect batch ing or the equivalent Onlim zation Method Write all values for all tags Write only latest value for non boolean tags White only latest value for all tags writes for every 1 read www kepware com 1
13. point configuration information for point type lt point type gt on device lt device name gt User defined point configuration upload for point type lt point type gt logical address lt logical address gt parameter number lt parameter gt of device lt device name gt failed Error reason gt Block read for point type lt point type gt logical address lt logical address gt parameter range lt start parameter end parameter gt of device lt device name gt 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 to access the new parameters available in the upgraded user program Read for point type lt point type gt logical address lt logical address gt parameter number lt parameter gt of device lt device name gt failed Parameter is not in the loaded UDP configuration Error Type Serious Possible Cause The user program that is associated with this parameter has been upgraded to a newer version Solution Reinitialize the server to access the new parameters available in the upgraded user program Unable to load user defined point configuration for point type lt point type gt logical address lt logical address gt parameter number lt parameter gt of device lt device name gt The number of parameters for this point is 0
14. 0 Fisher ROC Serial Driver Help Optimization Method Accept the default or change the selection by clicking in a radio button e Write all values for all tags most data most network traffic e Write only the latest value for non Boolean tags least data least network traffic e Write only the latest value for all tags key data moderate network traffic Duty Cycle Accept 10 default writes for every 1 read or adjust using the up down arrows The range is 1 10 13 Click Next gt 14 In the New Channel Non Normalized Float Handling wizard step configure how non normalized values will be handled how this driver handles non nomalized floating values Unmodified handling delivers the nomalized value while Replaced with zero changes normalized floating point values to zero Non nomalized values should be Replaced with zero Unmodified Replaced with zero recognizes invalid outliers and eliminates them by replacing the value with integer zero default Unmodified allows values that are potentially invalid outliers into the data stream 15 Click Next gt 16 In the New Channel Inter Device Delay wizard step configure the time in milliseconds between requests to devices www kepware com Fisher ROC Serial Driver Help 11 17 18 19 20 the amount of time in milliseconds the channel ays sending a new request to the next device after iving a response from the last device
15. C Error Codes 47 ROC initialization error Unable to read general configuration 37 ROC initialization error Unable to retrieve I O map 38 ROC Point Types 25 S Scan Mode 14 Serial Communications 40 Serialization of EFM data to temporary file lt file name gt failed Reason lt file I O error gt 38 T Tag Import Settings 19 The username or password supplied was not accepted Error 6 38 The username or password supplied was not accepted Error 63 39 Time Synchronization 18 Time synchronization with device lt device name gt failed lt Error reason gt 39 Timings and Timeouts 15 U Unable to generate a tag database for device lt device gt Reason lt error reason gt 32 Unable to generate a tag database for device lt device gt Reason Auto tag generation failed Device is not responding 32 Unable to generate a tag database for device lt device gt Reason Error while reading from import file 32 Unable to generate a tag database for device lt device gt Reason Error while reading from ROC system file 33 www kepware com 52 Fisher ROC Serial Driver Help Unable to generate a tag database for device lt device gt Reason Failed to open recordset 33 Unable to generate a tag database for device lt device gt Reason Import file lt file name gt not found 33 Unable to generate a tag database for device lt device gt Reason Input file is corrupt 33 Unable to generate a tag database for dev
16. CP requests that use Explicit Congestion Notification ECN To communicate with these devices the global TCP IP ECN parameter must be disabled Note This driver does not support Report by Exception www kepware com 6 Fisher ROC Serial Driver Help Channel Setup 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 The maximum number of supported channels is 256 To create a new channel 1 In the Project View right click and choose New Channel File Edit View Tools Runtime Help 1 al be Crames Devices vj p 7 i ES Channell Channel Name Chi Krees Channel d Channel IA channel name can be from 1 to 256 characters in length Names can not contain periods double quotations or start with an underscore 3 Click Next gt 4 From the Device Driver drop down select Fisher ROC Serial www kepware com Fisher ROC Serial Driver Help 7 the device driver you want to assign to channel list below contains the names of the drivers that are installed on your system 5 Click Next gt 6 In the New Channel Communication Serialization wizard step configure the channel None 1 www kepware com 8 Fisher ROC Serial Driver Help Virtual Network Select the
17. Error Type Serious www kepware com 46 Fisher ROC Serial Driver Help Possible Cause The user program that supports the point type is not installed on the device Solution Verify that the user program that supports the point type is installed on the device Unable to parse the user defined point configuration information for point type lt point type gt on device lt device name gt Error Type Serious Possible Cause There was unexpected data in the UDP configuration read from the device Solution This error requires further troubleshooting Please contact Technical Support User defined point configuration upload for point type lt point type gt logical address lt logical address gt parameter number lt parameter gt of device lt device name gt failed Error reason Error Type Serious Possible Cause The error occurred due to the specified reason Solution The solution depends on the specified error reason See Also Error Reasons www kepware com Fisher ROC Serial Driver Help ROC Error Codes Error Codes Returned by Opcode 255 Opcode 255 is an error message indicator that returns an error code Flash PACS FloBoss 500 Series FloBoss 100 Series and RegFlo Models D Invalid Logical Number PointNumber CS D LBE too many data bytes TT Ve Recewedtoofewdatabytes TT 8 JDid not receive 2 data pyte TT D Did not receive 3 data pyte TT 20 Security error ROCPACs and FloBoss 407 Models R
18. Fisher ROC Serial Driver Help 2015 Kepware Inc 2 Fisher ROC Serial Driver Help Table of Contents Table of Contents 2202 0 0 02 ce eset ee ees 2 Fisher ROC Serial Driver Help 5 OVERVICW ceils ee me ce Anne AES en SE bars Ade coal te 5 Ch nnel Setup i ee he eh OS les yl eene oll 6 Device Setup tse eit es kN ner an sr der 12 ele TEE 14 Timings and Timeouts 2 20 222222 iii 15 Automatic Demotion 15 Automatic Tag Database Generation 17 Time Synchronization 18 Tad IMpOrt Settings Ee Ee ao din tac dd e 19 Communication Specification 21 Operator Identification 22 EEMIMEC NS sd sk et en e Sash een ne 22 Modem Setuprs i EC A Neh eee A ne ee re ee eat 23 Data Types Description 24 Address Descriptions 25 ROG ele 25 Logical Point Number Details 28 User Defined Point Types 28 User Table Points 2222 c2eccit sete Lo Sa ed oh EE 29 BIC ASSIGNINGNES EEE es Ar Pres ART E E 29 Error Descriptions 30 Address Validation shme vi ass ee run ME EE 30 Address lt address gt is out of range for the specified device or register 30 Data type lt type gt is not valid for device address lt address gt 30 Device address lt address gt contains a syntax error 2 2 2 2 222222222222 2222222 30 De
19. For information on how legacy and non legacy tag names are automatically generated based on the Use legacy tag names option refer to the table below pres Type Mode Jaume rares Non Boolean Legacy IPAddress_12_0 12 0 1 Non Legacy IP Address 12 T12 L0 P1 125 1 Boolean Bit Legacy HighAlarm_3_0 Non Legacy High Alarm 3 T3 LO P16 Bit 2 www kepware com 20 Fisher ROC Serial Driver Help See Also Automatic Tag Database Generation www kepware com Fisher ROC Serial Driver Help 21 Communication Specification Communication Specification settings are defined as a device is added and configured through the New Device wizard and can also be modified after the device has been added To define the Communication Specification settings for a new device follow the steps for Adding a Device To modify settings on a defined device select the device right click select Properties and select the Communication Specification tab Destination Device address 240 Device group 240 Source Host address 1 Host group i Read Optimization IT Use OpCode 180 for read requests Descriptions of the parameters are as follovvs s 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 s 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 s Host a
20. S 45 Read for point type lt point type gt logical address lt logical address gt parameter number lt parameter gt of device lt device name gt failed Parameter is not in the loaded UDP configuration 45 Unable to load user defined point configuration for point type lt point type gt logical address lt logical address gt parameter number lt parameter gt of device lt device name gt The number of parameters for ENISHOINE ISO EE 45 Unable to parse the user defined point configuration information for point type lt point type gt on device lt device Names za 4 acs el eS ite i tee ee eas AE 46 User defined point configuration upload for point type lt point type gt logical address lt logical address gt parameter number lt parameter gt of device lt device name gt failed lt Error reason gt 46 ROG Error Codes fests ck ae d eo hae Bee av nae SEELEN 47 Errr REASONS Es sso coun Nate ne t Ee 48 De E EE 49 www kepware com Fisher ROC Serial Driver Help 5 Fisher ROC Serial Driver Help Help version 1 068 CONTENTS Overview What is the Fisher ROC Serial Driver Channel Setup How do I configure channels for use with this driver Device Setup How do I configure a device for use with this driver Data Types Description What data types does this driver support Automatic Tag Database Generation How can tags be automatically created for this driver Address Descriptions How do I address a d
21. Yes Yes Yes es 38 User Defined Typically Function Config for LOI Yes Y and COM2 39 User Defined Typically Host Config for COM1 ys vs o a5 Meter Calibration and Samper ys o a6 Meter Configuration ELE a7 fete mon veus fs o TJ a8 fPD Control Parameters fs fn US Jupioad to disk NO fn so Domare NO fn 52 Battery Perameters LE LE 53 Modbus Configuration Parameters fs o 54 Modbus Function Tables s Mm TJ 55 Modbus Special Function Tabe vs o e 60 77 SAM User Defined Parameters o fn h 0 Enhanced Communication ECM Parameters Yes no o C e T __fw _ www kepware com 28 Fisher ROC Serial Driver Help C EL LE LE LES fes femurs fs fo o 89 Chart User List Parameters fs fo fn id B3 icense Key Information Parameters fs o fn __ sa User Program Paremeters es e h __ 98 Extended Soft Point Parameters ve o o Modbus Configuration Parameters vs m m TJ Modbus Register Mapping Parameters vs m m TJ Modbus Master Modem Configuration KE 121 Modbus Master Polling Table Configuration Parameters 122 DS800 Configuration Parameters FloBoss 100 Series and FloBoss 500 Series Backward Compatibility This point type is only supported by FloBoss 107 ROC Point Types for RegFlo REENEN CECR HE fermes a TJ BP Jiserete Gutputs 5 farGstibretion TI 6 ana imputs 57 Keypad Login Parameters TJ 4 Analog Outputs 80 Regulator Parameters 8
22. alid range is 0 to 5 The default setting is unchecked EFM Meters EFM Meter settings are defined when a device is added and configured through the New Device wizard and can also be modified at any time To define the EFM Meter settings for a new device follow the steps for Adding a Device To modify settings on a defined device select the device right click select Properties and select the EFM Meters tab Important The meter order in the EFM Meter List should match the order of the meters in ROCLINK 800 Only Hourly and Daily History data may be uploaded from the FloBoss 100 Series and RegFlo devices Extended History data is not supported for those devices The meter order in the meter list should corespond to the order of meters in ROCLINK 800 Non Meter Events Broadcast Meter Count 2 E Clear cache on next upload Name Non Meter Events Add 1 Meter 1 Yes 2 Meter 2 Yes Remove Move Up It Move Down www kepware com Fisher ROC Serial Driver Help 23 Descriptions of the parameters are as follows s Non Meter Events This parameter specifies how non meter EFM events are provided to EFM Exporters Options include Ignore Broadcast and Selected Meters The default setting is Broadcast Descriptions of the options are as follows s Ignore This option does not send non meter events for any meters s Broadcast This option sends non meter events for all meters Selected Meters This option only sen
23. ata location on a Fisher ROC Serial device Error Descriptions What error messages does the Fisher ROC Serial Driver produce Overview The Fisher ROC Serial Driver provides a reliable way to connect Fisher ROC Serial controllers to OPC client applications including HMI SCADA Historian MES ERP and countless custom applications Note For more information on available Opcodes Point Types Parameters and Opcode 255 Error Codes refer to the ROC Protocol User Manual Important EFM functionality is not available in all server versions To determine whether support is available refer to the Server Summary Information topic located in the server help file 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 Ethernet Encapsulation This driver supports Ethernet Encapsulation which allows communications with serial devices attached to an Ethernet network using a Serial to Ethernet server It may be enabled through the Communications tab in Channel Properties For more information refer to Channel Properties Ethernet Encapsulation in the server s help documentation Important Some FloBoss 100 Series devices such as FloBoss 107 fail to respond to T
24. bes the file error that occurred Possible Cause 1 The disk is full 2 Apermission error was encountered when the EFM pointer cache was written Solution The server attempts to update the EFM pointer file periodically in addition to when the server is shutdown If the pointer file cannot be written the server re polls uploading all EFM data during the next EFM poll for meters in the device Note For more information refer to the extended error www kepware com 36 Fisher ROC Serial Driver Help Block read for point type lt point type gt logical address lt logical address gt parameter range lt start parameter end parameter gt of device lt device name gt failed lt Error reason gt 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 Device lt device gt responded with error Tag lt tag address gt Details lt error code gt Error Type Serious Possible Cause 1 The connection between the device and the host PCis intermittent 2 The communication parameters for the serial connection are incorrect 3 Value written is out of range or write was performed while in an incorrect setup area Solution 1 Checkthe cabling between the PC and the device 2 Verify that the specified communication parameters match those of the device See Also Device Setup Fa
25. ce lt device gt Reason Input file not found 34 Unable to generate a tag database for device lt device gt Reason Low memory resources 34 Unable to generate a tag database for device lt device gt Reason ROC system file lt file name gt not TA NL en nee 34 Unable to generate a tag database for device lt device gt Reason System DB file lt file name gt not TOUNGS Coe cto bt eset SAS Got tte BOLO EN SETS E SUE A RARE EE 34 Device Specific Messages 222 2222222222 34 lt Device Name gt Failed to read EFM pointer file lt Extended error gt 2 2 222 35 lt Device Name gt Failed to write EFM pointer file lt Extended error gt 2 22 35 Block read for point type lt point type gt logical address lt logical address gt parameter range lt start parameter end parameter gt of device lt device name gt failed SError reason gt 36 Device lt device gt responded with error Tag lt tag address gt Details lt error code gt 36 Failed to obtain data block for point type lt point type gt logical address lt address gt Starting Parameter lt starting parameter gt ending parameter lt ending parameter gt for device lt device gt Error lt ROC error Godo Dis ie tae eS oe EN boned et t OLE Ne te a ga te 36 Failed to write data for point type
26. ce s data points Extra tags may be generated that affect the quality of other generated tags To configure Automatic Tag Database Generation settings locate the Database Creation tab in device properties Device Properties Redundancy Tag Import Settings Address Specification Operator Identification Time Synchronization General Scan Mode Timing Auto Demotion Database Creation Settings Automatic tag database generation on device startup Do not generate on startup OD Perfom the following action on previously generated tags Delete on create Add generated tags to the following group ee M Allow automatically generated subgroups Apply Help Note For information on importing tags from a ROCLINK project refer to Tag Import Settings www kepware com 18 Fisher ROC Serial Driver Help Time Synchronization Time Synchronization settings are defined as a device is added and configured through the New Device wizard and can also be modified after the device has been added To define the Scan Mode for a new device follow the steps for Adding a Device To modify settings on a defined device select the device right click select Properties and select the Time Synchronization tab Device Time Zone UTC 05 00 Eastem Time US amp Canada e IT Respect Daylight Saving Time Synchronization Method Lijez ET Absolute Interval Descriptions of the parameters are as follows Sel
27. d device is not responding Unable to generate a tag database for device lt device gt Reason Error while reading from import file Unable to generate a tag database for device lt device gt Reason Error while reading from ROC system file Unable to generate a tag database for device lt device gt Reason Failed to open record set Unable to generate a tag database for device lt device gt Reason Import file lt file name gt not found Unable to generate a tag database for device lt device gt Reason Input file is corrupt Unable to generate a tag database for device lt device gt Reason Input file not found Unable to generate a tag database for device lt device gt Reason Low memory resources Unable to generate a tag database for device lt device gt Reason ROC system file lt file name gt not found i Unable to generate a tag database for device lt device gt Reason System DB file lt file name gt not found SS www kepware com 32 Fisher ROC Serial Driver Help Error importing CSV tag record lt record number gt Address lt Address gt is out of range for the specified device or register Error Type Warning Possible Cause An imported tag address specifies a location that is beyond the range of supported locations for the device Solution Verify that the address is correct if it is not re enter it in the file being imported Unable to generate a tag database for device lt device gt Reas
28. ddress This parameter specifies the ROC unit number of the server The valid range is 1 to 255 The default settingis 1 s Host group This parameter specifies the ROC group number of the server The valid range is 1 to 255 The default settingis 1 s Use Opcode 180 for read requests This option should be used if few parameters from each point type and logical address are typically used as it yields more efficient communication If unchecked the driver uses Opcode 167 to read entire point type logical addresses in one transaction The default is unchecked www kepware Com 22 Fisher ROC Serial Driver Help Operator Identification This dialog is used to specify the operator identification values used when logging into the ROC device during initialization To view or change these settings after the device has been added right click on the device and select Properties Operator Identification Device Login Usemame LOl Password anne E Access Level Descriptions of the parameters are as follows Username This parameter specifies the authorized account identity Three characters as set in the device are required s 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 Access Level When checked this option specifies that the ROC device has defined access levels The v
29. de See Also ROC Error Codes User table configuration upload on device lt device name gt failed Framing error Error Type Serious Possible Cause There may be an error in the device configuration or the server received a malformed packet Solution Troubleshoot the device configuration www kepware com Fisher ROC Serial Driver Help 45 User table configuration upload on device lt device name gt failed Internal error Error Type Serious Possible Cause Inadequate system resources Solution Free system resources and reinitialize the server If trouble persists please contact Technical Support User Defined Point Messages The following messages may be generated Click on a link for a description of that message Block read for point type lt point type gt logical address lt logical address gt parameter range lt start parameter end parameter gt of device lt device name gt failed Parameters are not in the loaded UDP configuration Read for point type lt point type gt logical address lt logical address gt parameter number lt parameter gt of device lt device name gt failed Parameter is not in the loaded UDP configuration Unable to load user defined point configuration for point type lt point type gt logical address lt logical address gt parameter number lt parameter gt of device lt device name gt The number of parameters for this point is O Unable to parse the user defined
30. ds non meter events for enabled meters Meter Count This parameter displays the number of meters that have been added to the device s EFM Meter List This list view displays the meters that are currently supported by the device including the meter name and Non Meter Event configuration Note The column displays the actual meter number of each configured meter This is the one based meter number that corresponds to the meter numbers the ROCLINK 800 configuration software used to configure ROC devices s Add When clicked this button opens the Meter Configuration dialog for adding a new meter to the device Remove When clicked this button deletes the selected meter from the EFM Meter List s Modify When clicked this button opens the Meter Configuration dialog for updating the selected meter in the EFM Meter List e Move Up When clicked this button changes the order moving the selected meter up in the EFM Meter List e Move Down When clicked this button changes the order moving the selected meter down in the EFM Meter List Clear Cache on Next Upload Users have the option to clear any cached EFM data from the device during the next upload This feature also removes pointer files which are used to track EFM uploads to prevent uploading the same records twice All EFM data is re uploaded Once the cache is cleared this parameter is automatically disabled To enable this option open Device Properties EFM Meters and click Cl
31. e tables provide the ability to map any Point Type parameters to tables in the device This driver has the ability to read and write data points in the user tables using Opcodes 10 and 11 The syntax for user table tags is user_table n m where nis the user table number and mis the data point or location within that table The user table number and location number are zero based For example the first location in the first user table is user_table 0 0 Important Users must increment the version number of the user table when making changes to the table configuration Failure to do so when making changes to the table while the server is actively reading user table tags results in bad quality tags or erroneous data Supported User Table Point Range user_table 0 0 to user_table 15 43 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 Bit T 6 5 H 3 2 1 0 Response Code 1 0 0 0 0 0 0 D Communication Error E L Parity Error V Parity Error Reserved Overrun Error Buffer Overflow Framing Error Undefined www kepware com 30 Fisher ROC Serial Driver Help Error Descriptions The following categories of messages may be generated Click on a link to see a list of related messages Address Validation Automatic Tag Database Generation Device Specific Messages Dev
32. ead Errors 8 JMorethan 250 data bytes in response 9 Invalid parameter One of the following conditions occurred Did not receive 4 data bytes Invalid point type Write Errors Received less than 4 data bytes Point type out of range 1 24 are valid Point does not exist or invalid parameter Not enough data bytes received www kepware com 48 Fisher ROC Serial Driver Help Error Reasons Error Reason Possible Cause Solution JI Device not For more information refer to For more information refer to Device Sdevice name gt responding Device lt device name gt is not is not responding responding Device The ROC device responded with an For more information refer to ROC Error Codes responded error code with error code Framing error The response packet from the ROC This error is very rare If encountered users should device has data fields that are not check with the manufacturer to ensure that the ROC as per the protocol device is consistent with the protocol Operator The operator identification login Refer to the Event Log message that corresponds to the identification with User ID and password operator identification failure error failed www kepware com Fisher ROC Serial Driver Help 4 Index lt lt Device Name gt Failed to read EFM pointer file lt Extended error gt 35 lt Device Name gt Failed to write EFM pointer file lt Extended error gt 35 A
33. ear cache on next upload The default setting is unchecked Meter Configuration Meter Configuration Meter Name Meter_1 e Descriptions of the parameters are as follows Meter Name This parameter specifies the meter name Each meter must be assigned a unique name The default setting is Meter_1 Receive Non Meter Events When checked this option enables the meter to receive non meter events Note This option is only available when the Non Meter Events parameter is set to Selected Meters Modem Setup This driver supports modem functionality For more information please refer to the topic Modem Support in the OPC Server Help documentation www kepware com 2 Fisher ROC Serial Driver Help Data Types Description Data Type Single bit Char Signed 8 bit value bit O is the low bit bit 6 is the high bit bit 7 is the sign bit Byte Unsigned 8 bit value bit O is the low bit bit 7 is the high bit Short Signed 16 bit value bit O is the low bit bit 14 is the high bit bit 15 is the sign bit Word Unsigned 16 bit value bit O is the low bit bit 15 is the high bit DWord Unsigned 32 bit value bit O is the low bit bit 31 is the high bit Float 32 bit floating point value bit O is the low bit bit 31 is the high bit TLP 32 bit value Point type Logical or point number and parameter number use three bytes The top byte is not used A linear group of ASCII characters with preserved whitespace 1 byte pe
34. ecified error reason See Also Error Reasons Operator identification Read for point type lt point type gt logical address lt logical address gt parameter number lt parameter number gt of device lt device name gt failed lt Error reason gt 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 ROC initialization error Unable to read general configuration Error Type Fatal www kepware com 38 Fisher ROC Serial Driver Help Possible Cause The driver may not be receiving a response from the device Solution 1 Make sure the device is physically connected and powered on 2 Check that the COM port is working and configured properly at the channel level in the server 3 Check the device level Operator Identification and Communication Specification settings and verify that they are correct See Also Operator Identification Communication 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 lt file name gt failed Reason lt file I O er
35. ecified user table Error parsing user table configuration on device lt device name gt User table lt table number gt contains an invalid user defined point type location or parameter in table location lt location address gt Error Type Serious Possible Cause There is an error in the device configuration The specified user table is configured with at least one invalid user defined point Solution Configure the specified user table with valid TLP and or UDP entries Error parsing user table configuration on device lt device name gt User table lt table number gt contains an invalid point type location or parameter in table location lt location address gt Error Type Serious Possible Cause There is an error in the device configuration The specified user table is configured with at least one invalid TLP Solution Configure the specified user table with valid TLP entries Read for user table lt table number gt location lt location address gt of device lt device name gt failed Device returned error code lt error code gt Error Type Serious Possible Cause The error occurred for the reason specified by the error code Solution The solution depends on the specified error code See Also ROC Error Codes Read for user table lt table number gt location lt location address gt of device lt device name gt failed Framing error Error Type Serious Possible Cause There may be an
36. ect the time zone in which the device is installed This is used for the data timestamps from the device If the environment servers devices clients adjust for Daylight Saving Time click to enable the option to Respect Daylight Saving Time There are three options for Synchronization Method s Disabled allows device client and server times to be fully independent default Absolute establishes a precise daily time when clocks in the environment servers devices clients are forced to the same time This allows data correlation by timestamp Use the up down buttons to specify if the synchronization time Synchronization Method Tine zom A s Interval establishes a recurring synchronization of the environment clocks every specified number of minutes Synchronization Method Interval mins 60 www kepware com Fisher ROC Serial Driver Help 1 Tag Import Settings Users can create a tag database based on either the device s configuration file or a ROCLINK 800 project file To view or change the Tag Import settings after the device has been added right click on the device and select Properties Tag Import Settings Import method Online from Device dl Use legacy tag names Offline Settings Tag import file ROC system file System DB file Display descriptions Descriptions of the parameters are as follows s Import method This parameter specifies the import method Options include Online fro
37. eouts Timings and Timeouts settings are defined as a device is added and configured through the New Device wizard and can also be modified after the device has been added To define the Timings and Timeout settings for a new device follow the steps for Adding a Device To modify settings on a defined device select the device right click select Properties and select the Timing tab Connect timeout 3 seconds Request timeout 3000 milliseconds Fail after 3 successive timeouts Interrequest delay 0 milliseconds Descriptions of the parameters are as follows s Connect timeout specifies the number of seconds before the server determines the connection has failed The default is 3 seconds Request timeout specifies the number of milliseconds before the server determines the a single poll failed The default is 3000 milliseconds Fail after specifies the number of consecutive attempts are considered a failed connection The default is 3 successive timeouts Inter request delay specifies the number of milliseconds between poll attempts The default is 0 milliseconds Automatic Demotion Automatic Demotion settings are defined as a device is added and configured through the New Device wizard and can also be modified after the device has been added To define the Scan Mode for a new device follow the steps for Adding a Device To modify settings on a defined device select the device right click select Properties a
38. er 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 EFM lt type gt upload failed for device lt device gt lt Reason gt Error Type Warning Possible Cause An EFM upload of the specified type could not be completed due to the specified reason Solution Resolve the issue Then re attempt the EFM upload Resetting the EFM cache for device lt device gt Error Type Informational Possible Cause The EFM cache was successfully cleared for the specified device Solution N A Serial Communications The following error warning messages may be generated The messages are listed here in alphabetical order Communications error on lt channel name gt lt error mask gt COMn does not exist COMn is in use by another application Error opening COMn Unable to set comm parameters on COMn Communications error on lt channel name gt lt error mask gt Error Type www kepware com Fisher ROC Serial Driver Help a Serious Error Mask Definitions B Hardware break detected F Framing error E 1 0 error O Character buffer overrun R RX buffer overrun P Received byte parity error T TX buffer full Possible Cause 1
39. error in the device configuration or the server received a malformed packet Solution Troubleshoot the device configuration www kepware com KE Fisher ROC Serial Driver Help Read for user table lt table number gt location location address gt of device lt device name gt failed Location is not configured in the user table Error Type Serious Possible Cause There is an error in the device configuration The specified user table location is undefined Solution Define the missing table location in the device User table configuration upload on device lt device name gt failed Device not responding Error Type Serious Possible Cause 1 Theconnection between the device and the host PC is intermittent 2 The communication parameters for the Ethernet 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 network 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 User table configuration upload on device lt device name gt failed Device responded with error code lt error code gt Error Type Serious Possible Cause The error occurred for the reason specified by the error code Solution The solution depends on the specified error co
40. ice lt device gt Reason Input file not found 34 Unable to generate a tag database for device lt device gt Reason Low memory resources 34 Unable to generate a tag database for device lt device gt Reason ROC system file lt file name gt not found 34 Unable to generate a tag database for device lt device gt Reason System DB file lt file name gt not found 34 Unable to load user defined point configuration for point type lt point type gt logical address lt logical address gt parameter number lt parameter gt of device lt device name gt The number of parameters for this point is 0 45 Unable to parse the user defined point configuration information for point type lt point type gt on device lt device name gt 46 Unable to set comm parameters on COMn 41 User defined point configuration upload for point type lt point type gt logical address lt logical address gt parameter number lt parameter gt of device lt device name gt failed lt Error reason gt 46 User Defined Point Error Messages 45 User Defined Point Types 28 User Configurable Table Messages 42 User table configuration upload on device lt device name gt failed Device not responding 44 User table configuration upload on device lt device name gt failed Device responded with error code lt error code gt 44 User table configuration upload on device lt device name gt failed Framing error 44 User table configuration upload on device
41. ice Status Messages Serial Communications User Configurable Table Messages User Defined Point Error Messages See Also ROC Error Codes Error Reasons Address Validation The following messages may be generated Click on the link for a description of the message Address lt address gt is out of range for the specified device or register Data Type lt type gt is not valid for device address lt address gt Device address lt address gt contains a syntax error Device address lt address gt is not supported by model lt model name gt Device address lt address gt is read only Missing address Address lt address gt is out of range for the specified device or register Error Type Warning Possible Cause A tag address that has been specified statically references a location that is beyond the range of supported locations for the device Solution Verify that the address is correct if it is not re enter it in the client application Data type lt type gt is not valid for device address lt address gt 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 Device address lt address gt contains a syntax error Error Type Warning Possible Cause A tag address that has been specified statically contains one or more invalid characters Solution Re enter the addre
42. iguration upload on device lt device name gt failed Device responded with error code lt error code gt User table configuration upload on device lt device name gt failed Framing error User table configuration upload on device lt device name gt failed Internal error Block read for user table lt table number gt location range lt start location gt lt end location gt of device lt device name gt failed Device returned error code lt error code gt Error Type Serious Possible Cause The error occurred for the reason specified by the error code Solution The solution depends on the specified error code See Also ROC Error Codes Block read for user table lt table number gt location range lt start location gt lt end location gt of device lt device name gt failed Framing error Error Type Serious Possible Cause There may be an error in the device configuration or the server received a malformed packet Solution Troubleshoot the device configuration Block read for user table lt table number gt location range lt start location gt lt end location gt of device lt device name gt failed Locations are not configured in the user table Error Type Serious www kepware com Fisher ROC Serial Driver Help 43 Possible Cause There is an error in the device configuration At least one location in the specified range is undefined Solution Define missing location s in the sp
43. iled to obtain data block for point type lt point type gt logical address lt address gt Starting Parameter lt starting parameter gt ending parameter lt ending parameter gt for device lt device gt Error lt ROC error code gt Error Type Serious Possible Cause 1 Invalid tag address for point in block 2 Device not responding Solution 1 Verify the cabling between the PC and the device 2 Confirm that all tags within this block exist on the device See Also ROC Error Codes www kepware com Fisher ROC Serial Driver Help Failed to write data for point type lt point type gt logical address lt address gt parameter lt parameter gt for device lt device gt Error lt error code gt 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 Correctthe address 3 Confirm that the address is supported by the controller in use 4 Supply an operator identification with sufficient privileges See Also ROC Error Codes Operator identification failed for device lt device name gt lt Error reason gt Error Type Serious Possible Cause The error occurred due to the specified error reason Solution The solution depends on the sp
44. ion range lt start location gt lt end location gt of device lt device name gt failed Framing error Block read for user table lt table number gt location range lt start location gt lt end location gt of device lt device name gt failed Locations are not configured in the user table Block read for user table lt table number gt location range lt start location gt lt end location gt of device lt device name gt failed Device returned error code lt error code gt Error parsing user table configuration on device lt device name gt User table lt table number gt contains an invalid point type location or parameter in table location lt location address gt Error parsing user table configuration on device lt device name gt User table lt table number gt contains an invalid user defined point type location or parameter in table location lt location address gt Read for user table lt table number gt location lt location address gt of device lt device name gt failed Device returned error code lt error code gt Read for user table lt table number gt location lt location address gt of device lt device name gt failed Framing error Read for user table lt table number gt location lt location address gt of device lt device name gt failed Location is not configured in the user table User table configuration upload on device lt device name gt failed Device not responding User table conf
45. l GEN ROC300 Series ROC300 Description FlashPAC Series ROCPAC DREES 5 Proportional Integral and Derivative PID Control es fes D local Display Panel vs js Gi renkparameters fe js GS AlCalibration fe js ES 32 User penneg Typically Modem contig for COM1 33 user Defined Typically Modem Config for LOT and com yes vs 40___ Multi Variable Sensor MVS Parameters ver o Cd fai AGA Run Parameters es a2 entre Run Parameters es EES Power Gomes TN 9 upload to Disk fe Cd 5o DownfoadtoROC oS e e CE S A Cd 57 Kevpad Login Security parameters e h Y s9 Program Flash Control Parameters es MM Added via a user program ROC Point Types for FloBoss 100 Series FloBoss 407 and FloBoss 500 Series Point Types Description FloBoss FloBoss FloBoss VP P 100 Series 407 Series 500 Series jo Jeonfigurebte opcode Discrete Inputs Discrete Outputs www kepware com Fisher ROC Serial Driver Help Ve pomo Nes frs fs US Historyparametrs res No frs Tee le le Je Diagnostics Yes No 21 Information for User Defined Points v res fre 2223 DECHE KE 32 No COM1 and COM2 i N 34 User Defined Typically Modbus Config for COM1 35 User Defined Typically Function Config for COM1 No No es es es es User Defined Typically Host Config for COM1 37 User Defined Typically Modbus Config for LOI Yes and COM2 N A Yes Yes Yes
46. lt device name gt failed Internal error 45 User Table Points 29 W Write for the following tags of device lt device name gt failed lt tag list gt lt Error reason gt 39 Write request rejected on read only item reference lt channel name gt lt device name gt lt address gt 39 www kepware com
47. m Device and Offline from Import File The default setting is Online from Device Descriptions of the options are as follows s Online From Device This method automatically creates tags by polling the device for its configuration and I O data Offline From Import File This method automatically creates tags from a project file created in ROCLINK 800 s Use legacy tag names When checked Automatic Tag Database Generation creates tags with names consistent with the tags created in prior versions of the server When unchecked Automatic Tag Database Generation creates tags with names consistent with the current version of the server The default setting is checked Note For more information refer to Legacy vs Non Legacy Tag Names below s Tag import file When pressed this button invokes a dialog for locating the 800 file that was created using the ROCLINK800 software ROC system file When pressed this button invokes a dialog for locating the mdb file This file is usually named ROC mdb and resides in the same folder where the ROCLINK 800 software is installed e System DB file When pressed this button invokes a dialog for locating the mdw file This file is usually named ROCLINK mdw and resides in the same folder where the ROCLINK 800 software is installed s Display descriptions When checked this option includes the tag descriptions from the ROCLINK 800 master database Legacy vs Non Legacy Tag Names
48. nd select the Auto Demotion tab You can demote a device for a specific period upon communications failures During this time no read request writes if applicable will be sent to the device Demoting a failed device will prevent stalling communications with other devices on the channel successive failures Demote for 10000 milliseconds E Discard write requests during the demotion period www kepware com 16 Fisher ROC Serial Driver Help Descriptions of the parameters are as follows s Enable auto device demotion on communication failure Allows communication to bypass a non responsive device and attempt data collection from other devices Demote after n successive failures Defines the number of failed attempts at communication before a device is bypassed The default is 3 Demote for n milliseconds Configures the time in milliseconds the demoted device is bypassed to allow other communication to occur Once the delay expires attempts to communicate with the device resume The default is 10000 milliseconds e Discard write requests during the demotion period Allows requests to be removed rather than queued while the device is non responsive and demoted www kepware com Fisher ROC Serial Driver Help Automatic Tag Database Generation This driver supports the server s Automatic Tag Database Generation feature When enabled a list of tags is built within the server that correspond to the devi
49. nsure 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 runtime Device Specific Messages The following error warning messages may be generated The messages are listed here in alphabetical order lt Device name gt Failed to read EFM pointer file lt Extended error gt www kepware com Fisher ROC Serial Driver Help 35 lt Device name gt Failed to write EFM pointer file lt Extended error gt Block read for point type lt point type gt logical address lt logical address gt parameter range lt start parameter end parameter gt of device lt device name gt failed lt Error reason gt Device lt device gt responded with error Tag lt tag address gt Details lt error code gt Failed to obtain data block for point type lt point type gt logical address lt address gt starting parameter lt starting parameter gt ending parameter lt ending parameter gt for device lt device gt Error lt ROC error code gt Failed to write data for point type lt point type gt logical address lt address gt parameter lt parameter gt for device lt device gt Error lt error code gt Operator identification failed for device lt device name gt lt Error reason gt Read for point type lt point type gt logical address lt logical address gt parameter number lt parameter number gt of de
50. og 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 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 26 Fisher ROC Serial Driver Help 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 Manua
51. oject is pointing to the correct ROC system file 2 Re install the ROCLINK 800 software to re install the system file Then re try the import Unable to generate a tag database for device lt device gt Reason Failed to open record set Error Type Warning Possible Cause 1 The project file is corrupt or does not exist 2 The location of the ROC MDB and or ROCLINK MDW files have been specified incorrectly Solution In the server project right click on the device and select Properties Open the Tag Import Settings tab to check the name of the project file to import See Also Tag Import Settings Automatic Tag Database Generation Unable to generate a tag database for device lt device gt Reason Import file lt file name gt not found Error Type Warning Possible Cause The import file cannot be found Solution Ensure that the tag import file 800 is present in the location specified in the Tag Import Settings tab of Device Properties This file must be accessible to the server runtime Unable to generate a tag database for device lt device gt Reason Input file is corrupt Error Type Warning Possible Cause The import file is corrupt Solution In the server project right click on the device and select Properties 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 www kepware com 34 Fishe
52. on lt error reason gt Error Type Warning Possible Cause The error occurred due to the specified error reason Solution The solution depends on the specified error reason See Also Error Reasons Unable to generate a tag database for device lt device gt Reason Auto tag generation failed Device is not responding Error Type Serious Possible Cause 1 The connection between the device and the host PC is intermittent 2 The communication parameters for the serial connection are incorrect Solution 1 Verify the cabling between the PC and the device 2 Verify that the specified communication parameters match those of the device Unable to generate a tag database for device lt device gt Reason Error while reading from import file Error Type Warning Possible Cause 1 Thetag import file 800 is corrupt 2 Thespecified 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 www kepware com Fisher ROC Serial Driver Help 33 Unable to generate a tag database for device lt device gt Reason Error while reading from ROC system file Error Type Warning Possible Cause 1 The ROC system file mdb is corrupt 2 The specified file was not created using the ROCLINK 800 software Solution 1 Ensure that the pr
53. r ROC Serial Driver Help See Also Tag Import Settings Automatic Tag Database Generation Unable to generate a tag database for device lt device gt Reason Input file not found Error Type Warning Possible Cause The import file cannot be found Solution In the server project right click on the device and select Properties Open the Tag Import Settings tab to check the name of the project file to import This file must be accessible to the server runtime See Also Tag Import Settings Automatic Tag Database Generation Unable to generate a tag database for device lt device gt Reason Low memory resources Error Type Warning Possible Cause The memory required for automatic tag generation could not be allocated The process is aborted Solution Close unused applications and or increase the amount of virtual memory and try again Unable to generate a tag database for device lt device gt Reason ROC system file lt file name gt not found Error Type Warning Possible Cause The ROC system file cannot be found Solution Ensure that the ROC system file mdb is present in the location specified in the Tag Import Settings tab of Device Properties This file must be accessible to the server runtime Unable to generate a tag database for device lt device gt Reason System DB file lt file name gt not found Error Type Warning Possible Cause The System DB file cannot be found Solution E
54. r character 64 bit floating point value Date Date format YYYY MM DDTHH MM SS 000 Example 2000 01 01T12 30 45 000 For more information refer to Logical Point Number Details and ROC Point Types www kepware Com Fisher ROC Serial Driver Help 25 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 s T The Point Type e Li The Logical Address e 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 7 L P B where e B The Bit Offset For example the address 1 50 3 2 indicates the following s Point Type 1 s Logical Address 50 s 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 belovv ROC Point Types Logical Point Number Details User Defined Point Types Bit Assignments ROC Point Types The availability of point types varies by model and by how the particular unit is equipped Points may be physical VO 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 Anal
55. ror gt Error Type Warning Possible Cause 1 Thedriver was unable to create the specified file directory 2 Thedriver was unable to access the specified file Solution 1 Verify that the disk has sufficient disk space 2 Verify user permissions for the specified file directory The username or password supplied was not accepted Error 6 Error Type Fatal Possible Cause An access level has been enabled on the device but not in the driver Solution Check the Operator Identification settings and make sure the Enable Access Level checkbox is checked See Also Operator Identification www kepware com Fisher ROC Serial Driver Help 30 The username or password supplied was not accepted Error 63 Error Type Fatal Possible Cause The access level that has been enabled on the device is lower than the operator s access level Solution Check the Operator Identification settings and make sure the operator s access level is less than or equal to the access level enabled in the device See Also Operator Identification Time synchronization with device lt device name gt failed Error reason gt 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 lt device name gt failed lt tag list gt lt Error reason gt Error T
56. ss in the client application www kepware com Fisher ROC Serial Driver Help 31 Device address lt address gt is not supported by model model name gt Error Type VVarning Possible Cause A tag address that has been specified statically references a location that is valid for the communications protocol but not supported by the target device Solution 1 Verify that the address is correct if itis not re enter it in the client application 2 Verify that the selected model name for the device is correct Device address lt address gt is read only Error Type VVarning Possible Cause A tag address that has been specified statically has a requested access mode that is not compatible with what the device supports for that address Solution Change the access mode in the server application Missing address Error Type VVarning Possible Cause A tag address that has been specified statically has no length Solution Re enter the address in the server application Automatic Tag Database Generation Messages The folloving messages may be generated Click on a link for a description of that message Error importing CSV tag record record number gt Address lt address gt is out of range for the specified device or register Unable to generate a tag database for device lt device gt Reason lt Error reason Unable to generate a tag database for device lt device gt Reason Auto tag generation faile
57. vice lt device name gt failed lt Error Reason gt ROC initialization error Unable to read general configuration ROC initialization error Unable to retrieve I O map Serialization of EFM data to temporary file lt file name gt failed Reason lt file I O error gt The username or password supplied was not accepted Error 6 The username or password supplied was not accepted Error 63 Time synchronization with device lt device name gt failed lt Error reason gt Write for the following tags of device lt device name gt failed lt tag list gt lt Error reason gt Write request rejected on read only item reference lt channel name gt lt device name gt lt address gt lt Device Name gt Failed to read EFM pointer file lt Extended error gt Error Type Warning Extended Error When supplied by the operating system this describes the file error that occurred Possible Cause 1 A permission error was encountered when the EFM pointer cache was read 2 The EFM pointer cache file is corrupt Solution The Fisher ROC Serial Driver automatically generates a new EFM pointer file however the server re polls uploading all EFM data during the next EFM poll for meters in the device Note For more information refer to the extended error lt Device Name gt Failed to write EFM pointer file lt Extended error gt Error Type Warning Extended Error When supplied by the operating system this descri
58. vice address lt address gt is not supported by model lt model name gt 31 Device address lt address gt is read only _ 22 2 2 222122222222222222i2eel lili 31 Missing address 2 t Ae Rene SS ere nr A Ce E agit 31 Automatic Tag Database Generation Messages 0000000000000000 1000n 31 Error importing CSV tag record lt record number gt Address lt Address gt is out of range for the Specified device or register ag ue EE Bolt te AN dE AEN nuits 32 Unable to generate a tag database for device lt device gt Reason lt error reason gt 32 Unable to generate a tag database for device lt device gt Reason Auto tag generation failed Device is Notr spondinGd i Abi et SERA ale Me Riz ins monte Bae tee Eau Pire ne eas 32 Unable to generate a tag database for device lt device gt Reason Error while reading from import file 32 Unable to generate a tag database for device lt device gt Reason Error while reading from ROC system WIER 33 Unable to generate a tag database for device lt device gt Reason Failed to open record set 33 Unable to generate a tag database for device lt device gt Reason Import file lt file name gt not found 33 Unable to generate a tag database for device lt device gt Reason Input file is corrupt 33 www kepware com Fisher ROC Serial Driver Help 3 Unable to generate a tag database for devi
59. view the configuration 26 If necessary use the lt Back button to return to previous steps to make changes 27 Click Finish gt Scan Mode Scan Mode settings are defined as a device is added and configured through the New Device wizard and can also be modified after the device has been added To define the Scan Mode settings for a new device follow the steps for Adding a Device To modify settings on a defined device select the device right click select Properties and select the Scan Mode tab Choose the first default option to use the scan rate requested by the client Set a lower limit on the requested rate by choosing the second option Force all tags to scan at the same rate by choosing the third option Disable active scanning by choosing the last option Select if clients are expected to poll this device for data Sean Mode Request data no faster than Request all data at Do not scan demand poll onby Descriptions of the parameters are as follows Respect client specified scan rate uses the polling frequency of the client requesting data default Request data no faster than sets atime in milliseconds to be the maximum frequency of polling Request all data at sets an interval in millisecond when all tag information is collected s Do not scan demand poll only allows a device to be polled by another process www kepware com Fisher ROC Serial Driver Help 15 Timings and Tim
60. ype 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 request rejected on read only item reference lt channel name gt lt device name gt lt address gt Error Type Warning Possible Cause The driver was attempting to write to read only data in the ROC controller Solution Do not attempt to write to read only points Note In some situations the automatic tag generation process identifies read only data as read write based on the configuration that the driver retrieved from the ROC controller and the ROC specification Nonetheless the ROC controller itself is the final authority on whether a point is writable For more information refer to the controller s documentation www kepware com 4 Fisher ROC Serial Driver Help Device Status Messages The following error warning messages may be generated The messages are listed here in alphabetical order Device lt device name gt is not responding EFM lt type gt upload failed for device lt device gt lt Reason gt Resetting the EFM cache for device lt device gt Device lt device name gt is not responding Error Type Serious Possible Cause 1 The connection between the device and the Host PC is intermittent 2 The communication parameters for the serial connection are incorrect 3 The response from the device took long

Fisher ROC Serial Driver Help

Contents

Download Pdf Manuals

Related Search

Related Contents