Just got the following from Lou Estey at UNVACO:
Paul in PA
All,
I found out yesterday that on 6 March 2014 JAVAD GNSS changed a couple of key parameters
that effect the decoding of SBAS and Galileo pseudorange and phase values when using
many of the JPS messages which includes (at least):
- [rc], [r1], [r2], [r3], [r5], [rl] for pseudoranges
- [1R], [2R], [3R], [5R], [lR] for relative pseudoranges
- [1r], [2r], [3r], [5r], [lr] for relative pseudoranges
- [CP], [1P], [2P], [3P], [5P], [lP] for relative phases if using
either of the above sets of pseudoranges
- [cp], [1p],[2p], [3p], [5p], [lp] for integer relative phases if using
either of the above sets of pseudoranges
There is no impact:
- on GPS, GLONASS, QZSS, or Beidou pseudorange or phase values
- if using the [RC], [R1], [R2], [R3], [R5], [Rl] messages for pseudoranges
- if using the [PC], [P1], [P2], [P3], [P5], [Pl] messages for carrier phases
- if using the [pc], [p1], [p2], [p3], [p5], [pl] messages for carrier phases
Note 1: This does not impact reading of Topcon TPS messages.
Note 2: Decoding in teqc using the original key parameters was added to teqc
on 9 May 2012 for Galileo, Beidou, and QZSS -- so versions of teqc from that
date forward would yield the correct SBAS and Galileo pseudorange and phase
values (when using the specific JPS messages listed above) until the JAVAD GNSS
receiver firmware was updated after 6 March 2014.
Note 3: You can figure out which JPS messages your data has by using the
'+diag' (= "turn parsing and other diagnostics on") option which send output
to standard error (stderr); suppress conversion to RINEX with '+mds' or '+meta',
e.g. with most UNIX/Linux shells:
teqc -jav jps +diag +mds file.jps 2>&1 | more
... and look at the message IDs at the end of lines starting with "Javad JPS frame".
A correction to teqc will obviously be in the next release, but I'm not
sure when that will be since we're in the middle of several changes right now.
However, if you need an interim version in the meantime, please contact me directly.
Sorry about this.
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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For a couple of years now, I've thought that there was something fishy going on.
JA, PLS SoCal
What the world you talkin bout there Willis?
Some of us are knowledgeable, about some some of that. But, I for one, know more about skinning a deer, than I do about that. So, won't you please translate that into "deer skinner" so we all can learn?
Thanks!
N
Nate,
If you do not use SBAS (WAAS) in your position solutions this does not affect you, I think.
I use teqc to parse and rearrange my observables data, but there are so many other things teqc can do that I know nothing about.
In other words given the proper commands teqc can skin, bone and cook your deer.
Paul in PA
I think I use waas a little.
Javad will stake autonomously, without a base. Great for finding your old base site.
Sent from my VS880PP using Tapatalk
Nate The Surveyor, post: 377817, member: 291 wrote: I think I use waas a little.
Javad will stake autonomously, without a base. Great for finding your old base site.Sent from my VS880PP using Tapatalk
Could just be using an autonomous position for the base too?
SHG
Yes... Data flow often goes like this:
Set up base autonomously.
Work all day.
Return to base.
All base data is translated from base to rover.
Go home. After GPS midnight, plug the Javad LS into a LAN line. Press dpos. Upload it.
In about 15 mins. You have real spc coords for all your work that day.
Next time out, you stake your base autanomously, Boom! your on it!
