Codeplug Configurations Between Different APX Radios

[blantonl]

Are there any processes in place to convert codeplug configurations between different APX radios?

Say for instance, copying a APX7000 configuration to an APX8000.

Granted feature codes and that stuff play into the equation, but given that an APX8000 supports everything a APX7000 does, is there an easy way to copy the configuration between codeplugs, or is it just a copy/paste festival of work?

 

[clbsquared]

Drag and drop. It's in the help menu. Open two instances of CPS ( donor codeplug & receiving codeplug. Load keys into both codeplugs. Drag and drop the entire top node or individual tree nodes. Fix minor errors noted in the "drag and drop" report. Save codeplug

 

[MTS2000des]

Top level drag and drop. You shouldn't have too many invalid fields IF your 8000 has all the RF bands and features in it's flashcode present in the 7000 donor AND the firmware/codeplug versions match or the target is at least at a higher revision as the donor.

 

[blantonl]

This absolutely warms my heart. Thank you!

 

[GTR8000]

You may've already finished your codeplug up, but for the sake of others reading...drag and drop the scan lists last, and if the zone numbering doesn't match up exactly between codeplugs, it's going to hose up all of the scan list members.

 

[MTS2000des]

I always start with a "virgin" target codeplug if possible. This eliminates the issues with scan lists, trunking systems not lining up, etc. If there is existing zone/channel/trunking/scan, then yes, what is mentioned above can be an issue. To avoid this, use a factory or blank target codeplug if available. Just make sure it is at the same or higher revision level as the source.

 

[wa8pyr]

This absolutely warms my heart. Thank you!

Works for the Astro25 line, too.

You may've already finished your codeplug up, but for the sake of others reading...drag and drop the scan lists last, and if the zone numbering doesn't match up exactly between codeplugs, it's going to hose up all of the scan list members.

Actually I would correct that a bit. If you're dragging and dropping a section at a time, do the systems first, then the scan lists, then the personalities, then the zones, then do the scan lists again.... especially if you're programming an Astro25 radio. If you wait to drag the scan lists last, you'll lose the scan list numbers in the personalities and have to go through to set them up again in each personality.

For APX, it's been a mixed bag for me as to whether CPS remembers the scan list numbers or not, so I just follow the same steps I use for Astro25 radios (as above); works every time.

Easiest is top-level drag and drop (one drag/drop and you're done), although every now and again this causes problems and I have to resort to dragging a section at a time.

It's times like that I really appreciate Harris, Tait and the others; one codeplug works in nearly any radio, just tell the software what model radio it's going into and the software will ignore the features that aren't there.

 

[GTR8000]

Actually I would correct that a bit. If you're dragging and dropping a section at a time, do the systems first, then the scan lists, then the personalities, then the zones, then do the scan lists again.... especially if you're programming an Astro25 radio. If you wait to drag the scan lists last, you'll lose the scan list numbers in the personalities and have to go through to set them up again in each personality.

For APX, it's been a mixed bag for me as to whether CPS remembers the scan list numbers or not, so I just follow the same steps I use for Astro25 radios (as above); works every time.

There are no scan list numbers for the APX, it's all based on the scan list names. The problem is not waiting until last to bring the scan lists over because the names that are referenced in each conventional/trunking personality won't be found (those will clear up later), but the issue is that if the zones aren't exactly the same as the donor radio, those zone channel references in the scan lists will be fubar.

Trust me...been there, done that countless times over a full decade with the APX series.

 

[wa8pyr]

There are no scan list numbers for the APX, it's all based on the scan list names. The problem is not waiting until last to bring the scan lists over because the names that are referenced in each conventional/trunking personality won't be found (those will clear up later), but the issue is that if the zones aren't exactly the same as the donor radio, those zone channel references in the scan lists will be fubar.

Trust me...been there, done that countless times over a full decade with the APX series.

So have I, been fussing around with APX radios since 2008. You're right that it's scan list names rather than numbers in the APX, but the idea is the same; I've still found my process to work flawlessly. My preference is top-level drag and drop, but sometimes I've had glitches that made dragging things over a section at a time work better.

 

[MTS2000des]

Top level D&D works great when writing to a "virgin" codeplug that is at the same revision level as the target: e.g. source APX7000 is at same CP version with same HOST firmware R26.03 and target is at R26.03 and COMPLETELY BLANK (factory). Provided you have valid system keys (assuming trunking is involved), everything harmoniously migrates over with no botched personalities, zones or scan list issues. When our EMA bought 8000XEs, this is how I programmed them and had zero issues. I later added U-TAC NIFOG stuff as requested.

 

[IFRIED91]

Works for the Astro25 line, too.



Actually I would correct that a bit. If you're dragging and dropping a section at a time, do the systems first, then the scan lists, then the personalities, then the zones, then do the scan lists again.... especially if you're programming an Astro25 radio. If you wait to drag the scan lists last, you'll lose the scan list numbers in the personalities and have to go through to set them up again in each personality.

For APX, it's been a mixed bag for me as to whether CPS remembers the scan list numbers or not, so I just follow the same steps I use for Astro25 radios (as above); works every time.

Easiest is top-level drag and drop (one drag/drop and you're done), although every now and again this causes problems and I have to resort to dragging a section at a time.

It's times like that I really appreciate Harris, Tait and the others; one codeplug works in nearly any radio, just tell the software what model radio it's going into and the software will ignore the features that aren't there.

Going off topic for a sec you’re partially correct here except xg100p/m Unity mission plans… those cannot be intermingled between radios due to their multiband nature… speaking for RPM140C not sure about RPM2

 

[IFRIED91]

Works for the Astro25 line, too.



Actually I would correct that a bit. If you're dragging and dropping a section at a time, do the systems first, then the scan lists, then the personalities, then the zones, then do the scan lists again.... especially if you're programming an Astro25 radio. If you wait to drag the scan lists last, you'll lose the scan list numbers in the personalities and have to go through to set them up again in each personality.

For APX, it's been a mixed bag for me as to whether CPS remembers the scan list numbers or not, so I just follow the same steps I use for Astro25 radios (as above); works every time.

Easiest is top-level drag and drop (one drag/drop and you're done), although every now and again this causes problems and I have to resort to dragging a section at a time.

It's times like that I really appreciate Harris, Tait and the others; one codeplug works in nearly any radio, just tell the software what model radio it's going into and the software will ignore the features that aren't there.

Also RPM doesn’t know what features are currently enabled on a particular radio.. if you write a mission plan to using a feature that one radio has to one that doesn’t you’ll get an error when selecting that channel/zone/system