XTL5000 Channel Info -> XTL2500?

[Birken Vogt]

Reprogramming a sizeable customer. Customer has mostly XTL5000s but some XTL2500s appeared. What is the most efficient way to get the channel information we have already built from the 5000 into the 2500? Cloning just says model type mismatch.

 

[mwb9122]

You can drag and drop with 2 sessions of CPS open or you can export everything from the 5000 and import it into the 2500 under File>Import/Export.

 

[tsunami_australia]

Yes I confirm, I just dumped a stack of zones from my 5000 to my new (to me) 2500 the other day. That said however, for some reason I cannot dump 5000 or 2500 -> XTS2500 (mobile->portable). Had to build a portable cpg from scratch to match .

 

[mwb9122]

Yes I confirm, I just dumped a stack of zones from my 5000 to my new (to me) 2500 the other day. That said however, for some reason I cannot dump 5000 or 2500 -> XTS2500 (mobile->portable). Had to build a portable cpg from scratch to match .

That's weird. I drag and dropped an XTS2500 from a XTL5000 just the other day

 

[Ice-T]

That's weird. I drag and dropped an XTS2500 from a XTL5000 just the other day

Maybe he meant via import/export? Drag & drop certainly works between portables & mobiles.

 

[tsunami_australia]

No I meant drag and drop. I thought it should work but it refused so thought perhaps it is a port vs mobile thing. Would FPP affect that?

 

[ptolemy9200]

I had same problem once on a fpp 2500 going over to a model 2 xts5000. I forget what I did to solve issue. If I recall I'll post but I know I got around it.

 

[nhfirefighter]

FPP will cause issues. You can't drag drop into a radio with FPP. You can drag drop out so if you a mobile you want programmed the same I find it is easiest to make all my changes in the portable codeplug and drag over to the mobile.

 

[tsunami_australia]

That makes sense as to what I'm experiencing though not quite what I wanted to hear . Does anyone know of a particular reason why?

Either way most of my unplanned upcoming changes will be in the same split XTL as the handheld so that could be a way to look at it (an EMS changes frequencies etc which happens here from time to time, especially RFS who jam the repeaters too close). I think anything/everything in the S that has a likely hood of changing in the near future will be the 450-470 stuff anyway that is covered by all of them.

Spent a couple of days rebuilding a profile for the handheld without drag n drop . Hopefully I can clone to the next for the mrs when I get it lol.

 

[Birken Vogt]

You can drag and drop with 2 sessions of CPS open or you can export everything from the 5000 and import it into the 2500 under File>Import/Export.

This is the approach I used and it worked beautifully.

I also had another project to do where I had to modify the programming of a different radio with some new stuff I was supplied on a spreadsheet. Export to CSV, use 2 spreadsheets side by side to populate the new channels, import back from CSV. It took some maneuvering to do both steps correctly but it sure beats typing channel after channel into the little boxes in the Motorola software and risking an error.

Thanks very much for the education.

 

[tsunami_australia]

The import failed with errors from a CSV export for some reason when I tried that .

 

[nhfirefighter]

As far as I can tell FPP flashcodes don't allow import just as they don't allow drag and drop. The fpp changes something with how the radio functions.

 

[mwb9122]

The import failed with errors from a CSV export for some reason when I tried that .

It usually always does but if you look thru the codeplug, must of the important stuff transfers over

 

[mfire39]

Q52 only FPP will allow a drag & drop.. Once Q53 is in the mix, you can't drag & drop.

 

[Birken Vogt]

It usually always does but if you look thru the codeplug, must of the important stuff transfers over

That was my experience, leaving out useless junk like "XZ" PL code and the talk around frequency generates some errors but it still works.

It is great for getting the bulk data entry and error-prone keying of frequencies out of the way and not having to use the awful pull down menu for selecting PL tones.