Steve, the current release of
JMT for Android is
1.2.10.
DPOS
Regardless (v1.2.0 or v1.2.10) and as you already know, DPOS only uses .jps files, which are the native format for Javad GNSS equipment. If the DPOS submission is made immediately upon the close of the acquired data from the field, the IGS orbits' unavailability may cause the behavior that we (you and I) are observing. Specifically, I'm seeing Processing... hang at 30% on the processing screen and then, after waiting long enough, the DPOS Process Result screen indicates
The IGS orbits were not available at processing time:
As best as I'm aware of, the remedy is to wait; however, the exact amount of time for waiting is not clearly understood by me. The IGS data is most critical for processing the GLONASS parts of the field data as the GLONASS SVs are in a much lower orbit making their broadcast ephemeris undesired. This is the chief reason NGS gives (at least). This remedy has less to do with JMT v1.2.10 than it does for how the developers are handling Justin's implementations for DPOS. So keep the faith, they're working on this as part of some very exciting new features coming down the pipeline for J-Field.
OPUS
ABORT messages from OPUS are frequently seen for any number of reasons, sometimes, those messages are even valid while other times they're nonsensical. Often, waiting a day to resubmit to OPUS will result in its SOLUTION. This is true either using JMT or your browser for OPUS submissions. OPUS doesn't process GLONASS data and therefore the IGS ephemeris isn't required. Here again, the remedy for OPUS abort messages is often time.
Here's the abort message that resulted when I submitted the RINEX file via JMT for Android:
Code:
FILE: dirty1.14O OP1418751637716
1007 The RINEX dataset submitted to OPUS failed to pass an initial
1007 test for one or more of the following reasons.
1007 1. The data only contained values for a single frequency.
1007 2. RINEX file not formatted correctly.
1007 3. One of the lines in the RINEX file is over 80 characters
1007 in length.
1007
The exact same message was seen when the file was submitted using my browser. Personally, I am not convinced that reasons 1, 2 or 3 listed by NGS are true but I've got other things needing to be done before performing a necropsy on the data.
