Yesterday, I went out and set up one of my R8's on?ÿ a point where I was hoping to get a 4hr minimum observation for aN OPUS share.
?ÿthis point is on a rock outcrop and I figured the setup would be stable for the entire time without a lot of leveling problems due to melting ice/ thawing/ etc.
I set up start my base?ÿfile and begin logging data in the rcvr head via the GNSS functions/start base/fast static route in the data collector.
?ÿI had a cammie in the head and the cowbell hooked up.
?ÿI come back about 5 hrs later to pick up- everything is level, life is good, I shut down and go back to the office..... where I find I have 2 files....
?ÿone is about an hr long the other is about 3 hrs long and there is a a 50 minute gap between the files....
how in the froghair does it stop logging, wait 50 minutes and start a new file -ON IT'S OWN- and begin logging again?
?ÿThese heads have never been configured?ÿto begin logging on startup....
Here's the header for the 2 files....
?ÿ
-
?ÿ
?ÿ
?ÿ
If the power was interrupted then restored the receiver would go back to doing what it was doing before. The question is how did it lose power for 50 minutes and then come back to life? Very strange.
I have an R10 that we were using as a base day after day, and then one day did not collect any data at all. I pulled up the WebUI and looked, and data logging was disabled, it had always been enabled before and in fact collected data the previous day. Had another problem with the modem, so sent it in for repair. I carefully explained about the data logging problem. They replaced the modem, not sure if they did anything else. It actually went out to Trimble, not just the dealer's shop.
Got it back last wednesday. I wanted to test to see if there was any difference in height due to the presence or absence of an internal battery (there is, about 1 cm). So, I ran it continuously for a week (external power). Ran fine for six days, creating hourly files continuously. Yesterday, at 21:55 UTC it stopped collecting data. I could not log in from either the cell modem (static IP) or by wifi (it was connected all week to my office wifi as a client), but it was still powered on.?ÿ
I brought it in, power cycled it, it connected right up to wifi, and data logging was disabled. Not sure how that gets changed, but obviously Trimble was not able to fix it (maybe they never even were able to replicate the problem).
When it did not log data previously, it cost me an entire day in the field that had to be redone.?ÿ?ÿ
?ÿ
?ÿ
I had an R10 collect with a gap or gaps in the data.?ÿ Loyal helped me make use of the file (RS) and it did have gaps.?ÿ Weird, never did figure it out.?ÿ Haven't used it for static since, will test it before I do.?ÿ Before that I had collected some static files just fine.
here's the set up-
?ÿ
?ÿThat dude on the fence post was messing with you.
?ÿ
If I read the files correctly, it thought the antenna dropped 5 cm between sessions.
And the marker name changed.
Do those match any other sessions in memory?
Wouldn't that be something if it turned out you could start and stop logging with a click of a garage door opener?
Just because I'm paranoid, doesn't mean they aren't out to get me.
First order bench mark in rock outcrop - doesn't get any better than that except for limited sky visibility and the power lines overhead.?ÿ At least the south sky is open.
https://www.ngs.noaa.gov/cgi-bin/ds_mark.prl?PidBox=TN0453
I see this is a re-occupation, so you'll know if the results are close.?ÿ
You folks are to be congratulated on the number of OPUS shares submitted in your area.?ÿ There are more shares in your zip code than in several counties combined around here.
Well my measure up was 1.832 meters to enter bumper the marker name in the 1st file was incorrectly keyed in as L428 as is shown in the 1st file the new height is something random and the default marker name in the 2nd file is the last 4 of the head serial number. I don't think I want to spend the time researching the HI measure up back thru the last ??? # of days of use.