APX CPS R35 slow as **** to read radios

[GTR8000]

Just installed the latest APX CPS R35.00.00 on three separate computers and read a bunch of different type radios, and the software is taking absolutely forever to get past the Read Radio Verification screen. Click on the window and it goes (Not Responding). I just read a 7500 mobile and it took over FIVE MINUTES to finally see the codeplug in CPS. How ridiculous, can they ever get a CPS/FW release right these days?

And before anyone chimes in with "but it says that it may take several minutes"...yeah, that message has appeared as far back as CPS R33, but it never, ever actually took more than a few seconds on a very basic/small codeplug. This is new bad behavior in R35.

 

[KevinC]

Is your squelch set to 2?

 

[GTR8000]

Of course, but also it's always MSI's fault, c'mon now.

 

[DMS11B]

34 did the same to us, individual stand-alone CPS sessions on different pc's had the same 10 minute verification BS, and nearly crashed our RM Server, for us it was due to a client updating their fw from R19 to R34 just prior to us importing and reading them into our RM.

Mother MOTO claimed it was CPS and RM re-aligning the data within the radio to the new R34 and FW34...

 

[APX8000]

Just click read and pour a nice bourbon....

 

[mikewazowski]

R34 did the same thing here.

 

[nhfdcadet]

I haven't even seen anything from the factory yet on 34, guess I have this to look forward to.

 

[KE4ZNR]

R34 did the same thing here.

Yep. But I work for a local government radio shop so we don't rush anything....
And it is time for another break....be back later....

 

[nikronzo]

Good excuse to start smoking again; read a radio, take a cigarette break, write the radio, take another cigarette. APX CPS, making smoking popular again!

 

[MTS2000des]

Good excuse to start smoking again; read a radio, take a cigarette break, write the radio, take another cigarette. APX CPS, making smoking popular again!

I'll pass. Lung cancer sucks, and so does nicotine piss residue all over everything.

 

[KE4ZNR]

I'll pass. Lung cancer sucks, and so does nicotine piss residue all over everything.

As someone who smoked in his youth many decades ago but now is anti-tobacco I agree.
These days I get headaches and physically sick if I am around a smoker for any period of time.
Sincerely,
Someone who lives & works in the heart of "Tobacco Road": Durham NC.

 

[wa8pyr]

Just installed the latest APX CPS R35.00.00 on three separate computers and read a bunch of different type radios, and the software is taking absolutely forever to get past the Read Radio Verification screen. Click on the window and it goes (Not Responding). I just read a 7500 mobile and it took over FIVE MINUTES to finally see the codeplug in CPS. How ridiculous, can they ever get a CPS/FW release right these days?

And before anyone chimes in with "but it says that it may take several minutes"...yeah, that message has appeared as far back as CPS R33, but it never, ever actually took more than a few seconds on a very basic/small codeplug. This is new bad behavior in R35.

View attachment 176314

Guess they’re not testing CPS before they release it again.

I’m personally convinced that the people who write the APX CPS are a bunch of gamers who wouldn’t know a radio if it bit ‘em on the butt, much less never had to program one….

 

[Radio99]

Running CPS R35.00.00 on a Windows 11 machine and read a loaded 8K in 13.85 seconds

 

[GTR8000]

Reading the codeplug isn't the issue, that takes a few seconds, it's the Read Radio Verification step that it's getting hung up on for ages...at which point the radio has long since reset after reading the codeplug. I never had any issues with any radios on R34 despite the message stating it may take a few minutes.

All of the radios I've tested so far are on FW R35 and were already read/written with R35, so there shouldn't be anything that needs to be "re-aligned". Everything is at R35. Whatever, maybe R36 will fix it later this year.