Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NTRIP Caster not working #44

Open
ralphkink opened this issue Sep 12, 2021 · 1 comment
Open

NTRIP Caster not working #44

ralphkink opened this issue Sep 12, 2021 · 1 comment

Comments

@ralphkink
Copy link

ralphkink commented Sep 12, 2021

Problem: esp32-xbee in caster mode does not sent valid messages and crashes the module after some time.

Setup:

  • Ardusimple XBEE, running firmware v0.5.4
  • XBEE configured as NTRIP caster on local WiFi (placed directly next to access point)
  • GNSS board: simpleRTK2B-F9P V3, configured as base station with ublox config file

Clients:
I've tried two different NTRIP clients:

  • BKG Ntrip Client Version 2.12.17 (only NTRIP v1 seems to be able to connect to XBEE)
  • u-center 21.05 NTRIP Client function
  • I've only used the clients for testing in sequence, never both at the same time

Symptoms:

  • After inital connect, both clients are able to retrive the name of the mountpoint
  • u-center initially report a "green" connect of the client but seems to receive incomplete data and reports a connection error 10035
  • BKG client reports a error on connect attempt
  • After some minutes, the ESP32 XBee Config web page "degenerates" - it sill loads but it seem CSS files are missing. Anyway, something is going south on the ESP
  • After some more minutes, the ESP becomes unresponse (cannot access via HTTP anymore, NTRIP clients report "disconnect"
  • The symptoms can be reproduced 100% of attempts

Is this a know bug? Anything I can do on my end?
Big thanks in advance for any help provided!

Additional information / Attachments: (see below)

  • u-center NTRIP log file
  • screen shot from BKG client connection attempt
  • screen shot from corrupted web page

--- u-center log file ---
10:02:33 Send mountpoint request (base)
10:02:33 Data received from server (15bytes).
10:02:55 Ending NTRIP session.
10:02:55 Closing connection to server.
10:02:58 Connection error received (10035).
10:02:58 Server connection closed.
10:06:24 Ending NTRIP session.
10:06:24 NTRIP session already closed.
10:06:24 Start NTRIP session.
10:06:24 Connected to NTRIP server.
10:06:24 Send mountpoint request ()
10:06:24 Data received from server (184bytes).
10:06:24 Connection error received (0).
10:06:24 Ending NTRIP session.
10:06:24 Closing connection to server.
10:06:24 Server connection closed.
10:06:27 Start NTRIP session.
10:06:27 Connected to NTRIP server.
10:06:27 Send mountpoint request (base)
10:06:27 Data received from server (15bytes).

--- XBEE web site ---
corrupt web page

--- BKG Ntrip Client output on connection to mount point ---
image

@ralphkink
Copy link
Author

Meanwhile, I was able to solve the problem, but would still consider this a bug (or at least room for improvement) for
esp32-xbee. Root cause was:

  • In UBX-CFG-PRT "Protocol Out" was (correctly) set to "5 - RTCM3" for UART2
  • BUT, in UBX-CFG-MSG the RTCM3.3 message were disabled for UART2

So the esp32-xbee did not receive any data from the ZED-FP9, and hence the Caster did not send any data (or incomplete data?). This is causing the u-center NTRIP clients to do disconnects and new connection requests over and over again. 

As far as I can tell, the repeated connects/disconnects seem to destabilize the esp32-xbee, eventually leading to a crash after about 15mins.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant