Modify

Opened 11 years ago

Closed 7 years ago

#7 closed defect (fixed)

Ephemerides missing from stream coming from TCP/IP port

Reported by: rpiriz@… Owned by: stuerze
Priority: normal Component: BNC
Version: Keywords:
Cc: weber

Description

Hi there! I have a Topcon receiver connected to a serial port of my computer with output redirected to a TCP/IP port. The receiver is configured to output GPS and GLONASS navigation messages (RTCM messages 1019 and 1020). I am trying to do PPP with BNC (v 2.5), using this stream and CLK31 or CLK11 corrections. It does not seem to work, apparently observations from the receiver arrive OK, but not ephemerides. I have validated the TCP/IP stream with other software (RTKLIB) and it works correctly for RTK. Maybe I am doing something wrong in BNC, does BNC support ephemerides coming with the obs stream, or do I have to add another stream like RTCM3EPH? Thanks for your help - Ricardo.

Attachments (0)

Change History (6)

comment:1 by stoecker, 11 years ago

Cc: weber added

comment:2 by stoecker, 10 years ago

@Mr. Weber:

Can this be closed? Any answer for it?

comment:3 by mervart, 10 years ago

Owner: changed from mervart to rpiriz@…
Status: newneedinfo

comment:4 by stuerze, 7 years ago

Owner: changed from rpiriz@… to stuerze
Status: needinfoassigned

comment:5 by stuerze, 7 years ago

Using BNC's current version I cannot verify this observation.

BNC is able to

  • get ephemeris messages from an IP port connected receiver, and
  • compute a PPP solution from its observations.

My recommendation is to scan the imcomming RTCM messages.
This can be activated within the panel called 'Miscellaneous'.

--
Extract of RTCM message scan result during test:

15-03-30 07:53:26 ERLA0: Received message type 1019
15-03-30 07:53:26 ERLA0: Received message type 1019
..
15-03-30 07:53:27 ERLA0: Received message type 1020
15-03-30 07:53:27 ERLA0: Received message type 1020
15-03-30 07:53:27 ERLA0: Received message type 1020
15-03-30 07:53:27 ERLA0: Received message type 1020
15-03-30 07:53:27 ERLA0: Received message type 1020
15-03-30 07:53:27 ERLA0: Received message type 1004
15-03-30 07:53:27 ERLA0: Received message type 1012

Extract of PPP results using observations and navigation messages from an IP port connected receiver during test:

15-03-30 08:44:06 2015-03-30_08:44:06.000 ERLA0 X = 4067021.7641 Y = 790886.6299 Z = 4833355.5630 NEU:  +0.1955  +0.5579  -0.9638 TRP:  +2.2897  +0.0063
15-03-30 08:44:07 ERLA0: Received message type 1004 
15-03-30 08:44:07 ERLA0: Received message type 1012 
15-03-30 08:44:07 2015-03-30_08:44:07.000 ERLA0 X = 4067021.7629 Y = 790886.6302 Z = 4833355.5607 NEU:  +0.1949  +0.5584  -0.9662 TRP:  +2.2897  +0.0062
15-03-30 08:44:08 ERLA0: Received message type 1004 
15-03-30 08:44:08 ERLA0: Received message type 1012 
15-03-30 08:44:08 2015-03-30_08:44:08.000 ERLA0 X = 4067021.7624 Y = 790886.6306 Z = 4833355.5617 NEU:  +0.1958  +0.5588  -0.9657 TRP:  +2.2897  +0.0062
15-03-30 08:44:09 ERLA0: Received message type 1004 
15-03-30 08:44:09 ERLA0: Received message type 1012 
15-03-30 08:44:09 2015-03-30_08:44:09.000 ERLA0 X = 4067021.7631 Y = 790886.6303 Z = 4833355.5630 NEU:  +0.1962  +0.5585  -0.9643 TRP:  +2.2897  +0.0061
15-03-30 08:44:10 ERLA0: Received message type 1004 
15-03-30 08:44:10 ERLA0: Received message type 1012 
15-03-30 08:44:10 2015-03-30_08:44:10.000 ERLA0 X = 4067021.7629 Y = 790886.6309 Z = 4833355.5628 NEU:  +0.1962  +0.5591  -0.9645 TRP:  +2.2897  +0.0061
15-03-30 08:44:11 ERLA0: Received message type 1013 
15-03-30 08:44:11 ERLA0: Received message type 1004 
15-03-30 08:44:11 ERLA0: Received message type 1012 
15-03-30 08:44:11 2015-03-30_08:44:11.000 ERLA0 X = 4067021.7628 Y = 790886.6319 Z = 4833355.5613 NEU:  +0.1951  +0.5601  -0.9656 TRP:  +2.2897  +0.0060
15-03-30 08:44:12 ERLA0: Received message type 1004 
15-03-30 08:44:12 ERLA0: Received message type 1012 
15-03-30 08:44:12 2015-03-30_08:44:12.000 ERLA0 X = 4067021.7642 Y = 790886.6331 Z = 4833355.5630 NEU:  +0.1950  +0.5609  -0.9632 TRP:  +2.2897  +0.0060

comment:6 by stuerze, 7 years ago

Resolution: fixed
Status: assignedclosed

Modify Ticket

Change Properties
Action
as closed The owner will remain stuerze.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.