TTGO LoRa32 V1.0 #27
Comments
|
Thanks. Do you know the exact version of your TTGO LoRa32? I don't have any of the TTGO LoRa32 v1.x boards and therefore have to rely on LilyGo's documentation. The TTGO LoRa32 v1.3 schematic diagram does not show a LED nor seems the display's reset connected to a GPIO pin. If you have an older version I could add an additional board definition to LMIC-node for older (pre-v1.3) TTGO LoRa 32 v1.x boards and add the display reset and LED pin definitions. |
|
Thanks for getting back to me. It doesn’t sound like I have a v1.3 version. The blue LED is on. For some reason it works the opposite of the transmit flag. I tried some different code in LMIC-node to get it to work properly but I wasn’t successful. Weird.
Mine is 2 or 3 years old. The display is pooping out as you can see. No indication of version. Here is the pin-out diagram that matches it.
… On Jan 31, 2022, at 6:53 AM, Leonel Lopes Parente ***@***.***> wrote:
Thanks.
Do you know the exact version of your TTGO LoRa32?
Can you provide a picture of the top and bottom sides?
I don't have any of the TTGO LoRa32 v1.x boards myself and therefore have to rely on LilyGo's documentation.
Unfortunately their versioning is unclear (sucks) and documentation is poor and unreliable.
The TTGO LoRa32 v1.3 schematic diagram does not show a LED nor seems the display's reset to be connected to a GPIO pin.
Is it possible that you have an older version than v1.3? (With the v1.3 board the vesion in printed on PCB bottom side).
If you have an older version I could add an additional board definition to LMIC-node for older (pre-v1.3) TTGO LoRa 32 v1.x boards and add the proper display reset and LED pin definitions.
—
Reply to this email directly, view it on GitHub <#27 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF4WTTASMSILTDD7HUZBJNLUYZZ3FANCNFSM5M3NQ7ZA>.
You are receiving this because you authored the thread.
|
There's nothing to see here. It looks like you forgot to attach the images. |
|
They were attached to the return email.
Fatfingered from my iPhone
… On Feb 14, 2022, at 11:31 AM, Leonel Lopes Parente ***@***.***> wrote:
The display is pooping out as you can see. No indication of version. Here is the pin-out diagram that matches it.
There's nothing to see. It looks like you forgot to attach the images.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
|
|
Maybe too big for GitHub.
Fatfingered from my iPhone
… On Feb 14, 2022, at 11:31 AM, Leonel Lopes Parente ***@***.***> wrote:
The display is pooping out as you can see. No indication of version. Here is the pin-out diagram that matches it.
There's nothing to see. It looks like you forgot to attach the images.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
|
|
You can add them in the regular way via the GitHub site (or possibly via the GitHub app). |
|
|
|
Thanks for adding the pictures. Your board looks like the predecessor of TTGO LoRa32 v1.3 as shown (called V1) here: Big ESP32 topic Let's call that version v1.0, because version information about pre-v1.3 boards is not available from LilyGO.
Can you test if the LED on GPIO2 on your board is active-low or active-high? The following library and example can help with that: EasyLed active-level tester In the example code, in the lines EasyLed led(LED_BUILTIN, EasyLed::ActiveLevel::Low, EasyLed::State::Off); //Use this for an active-low LED
// EasyLed led(LED_BUILTIN, EasyLed::ActiveLevel::High, EasyLed::State::Off); //Use this for an active-high LEDreplace |
|
I’m traveling and won’t be able to do that for a while. I tried it both ways in your code previously and it still worked backward. Didn’t troubleshoot further.
…Sent from my iPad
On Feb 24, 2022, at 7:41 AM, Leonel Lopes Parente ***@***.***> wrote:
Thanks for adding the pictures.
Your board looks like the predecessor of TTGO LoRa32 v1.3 as shown here: Big ESP32 topic
Let's call that version v1.0, because version information about pre-v1.3 boards is not available from LilyGO.
I can add a separate board definition for v1.0 version (in addition to the v1.3 version) to LMIC-node.
It doesn’t sound like I have a v1.3 version. The blue LED is on. For some reason it works the opposite of the transmit flag.
Can you test if the LED on GPIO2 on your board is active-low or active-high?
The following library and example can help with that: EasyLed active-level tester
In
EasyLed led(LED_BUILTIN, EasyLed::ActiveLevel::Low, EasyLed::State::Off); //Use this for an active-low LED
// EasyLed led(LED_BUILTIN, EasyLed::ActiveLevel::High, EasyLed::State::Off); //Use this for an active-high LED
replace LED_BUILTIN with 2.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
|
|
I would appreciate if you can check it when possible again. |
|
I have this board. The LED is active-high. The main problem is getting the display to work. V frustrating - I'd appreciate any pointers you have - prepared to get into it but stumped at the moment... |
|
Rereading the comments above, con confirm that adding RST pin 16 allows display to operate. Will clone and push tomorrow. |
|
@JohnMacrae Thanks for your feedback! I will add a separate board definition for TTGO LoRa 32 V1.0 later when I have time. |
My board does have an onboard blue led at pin 2.
I had to add rst (pin 16) to the display call to get it to work.
Nice app overall.
K
The text was updated successfully, but these errors were encountered: