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
I'm trying to adapt this sketch for a custom ESP32 based board with an external GPS and a different pinmap. After a while I realized that GPS_RX and GPS_TX (gps.h) are defined in a pretty unusual way here.
The pin GPS_RX means the TX pin of the ESP here (wired to RX of the GPS). GPS_TX is the RX pin of the ESP (wired to TX of the GPS).
I understand that this won't really matter if you just use the T-Beam, but for others who are planning to reuse the code for other boards, this notice might be helpful since it is not the "normal" way most people would handle the terms RX and TX.
The text was updated successfully, but these errors were encountered:
jayAitch256
added a commit
to transportkollektiv/feuchtraumabzweigdose-testing
that referenced
this issue
Apr 26, 2021
I'm trying to adapt this sketch for a custom ESP32 based board with an external GPS and a different pinmap. After a while I realized that
GPS_RX
andGPS_TX
(gps.h) are defined in a pretty unusual way here.The pin
GPS_RX
means the TX pin of the ESP here (wired to RX of the GPS).GPS_TX
is the RX pin of the ESP (wired to TX of the GPS).I understand that this won't really matter if you just use the T-Beam, but for others who are planning to reuse the code for other boards, this notice might be helpful since it is not the "normal" way most people would handle the terms RX and TX.
The text was updated successfully, but these errors were encountered: