This morning I was observing a 3-hour static session with a 4000SSi. Around the middle of the session I walked over to due a routine check on the receiver, and saw a message on the display that said something like "No SVs tracked." I didn't take the time to write the message down, I just hustled back to the truck and grabbed another receiver to swap in. When I looked at the file later, it shows between 5 and 9 SVs the whole time, with 8 at the end.
The stop time is about right for when I shut it down (I neglected to write that down, too -- I was focused on salvaging the session). There's about an 8-minute interval between the stop time on the suspect unit and the start time on the replacement, which seems a few minutes long, but it seems unlikely that I happened to walk over just when the receiver stopped tracking satellites.
I don't know what to make of this. Have any of you ever run into this kind of problem?
> I don't know what to make of this. Have any of you ever run into this kind of problem?
I can definitely say that I have not seen that happen with my 4000ssi. I wonder if there's a problem with the antenna cable. Was it windy today and was the cable flopping around?
> I wonder if there's a problem with the antenna cable. Was it windy today and was the cable flopping around?
It was dead still, and I didn't disrupt the cable at any point in the session, so I don't think that's it. (I wish it was!)
Sorry I can't help, but some may say using a 4000ssi in 2015 is odd behaviour 🙂
> Sorry I can't help, but some may say using a 4000ssi in 2015 is odd behaviour 🙂
Do you think they'd forgive my oddness when they saw me swap in a 4700 when the 4000SSi went goofy? I mean, that's a whole generation newer!
Next Jim, we will find out you have a 5700! Just giving you a hard time, shoot I am still using a TS from 1998, but it works for what little I need to use it, so I will continue to do so until it won't.
Have you thought about replacing that one with a X90 OPUS. ONE LOST STATIC SESSION COULD COST MORE THA AN x90 OPUS.
4700 is a great receiver except it only has indicator lights.
We were doing a small triangle, static while we hunted for boundary monuments.
I found two pipe, brass cap control monuments set in the 1990s at a fire station in the state forest. I staked out the third with the S6, found it. Then we set a couple more control points with better sky visibility plus we need them for topo. I then left the S6 up and running. I set up the RTK base (R4-3) with the robot controller. Then I go to second new point, get an RTK shot to have a point to start a Faststatic base. At this point there is some arguing between the robot and the R4 (Bluetooth) about who gets to talk with the controller. We go to another point with our second rover to do the same. Nothing from the base. Go over there with the controller. The base stopped being an RTK base and stopped storing the file. Start it up again and start the second rover as Faststatic base and no glitches after that.
I've never had them stop like that. My working theory is it had something to do with the interference from the S6 but I don't know for sure.
Classic description of a bad cable. The same issue was resolved with the office base by replacing the cable to the antenna, it was connected and was never touched or moved beyond attaching it to a receiver and it still went bad and started causing a loss of satellite message.
> 4700 is a great receiver except it only has indicator lights.
I agree. While I miss the ability to enter station name, filename, antenna type and height, and to monitor power sources more finely than blink/no-blink, I may start relying more on the 4700s now that I've had a couple of my 4000-series receivers begin to go funky. I do have a TSC1 I can use to control some of those features, but that complicates the logistics a little.
> Classic description of a bad cable.
I'd be more inclined to think it was the cable if the data was, in fact, not being received. In this case, though, it looks like the SVs were being tracked and recorded, despite the message displayed. It's *possible* that I happened to walk over to the receiver within a minute or so of the cable crapping out, but it seems unlikely.
That's what the cable to the base would do. It would work then go to 0 then see 8 then back to 0 finally the cable was replaced and its worked for years no problems.
If you have replacements I'd try it for a test to isolate the problem. Eliminate the cable as the issue.
