These are very similar software products. We use SPSO only to process/adjust static obs. SPSO v4.11
Ran a network using 2 base units and 2 rovers occupying for 10-15 min. over 12 stations. Turned receiver on at each setup, occupied for 10-15 min, rover off; repeat at next station. Equip= Trimble R8-4 and SP Epoch 50
Both Base files imported. Of the rover files only 4 imported. Got this error on 20 of the occupations:
"(filename.t02) failed because a suitable importer could not be found"
Trimble and Epoch files both were rejected. No obvious pattern w/ rejected and accepted files.
Any ideas on why these are rejected and how to resolve this??ÿ A 350 ac. grading job is waiting for the control! Ahhhh
Also, the import dialog box will not list time on/off. Reads "invalid leap seconds"?ÿ What does this mean?
Most likely your version of SPSO was released before the latest leap second was added, or recent(ish) GPS week rollover.
Were you actually ending the static sessions before turning off the receivers, or just doing a hard reset/shutdown? I know some of the older units (R6/R8) could have problems if the static session wasn't shut down properly.
?ÿ
Edit: have you tried converting to rinex and then importing?
@rover83?ÿ
Thanks for your insight. Is is an older version of SPSO (v4.11), so the rollover week may be the issue w/ "invalid leap seconds" message.
And yes, simply turned off receiver, but I do not beleive that to be the issue preventing import to SPSO, because:
1. In the past, have been able to import static files that were terminated by powering down receiver.
2. Person running static w/ R8s had a data controller and he started/stopped by the connecting receiver w. the Ranger data controller. And many of those files were rejected by the import routine as well. (Preferred method but we had only one Ranger available that day.)
I have seen similar errors in TBC caused by updates to the "Configuration Utilities" that run inside TBC - seems these are the components that handle file conversions, imports, etc.?ÿ You may want to check for and run updates on those.
Make sure your office software is updated. If you have receivers that don??t have firmware to account for the leap second, some fixing of the data file might be needed. I used a 5800 that didn??t have updated firmware and Trimble had to fix the data files fir me.
