Skip to content

App doesn't work with ublox LEA M8P #7

Closed

Description

@kalon33

Using a USB GPS module based on a ublox LEA M8P, I got the error "too many connection problems". GPS is working properly with u-center on Windows 10.

Activity

  1. kalon33 commented on Aug 24, 2017

    @kalon33
    Author

    screenshot_2017-08-24-22-57-14
    screenshot_2017-08-24-22-56-33

  2. freshollie commented on Aug 25, 2017

    @freshollie
    Owner

    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?

  3. self-assigned this
    on Aug 25, 2017
  4. kalon33 commented on Aug 25, 2017

    @kalon33
    Author
  5. freshollie commented on Aug 25, 2017

    @freshollie
    Owner

    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.

  6. kalon33 commented on Aug 25, 2017

    @kalon33
    Author
  7. freshollie commented on Aug 25, 2017

    @freshollie
    Owner

    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.

  8. kalon33 commented on Aug 25, 2017

    @kalon33
    Author
  9. freshollie commented on Aug 25, 2017

    @freshollie
    Owner

    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?

  10. 19 remaining items

  11. freshollie commented on Aug 27, 2017

    @freshollie
    Owner

    Reading the log, it looks like the NMEA protocol being read back has not been implemented into the driver.

    Other android apps that are normally giving satellites list with internal GPS doesn't provide any info now.

    I don't understand what you mean this.

  12. freshollie commented on Aug 27, 2017

    @freshollie
    Owner

    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.

  13. kalon33 commented on Aug 27, 2017

    @kalon33
    Author

    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)

  14. freshollie commented on Aug 27, 2017

    @freshollie
    Owner

    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?! :))

  15. freshollie commented on Aug 27, 2017

    @freshollie
    Owner

    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.

  16. kalon33 commented on Aug 27, 2017

    @kalon33
    Author

    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 :)

  17. freshollie commented on Aug 27, 2017

    @freshollie
    Owner

    "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.

  18. added a commit that references this issue on Aug 27, 2017
    b37e0b0
  19. kalon33 commented on Aug 27, 2017

    @kalon33
    Author

    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).

  20. kalon33 commented on Aug 27, 2017

    @kalon33
    Author

    I don't have fix type info neither. Is that expected?

  21. kalon33 commented on Aug 27, 2017

    @kalon33
    Author

    neither VDOP/HDOP/PDOP...

  22. freshollie commented on Aug 27, 2017

    @freshollie
    Owner

    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.

  23. added 2 commits that reference this issue on Dec 4, 2017
    b47f6a5
    d0b3187
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions