You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, it supports NMEA, outputting various versions of it, currently set as 4.1 version. Do you want an NMEA output log?
No, I couldn't find other app on the playstore working with USB devices, when this one is properly detecting the device and naming it.
Ublox GPS chips works with three protocols: NMEA, proprietary UBX one, and another one (RTCM if I remember well). Here are protocol specs for mine, M8 series, which supports notably GPS, Glonass, Beidu and Galileo: https://www.u-blox.com/sites/default/files/products/documents/u-blox8-M8_ReceiverDescrProtSpec_(UBX-13003221)_Public.pdf
----- Mail original -----
De: "Oliver Bell" <notifications@github.com>
À: "freshollie/UsbGps4Droid" <UsbGps4Droid@noreply.github.com>
Cc: "Nicolas Derive" <kalon33@ubuntu.com>, "Author" <author@noreply.github.com>
Envoyé: Vendredi 25 Août 2017 10:33:43
Objet: Re: [freshollie/UsbGps4Droid] UsbGPS stopped: too many connection problems (#7)
I see this device supports NMEA. Is it possible I could get a log? I have only been testing this on http://usglobalsat.com/p-688-bu-353-s4.aspx .
Do any other apps in the playstore work with this device?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub , or mute the thread .
For now I'm going to concede that I will not be able to make this device work due to it having a vast array of protocols which need to be selected and I have no way of testing.
If you want this app to work I suggest buying the GPS using I linked.
Other options are you edit the driver to work with your device and then send me a pull request once completed.
I don't think they really need to be selected: by default, and if you don't have any manner to store parameters on the chip (flash or battery to keep RAM on when chip is not On), which is the majority of the devices I've seen, device outputs NMEA.
That said, is that complex work to edit the driver to work with my device? If it is, I may have a look at sending a similar device to you to give you some way to test (if you want that? and have time to work on this).
----- Mail original -----
De: "Oliver Bell" <notifications@github.com>
À: "freshollie/UsbGps4Droid" <UsbGps4Droid@noreply.github.com>
Cc: "Nicolas Derive" <kalon33@ubuntu.com>, "Author" <author@noreply.github.com>
Envoyé: Vendredi 25 Août 2017 14:03:44
Objet: Re: [freshollie/UsbGps4Droid] UsbGPS stopped: too many connection problems (#7)
For now I'm going to concede that I will not be able to make this device work due to it having a vast array of protocols which need to be selected and I have no way of testing.
If you want this app to work I suggest buying the GPS using I linked.
Other options are you edit the driver to work with your device and then send me a pull request once completed.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub , or mute the thread .
I mean yeah I could probably edit the driver if I had the device, but editing a driver for a device which I don't own would be nearly impossible.
Can you send me the android log file after you get the too many connection problems?
That error is raised when the device is not outputting any info at all. All this service does is literally read the data output directly strings, and it sounds like your device is sending none (Possibly waiting for the correct start signal)
I don't want you to send me anything expensive as I have no guarantee of this working. Though if you are still serious about sending me a device to work with then that can be arranged.
What kind of logfile do you need? adb logcat output? Anything else that would be useful for you? I will have a look to give you these over the weekend.
Apparently this device is detected as a USB serial one (creates a COM port on Windows, and equivalent /dev/tty*** on Ubuntu Linux).
If you think there's a way to get the device to work if you have it in hands, there's no problem for me to send mine or buy another one to send it to you. Supporting it would probably benefit to the community somehow so that's not wasted :)
----- Mail original -----
De: "Oliver Bell" <notifications@github.com>
À: "freshollie/UsbGps4Droid" <UsbGps4Droid@noreply.github.com>
Cc: "Nicolas Derive" <kalon33@ubuntu.com>, "Author" <author@noreply.github.com>
Envoyé: Vendredi 25 Août 2017 14:22:04
Objet: Re: [freshollie/UsbGps4Droid] UsbGPS stopped: too many connection problems (#7)
I mean yeah I could probably edit the driver if I had the device, but editing a driver for a device which I don't own would be nearly impossible.
Can you send me the android log file after you get the too many connection problems?
That error is raised when the device is not outputting any info at all. All this service does is literally read the data output directly strings, and it sounds like your device is sending none (Possibly waiting for the correct start signal)
I don't want you to send me anything expensive as I have no guarantee of this working. Though if you are still serious about sending me a device to work with then that can be arranged.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub , or mute the thread .
In some other android GPS apps (for internal GPS devices), you can get a list of current satellites used, and various info about GPS. For now I don't have them with the external one. Is that expected?
Now I have proper position fix, with altitude and number of satellites used in UsbGPS (the latter one not outside UsbGPS)
If you want an interpretation of the satellite positions, please make a separate issue. It will take much longer for me to produce, though it is a long term goal.
Is that expected that GPS time is a long integer, not usual time format? I'll create this issue, and, if you mind, another one to have some basic options like the ones available for sirf devices :)
so this is OK, both strings look like the same kind of thing. What's the difference between altitude (MSL) and altitude? I get both from my internal chip and only MSL one from external device (but not labeled as such).
Activity
kalon33 commentedon Aug 24, 2017
freshollie commentedon Aug 25, 2017
I see this device supports NMEA. Is it possible I could get a log? I have only been testing this on http://usglobalsat.com/p-688-bu-353-s4.aspx.
Do any other apps in the playstore work with this device?
kalon33 commentedon Aug 25, 2017
freshollie commentedon Aug 25, 2017
For now I'm going to concede that I will not be able to make this device work due to it having a vast array of protocols which need to be selected and I have no way of testing.
If you want this app to work I suggest buying the GPS using I linked.
Other options are you edit the driver to work with your device and then send me a pull request once completed.
kalon33 commentedon Aug 25, 2017
freshollie commentedon Aug 25, 2017
I mean yeah I could probably edit the driver if I had the device, but editing a driver for a device which I don't own would be nearly impossible.
Can you send me the android log file after you get the too many connection problems?
That error is raised when the device is not outputting any info at all. All this service does is literally read the data output directly strings, and it sounds like your device is sending none (Possibly waiting for the correct start signal)
I don't want you to send me anything expensive as I have no guarantee of this working. Though if you are still serious about sending me a device to work with then that can be arranged.
kalon33 commentedon Aug 25, 2017
freshollie commentedon Aug 25, 2017
Android has its own USB wrapper which doesn't require access to /dev/tty***. As this cannot be done without root. See https://developer.android.com/reference/android/hardware/usb/package-summary.html
The logcat would be perfect. I have several debug lines which I can read from the output and maybe understand the problem.
Can you
cat /dev/tty***on your computer with the devices plugged in and also send me the output?19 remaining items
freshollie commentedon Aug 27, 2017
Reading the log, it looks like the NMEA protocol being read back has not been implemented into the driver.
I don't understand what you mean this.
freshollie commentedon Aug 27, 2017
I've built an APK at the same link to work for added NMEA set, try that. Leave the GPS somewhere where it can get a fix. The log showed no GPS fix.
kalon33 commentedon Aug 27, 2017
In some other android GPS apps (for internal GPS devices), you can get a list of current satellites used, and various info about GPS. For now I don't have them with the external one. Is that expected?
Now I have proper position fix, with altitude and number of satellites used in UsbGPS (the latter one not outside UsbGPS)
freshollie commentedon Aug 27, 2017
Yes, that is expected due to the driver not interpreting the list of satellites from the device, only the number.
So the device is now working perfectly?! :))
freshollie commentedon Aug 27, 2017
If you want an interpretation of the satellite positions, please make a separate issue. It will take much longer for me to produce, though it is a long term goal.
kalon33 commentedon Aug 27, 2017
yep, that's now working :)
Is that expected that GPS time is a long integer, not usual time format? I'll create this issue, and, if you mind, another one to have some basic options like the ones available for sirf devices :)
freshollie commentedon Aug 27, 2017
"Gps Time" should be the same length as "Sys Time" as can be seen from the screenshots. That's great this is now working, I am surprised.
Fixes and closes #7, fixed endpoint finder, fixed NMEA parser to work…
kalon33 commentedon Aug 27, 2017
so this is OK, both strings look like the same kind of thing. What's the difference between altitude (MSL) and altitude? I get both from my internal chip and only MSL one from external device (but not labeled as such).
kalon33 commentedon Aug 27, 2017
I don't have fix type info neither. Is that expected?
kalon33 commentedon Aug 27, 2017
neither VDOP/HDOP/PDOP...
freshollie commentedon Aug 27, 2017
Do the altitude numbers differ? I just read what comes from the nmea and add it to a location object.
https://developer.android.com/reference/android/location/Location.html
Notice this object does not have the ability to set satellites or any of that info. I am pretty sure this is a limitation of android.
Fixes and closes #7, fixed endpoint finder, fixed NMEA parser to work…
Fixes and closes #7, fixed endpoint finder, fixed NMEA parser to work…