• If posting about a radio issue: Include the HOST, DSP and UCM/secure firmware versions, flashcode and CPS version you're using along with the operating system info. This is critical information.

Trbo radios and cps12.0

Status
D

darnalljason

Not Registered
Don't have a copy of the fsb handy but if you are using trbo cps 12.0 make sure u have the 2.5 firmware on your radio or you will break the radios ability to ptt on any digital channel

Motorola will release 12.1 in January and if you experience the ptt problem simply update your firmware
 

NotATechGuy

Contributing Member
CS Forums $upporter
Joined
Nov 22, 2014
Messages
36
Thanks for the heads up. I try to keep CPS and firmware versions matched. I just updated to R12 and first thing I did was update the firmware. I've yet to try it out at work. Hoping to get the new Enhanced Noise Suppressor feature activated this weekend.
 

Forts

Prolific Contributor
CS Forums $upporter
Joined
Aug 6, 2012
Messages
857
I've personally had this happen on one of my radios.... couldn't understand what in the hell was going on when the PTT would bonk of every damn channel. Thankfully a recovery fixed things up. Just a little bit of a faux pas there, eh Motorola??
 

Notarola

Prolific Contributor
CS Forums $upporter
Joined
Feb 4, 2012
Messages
2,219
I too experienced the issue. but updating the firmware before updating the codeplug fixed it. In the one instance I was able to load in the previously saved codeplug and fix the radio.

You would think moto would test such conditions like previous firmware/new cps before releasing the CPS. Moto is known for releasing CPS long before the matching firmware is released. On a large fleet where updates are done routinly it is possible to do 50-100 units at a time before any testing is done (a mistake i never repeated). Its very difficult to have to explain how you bricked a pile of units using the manufacturers newest software.
 

foxtrotdelta

Prolific Contributor
CS Forums $upporter
Joined
Jun 10, 2012
Messages
202
I had to open a case with them on 12/11 when we discovered this "feature" while in the midst of converting a customer from analog to digital. They have approximately 775 radios and only had about 200 left when we all updated to 12.0 because our RMS computer was having issues that seemed to be fixed by the new CPS. Well, we were using OTAP as much as we could and then manually programming/entering others into the RMS when they called us late one night to say a bunch of radios had stopped transmitting.

Were able to downgrade back to 11.5 and had to manually touch all of the affected radios but got them back. Told Moto that the customer was NOT going to let us go through updating the firmware in every single radio as we had disrupted them enough with the initial programming. I'm glad it's not just us having this issue!
 

phonebuff

Prolific Contributor
CS Forums $upporter
Joined
Nov 10, 2013
Messages
678
While the Audio fix in the new firmware is great -- When you have hundreds if not thousands of radios to touch this is really a problem.

I thought they test -3 generations of everything before release.

But hey they did meet the release date. :-(
 

com501

Prolific Contributor
CS Forums $upporter
Joined
Jan 18, 2013
Messages
2,845
Has anyone been able to revert to 11.5 or 11.6 CPS for affected radios if the radio has already been programmed, or do they get the 'too new for this application' error message?
 

foxtrotdelta

Prolific Contributor
CS Forums $upporter
Joined
Jun 10, 2012
Messages
202
We've had no problem at all reverting back to 11.5. I was afraid it would happen (codeplug too new error) but it worked and resolved the issue at least temporarily. Now, if you have a radio with 2.5 firmware in it, then you need 12.0.
 
Status