issue with CPS for xts3000

[Mrestivo]

Hey yall,

Having some issues with programming my xts3000. I have the astro sabre and xts3000 cps software (5.3.0) installed. The USB to radio cable from bluemaxer is reading fine on my pc. No matter which port I assign I still get communication with radio failed?

Tried it in a sand box as well. Same issue. Kinda running out of ideas and its just amateur programming too nothing fancy

any help would be great

 

[jeepsandradios]

I was not aware XTS3K or Saber could be programmed over USB. I program both of mine with a RIB and appropriate cable.

 

[Project25_MASTR]

What OS are you running the CPS on?

@jeepsandradios I've programmed plenty of XTS3ks and Astro Spectra's via a USB serial adapter, but never used a dedicated cable. My guess is this is a TTL-USB based cable that interfaces directly with the radio. Should work fine...in theory.

 

[jeepsandradios]

Ok. I've never seem a rib less cable for the 3K or Saber. All of mine require a RIB. The XTS1500/2500/5000 had a rib less cable. YMMV

 

[MTS2000des]

Your using a 32 bit version of Windows, right? The ancient XTS3000/Astro Saber CPS won't read/write on 64 bit versions.

 

[Mrestivo]

win 11 64 but even on VmWare running xp at 32 i get the same error. cable wise its from bluemaxer49. cps is 5.3.0

 

[MTS2000des]

So use an actual period correct supported O/S as the documentation included with the CPS specifies on a physical machine and report back.

 

[vagrant]

Just some info. I previously owned an XTS3000 model 3 UHF R1. I used CPS 5.03 to read/write using Windows 10 Pro 64 bit OS on a PC and not a Mac via emulation software. The XTS3k programming cable had a serial connector. I used a Gigaware USB to Serial cable for connectivity. I just checked the CPS shortcut and it was running in compatibility mode for Windows 7. I do not recall if I did anything special about the port speed/settings on the computer to slow down the buffer.

Still, I definitely agree about using the CPS supported OS and especially using a serial port on the computer versus a USB to Serial cable. I probably had problems with the XTS3k as well if I adjusted the compatibility mode to Windows 7. Oh...one more thing. If it fails on a read or write, try again and just wait and I mean wait. If you do not get an error window, or it looks like CPS is frozen...wait. Do not click/close, just wait.

Your using a 32 bit version of Windows, right? The ancient XTS3000/Astro Saber CPS won't read/write on 64 bit versions.

 

[MTS2000des]

It may work, but it is also not guaranteed to work. This is where many folks who are trying to get these 20 year old radios up and running create much headache for themselves.

Using the supported operating systems and hardware minimizes the chance of issues. Not to mention, unlike newer product lines (Astro 25, APX, TRBO) these radios can be put into comatose states if something hoses during a write as both the internal and external codeplugs are extracted, read into RAM, then spit back into the radio. Plenty of opportunity to wind up with a paperweight using unsupported O/Ses, virtual machines, voodoo, etc.

Or just get newer stuff. Astro 25 subscribers are a mile above those 1st gen P25 subscribers in software, hardware, capability and performance. And CPS runs on "modern" PCs without headaches.

 

[vagrant]

Indeed. I use XTS5k VHF & UHF radios in XTVA's at home. I find the XTS5k to be amateur budget friendly, even a model 3 w/FPP. Hell, they cost less than whatever new Yaesu, Kenwood, Icom handheld and are incredibly more durable. Still, in the field I use an APX 7000XE and enjoy the Bluetooth programming and BT mic. That radio is not for the frugal amateur though.

 

[iowajm780]

I dorked two XTS3000’s. Running XP 32 bit using a USB to serial adapter. Worked great until one day it did not work and died doing write, The old saying it worked good yesterday, well it did not work great the next day. XTS3000 number 2 was my fault, When writing it does not beep, only the display indicates with service or program or so like that, The LCD was dead, but the radio worked, While writing to the code plug, I forgot it does not beep when writing to the radio and I thought the RIB or programming cable was bad and pulled it while writing the codeplug and bricking it. No big loss, got them from Ebay cheap. Oh well..

 

[Echo4Thirty]

Just some info. I previously owned an XTS3000 model 3 UHF R1. I used CPS 5.03 to read/write using Windows 10 Pro 64 bit OS on a PC and not a Mac via emulation software. The XTS3k programming cable had a serial connector. I used a Gigaware USB to Serial cable for connectivity. I just checked the CPS shortcut and it was running in compatibility mode for Windows 7. I do not recall if I did anything special about the port speed/settings on the computer to slow down the buffer.

Still, I definitely agree about using the CPS supported OS and especially using a serial port on the computer versus a USB to Serial cable. I probably had problems with the XTS3k as well if I adjusted the compatibility mode to Windows 7. Oh...one more thing. If it fails on a read or write, try again and just wait and I mean wait. If you do not get an error window, or it looks like CPS is frozen...wait. Do not click/close, just wait.

Using a 64 bit OS creates a VERY high risk of codeplug corruption resulting in a FL 01/82 brick being created. We keep numerous vintage machines around the shop, all the way back to a 486 to make sure we do program picky radios properly.

That said, W10 32 bit works fine for the ASTRO series here. Its the 64 bit OSs that seem to be the issue.

 

[com501]

Stick with OEM cables, an OEM RIB, and a computer manufactured in the time period of the radios, and you will never have a problem.

Older radios have different expectations from the software than newer radios, and a lot depends on the computers used when developing.

In a side note, a paper I read recently on an attempt to get an Apollo 11 era flight control computer to run described the same frustrations you are experiencing now.

 

[MTS2000des]

One has to understand that these ANCIENT radios are VERY DIFFERENT codeplug structure wise from "modern" radios. Regular old CPS (and RSS) touches the "sensitive" areas of the "internal" codeplug such as the tuning partition. Using unsupported operating systems and hardware CAN LEAD YOU TO A PAPERWEIGHT and NO ONE MAY BE ABLE TO HELP YOU. The number of person(s) with actual skill set, access to things like special tools, flash keys and SmartRIBs are less than a couple dozen.

Motorola (and other vendors) learned over the past 25 years and modern radios like the APX and Astro 25 are pretty (but not totally) immune to the bad things that happened to these legacy radios. I'll say it again, Blockbuster Video was on every corner renting VHS tapes by the hundreds a night when these radios were in production, and people were jamming to the Macarena on cassette tapes. That is how OLD they are.

 

[iowajm780]

My XTS300’s were cheap enough to use non-oem programming cables. It worked for awhile then they crapped out. No big loss as they were not that valuable anyway. Now programming my APX6000’s, for the high dollar they cost me, it’s all oem programming stuff, no matter what it cost me. I even have an oem cable for my XTS2500’s and my XTL5000. They are both EOL’d, and old, but work fantastic and the cables from Motorola were not that expensive. However, please don’t tell Motorola, they failed to charge me for my XTL5000 programming cable for some reason many years ago.🙂

 

[MTS2000des]

Here's another reality: radios like the Astro Spectra, XTS3000, even the Astro 25 line all have EEPROMs that store data and the radios operating system do things in the background that store data such as scan list members, last affiliated zone/channel (in case of trunking personalities), call lists, etc. All EEPROMs have a finite life cycle. It's in the millions but after two decades or more of daily use, they eventually fail- and that's when radios "wake up" with things like FAIL 01/82. No software can fix it. The EEPROM has to be physically replaced. Not a big deal IF one has the right SMD rework station and parts, but the hard part is with the legacy radios is rebuilding the tuning values and manually retuning the radio to get it working well again.

Just more food for thought when you see the Ebay flipper turds wanting Elivs Presley prices for ancient scrap on it's last leg.

 

[Mrestivo]

thank you guys for the help and input. I probably will invest in a 32x Toughbook with xp on it. regarding cables and ribs can anyone be kindly provide a link/product # for that,

On other p25 digital is there any other ones besides Motorola that can handle p25 and a bit better to self program?

 

[chrismol1]

self program? yea ditch the 3000 and get an XTS5000 or XTS2500 with front panel programming