To get into WiFi configuration follow these steps (from online docs):
Power the RTK Surveyor on in Rover mode. Once the device has started the Bluetooth status LED should be blinking at 1Hz. Now toggle the SETUP switch from Base and back to Rover within 1 second. If successful, the Bluetooth status LED will begin fading in/out. The device is now broadcasting as a WiFi access point. Connect to WiFi network named ‘RTK Config’.
Followed these directions, which has worked perfectly on my previously purchased GPS-18443 (order 9630112), no joy, no “RTK Config” wireless is discovered on GPS-18443 (order 9630119).
I note that the announced BT device name on the non-working GPS-18443 (order 9630119) is “Surveyor Rover-3932” while the working GPS-18443 (order 9630112) is “Surveyor Rover-8CAE”. If the announced BT device name incorporates something like the unit serial number expressed in hexadecimal.
GPS-18443 (order 9630112) “Surveyor Rover-8CAE” works every time according to the online directions quoted above.
So as an alternative:
https://docs.sparkfun.com/SparkFun_RTK_ … bluetooth/
The RTK device will be a discoverable Bluetooth device (both BT SPP and BLE are supported). For information about Bluetooth pairing, please see Connecting Bluetooth.
The "Connecting Bluetooth" is a link to:
https://docs.sparkfun.com/docs/connecting_bluetooth.md
Which does this:
404
File not found
Following posted directions and using “Serial Bluetooth Terminal” Android Play Store (looks like your illustration), I successfully make a connection. Settings are as illustrated:
https://docs.sparkfun.com/SparkFun_RTK_ … l-settings
What I get is a constant stream of data, sending “+” 3 times, or “+++” once changes nothing but characters are echoed.
This allows the opening of the config menu as well as the viewing of all regular system output.
How?
We are directed to:
https://docs.sparkfun.com/SparkFun_RTK_ … nal-window
Press any key to open the configuration menu.
and
Pressing any button will display the Main menu.
Doesn't change anything.
Resolved by updating very out-of-date firmware. Only one of the available upgrade paths was workable, the desktop GUI uploader, all the rest for my device were blocked by non-supporting firmware. I tried them all.
What version of firmware did you have? I’m having similar issues.