I hope to get my TTGO LoRa32 V2.1 T3_1.5 or _1.6 today. I have a lot of stipid questions that might answer themself when I start to play with the board. If the board is delivered with the Paxcounter program preinstaled, how do I get the EUI number so I can register the device to TTN?
I contacted LilyGO and got the right link to the actual code: https://github.com/cyberman54/ESP32-Paxcounter
I played with the code and compiled it again and all is fine. The display isnât flipped anymore. You have to set #define DISPLAY_FLIP 0 in ttgov21.h to got a non flipped display.
- In your TTN account, create an application and link to a device
- Download and install Atom and PlatformIO
- Download the source code from the link in my previous post
- Open Project in PlatformIO
- Create loraconf.h from loraconf.sample.h and copy / paste your DEVEUI, APPEUI and APPKEY from your device in your TTN account
- Choose your board in platformio.ini
- Compile
- Upload to you board
- Lean back and wait for your device to join
(Hope I didnât forgot a step)
1 Like
I did not get my TTGO today 
so I got one more day to think. It was the DEVEUI I wonder how to get. I see TTN got a sketch -> Deviceinfo that will give it.
The paxcounter software (if installed on the module) shows the DEVEUI on the OLED-display while the module is starting. Take a picture with your smartphone, look at it, and enter the DEVEUI in TTN console.
2 Likes
I usually generate the DevEUI in the TTN console and use thatâŚ
You can do so, you need to copy/paste the generated DEVEUI in file /src/loraconf.h and then build the code.
It is better to generate a DEVEUI from a MAC address (if the device has one) than let the console create a random DEVEUI (but both will work).
Agree.
Most of the devices I have canât generate an Id which is guaranteed to be unique. So between a non unique ´hardware´ Id and the TTN one, I take the easy route.
But you are right, when the device has a unique MAC it is better to use it âI am just lazy.
The ESP32 has one. 
But indeed, letting the Console generate one is easier (unless you want to be able to uniquely identify your nodes).
1 Like
I installed the paxcounter on two devices: ttgov21 and ttgov2. On ttgov21 all is well, on ttgov2 the node is joining and had success, âjoinedâ is shown in the OLED and I see the joining in TTN console. The first package with zero payload seems to appear in TTN console but on OLED of the node the package is queued. After a while OLED displays the message âLora busyâ and nothing else happens. Whatâs going wrong? I tried on 2 different ttgov2 boards with the same result.
Hello everyone,
I would like to get a T-Beam module but Iâd like to know if low power works on it (gps as well).
Any hardware issues with the latest version?
on ttgov2 you need to wire DIO1 pin of LoRa module by soldering a piece of wire on the board. Read the hal file ttgov2.h !
T-Beam is not a real low power device, missing features to switch off peripherals.
Just to be sure: [wrong wiring deleted]
Right?
No. You must wire âLora_IRQâ (26) with âGPIO33â (33).
See ttgov2.h:
{1} Must be manually wired!
DIO1 is wired to a separate pin but is not wired on-board to pin/GPIO33.
Explicitly wire board pin labeled DIO1 to pin 33 (see TTGO V2.0 pinout).
Only this connection and not more?
[wrong wiring deleted]
yes, for paxcounter app only this 1 wire is needed.
I connected the two pins but the problem is still the same: Lora busy
I canât help you further then. If it works with your TTGOv2.1 on the same LoRa Gateway it probably somehow will be caused by your TTGOv2.
Double check the wiring.
LoRa Busy usually means that the LMIC stack does not see TX COMPLETE events, or the duty cycle is reached. If the problem occurs after startup, it canât be a duty cycle limit, so i assume that your board does not feed LMIC with TX COMPLETE events. This is the function of the DIO1 pin, labelled âLora IRQâ on the pcb.
I have a TTGOv2 board up and running with paxcounter, after i placed the wire it worked. But maybe this pcb is not identical with yourâs, there are different chinese versions on the market it seemsâŚ