Challenger V8 and Challenger10 firmware (prior to V10-06) use . Challenger10 firmware V10-06 (and later) uses text descriptions instead of text words. Before you migrate a Challenger V8 panel to Challenger10, ChallengerSE, or ChallengerLE hardware, you need to know the Challenger10 firmware version in order to avoid a mismatch of features (which would prevent connection to Titan).Migrating a Challenger V8 panel to Challenger10
Challenger V8 and Challenger10 firmware (prior to V10-06) use text words. Challenger10 firmware V10-06 (and later) uses text descriptions instead of text words. Before you migrate a Challenger V8 panel to Challenger10, ChallengerSE, or ChallengerLE hardware, you need to know the Challenger10 firmware version in order to avoid a mismatch of features (which would prevent connection to Titan).
Note: If you do not know what firmware version has been installed in your Challenger10 hardware (Challenger panel PCB), then we recommend that you use an LCD RAS to check the firmware version number. You will need to connect (at least) RAS 1 and then apply power to the panel to check the Challenger version number via Install menu 11-Version.
After migrating to Challenger10 and connecting to Titan, you can easily upgrade the panel's firmware if needed.
The following is a typical upgrade process via Titan. The overall process to upgrade a Challenger V8 panel to Challenger10 is in two parts:
Part 1: Convert the Challenger record in Titan
Connect Titan to the Challenger V8 panel, and make it the active system.
Upload the Challenger V8 database to Titan to backup the data, if needed.
We recommend that you back up the Challenger V8 panel's data by using the Export function in System Manager.
If the Challenger V8 panel has IP connections to management software, IP Receiver, and so on, record the IP addresses and configuration details for reuse later.
Deactivate the system.
Select Admin > Challenger, and then display the record for the Challenger V8 panel to be migrated. The Type field will have Challenger V8 selected.
Click the Type arrow, select either "Challenger10" or "Challenger10 (pre V10-06)", as applicable to the Challenger10 firmware, and then click Save. Click Yes when asked if you want to continue. When finished, the Type field will have either "Challenger10" or "Challenger10 (pre V10-06)" selected (you cannot convert back to Challenger V8).
If the migration was successful, a message displays: "Successfully migrated. When panel is first set online, Titan will ask you to synchronise the panel with Titan installer database. Note that you need to download users separately. Note that the V8 default alarm groups from 4 to 6 (if used) and alternate user categories (if used) will need to be migrated to V10 manually". Alarm group number 4, 5, and 6 are not applicable to Challenger10.
If the migration was not successful, a message displays: "Error encountered in the migration. Please restore your backup using System Manager".
Part 2: Install hardware and connect to Titan
Power down the Challenger V8 panel, remove all cabling, and replace the PCB with a Challenger10 PCB. Reconnect cabling (most cabling reconnects in the same location as on the V8 PCB).
Repower the Challenger panel. A new (or defaulted) Challenger10 panel is armed, and the RAS LED for area 1 illuminates.
Connect the Challenger10 panel to Titan, and make it the active system (see Connecting to a Challenger10 panel for details).
Note: When the first converted panel is online, Titan displays the message "Titan has detected that one or more Challenger10 panels has not been synchronised after migration. It is strongly recommended that the panels are synchronised to ensure that the programming in Titan matches the programming in the panel. Do you wish to proceed with panel synchronisation?" Select Yes to synchronise. Titan first uploads the comms of the converted panel and then downloads the configuration (except users) from Titan to the panel.
Depending on how the Challenger10 panel is connected to Titan, at least one of the ten communications paths is already programmed. Paths 1, 2, and 3 are preconfigured for CID Dialler, USB Installer, and Management Software (path 3 is enabled). Configure these and other communications paths as needed.
NOTE: When migrating form a non IUM panel check in the management software settings if you have any user offsets. Main Menu > Challenger > System options > User offsets. If you do then remove them.