Waas float processing

Nate The Surveyor

Well-Known Member
Ok, what did you do, and what was your goal?
Was your base set up, but you were beyond radio range, and you got a waas shot, and you need to crunch it against your base?
Or ?
Was your t3 not set up, but you set your LS on an unknown point, for 30 min, and you want to process that file?
I'm guessing, but you have some options here....
 

Steven hill

New Member
Ok, what did you do, and what was your goal?
Was your base set up, but you were beyond radio range, and you got a waas shot, and you need to crunch it against your base?
Or ?
Was your t3 not set up, but you set your LS on an unknown point, for 30 min, and you want to process that file?
I'm guessing, but you have some options here....
My base was set , 35 w radio and i was 400 ' away from intersection of fences where i simply needed to get alinement of prior occupation for a survey in the middle of forest. Also, i need this procedure in my knowledge so i can learn how Waas can be implemented to set nails in unforgiving ravines and razor back hills. I lose radio with many of these jobs and no phone service
 

Nate The Surveyor

Well-Known Member
OK, first off, think in terms of Base to Rover processing. WAAS float is a part of the Javad Philosophy of giving you the BEST answer as fast as it can. So, it gives you a coordinate that is often within 5 or so feet.
But, now we are going to BASE to ROVER processing.
So, AFTER downloading the BASE file to Rover.
Press POINTS. Highlight the point that was processed via WAAS.
Then press the 3 bars. (resource button) then Right arrow twice.
Then press Post Process selected point. It will now process the point.
Now, be sure to select the RTPK value, over the RTK point. The RTK point I believe is the WAAS or field point. The Post Processed RTPK point is the good one. You generally will want to make 3 shots, maybe of 5-8 minutes each. This will usually give you three points that agree within a few hundredths.
Anyway, This is a great function.
Nate
 

Michael

Active Member
OK, first off, think in terms of Base to Rover processing. WAAS float is a part of the Javad Philosophy of giving you the BEST answer as fast as it can. So, it gives you a coordinate that is often within 5 or so feet.
But, now we are going to BASE to ROVER processing.
So, AFTER downloading the BASE file to Rover.
Press POINTS. Highlight the point that was processed via WAAS.
Then press the 3 bars. (resource button) then Right arrow twice.
Then press Post Process selected point. It will now process the point.
Now, be sure to select the RTPK value, over the RTK point. The RTK point I believe is the WAAS or field point. The Post Processed RTPK point is the good one. You generally will want to make 3 shots, maybe of 5-8 minutes each. This will usually give you three points that agree within a few hundredths.
Anyway, This is a great function.
Nate
Nate,
When you process the point this way, is it using the RTPK in the LS+ or are waiting to get internet connection to DPOS? Mike
 

Nate The Surveyor

Well-Known Member
Yes, and.... If you return to base, connect base-rover, but don't shut down base, you can still do the above steps..., it will pull the base data from the base, via Bluetooth. (I've not tried this, but was told it would work).
N
 

Nate The Surveyor

Well-Known Member
Another thing. Go buy a cheap painters pole. Drill out the top, and install a piece of 5/8 x 11 bolt. Elevate base UHF antenna as high as you can.
Rtk and RTPK both will be better.
N
 

Nate The Surveyor

Well-Known Member
Just an interesting note. If you go to the woods, shoot 75 shots, and some of those shots you just stored RTK values. You did NOT wait for RTPK.
You come home, and DPOS it. (But not with base-rover, because you are using RTPK), and point 4775 shows red, because DPOS value does not agree with RTK. (Please note, it seems to process base to rover, ANYWAY, even though base rover is not turned on, because there is no RTPK value in the LS).
Now, do the above procedure, to process that one point 4775, with RTPK. And.....
It gets it right, and now the RTPK value changes, (from DPOS value) to RTPK value.
This is most interesting information.
Nate
 

Michael

Active Member
Just an interesting note. If you go to the woods, shoot 75 shots, and some of those shots you just stored RTK values. You did NOT wait for RTPK.
You come home, and DPOS it. (But not with base-rover, because you are using RTPK), and point 4775 shows red, because DPOS value does not agree with RTK. (Please note, it seems to process base to rover, ANYWAY, even though base rover is not turned on, because there is no RTPK value in the LS).
Now, do the above procedure, to process that one point 4775, with RTPK. And.....
It gets it right, and now the RTPK value changes, (from DPOS value) to RTPK value.
This is most interesting information.
Nate
Would you have the base setup and running even if you are not getting communication between base and rover (assuming you have DPOS known base already) and download the base to the LS when get within blue tooth range and then RTPK?
 

Nate The Surveyor

Well-Known Member
Michael, you can (apparently) do it either way. It's a timing issue. Do you NEED that data to compute, and finish your days work? IF so, download it while the base is still running.
If you don't need it immediately, take it home and DPOS it. HOWEVER, DPOS does not process it as RIGOROUSLY as RTPK does. So, if there is any worry, as in, its a woods shot, I'd go straight to RTPK, or DOPS it, and store that value on a thumb drive, (EXPORT COORDS) and then Post Process it , via the RTPK engine, and see if it changes the coord. IF it does change it very much, I'd assume the RTPK is more likely to be good. HOWEVER, all these woods shots, need redundancy. Shoot them at least 2x.
But, get your UHF antenna up as high as you can.
And, if you are experiencing REDUCED range, towards the end of a day, your base battery may be getting low. Javad gear LIKES hot base batteries.

N
 

Nate The Surveyor

Well-Known Member
AFTER downloading the BASE file to Rover.
Press POINTS. Highlight the point that was processed via WAAS.
Then press the 3 bars. (resource button) then Right arrow twice.
Then press Post Process selected point. It will now process the point.
Now, be sure to select the RTPK value, over the RTK point.
I want to bring up another use for this feature.
You went 2 miles from base, into a little ravine. Signal was very spotty. You took 3 shots, that were 5 min ea. Set a nail. Returned to base, and went home. Base is downloaded.
Your 3 ravine shots were not too good.
Now use this form of post processed RTPK, that I've listed above. It still does not give you rtk. It's still just as spotty. BUT, RTPK in post process form is as solid as a rock. 3 shots from RTPK that are usable. You are using RTPK to fill in the spotty radio. In that location.
It works.
I've used it on prev field shots where rtk and RTPK did NOT agree in the field, (due to a few missing epochs). Now, post processed RTPK in its FULL form cleaned up, and RTPK in the office, resulted in a good RTPK shot.
;)
N
 

JoeD

Member
I had a similar situation a week ago here in the UP of Michigan. I had to locate a corner in a not so nice a location that I never wanted to go back to again.
I set up my base (T3 with 35 w radio) and clawed my way through brushy ravines to the 1/4 corner I needed to locate. When I got there, I had no radio link. No problem, I had contingencies. I had a Topcon Hiper Plus running on a known point a couple miles away that I could post process with Post-Processing software to, along with the T3 base. I set up the LS and ran about an hour of WAAS float. The area around the corner was not that thick so I thought I was good. Then I discovered that my Topcon Base had a hiccup and thought it was 1988. No problem, I would DPOS my T3 base and Post-Process from that to the corner and also DPOS the corner session as a check. Again, everything failed. As luck would have it, all the CORS stations within a fifty miles were down that day. (October 5). After reading this post, I tried the procedure described by Nate. Again, no luck. I got a "Failed (No solution for this vector.) Is there anything left to try, or was October 5th just the GPS day from hell?
 

Nate The Surveyor

Well-Known Member
I'm thinking if you could fractionate that 1 HR file, into 5 minute segments, and process them individually, you may have what you want/need. Probably discard some of those 5 minute ones too. 5x12 is 60. So, you could get several of those files to yield the truth.
Nate
 
Top