Believe it or not. We did more review. Fault battery caused it to tx on trunking...
-
To anyone looking to acquire commercial radio programming software:
Please do not make requests for copies of radio programming software which is sold (or was sold) by the manufacturer for any monetary value. All requests will be deleted and a forum infraction issued. Making a request such as this is attempting to engage in software piracy and this forum cannot be involved or associated with this activity. The same goes for any private transaction via Private Message. Even if you attempt to engage in this activity in PM's we will still enforce the forum rules. Your PM's are not private and the administration has the right to read them if there's a hint to criminal activity.
If you are having trouble legally obtaining software please state so. We do not want any hurt feelings when your vague post is mistaken for a free request. It is YOUR responsibility to properly word your request.
To obtain Motorola software see the Sticky in the Motorola forum.
The various other vendors often permit their dealers to sell the software online (i.e., Kenwood). Please use Google or some other search engine to find a dealer that sells the software. Typically each series or individual radio requires its own software package. Often the Kenwood software is less than $100 so don't be a cheapskate; just purchase it.
For M/A Com/Harris/GE, etc: there are two software packages that program all current and past radios. One package is for conventional programming and the other for trunked programming. The trunked package is in upwards of $2,500. The conventional package is more reasonable though is still several hundred dollars. The benefit is you do not need multiple versions for each radio (unlike Motorola).
This is a large and very visible forum. We cannot jeopardize the ability to provide the RadioReference services by allowing this activity to occur. Please respect this.
Harris NAS
- Thread starter MissouriSirens
- Start date
Battery charged and showed 100. HE told me this, radio NAS with a brand new battery and after putting in the one battery, the TX module or something like that would get activated because the dying battery bypassed the software and then would active the tx inhibit after the fact. He checked it, sent it to me, and it seems like a one off case. He cant replicate it. It was a software glitch we think... It had really old firmware. It did it twice and then after an update he cant replicate it.
My XG100s (P and M) and XL200s are completely invisible to the system, verified on Genwatch and running a report on my ID. Something is amiss. Perhaps old firmware with a bug?
Thats where we are at. old FW. We updated it and the issue wont return... It was so strange because it never affiliated, just de affiliated... It would TX, BONK, and be normal. It like i said never showed up as an affiliation just as a deaff...
There is a known bug when programming with certain later revisions of RPM2, 19A for sure, and working on older radios like the XG-100M that the radio will still try to transmit data to the control channel. There is no indication of what exactly it is doing, just the RSSI bars flashing red. No “Registering” or the TX/RX Data icon showing up, nor does the radio bonk or go out of range or display the “Invalid Unit” message even if changed to an invalid ID.
I have not been able to nail down exactly what causes it, but after updating everything to R06T02 and using 19C it seems to mostly be resolved.
I have not been able to nail down exactly what causes it, but after updating everything to R06T02 and using 19C it seems to mostly be resolved.
Last edited:
Well the older firmware r06k07 seemed to be the same with rpm1 and the p series of the xg100
Just for informational purposes, I confirmed by experimentation that, a radio such as an XG-75P, provisioned with P25 Phase 1 trunking, but not with Phase 2 trunking, will not show any error messages if the TDMA check box is checked in the system data for a P25 system.
However, it also will not hear or in any way indicate that there is Phase 2 traffic.
I was expecting a feature encryption error, as Phase 2 operation requires that feature, no 47.
However, it also will not hear or in any way indicate that there is Phase 2 traffic.
I was expecting a feature encryption error, as Phase 2 operation requires that feature, no 47.
I have noticed with an XG-75P programmed to monitoring only on a P25 system, in fringe coverage areas,
that sometimes it would show several brief flashes of the RX/antenna indicator on the display accompanied by audio pulses,
at first I was thinking that due to some error the radio may have been trying to login. But no, it's apparently just a characteristic of marginal and rapidly varying RX signal strength. At no time did the TX indicators (on display or the red LED) appear.
It was similar to what the radio will do with multiple failed login attempts, but it's not that.
that sometimes it would show several brief flashes of the RX/antenna indicator on the display accompanied by audio pulses,
at first I was thinking that due to some error the radio may have been trying to login. But no, it's apparently just a characteristic of marginal and rapidly varying RX signal strength. At no time did the TX indicators (on display or the red LED) appear.
It was similar to what the radio will do with multiple failed login attempts, but it's not that.
If it shows the antenna and does a beep beep beep, it means it has found a CC but is still getting data. i believe, my 75 does it. I have a 75 W/ TDMA and I don't use it anymore.
There is a YouTube tutorial for the xg100p and it should be the same for the xg75. It is a great resource and I have used it and it works good
It is the exact same. It works with RPM2 however, you need AAC and you need to disable other things.
I have had a very similar thing just like that with a P5400 VHF that was monitoring a local P25 system. Anytime the signal dropped the radio would go into CC SCAN, it would beep and indicate with the green light until it locked back on. Definitely would concur that it must just be standard in the radios to do that.
Ive had my one radio roam to other systems sites, then bonk at me too. (Enhanced CC)
