u dont have 8551, u have shitty 621 one. first to change.
...found some Original Backups even Ksger 3.1
Not tested by me!Are they different from the ones in github?
Quote from: DavidAlfa...found some Original Backups even Ksger 3.1
Not tested by me!Are they different from the ones in github?
I dont see any for Ksger 3.1 on github
It seems it has been resolved by a complete erase from the STM32 utility. It now works fine. I don't know the reason why a complete erase from the utility would differ from a new flash which does an erase or an All Reset.
A question: When setting the zero value in calibration, when I start the board the first time, the temperature in the debug menu is around 30, 6 degrees above the ambient with an adc around 30. If I left the debug menu running (set at zero) it slowly rises in a few minutes to reach around a 100 degrees!
Which value should I be using for zero in calibration ?
Uhh...
What is 32...44? °C?
135 ADC value when reading 44...°C?
Typically you calibrate when the system has fully heated up and got stable.
Some drift is normal as the handle/board heat up, it's working with very small signals and there's no compensation of any kind, few tens of microvolts are enough to change the readings slightly.
Given the way they're made, that's more a design issue than a hardware failure.
If not done yet, I'd redo the soldering joints of every single smd resistor, capacitor...
Is there a way to enter the zero value manually instead of capturing it? I'd have to power the board for half an hour and wait for it stabilize.
Anyone tried this handle? : https://www.aliexpress.com/item/4000130747937.html
On paper it checks all the right boxes. I mean, it's made of aluminium, has a usable shape, short tip to grip distance, a large silicon sleeve and is suspiciously cheap (compared to all the "nice" T12 handles). So, is it as good as advertised or yet another piece of garbage that burn user's hand or doesn't fit the tip properly?
I just say because I've received few reports of the controller going nuts randomly, magically fixed after lowering the screen brightness.
So it must be the LDO, might be overheating, defective, a broken solder joint... there's no way I could know unless the owner works on it, which almost never happens.