ElroyJetson
Getting tired of all the stupidity.
My shop purchased RPM/ProGrammer 20 fairly recently to support some work we picked up, and of course I was a significant contributing factor in it, as I may not be an expert at EDACS and M/A-Com radios,
but I'm not totally uninformed, either.
I finally got around to upgrading the firmware and DSP in my own "personal" direct FM model 7100IP,
which has every option you'd ever want in it. I'm up to J2R15 radio code and a very nice DSP code
that supports every feature my radio has, so that's good.
What's really cool about the new radio code (J2R13 and above) is that, now, the FCC menu actually
works while monitoring a trunking system, and it's quite useful. It has several pages of data you
can scroll through, which give you the channel number you're currently listening to or talking on,
(logical channel number), the signal strength of it, the frequency variance between your radio's
oscillator and the reference, which is the control channel, and the system usage moment by moment,
expressed as a percentage. 0 percent means the system is idle, of course, and 100 percent is the
point at which users are probably getting busy signals. I have yet to see the system exceed 40
percent, so it seems that the local system has adequate capacity, but weekend night traffic will
be the real test of that.
The only thing I don't really like about RPM is that it can only read and understand a ProGrammer
personality if it reads it from disk. It can't directly handle a ProGrammer personality by reading it
from a radio. The radio has to be upgraded to RPM compatible firmware in order for its personality
to be directly readable.
Oh yeah...I would like to see the full suite of recovery tools added back to the radio maintenance tools,
but an earlier version still works anyway so it's a minor inconvenience. I've considered trying out a
hybrid installation, using the radio maintenance executable from version 18 and installing it in the
programmer/rpm version 20 installation.
Elroy
but I'm not totally uninformed, either.
I finally got around to upgrading the firmware and DSP in my own "personal" direct FM model 7100IP,
which has every option you'd ever want in it. I'm up to J2R15 radio code and a very nice DSP code
that supports every feature my radio has, so that's good.
What's really cool about the new radio code (J2R13 and above) is that, now, the FCC menu actually
works while monitoring a trunking system, and it's quite useful. It has several pages of data you
can scroll through, which give you the channel number you're currently listening to or talking on,
(logical channel number), the signal strength of it, the frequency variance between your radio's
oscillator and the reference, which is the control channel, and the system usage moment by moment,
expressed as a percentage. 0 percent means the system is idle, of course, and 100 percent is the
point at which users are probably getting busy signals. I have yet to see the system exceed 40
percent, so it seems that the local system has adequate capacity, but weekend night traffic will
be the real test of that.
The only thing I don't really like about RPM is that it can only read and understand a ProGrammer
personality if it reads it from disk. It can't directly handle a ProGrammer personality by reading it
from a radio. The radio has to be upgraded to RPM compatible firmware in order for its personality
to be directly readable.
Oh yeah...I would like to see the full suite of recovery tools added back to the radio maintenance tools,
but an earlier version still works anyway so it's a minor inconvenience. I've considered trying out a
hybrid installation, using the radio maintenance executable from version 18 and installing it in the
programmer/rpm version 20 installation.
Elroy