Astro 25 Mobile Control Head Sync (CH firmware upgrade)

[escomm]

Readme:

===============================================================
Control Head Synchronization file
===============================================================
* ASTRO 25 Mobile CPS MUST be installed before copying this file over*
Control Head Synchronization file (Astro_25_CH_xx.cnv) is used by the
'Synchronize Control Head with Radio' feature in the ASTRO 25 Mobile CPS.
This feature can be found under CPS Menu Bar -> 'Tools' menu.
The 'Synchronize Control Head with Radio feature updates the software in the
attached control head (s) to match with the software in the radio.
Warning: Only use this feature when the control head powers-up in
'Maintenance Mode'.
The Control Head Synchronization file contains all of the software versions for the Control Head and a new version is released every time a new radio software version is available.
Please make sure to copy this file in the 'Upgrade' folder of the
ASTRO 25 Mobile CPS directory. For example, if the ASTRO 25 Mobile CPS
is installed in the default directory, then there already exists a copy of this file at:
C:\Program Files\Motorola\ASTRO 25 Products\ASTRO 25 Mobile CPS\Upgrade
When using the 'Synchronize Control Head with Radio' feature, make sure to select the correct file in the Synchronize Control Head window.

Selecting the ‘Browse’ button will point to the ‘Upgrade’ folder where all of the
Astro_25_CH_xx.cnv files are located.

Make sure to select the most recent Control Head Synchronization file.

[MotoFAN]

When these Control Head Synchronization files are needed? Seen them on MOL, but I do not know what for they.

[escomm]

The Control Head Synchronization file contains all of the software versions for the Control Head and a new version is released every time a new radio software version is available.

[MotoFAN]

Any reason to upgrade Control Head software if radio firmware upgrade (Host/DPS) has NOT been performed?

[Jim202]

Any reason to upgrade Control Head software if radio firmware upgrade (Host/DPS) has NOT been performed?

Simple answer is if the radio and the head work correctly, you don't want to mess with the SYNC function of
the software. If you have a head and radio that don't play together, then you will need to run the SYNC function
to get both the radio and the control head to talk with each other correctly.

You run into this situation if you buy just the radio and then take a head that is laying around and marry them
together. The chance of them working the first time is rather remote without using the SYNC function.

Jim

[MotoFAN]

Jim202

Ok, thank you very much for comprehensive answer.

I am interesting because my XTL2500 with Remote head power-ups with stranger effects. Here is more info: http://batboard.batlabs.com/viewtopic.php?f=4&t=93197

[Astro Spectra]

Be warned that 'Maintenance Mode' will be displayed on the head if for any reason there is no power applied to the transceiver deck.

[2wayfreq]

I have ASTRO_25_CH_AC.cvn in the folder. Is that correct and is ".cnv" a typo?

[escomm]

Looks correct and Motorola has been using the .cvn file extension for firmware files for a long time.

[MotoFAN]

I have ASTRO_25_CH_AC.cvn in the folder. Is that correct and is ".cnv" a typo?

Coorect extension is .cvn.

[ASTROMODAT]

Beware of a Motorola bug that can bite you whilst doing the CH sync dance! We converted from XTL5000's with the old HHCH W3 to the Odyssey 03 HHCH. This meant that we had to do a ton of CH syncs. In some cases, right after completing the CH sync successfully, the CPS was corrupted. Worse yet, 100% of the stored codeplug files on that particular PC were all corrupted. The freqs were all red, completely unusable, and could not be overwritten. Called The Big M tech support and they said this is a known problem with CH syncing, and we must reload the CPS, and HOPE our previously saved codeplug files could be restored. They said it would be a krapshoot as to whether we could recover our codeplugs (but they used more polite language, of course). They proceeded to admonish me that this is why one should always have backups of all of their codeplugs on another external memory device, independent from the working PC, thus throwing the blame onto me, juxtaposed to addressing why they haven’t fixed this problem. Oh, well---life in the big city!