Honeywell HC900 Ethernet Driver Help
Contents
1. 22 Missing address lt LCR ie eee Oh we ele ned Std ah cans hei a tee he ide otis n 22 Device address lt address gt contains a syntax error 2 2 22 23 Address lt address gt is out of range for the specified device or register 23 Device address lt address gt is not supported by model lt model name gt 23 Data Type lt type gt is not valid for device address lt address gt 23 Device address lt address gt is Read Only 002 220i cece eee eens 23 Array size is out of range for address lt address gt 22 23 Array support is not available for the specified address lt address gt 24 Device Status Messages 24 Device lt device name gt is not responding 24 Unable to write to lt address gt on device lt device name gt 24 Device Specific Messages 24 Failure to initiate winsock dil2. 27 Invalid tag type field lt field gt record lt record gt 28 Could not import tag in record lt record gt unknown block name 28 Invalid block name lt name gt field lt field gt record lt record gt could not be coerced 28 Invalid block name lt old name gt field lt field gt record lt record gt changed to lt new gt _ _ 28 INDEX RS RN 30 www kepware com 4 Honeywell HC900 Ethernet Driver Help Honeywell HC900 Ethernet Driver Help Help version 1 022 CONTENTS Overview What is the Honeywell HC900 Ethernet Driver Device Setup How do I configure a device for use with this driver Data Types Description What data types does the Honeywell HC900 Ethernet driver support Automatic Tag Database Generation How can I easily configure tags for the Honeywell HC900 Ethernet driver Address Descriptions How do I reference a data location in a Honeywell HC900 Ethernet device Optimizing Your Honeywell HC900 Ethernet Communications How do I get the best performance from the Honeywell HC900 Ethernet driver Error Descriptions What error messages does the Honeywell HC900 Ethernet driver produce Overview The Honeywell HC900 Ethernet Driver provides an easy and reliable way to connect Honeywell HC900 Ethernet controllers to OPC Client ap
3. 25 Bad address in block x to y on device lt device name gt 2 2 22 25 Bad received length x to y on device lt device name gt 25 Tag Import Specific Messages 2 222222222222 222222 25 www kepware com Honeywell HC900 Ethernet Driver Help 3 Could not read record lt record gt Buffer length exceeded 2 25 No tags imported Unsupported file format 26 Could not parse expected data field lt field gt record lt record gt 26 Invalid decimal address field lt field gt record lt record gt 26 Invalid tag name lt name gt field lt field gt record lt record gt could not be coerced into valid name 26 Invalid tag name lt old name gt field lt field gt record lt record gt changed to lt new name gt 27 Invalid datatype field lt field gt record lt record gt 27 Invalid access field lt field gt record lt record gt 2 2 2 22222 27 Invalid type field lt field gt record lt record gt
4. 1 Edit the specified field to reduce length if possible 2 Edit the file and replace the delimiter 3 Regenerate the file Invalid decimal address field lt field gt record lt record gt Error Type Warning Possible Cause 1 The data in the specified field is not a decimal value possibly due to a file editing error 2 The file is not in one of the supported formats 3 The file is corrupted Solution 1 Edit the file and correct the specified field 2 Regenerate the file See Also Creating Tag Import Files Invalid tag name lt name gt field lt field gt record lt record gt could not be coerced into valid name Error Type Warning Possible Cause The tag name specified in the file is not a valid OPC server tag name and the driver s tag name modification mech anism was unable to create a unique and valid name based on the field Solution www kepware com Honeywell HC900 Ethernet Driver Help Manually create the tag Invalid tag name lt old name gt field lt field gt record lt record gt changed to lt new name gt Error Type Information Possible Cause This is not truly an error Tag names that are valid in the Hybrid Control Designer are not necessary valid in the OPC server The driver created a valid tag name based on the name read from the file Solution N A Invalid datatype field lt field gt record lt record gt Error Type Warning Possible Cause
5. Important In hex the coil or register number is not the same value as the Modbus address given in the Hon eywell documentation It is one greater Example The 127 Th input coil would be addressed as 1127 using decimal addressing or H17F using hexadecimal addressing Internal Registers The default data types are shown in bold Decimal Addressing www kepware com Honeywell HC900 Ethernet Driver Help Honeywell HC900 Ethernet Driver Help 19 Data Type access 3XXXXX 1 65536 Word Short BCD Read Only 3xxxxx bb XXXXX 0 XXXXX 15 Boolean Read Only 3XXXXX 1 65535 Float DWord Long LBCD Read Only Hexadecimal Addressing Data Type Access H3yyyyy 1 10000 Word Short BCD Read Only H3yyyyy c yyyyy O yyyyy F Boolean Read Only H3yyyyy 1 FFFF Float DWord Long LBCD Read Only Note Honeywell documentation often gives the location of parameters in device memory as a 1 based coil or reg ister number in decimal and a 0 based Modbus address in hex The coil or register number is the Modbus address plus 1 For example Honeywell documentation may discuss Variable 1 at holding register 6337 with Modbus address 0x18C0 This may be confusing Users should make sure that the coil or register number is specified when creating tags with this driver instead of the given Modbus address This number may be expressed in decimal as in the Honeywell documentation or in hex Important In hex the coil o
6. 1 OxBF800000 OxBF 0x80 Note If this device property is left unchecked the driver will use the Honeywell default FP B If checked the FP LB format will be used The driver does not currently support the Honeywell FP BB and FP L double register for mats www kepware com Honeywell HC900 Ethernet Driver Help Block Sizes Coil Block Sizes Coils can be read from 8 to 800 points bits at a time Register Block Sizes Registers can be read from 1 to 120 locations words at a time Device Properties General Timing Auto Demotion Settings Blocks Tag Generation Coils 8 800 in multiples of 8 Qutput Coils E Input Coils 32 E Registers 1 120 Internal Registers 2 Holding Reaisters 32 E Cancel Apply Xl Help Given the overhead involved in sending data via TCP IP it is generally advantageous to keep the block size large Reducing the block size may improve performance however if data will be read from non contiguous locations within the device www kepware com 8 Honeywell HC900 Ethernet Driver Help Data Types Description HONTE Boolean Single bit Unsigned 16 bit value bit O is the low bit bit 15 is the high bit Signed 16 bit value bit O is the low bit bit 14 is the high bit bit 15 is the sign bit Unsigned 32 bit value bit O is the low bit bit 31 is the high bit Signed 32 bit value bit O is the low bit bit 30 is th
7. 1 The datatype in the specified field is not one of the types supported by the driver possibly due to a file editing error 2 The file is notin one of the supported formats 3 The file is corrupted Solution 1 Edit the file and change the specified field to a supported datatype Supported types are unsigned 16 signed 16 unsigned 32 signed 32 and Float 32 2 Regenerate the file See Also Creating Tag Import Files Invalid access field lt field gt record lt record gt Error Type Warning Possible Cause 1 The access type in the specified field is not one of the types supported by the driver possible due to a file edit ing error 2 The file is notin one of the supported formats 3 The file is corrupted Solution 1 Edit the file and change the specified field to a supported access types Supported types are R W and R W 2 Regenerate the file See Also Creating Tag Import Files Invalid type field lt field gt record lt record gt Error Type Warning Possible Cause 1 The type in the specified field is not one of the types expected by the driver possible due to a file editing error 2 The file is notin one of the supported formats 3 The file is corrupted Solution www kepware com 28 Honeywell HC900 Ethernet Driver Help 1 Edit the file and change the specified field to a supported type Expected types are Variable and Signal Tag There are many
8. Once a channel has been defined a series of devices must then be defined under that channel Each of these devices represents a single Honeywell HC900 controller from which data will be collected While this approach to defining the application will provide a high level of performance it won t take full advantage of the Honeywell HC900 Ethernet driver or the network An example of how the application may appear when configured using a single channel is shown below E E Each device appears under a single Honeywell z gt HC900 Ethernet channel In this configuration the File Edit View Users Toc driver must move from one device to the next as we Y i i i i i En quickly as possible in order to gather information D ar E 7 il SS at an effective rate As more devices are added or Honeywell_1 more information is requested from a single IM Station_1 device the overall update rate begins to suffer M Station_2 IT Station_3 IT Station_4 IT Station_5 If the Honeywell HC900 Ethernet driver could only define one single channel then the example shown above would be the only option available however the Honeywell HC900 Ethernet driver can define up to 16 channels Using multiple channels distributes the data collection workload by simultaneously issuing multiple requests to the network An example of how the same application may appear when configured using multiple channels to improve performance is shown below tse Ea
9. The file created can now be used directly by the driver s tag import feature Example Two 1 To create a file describing all of the Signal Tags in use by the controller click Tag Information Signal Tags www kepware com EOS Honeywell HC900 Ethernet Driver Help Export Report x Select a report category to export Controller Recipes Modbus Register Map gt Tag Information Variables Signal Tags and Variables 2 After all selections have been made users will be prompted to specify a file name Note The file created can now be used directly by the driver s tag import feature Example Three 1 To create a file describing all of the tags for an HC900 configuration using the Fixed Modbus Map the default select All Modbus Registers Export Report E xi Select a report category to export Controller Modbus Register Map gt All Modbus Registers 2 Next specify the file name for import Example Four 1 To create a file for all named Modbus partitions using a Custom Modbus Map HC900 ver 4 0 firmware and later select All Modbus Partitions Export Report x Select a report category to export Controller Recipes Modbus Map Partitions gt All Modbus Partitions Summary Function Block Report www kepware com Honeywell HC900 Ethernet Driver Help 2 Next define the file name for import Users may choose to delete partitions that do not contain
10. address gt is out of range for the specified device or register Device address lt address gt is not supported by model lt model name gt Data Type lt type gt is not valid for device address lt address gt Device address lt address gt is Read Only Array size is out of range for address lt address gt Array support is not available for the specified address lt address gt Device Status Messages Device lt device name gt is not responding Unable to write to lt address gt on device lt device name gt Device Specific Messages Failure to initiate winsock dll Bad address in block x to y on device lt device name gt Bad received length x to y on device lt device name gt Tag Import Specific Messages Could not read record lt record gt Buffer length exceeded No tags imported Unsupported file format Could not parse expected data field lt field gt record lt record gt Invalid decimal address field lt field gt record lt record gt Invalid tag name lt name gt field lt field gt record lt record gt could not be coerced into valid name Invalid tag name lt old name gt field lt field gt record lt record gt changed to lt new name gt Invalid datatype field lt field gt record lt record gt Invalid access field lt field gt record lt record gt Invalid type field lt field gt record lt record gt Invalid tag type field lt field gt record lt record
11. other types used for function block data but the driver should not be trying to process these when importing a function block file 2 Regenerate the file See Also Creating Tag Import Files Invalid tag type field lt field gt record lt record gt Error Type Warning Possible Cause 1 The tag type in the specified field is not one of the types expected by the driver possible due to a file editing error 2 The file is notin one of the expected formats 3 The file is corrupted Solution 1 Edit the file and change the specified field to a supported tag type Expected tag types are Digital and Analog 2 Regenerate the file See Also Creating Tag Import Files Could not import tag in record lt record gt unknown block name Error Type Warning Possible Cause The driver read a header that indicated that the file was a Detailed Function Block Report The driver did not find an expected block sub header record Solution Verify that the file is a Detailed Function Block Report and that the block sub headers are present Regenerate the file if needed Invalid block name lt name gt field lt field gt record lt record gt could not be coerced Error Type Warning Possible Cause The tag name specified in the file is not a valid OPC server group name and the driver s tag name modification mechanism was unable to create a unique and valid name based on field Solution Edit the file and modi
12. variables signal tags and Set Point Programmers are used in the project The driver creates a set of tags based on these settings After all parameters have been specified click Apply or OK to begin the tag generation process Device Properties x General Timing Auto Demotion TCP IP Settings Blocks Tag Generation Tag Import ARNING Generated tags may not be valid if Custom Modbus Map is in use in controller Number of loops E Number of variables jo Number of signal tags jo Number of SP Programmers jo Details Cancel Apply Help Number of Loops This parameter is used to enter the number of control loops used in the controller 1 32 Tags for the most important loop parameters are created for each loop The default parameter names are similar to those listed in the HC900 Communications Manual Loops are listed according to their loop number e g Loop_01 in the order www kepware com Honeywell HC900 Ethernet Driver Help entered in the controller configuration For information on how to associate the control loop number with the tag name assigned in the controller configuration refer to Tag Generation Notes Number of Variables This parameter is used to enter the number of Read Write variables used in the controller configuration Var iables are listed by number in the same sequence as in the controller configuration Each variable will have an analog Float and a digital Boolean
13. 00 Ethernet Driver Help N No tags imported Unsupported file format 26 O Optimizing Your Honeywell HC Ethernet Communications 21 TA K 18 OVervieW bamos cn tects seed eb da des Date Mdr ents a pi dde e Lo Cubic Dae 4 R Register Block Sizes ooooocccccccccccccccccccccccccccccnnnnnnnnnnnnn nn ee eeeeeeeeeeeeeeeeeeeeeeees 7 S S o AE E N E E ERA E E E lal A E E A 6 A RN 8 T Tag Generation cn ccoo ccoo 9 Tag Generation SP Programmer Details 2222 11 LE A O 11 Tag Import Specific Messages 22 25 TCP I cito ld e el er nos 6 U Unable to write to lt address gt on device lt device name gt 24 W A A tt dd eh eMail 8 www kepware com
14. 8 C Coll Block SIZES rennes rm nier ne Aer AR nn SSA nee een Ne nm Aereo 7 Could not import tag in record lt record gt unknown block name 28 Could not parse expected data field lt field gt _ record lt record gt 26 Could not read record lt record gt Buffer length exceeded 25 Creating Tag Import Files 0000002 ccc cece cece cece ccc cece cece cece cee cnc 14 D Data Type lt type gt is not valid for device address lt address gt _ 2 2 22 23 Data Types Description 222005220 ascscsnsddes foae sand tica dan en Res sees 8 Device lt device name gt is not responding 24 Device address lt address gt contains a syntax error 23 Device address lt address gt is not supported by model lt model name gt 23 Device address lt address gt is Read Only 23 Device Setup soo er me re a ae Faas Eas poros a e 5 Device Specific Messages 24 Device Status Messages tua dee See an 2 sia Ye dr 24 DWM asisto llosa tit ann sn eee anse 8 www kepware com Honeywell HC900 Ethernet Driver Help E Error Descriptions o dd Sees a das os Aes 22 F Fail
15. Configuration Upload E Hana Up Modern E Properties Write Protect File amp Print Report Ctrl P Print Report Preview Export Report Printer Setup 1 HC9DOStandardDemo_091203D cde 2 C DOCUME 11 Jupload tmp 3 OrigimalConfiguration cde 4 Config1 from FURNACE1 cde 5 Config1033753640 cde Exit 1 0 Blocks 14 Analog Input JA Analog Out 018 1118 www kepware com Honeywell HC900 Ethernet Driver Help Note Users will be given the option to export Controller FBDs or Recipes data Controller and Recipes data will not be of use to the driver Of the FBDs options only the Summary Function Block Report will not be of use to the driver One or more of the files generated by any of the other FBDs options may be imported Example One 1 To create a file describing the tags used by the various function blocks defined in the controller click Modbus Register Map Detailed Function Block Report Export Report x Select a report category to export Controller b Summary Function Block Report User Defined Signals and Variables 2 Next specify the types of function blocks that will be included in the export file Select Blocks for Exporting Ed IV Loops v Alternators V Sequencers IV Device Controls V SP Programmers IV Hand Off Autos VW SP Schedulers MV Ramps M Stages Cancel 3 Click OK and then specify a file name Note
16. D 1 0R WHT OR WHT 1 TD RD 3 GRN WHT GRN WHT 3 RD BLU BLU 5 BLU WHT BLU WHT 5 10 Basel RD 6 GRN GRN 6 RD BRN WHT BRN WHT BRN 2 o o BRN RJ45 RJ45 12345678 8 pin RJ45 Note When a failure occurs during operation the driver will post error messages www kepware com 6 Honeywell HC900 Ethernet Driver Help TCP IP In order to use this driver TCP IP must be properly installed For information on TCP IP setup refer to the Win dows documentation Port Device Properties x Settings Blocks Tag Generation Tag Import General Timing Auto Demotion TCP IP Port 502 This parameter specifies the TCP IP port number that the remote device is configured to use The default port number is 502 Settings First Word Low in 32 Bit Data Types Float Two consecutive register addresses are used for 32 bit data types such as Floats Users can specify whether the driver should treat the contents of the first register as the low or high word in 32 bit values The HC900 can be configured to use a number of Double Register Formats The formats are as follows Format Description ete order FP B Floating Point Big Endian 4 3 2 1 Honeywell default Modbus standard Examples of Data in FP B Format Value decimal Value hex Register N Register N 1 High Low High Low 100 0 0x42C80000 0x42 0xC8 55 32 0x425D47AE 0x42 0x5D 0x47 OxAE E 0x40000000 0x40 0x3F800000 Ox3F 0x80 0x00 0x00
17. Honeywell HC900 Ethernet Driver Help O 2012 Kepware Technologies 2 Honeywell HC900 Ethernet Driver Help Table of Contents Table of C OHS ur A o 2 Honeywell HC900 Ethernet Driver Help 4 OVEIVIEW 2 5c tr in bent sf LR Te de tetas ale a 4 Device STU Pus sce sc ci tat Gs den a er BN OS SS ah de Ao lal du tte AN a Et a ddr BEN PL 5 TC PIP oa exe Sovareninaden es ache de dE Res A Ie ne See es Res 6 SEINS A E ne NN re a dun Ihc aM des 6 Block SIZES 002 SI AAA we deed ce 7 Data Types Description nc n nr 8 Automatic Tag Database Generation 22 9 Tag Generation tes on ne coed ah wt eme annee ota done 9 Tag Generation SP Programmer Details 11 Tag MPO tesco es Le ane ttt ri eee 11 Addilimport File ss 20 de a de ad da dl at e von EE 13 Creating Tag Import Files xed esses cee hice Seen Ei ta eE cda 14 Address Descriptions 18 Output Coils serca ala tea ct eee les a ere tee anit 6 chil 18 input COINS so ae O E ee 18 Internal Register a dl e En eo dede doo de de 18 Holding Registers ccoo ct A a 2e fans MON iia 19 Optimizing Your Honeywell HC900 Ethernet Communications 21 Error Descriptions ccoo ce de e e re do cat Die eae et ed a A en eds ot 22 Address Validation
18. ain Floating point data Likewise a tag addressing register 6338 as a Float would not be useful either since variables are mapped to registers 6337 6339 6341 and etc These are starting addresses Each value uses two registers For information on the correct starting address and data type for each parameter refer to the device doc umentation Variables and Signal Tags Depending on the device configuration variables and signal tags can be used for either analog or digital data If the data type is a digital Float the actual data stored in the device will be in IEEE Floating point format TRUE ON will be stored as 1 0 and FALSE OFF will be stored as 0 0 Users may read and write to any of these locations using tags with a data type of Float Many client applications however will not be able to handle digital values rep resented as Floats because TRUE is typically coerced into a Float value of 1 0 In this case tags that address dig ital variables and signals with a data type of Boolean should be created The driver will automatically convert these values to and from true Booleans Likewise digital Words and DWords are stored in the device as Words and DWords respectively although they may be addressed with a data type of Boolean TRUE ON will be stored as 1 and FALSE OFF will be stored as 0 In this case tags that address digital variables and signals with a data type of Boolean should be created The driver will automatically convert thes
19. as the tags in the controller See Also Tag Import Tag Generation SP Programmer Details At least two groups of tags Parameters and Additional Parameters will be generated for each set point pro grammer specified in the Tag Generation Device Properties dialogs In addition the driver may be configured to create groups of tags for each set point programmer segment used in the controller configuration To do so click on the Details button on the Tag Generation dialog in order to show the number segments configured for each set point programmer Then double click on a programmer row to edit O to 50 segments may be specified for each set point programmer Set Point Programmer Details x Programmer Segments 2 0 Tag Import The Honeywell HC900 Ethernet driver can automatically create tags in the OPC server through either Tag Import or Tag Generation Tag Import involves importing tags that have been defined in a Hybrid Control Designer appli cation version 2 1 or later Itis the preferred method because it only imports the tags defined in the controller and no others Tag Generation creates a set of tags based on a general description of the controller s con figuration For more information refer to Tag Generation The Tag Import Device Properties dialog is first used to specify a list of files from which tags will be imported After the tag import file list has been specified click Apply or OK to start the tag generati
20. ch device has now been defined under its own channel In this new configuration a single path of File Edit View Users Toc execution is dedicated to the task of gathering data a En Y from each device If the application has 16 or fewer O a El 2 im aa devices it can be optimized exactly how it is shown Honeywell_1 here m Station_1 The performance will improve even if the appli E GP Honeywell_2 cation has more than 16 devices While 16 or fewer Im Station_2 devices may be ideal the application will still ben ge Honeywell 3 efit from additional channels Although by spread m Station 3 ing the device load across all channels will cause 7 the server to move from device to device again it 2 4 Honeywell_4 can now do so with far less devices to process on a IM Station_4 single channel E gp Honeywell_5 Im Station_5 Block Size which is available on each defined device can also affect the Honeywell HC900 Ethernet driver s per formance Block Size refers to the number of bytes that may be requested from a device at one time To refine the performance of this driver may be configured to 1 to 120 registers and 8 to 800 bits www kepware com 22 Honeywell HC900 Ethernet Driver Help Error Descriptions The following error warning messages may be generated Click on the link for a description of the message Address Validation Missing address Device address lt address gt contains a syntax error Address lt
21. decimal and a 0 based Modbus address in hex The coil or register number is the Modbus address plus 1 For example Honeywell documentation may discuss Variable 1 at holding register 6337 with Modbus address 0x18C0 This may be confusing Users should make sure that the coil or register number is specified when creating tags with this driver instead of the given Modbus address This number may be expressed in decimal as in the Honeywell documentation or in hex Important In hex the coil or register number is not the same value as the Modbus address given in the Hon eywell documentation It is one greater Example The 255 th output coil would be addressed as 0255 using decimal addressing or HOFF using hexadecimal addressing Address Data Type 1Xxxxx 1 65536 Boolean Read Only Hexadecimal Addressing Address Data Type HI 110000 Read Only Note Honeywell documentation often gives the location of parameters in device memory as a 1 based coil or reg ister number in decimal and a 0 based Modbus address in hex The coil or register number is the Modbus address plus 1 For example Honeywell documentation may discuss Variable 1 at holding register 6337 with Modbus address 0x18C0 This may be confusing Users should make sure that the coil or register number is specified when creating tags with this driver instead of the given Modbus address This number may be expressed in decimal as in the Honeywell documentation or in hex
22. e high bit bit 31 is the sign bit Two byte packed BCD Value range is 0 9999 Behavior is undefined for values beyond this range Four byte packed BCD Value range is 0 99999999 Behavior is undefined for values beyond this range 32 bit Floating point value The driver interprets two consecutive registers as a Floating point value by making the second register the high word and the first reg ister the low word If register 40001 is specified as a Float bit O of register 40001 would be bit O of the 32 bit word and bit 15 of register 40002 would be bit 31 of the 32 bit word www kepware com Honeywell HC900 Ethernet Driver Help 9 Automatic Tag Database Generation The Honeywell HC900 Ethernet driver can create tags for the application automatically either individually or in combination The preferred method is Tag Import wherein the driver reads controller configuration data from one or more CSV files exported by the Honeywell Hybrid Control Designer application version 2 1 or later Users receive the exact set of tags that are being used by the controller Alternatively the driver s Automatic Tag Data base Generation feature offers the Tag Generation method wherein the driver is given a general description of the controller s configuration such as the number of loops and set point programmers used and then generates a set of tags based on that description Users may add or subtract tags manually after the tag generation ope
23. e 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 loca tions for the device Solution Verify that the address is correct if itis not re enter it in the client application Device address lt address gt is not supported by model lt model name gt Error Type Warning 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 Verify that the address is correct if itis not re enter it in the client application Also verify that the selected model name for the device is correct 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 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 client application Array size is out of range for address lt address gt Error Type Warning www kepware com 24 Honeywell HC900 Ethernet Drive
24. e values to and from true Booleans For more information on Boolean to data type conversion refer to the table below Data Type in Driver Data Type on Controller Boolean Float 4xxxx1 DF Boolean Word 4xxxx1 DW Boolean DWord 4xxxx1 DDW Note These are legacy projects Arrays Arrays are also supported for the holding register addresses The syntax for declaring an array using decimal addressing is as follows 4xxxx cols with assumed row count of 1 and 4xxxx rows cols For Word Short and BCD arrays the base address rows cols 1 cannot exceed 65536 For Float DWord Long and Long BCD arrays the base address rows cols 2 1 cannot exceed 65535 For all arrays the total number of registers being requested cannot exceed the holding register block size that was specified for this device www kepware com Honeywell HC900 Ethernet Driver Help 21 Optimizing Your Honeywell HC900 Ethernet Communications The Honeywell HC900 Ethernet driver has been designed to provide the best performance with the least amount of impact on the system s overall performance While the Honeywell HC900 Ethernet driver is fast there are a cou ple of guidelines that can be used in order to control and optimize the application and gain maximum per formance Our server refers to communications protocols like Honeywell HC900 Ethernet as a channel Each channel defined in the application represents a separate path of execution in the server
25. fy the tag name in the block subheader Invalid block name lt old name gt field lt field gt record lt record gt changed to lt new gt Error Type Information Possible Cause This is not truly an error Tag names that are valid in the Hybrid Control Designer are not necessary valid in the OPC server The driver created a valid group name based on the name read from the file Solution N A www kepware com Honeywell HC900 Ethernet Driver Help 2 www kepware com sw Honeywell HC900 Ethernet Driver Help Index A Add Import File 2 222 2 22 c ccc cc cece cece cece conc 13 Address lt address gt is out of range for the specified device or register 23 Address Descriptions 18 Address Validation 25 22 28 222 ist se cet dei ent reed eee 22 Array size is out of range for address lt address gt 23 Array support is not available for the specified address lt addressS gt ooo 24 Automatic Tag Database Generation 9 B Bad address in block x to y on device lt device name gt 25 Bad received length x to y on device lt device name gt 25 BED o E E a o e dal e 8 OIA AAA A E RS ER 7 Boolean dd ti DR ES aara aE net se sacs oe
26. gt Could not import tag in record lt record gt unknown block name Invalid block name lt name gt field lt field gt record lt record gt could not be coerced into valid group name Invalid block name lt old name gt field lt field gt record lt record gt changed to lt new name gt Address Validation The following error warning messages may be generated Click on the link for a description of the message Address Validation Missing address Device address lt address gt contains a syntax error Address lt address gt is out of range for the specified device or register Device address lt address gt is not supported by model lt model name gt Data Type lt type gt is not valid for device address lt address gt Device address lt address gt is Read Only Array size is out of range for address lt address gt Array support is not available for the specified address lt address gt Missing address Error Type Warning Possible Cause A tag address that has been specified statically has no length Solution Re enter the address in the client application www kepware com Honeywell HC900 Ethernet Driver Help 23 Device address lt address gt contains a syntax error Error Type Warning Possible Cause An invalid tag address has been specified in a dynamic request Solution Re enter the address in the client application Address lt address gt is out of range for th
27. igital and analog data types Users do not need to specify ahead of time what type of data each tag will be accessing Instead they only need to configure the client application to use the appropriate version of the tag Users may also delete any unused tags from the server they are of no con sequence as long as the client does not use them 3 All tags generated by this driver are given generic names To help associate the tags generated by this driver with the tags configured in the controller it is recommended that two reports be printed from the Honeywell Hybrid Control Designer application relative to the controller configuration To do so click File Print Report Preview and then select FBDs e For information on variables and signal tags select Tag Information The Tag Generation Wizard will list the variables and signal tags in the same numerical order as documented e For information about loop order and SP programmer order select the Block Modbus Addresses report The Tag Generation Wizard will list the loops and SP programmers in the same numerical order as doc umented Note Users should record the associated tag names for these blocks www kepware com Honeywell HC900 Ethernet Driver Help 11 4 If Hybrid Control Designer version 2 1 or later is being used the Tag Import method may be preferable because it only imports the tags defined in the project Additionally the imported tags will have the same or sim ilar names
28. meters including those specific to the current segment and programmer start hold advance and reset e Additional Parameters This group contains other setup parameters plus the current program number the program save request that assigns a set of parameters previously written to the programmer block to a stored profile number and the auxiliary output status if used e Segment Specific Parameters These groups are specific to each segment for profile setup Note For more information on using these parameters for program monitoring and profile setup refer to the HC900 Communications User Manual Tag Generation Notes 1 Depending on the device s configuration variables and signal tags can be used for either analog or digital data In either case the actual data stored in the device will be in IEEE Floating point format For digital data TRUE ON will be stored as 1 0 and FALSE OFF will be stored as 0 0 Users may read and write to any of these loca tions using tags with a data type of Float however many client applications will not be able to handle digital values represented as Floats This is because TRUE is typically coerced into a Float value of 1 0 The driver will automatically do the required conversion to or from a true Boolean if the tag is created with the Boolean data type 2 Each variable or signal tag is created with two listings with different tag names ending in B for Boolean or F for Float thus representing the d
29. on parameters match those of the device 3 Verify that the Network ID given to the named device matches that of the actual device 4 Increase the Request Timeout setting so that the entire response can be handled Unable to write to lt address gt on device lt device name gt Error Type Serious Possible Cause 1 The named device may not be connected to the network 2 The named device may have been assigned an incorrect Network ID 3 The named device is not responding to write requests 4 The address does not exist in the PLC Solution 1 Check the PLC network connections 2 Verify that the Network ID given to the named device matches that of the actual device Device Specific Messages The following error warning messages may be generated Click on the link for a description of the message Device Specific Messages Failure to initiate winsock dll www kepware com Honeywell HC900 Ethernet Driver Help 25 Bad address in block x to y on device lt device name gt Bad received length x to y on device lt device name gt Failure to initiate winsock dll Error Type Fatal Possible Cause Could not negotiate with the operating systems winsock 1 1 functionality Solution Verify that the winsock dll is properly installed on the system Bad address in block x to y on device lt device name gt Error Type Fatal addresses falling in this block Cause This error is reported when the d
30. on process 6 Note Alternatively users can press the Regenerate button Y www kepware com Honeywell HC900 Ethernet Driver Help Device Properties D xj General Timing Auto Demotion TCP IP Settings Blocks Tag Generation Tag Import Tag import files __ Add Remove Options S Cancel Apply Help Add This button is used to add a tag import file to the list For more information refer to Add Import File Remove This button is used to remove the selected tag import file from the list Options This button is used to display additional options in the Tag Import Options dialog Regenerate If changes are made to Tag Import Files Tag Import Options or Tag Generation the driver will automatically regenerate tags upon the selection of OK Apply or Regenerate This button will force the tags to regenerate even if there have not been any changes made to the settings Note If the configuration is not connected to the Runtime or if there are no files in the Tag Import Files list this button will be disabled Add Import File x Tag import file Bk OK Enhanced Cancel te Help Display Descriptions When checked this parameter specifies that the tag descriptions defined in the Hybrid Control Designer be used as the tag descriptions in the OPC server Descriptions for OPC server tags are limited to 64 characters and will be truncated if necessary Tag Naming This parameter i
31. ore information refer to Variables and Signal Tags Note Honeywell documentation often gives the location of parameters in device memory as a 1 based coil or reg ister number in decimal and a 0 based Modbus address in hex The coil or register number is the Modbus address plus 1 For example Honeywell documentation may discuss Variable 1 at holding register 6337 with www kepware com Honeywell HC900 Ethernet Driver Help Modbus address 0x18C0 This may be confusing Users should make sure that the coil or register number is specified when creating tags with this driver instead of the given Modbus address This number may be expressed in decimal as in the Honeywell documentation or in hex Important In hex the coil or register number is not the same value as the Modbus address given in the Hon eywell documentation It is one greater Tag Addressing and Data Type Assignment Since this driver is derived from the Modbus Ethernet driver it allows tremendous flexibility in addressing and data type assignment No effort is made to restrict address and data type options to reflect the complexities of the data mapping in Honeywell HC900 devices Thus it is possible to configure tags that will not access data stored in the device correctly For example users could create a tag addressing register 6337 with a data type of word Such a tag would not be useful here since this is the starting address of Variable 1 and will always cont
32. parameter listing For information on how to select the appropriate type as well as how to associate the variable number with that assigned in the controller configuration refer to Tag Gen eration Notes Number of Signal Tags This parameter is used to enter the number of Read Only signal tags used in the controller configuration Signal tags are listed by number in the same sequence as in the controller configuration Each signal tag will have an analog Float and a digital Boolean parameter listing For information on how to select the appropriate type as well as how to associate the signal tag number with that assigned in the controller configuration refer to Tag Generation Notes Number of SP Programmers This parameter is used to enter the number of SP programmers used in the controller 1 8 For information on how to associate the set point programmer number with the tag name assigned in the controller configuration refer to Tag Generation Notes Details This button invokes the Set Point Programmer Details dialog which may be used to specify additional tag gen eration parameters that are specific to each set point programmer For more information refer to Tag Gen eration SP Programmer Details Tags for each set point programmer are categorized into three groups Parameters Additional Parameters and Segment Specific Parameters Descriptions are as follows e Parameters This group contains the current programmer status para
33. pertinent tags or that are empty They may also select individual partitions for import Note Signal tag and variable data may be interpreted analog values or digital values For example for digital Float value 0 0 for FALSE OFF or 1 0 for TRUE ON for digital Word or DWord 0 for FALSE OFF or 1 for TRUE ON The driver will automatically assign the appropriate data type of Float for analog values and Boolean for digital values using the data in the Tag Information export file s It will also perform any necessary data type con versions during Runtime Boolean to data type conversions are not performed for user defined signal tags and variables For more information refer to Holding Registers Important The driver uses the header records in each import file to determine its content Do not modify these headers www kepware com Address Descriptions Address specifications vary depending on the model in use Select a link from the following list to obtain specific address information for the model of interest Output Coils Input Coils Internal Registers Holding Registers Output Coils The default data type is shown in bold Decimal Addressing Address 0XXXXX 1 65536 Boolean Read Write 9 3 a 0 U 9 or y T 0 Hexadecimal Addressing Address Data Type HOyyyyy 1 10000 Boolean Read Write Note Honeywell documentation often gives the location of parameters in device memory as a 1 based coil or reg ister number in
34. plications including HMI SCADA Historian MES ERP and countless custom appli cations It is intended for use with Honeywell HC900 Hybrid Controllers and similar devices www kepware com Honeywell HC900 Ethernet Driver Help 5 Device Setup Supported Devices HC900 Hybrid Controller Communication Protocol Modbus Ethernet using Winsock V1 1 or higher Connection Timeout This parameter specifies the time that the driver will wait for a connection to be made with a device Depending on network load the connect time may vary with each connection attempt The default setting is 3 seconds The valid range is 1 to 60 seconds Request Timeout This parameter specifies the time that the driver will wait on a response from the device before giving up and going on to the next request Longer timeouts only affect performance if a device is not responding The default setting is 1000 milliseconds The valid range is 50 to 30000 milliseconds Retry Attempts This parameter specifies the number of times the driver will retry a message before giving up and going on to the next message The default setting is 3 retries The valid range is 1 to 10 Device ID PLC Network Address The Device ID is used to specify the device IP in standard YYY YYY YYY YYY format Maximum Number of Channels and Devices The maximum number of supported channels is 16 The maximum number of supported devices is 8192 Cable Diagrams Patch Cable Straight Through T
35. r ation is completed The driver may be configured to use Automatic Tag Database Generation either through the New Device Wizard or an existing device object s Device Properties dialog Users can acess tag import and generation settings through the correct property tab The driver creates the tags upon completion of the Device Wizard or once OK or Apply is pressed in Device Properties The driver will place messages in the server s event log as the tag gen eration process proceeds See Also Tag Import and Tag Generation Tag Generation The Honeywell HC900 Ethernet driver has the ability to automatically create tags in the OPC server by using either Tag Generation or Tag Import Tag Generation creates a set of tags that is based on a general description of the controller s configuration Tag Import involves importing tags that have been defined in a Hybrid Control Designer application version 2 1 or later For more information refer to Tag Import Note The driver will generate tags assuming the Universal Modbus Map is in use in the controller Newer ver sions of the HC900 may use the Custom Modbus Map where various control parameters can be mapped to user defined Modbus Partitions The driver assumes the Universal Modbus Map is in use by default Therefore if the controller uses the Custom Modbus Map it is recommended that Tag Import be utilized instead The Tag Generation Device Properties dialog is used to specify how many loops
36. r Help Possible Cause A tag address that has been specified statically is requesting an array size that is too large for the address type or block size of the driver Solution Re enter the address in the client application to specify a smaller value for the array or a different starting point Array support is not available for the specified address lt address gt Error Type Warning Possible Cause A tag address that has been specified statically contains an array reference for an address type that doesn t sup port arrays Solution Re enter the address in the client application to remove the array reference or correct the address type Device Status Messages The following error warning messages may be generated Click on the link for a description of the message Device Status Messages Device lt device name gt is not responding Unable to write to lt address gt on device lt device name 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 broken 2 The communication parameters for the connection are incorrect 3 The named device may have been assigned an incorrect Network ID 4 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 communicati
37. r register number is not the same value as the Modbus address given in the Hon eywell documentation It is one greater Arrays Arrays are also supported for the holding register addresses The syntax for declaring an array using decimal addressing is as follows 3xxxx cols with assumed row count of 1 and 3xxxx rows cols For Word Short and BCD arrays the base address rows cols 1 cannot exceed 65536 For Float DWord Long and Long BCD arrays the base address rows cols 2 1 cannot exceed 65535 For all arrays the total number of registers being requested cannot exceed the internal register block size that was specified for the device Holding Registers The default data types are shown in bold Decimal Addressing Data Type Access 4XXXXX 1 65536 Word Short BCD Read Write 4xxxxx bb XXXXX 0 XXXXX 15 Boolean Read Write 4xxxxx DF 1 65536 Boolean Float Read Only 4xxxxx DW 1 65536 Boolean Word Read Only 4xxxxx DDW 1 65536 Boolean DWord Read Only AXXXXX 1 65535 Float DWord Long LBCD Read Write For more information refer to Variables and Signal Tags Hexadecimal Addressing Range Data Type Access H4yyyyy 1 10000 Word Short BCD Read Write H4yyyyy c yyyyy O yyyyy F Boolean Read Write H4yyyyy DF 1 10000 Boolean Float Read Only H4yyyyy DW 1 10000 Boolean Word Read Only H4yyyyy DDW 1 10000 Boolean DWord Read Only H4yyyyy 1 FFFF Float DWord Long LBCD Read Write For m
38. river attempts to read a location in a PLC that does not exist For example in a PLC that only has holding registers 40001 to 41400 requesting address 41405 would generate this error Once this error is generated the driver will not request the specified block of data from the PLC again Any other addresses being requested that are in this same block will also go invalid Solution The client application should be modified to ask for addresses within the range of the device Bad received length x to y on device lt device name gt Error Type Fatal addresses falling in this block Cause The driver attempted to read a block of memory in the PLC The PLC responded with no error but did not provide the driver with the requested block size of data Solution Ensure that the range of memory exists for the PLC Tag Import Specific Messages The following error warning messages may be generated Click on the link for a description of the message Tag Import Specific Messages Could not read record lt record gt Buffer length exceeded No tags imported Unsupported file format Could not parse expected data field lt field gt record lt record gt Invalid decimal address field lt field gt record lt record gt Invalid tag name lt name gt field lt field gt record lt record gt could not be coerced into valid name Invalid tag name lt old name gt field lt field gt record lt record gt changed to lt new name g
39. s used to specify the tag naming option which will become the default setting for all new devices added thereafter Options include Enhanced or Legacy Descriptions are as follows e Enhanced This option has fewer naming constraints and is consistent with the naming requirements of the current OPC server Tag names cannot have a period double quotes or start with an underscore www kepware com Honeywell HC900 Ethernet Driver Help 13 e Legacy This option enforces the stricter naming requirements of previous versions of this driver Tag names must start with a letter and the name must consist of letters and digits only Note The default setting for existing projects is Legacy Tag Import Notes The Hybrid Control Designer can generate many different types of export files which are only used by this driver and are given as Hybrid Control Designer menu options For more information refer to Creating Tag Import Files 1 FBD Modbus Register Map Detailed Function Block Report 2 FBD Modbus Register Map User Defined Signals and Variables 3 FBD Tag Information Signal Tags 4 FBD Tag Information Variables 5 FBD Tag Information Signal Tags and Variables 6 FBD Modbus Partitions Selected Partition Name Used for Custom Map 7 FBD All Modbus Registers 8 FBD All Modbus Partitions Used for Custom Map Additional Notes 1 Using options 3 5 or 4 5 users can create files with duplicate informa
40. t Invalid datatype field lt field gt record lt record gt Invalid access field lt field gt record lt record gt Invalid type field lt field gt record lt record gt Invalid tag type field lt field gt record lt record gt Could not import tag in record lt record gt unknown block name Invalid block name lt name gt field lt field gt record lt record gt could not be coerced into valid group name Invalid block name lt old name gt field lt field gt record lt record gt changed to lt new name gt Could not read record lt record gt Buffer length exceeded Error Type Warning www kepware com 2 Honeywell HC900 Ethernet Driver Help Possible Cause 1 A record exceeded the maximum allowed length of 1024 characters 2 File may be corrupted Solution 1 Edit tag name and description data to reduce length 2 Regenerate file No tags imported Unsupported file format Error Type Warning Possible Cause The import file is not one of the types the driver is able to read Solution Change the import file type to one that is supported See Also Creating Tag Import Files Could not parse expected data field lt field gt record lt record gt Error Type Warning Possible Cause 1 The field exceed the maximum allowed length of 256 characters 2 The field delimiter comma is missing possibly due to a file editing error 3 The file is corrupted Solution
41. tion If used in the driver s import tag file list this will result in the creation of duplicate tags 2 Option 6 refers to the selection of an individual named partition from a list of all named partitions while option 8 refers to the selection of all named partitions 3 Using 7 any other option will result in duplicate tags 4 The preferred method for importing all tags is a single file Use option 6 for applications utilizing the Fixed Modbus Map default for HC900 If the Custom Modbus Map for Modbus Partitions is utilized in HC Designer use option 7 5 Tags generated from an import operation will be placed in groups For file type 2 the driver will create groups called UserDefinedVariables and UserDefinedSignalTags For file types 3 4 and 5 the driver will create groups called TagInfoVariables and TagInfoSignalTags For file type 1 the driver will create groups based on the block names given in the file For Custom Map partition import the Partition name will be used as a primary group name 6 Aleading underscore in group names will be replaced with an A 7 Tag names may be modified slightly to create valid OPC server tag names Digits may be appended to the end of a tag name to make the name unique Any name changes will be reported in the server s event log A leading underscore in tag names will be replaced with O zero OPC Server Requirements for Valid Tag Names The following is required by the OPC ser
42. ure to initiate winsock dll oo 0 000 cnn cnn cccc cnn nn cnc 25 A A A A O A 8 H Holding Register lancia 2 A A A A oa 18 Holding Registers 11 outra lisos are 19 l INPUECOIS tr a a da AEAEE EAEE de AE 18 Internal Registers 2 9 5 02 8252 a ri dan 18 Invalid access field lt field gt record lt record gt 2 27 Invalid block name lt name gt field lt field gt record lt record gt could not be coerced 28 Invalid block name lt old name gt field lt field gt record lt record gt changed to lt new gt 28 Invalid datatype field lt field gt record lt record gt 27 Invalid decimal address field lt field gt record lt record gt 26 Invalid tag name lt name gt field lt field gt record lt record gt could not be coerced into valid 26 NAMES tenso o a AO O PC NE LL NES Invalid tag name lt old name gt field lt field gt record lt record gt changed to lt new name gt 27 Invalid tag type field lt field gt record lt record gt 28 Invalid type field lt field gt record lt record gt 27 L EBCD AR O a A A IN acetate ee 8 A RR 8 M MISSING address eria a ld Ll 22 www kepware com 32 Honeywell HC9
43. ver for a valid tag name e The tag name cannot start with an underscore_ e Periods double quotes and back slashes are not allowed e The tag name must be no longer than 256 characters e Tags may have the same name as long as they are in different groups Add Import File To add a file to the Tag Import configuration type the full path and filename in the box provided Alternatively click the button to browse to the desired file www kepware com 14 Honeywell HC900 Ethernet Driver Help Tag import file Note For more information on the driver s tag import capability refer to Tag Import Creating Tag Import Files The Honeywell Hybrid Control Designer version 2 1 and later is used to export controller configuration data to Comma Separated Variable CSV format files The files that contain tag information can in turn be imported by this driver For more information on driver configuration refer to Tag Import For instructions on how to create a tag import file refer to the information below 1 To create an export file start the Hybrid Control Designer and then open a configuration file Alternatively upload a controller configuration 2 Next click File Export Report Hybrid Control Designer HC900 C50 Rey 2 0x HC900Stand ER File Edit View Monitor Recipes Window Help C O New Ctrl N gt Open Ctrl O fel Save Ctrl s Save s Ga Download a Upload
Download Pdf Manuals
Related Search