[IGSSTATION-3641]: R23 tracking failure concerning JPS/TPS receiver models

[Stefan Schaer]

******************************************************************************
IGS Station Mail          31 Mar 03:22:15 PDT 2010      Message Number 3641
******************************************************************************

Author: Stefan Schaer


Dear IGS colleagues,

In IGS Mail 6115

http://igscb.jpl.nasa.gov/mail/igsmail/2010/msg00063.html

we pointed to an obvious R23 tracking failure concerning JPS receiver
models. This GLONASS tracking problem is relevant for GNSS POD since
more than 57 (!) JPS as well as TPS receiver models of the IGS are
affected (they do not provide tracking data for R23, which is meanwhile
marked usable):

adis:  JPS LEGACY          2.6.1 JAN,10,2008
ankr:  TPS E_GGD           2.6.1 JAN,10,2008
azco:  TPS LEGACY          3.3 JUL,10,2008 P4
bogo:  TPS EUROCARD        2.6.1 JAN,10,2008
borj:  JPS LEGACY          2.6.1 JAN,10,2008
cagz:  TPS E_GGD           3.3 JUL,10,2008 P4
como:  TPS E_GGD           3.4 DEC,12,2009 P2
crar:  TPS ODYSSEY_E       3.3 JUL,10,2008 P4
dlft:  JPS LEGACY          2.6.1 JAN,10,2008
dres:  JPS LEGACY          2.6.1 JAN,10,2008
faa1:  JPS LEGACY          3.3
ffmj:  JPS LEGACY          2.6.1 JAN,10,2008
godz:  JPS EGGDT           2.7.0
helg:  JPS LEGACY          2.6.1 JAN,10,2008
hofn:  TPS E_GGD           2.6.1 JAN,10,2008
hueg:  JPS LEGACY          2.6.1 JAN,10,2008
irkj:  JPS LEGACY          2.6.0 OCT,24,2007 OB
jplv:  JPS EGGDT           2.7.0
khaj:  TPS E_GGD           -UNKNOWN-
kir0:  JPS EGGDT           2.6.1 JAN,10,2008
kour:  JPS LEGACY          3.4
leij:  JPS LEGACY          3.4 DEC,12,2009 P2
lhaz:  TPS E_GGD           3.4 DEC,12,2009 P2
mal2:  JPS LEGACY          3.3
mar6:  JPS E_GGD           2.6.1 JAN,10,2008
mas1:  JPS LEGACY          3.4
mccj:  TPS EGGDT           2.6.1B8 DEC,19,2007
metz:  JPS EUROCARD        2.6.1 JAN,10,2008
mobj:  JPS LEGACY          2.6.1 JAN,10,2008
mtbg:  TPS GB-1000
muej:  JPS LEGACY          2.6.1 JAN,10,2008
novm:  JPS LEGACY          -UNKNOWN-
ohi2:  JPS E_GGD           3.4 DEC,12,2009 P2
onsa:  JPS E_GGD           2.6.1 JAN,10,2008
park:  JPS E_GGD           2.7.0
pfa2:  TPS E_GGD           2.7.0 MAR,31,2008
pous:  TPS GB-1000         3.3 DEC,22,2008 P6
reyk:  TPS E_GGD           3.4 DEC,12,2009 P2
sass:  JPS LEGACY          2.6.1 JAN,10,2008
ske0:  JPS E_GGD           2.6.1 JAN,10,2008
sofi:  TPS E_GGD           2.6.1 JAN,10,2008
spt0:  JPS E_GGD           2.6.1 JAN,10,2008
sunm:  JPS LEGACY          JPS_4 / 2.6.1 JAN,1
sydn:  JPS E_GGD           2.3P3
ters:  TPS ODYSSEY_E       3.4 MAY,13,2009
thu2:  JPS LEGACY          2.6.0 OCT,24,2007 OB
titz:  JPS LEGACY          2.6.1 JAN,10,2008
tixj:  TPS ODYSSEY_E       2.7.0 MAR,31,2008
unbj:  TPS LEGACY          2.6.1 JAN,10,2008
unpg:  TPS ODYSSEY_E       3.3 JUL,10,2008 P4
vesl:  TPS GB-1000         3.3 DEC,22,2008 P6
vil0:  JPS EGGDT           2.6.1 JAN,10,2008
vis0:  JPS EGGDT           2.6.1 JAN,10,2008
warn:  JPS LEGACY          2.6.1 JAN,10,2008
wtzj:  JPS LEGACY          2.6.1 JAN,10,2008
wtzz:  TPS E_GGD           3.4 DEC,12,2009 P2
zimj:  JPS LEGACY          2.6.1 JAN,10,2008

Interestingly, the only TPS receiver group not affected is:

bake:  TPS NETG3           3.4
dubo:  TPS NETG3           3.4
frdn:  TPS NETG3           3.4
gope:  TPS NETG3           3.4 MAY,13,2009
iqal:  TPS NETG3           3.4
mdvj:  TPS NETG3           3.3 DEC,22,2008 P6
nurk:  TPS NETG3           3.3
sch2:  TPS NETG3           3.4
svtl:  TPS NETG3           3.4 MAY,13,2009
tn22:  TPS NETG3           3.4 DEC,12,2009 P2
unbt:  TPS NET-G3          3.4 NOV,05,2009  P2B
vald:  TPS NETG3           3.4
whit:  TPS NETG3           3.4

Best regards,

The CODE AC Team