I am trying to set up my RTK Mosiac X-5 as a base station for corrections to my RTK Torch. I Have the mosiac connected to my laptop via USB, I was successfully able to connect it to the NTRIP caster I set up with rtk2go.com but every 10 seconds the connection goes red for about 1 second. Then when I try to get the updates from my mountPt for the RTK Torch on the SW Maps apps it won’t let me connect to the server. I’m not sure if these are related issues but I just need to find a way to consistently receive corrections on my Torch from the Mosiac.
Please have a read through the page below. It shows how to check that your corrections are being sent to RTK2go correctly. Check that first, then move on to configuring the Torch.
I have followed the directions on that page so I am confused why everything isn’t working. In the Septentrio webpage it shows my Ntrip stream to rtk2go is green but it turns red for 1 second every 10 seconds but it does show that my base station is up and running in rtk2go. So it seems like it is still sending corrections even though it loses connection periodically. But I wonder if that periodic disconnection is impacting the Torch’s ability to connect as a client to receive the ntrip corrections.
I think I found one of my problems. In SW Maps in the NTRIP credentials I was using the mountPt username and password instead of using my email for username and “none” as password. Now when I try to connect instead of constantly saying disconnected instead it tries to connect then says connection timeout. While it never shows I’m connected on the app the status page in rtk2go breifly shows that my mountPt has a user connected.
Any ideas on what my problem could be causing the connection timeout? I have good internet connection on my phone.
Is your RTK X5 connected to your network via Ethernet, or via WiFI? If via WiFi, are you able to try Ethernet? If via WiFi, have you kept the X5-ESP32 Ethernet cable clear of the ESP32 WiFi antenna? I have seen issues caused by the WiFi transmit injecting errors into the Ethernet data.
It is connected by usb directly to my computer and I have enabled outgoing internet access over usb in the septentrio webpage and allowed access to share wifi on my laptop. And that all seems to be working.
Please check your RTK mosaic-X5 is in Ethernet mode. Being in WiFi mode shouldn’t matter, but maybe the ESP32 is periodically resetting the X5 because the X5-ESP32 Ethernet link is not up? Ethernet mode is the default, it would only be in WiFi mode if you have selected that through the CONFIG ESP32 console.
It is already in ethernet mode. If I miss an update 1 out of every 10 seconds I am okay with that if that’s just what happens but I can’t get my torch to connect to receive any of the corrections.
I fixed one issue to now use an email address for user name for the ntrip client server in SW Maps and “none” for the password and now it tries to connect but it says “connection timeout” now. While it is trying to connect I temporarily see a connected user to my mountPt on rtk2go but it drops off after the timeout is hit.
I was just messaging with the rtk2go people and it looks like my connection timeout when attempting to connect to the client server occurs after the 10 second mark as well. So now it looks like the base losing the connection every 10 seconds is causing me to not be able to connect and receive corrections.
What could be potential causes for this? I believe I have everything set up right as described in the documentation.
@PaulZC is there any chance we could call to chat 1-on-1 to try and figure this out? I’m trying to figure this out asap for use on Monday.
Any help would still be much appreciated whenever you can get to it!
A few more updates though as I have been messing with it more. I changed the configuration of the rtk mosaic x5 to wifi mode and I was still able to act as an ntrip server base but it also would red line every 10 seconds and the torch still would not connect in SW Maps.
I also tried to reconfigure my torch to connect to wifi and manually enter the ntrip server I wanted to connect to as a client following the directions for using the serial port but I was never able to access the menu, I just kept getting an error which another person is having on this thread Torch serial config.
I was able to connect to the torch on SW Maps for android and connected as an ntrip client but sadly I could only borrow it for a few minutes so I wasn’t able to take enough time for testing to see if I could establish an rtk lock, I could just see that it said I was connected as a client. So now I am thinking maybe the problem is SW Maps on IOS and the new torch are incompatible?
Still looking at all the options for trouble shooting. Thanks for the help!
Many apologies. I saw your other post. I suspect your Torch isn’t running the RTK Everywhere Firmware either. That would explain a whole load of badness… Apologies for the hassle. Please upload the 2.1 firmware and you should be able to get corrections.
I have an RTK mosaic-X5 configured the same as yours: Ethernet mode (Ethernet not connected); USB connection to a Windows laptop; “Outgoing Internet Access Over USB” enabled; WiFi \ More Adapter Options \ Sharing \ “Allow other network users to connect through…” (Ethernet 3 in my case). It took me a while to remember the “arp -a” trick to find the new X5 IP address for the Ethernet-over-USB web page, but the Septentrio video was very useful here.
I’m sending corrections from the X5 to RTK2go. I am seeing the same red line “No data sent” issue, every 10 seconds. But, despite that, RTK2go is happy with the connection.
I have an RTK Torch running a fresh install of RTK Everywhere 2.1. Through the serial console, I gave it the WiFi SSID and password. Exited the menu to apply the changes. Re-opened the menu and entered the RTK2go settings using option 1 followed by 7. Exit the menu to apply the settings. The Torch is getting corrections and is RTK Fixed.
I always enter my true email address in option 10 Caster User Name - replacing the default “test” email address.
Please remember that the X5 “Outgoing Internet Access Over USB” defaults to “Off”. You will need to save the change in the “Boot” configuration to enable it at power-on.
Apologies again for the hassle - I hope this helps,
Paul