In the last week all my stuff has been rejected. Two from an old Zephyr/5700 setup that's worked fine in the past and two from an R10-2. I'v submitted both RINEX .23o's and raw .T04's and get a couple different but similar rejection notices that are something like this (which don't seem to me to point to valid issues):
1020 OPUS aborted on the submitted data file for one or more of the following
1020 reasons. OPUS cannot process the data file.
1020 1. Collection interval of the data file was not one of the allowed rates.
1020 The intervals that are accepted are 1,2,3,5,10,15,30 seconds.
1020 2. The time of each epoch is offset from one of the above intervals. The
1020 seconds epoch field must coincide with one of the above rates.
1020 3. The data file may have been collected in kinematic mode. OPUS does not
1020 process kinematic data files.
1020 4. Note: OPUS processes data every 30 seconds, and 2+ hour files
1020 collected at the 1 second rate should be changed to 30 seconds.
1020 5. If your data were collected today or yesterday, we may not have
1020 sufficient CORS data - try resubmitting your file tomorrow.
OR
9999 Error: Datasets less than two hours in duration no longer accepted to OPUS-S.
9999 Your data file appears to span less than 2 hours. OPUS guidelines require a
9999 minimum data span of 2 hours and strongly recommend 4 hours to achieve
9999 best accuracies. Datasets less than two hours in duration are no longer
9999 allowed in OPUS-S. Please re-submit your data to OPUS-RS.
9999 If your file is actually over 2 hours, check for formatting compliance
(definitely more than 4 hr stew time for both these)
??
Post one of the RINEX files, maybe something will jump out at one of us. (You'll have to change the extension to .txt or one of the other accepted file types.)
If you share a file, be happy to take a look.
Or for OPUS questions you can always reach out to your neighborhood Regional Geodetic Advisor at NGS.
Thank you both. Here's one that I'd really like to get. It's an old 5700 receiver that was collecting static fine last year, last time I used it. Weird thing is when processing RINEX I'm getting .04o, .04n files... thought they should be .23o, .23n
Here's the message I keep getting, trying different things on OPUS:
1020 OPUS aborted on the submitted data file for one or more of the following
1020 reasons. OPUS cannot process the data file.
1020 1. Collection interval of the data file was not one of the allowed rates.
1020 The intervals that are accepted are 1,2,3,5,10,15,30 seconds.
1020 2. The time of each epoch is offset from one of the above intervals. The
1020 seconds epoch field must coincide with one of the above rates.
1020 3. The data file may have been collected in kinematic mode. OPUS does not
1020 process kinematic data files.
1020 4. Note: OPUS processes data every 30 seconds, and 2+ hour files
1020 collected at the 1 second rate should be changed to 30 seconds.
1020 5. If your data were collected today or yesterday, we may not have
1020 sufficient CORS data - try resubmitting your file tomorrow.
Here's your problem:
2004 5 19 20 2 0.0000000 GPS TIME OF FIRST OBS
2004 5 20 0 55 30.0000000 GPS TIME OF LAST OBS
Why would it do that? Before this setup (after getting bad data from the first two) I Winflashed it, looking for something to do with date. I didn't find anything, but expected that as I thought that was a value received from the sats. I also opened it up with the configuration toolbox and poked around in there, resst it to factory and reinstated a saved "current" configuration from when it was working fine.
Thanks for the direction and no need to spend time, but just brings up questions for me.
Can I use a text editor to find and replace on the date info in there? I could set it to UTC of the setup if needed.
Mahalo.
Found a bulletin about firmware and rollover issues for the 5700/5800 model 1 receivers:
https://www.seilergeo.com/trimble-survey-gnss-firmware-week-number-roll-over-wnro-issue/
Looks like those receivers are officially EOL unless you manually adjust the time.
Hey Dave, could you confirm when your observations began for that file? Was it on Tuesday of this week? About noon local time?
I would bet that a script could solve this issue and keep the receiver chugging along.
"Was it on Tuesday of this week? About noon local time?"
If I matched my notes up correctly, it was started Wednesday (1/3) at about 8:30 am HST. We're UTM-10 so that should've shown 6:30ish pm UTM 1/3. I thought firmware v2.32 for those solved the rollover problem.
I got it fixed!!!!
1. couldn't open the seilergeo site... not sure why. It just continued to time out. Even when I just went to seilergeo.com (??)
2. searched your (rover83) phrase "firmware and rollover issues for the 5700/5800 model 1 receivers" and poked around at a few listings to find this. Here. From August https://rpls.com/forums/discussion/trimble-5700-r7-date-log-file-is-2004-not-2023-how-to-set-receiver-time-and-date/ and saw stuff on teqc. I used to use the DOS version of that quite a bit, but saw the WinTEQC app offered by I believe silkwerks.
Tried it. No go. Tried it with teqc,exe in the folder. Still no. Tried it in my Win7 Pro VM box. Worked - sort of, but it kept failing in a different way. Downloaded 2 beta versions from that site and ended up getting the WinTeq2 beta working (from Kevin at SurveyorConnect). But it didn't do a comprehensive date change (even after the suggested changing of extension to .24o). Opened that partially changed 24o file and used a text editor for 20 minutes changing dates (such as 2024 1 5 8 30 00.00000) and replacing almost any 2004 with 2024.
Worked!
Then after almost 2 hours of reading up on crap, I found this site: https://sgss.ca/tools/rinex_date.html
Loaded my original .04o file into it and it updated everything in like 3 seconds (!!)
Amazing. Thanks so much for both (all) your help guiding me down this rabbithole. If I'm ever gonna waste time this is probably my 2nd (or 3rd) favorite way to do it.
(if I ever make any money doing this I'll definitely support rpls (the all new) more than I have.
I would still like to know how/why the old beast started doing this differently (and how to get it to behave again), but I bet I'd be even more satisfied just getting something that's much more up to date; forget about this whole experience.
Solving a nagging problem and learning something new is always a great feeling.
Great to hear you solved it.
Thanks for posting that RINEX UP-Dater link, pretty cool/funny that someone made that!
