Hello All--I got my robot back from the shop for calibration.
I just sent in the robot itself (no collector, radio, etc). I try to connect through the nomad with Spectra Pro like normal--and the robot keeps connecting, disconnecting. I will be on the rod, the robot will power on, it does its 180° initialization, I hit search and the robot turns off and back on again--bringing me back to the level bubble. Radio on the software says 'good' radio connection. But whenever I hit a command in survey pro remote control, it resets. Any thoughts?
The top problem to troubleshoot with that gun, from my experience, is the cable from the DC to the radio. When that is going bad, it does very odd things.
Second thing to try is switching out is both antennas.
Third think to look at is the battery on the radio. If it's just slightly loose, it will break communication for a split second, and often try to reconnect, when you jar or tap the rod down. Try genitally prying out the battery prongs on the radio, or using a little contact cleaner there.
I'd say those are the three most common problems that I've seen, but there are many things that can go wrong, and may need a professional analysis to figure it out.
> Try genitally prying out the battery prongs on the radio, or using a little contact cleaner there.
Oddly, that is something I would have never thought to suggest. Jim Frame might have, though.
Or...this has not happened to me, yet, but I've heard of it from a friend: when it was at the shop, they upgraded the firmware on the gun and now it's not compatible with your DC. This is Trimble after all...
Thanks guys. I tried the battery thing, didn't help matters. I will order some new antennas. Don't think it's the collector cord, works well hooked to the gun. My other suspicion is the nomad bottom port after that.
One other thing that occurred to me is that you said you just got it back from the shop. You should ask your service techs if they "updated" the firmware on the gun. They often do that automatically when you bring them in for service. Sometimes the DC/Software doesn't play nice with the onboard Robotic software, and we had some issues after firmware updates. This actually does sound like it could be a software conflict, since issuing commands on your DC seems to cause the gun to go haywire.
Edit: Just saw that Eric beat me to it. I didn't go back and read the prior posts before posting.
I had that happen on my Focus and it was the battery on the radio at the pole. Several years ago I had a 5603 where they updated the firmware during a service and I had to upgrade my data collector software after a couple of months gong back and forth before I realized what was done.
