Page 1 of 1

xts5000 cps13 problem

Posted: Fri Oct 09, 2009 8:43 am
by mike m
I have a weird cps13 problem with a high UHF XTS5000.

Radio: xts5000, Model III, UHF range 2, flashcode 180008-000482, with firmware rev R12.00.13 and using cps13.

Radio has 11 zones with 16 channels per zone.

The channel name corresponds to the actual frequency with an alphanumeric such as 450.00 etc for each channel, IE the channel alpha correspond to the actual frequency in the radio.

Zones are named Z1, Z2.... Z11 standard motorola default name.
channels are named 450.000, 453.325,.... for example, you get the idea.

After programming the radio the zone names in 75 % of the zones disappear, some of the higher zone names are still there, zone 9, 10 and 11 but most of the lower zone alpha characters from 1 thru 7 and 8 are gone or partially missing.

Zone 1 channel 1 however displays a 1 in the zone name, the Z is gone and even the number 1 is gone in the rest of zone 1's channels.

The Customer has reprogrammed several radios with new, different codeplugs, and each time the same results so it's not one single corrupted codeplug issue.

Changed out the displays on the radios and no change, same weirdness.

The radio operates fine on all channels by the way, its just that the zone names are gone on some zones.

When the decimal point is removed from the channel alpha numeric the radios program fine and all zones names are intact.

Anyone else using CPS 13 and see any similar problems when a decimal point is used in a channel name ?

I don't have the radio with me at this time nor do I have the codeplug so I can't send it out, the radios are in Texas at this time.

All I have are some screen shots showing the weirdness.

Mike

Re: xts5000 cps13 problem

Posted: Fri Oct 09, 2009 12:20 pm
by fineshot1
Open "Display & Menu" under the "general" tab - is the balance between the channel text and zone text size such that there is no conflict between them?

Re: xts5000 cps13 problem

Posted: Fri Oct 09, 2009 5:03 pm
by mike m
The zone and channel text size is set correetly, there is no conflict there.

3 characters for zone and the rest for channel, we have been using the same master default codeplug for the same model radios under CPS12, it's only when we went to CPS 13 using the new radios that the problem occured occured.

The only change was that newer firmware radios were added and these radios were cloned from a default codeplug, into the new XTS5000's using CPS 13.

Even making up a raw master codeplug from the ground up with a new untouched Fw12.00.17 radio results in the same problem.

Re: xts5000 cps13 problem

Posted: Fri Oct 09, 2009 7:14 pm
by akardam
If you read the codeplug out of an affected radio, do the zone and channel names show up OK in CPS?

Re: xts5000 cps13 problem

Posted: Sat Oct 10, 2009 10:04 am
by mike m
yep CPS displays fine it's just the radios that are effected.

I have more info now and I found a radio with the same problem FW, it seems to be localized to firmware 12.00.13 radios using CPS 13.

I programmed one of the same rev FW radios on an Pc using CPS 12 and it doesn't do it but then when I programmed the same codeplug in and out of the same radio using CPS 13 it showed up.

I'm going to downgrade the flash of the radio to FW 12.00.00 and see if CPS 13 is still buggy.

The customer has requested to stay at Fw 12.00.00 and I'm not sure how they ended up with a higher rev Fw radio, sometime things slip out by mistake.


Mike

Re: xts5000 cps13 problem

Posted: Sat Oct 10, 2009 2:10 pm
by akardam
Are you using R13.00.00 or R13.00.01, or both?

Re: xts5000 cps13 problem

Posted: Mon Oct 12, 2009 12:41 pm
by akardam
To follow up on this, after testing R13.00.00 and R13.00.01 CPS with an XTS2500 M1.5 R12.00.13 and an XTS5000 M2 R12.00.13, I was unable to duplicate the issue. These radios have 4-6 zones of 16 channels each, in a 3/9 zone name/channel name split. I experienced absolutely no loss of zone or channel names.

Any other data you can provide?

Re: xts5000 cps13 problem

Posted: Thu Oct 15, 2009 3:09 am
by sprayon
I have seen this problem in the past myself. I have found that if you just remove the decimal itself and replace with a space it works. Have you tried this? It has worked on all the ones I have done...