Warning: PPL is Offline Continuing to struggle with Woods, and RTK Torch Configuration

GPS/GNSS SparkPNT / Consumer Products
1

I searched for “PPL is offline” but didn’t find anything.

I continue to struggle to get an RTK Torch configuration that will work on my woods, where not only are the woods deep, the Cell Signal isn’t always the greatest….

Spent 3 hours Saturday at the top of the ridge, so less mountain in the way of satellite signal. And I could get e-mail on my phone so I believe data signal was working.

My configuration is SparkFun RTK Torch, connected to Android Tablet via Bluetooth for SW MAPS. RTK Torch connected over Wifi to iPhone HotSpot to get PointPerfect corrections. It was getting corrections from what I was seeing via serial port.

I could not get RTK Fix no matter what configuration tweak I tried.

And watching serial port for messages noticed this below:

Warning: PPL is offline.

The PUSHING statements would have varying byte sizes around xxx= 607, 177, 304, 152

Pushing xxx bytes from pp/ip/LAxxxxxxxxxx/N35 topic to PPL for UM980

Warning:PPL is offline

And I have occasionally seen an error
UM980 Rover failed to configure Rover config failed

but didn’t think I saw it this Saturday….. What does PPL is offline mean and did I just need to reboot to fix (which I failed to try ;( – stupid of me for sure….

ChatGPT says… this may actually be a known problem in firmware 2.2 ??
But Sarah Connor said not to trust it……

is there a Serial port command to restart PPL in the field or just need to get lucky and reboot until there isn’t an error?

And I didn’t read in Release Candidate 2.3RC that it was going to do anything about PPL Offline error?

2

And I tried updating UM980 to latest firmware from (build 17548)

and now I don’t get a version of UM980 displayed and now I can consistently get UM980 Rover failed to Configure and Warning: PPL is offline message

I’ve rebooted multiple times and now PPL is offline all the time, and UM980 won’t configure..

see Startup/Bootup messaged below

AC:15:18:92:7C:C0 - wifiMACAddress
AC:15:18:92:7C:C2 - btMACAddress
AC:15:18:92:7C:C3 - ethernetMACAddress
LittleFS Started
Using profile #0
PSRAM Size (bytes): 2097152
I2C Devices:
0x08 - HUSB238 Power Delivery Sink Controller
0x0B - BQ40Z50 Battery Pack Manager / Fuel gauge
0x5C - MP27692A Power Management / Charger
0x60 - ATECC608A Cryptographic Coprocessor

SparkFun RTK Torch v2.2

GNSS UM980 online
Profile ‘PPerfectTiltOFF’ loaded
Fuel gauge configuration complete
Charger configuration complete
UM980 configuration maintained
No GNSS date/time available for system RTC.
UM980 Rover failed to configure
Rover config failed

I am going to put version 11833 back on…. which may or may not have been the version it had?

3

Replaced firmware to 11833 and the errors for PPL Offline and UM980 Rover failed to Configure went way… but Version of UM980 does not show version on boot up, so not sure what version is really running

AC:15:18:92:7C:C0 - wifiMACAddress
AC:15:18:92:7C:C2 - btMACAddress
AC:15:18:92:7C:C3 - ethernetMACAddress
LittleFS Started
Using profile #0
PSRAM Size (bytes): 2097152
I2C Devices:
0x08 - HUSB238 Power Delivery Sink Controller
0x0B - BQ40Z50 Battery Pack Manager / Fuel gauge
0x5C - MP27692A Power Management / Charger
0x60 - ATECC608A Cryptographic Coprocessor

SparkFun RTK Torch v2.2

GNSS UM980 online
Profile ‘PPerfectTiltOFF’ loaded
Fuel gauge configuration complete
Charger configuration complete
UM980 configuration maintained
No GNSS date/time available for system RTC.
Bluetooth SPP and BLE broadcasting as: Torch Rover-7CC2
STATE_ROVER_NOT_STARTED → STATE_ROVER_NO_FIX
Rover Accuracy (m): 0.000, SIV: 0 GNSS State: No Fix
Rover Accuracy (m): 0.000, SIV: 0 GNSS State: No Fix
WiFi station state: WIFI_STATION_STATE_OFF, No consumers
MQTT Client state: MQTT_CLIENT_OFF, MQTT not enabled!
MQTT Client subscribe topics:
MQTT Client subscribed topics:
Network: Offline
WiFi Soft AP: Offline
Correction Source: None
Rover Accuracy (m): 0.000, SIV: 0 GNSS State: No Fix
Rover Accuracy (m): 0.000, SIV: 0 GNSS State: No Fix
Rover Accuracy (m): 0.000, SIV: 0 GNSS State: No Fix

This seems better….

Pushing 157 bytes from pp/ip/L4N3xxxxxx topic to PPL for UM980
Rover Accuracy (m): 3.449, SIV: 12 GNSS State: 3D Fix
Rover Accuracy (m): 3.339, SIV: 13 GNSS State: 3D Fix
Pushing 157 bytes from pp/ip/L4N3xxxxxxxxx topic to PPL for UM980
Rover Accuracy (m): 3.956, SIV: 14 GNSS State: 3D Fix
Rover Accuracy (m): 4.285, SIV: 14 GNSS State: 3D Fix
Rover Accuracy (m): 3.900, SIV: 14 GNSS State: 3D Fix
Pushing 157 bytes from pp/ip/L4N3xxxxxxxxxxxxxxxxxxxxx topic to PPL for UM980

Two cold reboots and no errors… and push to PPL for UM980 successful

I will test at house Monday (Oct 6, 2025) - raining… Tuesday….

4

Testing Oct 9th 5pm. Better… but in mostly wide open in my opinion it lost RTK Fix after only about 100 points averaged. Then in about 5 min got it back for 60avg, lost it briefly then averaged continued to get to 120 before writing it.

And I did it 3 times and via SW Maps it said the 3 readings were 0.9ft apart?(Per SWMaps, however when I exported and had ChatGPT calculate distances apart point 1 was 5 inches from 2&3 and 2&3 were only 0.75 inches apart) even when the points were recorded with RTK FIX avg of 80-12 readings each?

Does this look like too much surrounding trees to maintain RTK Fix??

, or do I still have some software configuration issues? No PPL error on push to UM980. And it seemed to be downloading bytes from PointPerfect and pushing them over to UM980 without error.

IMG_69751
IMG_697511920×443 138 KB

IMG_69741
IMG_697411920×448 142 KB

5

clarifying the first reading where RTK Fix failed after 60 average points was 5 inches away from points 2 and 3. Points 2 and 3 recorded as only 0.75 inches apart… darn good, but not good that within 15 minutes they should all be 0.75 right? I’m I just expecting too much from PointPerfect corrections and bad cell service? And trees and not a wide open 100 acres field in Iowa?

6

Hi Chris - you’re reports and testing are superb. I don’t want to muddy the waters too much, but your correction source (PointPerfect MQTT over IP) is good but not what we’re recommending anymore. 1) u-blox is EOL’ing it fall of 2026, and 2) We’ve found it performs worse than their Flex RTCM/NTRIP service. I have a strong belief they use different models behind the curtain (MQTT being the original, NTRIP being newer/better). Would you consider giving the NTRIP/RTCM a test and letting us know your results? I’m happy to give you NTRIP credentials that will last for 30-days.

1 Like
7

Sorry - I didn’t address your other issues: v11833 is what ships on most Torches, v13504 has HAS support, and v17548 is the newest/latest that our ESP32 firmware is not wholly tested with. I recommend v13504. Additionally, we release ‘release candidates’ of the ESP32 firmware that may be helpful if you want to try the latest features and compatibilities with v17548 UM980 firmware. Just know the RCs are in a great state of flux (so don’t use it in the field if you need to get work done!) but should be functional.

8

Sparky, would be more than happy to test RTCM/NTRIP, but let’s do it in December when the leaves are down in East Tennessee, I will have more time to test, and the test is more likely to succeed. (I used the Book Mark function to set a reminder for me December 1 to reach out to you)

9

My “Work” isn’t too serious, so I can try some things occasionally, but then some deadline comes up and I need drop everything else to take care of the “new” priority. I will first tryout v13504 and see how it changes any of my results testing either on my 155ft test stretch or out in the valleys and ridge tops of our forest. The big push this December is a 3,517.33ft stretch along the ridge top, with 34 directional calls. I’m hoping that being on the ridge top increases my odds of success.

10

Under Firmware 2.2, and UM980 v13504, it still does not report version of UM980 firmware at boot up.

(1216) esp_cor��VW
}���͡� No core dump partition found!
E (1216) esp_core_dump_flash: No core dump partition found!

AC:15:18:92:7C:C0 - wifiMACAddress
AC:15:18:92:7C:C2 - btMACAddress
AC:15:18:92:7C:C3 - ethernetMACAddress
LittleFS Started
Using profile #0
PSRAM Size (bytes): 2097152
I2C Devices:
0x08 - HUSB238 Power Delivery Sink Controller
0x0B - BQ40Z50 Battery Pack Manager / Fuel gauge
0x5C - MP27692A Power Management / Charger
0x60 - ATECC608A Cryptographic Coprocessor

SparkFun RTK Torch v2.2

GNSS UM980 online
Profile ‘PPerfectTiltOFF’ loaded
Fuel gauge configuration complete
Charger configuration complete
UM980 configuration maintained
No GNSS date/time available for system RTC.
Bluetooth SPP and BLE broadcasting as: Torch Rover-7CC2

Initial test outdoors achieved RTK Fix quickly, and I will do additional testing this afternoon to see if UM980 v13504 holds RTK Fix better (assuming upgrade worked as version is not reported)

11

October 10th - hour and half of testing outside…. Failure

upgraded to v13504 on UM390. Boot up did not show version of UM390 but doing the upgrade did not show any errors so assuming it worked. Unfortunately this upgrade did not help get RTK FIX. And in testing in the exact same locations, and also in one area with clearer view of the sky I still failed to get RTK Fix. And after trying various satellite elevation settings, signal/noise settings the WARNING: PPL Offline came back but after a reboot went away. I am going to try to go to a more wide open field, and if that fails on RTK Fix there must be something else wrong with what I am doing.

12

@sparky The leaves are all down here in East Tennessee, so I am going to start doing some Surveying work on the Farm using my existing PointPerfect subscription. After I give that a go for a few sessions, I would be interested in testing the new service, probably early January.

Is your offer still available?

Also the billing department may need to know exactly how to deal with it, as Maria is currently trying to resolve a double billing issue that started back in September. Happy Holidays (12/15/2025)

1 Like
13

Yep! Credentials will be PM’d.

2 Likes
14

Thanks - and any special configuration settings to share with the community? I believe I was holding corrections in the past for 60 seconds maybe more due to my poor signal quality in the deep woods (don’t quote me on that time as my memory isn’t what it used to be) …. basically should the RKT Torch have any special settings to do things differently than the legacy PointPerfect corrections? I hope to try it out in front of the house this week, and at the farm/woods within a week or two

15

If you’re brave, start from a factory reset, but if you’ve got too many settings configured, I recommend disabling PointPerfect so that the device is not trying to start WiFi or get corrections over the legacy system.

2 Likes
16

I have tried so many settings, and set them to so many values I think factory reset is totally in order. I will start with that now (2:28pm EST) and see how it goes.. probably post an update tomorrow. As a base case I just took it out there with my legacy settings and set in on my test tract, and it never got better than DGPS accuracy and consistently said I was 1-2ft from my marker. It was reporting getting legacy PPP corrections ok…. wish me luck….

boom GIF

17

Quick update - results are very promising but one day of testing can be …. Misleading. I was able to maintain RTK Fix for over an hour and also went down into the valley behind my house 40-50ft down from test track and surrounded by woods and maintained RTK Fix for 10 minutes…. Then it started raining. Tomorrow I will test more extensively

3 Likes
18

You’re going to love the RTCM PP over NTRIP :wink:

It can’t perform any special magic under heavy canopy, but I’ve found it far superior to the “old” MQTT PP. I think that’s mostly due to being OSR verses SSR.

1 Like
19

Day two - test 1 - My configuration is FACTORY defaults, RTK Torch software version 2.2
The only settings changes I made were to Add the Credentials @sparky gave me, add WiFi configurations, and set PointPerfect Corrections to FLEX NTRIP/RTCM

I am getting RTK Fix in under a minute (restarting at nearby shutdown point so may resolve faster)

But it’s resolving and keeping RTK Fix. And it’s raining and cloudy so that might reflect signals, but it’s working like a champ…. I want to drive to the Farm/Forest right now!!! Awesome so far.

I didn’t even change the MINIMUM ELEVATION FOR A GNSS SATELLITE
or MINIMUM SATELLITE SIGNNAL LEVEL FOR NAVIGATION
although once in my dense woods, I may need to experiment

Once it stops raining I will put on boot and just hike into the woods behind the house to test, which has as bad a view of the horizon as most of my woods, good test without driving 45minutes to the farm….. I AM VERY EXCITED!!!

Below is my current Config (minus Password and identifying details)

Menu: User Profiles

  1. Select TestCorrectionService ← Current
  2. Select (Empty)
  3. Select (Empty)
  4. Select (Empty)
  5. Select (Empty)
  6. Select (Empty)
  7. Select (Empty)
  8. Select (Empty)
  9. Edit profile name: TestCorrectionService
  10. Set profile ‘TestCorrectionService’ to factory defaults
  11. Delete profile ‘TestCorrectionService’
  12. Print profile
    x) Exit
    12
    Select the profile to be printed (1-8): 1

sizeOfSettings=4000

rtkIdentifier=34
antennaHeight_mm=1800
antennaPhaseCenter_mm=116.50
coordinateInputType=0
fixedAltitude=1560.0890
fixedBase=0
fixedBaseCoordinateType=0
fixedEcefX=-1280206.568
fixedEcefY=-4716804.403
fixedEcefZ=4086665.484
fixedLat=40.090294790
fixedLong=-105.185057610
observationSeconds=60
observationPositionAccuracy=5.00
surveyInStartingAccuracy=2.0
enablePrintBatteryMessages=1
shutdownNoChargeTimeoutMinutes=0
enableBeeper=1
bluetoothRadioType=2
sppRxQueueSize=2048
sppTxQueueSize=32
correctionsSourcesLifetime=30
correctionsPriority_External Radio=2
correctionsPriority_ESP-Now=3
correctionsPriority_LoRa Radio=4
correctionsPriority_Bluetooth=5
correctionsPriority_USB Serial=6
correctionsPriority_TCP (NTRIP)=1
correctionsPriority_L-Band=7
correctionsPriority_IP (PointPerfect/MQTT)=0
debugCorrections=0
debugEspNow=0
enableEspNow=0
espnowPeerCount=0
espnowPeer_0=00:00:00:00:00:00,
espnowPeer_1=00:00:00:00:00:00,
espnowPeer_2=00:00:00:00:00:00,
espnowPeer_3=00:00:00:00:00:00,
espnowPeer_4=00:00:00:00:00:00,
autoFirmwareCheckMinutes=1440
debugFirmwareUpdate=0
enableAutoFirmwareUpdate=0
serialGNSSRxFullThreshold=50
uartReceiveBufferSize=2048
debugGnss=0
enablePrintPosition=0
measurementRateMs=500
navigationRate=1
gnssConfiguredOnce=1
gnssConfiguredBase=0
gnssConfiguredRover=1
debugHttpClientData=0
debugHttpClientState=0
debugMqttClientData=0
debugMqttClientState=0
mdnsEnable=1
mdnsHostName=rtk
debugNetworkLayer=0
printNetworkStatus=1
debugNtripClientRtcm=0
debugNtripClientState=0
enableNtripClient=1

ntripClientCasterHost=ppnXXXXX DETAILS OF HOST HERE

ntripClientCasterPort=2101

ntripClientCasterUser= MY USER ID HERE

ntripClientCasterUserPW= MY PASSWORD HERE

ntripClientMountPoint=NEAR-RTCM

ntripClientMountPointPW=
ntripClientTransmitGGA=1
debugNtripServerRtcm=0
debugNtripServerState=0
enableNtripServer=0
enableRtcmMessageChecking=0
ntripServerCasterHost_0=rtk2go.com
ntripServerCasterHost_1=
ntripServerCasterHost_2=
ntripServerCasterHost_3=
ntripServerCasterPort_0=2101
ntripServerCasterPort_1=2101
ntripServerCasterPort_2=2101
ntripServerCasterPort_3=2101

ntripServerCasterUser_0=test@test.com

ntripServerCasterUser_1=
ntripServerCasterUser_2=
ntripServerCasterUser_3=
ntripServerCasterUserPW_0=
ntripServerCasterUserPW_1=
ntripServerCasterUserPW_2=
ntripServerCasterUserPW_3=
ntripServerMountPoint_0=bldr_dwntwn2
ntripServerMountPoint_1=
ntripServerMountPoint_2=
ntripServerMountPoint_3=
ntripServerMountPointPW_0=WR5wRo4H
ntripServerMountPointPW_1=
ntripServerMountPointPW_2=
ntripServerMountPointPW_3=
bluetoothInterruptsCore=1
btReadTaskCore=1
btReadTaskPriority=1
debugMalloc=0
enableHeapReport=0
enablePrintIdleTime=0
enablePsram=1
enableTaskReports=0
gnssReadTaskCore=1
gnssReadTaskPriority=1
gnssUartInterruptsCore=1
handleGnssDataTaskCore=1
handleGnssDataTaskPriority=1
i2cInterruptsCore=1
measurementScale=0
printBootTimes=0
printPartitionTable=0
printTaskStartStop=0
psramMallocLevel=40
rebootMinutes=0
resetCount=0
periodicDisplay=137438953988
periodicDisplayInterval=15000
autoKeyRenewal=1
debugPpCertificate=0
geographicRegion=0
lastKeyAttempt=0
lbandFixTimeout=180
pointPerfectBrokerHost=
pointPerfectClientID=
pointPerfectCurrentKey=
pointPerfectCurrentKeyDuration=0
pointPerfectCurrentKeyStart=0
pointPerfectDeviceProfileToken=
pointPerfectKeyDistributionTopic=
pointPerfectNextKey=
pointPerfectNextKeyDuration=0
pointPerfectNextKeyStart=0
pplFixTimeoutS=180
regionalCorrectionTopics_0=
regionalCorrectionTopics_1=
regionalCorrectionTopics_2=
regionalCorrectionTopics_3=
regionalCorrectionTopics_4=
pointPerfectService=1
profileName=TestCorrectionService
enablePrintRingBufferOffsets=0
gnssHandlerBufferSize=4096
dynamicModel=0
enablePrintRoverAccuracy=1
minCNO=10
minElev=10
enablePrintRtcSync=0
dataPortBaud=115200
echoUserInput=1
enableGnssToUsbSerial=0
radioPortBaud=57600
serialTimeoutGNSS=1
disableSetupButton=0
enablePrintDuplicateStates=0
enablePrintStates=0
lastState=0
debugTcpClient=0
enableTcpClient=1
tcpClientHost=
tcpClientPort=2948
debugTcpServer=0
enableTcpServer=0
tcpServerPort=2948
tcpUdpOverWiFiStation=1
timeZoneHours=0
timeZoneMinutes=0
timeZoneSeconds=0
debugUdpServer=0
enableUdpServer=0
udpServerPort=10110
enableGalileoHas=0
enableImuCompensationDebug=0
enableImuDebug=0
enableTiltCompensation=1
constellation_BeiDou=1
constellation_Galileo=1
constellation_GLONASS=1
constellation_GPS=1
constellation_QZSS=1
messageRateNMEA_GPDTM=0.00
messageRateNMEA_GPGBS=0.00
messageRateNMEA_GPGGA=0.50
messageRateNMEA_GPGLL=0.00
messageRateNMEA_GPGNS=0.00
messageRateNMEA_GPGRS=0.00
messageRateNMEA_GPGSA=0.50
messageRateNMEA_GPGST=0.50
messageRateNMEA_GPGSV=1.00
messageRateNMEA_GPRMC=0.50
messageRateNMEA_GPROT=0.00
messageRateNMEA_GPTHS=0.00
messageRateNMEA_GPVTG=0.00
messageRateNMEA_GPZDA=0.00
messageRateRTCMBase_RTCM1001=0.00
messageRateRTCMBase_RTCM1002=0.00
messageRateRTCMBase_RTCM1003=0.00
messageRateRTCMBase_RTCM1004=0.00
messageRateRTCMBase_RTCM1005=1.00
messageRateRTCMBase_RTCM1006=0.00
messageRateRTCMBase_RTCM1007=0.00
messageRateRTCMBase_RTCM1009=0.00
messageRateRTCMBase_RTCM1010=0.00
messageRateRTCMBase_RTCM1011=0.00
messageRateRTCMBase_RTCM1012=0.00
messageRateRTCMBase_RTCM1013=0.00
messageRateRTCMBase_RTCM1019=0.00
messageRateRTCMBase_RTCM1020=0.00
messageRateRTCMBase_RTCM1033=10.00
messageRateRTCMBase_RTCM1042=0.00
messageRateRTCMBase_RTCM1044=0.00
messageRateRTCMBase_RTCM1045=0.00
messageRateRTCMBase_RTCM1046=0.00
messageRateRTCMBase_RTCM1071=0.00
messageRateRTCMBase_RTCM1072=0.00
messageRateRTCMBase_RTCM1073=0.00
messageRateRTCMBase_RTCM1074=1.00
messageRateRTCMBase_RTCM1075=0.00
messageRateRTCMBase_RTCM1076=0.00
messageRateRTCMBase_RTCM1077=0.00
messageRateRTCMBase_RTCM1081=0.00
messageRateRTCMBase_RTCM1082=0.00
messageRateRTCMBase_RTCM1083=0.00
messageRateRTCMBase_RTCM1084=1.00
messageRateRTCMBase_RTCM1085=0.00
messageRateRTCMBase_RTCM1086=0.00
messageRateRTCMBase_RTCM1087=0.00
messageRateRTCMBase_RTCM1091=0.00
messageRateRTCMBase_RTCM1092=0.00
messageRateRTCMBase_RTCM1093=0.00
messageRateRTCMBase_RTCM1094=1.00
messageRateRTCMBase_RTCM1095=0.00
messageRateRTCMBase_RTCM1096=0.00
messageRateRTCMBase_RTCM1097=0.00
messageRateRTCMBase_RTCM1104=0.00
messageRateRTCMBase_RTCM1111=0.00
messageRateRTCMBase_RTCM1112=0.00
messageRateRTCMBase_RTCM1113=0.00
messageRateRTCMBase_RTCM1114=0.00
messageRateRTCMBase_RTCM1115=0.00
messageRateRTCMBase_RTCM1116=0.00
messageRateRTCMBase_RTCM1117=0.00
messageRateRTCMBase_RTCM1121=0.00
messageRateRTCMBase_RTCM1122=0.00
messageRateRTCMBase_RTCM1123=0.00
messageRateRTCMBase_RTCM1124=1.00
messageRateRTCMBase_RTCM1125=0.00
messageRateRTCMBase_RTCM1126=0.00
messageRateRTCMBase_RTCM1127=0.00
messageRateRTCMRover_RTCM1001=0.00
messageRateRTCMRover_RTCM1002=0.00
messageRateRTCMRover_RTCM1003=0.00
messageRateRTCMRover_RTCM1004=0.00
messageRateRTCMRover_RTCM1005=0.00
messageRateRTCMRover_RTCM1006=0.00
messageRateRTCMRover_RTCM1007=0.00
messageRateRTCMRover_RTCM1009=0.00
messageRateRTCMRover_RTCM1010=0.00
messageRateRTCMRover_RTCM1011=0.00
messageRateRTCMRover_RTCM1012=0.00
messageRateRTCMRover_RTCM1013=0.00
messageRateRTCMRover_RTCM1019=0.00
messageRateRTCMRover_RTCM1020=0.00
messageRateRTCMRover_RTCM1033=0.00
messageRateRTCMRover_RTCM1042=0.00
messageRateRTCMRover_RTCM1044=0.00
messageRateRTCMRover_RTCM1045=0.00
messageRateRTCMRover_RTCM1046=0.00
messageRateRTCMRover_RTCM1071=0.00
messageRateRTCMRover_RTCM1072=0.00
messageRateRTCMRover_RTCM1073=0.00
messageRateRTCMRover_RTCM1074=0.00
messageRateRTCMRover_RTCM1075=0.00
messageRateRTCMRover_RTCM1076=0.00
messageRateRTCMRover_RTCM1077=0.00
messageRateRTCMRover_RTCM1081=0.00
messageRateRTCMRover_RTCM1082=0.00
messageRateRTCMRover_RTCM1083=0.00
messageRateRTCMRover_RTCM1084=0.00
messageRateRTCMRover_RTCM1085=0.00
messageRateRTCMRover_RTCM1086=0.00
messageRateRTCMRover_RTCM1087=0.00
messageRateRTCMRover_RTCM1091=0.00
messageRateRTCMRover_RTCM1092=0.00
messageRateRTCMRover_RTCM1093=0.00
messageRateRTCMRover_RTCM1094=0.00
messageRateRTCMRover_RTCM1095=0.00
messageRateRTCMRover_RTCM1096=0.00
messageRateRTCMRover_RTCM1097=0.00
messageRateRTCMRover_RTCM1104=0.00
messageRateRTCMRover_RTCM1111=0.00
messageRateRTCMRover_RTCM1112=0.00
messageRateRTCMRover_RTCM1113=0.00
messageRateRTCMRover_RTCM1114=0.00
messageRateRTCMRover_RTCM1115=0.00
messageRateRTCMRover_RTCM1116=0.00
messageRateRTCMRover_RTCM1117=0.00
messageRateRTCMRover_RTCM1121=0.00
messageRateRTCMRover_RTCM1122=0.00
messageRateRTCMRover_RTCM1123=0.00
messageRateRTCMRover_RTCM1124=0.00
messageRateRTCMRover_RTCM1125=0.00
messageRateRTCMRover_RTCM1126=0.00
messageRateRTCMRover_RTCM1127=0.00
httpPort=80
debugWebServer=0
debugWifiState=1
enableCaptivePortal=1
wifiChannel=1
wifiConfigOverAP=0
wifiNetwork_0SSID=Surveillance249
wifiNetwork_0Password= PASSWORD HERE
wifiNetwork_1SSID=Peanut2.4
wifiNetwork_1Password= PASSWORD HERE
wifiNetwork_2SSID=ATTforthedogs
wifiNetwork_2Password= PASSWORD HERE
wifiNetwork_3SSID=
wifiNetwork_3Password=
wifiConnectTimeoutMs=20000
outputTipAltitude=327680
useLocalizedDistribution=0
localizedDistributionTileLevel=5
useAssistNow=0
requestKeyUpdate=0
enableLora=0
loraCoordinationFrequency=910.000
debugLora=0
loraSerialInteractionTimeout_s=30
enableMultipathMitigation=1
debugSettings=0
enableNtripCaster=0
baseCasterOverride=0
rtkFirmwareVersion=v2.2
gnssFirmwareVersion=13504
gnssUniqueId=ff3bd4976a7d169b
otaRcFirmwareJsonUrl=
otaFirmwareJsonUrl=

Menu: User Profiles

  1. Select TestCorrectionService ← Current
  2. Select (Empty)
  3. Select (Empty)
  4. Select (Empty)
  5. Select (Empty)
  6. Select (Empty)
  7. Select (Empty)
  8. Select (Empty)
  9. Edit profile name: TestCorrectionService
  10. Set profile ‘TestCorrectionService’ to factory defaults
  11. Delete profile ‘TestCorrectionService’
  12. Print profile
    x) Exit
20

Many thanks for sharing Chris (@ChrisO ),

This line jumps out at me:

outputTipAltitude should be boolean: 0 or 1

This is what caused this bug to appear…

If you’ve done a Factory Reset, then outputTipAltitude should default to 0 (false).

I wonder if it could be caused by outputTipAltitude not being passed to the web config page correctly. We’ve just added a fix for that - but it hasn’t yet made its way into a release.

I’ll keep scratching my head about this…!

Tagging @sparky just so he is aware.

Best,
Paul

1 Like