To make sure the receiver is recording static data, once it is running go to the Instrument menu on the controller and select "Import from Receiver". You can then check that there is a current file (with the locked symbol). If you do this a couple of minutes after starting then file size should be about 5k. Then just "escape" out of the menu.
Just to clarify the last post - I should have started by saying that you need to check the actual live job is recording. A dummy can be checked as recording and then something goes awry when you start the real job. It's good practice to recheck the static again when ever you are in range, by the same method.
Results?
So will you let us know if you got this to work for you?
Results?
Well thank you all for the wonderful responses. I have successfully stored a T02 file and converted to Rinex. Now, I have an issue with OPUS aborting the file per the following message:
The RINEX data submitted to OPUS contains data taken from more than one
location. This can be verified by opening up your RINEX file and
searching for "MARKER". OPUS will only process data taken from one
location. Try separating the data into individual files and then
re-submit the data
Aborting...
I cabled the DC to the receiver to ensure no lost data so I feel good about the data that was collected. The receiver was NOT moved once the file download began. Any suggestions?
Results?
Send me your RINEX file, and I'll take a look. I'm pretty sure I know what is going on (maybe).
ldogeo at aol dot com
Loyal
Results?
I've found that when I run a fast static session with my 4000sse's I have to edit the rinex file before OPUS will process it. Open your rinex file with a text editor (notepad, wordpad, etc) and look for "MARKER NAME" and "MARKER NUMBER". These should be in the header but if you find them further down in the file OPUS thinks that you have multiple occupations. With the 4000sse's I always end up with a few lines of observations data between the header and the point where I enter the actual station name for the occupied point. Deleting these observations and any "MARKER NAME" "MARKER NUMBER" entries below the header clears up the issue.
Search the forum, several people have posted good info on editing rinex files manually and using TEQC or other utilities.
Edit: I see Loyal posted while I was typing, he's helped me several times in the past and is a wealth of knowledge.
Results?
I do believe I predicted this...
Do what Stephen says and it should work for you. We won't rest until you post your OPUS results!
Results?
FIXED!
Cleaned the kinematic data out (top & bottom) with NOTEPAD, and removed the GLONASS data using TEQC.
Successfully processed through OPUS_RS
Piece of cake 😉
Loyal
Results?
Talked to tech support at Trimble. Apparantly I was given bad advice concerning the process of storing the T02 file. Originally I was told to not use the "Start Base Receiver" command under the Static Survey style but go directly to measure points. Their original explanation was that this receiver was only a VRS/Rover unit so it was proper to skip. I have sent a new Rinex file that was unedited to OPUS and am waiting for a response.
Thank you Loyal for all your help. Rapid Static is not the normal process for our work by the way, only used for this exercise.
Results?
I was successful with the new guidelines given by Tech support. Thank you all, you guys are now all honorary HOGS. lol
RINEX FILE: 7490292n.12o TIME: 15:50:39 UTC
SOFTWARE: rsgps 1.37 RS43.prl 1.86 START: 2012/10/18 13:40:45
EPHEMERIS: igu17104.eph [ultra-rapid] STOP: 2012/10/18 14:25:45
NAV FILE: brdc2920.12n OBS USED: 4086 / 4275 : 96%
ANT NAME: TRM_R8_GNSS NONE QUALITY IND. 25.37/ 0.33
ARP HEIGHT: 0.00 NORMALIZED RMS: 0.334
REF FRAME: NAD_83(2011)(EPOCH:2010.0000) IGS08 (EPOCH:2012.79668)
X: -69809.675(m) 0.005(m) -69810.455(m) 0.005(m)
Y: -5123165.746(m) 0.013(m) -5123164.329(m) 0.013(m)
Z: 3786032.157(m) 0.011(m) 3786032.032(m) 0.011(m)
LAT: 36 38 45.84722 0.008(m) 36 38 45.87119 0.008(m)
E LON: 269 13 9.55257 0.005(m) 269 13 9.52040 0.005(m)
W LON: 90 46 50.44743 0.005(m) 90 46 50.47960 0.005(m)
EL HGT: 134.107(m) 0.015(m) 132.904(m) 0.015(m)
ORTHO HGT: 163.382(m) 0.018(m) [NAVD88 (Computed using GEOID12A)]
UTM COORDINATES STATE PLANE COORDINATES
UTM (Zone 15) SPC (2401 MO E)
Northing (Y) [meters] 4057904.809 90214.602
Easting (X) [meters] 698392.240 224902.542
Convergence [degrees] 1.32507819 -0.16753030
Point Scale 1.00008493 0.99994109
Combined Factor 1.00006388 0.99992005
US NATIONAL GRID DESIGNATOR: 15SXA9839257904(NAD 83)
BASE STATIONS USED
PID DESIGNATION LATITUDE LONGITUDE DISTANCE(m)
DN6073 MOAT MODOT ALTON CORS ARP N364121.708 W0912236.552 53510.8
DH7109 ARPG PARAGOULD CORS ARP N360332.787 W0903107.624 69245.6
DM4672 MODX MODOT DEXTER CORS ARP N364824.820 W0895842.958 73839.4
DN4498 MOBE MODOT BUNKER CORS ARP N372719.287 W0911256.714 97800.1
DL6310 MOBW MODOT BELLEVIEW CORS ARP N374217.741 W0904438.616 117560.6
DN5828 MOHS MODOT HOUSTON CORS ARP N372017.542 W0915623.584 128643.5
DM4627 ARM3 MOUNTAIN HOME 3 CORS ARP N362209.246 W0922223.292 145925.1
DL6300 MODR MODOT DRAKE CORS ARP N382745.474 W0912754.943 210490.3
DL6012 MOBR MODOT BRANSON CORS ARP N364235.201 W0931323.592 218433.3
NEAREST NGS PUBLISHED CONTROL POINT
GE0341 TT 61 B N363841.74 W0904746.02 1384.6
