XPR6350 USB Issues

[axel]

So I'm coming to DMR from the P25 side of things. Got ahold of a 6350 for cheap and am trying to get it programmed and bring it up to speed firmware wise.

I'm on Win10 and running CPS 13.0.666, and I've got what should be a legit Moto USB cable. For some reason, CPS is being very picky.

First I found that the cable didn't like my USB 3 ports very much. That wasn't too shocking as some other USB devices of mine don't like them either. Moving over to USB 2 let me read the radio just fine. I fiddled with some basic settings and rewrote the radio as a test. It seemed to work fine. Changed a few more settings, went to write the radio again, and it failed saying it couldn't find the radio. I closed CPS, rebooted the radio, restarted CPS, and could read it again.

It seems like every time the radio reboots, after a codeplug write or power cycle, CPS looses connection with it entirely and both the radio and the software have to be restarted to program them again.

Additionally, I attempted several times to update the firmware to 1.12.17. It's on 1.08 right now and I'd like the audio fixes and other improvements that come with 1.12. After following the above restart procedure, CPS gets to 24% on the firmware upgrade and then fails with error #9470. I tried an update two more times and the same result came up every time. Fails at 24% with error #9470.

I'm back at work now, but when I get home tonight I'm going to fiddle with things some more. I'd appreciate advice from anybody who's had similar issues. I know for some they had to go through one or two steps of firmware updates to get to 1.12. I might try and get ahold of an older version of CPS and see if the problem resolves.

Cheers

 

[Mars]

You're not alone. I have had to perform the firmware update at least 20 times on the 6350, in order for it to take. Like you say, it crashes constantly and does not complete.

The firmware update is a batch job. I suspect there are timing issues. The percentage is just an indication of where in the batch job it is failing. It's unfortunate no one at Motorola is volunteering to debug the process.

 

[axel]

Well good to know I'm not the only one with issues. I'd expect no less quality from those fine folks over at MSI.

I'll keep massaging it tonight and hopefully it'll go through.

 

[Viper1-6]

Well good to know I'm not the only one with issues. I'd expect no less quality from those fine folks over at MSI.

I'll keep massaging it tonight and hopefully it'll go through.

Unless it is being used on a proprietary Motorola trunk system, you would be better off dumping the POS(software&shareware) and invest in Tait, Hytera or, God forbid CSI... It is obvious Motorola can not, or will not pay decent money for decent software engineers.

 

[Gtaman]

I had all kinds of issues with mine on windows 10. On my Windows 8.1 machine I have never had any major problems. I did have to reinstall the USB driver but the cable works fine on my 3.0 ports. I had a few firmware update issues but they all fixed themselves. The only issue I have is every damn time I unplug and plug in a radio it creates a network device connection. I think I'm at network "36" now.

 

[axel]

I'll have to play around with drivers a bit.

Trust me, if I were going into the DMR game in any serious capacity I'd either be going with gen 2 stuff or with something from Tait. I picked up this like-new 6350 for $100 with all accessories and it was only to be able to use the club's DMR machine when I need to. Otherwise we're primarily P25.

 

[Alpha]

I had all kinds of issues with mine on windows 10. On my Windows 8.1 machine I have never had any major problems. I did have to reinstall the USB driver but the cable works fine on my 3.0 ports. I had a few firmware update issues but they all fixed themselves. The only issue I have is every damn time I unplug and plug in a radio it creates a network device connection. I think I'm at network "36" now.

Go to Network and Sharing Center, under "View your Active Networks", click on the weird blue building icon on the far left side of the pane. That should bring up a "Set Network Properties" window. Click on the link at the bottom "Merge or Delete Network Locations". That should bring up the "Merge or Delete Network Locations" window. There, you can see all the network location names it has memorized, you can delete the inactive ones - "Network", "Network 1", etc. You can shift-select multiple ones and delete them all with one keystroke.

That won't keep it from adding new ones every damn time, but at least you can delete them as you go. I have NOT yet figured out how to delete the ghosts of radios connected - the "Network Adapters" that get created each time a new radio is hooked up to the system like "APX Radio #4", etc., but at least I have figured out half the problem. Sheite software written by clueless morons.

 

[com501]

Go to Network and Sharing Center, under "View your Active Networks", click on the weird blue building icon on the far left side of the pane. That should bring up a "Set Network Properties" window. Click on the link at the bottom "Merge or Delete Network Locations". That should bring up the "Merge or Delete Network Locations" window. There, you can see all the network location names it has memorized, you can delete the inactive ones - "Network", "Network 1", etc. You can shift-select multiple ones and delete them all with one keystroke.

That won't keep it from adding new ones every damn time, but at least you can delete them as you go. I have NOT yet figured out how to delete the ghosts of radios connected - the "Network Adapters" that get created each time a new radio is hooked up to the system like "APX Radio #4", etc., but at least I have figured out half the problem. Sheite software written by clueless morons.

They used to show up in Device Manager when you viewed hidden devices. I don't know where they go now either.

 

[com501]

As an aside, Trbo network adapters should always only have IPv4 checked. Everything else should be unchecked.

 

[axel]

Finally was able to get the radio updated to 1.12.17. Had to fire up the crusty toughbook running Win7, but it seems to have worked. It failed during the update at around 80%, but then when I tried running it again it said that my radio was on the latest firmware. It also erased my codeplug, but I wrote it back and it seems to be fine now.

Interestingly, the radio has no talk permit tone on keyup. It's not disabled, and there's no option for it. Is there something I'm missing here, or do the 6350's not have the option for a talk permit tone? It's useful to have on DMR repeaters so you know you've made it in.

 

[Gtaman]

Finally was able to get the radio updated to 1.12.17. Had to fire up the crusty toughbook running Win7, but it seems to have worked. It failed during the update at around 80%, but then when I tried running it again it said that my radio was on the latest firmware. It also erased my codeplug, but I wrote it back and it seems to be fine now.

Interestingly, the radio has no talk permit tone on keyup. It's not disabled, and there's no option for it. Is there something I'm missing here, or do the 6350's not have the option for a talk permit tone? It's useful to have on DMR repeaters so you know you've made it in.

Mine did that. It's the buggy ass firmware. Uncheck it. And write the radio. Then recheck it and write back. See if that fixes it.

 

[axel]

<disregard>

Forgot about basic/expert views.

 

[Mars]

Finally was able to get the radio updated to 1.12.17. Had to fire up the crusty toughbook running Win7, but it seems to have worked. It failed during the update at around 80%, but then when I tried running it again it said that my radio was on the latest firmware. It also erased my codeplug, but I wrote it back and it seems to be fine now.

Interestingly, the radio has no talk permit tone on keyup. It's not disabled, and there's no option for it. Is there something I'm missing here, or do the 6350's not have the option for a talk permit tone? It's useful to have on DMR repeaters so you know you've made it in.

You just screwed your radio by writing your old code plug back to it.

Unfortunately, all of the changes are in the encrypted XML file, which is your code plug. By writing the previous version back, any changes gained during the firmware upgrade are lost.

The only way to fix this is to perform a recovery.

Do not write old code plugs to your radio. I have posted on this issue before. It is something Motorola refuses to address because they're mentally retarded.

 

[com501]

You just screwed your radio by writing your old code plug back to it.

Unfortunately, all of the changes are in the encrypted XML file, which is your code plug. By writing the previous version back, any changes gained during the firmware upgrade are lost.

The only way to fix this is to perform a recovery.

Do not write old code plugs to your radio. I have posted on this issue before. It is something Motorola refuses to address because they're mentally retarded.

^^^^ What he said. Recover the radio then do a drag and drop. MARS is 100% correct, do NOT write your old codeplugs to radios!!

 

[axel]

The thought didn't even cross my mind. When it powered on as unprogrammed I had an "oh shit" moment and quickly wrote the radio, hoping I didn't really screw something up in the update process.

It's a small codeplug so it shouldn't be too hard to D&D everything over. Thanks for the heads up. I probably wouldn't have noticed a difference otherwise until I started getting poor audio reports.