So you didn't solder the sd card in? But your work around looks good.

Rolz said..
hello all,
one of my new units seemed to freeze on boot, it's just locked on this screen.
I haven't seen this before, so wondering what the recommend process is?
Leave it as is for a week+ so it totally drains flat?
Then charge and see what happens?
Issue happened Sunday so I still have a few more days I think until properly flat as the device was apparently full charged.

I get this too. When i still have access a connection to the micro usb fixes it straight away. Not sure how to fix it when its all full off epoxy except the wait a see method ?

rp6conrad said..

Alhop said..

Rolz said..
hello all,
one of my new units seemed to freeze on boot, it's just locked on this screen.
I haven't seen this before, so wondering what the recommend process is?
Leave it as is for a week+ so it totally drains flat?
Then charge and see what happens?
Issue happened Sunday so I still have a few more days I think until properly flat as the device was apparently full charged.

I get this too. When i still have access a connection to the micro usb fixes it straight away. Not sure how to fix it when its all full off epoxy except the wait a see method ?

This must be a power supply issue : @boot, the current peaks can be >300 mA (Wifi try to connect), and this causes a power fail. It can be the protection in the lipo, when the lipo has a very low voltage (<3V). When connecting to usb, the supply voltage rises to 5V, and the power supply is again OK.
Another issue could be the (weak") fuse protection in the circuit of the batt connector : sometimes this fuse blows, and the battery supply over the batt connector will not work anymore. A easy fix is to directly solder your bat to the "Vbat" connection and GND.
My advice : test the assembly for a complete drain of the battery. Then, try to start it up with only the inductive charging, but the coil already installed in the housing !!
There is a chance that the coil is to far away from the charging coil, and that the charging power is not strong enough to start the charging.
Good luck !!!

I'm already on VBat / Ground so that rules that out.

Looking awesome Al...Is that a Resin print?

Looking very nice, popping candy red!
Did you continue pooring until it started to flood over the edges in a single go, or did you treated the case with resin first? I'm waiting for my resin to arrive as well. Will post some pictures later this week.

Freezer said..
Looking very nice, popping candy red!
Did you continue pooring until it started to flood over the edges in a single go, or did you treated the case with resin first? I'm waiting for my resin to arrive as well. Will post some pictures later this week.

Yep that's what i did. Just kept pouring in the top until it went over the sides. I was going to use a polycarb screen but just filled it with epoxy instead. It sets super clear and rubbery so should protect the e-paper quite well.

Printing box two at the moment so will take some snaps of my process next time.

Alhop said..

Freezer said..
Looking very nice, popping candy red!
Did you continue pooring until it started to flood over the edges in a single go, or did you treated the case with resin first? I'm waiting for my resin to arrive as well. Will post some pictures later this week.

Yep that's what i did. Just kept pouring in the top until it went over the sides. I was going to use a polycarb screen but just filled it with epoxy instead. It sets super clear and rubbery so should protect the e-paper quite well.

Printing box two at the moment so will take some snaps of my process next time.

Out of interest what brand of epoxy did you go with? I've seen some go yellow and if I do go down epoxy path I want to be sure I get that super clear look like you've got going

Rolz said..

Alhop said..

Freezer said..
Looking very nice, popping candy red!
Did you continue pooring until it started to flood over the edges in a single go, or did you treated the case with resin first? I'm waiting for my resin to arrive as well. Will post some pictures later this week.

Yep that's what i did. Just kept pouring in the top until it went over the sides. I was going to use a polycarb screen but just filled it with epoxy instead. It sets super clear and rubbery so should protect the e-paper quite well.

Printing box two at the moment so will take some snaps of my process next time.

Out of interest what brand of epoxy did you go with? I've seen some go yellow and if I do go down epoxy path I want to be sure I get that super clear look like you've got going

I checked with Flex and you need to ensure a few things: Needs to be of the pooring type, ultra clear, slow curing, low-heat, being able to fill the right thickness level. The UV resistance is important, as it will not turn yellow over time. However Flex had no problems while it was not listed as UV resistant.
I went for the following: www.mrboat.nl/epoxy-giethars/epoxy-giethars-ultra-clear-75/
I printed a frame that will keep the case nicely level. I already received the pooring epoxy, but will likely start doing the first pore on Friday. Fingers crossed.

Beitian added several M10 chips (ubx M10050) to the assortiment !! They are marked as the BE-series. Again in different sizes : BE-180, BE-220, BE-250, BE-280. There is even a BE-126, but without Antenna. I ordered 2* BE-180. Price is the same as the BN series (ubx M8.)
nl.aliexpress.com/item/1005004756134206.html?spm=a2g0o.order_list.order_list_main.5.3c7e79d24KLnwL&gatewayAdapt=glo2nld
I received 3 16GB micro SD cards from Ali, first tests look good. Read/write speeds even better then the Sandisk Ultra 16GB.
nl.aliexpress.com/item/1005004274548931.html?spm=a2g0o.order_list.order_list_main.10.3c7e79d24KLnwL&gatewayAdapt=glo2nld
Greetings, Jan.

Rolz said..

Alhop said..

Rolz said..
hello all,
one of my new units seemed to freeze on boot, it's just locked on this screen.
I haven't seen this before, so wondering what the recommend process is?
Leave it as is for a week+ so it totally drains flat?
Then charge and see what happens?
Issue happened Sunday so I still have a few more days I think until properly flat as the device was apparently full charged.

I get this too. When i still have access a connection to the micro usb fixes it straight away. Not sure how to fix it when its all full off epoxy except the wait a see method ?

interestingly I have another unit with a frozen screen... again with the wake up screen, also with 5.71
Will let this one run down before putting on charge again to see if it comes back to life.
The first one I had frozen was def the board, but to freeze at the same spot makes me wonder...

How long is a general rule of thumb to wait for the battery to go flat before trying to put on wireless charger?
This Sunday will be a week.

Maybe slightly differant but had the same happen with two units I am putting together at the moment, lucky not potted so using Arduino plugged them back in to unfreeze.

Interestingly I first loaded the Firmware via USB and everything worked fine unit starts, stops, sat okay etc but when I went to change the config file via connecting it via wireless and using the new web interface is when the issues started, exactly like your frozen screen.

The issue seems to have resolved itself by first pluggung in the USB to unfreeze, connect via wireless and then load the firmware via the new Web Interface this then solved the issue when changing the config file via web interface no longer freezing the screen.

The units booted as per normal, seems if you load the firmware via the USB then try to change the config file via webinterface it freezes the unit on the above screen, might not be whats happening with your units Rolz and it could be I'm doing something wrong.

decrepit said..

Rolz said.. How long is a general rule of thumb to wait for the battery to go flat before trying to put on wireless charger?
This Sunday will be a week.

Just because the screen is frozen, doesn't mean the processor has stopped running.
The battery probably went flat in 10hrs. Even if it hasn't you don't put much energy in it by a quick charge to see if it wakes. That's what Anita found anyway.

The first one that froze and was unrecoverable the battery was still full charge, I'm currently using it to test on my 4th build... so between my first one that is still just amazing and why I'm persisting and the bad luck on the others, I'll figure out whats going on

This morning I decided to put the frozen one on the wireless charger and it came back to life... though initially it cycled through the screens, then turned off and back on... now after being on charger for an hour it sits on the esp32ap screen...

But when I connect to it, I get 2 ping responses and then shuts down, does save data screen and then reboots again back to esp32ap screen.

I'm leaning towards the reed switch in it has crapped out.

Will leave on charge a little longer and if no luck will have to crack it open

boardsurfr said..
You may also want to double-check that you are loading the correct firmware. If the wrong firmware is loaded, it may look like everything is fine, but the units appear to freeze on some screens. I just had that happen after downloading and compiling the current firmware, and not realizing that the 5.72 sources on Github have the M10 chips set as the default, without checking if that is indeed the case.

To Jan: when supporting multiple chips that require different initialization or baud rates, it becomes essential to verify that the communication works as expected. For example, the firmware should check if it receives the "ACK" messages after setting anything. That way, it should be possible to automatically figure out the chip type and the correct baud rate.

Good one! I just flashed some new screens to the latest firmware (before connecting anything). I will connect some M10 chips but of you use still the older M8 ones (BN180, BN220, BN280) you need to comment out the 6th line in the Rto5.h:
#define UBLOX_M10 //indien ublox M10 wordt gebruikt, andere ublox init nodig !!!
into
//#define UBLOX_M10 //indien ublox M10 wordt gebruikt, andere ublox init nodig !!!

In the Ubloc.ccp it will check if this parameter is defined, otherwise it will use the M8 initialization.
It would definately be nice if the firmware would switch between the various gps chips, baudrates and epaper-screens instead of loading different bin files.

boardsurfr said..
You may also want to double-check that you are loading the correct firmware. If the wrong firmware is loaded, it may look like everything is fine, but the units appear to freeze on some screens. I just had that happen after downloading and compiling the current firmware, and not realizing that the 5.72 sources on Github have the M10 chips set as the default, without checking if that is indeed the case.

To Jan: when supporting multiple chips that require different initialization or baud rates, it becomes essential to verify that the communication works as expected. For example, the firmware should check if it receives the "ACK" messages after setting anything. That way, it should be possible to automatically figure out the chip type and the correct baud rate.

I'm just downloading the bin file, not compiling...
This was the one I've been using github.com/RP6conrad/ESP-GPS-Logger/tree/master/Bin_files_BN213
Will do a build and test later on today, once confirmed it's all ok compared to my existing esp32-gps and my mini-motion I will seal it up.
Fingers crossed that'll be my last bad luck one

That's what can happen with open source stuff. A small user base, makes specialised stuff uneconomical commercially. It only takes a handful of smart enthusiasts, to come up with the goods