I read on another thread where a user had difficulty getting his device to stick when selecting ‘Reset to logging defaults’ in the WiFi GUI. He suggested there should/could be an icon on the LCD display to show if the unit was in Surveying or Logging defaults mode.
I had the same a couple of days ago, where I connected to three units in turn by WiFi, selected ‘Reset to logging defaults’, saved, restarted, and then reconnected to check it had stuck, only to find out after many hours of logging that it had not stuck and was in fact in ‘Surveying defaults’.
To that end, I would concur that an icon would be a good idea (granted that wont be so useful with user defined messages or with the RTK Surveyor…) Better still, on the device menu, have an option to toggle these two settings physically using the power/config button.
I ended up logging in with the ESP32 interface and reconfiguring the devices again, but all in all lost many hours of work. I can only assume that my browser cache kept showing old history and was not in fact refreshing the GUI of the device I was actually connected to at that time…
The device will load settings first from internal NVM, then from an SD card if available. The SD settings win. This allows a multitude of units to be programmed from one microSD card if needed. Perhaps you setup your unit, then inserted an SD card with alternate settings, overwriting your original intent. Please know that you can report issues over here: https://github.com/sparkfun/SparkFun_RT … are/issues Of course in all my hours of testing and poking, I’ve never seen anything like you describe (that would be far too easy for Murphy’s law!). If you can put together replicable steps, that would be ideal.
Know that a device can have up to 8 profiles. This makes it easier to switch between setups, but you are correct in that there is no icon indicating the profile that is currently running.
I forgot to say that I actually set them all to factory reset as well, prior to using the WebGUI to configure. That said, you could be right in that I probably did put the SD cards in afterwards, thus resetting them back to what they were previously configured as… I stupidly thought that settings in memory would trump settings on SD card (well to be honest clearly I didn’t put too much thought into it at all!). I’ll make sure I update our procedures to reflect this.
That said, my error only goes to serve as an example of how you really don’t know what is being logged (without going back into the configuration), and any visual indication would give some confidence when deploying the equipment for prolonged periods. Thanks for the guthub link.
Just thinking about this more. Maybe the dynamic image of the SD card filling up on the LCD screen could have a ‘S’ or ‘L’ (or ‘C’ for custom messages) superimposed over the card imagery?
Hi @sparky, thanks for this and great to see a suggestion make it way to firmware.
That said, is there any chance of getting menu items to be able to toggle between Surveying defaults / Logging (PPP) defaults? I had it again that I was in the Wifi config and set update to 1Hz, saved, then went and changed messages to ‘Logging defaults’, saved, and rebooted. But when it come up there was no ‘P’ on the display. Went and got another device and repeated and all good.
Not sure if it is a browser cache thing (and device has switched WiFi networks) but this has caught me out a number of times now.
Just to come back on this. Not sure when the profile support was implemented, but this is the perfect solution to my suggestion of having menu items for toggling between Surveying defaults / Logging (PPP) defaults and works very well. That said, yet again I have got caught out with the browser cache (when toggling between profiles). Seems if you refresh the browser then all the profile config comes up ok, but if not the messages settings are still displaying the cached values for the earlier profile (tested in Firefox and Edge).
Hello, what you express has happened to me many times.
As I know the subject, if I doubt, I leave the browser and go back to the wifi config page. The sad thing is that you will have to enter the modifications again.
That refreshes the data and generally solves my problems.
I’m not sure if refreshing the page has the same effect.
I’ve noticed logging configuration and other profile setting weirdness that I wonder might have been caused by my browser cache when using WiFI config. I’ve come back 6 hours later and found the log file doesn’t have the messages I thought I set it to have.
I’ve gotten better at closing my browser tabs first, then connecting to my Facet, and then to be sure to refresh when configuring my Facets. Though sometimes I forget…
