Select to expand quote

Actimel87 said..
It is set as M10 @ 38400.
I just downgraded from FW5.81B74 to FW 5.76BN. This version 5.76BNworks in terms of Display presentation really well.

I will test 5.82BN.

You have to use the SW version with the correct index for your screen. If you have a 213BN screen, you must use the 5.xxBN.bin SW. If you have a 213B74 screen, you have to use the 5.xxB74.bin
With the wrong bin file, you will have issues with the display.
Greetings, Jan.

Nice issue, I have 2 the same devices (m10, 213bn led, 1500 lipo).
Fully charged with default configuration, displays nr 1 max 75% battery and nr2 100% batterylevel. I did a durancetest. Nr1 switched off after 14,33 hour (yes the version which starts at 75%) and nr2 after 12,8 hour.

so nr 1 battery has more capacity but when you look at the display you would think outwise.

If i change the "cal_bat", is this pure for the display or will it change the working to?

Select to expand quote

BigBoss said..
If i change the "cal_bat", is this pure for the display or will it change the working to?

Yes, it will change the working time ! When the measured voltage drops below 3.1 V, the device will shut off. However, the voltage measurement is influenced by the calibration factor.
One should adjust the calibration factor, so that fully loaded the display says 99% (because >100% is cuttoff to 100% in the SW).
When you have a (reliable) multimeter, you can measure the voltage between BAT and GND. 4.2 Volt is 100% charge.
Greetings, Jan.

Select to expand quote

rp6conrad said..

BigBoss said..
If i change the "cal_bat", is this pure for the display or will it change the working to?

Yes, it will change the working time ! When the measured voltage drops below 3.1 V, the device will shut off. However, the voltage measurement is influenced by the calibration factor.
One should adjust the calibration factor, so that fully loaded the display says 99% (because >100% is cuttoff to 100% in the SW).
When you have a (reliable) multimeter, you can measure the voltage between BAT and GND. 4.2 Volt is 100% charge.
Greetings, Jan.

Thanks Jan.
I didn't measure the vbat (will do that). those 2 devices has the 213bn with leds. When charging, the color of the main led is blue and there is a charging led in red. If the battery is fully loaded the red led goes off. The main one remain blue. When you discharge the charger the main led turns green.
mostly with a fully charge battery the display say 100% (4.2 V) after the test i fully charged both devices again, same result. Nr 1 max out at 75% nr 2 at 100%

but tonight i will measure the voltage.

It becomes more strange.
Vbat is 4 volt. nr1 says 57%nr2 says 88%.
both exactly 3.99 volt on the voltmeter

The webserver give different results (not corresponding to the real voltage)

If you change cal_bat, do the Voltages in the webserver change ? What voltage are you measuring during charging ?Charging is handled by the charging IC on the board, this prevents overcharging and limits the charging current (no SW involved). A second safety is the chip on lipo, also limit the max voltage and current + switch off @ low voltage.
After all, the ADC from the ESP32 is not the top, don't expect exact measurements...

Select to expand quote

rp6conrad said..
If you change cal_bat, do the Voltages in the webserver change ? What voltage are you measuring during charging ?Charging is handled by the charging IC on the board, this prevents overcharging and limits the charging current (no SW involved). A second safety is the chip on lipo, also limit the max voltage and current + switch off @ low voltage.
After all, the ADC from the ESP32 is not the top, don't expect exact measurements...

Yes the voltages changes.
now i have set cal_bat of nr1 to 1.83 and nr2 to 1.73. I have measure the vbat with the multimeter so that the voltage given by the webserver is equal with the multimeter. 4.18 volt = 100 % now on both devices.
3.80 Volt = 75%

charging voltage on the multimeter is 4.17 a 4.18 volt now

Jan, could beside the percentage also the voltage be shown in the screens when there is room at the bottom?I run both values also in my FPV planes and drones onscreen display. For some reason mixing those values in my brain gives a better understanding of the battery state than one of them seperate.

Paco

Finally I have done some firmware modifications to support the larger screen of 2.66inch (bn266). Workes on it during the evenings and weekends in the past 6 weeks. As the resolution changed it was a big rewrite of the screens, also for the standard 2.13. I tried to keep it similar with some small improvements here and there. Slightly more stat info on pages 2-5, distance field includes battery info. 2 new logo's OneHundred an NorthSails. Battery is now configurable in the config for either voltage or percentage (from recent discussions). As I started with the firmware 5.81 it will require quite a bit of merging by Jan (sorry Jan). I'm quite sure it might need a bit of polishing.
With the larger screen I was able to stack a 4000mah lipo inside that was able to log 47.5hrs on a single charge.
I do like the bigger screen as readibility is greatly improved.
I always wanted a track bitmap plot but that requires more puzzling on my side (started 1.tyrs ago). On the geeky Alpha StarWars targeting graphic I haven't even started.
If people have specific screen requests please indicate them on github.

Select to expand quote

Freezer said..
Finally I have done some firmware modifications to support the larger screen of 2.66inch (bn266). Workes on it during the evenings and weekends in the past 6 weeks. As the resolution changed it was a big rewrite of the screens, also for the standard 2.13. I tried to keep it similar with some small improvements here and there. Slightly more stat info on pages 2-5, distance field includes battery info. 2 new logo's OneHundred an NorthSails. Battery is now configurable in the config for either voltage or percentage (from recent discussions). As I started with the firmware 5.81 it will require quite a bit of merging by Jan (sorry Jan). I'm quite sure it might need a bit of polishing.
With the larger screen I was able to stack a 4000mah lipo inside that was able to log 47.5hrs on a single charge.
I do like the bigger screen as readibility is greatly improved.
I always wanted a track bitmap plot but that requires more puzzling on my side (started 1.tyrs ago). On the geeky Alpha StarWars targeting graphic I haven't even started.
If people have specific screen requests please indicate them on github.

super cool! nice one Freezer!

Update SW 5.83 is available on github. Changes :
CPU freq logging configurable 40, 80, 160 or 240 MHz (longer battery life with lower CPU-freq)
CPU freq when SetupGPS() 240 MHz -> 40 mHz, Current with M10 87 mA -> 47 mA
Warning in webpage "Files" if CPU-freq is not optimal
Checksum fail UBX message in error log (*.txt file)
Voltage battery in infobar
First test : 5 Hz -> need 80 MHz, 10 Hz -> need 160 Mhz
Add "Giant font ON" in speed screens
Moved E_paper task to core 0
RxBuffer Serial2 1024 -> 2048
Support for T5 BN266 screen (All credits to SD Freezer !)

Greetings, Jan.

Select to expand quote

rp6conrad said..
Update SW 5.83 is available on github. Changes :
CPU freq logging configurable 40, 80, 160 or 240 MHz (longer battery life with lower CPU-freq)
CPU freq when SetupGPS() 240 MHz -> 40 mHz, Current with M10 87 mA -> 47 mA
Warning in webpage "Files" if CPU-freq is not optimal
Checksum fail UBX message in error log (*.txt file)
Voltage battery in infobar
First test : 5 Hz -> need 80 MHz, 10 Hz -> need 160 Mhz
Add "Giant font ON" in speed screens
Moved E_paper task to core 0
RxBuffer Serial2 1024 -> 2048
Support for T5 BN266 screen (All credits to SD Freezer !)

Greetings, Jan.

Thanks Jan for your wonderfull efforts.

Dry testing the 5.83 version for lower power drain @ 80 Mhz @ 5Hz.Nice to see the real battery value.

The Gopro 9 case in a holder.
Clips in from the rear and can be secured by a zipp tie all around.


The charge receiver coil with short distance to the charge plate coil.

Select to expand quote

PacoRaapNL said..

The Gopro 9 case in a holder.
Clips in from the rear and can be secured by a zipp tie all around.

Wow that's a good idea. Then you can strap it to your arm, is that the idea?

Wow that's a good idea. Then you can strap it to your arm, is that the idea?

Yes.No modification to the Gopro case.Just click in and secure with a zip tie.The straps are on the slow boat from China.

Will show when it is ready.

Paco

Select to expand quote

PacoRaapNL said..
Wow that's a good idea. Then you can strap it to your arm, is that the idea?

Yes.No modification to the Gopro case.Just click in and secure with a zip tie.The straps are on the slow boat from China.

Will show when it is ready.

Paco

Would you consider sharing the 3d print files? I would be keen to have one I don't have to seal up.

Select to expand quote

shannon19 said..

PacoRaapNL said..
Wow that's a good idea. Then you can strap it to your arm, is that the idea?

Yes.No modification to the Gopro case.Just click in and secure with a zip tie.The straps are on the slow boat from China.

Will show when it is ready.

Paco

Would you consider sharing the 3d print files? I would be keen to have one I don't have to seal up.

No problem to share.

Select to expand quote

PacoRaapNL said..

shannon19 said..

PacoRaapNL said..
Wow that's a good idea. Then you can strap it to your arm, is that the idea?

Yes.No modification to the Gopro case.Just click in and secure with a zip tie.The straps are on the slow boat from China.

Will show when it is ready.

Paco

Would you consider sharing the 3d print files? I would be keen to have one I don't have to seal up.

No problem to share.

If you share them on Printables, it can be added to the list of available files from Flex: www.printables.com/@Flex/collections/474942

Select to expand quote

Freezer said..

PacoRaapNL said..

shannon19 said..

PacoRaapNL said..
Wow that's a good idea. Then you can strap it to your arm, is that the idea?

Yes.No modification to the Gopro case.Just click in and secure with a zip tie.The straps are on the slow boat from China.

Will show when it is ready.

Paco

Would you consider sharing the 3d print files? I would be keen to have one I don't have to seal up.

No problem to share.

If you share them on Printables, it can be added to the list of available files from Flex: www.printables.com/@Flex/collections/474942

Here you go...................
www.printables.com/model/793351-holder-for-go-pro-with-diy-esp32-gps

Paco

Added to collection. Hoping those lurkers with other awesome prints will share too. For sure the more people share their designs, more will be inspired to come up with better ideas. No pressure Al, but your integrated boom design you showed is way better than my version IMHO. Eventually will get around to copying you.

www.printables.com/@Flex/collections/474942

Select to expand quote

Flex2 said..
Added to collection. Hoping those lurkers with other awesome prints will share too. For sure the more people share their designs, more will be inspired to come up with better ideas. No pressure Al, but your integrated boom design you showed is way better than my version IMHO. Eventually will get around to copying you.

www.printables.com/@Flex/collections/474942

Things get more and more professional along the way when people get inspired Flex2.

I also added the internal part stl files for the GoPro Hero 8 case and some other info.Will add my other designs soon.

I am still testing waterproofing the case with using transparant 1 mm thick 10 mm width acryl tape from China.nl.aliexpress.com/item/1005005751052700.html?spm=a2g0o.order_list.order_list_main.60.1ba179d2aDR7ck&gatewayAdapt=glo2nld

Thanks so much for all the work everyone! I'll have a look at making an arm mounted version soon. ??

Select to expand quote

rp6conrad said..
Update SW 5.83 is available on github. Changes :
CPU freq logging configurable 40, 80, 160 or 240 MHz (longer battery life with lower CPU-freq)
CPU freq when SetupGPS() 240 MHz -> 40 mHz, Current with M10 87 mA -> 47 mA
Warning in webpage "Files" if CPU-freq is not optimal
Checksum fail UBX message in error log (*.txt file)
Voltage battery in infobar
First test : 5 Hz -> need 80 MHz, 10 Hz -> need 160 Mhz
Add "Giant font ON" in speed screens
Moved E_paper task to core 0
RxBuffer Serial2 1024 -> 2048
Support for T5 BN266 screen (All credits to SD Freezer !)

Greetings, Jan.

For anybody that is interested in more battery operating lifetime, the modifications of Jan to throtle the frequency has a really nice impact.

I had it running in a real life example with multiple trips with car and bicycle and it lasted for 325527sec => 90 hours and 25 minutes (it is listed in the txt file)
I had it running on a 4000mah battery, BN266 screen and Beitian M10 @40MHz. It is not recommended to set it to 40MHz as it would loose datapoints, but in a quick check inside the data I could not find it (does not mean they are not there though). Now I'm repeating the test @80Mhz. Expectation is it will run 20% shorter, but should still be 72h20 long and significantly longer than the default 47h15@240MHz. I recharged it again and now repeating the rest at 80MHz to confirm.

Obviously the results with an M8 will be less as it draws more power. Curious to see those numbers as well.

Just looks at the sizes of these files:

The display does not look good for values >100, need to lower the digits from 2=>1 to keep it within the available space:

Select to expand quote

Flex2 said..
Added to collection. Hoping those lurkers with other awesome prints will share too. For sure the more people share their designs, more will be inspired to come up with better ideas. No pressure Al, but your integrated boom design you showed is way better than my version IMHO. Eventually will get around to copying you.

www.printables.com/@Flex/collections/474942

Happy to upload mine when I get a chance.

I am testing this gps (low current) M10 with 5.83

vi.aliexpress.com/item/1005004745320234.html?spm=a2g0o.order_list.order_list_main.25.27df1802qzd0vU&gatewayAdapt=glo2vnm

In configuration I set GPS type to auto detect and reboot the config.
When I log in again the default is not auto detect anymore but always M8 9600.
Is this correct?When set at M10 34000 it also does not initialize.TX and RX are on 32 and 33.Red led on GPS pulses at 1 hz.

Paco

are you sure that's genuine?
We've had devices claimed to be M8 but only M6 or 7

Select to expand quote

decrepit said..
are you sure that's genuine?
We've had devices claimed to be M8 but only M6 or 7

I hope soo. It is coming from the manufacturer store.

I need confirmation about the gps-type in the configuration settings default setting.
Like said when I choose AUTO and save the config and look again it shows M8@9600BD again.I asume that when I set Auto the setting to AUTO it stays at AUTO.Please corretc me if I am wrong.If I choose an other setting like M10@38400 and save it, it also reverts back to M8@9600BD.

When the setting is "Auto", there is a check @ boot which type of gps module is connected. When the module is recognized, the exact type is written to EEPROM, and to the config file. Second boot gives then the last detected type. If you load SW 5.75, auto detection is active @ every boot !

hey guys, collecting parts for my first gps device.
the waterproof button. is it 3-6v? and standard latching or momentary?
de.aliexpress.com/i/4000511699198.html
as example what i found. open for other suitable buttons...

You need a momentary button, 3-6 V.
Greetings, Jan.