I have a set up where I am using a survey grade Hemisphere R632 GNSS receiver capable of outputting RTCM as a virtual base station via an internal NTRIP Caster.
I have tested the functionality using an NTRIP Client (Lefebure) and can see the stream OK, but when configuring on my RTK Express I note that I cannot configure the NTRIP Caster address with a static IP (so can only assume it will accept only DQDN like ‘rtk2go.com’)?
is there any way to hack an internal hosts file or something, or can it be added to a future firmware update to allow IPv4 addresses?
Hi Sparky, updated 2x Facets from 2.2 to 2.5 OK, then went to the RTK Express and as far as I can see the web GUI disappeared and I have a duff flash. I cannot power on and it is not charging on any port now. Is there a recovery procedure to get it going again?
as far as I can see the web GUI disappeared and I have a duff flash
web GUI - do you mean the RTK Uploader? Please close and reopen it. If the unit is not properly powering on, you can force power-off the device by holding the power button for ~15 seconds with no USB cable attached. This will force the power system off. Press the power button for ~3s and the unit should power on and stay on.
Do you have access to Tera Term (https://ttssh2.osdn.jp/index.html.en)? Close all other programs that use the COM port that the CH340 is using. Then try opening the port using TeraTerm. I’ve seen TeraTerm toggle the DTR/RTS lines in a way that correctly resets the ESP32.
Hi Sparky, the CH340 was only visible for about 5-10 seconds before it disappeared as a port in Win11…
Okay, for anybody else who accidentally bricked it, this is what I managed to get to work. Change to a USB A to USB C cable (I was using USB C to USB C). Once connected the charging light come on. When trying to power on nothing happened, but the CH340 port did enumerate in Windows and then stay active. From there I was able to use the RTK_Firmware_Uploader_GUI again to flash the 2.5 firmware. A reboot and all was good again…
Just a quick update in that I managed to brick the RTK Express again during a firmware update. This time it didn’t matter what cable I used (USB C or USB A). However, if I used both ports (one to power at the ublox port, and one for the update on the ESP32 port) I managed to enumerate a port and reflash and recover! Hope that helps someone.