Buying used XPR 3500e, are there questions I should ask?

[xohs]

I appreciate the feedback. My use case is fairly simple, I'm interested in understanding how to configure and operate the encryption function of XPR3500e radios. I work in information security and have years of experience with most technical topics, radio is unfortunately not one of them (yet) so here we are. I expect this to be a great platform for me to expand/test/learn with, and I do intend to file for a license before I begin. Itinerant sounds like a great option as it fits this use case. I'm also not in a big rush, which is great because I expect the FCC process to be slow.

The feedback here has been super helpful so far. In terms of an actual radio, I'll ask about password protection and also for a clear photo of the labels. It will be a few weeks before I get to buying radios as I have to hack through learning the license process first.

 

[K2NEC]

Another thing that no one previously mentioned, there's an "Amazon" model of 3500e, the model number ends in -AMA or -AMA2. These are flashed differently and have a very limited feature set, I'd also be willing to bet that most of those are password protected. In any case, avoid at all costs.

 

[alcahuete]

I'm interested in understanding how to configure and operate the encryption function of XPR3500e radios.

It's very simple. Set your key and either configure the channels to run full time encryption, or program one of the buttons to be able to turn it on and off.

I'm also not in a big rush, which is great because I expect the FCC process to be slow.

You will normally have your license and allocations in a few weeks, sometimes quicker.

 

[tropiradio]

Other than that, the 3500's program similar to all other MOTOTRBO radios using either CPS 16 or CPS 2.0 depending on the firmware on the particular radio you get. As long as it doesn't arrive password protected, you're likely good to go for programming.

I would consider myself lucky if I don't have to program a radio with that horrible and painfully slow awful V2 CPS, and can still use good old (and fast and versatile) CPS v16. For what you intend to use the radios, absolutely no reason to "upgrade" to newer firmware and be caught into having to use V2 only. Just get V16 and continue to be happy.

 

[K9KLC]

I would consider myself lucky if I don't have to program a radio with that horrible and painfully slow awful V2 CPS, and can still use good old (and fast and versatile) CPS v16. For what you intend to use the radios, absolutely no reason to "upgrade" to newer firmware and be caught into having to use V2 only. Just get V16 and continue to be happy.

Unfortunately, everything I seem to get lately is too new firmware wise for CPS 16. I still have some radios that I've had for some time I use 16 on, but when you get stuff and it's simply got the newer firmware on it, not much choice. CPS 2 is slower I'll say that about it however, when it's needed it's needed.

 

[tropiradio]

Unfortunately, everything I seem to get lately is too new firmware wise for CPS 16. I still have some radios that I've had for some time I use 16 on, but when you get stuff and it's simply got the newer firmware on it, not much choice. CPS 2 is slower I'll say that about it however, when it's needed it's needed.

Just making the point of anybody migrating to V2 without any real need. I know everything new now is V2, but an older radio that does not need to be upgraded just programmed for a simple function as explained by the OP and it still has FW R02.09 or older, be happy with CPS16 and don't "upgrade" to V2 for no real valid reason. If FW is older than 2.09 you can always update it to that revision, and still stay within CPS16 operability.

If I loosely add up the time I spent waiting for that damn V2 CPS saying "not responding" o just waiting to open the next requested window, or even parsing a codeplug, specially once one reaches the 50-100 channel level, I'd say it easily doubles the time it takes to program any radio plus the added aggravation and frustration on having to wait on the stupid thing just because.