I have recently set up the esp32/ublox caster using the example 14 from the library it works great!! However I was wondering what part of the code I could delete in order not to have to press a key in order to start sending corrections. The caster is emlid so I’m not worried about being kicked off like rtk2go.
Ran a bench test on it and preformed flawlessly, however since there was no antenna plugged in no rctm data was being pushed out(as expected). Then rctm disconnect was activated thus requiring the keyboard entry again. Is there a way to remove this as well? Just thinking in the odd case it loses the
satellites I don’t have to go back on my roof to reset it.
Thank you for sharing your knowledge it helps a lot to us newbies!
This setup has been working for me until the other day. I have a Solar panel and a battery bank . We had a week of bad weather and my panel didn’t produce enough power to keep the batteries going until the next morning. Would it be possible to delete or add Moore code in the case of a power outage that it will reconnect without reset?
I’ve also noticed that the pps light no longer flashes. As soon as I reset the ESP32 it goes away, having the u centre open I can see it drops a lot of bands if I disconnect the ESP32 they come back.
If your battery voltage falls very slowly, the ESP32 may get itself into a state where it does not restart when the voltage increases (slowly) again. I have seen this on other processors - including the SAMD21. I have not seen it on ESP32, but I have not tested it either.
I think you probably need a “reset supervisor”. This is a small hardware device which holds the processor in Reset when the voltage is low. And then brings the processor out of reset when the voltage increases. I would recommend trying a reset voltage of 3.0V.
It might be useful to hold both the ESP32 and the ZED-F9P in reset when the voltage is low. The Reset signal is “active low” on both boards, so it is OK to link the Reset signals together.
Thank you I will take a look a the reset supervisors. I forgot to mention that this problem even happens with bench testing as soon as the ESP32 is connected it drops all the satellites. I have the zed f9p connected to via usb to the pc and the ESP32 via qwiic. I have even tried with another ESP32/zed f9p board/qwiic cable… when the esp32 is not connected the zed will pick up all satellites and flash in pps mode with u centre showing connections the moment esp 32 is connected u centre shows no more satellites and pps mode is no longer flashing.
I’m going to try uploading the original sketch code and see if the problem is still occurs.
In stand alone operation the esp 32 is providing power to the zed f9p, bench test the zed is providing the esp (just so u-centre can work). That being said after comparing the original code to the new one I noticed I make a big mistake and imputed my new coordinates incorrectly by using the last 2 numbers not adding the 0 at the end. It works as intended now! Assuming that the two are communicating to Each other the discrepancy would cause it drop?
I also wanted to say thank you for all your help!! I never thought I would want to learn about coding or building electronics but you have inspired me not only to keep going but to also share knowledge!!
I’ve run into a few more issues and wanted to run them by you.
After a few days I notice the esp32 disconnects from the wifi and requires a reset. After some digging on the internet it seams that this can be a common issue. Ive found some that states you can use “WiFi.reconnect()” in combination with “WiFi.disconnect()” and “ESP.restart()
What are your thoughts? And if so where would be a good place to insert it in the code?
Testing for things which take “a few days” to appear, takes up a huge amount of time and needs a dedicated hardware setup. I will try and investigate this and provide some recommendations on how to modify the code, but I will not be able to do that soon. Sorry!
Just want to give you an update as the esp32 working great since the last reset!(june 2) I believe the problem was with my Solar charger not the esp 32 itself.