Manual - Serial - Eternity Sales
Contents
1. 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 e Add When clicked this button will invoke the Meter Configuration dialog for adding a new meter to the device e Remove When clicked this button will remove the selected meter from the EFM Meter List e Modify When clicked this button will invoke the Meter Configuration dialog for modifying the selected meter in the EFM Meter List e Move Up When clicked this button will move the selected meter up in the EFM Meter List e Move Down When clicked this button will move the selected meter down in the EFM Meter List Clearing Cached Data Users have the option to clear any cached EFM data from the device during the next upload All device data will be re uploaded To do so open the Device Properties EFM Meters Then click Clear cache on next upload Meter Configuration www kepware com Fisher ROC Serial Driver Help 12 r Meter Configuration Descriptions of the parameters are as follows e Meter Name This parameter specifies the meter name Each meter must be assigned a unique name The default setting is Meter_1 e 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 paramet2. Reason Auto tag generation failed 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 recordset 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 Unable to generate a tag database for device lt device gt Reason System DB file lt file name gt not found Device Specific Messages 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 PointType lt point type gt Logical Address lt address gt Starting Parameter lt starting par
3. Fisher ROC Serial Driver Help 22 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 address in the client application Device address lt address gt is not supported by model lt model name gt Error Type Warning Possible Cause Atag 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 it is 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 Warning 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 Warning Possible Cause A tag address that has been specified statically has no length Solution Re enter the address in
4. 2 eee Se At er sete era dod Ne mater de dant Cae 21 Address Validation 3 sha cane a oh ahs OS ad Soe ha ren atv howd ASR Lee ERA 21 Address lt address gt is out of range for the specified device or register _ 21 Data Type lt type gt is not valid for device address lt address gt 22 Device address lt address gt contains a syntax error 22 Device address lt address gt is not supported by model lt model name gt 22 Device address lt address gt is Read Only 2 22 2222222222222 22 Missing address stne yn 29h 2 2 oA nan eos da Een nant emanated de wins wa en den aly 3 02 ENT 2 22 Automatic Tag Database Generation Error Messages 22 Error importing CSV tag record lt record number gt Address lt Address gt is out of range for the specified device orr gister 6362 Soh dae ins ei Eo ae en edi the OS La le ot ee Oe a sas 23 Unable to generate a tag database for device lt device gt Reason lt Error Reason gt 23 Unable to generate a tag database for device lt device gt Reason Auto tag generation failed Device is NOTTESPONGING hone eS eee na te PR Ue Be tal ne Me MA eae Mas nh Slate Ok eS Me AR 23 Unable to generate a tag database for devi
5. Error 63 29 Time synchronization with device lt device name gt failed lt Error Reason gt 29 Write for the following tags of device lt device name gt failed lt tag list gt lt Error Reason gt 29 Write request rejected on Read Only item reference lt channel name gt lt device name gt lt address gt 29 Device Status Messages 30 Device lt device name gt is not responding 30 EFM lt type gt upload failed for device lt device gt lt Reason gt 30 Resetting the EFM cache for device lt device gt 1 2 0 2 02 2 c cece c eee cece ee cece ee cee eee 30 Serial Communications _ 0 cccccecc cece cece cece ee ceececeeeceeeeceeeeceeeeeeececeeeeeeeeees 30 Communications error on lt channel name gt lt error mask gt 2 31 COMn does not xist 2 A 2o8ed eee se Ose Je cash See Al Res SAS Be gh Se aL eee 31 COMn is in use by another application 2 222 31 Error op ning COM e oh chad We en ees ty dais Set Lit te 31 Unable to set comm parameters on COMn 31 User Defined Point Error Me
6. No 0 y E 25 31 User Defined Ports o No COM1 and COM2 FloBoss 100 Series and FloBoss 500 Series Backward Compatibility LOS ROC Point Types for FloBoss 100 Series FloBoss 407 and FloBoss 500 Series cont 7 FloBoss ypes User Defined Typically Modbus Config for COM1 User Defined Typically Function Config for COM1 User Defined Typically Host Config for COM1 34 135 136 User Defined Typically Modbus Config for LOI and Yes COM2 User Defined Typically Function Config for LOI and Yes COM2 39 i 40 41 142 3 34 35 36 37 38 i 5 a0 a a2 a3 Meter Calibration and Sampler a6 Meter Configuration Parameters ves NoYes a7 Meter Flow Values ves No res 43 Ib Control Parameters ves No res 49 Upload to Disk NO NN 50 Download to ROC No No No 52 Battery Parameters fe fn fs 53 Modbus Configuration Parameters Me fn fs 54 Modbus Function Tables ves NoYes www kepware com Fisher ROC Serial Driver Help 55 Modbus Special Function Table Je JW e id 58 __ Revision Information fe ho Me 60 77 SAM User Defined Parameters fo ho m 80 Enhanced Communication ECM Parameters ves no fmo C S ww 86 Extended History rames fes o m es BiMUsertists fe ho m 89 onart User stearan fe o fn 83 license Key Information Parameters vs o Mm Ba User CProgramParameters fs o o 117 Modbus Configuration Parameters
7. 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 PC is 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 Check the cabling between the PC and the device 2 Verify that the specified communication parameters match those of the device See Also www kepware com Fisher ROC Serial Driver Help Device Setup Failed to obtain data block for PointType 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 Failed to write data for PointType lt point type gt Logical Address lt address gt Parameter lt parameter gt for device lt device gt Error lt error code g
8. 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 Manual aa ROC300 Series ROC300 Description FlashPAC Series ROCPAC fo configurable opcode ier Je E Proportional Integral and Derivative PID conf s tocat Display Panel es es fi Tank Parameters HE Function Sequence Table FST Parameters Soft Ponts Al Calibration No e J Database Setup ROC Tasks Information for User Defined Points User Defined Points 32 User Defined Typically Modem Config for COM1 User Defined Typically Modem Config for LOI and COM2 User Defined Typically Modbus Config for COM1 ROC Point Types for ROC300 Series cont Point ROC300 ROC300 Tunes Description Series Series YP FlashPAC ROCPAC 39 User Defined Typically Host Config for com es es 30 Pult Variable Sensor HVS rames peoo fo o 41 AGA Run Parameters Yes CS I aa Power Control V Nd 5 E A i 0 Download torse dN id Added via a user program ROC Point Types for FloBoss 100 Series FloBoss 407 and FloBoss 500 Series Point Types www kepware com Fisher ROC Serial Driver Help JS ries 407 Series 500 Series fo____ Configurable opcode fe JO Efron Paramees ef e Cid 20 ROC Tasks No Yes Diagnostics Yes No Information for User Defined Points 22 23 User Defined Points
9. 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 s 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 www kepware com 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 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 PointType lt point type gt Logical Address lt address gt Starting Parameter l
10. fe o Mm 118 Modbus Register Mapping Parameters fe o Mm 120 Modbus Master Modem Configuration vs o Mm 121 Modbus Master Polling Table Configuration Yes Parameters DS800 Configuration Parameters FloBoss 100 Series and FloBoss 500 Series Backward Compatibility ROC Point Types for RegFlo o Configurable opcode 7 Soton O o y EE EE EE CE Bo Regulator Parameters Logic Alarm Parameters Analog Outputs History Parameters 81 System Flags 84 User Discrete Values Communication Ports 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 ROC protocol for point types 1 to 5 are based on a physical input or output 1 0 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 e 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
11. port is working and configured properly at the channel level in the server 3 Check the device level Operator Identification and Address Specification settings and verify that they are correct 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 lt file name gt failed Reason lt file I O error gt Error Type Warning Possible Cause 1 The driver was unable to create the specified file directory 2 The driver 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 www kepware com 2 Fisher ROC Serial Driver Help See Also Operator Identification The username or password supplied was not accepted Error 63 Error Type Fatal Possible Cau
12. tag database for device lt device gt Reason Error while reading from ROC system file 24 Unable to generate a tag database for device lt device gt Reason Failed to open recordset 24 Unable to generate a tag database for device lt device gt Reason Import file lt file name gt not found 24 Unable to generate a tag database for device lt device gt Reason Input file is corrupt 24 Unable to generate a tag database for device lt device gt Reason Input file not found 25 Unable to generate a tag database for device lt device gt Reason Low memory resources 25 Unable to generate a tag database for device lt device gt Reason ROC system file lt file name gt not found 25 Unable to generate a tag database for device lt device gt Reason System DB file lt file name gt not found 25 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 32 Unable to parse the User Defined Point configuration information for point type lt point type gt on device lt device name gt 32 Unable to set comm parameters on COMn 31 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
13. 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 Verify the serial parameters and make any necessary changes www kepware com Fisher ROC Serial Driver Help 32 User Defined Point Error Messages The following error warning messages may be generated The messages are listed here in alphabetical order User Defined Point Error Messages 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 0 Unable to parse the User Defined Point confi
14. 33 User Defined Point Error Messages 32 User Defined Point Types 19 W Write for the following tags of device lt device name gt failed lt tag list gt lt Error Reason gt 29 Write request rejected on Read Only item reference lt channel name gt lt device name gt lt address gt 29 www kepware com
15. Display description Fons d oiire moat select e men ie p ca lt Back Net gt Cancel Descriptions of the parameters are as follows www kepware com Fisher ROC Serial Driver Help 8 e 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 e Online From Device This method automatically creates tags by polling the device for its configuration and I O data e Offline From Import File This method automatically creates tags from a project file created in ROCLINK 800 e Use legacy tag names When checked Automatic Tag Database Generation will generate tags with names that are consistent with the tags created in prior versions of the server When unchecked Automatic Tag Database Generation will generate tags with names that are 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 e Tag import file When pressed this button invokes a dialog for locating the 800 file that was created using the ROCLINK800 software e 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
16. Fisher ROC Serial Driver Help 2014 Kepware Technologies 2 Fisher ROC Serial Driver Help Table of Contents Table of Contents ox ocd ek a seen eae SOE Ail ante elena Aaah DAAE A AE EE AR a Seen ts 2 Fisher ROC Serial Driver Help _ 2 220 222 cece cece ee een eee e eee e cece eee eeeececeeeeee 5 OVERVIOW ois ees ccs orale E tides Sele ER ea A i EB tee ES SE tit 5 Channel Se tup iio oo laced rreri Agnus M hand bea PAR nee MR RE URL Or ee ddd deed ere gs 6 Device Setup yaso er en EOE LALOR LEE AOE OAL ohh is SUB 7 Tag Import Settings seteia peste ae ns cae eee chee de ele ae nee in 7 Address Specification LD ADADA L Lanan 8 Operator Identification crans aa a e a Ae A AO Be ee 9 EFM E Ti E EE OE EEI ENEAN IEEE EINN 10 Data Types Description cece raorao ceeeeeeeeeees 13 Automatic Tag Database Generation 2222 14 Address Descriptions eee 15 ROG Pointily pes E E N es Meee cael es od aoe i ts a ae hide ad 15 Logical Point Number Details 18 User Defined Point Types 19 Bit Assignments cc 19 Error Descriptions 2 2 2 2 2 2 c cece cece cece ccc c ence cece cece ceeeeeeeeeeeceeeeeeeeeettetetttstrees 20 Eiron Reasons
17. 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 TCP requests that use Explicit Congestion Notification ECN In order to communicate with these devices the global TCP IP ECN parameter must be disabled Note This driver does not support Report by Exception 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 then select Properties Tag Import Settings New Device Tag Import Settings se of offline import select the corresponding file paths Import method Online from Device 7 Use legacy tag names Offine Settings Tag impor file el comen System DBfile L F
18. ROCPACs and FloBoss 407 Models Read Errors 8 More than 250 data bytes in response 19s Invalid parameter One of the following conditions occurred 1 Did not receive 4 data bytes 2 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 35 Fisher ROC Serial Driver Help Index A Address lt address gt is out of range for the specified device or register 21 Address Descriptions 15 Address Specification 8 Address Validation 21 Automatic Tag Database Generation 14 Automatic Tag Database Generation Error Messages 22 B Bit Assignments 19 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 32 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 26 Cc Channel Setup 6 Communications error on lt channel name gt lt error mask gt 31 COMn does not exist 31 COMn is in use by another application 31 D Data Type lt type gt is not valid for device address lt address gt 22 Data Types Description 13 Device
19. The number of parameters for this point is 0 Error Type Serious 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 www kepware com 33 Fisher ROC Serial Driver Help 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 lt Error Reason gt 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 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 3 Invalid Logical Number Point Number S Received toomany data byes o e Recevettoo few des o C SSCS 5 Didnotreceive 3databyte SSCS EE oo www kepware com Fisher ROC Serial Driver Help a
20. 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 e Display descriptions When checked this option will include the tag descriptions from the ROCLINK 800 master database Legacy vs Non Legacy Tag Names For information on how legacy and non legacy tag names will be automatically generated based on the Use legacy tag names option refer to the table below Tag Type Mods Taname reg address Non Boolean Legacy IPAddress_137_0 137 0 1 Non Legacy IP Address 137 T137 L0 P1 137 0 1 Boolean Bit Legacy HighAlarm_3_0 3 0 16 2 Non Legacy High Alarm 3 T3 L0 P16 Bit 2 3 0 16 2 See Also Automatic Tag Database Generation Address Specification To view or change these settings after the device has been added right click on the device and then select Properties Address Specification www kepware com 9 Fisher ROC Serial Driver Help New Device Address Specification Specify the destination device address group and source host address group m Destination Device address Device group 240 Descriptions of the parameters are as follows e 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 e Device group This parameter specifies the group number of the r
21. ameter gt Ending Parameter lt ending parameter gt for device lt device gt Error lt ROC error code gt Failed to write data for PointType 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 device 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 Device Status Messages 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 Serial Communications Communications error
22. be 64 through 68 The ROC I O point database would reference these points by rack and module namely E1 to E5 Logical Point Numbers 0 to 127 For all other point types 0 and 6 59 the point number is 0 to x where x is one less than the total number of points that exist for that point type For example the four MVS points in a FloBoss 407 would be logical numbers 0 through 3 Note All parameters are 0 based for each point type www kepware com Fisher ROC Serial Driver Help User Defined Point Types User Defined Points UDP make user program data available to ROCLINK and OPC clients They are generally used for configuration purposes When creating a User Defined Point in the server the server Configuration will always set the data type to Default The data type will later be read live from the device Important Users must reinitialize the server after upgrading the user program on a device otherwise the server will not be able to access the new points available in the upgraded user program 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 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 will occur if the serve
23. ce lt device gt Reason Error while reading from import file 24 Unable to generate a tag database for device lt device gt Reason Error while reading from ROC system dE NE E AE EU POUR Minis EE ET canis Os Bane 24 Unable to generate a tag database for device lt device gt Reason Failed to open recordset 24 Unable to generate a tag database for device lt device gt Reason Import file lt file name gt not found 24 Unable to generate a tag database for device lt device gt Reason Input file is corrupt _ 24 Unable to generate a tag database for device lt device gt Reason Input file not found 25 Unable to generate a tag database for device lt device gt Reason Low memory resources 25 Unable to generate a tag database for device lt device gt Reason ROC system file lt file name gt not 25 www kepware com Fisher ROC Serial Driver Help 3 Unable to generate a tag database for device lt device gt Reason System DB file lt file name gt not found 25 Device Specific Messages eeeee eeececeeceeecec 26 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 26 Device lt device gt responded with error Tag
24. 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 data 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 an easy and 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 www kepware com 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 com Fisher ROC Serial Driver Help Device Setup Supported Devices FloBoss 100 Series FloBoss 407
25. elf is the final authority on whether a datum is writable For more information refer to the controller s documentation Device Status Messages The following error warning messages may be generated The messages are listed here in alphabetical order Device Status Messages 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 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 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
26. emote ROC device The valid range is 1 to 255 The default setting is 240 e Host address This parameter specifies the ROC unit number of the server The valid range is 1 to 255 The default setting is 1 e Host group This parameter specifies the ROC group number of the server The valid range is 1 to 255 The default setting is 1 Operator Identification This dialog is used to specify the operator identification values that will be 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 then select Properties Operator Identification www kepware com Fisher ROC Serial Driver Help 10 New Device Operator Identification ify the Operator Identification Usemame to in to the ROC device password is enabled enter the Password access level is enabled enter the Access Level m Device Login Usemame LOI MN Password M Access Level Descriptions of the parameters are as follows e Username This parameter specifies the username Three characters as set in the device are required e 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 e Access Level When checked this option specifies that the ROC device has defined access level
27. er is set to Selected Meters www kepware com Fisher ROC Serial Driver Help Data Types Description TR 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 String padded with spaces 64 bit floating point value Date Example Date format YYYY MM DDTHH MM SS 000 2000 01 01T12 30 45 000 www kepware com Fisher ROC Serial Driver Help u 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 H Device Properties Redundancy Tag Import Settings Address Specification Operator Identification Time Synchroni
28. guration 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 lt 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 in order to gain access to 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 in order to gain access to 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
29. he 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 s Runtime Unable to generate a tag database for device lt device gt Reason Input file is corrupt Error Type Warning www kepware com 25 Fisher ROC Serial Driver Help 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 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 then select Properties Then open the Tag Import Settings tab to check the name of the project file that will be imported This file must be accessible to the server s 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
30. le 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 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 project is pointing to the correct ROC system file 2 Re install the ROCLINK 800 software in order 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 recordset 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 then select Properties Then open the Tag Import Settings tab to check the name of the project file that will be imported 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 t
31. lt device gt responded with error Tag lt tag address gt Details lt error code gt 26 Device address lt address gt contains a syntax error 22 Device address lt address gt is not supported by model lt model name gt 22 Device address lt address gt is Read Only 22 Device name lt device name gt is not responding 30 Device Setup 7 www kepware com Fisher ROC Serial Driver Help 36 Device Specific Messages 26 Device Status Messages 30 E EFM lt type gt upload failed for device lt device gt lt Reason gt 30 EFM Meters 10 Error Descriptions 20 Error importing CSV tag record lt record number gt Address lt Address gt is out of range for the specified device or register 23 Error opening COMn 31 Error Reasons 21 Failed to obtain data block for PointType 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 27 Failed to write data for PointType lt point type gt Logical Address lt address gt Parameter lt parameter gt for device lt device gt Error lt error code gt 27 H Help Contents 5 M Missing address 22 O Operator Identification 9 Operator identification failed for device lt device name gt lt Error Reason gt 27 Overview 5 www kepware com Fisher ROC Serial Driver Hel
32. lt tag address gt Details lt error code gt 26 Failed to obtain data block for PointType 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 morcode gt 2 mr rt Re ee An Re Re cla ite dig OR ove we Soe bee 27 Failed to write data for PointType lt point type gt Logical Address lt address gt Parameter lt parameter gt for device lt device gt Error lt error code gt 27 Operator identification failed for device lt device name gt lt Error Reason gt 27 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 27 ROC initialization error Unable to read general configuration 28 ROC initialization error Unable to retrieve I O map 28 Serialization of EFM data to temporary file lt file name gt failed Reason lt file I O error gt 28 The username or password supplied was not accepted Error 6 28 The username or password supplied was not accepted
33. ode code Framing error The response packet from the ROC device This error is very rare If encountered has data fields that are not as per the users should check with the protocol manufacturer to ensure that the ROC device is consistent with the protocol Operator The operator identification login with Refer to the Event Log message that identification error User ID and Password failed corresponds to the operator identification failure For more information refer to Device lt device name gt is not responding For more information refer to ROC Error Codes Address Validation The following error warning messages may be generated The messages are listed here in alphabetical order Address Validation 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 www kepware com
34. on lt channel name gt lt error mask gt COMn does not exist www kepware com Fisher ROC Serial Driver Help 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 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 0 Unable to parse the User Defined 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 lt Error Reason gt See Also ROC Error Codes Error Reasons For more information on error reasons refer to the table below Error Reason Possible Cause Solution responding with error c
35. p P Point Number Details 18 R 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 32 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 27 Resetting the EFM cache for device lt device gt 30 ROC Error Codes 33 ROC initialization error Unable to read general configuration 28 ROC initialization error Unable to retrieve I O map 28 ROC Point Types 15 S Serial Communications 30 Serialization of EFM data to temporary file lt file name gt failed Reason lt file I O error gt 28 T Tag Import Settings 7 The username or password supplied was not accepted Error 6 28 The username or password supplied was not accepted Error 63 29 Time synchronization with device lt device name gt failed lt Error Reason gt 29 U Unable to generate a tag database for device lt device gt Reason lt Error Reason gt 23 Unable to generate a tag database for device lt device gt Reason Auto tag generation failed Device is not responding 23 Unable to generate a tag database for device lt device gt Reason Error while reading from www kepware com Fisher ROC Serial Driver Help s import file 24 Unable to generate a
36. r 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 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 7 6 5 4 3 2 1 0 Response Code 1 0 0 0 0 0 0 0 Communication Error E L Parity Error V Parity Error Reserved Overrun Error Buffer Overflow Framing Error Undefined www kepware com Fisher ROC Serial Driver Help 20 Error Descriptions The following error warning messages may be generated The messages are listed here in alphabetical order Address Validation 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 Automatic Tag Database Generation Error Messages Error importing CSV tag record lt 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 gt Unable to generate a tag database for device lt device gt
37. s The valid range is 0 to 5 The default setting is unchecked EFM Meters This dialog is used to add remove and modify EFM Meters The meter order in the EFM Meter List should match the order of the meters in ROCLINK 800 Important 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 www kepware com Fisher ROC Serial Driver Help New Device EFM Meters meter order in the meter list should comespond to order of meters in ROCLINK 800 Non Meter Events FEE Meter Count 0 Name ___ Non Meter Events Add Modify Move Up Descriptions of the parameters are as follows e 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 e Ignore This option will not send non meter events to any meters e Broadcast This option will send non meter events to all meters e Selected Meters This option will only send non meter events to those meters that are enabled to do so e Meter Count This parameter displays the number of meters that have been added to the device e 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
38. se 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 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 Write for the following tags of device lt device name gt failed lt tag list 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 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 a Read Only datum in the ROC controller Solution Do not attempt to write to Read Only points Note In some situations the Automatic Tag Generation process will identify Read Only datum as Read Write based on the configuration that the driver retrieved from the ROC controller and the ROC specification Nonetheless the www kepware com Fisher ROC Serial Driver Help 30 ROC controller its
39. ssages 32 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 32 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 32 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 32 Unable to parse the User Defined Point configuration information for point type lt point type gt on device lt device name gt ccc 32 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 33 www kepware com Fisher ROC Serial Driver Help www kepware com 5 Fisher ROC Serial Driver Help Fisher ROC Serial Driver Help Help version 1 059 CONTENTS Overview What is the Fisher ROC Serial Driver Channel Setup How
40. t 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 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 specified Error Reason See Also Error Reasons 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 www kepware com Fisher ROC Serial Driver Help 28 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 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
41. t 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 PointType 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 device 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 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
42. the server application Automatic Tag Database Generation Error Messages The following error warning messages may be generated The messages are listed here in alphabetical order Automatic Tag Database Generation Error Messages www kepware com 23 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 Unable to generate a tag database for device lt device gt Reason lt Error Reason gt Unable to generate a tag database for device lt device gt Reason Auto tag generation failed 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 recordset 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 Unable
43. the specified device Solution N A Serial Communications The following error warning messages may be generated The messages are listed here in alphabetical order Serial Communications 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 www kepware com Fisher ROC Serial Driver Help Communications error on lt channel name gt lt error mask gt Error Type 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 The serial connection between the device and the Host PC is 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
44. to generate a tag database for device lt device gt Reason System DB file lt file name gt not found 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 Reason 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 www kepware com Fisher ROC Serial Driver Help 24 Unable to generate a tag database for device lt device gt Reason Error while reading from import file Error Type Warning Possible Cause 1 The tag import fi
45. y model and by how the particular unit is equipped Points may be Physical 1 0 or Internal I O Physical I O Points Physical I O points are one of Discrete Inputs type 1 Discrete Outputs type 2 Analog Inputs type 3 Analog Outputs type 4 and Pulse Inputs type 5 The logical address for physical I O points is based on their position in the unit known as Point Number There are four slots for each rack The I O field is not typically fully populated Note Rack and slot are ROC nomenclature however many ROC devices have no physical racks or slots Logical addresses are calculated from the Point Number reference For information on reconciling the Point Number to the Logical Address refer to the table below For example an I O Point with ROCLINK 800 Point Number A5 would be Logical Address 4 An I O Point with ROCLINK 800 Point Number C5 would be Logical Address 36 by the function A B C5 or 15 16 5 36 Internal I O Points Internal I O points consist of PID settings system flags communications parameters and other internal information The internal I O logical address begins at 0 for each point type A ROC unit may have one or several of a given internal point type Each point type has a specific set of parameters ROC drivers have no array types Point Type Tables ROC Point Types for ROC300 Series ROC Point Types for FloBoss 100 Series FloBoss 407 and FloBoss 500 Series www kepware com Fisher ROC Serial
46. zation General Scan Mode Timing Auto Demotion Database Creation Settings S Automatic tag database generation on device startup z Perform the following action on previously generated tags Delete on cete Add generated tags to the following group m MV Allow automatically generated subgroups Note For information on importing tags from a ROCLINK project refer to Tag Import Settings www kepware com Fisher ROC Serial Driver Help Address Descriptions ROC addresses are divided first by Point Type Logical Address and then by Parameter Index within the Point Type The general format is T L P where e T The Point Type e L 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 e Point Type 1 e Logical Address 50 e Parameter 3 e Bit Offset 2 For a detailed listing of all point type parameters access data type length and description refer to the ROC device s ROC Protocol User Manual For more information on ROC addressing select a link from the list below ROC Point Types Logical Point Number Details User Defined Point Types Bit Assignments ROC Point Types The availability of point types varies b
Download Pdf Manuals
Related Search