I am having some trouble with a problem dataset and was hoping you guys could provide a little insight!
I ran a single baseline static observation to establish control at a remote site using a Trimble 4700 & 4800. The site was more wooded than I had planned, but I set the receivers in the best possibe locations I could find. Admittedly, the resulting data is not great, but it was a 3.5hr session, and based on past experience I feel it should be usable enough for what I am working on. The idea was to submit the data the file from each receiver to OPUS at least twice (using different CORS each time), review the extended output, hold one of the local stations fixed, process the baseline manually, compare the remaining station to the OPUS result, and if all checked out, run from there.
So, I downloaded data, and the file from 4800 looks OK. When I went to download the 4700, there were no files in the receiver from date of observation. The last file has an observation day of 76 instead of 95. Judging by the file size, it looks about right for my day in question, so I dropped that file into a TGO project (so I can use the better-than-TBC timeline view), and according to the file properties, the observation day, start time & stop time all coincide w/ actual observation time. I submitted both files to OPUS, and the file from the 4700 will process through OPUS with marginal results, but the file from the 4800 aborts with the "data too noisy or collected in kinematic" error. Just in case it was a *.dat file issue, I converted the 4800 file to RINEX using the Trimble conversion utility, submitted that file, and got the same error. Still no progress in that regard...
In the meantime, the file naming snafu has me worried. Next, I dropped both files in TBC & "fixed" the "here" position in the 4800 file and try to process just to see if I have usable data. (The 4800 was started first, so the TBC default is to run the baseline from that position first, and so for the sake of this exercise I just ran with it.) The baseline processor fails and I get the error message "No reference files are available." Thinking that maybe the file names with the mismatched dates of observation may be the problem, I manually changed the file name to the correct day, re-imported and tried to process, but without success. This error message has me stumped, especially since I can view the files (and their matching day/time) in the TGO timeline and I can check all the file properties in the TBC project and they look fine.
Any thoughts on what else to try? (and sorry for the book!)
The files from the Trimble 4800s have a quirky feature - the P2 data records are prezactly the same as the C1 records. The OPUS-Static processor usually cannot handle that and issues an error message like the one you received.
The solution is to strip out the P2 data (instructions here) - then OPUS-Static works fine with only L1, L2, and C1 records. (My tests show OPUS-Rapid Static is different - it needs the P2 data and somehow works even though that data is the same as C1.)
To get your data to process in TBC, my suggestion would be to convert the DAT file with the bad date stamp to RINEX and see what the actual epoch-by-epoch records show for dates. If those are wrong, then find-and-replace to correct them (as well as other date records in the header, etc.)
Good luck!
GB
Glenn - thanks for the reply. I will give that a shot this weekend.
I am not sure what to think of the RINEX check/fix for the file w/ the bad date stamp. My understanding of the process OPUS uses is that it converts all files to RINEX first and then crunches the numbers. If OPUS can successfully process the file I submit, then I doubt the dates in the file are incorrect, but I will certainly look into that possibility.
Thanks again!
> Glenn - thanks for the reply. I will give that a shot this weekend.
>
> I am not sure what to think of the RINEX check/fix for the file w/ the bad date stamp. My understanding of the process OPUS uses is that it converts all files to RINEX first and then crunches the numbers. If OPUS can successfully process the file I submit, then I doubt the dates in the file are incorrect, but I will certainly look into that possibility.
>
> Thanks again!
If you're still having problems try downloading GNSS software from ashtech (it's a freebie for static sessions) and see how that works. I really like it for my L1 stuff, it's much more user friendly than Trimble.