MightyMoe, post: 434141, member: 700 wrote: Fast static is not only used for OPUS.
The terms static, fast static, PPK have been used and caused some confusion since the early days of GPS. I think they are more legacy terms that really have little meaning these days. I normally use my PPK style to collect static observations at the rover, and I usually use my RTK-infill to collect static data at the base.
If I'm surveying and lose radio during a RTK-infill survey I will just locate the point in my PPK style, so you can mix and match.
Sometimes I may collect static base data using the PPK style.
I do have a static style that I use for control networks and I always start each receiver as a base, but you can use them as rovers you just have to be sure where YOU told it to store the data in your survey style, the receiver or the DC if you told it to collect in the DC on the rover you have to leave the DC at the receiver as it's collecting. Also, you need to be sure your styles are synced to each other, the PPK base and rover should be timed to collect at 1 sec, 5 sec, 10 sec, or whatever you like. you can't have the rover collecting at 5 sec, and the base at 15 sec. in that case you miss 2/3d of your data.
At the end of the day, a static session, a fast static session, a stationary PPK session produces the exact same data file, all of them could be sent to OPUS if you gave them enough time, and none of them will work with OPUS if they did not get enough time.
Basically you need to watch where you store the file, how long of an interval they are set up for, how long you collected data and with PPK you can move while you survey, while a moving PPK survey will not work with OPUS it sure will work well with CORS.
Ok so you mean what i've seen in webinar video was set to faststatic and not RTK mode coz OPUS don't accept kenimatic data.
OPUS does not support kinematic data. If you want to run RTK and log static at the base simultaneously then your Type under Base Options should be set to RTK & Logging, device to Receiver, and I typically log at 15 seconds - although if you're strictly using OPUS there's no reason to log at any faster than 30 seconds because that's what they process at.
Another thing I never understand...many people run an RTK base receiver and do NOT store data at the base. I get it if the receiver has no memory, but I have run across a number of people who don't store data, and they ask me why should they. Our survey styles for RTK all store data at the base. I typically process the base data against CORS or send to OPUS or RTX. But even if I don't, what possible harm would it do to collect this data?
I don't if we're using the same control every day or if it's a network point that's been properly observed and adjusted. But we always do on points that are unknown (obviously), in question, or new to us.
Lee D, post: 434232, member: 7971 wrote: OPUS does not support kinematic data. If you want to run RTK and log static at the base simultaneously then your Type under Base Options should be set to RTK & Logging, device to Receiver, and I typically log at 15 seconds - although if you're strictly using OPUS there's no reason to log at any faster than 30 seconds because that's what they process at.
Lee, what make me curious is on that video he send the data to opus and when opus sends back the corrected data, the other points just move automatically in relation to the base. now, i my base is on Faststatic which opus accepts, what would be my rover style? because Faststatic is independent right? so it means my rover shots will not be related to the base when ill process it to he TBC. my question is, how it was done on that video? this is what im trying to understand coz i want accurate base when im doing a fresh control and at the same time will do shots using the rover for other points i want to take data.
I have no idea what video you're speaking of. If you run RTK & Logging at your base, you'll have a T02 file with your static observations in it. Convert that to RINEX, send it to OPUS, and get your coordinates.
Now bring your JOB file from the collector into TBC. Open Project Explorer, expand your base point, and edit the Coordinate record (if it's in Global or Local coordinates), or else right click on the point and say Add Coordinate. Edit the Global (or Local if your coordinate system is US State Plane 1983) coordinate and make it Control. Your RTK points will shift to the new base coordinates when you hit Recompute. To verify this, note the position of one of the RTK points before you edit the base; it should move by the same deltas that the base does.
Lee D, post: 434283, member: 7971 wrote: I have no idea what video you're speaking of. If you run RTK & Logging at your base, you'll have a T02 file with your static observations in it. Convert that to RINEX, send it to OPUS, and get your coordinates.
Now bring your JOB file from the collector into TBC. Open Project Explorer, expand your base point, and edit the Coordinate record (if it's in Global or Local coordinates), or else right click on the point and say Add Coordinate. Edit the Global (or Local if your coordinate system is US State Plane 1983) coordinate and make it Control. Your RTK points will shift to the new base coordinates when you hit Recompute. To verify this, note the position of one of the RTK points before you edit the base; it should move by the same deltas that the base does.
ill try that.. thank you
If you do a "here" shot, the point is stored the same as a keyed in point. Later you can edit that point in Survey Controller or Access, and any shots from that point will also move.
I prefer to do a "here" shot, for example call it 23w for waas.
Then store that Lat/Long as 23.
The easiest way is to change your display to WGS84 and go to key in points and attempt to store 23w. It will warn you that the point already exist and populate all the fields with the original numbers. Change the point name to 23 (without the w) and store. Later you would edit 23 with the opus results and still have the original 23w shot.
James
Lee D, post: 434283, member: 7971 wrote: I have no idea what video you're speaking of. If you run RTK & Logging at your base, you'll have a T02 file with your static observations in it. Convert that to RINEX, send it to OPUS, and get your coordinates.
Now bring your JOB file from the collector into TBC. Open Project Explorer, expand your base point, and edit the Coordinate record (if it's in Global or Local coordinates), or else right click on the point and say Add Coordinate. Edit the Global (or Local if your coordinate system is US State Plane 1983) coordinate and make it Control. Your RTK points will shift to the new base coordinates when you hit Recompute. To verify this, note the position of one of the RTK points before you edit the base; it should move by the same deltas that the base does.
Hi Lee!
Sorry to bug you again, i've tried your idea i run rtk and logging at the base and convert the .TO2 file to rinex and the same opus won't accept the files because it's kinematic. by the way, im using the TCC at the TBC options to upload the file to opus.
my style was RTK for both base and rover and the base is logging on it's internal memory. based on your reply quoted above, you say ill run an RTK & logging at my base and ill have a .T02 file with my static observation. this is what make me confused is the static and RTK style. am i going to a FastStatic style log on my base and RTK on my rover? or if i do RTK style for both my base and rover on Trimble access on my DC would the base still log as Static? because what happen now is that i run an RTK style for both base and rover but opus detect it as kinematic data.
I think you may not understand that the Static file and the RTK file are separate files. It sounds like you are downloading the RTK file from the Data Collector and trying to upload that to OPUS. You need to get the Static file off of the receiver used as the Base. That file is stored in the internal memory of the Base receiver. You can either connect the receiver to your PC to download that file. Or you can download that file from the receiver to your data collector and connect your data collector to your PC. Then convert the Static file to Rinex and upload it to OPUS.
Sent from my iPhone using Tapatalk
OPUS (teqc filter) has no idea if a RINEX file is static or kinematic, it just reads what the file says it is. It is up to you to remove those comments from the file.
Paul in PA
Hi guys! anyone know what is the problem on this response from Opus...
Emmanuel, post: 434707, member: 12658 wrote: Hi guys! anyone know what is the problem on this response from Opus...
There aren't enough CORS sites with data to process a calculation for your point, sounds like you have TBC so you can process it yourself, it only takes a few minutes.
MightyMoe, post: 434721, member: 700 wrote: There aren't enough CORS sites with data to process a calculation for your point, sounds like you have TBC so you can process it yourself, it only takes a few minutes.
Hi MightyMoe,
i have a questions to ask, my setup for both Base and Rover was "RTK & Logging" using the "here" just to start the base. on the DC, it shows like two files are logging at the same time. the first one was the file name that i created on the webUI and the other file is somewhat when i started the base using the "here".
now, i've been asking this so many times.
1. EISurveyin201707021806A.T02 = File logging when the base is turned on
2. 02141831.T02 = File logging when i started the "here" on the base.
3. 07571830.t02 = File created when i do shots on the rover
Question 1:
Why when i upload the EISurveyin201707021806A.T02 using TCC on TBC it will say "the file has Kinematic data" and it wont upload to OPUS?
Question 2:
What File should i send to OPUS?
The 02141831.T02 was created using the "here" on the DC trimble access so when i imported it in to TBC it will show a fixed point and no need to send it to OPUS.
Question 3:
in relation to the above situation, does this tells me that i need to do a "FastStatic" on my Base Options in Survey style and process it to OPUS?
Then after that use the OPUS solution to set as a fixed point on the base and thats the time ill do the RTK shots on the rover? this means that i can't do it one time.
So i did a 2+ hours of data logging both the same in RTK & logging using "here" on the DC just to start the base. here what happen
1. I upload the raw data which i use the "here" and it shows no flag.
2. Even the base log file does not show a flag in TBC i still send it to opus just to try if the file will be process.
3. Opus send me back a corrected data.
4. I Change the point name using the notepad so it will be automatically change inside TBC.
5. I do drag and drop but instead of changing, it does this time show a red flag.
6. I delete the raw base file(not Opus Corrected) and used the OPUS corrected and click it as Control quality.
What happen during this procedure is that only the base shifted but the shots taken by rover doesn't adjust.
Did i do wrong on this? as i watched on youtube, the shouldn't be a red flag on the base when you do drag & drop on the opus corrected file and the rover shots should adjust itself based on the new control coordinates.
