Skip to content

Conversation

@hereway
Copy link

@hereway hereway commented Nov 27, 2025

Hello everyone, I have updated the GPS and rotary encoder configuration for the Heltec-T190, and also added GPS adaptation support for the Heltec-E290.

Update Summary:

  • Optimized GPS module configuration parameters for Heltec-T190
  • Improved the rotary encoder driver for Heltec-T190
  • Added complete GPS functionality support for Heltec-E290
  • Ensured GPS data parsing stability for both devices

Testing Status:

  • Successfully tested GPS positioning functionality on actual Heltec-T190 hardware

  • Verified operation response of the rotary encoder on T190

  • Completed basic GPS module functionality testing for E290

  • [√] I have tested that my proposed changes behave as described.

  • [√] I have tested that my proposed changes do not cause any obvious regressions on the following devices:

    • [√] Heltec (Lora32) V3
    • LilyGo T-Deck
    • LilyGo T-Beam
    • RAK WisBlock 4631
    • Seeed Studio T-1000E tracker card

@CLAassistant
Copy link

CLAassistant commented Nov 27, 2025

CLA assistant check
All committers have signed the CLA.

moduleConfig.canned_message.inputbroker_pin_a = ROTARY_A;
moduleConfig.canned_message.inputbroker_pin_b = ROTARY_B;
moduleConfig.canned_message.inputbroker_pin_press = ROTARY_PRESS;
moduleConfig.canned_message.inputbroker_event_cw = meshtastic_ModuleConfig_CannedMessageConfig_InputEventChar(28);
Copy link
Collaborator

@mverch67 mverch67 Nov 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if it's a good idea to hard-code these pin values into the firmware. These input pins are configurable for a reason. If they are hard-coded they cannot be used for sth different (e.g. detection sensor).
Instead these values should be configured via app or CLI.

* GPS pins
*/

#define GPS_L76K
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Heltec vision master doesn't have a built-in GPS so the default should always be not present.
#define GPS_DEFAULT_NOT_PRESENT 1

/*
* GPS pins
*/
#define GPS_L76K
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Heltec vision master doesn't have a built-in GPS so the default should always be not present.
#define GPS_DEFAULT_NOT_PRESENT 1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants