Triumph-LS set in vrs mode having trouble connecting to the base network

[Survey McCrea]

I have been using a Triumph-LS set in vrs mode but I am have trouble connecting to the base network. I did have Matt Sibole connect to the system and check my setting while this was happening and he suggested I post it here as a issue.

 

[Michael Stazhkov]

I have been using a Triumph-LS set in vrs mode but I am have trouble connecting to the base network. I did have Matt Sibole connect to the system and check my setting while this was happening and he suggested I post it here as a issue.

Please record GNSS file while your LS is attempting to connect to the base network (just collect and save one point). After that send the project to support ( projects screen on the LS -> push Send Project to Support button) and tell the receiver serial number or the project name.
What kind of trouble you experience? The LS can't establish connection or can't get corrections stream from the network?

 

[Jim Frame]

This is slightly of off-topic (at least as far as McCrea's problem goes), but I'd like to request that someone at Javad see if they can get corrections from (not just connect to) the CRTN station UCD1. Earlier this year -- or maybe even last year, time goes by so fast these days -- BARD changed the receiver at this station, and ever since then I've been unable to get usable corrections from it. Yehuda Bock maintains that everything is fine, but I think they've misconfigured the stream somehow. I don't have trouble with any other CRTN stations, just UCD1. It's less than 2 km from my office, which makes its unavailability particularly frustrating.

Thanks!

P.S. Michael Glutting has CRTN login credentials.

 

[Jim Frame]

I'm not sure if the following points to the problem or not, but here's a snippet of the stream coming from UCD1:

20-11-17 03:17:13 ========== Start BNC v2.12.6 (WIN32) ==========
20-11-17 03:17:13 Panel 'Miscellaneous' active
20-11-17 03:17:13 UCD1_RTCM3: Get data in RTCM 3.x format
20-11-17 03:17:13 Configuration read: C:/Users/jhfra\.config\BKG\BNC.bnc, 1 stream(s)
20-11-17 03:17:13 UCD1_RTCM3: Received message type 1004
20-11-17 03:17:13 UCD1_RTCM3: Observation Types: G 6 C1W L1W S1W C2P L2P S2P
20-11-17 03:17:14 UCD1_RTCM3: Received message type 1004
20-11-17 03:17:15 UCD1_RTCM3: Received message type 1004
20-11-17 03:17:16 UCD1_RTCM3: Received message type 1004
20-11-17 03:17:17 UCD1_RTCM3: Received message type 1004
20-11-17 03:17:18 UCD1_RTCM3: Received message type 1004
20-11-17 03:17:19 UCD1_RTCM3: Received message type 1004
20-11-17 03:17:20 UCD1_RTCM3: Received message type 1004
20-11-17 03:17:22 UCD1_RTCM3: Received message type 1006
20-11-17 03:17:22 UCD1_RTCM3: Received message type 1007
20-11-17 03:17:22 UCD1_RTCM3: Received message type 1004
20-11-17 03:17:22 UCD1_RTCM3: Antenna descriptor
20-11-17 03:17:22 UCD1_RTCM3: ARP (ITRF) X -2628825.7360 m
20-11-17 03:17:22 UCD1_RTCM3: ARP (ITRF) Y -4247933.3322 m
20-11-17 03:17:22 UCD1_RTCM3: ARP (ITRF) Z 3952176.6323 m
20-11-17 03:17:22 UCD1_RTCM3: Antenna height above marker 0.0083 m

For comparison, here's the stream from P271, which I've been using lately:

20-11-17 04:09:09 ========== Start BNC v2.12.6 (WIN32) ==========
20-11-17 04:09:09 Panel 'Miscellaneous' active
20-11-17 04:09:09 P271_RTCM3: Get data in RTCM 3.x format
20-11-17 04:09:09 Configuration read: C:/Users/jhfra\.config\BKG\BNC.bnc, 1 stream(s)
20-11-17 04:09:09 P271_RTCM3: Received message type 1004
20-11-17 04:09:09 P271_RTCM3: Received message type 1012
20-11-17 04:09:09 P271_RTCM3: Observation Types: G 6 C1C L1C S1C C2P L2P S2P
20-11-17 04:09:09 P271_RTCM3: Observation Types: R 6 C1P L1P S1P C2P L2P S2P
20-11-17 04:09:10 P271_RTCM3: Received message type 1004
20-11-17 04:09:10 P271_RTCM3: Received message type 1012
20-11-17 04:09:11 P271_RTCM3: Received message type 1004
20-11-17 04:09:11 P271_RTCM3: Received message type 1012
20-11-17 04:09:12 P271_RTCM3: Received message type 1004
20-11-17 04:09:12 P271_RTCM3: Received message type 1012
20-11-17 04:09:13 P271_RTCM3: Received message type 1004
20-11-17 04:09:13 P271_RTCM3: Received message type 1012
20-11-17 04:09:14 P271_RTCM3: Received message type 1004
20-11-17 04:09:14 P271_RTCM3: Received message type 1012
20-11-17 04:09:15 P271_RTCM3: Received message type 1006
20-11-17 04:09:15 P271_RTCM3: Received message type 1007
20-11-17 04:09:15 P271_RTCM3: Received message type 1004
20-11-17 04:09:15 P271_RTCM3: Received message type 1012
20-11-17 04:09:15 P271_RTCM3: Antenna descriptor TRM59800.00 SCIT
20-11-17 04:09:15 P271_RTCM3: ARP (ITRF) X -2621689.3692 m
20-11-17 04:09:15 P271_RTCM3: ARP (ITRF) Y -4242469.0176 m
20-11-17 04:09:15 P271_RTCM3: ARP (ITRF) Z 3962672.9052 m
20-11-17 04:09:15 P271_RTCM3: Antenna height above marker 0.0083 m

 

[Alexey Razumovsky]

Jim, could you share with us jps file logged by TLS with UCD1 corrections inside?

 

[Jim Frame]

In the attached project I collected point 1 from P271, the same point as point 2 from P268, then tried to collect point 3 (same point) from UCD1, but all I got was code float (I think -- it said CDF but was grayed out, see screenshot).

 

[Alexey Razumovsky]

Got it. I am waiting for P271, P268 data at https://www.ngs.noaa.gov/CORS/

 

[Alexey Razumovsky]

L1 and L2 phase UCD1 data does not look like true data. Geometry free combination L2 - L1 deals values closed to zero.

In the meantime I expect to see ambiguity shift. Moreover due to different ionosphere impact in L1 and L2 data we can always see ionosphere shift in L2 - L1 combination even if ambiguities have been resolved in transmitted data. Noise of L2 - L1 also exceeds the expected values 0.01-0.02 meters. Mostly if the phase data noise values are above 0.05-0.06 m it's not possible neither to resolve ambiguities nor getting phase solution.
Ask Yehuda Bock about explanation.
P.S. I guess UCD1 data provider eliminates ambiguties and iono from transmitted data. If so then how receiver can detect this using RTCM.
And last but not least with noise like this its not possible to resolve ambiguities on rover side because we use rover to base differences for searching integer ambiguities.

 

[Jim Frame]

I forwarded your response to Yehuda for review.

The noise -- at least some of it -- was probably due to the fact that I was in my driveway when I collected the data. The sky view isn't very good there.

 

[Jim Frame]

Yehuda verified that there's a problem, possibly with the Septentrio firmware, and maybe receiver configuration as well. He has notified the BARD folks, so I'm hopeful that this will get cleared up. I hate not being able to use a CRTN station that's so close to my office!

 

[Alexey Razumovsky]

I forwarded your response to Yehuda for review.

The noise -- at least some of it -- was probably due to the fact that I was in my driveway when I collected the data. The sky view isn't very good there.

The graph is for UCD1 #sats , L2-L1 raw phase data. There are no rover data at all.

 

[Alexey Razumovsky]

My thoughts UCD means U Code Differential? Code smoothed by phase.

 

[Jim Frame]

My thoughts UCD means U Code Differential?

University of California, Davis. UCD1 is attached to the parapet of the Physics & Geology Building on campus.