OPUS upload error

Sean Joyce

Well-Known Member
I received this message after uploading to OPUS.

The internal format of the raw file you submitted to OPUS could
not be converted to RINEX by NGS and is therefore not supported
by OPUS!
Please convert the raw file to RINEX before uploading or contact
your receiver manufacturer for an alternative solution.


I have uploaded many files before and never received this message.
I just recently updated the T2 firmware to the latest version.
Has something changed?
 

Matt Johnson

Well-Known Member
5PLS
Hi Sean, would you be able to put the raw file in a zip folder and attach it post? I don't think anything has changed that should cause it to not work any longer.
 

Sean Joyce

Well-Known Member
Matt
The zip file is over the size limit for upload. 7mb
I was doing a 2 hour static session for a TBM on a flood certificate
and it resulted in a 10mb raw file.
Will check the sampling rate to see if that changed from a 30 sec interval.
Can you lift the file size restriction so I can upload the file?
 

Sean Joyce

Well-Known Member
Matt;
I uploaded to DPOS and received a solution.
emailed you the file.
Just wondering why OPUS kicked it back when that never happened before.
Thanks.
 

Matt Johnson

Well-Known Member
5PLS
JPS2RIN will convert it to a rinex file which was processed by OPUS. I attached the solution.

When I tried to use TEQC to convert it there is an error message which is likely the same problem OPUS has with it:

upload_2015-5-31_14-59-4.png


Hopefully someone will be able to look into this and figure out what is wrong.
 

Attachments

  • log0528a.zip
    7.1 MB · Views: 390
  • OPUS_log0528a.txt
    2.7 KB · Views: 409

Sean Joyce

Well-Known Member
This is the only time I have ever had trouble with OPUS uploading a .jps file.
I have been using DPOS for my recent projects.
 

Joe Paulin

Well-Known Member
Hi guys, looks like you are not the only one with troubles, Sean... I just received the same error message that you got from OPUS when I tried to upload a .JPS file from my T-2 tonight. I have firmware version 3.6.1 on my T-2.
Here is the jps file to look at. I did use JPS2RIN to convert it and that worked just fine. I have submitted .jps files before with no problem, so I'm not sure what the problem would be. Thanks for looking into this!
 

Attachments

  • 219_093813.zip
    1.2 MB · Views: 513

Matt Johnson

Well-Known Member
5PLS
I just tried uploading a new file to OPUS and see the same error. I'll have someone look into it. It seems to be a problem with the latest firmware.
 

Alexey Razumovsky

Well-Known Member
JAVAD GNSS
5PLS
JPS2RIN will convert it to a rinex file which was processed by OPUS. I attached the solution.

When I tried to use TEQC to convert it there is an error message which is likely the same problem OPUS has with it:

View attachment 2597

Hopefully someone will be able to look into this and figure out what is wrong.
Teqc from https://www.unavco.org/software/data-processing/teqc/teqc.html is able to convert attached log0528a.jps to RINEX obs file that well processed with OPUS. In the meantime OPUS declines to process log0528a.jps. So it is OPUS issue.
 

Attachments

  • teqc.zip
    540.6 KB · Views: 390

Alexey Razumovsky

Well-Known Member
JAVAD GNSS
5PLS
I ran teqc for Win 64 bit. My teqc is attached to my previous answer. Certainly teqc version is the same, jps file to convert is the same. The result isn't the same.
 
Last edited:

Matt Johnson

Well-Known Member
5PLS
I found some information on this error that may be relevant at http://postal.unavco.org/pipermail/teqc/2009/000801.html:

Re: http://ls.unavco.org/pipermail/teqc/2009/000790.html
subject: two new intermittent problems with TPS data

Topcon engineers took a look at the files that gave rise to
the problems teqc was having. For at least the first case
(i.e. apparent rogue value in [RC] messages), nothing was
really wrong with the [RC] messages. What was wrong was a
missing message, [SI], which gives the tracked satellites
for an epoch, or subsequent epochs if the list is unchanged.
The reason for the occasional missing [SI] message is that
the data was from a rover and a few random messages were
lost in transmission. When the missing message is the [SI]
satellite list when there's a change in tracking, esp. a
reduction in the number of satellites from a previous set
of epochs, this is a problem. The Topcon engineers suggested
some things that could be done to improve teqc's veracity
in reading corrupted TPS/JPS data, but my opinion is that
the simple fix I made in teqc seems to be "good enough" for
most cases, and, if users really want the full professional
treatment for problematic data they really should fall back
to Topcon's own translator tps2rinx.exe (for Windows only),
because, quite frankly, Topcon engineers are always going
to be far more familiar with their data than I am ever going
to be.

The second case (i.e. [SI] list show zero satellites)
apparently is allowed by the firmware but doesn't occur
often. And I was mistaken: previous teqc versions would not
crash when this condition occurred, but teqc would cleanly
exit when this was detected, but report a rather cryptic
message of:

teqc: cannot allocate memory for Topcon CA bin (0 bytes) ... exiting

As I mentioned before, now knowing that a zero satellite
list is a valid state in TPS/JPS, this was easy to fix.

-------------------

Next release: I'm still trying to get the same GLONASS nav messages
collected from different GNSS receivers to vet teqc's reading
of Trimble's new GLONASS nav record, but this test still isn't done
and I have no idea when it might be. If it isn't done in two
weeks, I'll go ahead and try to get out a new version of teqc
without this vetting.

-------------------

That's it for now ...

cheers,
--lou

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Louis H. Estey, Ph.D. office: [+001] 303-381-7456
UNAVCO, 6350 Nautilus Drive FAX: [+001] 303-381-7451
Boulder, CO 80301-5554 e-mail: lou unavco.org
WWW: http://www.unavco.org http://jules.unavco.org

"If the universe is the answer, what is the question?"
-- Leon Lederman
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~​
 

Matt Johnson

Well-Known Member
5PLS
Alexey, do you think there is anything that could be done on our end to fix this or should someone try to contact the developers of TEQC to let them know about this bug?
 
Top