Don't blame you!!
Thanks Jim for the tip, I'll advise Alby that's what we want for the next batch.

To connect 5 Volt external inputs like coming from Wireless chargers or PoGo input pins you can use both red marked pins.The one beside the USB port has less other parts around and is easier to solder.
Lilygo T5 with onboard USB converter in B74 and BN versions.

Fine solder tip is advisable anyway.

Paco

Why not soldering + to Vbat and - to ground? much easier..

Select to expand quote

veton said..
Why not soldering + to Vbat and - to ground? much easier..

The problem is that most QI chargers deliver 5V output. A lipo has a max charging voltage of 4.2V. So, with a full lipo, the voltage will go to high and can destroy the lipo, or worse, the lipo can set fire. Luckily, the lipos that we use have a internal cutoff circuit, so the lipo is disconnected if the voltage go over 4.2V. Never the less, in my opinion is this not good practive. However, there are QI chargers with a output of 4.2V, these can be connected directly to Vbat.

thanks Jan, I wasn't aware the charge receivers came in 4.2V. I've ordered a few (same price) to test out. I will go that way in future as simple to solder to Vbat and don't need to extend the USB plug. The issue with the Qi charge receivers is they run quite hot, especially if not perfectly aligned so never charge more than an hr or so. The 4.2V versions should be more efficient and run cooler..in theory..will see if that is the case.

Since I found that option in the build manual, I'm using it. (Vbat+Gnd) I find it much easier if you don't have really good skills at soldering, you can ruin the board, as it happened to me..
I'm using these little coils in the marked pins, they deliver no more than 4,1 V . I hope that is enough protection in addition to the Lipo protection. The other pins give 5V.

es.aliexpress.com/item/1005008622419534.html?spm=a2g0o.order_list.order_list_main.95.3a19194dmyW638&gatewayAdapt=glo2esp

Hello!

Just about to purchase the parts from AliExpress, but I have been having a look at the Wireless communication systems, Meshtastic and Meshcore.

It looks like these are using an Arduino board from to receive and send the signal. How difficult would it be to create the GPS tracker with one of these boards? So using the LILYGO T3 S3 E-Paper ESP32-S3 ? Would it affect the GPS logging and would it still be allowed on the speedsites?

Just throwing it out there to be honest, think emergency message for help etc. Rather texting my wife I coming home, get the beer chilled!

Cheers


Rob

Select to expand quote

rp6conrad said..

veton said..
Why not soldering + to Vbat and - to ground? much easier..

The problem is that most QI chargers deliver 5V output. A lipo has a max charging voltage of 4.2V. So, with a full lipo, the voltage will go to high and can destroy the lipo, or worse, the lipo can set fire. Luckily, the lipos that we use have a internal cutoff circuit, so the lipo is disconnected if the voltage go over 4.2V. Never the less, in my opinion is this not good practive. However, there are QI chargers with a output of 4.2V, these can be connected directly to Vbat.

Like Jan said some Qi receivers only give 5 volt as output.

The Qi board Veton showed however is a 2 in 1 board.

VOUT gives 5 volt and needs to go to the red marked spots which go to the Lilygo T5 build in charger IC TP4054.

BAT is an output which is a Lipo charge output and provide max 4.2 volt and regulate and controls the charging process.
The led onboard provide the status.
You can see this as a bonus output if your device does not have a charge circuit included.

Paco

Select to expand quote

merlincat said..
Hello!

Just about to purchase the parts from AliExpress, but I have been having a look at the Wireless communication systems, Meshtastic and Meshcore.

It looks like these are using an Arduino board from to receive and send the signal. How difficult would it be to create the GPS tracker with one of these boards? So using the LILYGO T3 S3 E-Paper ESP32-S3 ? Would it affect the GPS logging and would it still be allowed on the speedsites?

Just throwing it out there to be honest, think emergency message for help etc. Rather texting my wife I coming home, get the beer chilled!

Cheers


Rob

Meshtastic / Meshcore are Wireless meshsystems which rely on nearby nodes to communicate. Distance node to node is limited, and more in the range of 1000 meter. As these devices are relatif rare now, I do not believe that this is a reliable system for emergency calls. A ESP32 S3 has not a build in Mesh radio, so a extra module should be needed. This can be done without affecting GPS functions.
Use of the ESP32 S3 is certainly possible, but you need to use ESP32 Library 2.x (1.x has no S3 support) and some changes in the SW. Also a TFT display needs changes in the code.

Select to expand quote

PacoRaapNL said..
To connect 5 Volt external inputs like coming from Wireless chargers or PoGo input pins you can use both red marked pins.The one beside the USB port has less other parts around and is easier to solder.
Lilygo T5 with onboard USB converter in B74 and BN versions.

Fine solder tip is advisable anyway.

Paco

I have to correct an error!
The spots that are connected to put external 5 volts on are not the red squares but the green squares.
Sorry for this mistake.

For those who look at the circuit as being a "WHAT IS THIS"?
I connected the loose ends for clarification.

VBUS is connected to the input from the USB connector so 5V comes in from there.
D7 and D8 are diodes with a fuse function.
They make sure that both give their voltage onto the switch.
They also make sure the USB 5V (VBUS) is not directly connected to the battery VBAT and vice versa.
Voltage goes through the blue arrow direction not against it.

Work in progress.
New 2026 version in the color lime green
The new formula Polymaker PETG used.


Easier way to enclose the main base with the acrylic tape and 0.3 mm PET or PVC sheet.
The black part is a sacrifice sheet so the acrylic tape does not change in form as it is very flexible and sticky when you need to remove the red side cover layer.
Cut along the outer edge of the main base and place the top cover.
Secure it with the 3 mm carbon rods.






Paco

Select to expand quote

PacoRaapNL said..
For those who look at the circuit as being a "WHAT IS THIS"?
I connected the loose ends for clarification.

VBUS is connected to the input from the USB connector so 5V comes in from there.
D7 and D8 are diodes with a fuse function.
They make sure that both give their voltage onto the switch.
They also make sure the USB 5V (VBUS) is not directly connected to the battery VBAT and vice versa.
Voltage goes through the blue arrow direction not against it.

Yes thats the theory, AND there is a (extra) fuse between VBAT and pin 2 (VCC)off the PH-2-WO connector (where the battery plugs in). That fuse will fail (changes is 90%) so thats why we advice to solder the battery to the VBAT pin.
But if you solder the battery to the 5V pin (Beside the VBAT pin) the battery cant charge properly ....... but it does?? Not recommended but if VBAT is not reacheble, 5V can be used as a work around

I have a problem with a BE220, It's not talking to the esp board.
At boot it says it's autodetecting the GPS, but after trying to configure it, comes back and says, "no gps frames for more than 10s"
Also for some strange reason , the config file isn't updating.
It says the changes have been saved OK but the config files hasn't changed from the old BN settings.

If I plug the old BN chip in it works OK.

I have a feeling if I can update the config file to the M10 settings it should work.

Am I doing something stupid here?????

You checked rx and tx are not swapped? Check datasheet BE220 and BN220 used.

The settings for the type of GPS used is not in the config.txt anymore, but in EEPROM. With a fresh ESP32, the GPS type in EEPROM is set as "AUTODETECT at boot", so with the first boot out of Wifi reach, first the baudrate is detected, and then the type of GPS (M8, M9 or M10). If the gps is recognized, the EEPROM is written with the detected baudrate and type. The config.txt is also written, as info for the config in the webserver. If you connect a different gps now, next procedure is necessary :
In the config (webserver configuration), set the type as "AUTODETECT", and submit.
Boot again, and go outside. Now, a new autodetect should be started.
Let me know your findings !
Greetings, Jan.

Select to expand quote

PacoRaapNL said..
You checked rx and tx are not swapped? Check datasheet BE220 and BN220 used.

Thanks Paco, I find the instructions on TX, RX a bit ambiguous. I wasn't sure if the esp pin marked "GPS TX"
Meant the TX pin on the esp or the TX pin from the GPS, so I did swap them around, didn't work either way.
But as posted, it works with an older BN, so I have it correct now.
As you say the data sheet is worth checking, in the process of trying to solve this I discovered the min voltage for the BE is 3.6v not the 3.25 I was getting from the parallel outputs. so I've switched to the 5v rail instead, made no difference of course.

Select to expand quote

rp6conrad said..
The settings for the type of GPS used is not in the config.txt anymore, but in EEPROM. With a fresh ESP32, the GPS type in EEPROM is set as "AUTODETECT at boot", so with the first boot out of Wifi reach, first the baudrate is detected, and then the type of GPS (M8, M9 or M10). If the gps is recognized, the EEPROM is written with the detected baudrate and type. The config.txt is also written, as info for the config in the webserver. If you connect a different gps now, next procedure is necessary :
In the config (webserver configuration), set the type as "AUTODETECT", and submit.
Boot again, and go outside. Now, a new autodetect should be started.
Let me know your findings !
Greetings, Jan.

Thanks Jan,
I think I've probably covered that procedure in my many attempts to get it working, so I don't hold out great hope, but I'll follow what you say exactly and get back here.

No luck, after boot it says auto detect GPS, then initializing GPS, then no frames in 10s.
I'm about to try the BE in another gps, don't ask me why it just seems like something I can do.

That was interesting, it's using version 5.76 and it's slightly different to version 5.87.
5.76, after GPS auto detect, has an exclamation mark after GPS and a question mark after ublox.
So is the BE220 a ublox M10???? if not I've bought the wrong thing!!!!!
EDIT.
Just checked, it's supposed to have the M10050 ublox M10 chip.
Is this too new for the firmware?

Just tried an older M10, auto detect found it OK and worked well for about 10m then stopped recording, no idea why at the moment.

Could it be possible that the new BE220 has a default baudrate of 115200 bd ? This bdrate was not supported in SW 5.87. Only SW5.91 and higher support baudrate 115 k !!
In the changelog MD :
###Changes SW5.91
* Added 115200 Baud for Beitian Bx122
* Bugfix for M8@38400 bd
* Added estimated Logspace left (webserver+display). Calculates logtime with actual settings sample-rate, file selection and free space.
* GPIO 19 Go to sleep pin PULLDOWN.
* GPIO 21 hold HIGH SIDE SWITCH
* GPIO2 pulldown in deepsleep, was still floating
* Added statscreen B , last run, best run, slowest run and average

Can you connect the ESP over USB to the Arduino IDE ? Then, check the "Serial monitor" (baudrate 115200) to see what is happening. When autodetect, you should see something as this :

Actual CPU freq before Wifi.begin(): 240
T5 MAC adress: search SSID1
ESP32 disconnected to WIFI
.ESP32 disconnected to WIFI
..ESP32 disconnected to WIFI
.ESP32 disconnected to WIFI
.ESP32 disconnected to WIFI
.ESP32 disconnected to WIFI
.ESP32 disconnected to WIFI
..ESP32 disconnected to WIFI
.search SSID2
.ESP32 Connected to SSID Station mode
ESP32 Soft AP switched off
.........No Wifi connection !
CPU freq 240 ?= 240
CPU freq ?= 80
XTAL freq ?= 40
Serial2 Txd is on pin: 33
Serial2 Rxd is on pin: 32
?O??kZb^??( g?CNbcc???C???F?ba???C???CHO????" BJ B?jH??CW
? BJ"F?H??C?{uHO????DHc??C?!? BJB??'?TJJJ??????JBJKJJH~J??????????m
???????T?JJJJKjJKjH~J?????????VuC?VuC?VuC?VuC??gJ)?
Check UBX_MON_VER @9600bd

Check UBX_MON_VER @38400bd
SW Ublox=ROM SPG 5.10 (7b202e)
HW Ublox=000A0000
Ublox M10 @38400bd

In the SW 5.91, there is also a check for 115200 bd if no correct answer on 9600 or 38400 !
Greetings, Jan.

Thanks Jan, that would make sense, I'll have a play tomorrow.
However I've found another problem with the older BE that works fine on one SD card, but on two others it only records 24kb then stops recording. The one that works doesn't want to mount on my linux machine. Is it a formatting problem do you think?
The cards that don't work on this esp work fine on others with the same SW version.

This old brain couldn't remember how to do the Arduino thing.
And you are right on the money Jan, I just update to 5.91. that's done the trick autodetected the M10@ 115.2kbd
I'll give it a run tomorrow and see how it performs.

I found the 24kb limit problem, there was a small solder blob across a couple of terminals, somewhere around 32, v3 and 34.

So now it's working great, thanks guys.

HELP!
I'm having trouble finding the .sbp files from my latest sessions. I've been linking to the unit with my phone and when connected I only find the following files:
A .txt file and a .gpy file for the sessions (although there was no .gpy file for yesterday).
When I've done this up until now there was an .sbp file to upload to KA72.
I've checked my other unit and it has .sbp files. Unfortunately I went for a quick sail today and only put one one unit on the boom. The loss of the data from today is no great loss, and yesterday I had my other unit for data, but I want to sort out what's wrong before the next windy day
Thanks
Thanks

Select to expand quote

TerryF said..
HELP!
I'm having trouble finding the .sbp files from my latest sessions. I've been linking to the unit with my phone and when connected I only find the following files:
A .txt file and a .gpy file for the sessions (although there was no .gpy file for yesterday).
When I've done this up until now there was an .sbp file to upload to KA72.
I've checked my other unit and it has .sbp files. Unfortunately I went for a quick sail today and only put one one unit on the boom. The loss of the data from today is no great loss, and yesterday I had my other unit for data, but I want to sort out what's wrong before the next windy day
Thanks
Thanks

Weird, all those files show 0MB, have you tried downloading the GPY file to see what's in it?
If it has data in it that should be fine, it's all I use.

Have a look at the configuration button, you can select different formats to be on or off, so if you really need the data in .sbp you can turn that on

Thanks for the quick reply, and the suggestions.
I tried using KA72 to upload the gpy file but it didn't work. I was wearing my Garmin FR255 today so I have the gpx file from that (which I've used to upload on KA72) so I did have data for today. I will check the configuration

That was the right idea Decrepit, the configuration was set to gpy ON and sbp OFF. I don't know why it changed, but I've switched it back. Thanks again

Despite the configuration changes I still didn't get an sbp file after today's sail. And no gpy file either. Just the txt file. See photo
I sailed with my second unit so have data to upload, but hoping to work out what has happened to this unit and why I don't have data.
Any other suggestions/ideas appreciated

I guess that there is something wrong with the SD-card. At boot, first the SD interface is checked, if no SD is found, the internal flash memory is used as storage. But the space is limited, something like 1.2 MB (as the correct Partition table was used by the first flashing). It seems now that the local storage is completely filled, and then no log files will be saved.
You can see in the boot screen if your local memory (max 1.2 MB), or SD card memory is used : Local memory : x kB, or SD : x MB.
Let me know your findings.