I was talking the headder on the charger PCB.
-
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.
I joined the cult (New XG-100M owner)
- Thread starter Teotwaki
- Start date
a picture would be useful for clearing this up
So Harris' OTAP has some sort of "kill" feature. Is it detailed in any of the available documents?
Im a little confused here, My guist was the XG-100P and P5400 both used the same battery.
I do know I have idetical bases (CH-104560) with 5 pin pockets for the P5400 and 4 pin pockets for the P7100.
I see now they are very different batteries.
Pretty much every manufacturer has some sort of kill or stun feature, but they only work if the radio is on a system with the feature, and is using a known radio ID. In the case of a trunked system, the radio also has to be affiliated to the system.
You could have some sort of global kill command on a conventional system, but for that to work without bad things happening you would have to ensure that every legitimate radio that might be on the channel is switched off, else you’ll kill radios you don’t want killed.
ElroyJetson
Getting tired of all the stupidity.
The P7100/700P/Jaguar and the XG-100P use similar batteries but the 100P battery is thicker, presumably has higher capacity, and makes the radio thicker when installed which can cause some cases not to fit, if you put the 100P type battery on a P7100 family radio.
I've run across a 100P battery but it was completely dead and would not charge so I am far from an authority on it. However it does fit on a P7100. It has four charging contacts.
The radios that are newer than the 7200 series portables (7300, 5300, XG-75P, etc) all share their own battery family.
I've run across a 100P battery but it was completely dead and would not charge so I am far from an authority on it. However it does fit on a P7100. It has four charging contacts.
The radios that are newer than the 7200 series portables (7300, 5300, XG-75P, etc) all share their own battery family.
I don't see much change but did note someone has JTAG headers installed on the control board.
Last edited:
I can say the XG-100 and XG-75 don't have that. Closest may be OTAP, but that would be an easy fix.
Maybe obliterate the codeplug, possibly the firmware, but a run through RPM will restore it. Moto, killed is dead.
Yea, I can live with that.
Actually, no. A trip to the depot will restore it. And it'll only cost $400....
I bought a lot of 4, some were dead. 5 red blinks. Reinserted the battery a couple times and finally went into recondition, then charged normally. These were Li-Ion batteries and should never go to zero just sitting. Just looked at one, the radio started but shut down. time for a charge after 2 months.
OTAP is Over The Air Programming, not stunning and killing radios. I suppose you could 'un-program' a radio via OTAP but that doesn't effect tuning parameters, just the codeplug/personality/mission plan. Neither does stun/kill via a trunked system. For that matter nothing permanent happens when a radio is stunned, it's easily revived with the proper tools and sometimes without them.
So, back on topic. Short story is, I have a radio with "Lost MRU" and attempted to reconnect via Putty. There seemed to be no response even though I banged in various commands. I had left Putty running and Lo & Behold, there appears to be a connection with a very slow response time. Here's a screen shot. (note: 7 Fatal Errors mentioned). Where the cursor is (green box at the bottom) each of the preceding boxes of three vertical dashes seems to be an undecipherable response from the radio. Thoughts on recovery? At least the radio is not bricked. Just seems to be in a slow speech mode.
Will it respond to a firmware write attemp? I assume not.
Is this the latest radio or an earlier one?
Mancow: Firmware write attempt via RPM2? If that's what you meant RPM2 can longer detect the radio connected to the serial port
PRCguy: Latest radio. It was almost working but I might have boogered it. Does not seem to be bricked but am guessing I have to delete firmware and reload. However RS232 communication is weird.
Here's the back story.
I just received a Ebay radio and the BurnApp was R13C03 and BootApp was 13. The CH721 I already had is R07.17 and worked fine with two other Xg100Ms I have.
The new radio was acting pretty odd in that the original mission plan did not seem to get erased when loading new plans through RPM2. I upgraded the firmware to RO6T02. Still the same problem. Next, using RPM2 I completed a format of the Flash Drive which seemed to help as I could load in a set of test frequencies in a mission plan and the radio seemed normal at that point.. (seemed)
Last thing I may have done that caused this: I wondered about the revision of the bootApp being the latest and may have (mistakenly) clicked on the Windows batch file "burn". Unfortunately I am unclear as to what I may have done that created this disaster. Right now Putty can sort of seem to communicate with the radio (see previous photo). I am using a desktop computer with two true physical DB9 serial connectors. My CanBus cable is good and the unused ports are terminated.
Same thing happened to me. I'll PM you a message.
Redbeard,,
I've repaired this particular radio by resoldering three critical RF connections. Discussion is here:
XG-100M RF Circuits Discussion
I have a XG-100M I bought a few months back and did not immediately test. Dumb move on my part. It turns out the radio programmed fine but it had no transmit power out and no receive sensitivity. It was as if there was a big attenuator in the middle of the antenna path. I figured I would...
Last edited:
I found another thread about M7300 radios displaying Lost MRU. Member Apco25 mentioned that RS232 terminal commands could be sent that might overcome the problem. I wonder if the same can be achieved for the XG-100M?
The thread is here:
M7300 Lost MRU, need recovery assistance
The CS7000 issue is most likely tied to firmware incompatibility.