HelixNet v4.2.7.0 Release Notes
Page 10 of 14
This Document Part No.
399G255
Rev
C
1.8
Upgrade Instructions
Upgrade Process:
1.
Back up the system configuration
2.
Update all HMS-4X and LQ in a Link Group to matching minor (4.
1
.x) firmware versions
3.
Allow the HMS-4X to complete update of its system components and configuration
4.
Load the HXII-BP *.ubifs.gz file into all HMS-4X
Using the CCM browser-based interface with HMS-4X units running v3.0 or higher:
1. Download the two v4.2.7.0 upgrade files (.ccb and .ubifs.gz)
2. Within the CCM browser utility, navigate to
Device
>
General
on the target HMS
3. Select the .ccb upgrade file and click
Upgrade
. Allow the system to update endpoints and system configuration.
4. Select the .ubifs.gz upgrade file and click
Upgrade
. Allow the system to update.
5.
Verify that all HMS are updated to version v4.2.7.0 from within the
General
page (IP on device icon is orange).
Using the front panel menus on HMS-4X units running v1.0* or higher:
1. Download the two v4.2.7.0 upgrade files to a USB Flash Drive (.ccb and .ubifs.gz)
2. Insert the USB Flash Drive into the USB port on the front of the Main Station
3. Press the Menu button on the HMS and navigate to:
Administration
>
Software
>
Upgrade
4. Select the .ccb upgrade file within the 4th display and press the encoder to apply. Allow the system to update.
5. Press the Menu button and navigate to:
Administration
>
Software
>
Upgrade
6. Select the .ubifs.gz upgrade file within the 4th display and press the encoder to apply. Allow the system to update.
7.
Verify that all HMS are updated to version v4.2.7.0
Please Note:
•
Loading the .ccb file upgrades the HMS, any hosted HLI modules and paired HBP, HKB and HRM.
Following firmware upgrade the HMS will upgrade its system configuration during which the HMS
and the CCM may be slow to respond. Allow 5 minutes before power cycling the HMS.
•
HelixNet configurations on HMS are forward compatible and automatically upgraded following
the firmware upgrade. Allow 5-10 minutes following the upgrade before power cycling the HMS
to allow the HMS to process the configuration update. Due to addition of features and ongoing
development, configurations upgraded configuration files are not backwards compatible.
•
To upconvert an older configuration file, the file must be on HMS during a firmware upgrade.
Configuration files should be only be upgraded to the next major version (i.e. 3.x to 4.x etc).
•
System downgrades will reset any configuration to default.
•
Stored HelixNet configuration files are only compatible with the version they were stored on.
For devices running old firmware:
•
HelixNet 1.x endpoints should be stepped to be upgraded to version 2.0 and then onwards to
version 3.1 before upgraded to version 4.x. Reset device to default if issues are encountered.
•
HelixNet 2.0 endpoints - connected over Ethernet - need to be upgraded to version 3.1 before
being upgraded to version 4.x or higher due to internal IP port changes.
