Installation and Starting SpecView > Instrument Definition/Detection > Honeywell HC900 > HC900 HCDesigner import: Notes on Updating an HC900

•	It is stongly advised that a backup (Archive) of the project is made before attempting to update. Although this process has been tested, changes in the future to HCDesigner might mean that the update routine spoils the existing instrument definitions within SpecView.

•	This import facility cannot be used to update an HC900 inside SpecView that was not initially created by this import facility – so, for example, a Specview project auto-detected in SpecView 2.5 build 831 (or older), or an HC900 created manually cannot subsequently be updated by this routine.

•

When Update is selected, a check is made on the HC900 elements already defined in the SpecView project and if there is only one, then the IP address of the HC900 becomes un-editable. If there is more than one HC900, then the address is requested to indicate which HC900 is to be updated. If there is any doubt then cancel and check carefully in the Variables List to see which HC900 needs to be updated.

•

Updating from a Fixed Modbus Map to a Custom Modbus Map (or vice versa) is allowed, but the update routine may create duplicate instruments, especially variables and Tags as these are defined differently in the two types of Map. If variables and/or Tags have already been used on screens from the Fixed Modbus Map file, then keep using those, otherwise start with the new ones for all future tags and variables used on screens inside Specview.

•	If Create Instrument Views on screen is checked, then any newly defined instruments in the new Modbus Map file will be added to the current screen.

•

If instruments or parameters have been renamed during the import, those changes may not be reflected in the labels that may have been placed on any screens, although the actual variables will have the new names. Therefore it may be necessary to edit some labels on screens, or re-create the instrument views if an instrument has been renamed.

•	After import, a summary screen is shown detailing the changes. If this summary indicated items that really should not be altered, then proceed with caution!

•	If an instrument is added where the name specified already exists, then the name will have '_2' (or '_3', '_4', etc.) automatically added making, for example Furnace1-PID_2.

•	If variables or tags are added to an existing project, then they will appear at the end of the variables or signal tags list in V2.5 of SpecView. i.e. they will be out of the usual numerical sequence.

•	Newly added blocks (e.g. more loops) will appear at the end of the Variables List.