Closed brandonros closed 3 years ago
philrandal
commented
3 years ago This usually means that something else has its mitts on the serial device, preventing gpsctl from syncing.
As my modifications to the upstream code consist mainly of config file handling, I am not sure how you can resolve the issue.
I've never tried this code against a USB interface. It's not designed for that purpose and I have no idea what modifications to the code would be necessary to support USB devices, if any.
brandonros
commented
3 years ago I plugged the same device into a Windows laptop (above was from Mac OS X) and it semi-worked with the u-blox software. I will update when I get the antenna that goes with it.
philrandal
commented
3 years ago The program was written for Raspberry Pis with the Uputronics GPS HAT. I've tested on Raspberry Pi OS Jessie, Buster, and Bullseye. Any other platform and you're on your own. Your symptoms suggest that another program is trying to access the GPS module at the same time as gpsctl
brandonros
commented
3 years ago Ok. I appreciate the help. Last thing, do you think it would be an easy fix to be able to work with gpsctl given the fact that screen actually works?
Brandons-MacBook-Air:gpsctl brandonros 2021-08-18 19:04:57 $ screen /dev/tty.usbmodem11401 9600
$GNTXT,01,01,02,u-blox AG - www.u-blox.com*4E
$GNTXT,01,01,02,HW UBX-M8030 00080000*60
$GNTXT,01,01,02,ROM CORE 3.01 (107888)*2B
$GNTXT,01,01,02,FWVER=SPG 3.01*46
$GNTXT,01,01,02,PROTVER=18.00*11
$GNTXT,01,01,02,GPS;GLO;GAL;BDS*77
$GNTXT,01,01,02,SBAS;IMES;QZSS*49
$GNTXT,01,01,02,GNSS OTP=GPS;GLO*37
$GNTXT,01,01,02,LLC=FFFFFFFF-FFFFFFFF-FFFFFFFF-FFFFFFFF-FFFFFFFD*2F
$GNTXT,01,01,02,ANTSUPERV=AC SD PDoS SR*3E
$GNTXT,01,01,02,ANTSTATUS=OK*25
$GNTXT,01,01,02,PF=3FF*4B
$GNRMC,,V,,,,,,,,,,N*4D
$GNVTG,,,,,,,,,N*2E
$GNGGA,,,,,,0,00,99.99,,,,,,*56
$GNGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*2E
$GNGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*2E
$GPGSV,1,1,00*79
$GLGSV,1,1,00*65
$GNGLL,,,,,,V,N*7A
$GNRMC,,V,,,,,,,,,,N*4D
$GNVTG,,,,,,,,,N*2E
$GNGGA,,,,,,0,00,99.99,,,,,,*56
$GNGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*2E
$GNGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*2E
$GPGSV,1,1,00*79
$GLGSV,1,1,00*65
$GNGLL,,,,,,V,N*7A
$GNRMC,,V,,,,,,,,,,N*4D
$GNVTG,,,,,,,,,N*2E
$GNGGA,,,,,,0,00,99.99,,,,,,*56
$GNGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*2E
$GNGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*2E
$GPGSV,1,1,00*79
$GLGSV,1,1,00*65
$GNGLL,,,,,,V,N*7ABunch of other programs are able to get a handle on the device no problem. Ended up using https://www.npmjs.com/package/gps
Thanks for your help. Let me know if you want to debug the serial portion of this not reading correctly on Mac. Could be a cool expansion.
philrandal
commented
3 years ago One more thing you can try.
Test the version in Tom Dilatush's slightlyloony repo I forked gpsctl from.
You'll need to hard code the serial port as --port is not correctly handled in his code.
You'll also notice a comment in my fork that the timing code doesn't seem correct.
I did mess with that a bit when I was having intermittent similar problems to yours.
Good luck.
Phil
On Thu, 19 Aug 2021, 00:31 Brandon Ros, @.***> wrote:
Bunch of other programs are able to get a handle on the device no problem. Ended up using https://www.npmjs.com/package/gps
Thanks for your help. Let me know if you want to debug the serial portion of this not reading correctly on Mac. Could be a cool expansion.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/philrandal/gpsctl/issues/17#issuecomment-901496528, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADRPDO3IM2WRH4WFOTLIQLT5Q7GRANCNFSM5CIJS5ZQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .
https://www.amazon.com/gp/product/B07ZR8R17Q/