Difference between revisions of "Exigo Devices Upgrade"
(→Upgrade from Version 1.2 to Exigo 1.3.3.0) |
|||
(48 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
+ | [[File:Exigo_devices.JPG|thumb|right|450px|Example of Exigo Devices]] | ||
+ | This article describes how to upgrade software on Exigo devices. | ||
− | + | All Turbine based Exigo devices use the same software image: | |
+ | * Access Panels | ||
+ | * Amplifiers | ||
+ | * System Controller (SSC) | ||
+ | * TKIE/TKIS kits | ||
+ | * IP Speakers | ||
− | ==Upgrade using the Web Interface== | + | Note that there is a separate upgrade procedure for the [[CRM-V Station Software Upgrade | CRM-V IP Flush Master Station]]. |
+ | |||
+ | {{Note}} Before you start configure the Exigo system it is important that all devices have been updated to the latest software/firmware. <br> Use only software/firmware from the same Exigo package. | ||
+ | |||
+ | == Upgrade from Version 1.2 to Exigo 1.3.3.0 == | ||
+ | '''Precautions when upgrading from Exigo 1.2 to Exigo 1.3.3.0:''' | ||
+ | * '''Upgrade all devices before upgrading ESC1''' | ||
+ | If you have a complete system with a database you should upgrade all endpoints before upgrading [[ESC1]]. <br> | ||
+ | Upgrading [[ESC1]] first may cause trouble because all devices will connect to ESC1 and download their config. <br> | ||
+ | Downloading a Exigo 1.3 config to a device running Exigo 1.2 may cause problems. <br> | ||
+ | It is also possible to disconnect all devices in order to prevent them to download the configuration from ESC1. | ||
+ | |||
+ | * '''First update the bootloader enviroment''' | ||
+ | When upgrading from Exigo 1.2 to Exigo 1.3.3.0 the bootloader needs to be updated first. <br> | ||
+ | This is done by entering the image file prefixed by "boot" in the upgrade prosess. | ||
+ | |||
+ | [[File:Boot update 1.PNG|thumb|left|500px|Update bootloader enviroment]] | ||
+ | <br style="clear:both;" /> | ||
+ | After successfully update of the bootloader, proceed to the normal update procedure. | ||
+ | |||
+ | == Upgrade using the Web Interface == | ||
+ | The Exigo devices can be upgraded via the web interface of the device. | ||
'''Prerequisites''' | '''Prerequisites''' | ||
# A TFTP Server must be available. A TFTP server can be downloaded from here: http://tftpd32.jounin.net/tftpd32_download.html | # A TFTP Server must be available. A TFTP server can be downloaded from here: http://tftpd32.jounin.net/tftpd32_download.html | ||
− | # Download the latest Exigo firmware/software package and unzip the folder. | + | # [[Downloads|Download]] the latest Exigo firmware/software package and unzip the folder. |
− | # Check if your local firewall is not blocking incoming ping/ICMP (Turbine station is pinging TFTP Server during update process). | + | # Check if your local firewall is not blocking incoming ping/ICMP (Turbine station is pinging the TFTP Server during update process). |
'''Upgrade procedure''' | '''Upgrade procedure''' | ||
Line 14: | Line 42: | ||
[[File:TFTP_Server_1.png|thumb|left|500px|TFTP32]] | [[File:TFTP_Server_1.png|thumb|left|500px|TFTP32]] | ||
<br style="clear:both;" /> | <br style="clear:both;" /> | ||
− | * Log on to the | + | * Log on to the '''Exigo device''' web interface. Default login credentials are '''admin''' and '''alphaadmin'''. Select '''Station Administration''' > '''Manual Upgrade''' |
− | * Enter the IP address of the TFTP server ( | + | * Enter the IP address of the TFTP server (i.e. the IP address of your PC) |
− | * Enter the image file: exi-x.x.x.x, and click Save settings | + | * Enter the image file: '''exi-x.x.x.x''', and click '''Save settings''' |
[[File:Turbine_update_1.png|thumb|left|500px|Secondary System Controller - Upgrade web interface]] | [[File:Turbine_update_1.png|thumb|left|500px|Secondary System Controller - Upgrade web interface]] | ||
<br style="clear:both;" /> | <br style="clear:both;" /> | ||
− | The station will now contact the TFTP server and download the files. The upgrade procedure takes about 3 minutes. The process can be monitored by clicking the Log viewer tab in the TFTP server program. | + | The station will now contact the TFTP server and download the files. The upgrade procedure takes about 3 minutes. The process can be monitored by clicking the '''Log viewer''' tab in the TFTP server program. |
− | ==Additional Information== | + | == Upgrade using the VS-IMT Intercom Management Tool == |
− | ===Installing a TFTP server on your PC=== | + | The Exigo devices can be upgraded with the use of the Vingtor-Stentofon Intercom Management Tool. <br> |
+ | The procedure can be found [[VS-IMT Upgrade | here]]. | ||
+ | |||
+ | == Upgrade using Primary System Controller Web Interface == | ||
+ | It is also possible to upgrade attached Exigo devices using the Web Interface on the Primary System Controller.<br> | ||
+ | Go to '''System Maintenance''' > '''IP Station Upgrade'''.<br> | ||
+ | Here you will see a list of the attached devices and the software version: | ||
+ | [[File:IP station upgrade 1.JPG|thumb|left|550px|Primary System Controller - IP Station Upgrade]] | ||
+ | <br style="clear:both;" /> | ||
+ | * For '''TFTP Server''' enter values in the '''IP Address''' and '''Image Name''' fields [[#Upgrade using the Web Interface | (See section above regarding TFTP Server)]], and click '''Save''' | ||
+ | * In the '''IP Stations''' list select the desired devices and click '''Update Station List''' | ||
+ | |||
+ | == Description of the exi-n.n.n.n package == | ||
+ | This software package is valid for the following products, "NAME(devicetree)": | ||
+ | * ENA2200(ena2) | ||
+ | * ENA2400(ena2) | ||
+ | * ESC1(esc) | ||
+ | * EAPIR-8(extended-exigopanel) | ||
+ | * ECPIR-3P(extended-exigopanel) | ||
+ | * ECPIR-P(extended-exigopanel) | ||
+ | * EAPFX-1(ex) | ||
+ | * EAPFX-6(ex) | ||
+ | * EAPII-1(extended-industrial) | ||
+ | * EAPII-6(extended-industrial) | ||
+ | * TKIS-2(compact) | ||
+ | |||
+ | === Alternative Ways of Upgrade === | ||
+ | ==== Alternative 1: Upgrade only devtree & bootloader: ==== | ||
+ | Set image file to "devtreeboot/exi-x-x-x-x" | ||
+ | ==== Alternative 2: Upgrade only devtree ==== | ||
+ | * Set image file to "compact/exi-x-x-x-x" | ||
+ | * Set image file to "extended/exi-x-x-x-x" | ||
+ | * Set image file to "extended-industrial/exi-x-x-x-x" | ||
+ | * Set image file to "extended-exigopanel/exi-x-x-x-x" | ||
+ | * Set image file to "ex/exi-x-x-x-x" | ||
+ | * Set image file to "ena2/exi-x-x-x-x" | ||
+ | * Set image file to "esc1/exi-x-x-x-x" | ||
+ | |||
+ | ==== Alternative 3: Upgrade only bootloader ==== | ||
+ | Set image file to "boot/exi-x-x-x-x" | ||
+ | == Additional Information == | ||
+ | === Installing a TFTP server on your PC === | ||
* Download the TFTP Server program tftpd64 standard edition (installer) from http://tftpd32.jounin.net/tftpd32_download.html. | * Download the TFTP Server program tftpd64 standard edition (installer) from http://tftpd32.jounin.net/tftpd32_download.html. | ||
− | * For 32 bit computers download tftpd32 standard edition (installer) | + | * For 32-bit computers download tftpd32 standard edition (installer) |
− | * Unzip the tftpdxx.yyy.zip file. (e.g. to C: \tftpdxx\) | + | * Unzip the tftpdxx.yyy.zip file. (e.g. to C:\tftpdxx\) |
− | * Run the tftpdxx.exe file. The program is run by selecting the extracted .exe file | + | * Run the tftpdxx.exe file. The program is run by selecting the extracted .exe file (no installation is needed). |
− | * Turn off | + | * Turn off everything except "TFTP Server" under '''Settings''' > '''Global'''. It is escpecially important to turn off "DHCP Server", as this server part of the tftpxx application may interfere with other DHCP servers in the network |
− | * Select the base directory (e.g. C:\Software) by selecting | + | * Select the base directory (e.g. C:\Software) by selecting '''Settings''' > '''TFTP''', then '''Browse''' |
* The TFTP Server program must be running during the software upgrade process | * The TFTP Server program must be running during the software upgrade process | ||
− | ==Troubleshooting== | + | == Troubleshooting == |
− | In | + | In case the upgrade is not successful it may be due to a Windows setting. |
* For Windows XP: http://www.sysprobs.com/enable-ping-in-xp | * For Windows XP: http://www.sysprobs.com/enable-ping-in-xp | ||
* For Windows7: http://www.sysprobs.com/enable-ping-reply-windows-7 | * For Windows7: http://www.sysprobs.com/enable-ping-reply-windows-7 | ||
* For Windows10: http://www.sysprobs.com/enable-ping-reply-and-ftp-traffic-in-windows-10-and-server | * For Windows10: http://www.sysprobs.com/enable-ping-reply-and-ftp-traffic-in-windows-10-and-server | ||
− | |||
− | |||
[[Category:Software upgrade]] | [[Category:Software upgrade]] |
Latest revision as of 09:35, 2 February 2018
This article describes how to upgrade software on Exigo devices.
All Turbine based Exigo devices use the same software image:
- Access Panels
- Amplifiers
- System Controller (SSC)
- TKIE/TKIS kits
- IP Speakers
Note that there is a separate upgrade procedure for the CRM-V IP Flush Master Station.
Before you start configure the Exigo system it is important that all devices have been updated to the latest software/firmware.
Use only software/firmware from the same Exigo package.
Contents
Upgrade from Version 1.2 to Exigo 1.3.3.0
Precautions when upgrading from Exigo 1.2 to Exigo 1.3.3.0:
- Upgrade all devices before upgrading ESC1
If you have a complete system with a database you should upgrade all endpoints before upgrading ESC1.
Upgrading ESC1 first may cause trouble because all devices will connect to ESC1 and download their config.
Downloading a Exigo 1.3 config to a device running Exigo 1.2 may cause problems.
It is also possible to disconnect all devices in order to prevent them to download the configuration from ESC1.
- First update the bootloader enviroment
When upgrading from Exigo 1.2 to Exigo 1.3.3.0 the bootloader needs to be updated first.
This is done by entering the image file prefixed by "boot" in the upgrade prosess.
After successfully update of the bootloader, proceed to the normal update procedure.
Upgrade using the Web Interface
The Exigo devices can be upgraded via the web interface of the device.
Prerequisites
- A TFTP Server must be available. A TFTP server can be downloaded from here: http://tftpd32.jounin.net/tftpd32_download.html
- Download the latest Exigo firmware/software package and unzip the folder.
- Check if your local firewall is not blocking incoming ping/ICMP (Turbine station is pinging the TFTP Server during update process).
Upgrade procedure
- Start the TFTP server program and click Browse, and select the folder where the latest version of exi-x.x.x.x software files are located
- Log on to the Exigo device web interface. Default login credentials are admin and alphaadmin. Select Station Administration > Manual Upgrade
- Enter the IP address of the TFTP server (i.e. the IP address of your PC)
- Enter the image file: exi-x.x.x.x, and click Save settings
The station will now contact the TFTP server and download the files. The upgrade procedure takes about 3 minutes. The process can be monitored by clicking the Log viewer tab in the TFTP server program.
Upgrade using the VS-IMT Intercom Management Tool
The Exigo devices can be upgraded with the use of the Vingtor-Stentofon Intercom Management Tool.
The procedure can be found here.
Upgrade using Primary System Controller Web Interface
It is also possible to upgrade attached Exigo devices using the Web Interface on the Primary System Controller.
Go to System Maintenance > IP Station Upgrade.
Here you will see a list of the attached devices and the software version:
- For TFTP Server enter values in the IP Address and Image Name fields (See section above regarding TFTP Server), and click Save
- In the IP Stations list select the desired devices and click Update Station List
Description of the exi-n.n.n.n package
This software package is valid for the following products, "NAME(devicetree)":
- ENA2200(ena2)
- ENA2400(ena2)
- ESC1(esc)
- EAPIR-8(extended-exigopanel)
- ECPIR-3P(extended-exigopanel)
- ECPIR-P(extended-exigopanel)
- EAPFX-1(ex)
- EAPFX-6(ex)
- EAPII-1(extended-industrial)
- EAPII-6(extended-industrial)
- TKIS-2(compact)
Alternative Ways of Upgrade
Alternative 1: Upgrade only devtree & bootloader:
Set image file to "devtreeboot/exi-x-x-x-x"
Alternative 2: Upgrade only devtree
- Set image file to "compact/exi-x-x-x-x"
- Set image file to "extended/exi-x-x-x-x"
- Set image file to "extended-industrial/exi-x-x-x-x"
- Set image file to "extended-exigopanel/exi-x-x-x-x"
- Set image file to "ex/exi-x-x-x-x"
- Set image file to "ena2/exi-x-x-x-x"
- Set image file to "esc1/exi-x-x-x-x"
Alternative 3: Upgrade only bootloader
Set image file to "boot/exi-x-x-x-x"
Additional Information
Installing a TFTP server on your PC
- Download the TFTP Server program tftpd64 standard edition (installer) from http://tftpd32.jounin.net/tftpd32_download.html.
- For 32-bit computers download tftpd32 standard edition (installer)
- Unzip the tftpdxx.yyy.zip file. (e.g. to C:\tftpdxx\)
- Run the tftpdxx.exe file. The program is run by selecting the extracted .exe file (no installation is needed).
- Turn off everything except "TFTP Server" under Settings > Global. It is escpecially important to turn off "DHCP Server", as this server part of the tftpxx application may interfere with other DHCP servers in the network
- Select the base directory (e.g. C:\Software) by selecting Settings > TFTP, then Browse
- The TFTP Server program must be running during the software upgrade process
Troubleshooting
In case the upgrade is not successful it may be due to a Windows setting.
- For Windows XP: http://www.sysprobs.com/enable-ping-in-xp
- For Windows7: http://www.sysprobs.com/enable-ping-reply-windows-7
- For Windows10: http://www.sysprobs.com/enable-ping-reply-and-ftp-traffic-in-windows-10-and-server