Page 1 of 1

Odd problem with XTS5000 and IMPRES battery

Posted: Wed Feb 08, 2006 11:44 am
by Mfire39
Hello all, this one has me really scratching my head. I upgraded from a VHF XTS5000 mod 2 to a mod 3. I'm using a NiCad IMPRES battery on this radio, and since I got it I have noticed that it doesn’t quite RX the way my old XTS did. It seamed to be a little less sensitive, and certain channels that were clear as day on my old 5000 would be somewhat scratchy on this new one. So I started by taking it in to my MSS for an alignment, and everything appeared in tune. So after trying some things, I noticed that when I would key up another radio near this one in close range, the RX audio would cut out until I moved the radios apart. So in between messing around with this, the battery was low and I put a non IMPRES battery on the 5000. After that, it started receiving like it should, and sounded great on all my channels. I even keyed up another radio next to it, and the RX audio didn’t cut out like it did before.

So for the heck of it, I put the IMPRES battery on a VHF mod 1 XTS5000 that I have, and it made that radio have bad RX, and less sensitivity like it did with my mod 3. So I guess I have to ask, could it be something in the internals of the IMPRES battery causing my radio to RX very bad when it's used? Has anyone else ever had a problem like this? The IMPRES battery in question is only a month old with a 609 date code. I'm currently just using reg NiCad’s on both my XTS's until I can figure this out. Both of my radios are TX/RX perfectly right now without the IMPRES battery. Just thought I would share my interesting story, because I have never seen or heard of a problem like this.

Thanks,

-Marc

Posted: Wed Feb 08, 2006 12:19 pm
by wavetar
What's the firmware version of your XTS5000? The reason I ask, is because there are known issues with XTS3000 units with firmware versions below 7.21.xx. when using Impres batteries. I haven't seen any SRN's concerning XTS5000 units, but it may be an 'unknown' issue (ie: not enough of them have it for Motorola to admit it). Or, it might be an issue that effects the older 2.xx.xx firmware XTS5000, and Motorola doesn't care about it.

Todd

Posted: Wed Feb 08, 2006 1:08 pm
by Mfire39
Hey Todd. My XTS5000 Mod 3 has R06.02.03, and my XTS5000 Mod 1 has R02.20.02 The IMPRES battery that I have affects both radios equally. I'm leaning towards some type of a fault in my battery.


-Marc

Posted: Thu Feb 09, 2006 4:29 am
by wavetar
It's possible, the batteries have their own logic board inside, and though I haven't taken one apart yet, I assume there's frequencies being generated in there which could cause problems if improperly shielded.

Here's something to try...put a small piece of electical tape over the center pin on the battery. That's the pin which 'talks' to the radio. In the XTS3000, covering that pin eliminates the problems. Maybe it'll do the same for you. Of course, you'll lose things like your battery gauge & other 'smart' information...but at least you'll have narrowed it down a bit more.

Todd

Posted: Thu Feb 09, 2006 1:10 pm
by Mfire39
Ok, so I put a strip of tape on the center pin of the battery and put it on the radio. None of the smart battery info appeared like you said it would. The radio gives me the same problem. My other Mod 1 also acts the same with the tape in place. Now, I did mannage to dig up an older IMPRES battery with a 2002 date code. It works great on both XTS's with no problems. So I think I might be able to narrow it down to, the IMPRES battery that I have is a faulty one. To date, I have tried about 4 other batteries including another IMPRES with no problems reported on both radios. So I guess my next question would be, is there anything that can be done with this possible "faulty" battery? IE, return/exchange since it's only about a month old?

Thanks,

-Marc

Impres

Posted: Thu Feb 09, 2006 1:24 pm
by 2wayguy
Call motorola parts and they will replace it if the date code shows it is only a month old. I have sent several back and they replaced them, no problem.

Posted: Thu Feb 09, 2006 2:26 pm
by Mfire39
I think thats what I'm going to end up doing.

-Marc