TTGO ESP32-Paxcounter LoRa32 V2.1 1.6.1

Hi, I just got my TTGO ESP32 LoRa32 V2.1 1.6.1 with Paxcounter preinstalled. Seems to work flawlessly.
I now wanted to replace Paxcounter with Meshtastic and have a few questions - as I am afraid of frying the hardware.

First of all I compared the pinout with the one from V1.6 - they have the same labels so this should be fine for external hardware.

Does anyone know if the interal pin connection is the same for the V1.6 and V1.6.1?
From what I understand it then should be firmware-tlora-v2-1-1.6-1.x.x.bin as stated on the hardware support page?
If pin connections should be different - could I destroy the module with flashing the wrong version?

Also I read in an article on TheThingsNetwork that with the V1.6 there are some versions which tend to “explode a connected battery”
The article should contain some pics to find out if the board is affected but unfortunately they are no longer there.

I added a screenshots of my V1.6.1 board - if anyone could tell me if the problem seems to be fixed there I would appreciate that. (I have five pictures ready but am only allowed to post one - I’ll try to add the others in seperate postings).

The pictures also may help @eriktheV-king for his sheet at replace with https):// (only two links allowed for me, as I’m a new user, so text only reference) to serve as a new hardware. My hardware looks different from the V1.6 which is shown on the Lilygo product page (see link above).

So any help would be appreciated.

Best Gulpman

Here’s the back of the board:

This is a close-up of the electronic section for the power management:

V1.6.1 seems to be pin compatible for external pins as can be seen from this close-up:

That’s annoying that the photos have disappeared form the TTN website! That being said, I suspect yours should be ok given that yours is model 1.6.1, and the offending model was 1.6, certainly the power section looks rather different from my 1.6 model anyway.

I have the same board version and it seems to be ok as what comes to charging a battery. It also runs meshtastic

Use the Meshtastic Flasher GUI. I have the same board, works fine. After the initial flashing that overwrites the the PAXcounter firmware, remember to check the update only box under advanced options when doing future updates. When attaching a battery, double check the polarity matches the board.

Sorry for the late reply, but when Murphey can strike, he strikes… My Laptop died and I had to order a new one. :face_with_diagonal_mouth:
Saying that - I now used the flasher GUI and it flashed Meshtastic flawlessly. Good job - very user-friendly! :+1:
Thank you guys for your help! Really appreciate it.

Anyone knows how to navigate screens on this board (v1.6) with meshtastic 1.2.64?
There is only a reset botton and a power.

You can connect external switch between IO12 and GND

Nice. It works :slight_smile: Thanks

I also have a couple TGO ESP32 LoRa32 V2.1 1.6.1. I have been able to flash them through the python application and the meahtastic app recognizes them on the android, however all my options on the app are greyed out. I cannot create a channel or anything. It says connected to radio (unknown) and the only option I have is to enter name and location. This is the same on both radios.

Same here.

It seems like the Beta device firmware is out of sync with the GUI flasher and the Android App that’s currently available in the store.

Since the Android app is still 1.2 I can understand that but I don’t understand how the flasher is out of sync with it.

I set the primary channel name using the CLI with the command…

meshtastic --ch-set name “insert channel name here” --ch-index 0

I then set a psk key for the primary channel with the command…

meshtastic --ch-set psk <insert 66 character hex key here> --ch-index 0

I create a psk key using an online random hex key generator. The key is then used for all the nodes on my mesh.

This works well for setting up multiple units and screenless router/relay nodes that have no need to be paired with a device. No need to scan QR codes.