T3 Base got knocked over

I was working in rural Clay County in Northeast Mississippi today. My convenient base station setup was in a pasture with a herd of about 20+ cows. They were on the other side of the pasture, and seemed to be happily munching away on fresh green grass.
I got my T3 communicating with my LS+ using Bluetooth and UHF, got green lights on my “collect” screen, and was good to go. I worked for a few hours collecting a few hard points using the new “canopy” collect style and the rest using the “precise topo” collect style. I was standing on two logs I had thrown in a ditch with about one foot deep of water and out about four feet from the bank to an iron pin that I needed to locate. I managed not to fall in, and was collecting my point when I noticed the yellow flashing box on my screen.
Wups, the base has moved.
I suspected curious cows, so I went back to my ATV, drove to the base station, and confirmed my suspicions. A herd of cows must have given my base station on a two-meter tripod a really good and curious inspection, and had knocked it over. It broke my Bluetooth antennas and knocked the rubber cover off the UHF antenna. And to show their contempt for a strange object in their pasture, one of them took a dump about two meters away and had his buddy knock my base station tripod over into the fresh pile. I retrieved my tripod and T3, went to the stock pond, cleaned the green stuff off with a rag soaked in pond water as best I could. There was green stuff lodged in the locking levers on the tripod head, and crammed into the joints pretty good. Oh, well. I cleaned it up and moved on.

My question is this: I need to DPOS today’s data. Has anyone had issues with running DPOS on a base station that was moved? The last 20 minutes or so of my roughly four hours of base data has been compromised. Will JUSTIN data processing at JAVAD ”see” that the data has an anomaly at the end of my base data file and automatically remove the bad data? Will I need to “fix,” or edit my data before I send it off to DPOS? How in the world would I do that? Need comments and suggestions, please. I think that only one point will be bad, and I collected new data on it from a new base setup on my hard points and the old base point, just to compare the numbers.

9163CDD8-788B-4EDF-A027-DF67666C827F.jpeg
63D633AA-A351-4E44-A3F5-123C336E1202.jpeg
 
Last edited:

Nate The Surveyor

Well-Known Member
Harold, I've had my base knocked over 2x. (Pre javad Topcon legacy e)
I bought this:
It's now been discontinued. And, I bought 5 fiberglass reflectors, 3 ft long.
And some plastic and stainless steel fence wire. It works well.
Sorry I can't help with your questions.
But I can say that a 12 volt fence charger will help alot!
Nate
 

ken larson

Active Member
Not the same, but I lost connection between the lsplus and the t3 this week. The base was on an autonomous location. 30 min in I had to reboot the rover and base and they reconnected and I went on with 2 more hours of location. When I went to DPOS, the base not only quite collecting raw data after the crash, but it revised its location. I ended up with two islands of data that were unrelated and only a 30 min occupation on the base to process.

I seem to have a disconnect issue often around noon EST.
 
Hey Harold, share the files. I will try to help.
Alexey:

I sent the two files to DPOS and had the JUSTIN software process the data. I read on another thread that someone had a similar problem, and the software recognized an anomaly at the end of the base data file. It appeared that the base file processing had eliminated the bad data.
My fieldwork continued after I drove back to the base station site. I picked up the base station tripod, leaned it against my ATV, connected with my LS+, and stopped and downloaded the data. I had roughly 15 to 20 minutes of bad data at the end of the file. I then turned off my LS+ and the T3.
I set up on a new base site and started everything up again, connected, and continued work. Just to make sure that I was getting consistent and reasonable data, I went back to three "hard points," - an iron pin found, an old setup nail, and my first base station point. I used the new "canopy" point collect style and had green "RTK FIXED" lights, and JFIELD completed the measurements. I took a couple of shots (I rotated the prism pole with bipod 180° between shots) on the iron pin and the first base station.
The processed point coordinates looked very close to me. The difference in Northings from my first base setup and the same point shot from my second base setup was 0.0755 feet; and the difference in Eastings was 0.0131 feet. I do not use the elevation z-ordinate in this type of work I do. I can attribute some of that error in the accuracy of my base station level bubble and my prism pole level bubble. I will consider these differences in error acceptable for my rural Mississippi work.

I am attaching four text files that were generated from my two DPOS base station submittals. Please understand that I am by no means an expert in interpreting the data returned. If these files will tell you what you need, please let me know. If I need to get you the RAW data files, please tell me how to do that.

I appreciate your willingness to help. I am satisfied that my numbers are good, and I plan to go with what I have. I would appreciate any input that you may have.

Thank you,
Harold Dendy, PE, PS
Dendy Engineering and Surveying, Inc.
rhdendy@hotmail.com
 

Attachments

  • 500_101257.jps, 501_102643.jps, 502_103202.jps... [57].txt
    109.9 KB · Views: 109
  • 500_101257.jps.txt
    2.8 KB · Views: 116
  • 600_153050.jps, 601_153517.jps, 602_153838.jps... [18].txt
    37.1 KB · Views: 112
  • 600_153050.jps.txt
    2.8 KB · Views: 120

Bryan Enfinger

Active Member
Why not convert the base files to rinex and trim the bad part out ?
You can either PP yourself or send to OPUS.

Post processing with Justin 3 is fun ! It's amazing what it can do with a little data and closed loops.
 
Top