|
<< Click to Display Table of Contents >> HC900 HCDesigner import of Modbus maps |
![]() ![]()
|
SpecView can import the modbus map file from HCDesigner to define all the blocks and tags from the HC900 into the SpecView Variables list.
There are two types of HCDesigner Modbus Maps for the HC900: 'Fixed Modbus Map' and 'Custom Modbus Map'. SpecView can import both types.
If using a Fixed Modbus Map, then the Control Loops 1-32 will be imported in full and will be represented in SpecView by a 'Loop' Instrument View. This also applies to the SPP blocks 1-8.
For a Custom Map which is based on a Fixed Map, again Control Loops 1-32 are imported in full (as are SPPs 1-8).
For additional Control Loops, the necessary parameters need to be placed in a custom Modbus map partition in HCDesigner. To retain full use of the SpecView Instrument View features it is necessary to include the parameters needed to support the PID interface for the HC900. You may use 'Select All' when adding parameters for Modbus addresses to the partition. This adds all of the PID parameters to the map. You may also use the Loops Template (Vista_PID.ptf) provided with HCDesigner but you will need to also include the 'LSP1' parameter for the local set point. See section below on importing custom loops from HCDesigner.
If all parameters listed for the Loop are not included, the Loop will still have the Instrument View associated with it, but those parameters not included will simply not work on the Instrument View.
For additional custom SPP blocks (numbered 9 and above), only the minimal SpecView Instrument View, which just has a single Parameter button is used. Clicking on this Parameter button allows access to all the parameters of the given block.
This minimal Instrument View is also used for all other HC900 parts (not Loops and SPPs 1-8).
Including a Tag Number as part of the name and help on naming conventions between HCDesigner & SpecView
Notes on updating an HC900 using this import facility