I am trying to get the torch to send data directly to a client via the torch’s wifi access point. I have the torch in Base mode, in the TCP/UDP menu I have “TCP server” enabled, I have “NTRIP Caster” enabled, i have it set to “Access point” and not “wifi”. I disabled bluetooth to free up ram. but when i start up the torch, i do not see the access point. What is going on? RTK Config works fine and that access point shows up, but when i try to run the torch as an NTRIP server, there is no access point
RTK Torch not broadcasting its wifi access point to send corrections. Config access point works fine
Does base cast mode behave any differently?
Also ensure whatever you’re using to search for the network has 2.4GHz wifi enabled
A bit of an update.
After not seeing the wifi ssid, i decided to reset the torch to factory defaults.
After doing that, I used the serial config
and set the torch to Base mode. I then set the “TCP server” to enabled and leave the port at its default number (2948 i believe), I set “NTRIP Caster” to enabled, and then I set it to “Access point” instead of wifi. I also set LoRa to enabled. I also disabled blutooth to save ram.
After doing this, I am able to turn on the torch and the SSID appears, “RTK 9FCA03”. I am able to connect to that wifi ssid.
I then go into my drone’s settings,
I input the IP address (192.168.4.1)
I input the port as 2101 (I tried 2948 but it did not work)
I then input the mount point “SparkBase”
I am able to connect and i get a pretty steady fix.
however, On my other torch that i use as a rover, There is absolutely no indication of LoRa traffic (no yellow/orange LED) even though it is configured properly (LoRa enabled, same frequency setting as base, etc).
I then double tapped the power button to turn on wifi config. I had touched nothing else, all I did was double tap to turn on the “RTK Config” wifi, I looked around the settings, and it had changed the setting from base to Rover! but it kept the Profile name, the TCP/UDP settings, and the LoRa settings.
I attempted to switch to Base Cast via the serial config menus.
My exact sequence was:
Reset the torch to default settings.
Go to the system menu and switch to Base Cast,
ensure the LoRa is enabled.
I disable blutooth.
I change nothing else (this means that the TCP/UDP menu options are all left disabled)
when I hit “X” from the main menu after doing all of the configuring so that everything saves, I get a messages that say:
Base Caster Mode - SIV: 0
STATE_BASE_CASTER_NOT_STARTED → STATE_BASE_NOT_STARTED
STATE_BASE_NOT_STARTED → STATE_BASE_CONFIG_WAIT
Base Caster Mode - SIV: 0
Base configured
STATE_BASE_CONFIG_WAIT → STATE_BASE_TEMP_SETTLE
Batt (99%): Voltage: 8.25V Charging: 5.79%/hr
Waiting for Horz Accuracy < 2.00 (m): 0.00, SIV: 0
Waiting for Horz Accuracy < 2.00 (m): 0.00, SIV: 0
Base Caster Mode - SIV: 0
Waiting for Horz Accuracy < 2.00 (m): 0.00, SIV: 0
Waiting for Horz Accuracy < 2.00 (m): 0.00, SIV: 0
LoRa radio configured for transmitting
Base Caster Mode - SIV: 0
Waiting for Horz Accuracy < 2.00 (m): 0.00, SIV: 0
Waiting for Horz Accuracy < 2.00 (m): 0.00, SIV: 0
I hit a key to go back into the config menus, and it has changed itself back to Base mode.
I test it and it behaves like it is just a base without the Access Point enabled. No SSID comes up.
I then tried testing the wifi browser config menu, initially the config menu came up and all of the settings had been retained.
I hit the exit button from the browser config menu without changing anything. The torch restarted. I double tapped the power button, looked in the config menu and all looked unchanged.
I exit the browser menu, waited for the restart beep. and then shutdown and turned on the torch. double tapped the power button and checked the config in browser, nothing changed. I then, without exiting the browser, shut off the torch.
Checking the config again seemed to not change anything.
But then I double tapped the power button to turn off the “RTK Config” wifi.
I double tapped it to check one more time, and it had changed itself to rover again.
This is extremely helpful. Thank you! What version of firmware are you running so that we can attempt to reproduce the issue?
I hit a key to go back into the config menus, and it has changed itself back to Base mode.
Above, the system menu shows ‘Base’, but regular output shows Base Caster. This is likely a typo. I’ve reported the issue here.
My unit, running v3.1 firmware, is successfully starting WiFi AP. However, I do not have LoRa on.
Above, if I turn LoRa on, I get binary output (looks like RTCM). I suspect you are indoors (SIV is 0) so you are not seeing the RTCM since the base survey in has not completed. Is that correct?
Issue for RTCM output during serial is here.
I then tried testing the wifi browser config menu,
For now, let’s use the serial terminal, get it working, then move to Web Config and then we’ll confirm that interface.
But then I double tapped the power button to turn off the “RTK Config” wifi. I double tapped it to check one more time, and it had changed itself to rover again.
I’ve opened an issue for this here.
Apologies, I meant to add that. I had updated everything to the latest firmware and confirmed in the serial that they had updated before doing anything with the Torches:
RTK Everywhere: v 3.1
UM980: 11833
LoRa Firmware: v2.0.2
Also, I turned on the Torches and connected to serial indoors to show you the messages I was getting.
However, to test the LoRa and see if the base was sending the corrections to the rover, I brought them outside.
And it seems as though if the LoRa is not starting at all. All though I have not looked at the serial output of the base while it is outside to see.
Just to be clear on what I am trying to achieve.
I need the Torch to be broadcasting its SSID at the same time as it is broadcasting over LoRa.
Our drone needs the corrections via NTRIP from the Torch’s ssid.
And at the same time we have another torch that is receiving corrections via LoRa.
I apologize for spamming messages. I am just trying to ensure you guys have as much information to work with as possible.
Recent tests have brought this information about:
Firmware versions:
RTK Everywhere: 3.1
UM980: I updated to 17548
LoRa version: 2.0.2
The first thing I did was reset was do a factory reset on the Torch I use as a base.
I then changed the following settings
Switched to Base mode
enabled TCP server and checked the NTRIP box underneath it. set port to default 2948 (or whatever it is)
set TCP server access to AP.
left bluetooth enabled in “Dual” mode
Enabled LoRa as well.
I turned on the base, it started broadcasting the “RTK 9FCA” ssid.
I connect our drone controller to the wifi SSID
I connected my drone to it and put in:
IP 192.168.4.1
Port: 2101
mountpoint: SparkBase
My drone is able to receive RTK corrections.
I then disconnect the drone from the “RTK 9FCA” wifi.
I double tap the power button to turn on the “RTK Config” wifi SSID.
however, when i double tap. The SSID does not change. it remains “RTK 9FCA”
I connected to it and opened “rtk.local” on my phone browser. And I was able to view the browser config menu. I then used the “exit and reset” button.
The Torch restarted, and I was able to connect my drone again and it received corrections like before.
This entire time, there was no indication that the LoRa was broadcasting (no yellow LED on the indicator that is to the right of the powerbutton).
I was not expecting the wifi SSID to stay the same when I double tapped the power button to get to the config menu
Apologies for spamming again, but yet another update. I decided to test what would happen if I reverted the RTK Everywhere firmware from 3.1 to 2.3.
I initially started with the following firmware versions:
RTK Everywhere: 3.1
LoRa firmware: 2.0.2
UM980:17548
I then used RTK uploaded to revert the Torche to version RTK everywhere version 2.3. I did not change the UM980 or LoRa firmwares at all.
Then, for the torch i use as a base i did the following:
I did a factory reset.
I changed the mode to Base.
I enabled the LoRa Radio.
Nothing else changed.
For the Torch I use as a Rover I did the following:
I did a factory reset.
I left the mode as rover.
I turned on the LoRa Radio.
I made the LoRa the highest priority method for receiving corrections.
I changed nothing else.
I then bring the Torches outside, turned them on, The yellow LED on both torches were blinking, the rover torch’s green fix led was on, and sw maps confirmed it had a fix.
I turned them both off. brought the torch that acts as a base inside and then added this change to the configuration:
I enabled TCP server, Enabled the NTRIP checkbox underneatht the TCP server checkbox, and set the access method to AP.
I brought the torches back outside. turned them both on.
Their yellow LED’s started blinking. the Rover torch got a fix. but there was no SSID broadcasting.
I then brought in the torch that was acting as a base, I then made the following changes:
I switched TPC server’s AP mode to Wifi mode, I then disabled the “NTRIP Caster” in the “TCP/UDP” menu. After that, I disabled the TCP server.
I then switched the Torch from Base mode to Base Caster mode.
I then brought the torches and the drone outside for another test.
This time, the yellow LED’s on both torches were blinking. The Rover Torch was getting a fix. AND the Base WAS broadcasting an “RTK 9FCA03” SSID.
I then connected my drone to the base. However, the corrections were not stable. The WiFi signal from the “RTK 9FCA03” ssid was strong, however on my drone it indicated it would lose connection to the server quite frequently, and it never went passed RTK float.
I then turned off the torches, and made one last change to the base in the config menu: I turned of bluetooth.
After testing, the results were the same as the previous test: the LoRa was working, the Rover got an RTK Fix. The WiFi ssid was broadcasting, the drone was able to connect and get corrections. Although the wifi signal from the ssid remained strong, the drone indicated it would lose connection to the server periodically and it never went passed float.
All configuration changes were made via the serial menu in Tera Term with the torches connected to a desktop via a usb cable