-
Notifications
You must be signed in to change notification settings - Fork 12
Description
Background:
I am using a Here GPS unit, utilizing only its UART pins. I have verified that the RX and TX are appropriately connected to the Mandeye's TX and RX, I have also verified that data is being collected and transmitted by the GPS both using an oscilloscope and using Minicom.
Issue:
Mandeye will not pickup the gps, giving the following output from curl http://127.0.0.1:8003/json/status:
"gnss": {
"buffer_size": 0,
"gga": {
"altitude": null,
"dgps_age": null,
"fix_quality": 0,
"hdop": null,
"height": null,
"latitude": null,
"longitude": null,
"satellites_tracked": 0,
"time": {
"h": 0,
"m": 0,
"s": 0
}
},
"init_success": true,
"is_logging": false,
"message_count": 0,
"nmea": {
"last_line": ""
}
}
However, if I run Minicom before Mandeye is ready, exiting with Ctrl + A + X, Mandeye will pickup the GPS, giving the following output from curl http://127.0.0.1:8003/json/status:
"gnss": {
"buffer_size": 0,
"gga": {
"altitude": removed for privacy,
"dgps_age": null,
"fix_quality": 1,
"hdop": removed for privacy,
"height": removed for privacy,
"latitude": removed for privacy
"longitude": removed for privacy,
"satellites_tracked": 5,
"time": {
"h": removed for privacy,
"m": 3,
"s": 50
}
},
"init_success": true,
"is_logging": false,
"message_count": 6,
"nmea": {
"last_line": "\n"
}
}
I have attempted to use stty to monitor the state of serial0 before and after running Minicom, and making those changes manually, however it doesn't seem to work. I have been able to successfully capture GNSS data during a long continuous scan using this "Minicom-first" method.
Thank you for all your time on this project! Please let me know if there are any tests you'd like me to do, or if I can supply you with more information.