I received my new GPS RTK2 board and the Bluetooth Mate Silver this week and started working with them yesterday. I followed the hookup guide for Connecting the GPS-RTK2 to a Correction Source. Everything worked great the first time. I shut everything down for the night and when I tried to hook up again today I can’t connect to the board at all. When I try to connect via usb in u-center the error message simply says “Can not connect to COM9 9600”. I tried disconnecting the bluetooth and get the same result. Any ideas?
Hi Danny,
That is a pretty strange error. Are you sure you are selecting the correct COM port and that it is not in use by another program like a terminal software? Double check the GPS is still showing up as a COM port in your Device Manager.
If you’re still having issues, please take a few photos of the top and bottom of your board and attach them to your reply.
Mark,
Thanks for the reply. I double checked the port was correct. I also manually removed the device from my Windows environment and when I plugged it back in the device reinstalled. When I then checked the device status in the device manager Windows reported the device is working properly. Next check was in u-center and the same problem persisted. Additionally, I plugged my C94-M8P board into the same physical USB on my computer and that device is working normally. I have attached some pictures as you requested.
Hi Danny,
Thanks for checking those suggestions and including the photos. They are very helpful. Nothing looks physically wrong with the board and I am pretty stumped with this error message as there is no documentation from u-blox about that specific issue. I have a feeling it is related to the USB cable or the USB connector on the board since your other u-blox board is connecting just fine.
Try opening a terminal using something like PuTTY or TeraTerm and check if you are still getting NMEA sentences printing from the ZED-F9P. Let me know if you have issues using a terminal program as well as u-center. If you happen to have another device with a USB Type C connector, try plugging it into your computer with the cable you are using with the ZED-F9P and see if you can interact with that device.
It may just be a defective cable that broke sometime after your first use and if that is the case, we can get you a replacement. If you do not have another USB Type C device and are not able to connect to the ZED-F9P with a terminal program, I think what would be best is to have the ZED-F9P and the USB cable sent back to SparkFun for testing.
I tried connecting with PuTTY and had similar results as u-center, not being able to make a connection at all. I tried connecting a smartphone with the same cable and was able to get a connection and transfer files with no issues. Sounds like it might be something integral to the board then?
It definitely seems like something is wrong with the serial connection on your ZED-F9P. If you purchased the GPS module directly from SparkFun, please fill out the form on the right side of [this page and link this forum post in the “Why do you want an RMA?” box and we will get you set up with an RMA ticket for your order.
If you did not purchase it directly from SparkFun, please send me a private message and we can discuss how we can move forward to resolve this issue.](Return Policy - SparkFun Electronics)
This is just a troubleshooting tip follow-up for this issue (or other similar issues with an unresponsive U-blox board) in case other users run into an issue like this with any of our U-blox-based GPS breakouts.
Testing confirmed the USB port was disabled or changed in a way that prevented u-center and other terminal programs from connecting to the board. Connecting it to an Arduino via I2C and running the [Factory Reset Example from the [SparkFun U-blox Arduino Library recovered the board and returned it to full functionality.
I hope this helps others who have strange behavior or unresponsive U-blox modules or just need to restore their GPS to factory settings.](GitHub - sparkfun/SparkFun_Ublox_Arduino_Library: Library to control UBX binary protocol and NMEA over I2C on Ublox GPS modules)](https://github.com/sparkfun/SparkFun_Ublox_Arduino_Library/tree/master/examples/Example10_ResetConfiguration)
@TS-Mark,
I have the exact same issue with two GPS_RTK2 boards. I do not see anything wrong on the board, and want to try unlocking the COM ports with an Arduino via I2C. I’m unfamiliar on how to wire up the Arduino with the GPS_RTK2 and would really appreciate any diagram you could give me. I do not currently have the QWICC cable, but can solder to the board if necessary.
Thanks.
Hi dr_knight,
Without a Qwiic cable, you can just solder to the I2C pins broken out on the side of the board like this photo shows: 
You can either solder wires to those pins or a male or female header to plug it into a breadboard or run M/F jumper wires to your Arduino. After that, just match the wires to the labeled I2C pins on your Arduino (eg. SDA->SDA, SCL->SCL, etc.) and then run the Factory Reset example from our Arduino Library I linked in my previous post.
Another option if you want to avoid soldering would be to use our [Qwiic Breadboard Jumper to convert from the Qwiic connector to your standard jumper wires.](Qwiic Cable - Breadboard Jumper (4-pin) - PRT-14425 - SparkFun Electronics)
Worked perfectly. I guess my 2 GPS_RTK2 boards were both locked out of the COM port. We did as you had to do and hooked up an Arduino via I2C, and used the Sparkfun library and the Reset script. Just giving you some feedback.