Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: HT1818Z3G5L GPS support #3616

Closed
hpsaturn opened this issue Apr 14, 2024 · 1 comment
Closed

[Feature Request]: HT1818Z3G5L GPS support #3616

hpsaturn opened this issue Apr 14, 2024 · 1 comment
Labels
enhancement New feature or request low-priority Possibly something we'll consider in the future but doesn't serve the core use-cases or problematic

Comments

@hpsaturn
Copy link

hpsaturn commented Apr 14, 2024

Platform

ESP32 T-Deck firmware (beta and alpha versions)

Overview

I have some radios ready with Meshtastic, and I was testing the T-Deck hardware with this GPS module HT1818Z3G5L, but I notice that the GPS is detected but the firmware can not retrieve the info maybe. I have using this module in other development and works fine with the TinyGPS library for example.

I'm relative new around the Meshtastic development, I did some PR in the Android app of it, and I know some things around the ESP32 development. What is the way or the first steps to try to contribute with support this module? Thanks in advance.

Serial output

WARN  | ??:??:?? 762 [GPS] 3 new GPS checksum failures, for a total of 17948.
WARN  | ??:??:?? 762 [GPS] 7 new GPS checksum failures, for a total of 17955.
WARN  | ??:??:?? 762 [GPS] 1 new GPS checksum failures, for a total of 17956.

Extra context

Here a video showing the issue:
https://github.com/meshtastic/firmware/assets/423856/89fe4116-e3f4-47ae-8ec0-b3935f05c1e1

@hpsaturn hpsaturn added the enhancement New feature or request label Apr 14, 2024
@GPSFan
Copy link
Contributor

GPSFan commented Apr 15, 2024

The AT6558 chipset is a Casic protocol chip and is not currently supported, but has a PR to add support. See PR #3610.

@thebentern thebentern added the low-priority Possibly something we'll consider in the future but doesn't serve the core use-cases or problematic label Apr 19, 2024
@thebentern thebentern closed this as not planned Won't fix, can't repro, duplicate, stale Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request low-priority Possibly something we'll consider in the future but doesn't serve the core use-cases or problematic
Projects
None yet
Development

No branches or pull requests

3 participants