I had an issue with Base Guard on Friday, ( the 13th.), I would like to share and possibly get some feed back. I am running JField 2.0.5.992 together with 3.7.2, Aug, 31, 2017 on the T2. The job I had the issue on is the third job I have started and completed since the upgrade noted above. Jobs 1 and 2 went off without a hitch. I started the third project on Thursday the 12th. in the normal fashion, occupied spike with autonomous position, collected about 40 shots with no issues, and returned to office that afternoon and processed the day with DPOS, all as smooth as glass! On day two, Friday, I moved the base to a more secure location , and started in the normal fashion. I then completed a Real Time Position Shift, checked into two points from the previous day ,with excellent results, and proceeded to collect additional points. All was well for about an hour, when I received the warning on the LS that the Base Station was out of its position by 37 feet, and not moving? To far for the base to have been knocked over. I was about a 1/4 mile away, so it took me a few minutes to get back in sight of the base. The warning continued to state the 37 ft. error all the way back to the base. I found the base undisturbed. I had a corner point within 200 ft. of the base, so I checked in on it, 0.02' hz?? I then powered off the LS , rebooted, applied the Shift again, and checked back into the said corner point with the same result, and no Base Guard warning. I then moved about 500 ft. to another position to collect, with no Base Guard Warning, and started the collection process. Immediately upon the activation of the Start button the Base Guard warning appeared, now with a statement that the base was moved 1,034 ft.?? I went ahead and completed the shot and called it a day. I returned to the office, processed the data with DPOS. Both of the positions I collected while I was receiving the Base Guard warning appear the be correct. Anyone else experienced this, or something like this with Base Guard? Any thoughts? Also, no real loss of production, just gave me a scare. I am beyond pleased with this equipment and the support that goes hand in hand with it, just amazing !!
Base Guard
- Thread starter Steve Hankins
- Start date
The Deviation Gaurd reports the maximum difference between the autonomous position and coordinate the base is transmitting since the time the base was started. If the autonomous position of the base momentarily jumps too far then you will continue to recieve the alert until you increase the threshold or turn off the alert. This can be done at the rover and does not require going back to the base. I feel that the default value of 10 meters is too low for this setting but you can always increase it when you start receiving alerts.
If you move the base 500 feet you need to select a new autonomous coordinate or a known coordinate if you have one. It sounds like you may not have done this when you moved the base.
If you move the base 500 feet you need to select a new autonomous coordinate or a known coordinate if you have one. It sounds like you may not have done this when you moved the base.
Matt, thank you for the quick reply, I believe I understand what was happening now. I did not realize the autonomous position might jump more than 10 meters. I also feel I may not have been clear about the last shot I collected on the second day, under the Base Guard warning. The rover was 500 ft. away from the base, the base never moved on the second day from its initial setup, autonomous position, real time position shift, verification on control. If I understand, the work flow in this situation, once you confirm the base is undisturbed, would be to turn off the warning from the LS, or increase the value from the 10 meters, no need to power off and or restart base and rover. Thanks again for your timely help, I am a fan!!
I'm not convinced that the position of the base jumps that much. It's been a while since I tested the autonomous position of the LS with sbas on, but I don't recall it ever jumping by more than 2 or 3 meters over 24 hours.
Mike Lacey
Member
Had the same issue on Friday, "Base moved 33 feet". Checked the base. checked a few points and everything was good. My Topcon Hiper Lites always did the same thing. After a few times of crying wolf, you tend to ignore it.
I have had the same error pop up. I have also had a couple of calls about it as well.
With that said, I have never seen the 2D Delta be more than 6-7' from truth so I am wondering why this message appears.
With that said, I have never seen the 2D Delta be more than 6-7' from truth so I am wondering why this message appears.
I believe it looks at the 3D delta. I still argue that this is a small probability that there can be 10 m error range as is evident by so many people reporting receiving this alert when it is set at 10 m.
Ronald Murphy
New Member
On last Thursday(3/22/18) we had a notification show up on our Triumph LS stating "Base STN off 47 feet". We had been using the unit for a couple of hours with no problems. I returned to the base to make sure it hadn't been moved or tampered with. Everything was in place. I ended up powering down the Triumph-2 and the Triumph LS and restarted. That seemed to work. We check several points and corners and all was good. Friday, I went to a different job site that we had worked on before and got base and rover up and running and got another notification "Base STN off 913 feet". Could not resolve the issue in the field. Came back to the office and updated the Triumph-2 (the LS is up to date). Returned to the job from Friday and the same notification appeared. Ended up creating new file and entering the same base coords and it worked fine. Why would this issue begin occurring without any changes to the settings in our equipment?
You just need to turn off the base theft guard. It compares the autonomous position of the base to the programmed position of the base. I'd the difference exceeds 10m you get a warning.
I would be concerned about the 900' warning though. Sounds like you may not have started the base with the right coordinates.
I would be concerned about the 900' warning though. Sounds like you may not have started the base with the right coordinates.
Ronald Murphy
New Member
Thanks for the quick response. The funny thing is that when I created a new job today, I used the same base coord as I had attempted to use in the old job file and had no issues. The base coord checked within a few feet of the autonomous position in the old job file and the new job file as one would expect.
That is curious. Hard to say without following all of the steps...
Regarding the warning message, I've found that the Anti Theft Guard is the least reliable monitor we have. I use the base guard feature, I just turn off the anti-theft guard. The other three detection methods are better in my opinion: tilt, Doppler shift and accelerometer. It's very unlikely for the base to move without these sensors detecting it and they are less prone to occasional false alarms.
Regarding the warning message, I've found that the Anti Theft Guard is the least reliable monitor we have. I use the base guard feature, I just turn off the anti-theft guard. The other three detection methods are better in my opinion: tilt, Doppler shift and accelerometer. It's very unlikely for the base to move without these sensors detecting it and they are less prone to occasional false alarms.
Ronald Murphy
New Member
Shawn, thanks again. We appreciate your help. We'll try that and if the issue still persists we will post again.
Bill Eggers
Active Member
Had the same problem today, warning that the base was off 35 feet. This has happened a few times before, usually only when my crew is using the equipment. It behaves better for me.
Will try turning off the Anti theft guard.
Will try turning off the Anti theft guard.
Bill Eggers
Active Member
One question, where do you turn off the Anti Theft?
See http://www.javad.com/jgnss/javad/news/pr20170906.html. The screens have changed slightly since this publication but you get the idea.