XTL2500 XTL 2500 Won't Communicate with CPS

[steinberg]

Hello all, I've been lurking around the site for a little while now, but I seem to have run into quite the boggling issue.

I have a Dash Mount XTL 2500 FW R14.00.03 that powers on and seems to function normally except it won't communicate with the CPS. I am using a rear accessory port OEM Moto serial cable and have tried CPS 20 and 20.01 on both a windows 10 desktop and 32bit windows xp laptop and get the same "Radio Failed to Acknowledge Error Context: 24, Status: c0000386" error. I've tried Flashzap mode and converting to a remote mount with the same results. Note, I have not tried any type of GCAI cable.

I know the cable and CPS are good because I can read and write to other XTL2500s.

The radio was previously cloned using a rear accessory OEM Moto USB cable on a different windows10 computer. I've tried on my machine to use a thrown together home brew USB cable but the radio shows up as an unknown USB device without drivers.

At this point I've just about run out of ideas short of picking up a GCAI cable and/or driving back across town to try the cable and computer that cloned it previously. Any ideas or suggestions?

 

[MotoBill]

If you haven't already done so, I would try reading another XTL to verify that your PC isn't at fault. I just went through this a couple of days ago myself whereby the Astro25 driver(s) for some unexplainable reason became corrupted and had to be reinstalled before CPS was able to communicate with any of my XTS/XTL radio's.

 

[jry]

try the rear USB port ...just need to sacrifice a USB cable and crimp the pins on

also make sure all the rs-232 pins are fully extended and haven't been pushed back into the connector body.

 

[steinberg]

If you haven't already done so, I would try reading another XTL to verify that your PC isn't at fault. I just went through this a couple of days ago myself whereby the Astro25 driver(s) for some unexplainable reason became corrupted and had to be reinstalled before CPS was able to communicate with any of my XTS/XTL radio's.

Yep, I tried 2 other XTL2500s and my XTS5000, all of which will read a write just fine.

try the rear USB port ...just need to sacrifice a USB cable and crimp the pins on

also make sure all the rs-232 pins are fully extended and haven't been pushed back into the connector body.

Rear USB port on the radio or the computer? I did try making my own USB cable for the rear port on the radio, but when I plug it in the computer doesn't recognize it and can't find any drivers.

The pins are all good.

 

[steinberg]

If you haven't already done so, I would try reading another XTL to verify that your PC isn't at fault. I just went through this a couple of days ago myself whereby the Astro25 driver(s) for some unexplainable reason became corrupted and had to be reinstalled before CPS was able to communicate with any of my XTS/XTL radio's.

I apologize for the late reply, I thought I submitted a reply earlier this morning.

Yes, I have confirmed with 2 other XTLs and a XTS portable that the cable/keyspan and PC/CPS are functioning normally. I'm not sure I've come across any other forum threads about this, but are there any known issues with XTLs not liking rear accessory cables? From what I recall I thought the rear port was the most reliable.

try the rear USB port ...just need to sacrifice a USB cable and crimp the pins on

also make sure all the rs-232 pins are fully extended and haven't been pushed back into the connector body.

I have tried making my own rear USB cable. When I plug it in the computer shows the radio popping up as an "Unknown USB device (Device Descriptor Request Failed)". I'd assume this is a driver issue, but as far as I know the most you can do to troubleshoot this is to reinstall the CPS, which I have.

Pins on the cable are all good.

 

[MotoBill]

With USB a no go, you still have the option of using RS-232 Serial from the rear accessory port. If necessary, you can add pins to your existing 26-pin USB Programming Cable per the signals (pins) shown in the table below under the DB9-F column. Ignore the color code as they reflect a specific cable that I used to fabricate my own programming cable.

If fabricating from a blank connector them be sure to include the Emergency jumper, and optionally the Ignition Sense and Speaker leads as needed.

 

[Number 6]

1. Remove the head.
2. Use a rear serial cable and a computer with a real serial port.
3. Make sure that you select the correct com port.
4. Upgrade your deprecated firmware to the last version.
5. Try reading the radio.
6. If no success then reinstall the head and try a serial GCAI cable at the front.
7. If no success then take radio to range and put it down.

 

[jry]

sounds like your last option is the GCAI cable

Will have to try the rear USB on one of mine and see what it shows for the driver

Made a cable that had both ....RS-232 I use for Auto Tune

 

[Colt45ws]

I made a rear USB cable for a XTL in a consolette recently. Actually I wired it to a panel mount female USB-B which I installed in the rear panel. So I can plug in to it with a common USB-A to USB-B printer cable and reprogram the thing without popping the case.
Anyway I got that USB error on my first try, Windows does not recognize the device. I swapped the data lines and it worked after that. The jumper I bought was wired backwards I guess, but that was the fix for me.

 

[com501]

To work on XTLs succesfully you have to have 4 (four) cables. GCAI USB and Serial, and rear accessory USB and Serial. Number 6 has the right idea. 14 and 17 were two notorious problem children. IF the radio still is functional you can try the serial front approach after doing the steps Number 6 suggested.

NOTE: Look carefully at the handy pictures that Motorola provides when the radio fails. They are ALL SERIAL cables.

 

[steinberg]

With USB a no go, you still have the option of using RS-232 Serial from the rear accessory port. If necessary, you can add pins to your existing 26-pin USB Programming Cable per the signals (pins) shown in the table below under the DB9-F column. Ignore the color code as they reflect a specific cable that I used to fabricate my own programming cable.

If fabricating from a blank connector them be sure to include the Emergency jumper, and optionally the Ignition Sense and Speaker leads as needed.

I guess I should clarify haha, I have an OEM HK6160 and home brew USB cable. Thank you for the diagram though, it'll come in handy if I ever need to make another cable.

1. Remove the head.
2. Use a rear serial cable and a computer with a real serial port.
3. Make sure that you select the correct com port.
4. Upgrade your deprecated firmware to the last version.
5. Try reading the radio.
6. If no success then reinstall the head and try a serial GCAI cable at the front.
7. If no success then take radio to range and put it down.

Got it, will try.

I also hate to ask, but is there anyone who has ibutton(s) with valid refreshes left? I think the jump from 14 to 20 is too large for the "dirty" method. Would upgrading to say 15 via the "dirty" method be a better than nothing solution until I can find an ibutton with valid refreshes?

Thank you all for the suggestions, I will continue to troubleshoot here, and report back.

 

[Number 6]

I guess I should clarify haha, I have an OEM HK6160 and home brew USB cable. Thank you for the diagram though, it'll come in handy if I ever need to make another cable.


Got it, will try.

I also hate to ask, but is there anyone who has ibutton(s) with valid refreshes left? I think the jump from 14 to 20 is too large for the "dirty" method. Would upgrading to say 15 via the "dirty" method be a better than nothing solution until I can find an ibutton with valid refreshes?

Thank you all for the suggestions, I will continue to troubleshoot here, and report back.

Where are you located?

 

[steinberg]

Where are you located?

Los Angeles area.

 

[Number 6]

That’s about 400 miles so it would be a bit of a hike. You could mail the radio but that could be expensive.