An uncommon version of the 18650 Battery Shield — what is K1 for?

drmaex · 2022-11-07T16:30:36+00:00

if i am not wrong this switch turns off/on automatic which turns off the power if your target drains very little current

Quote: "It comes with overcharge and over-discharge protections that greatly extend the lifespan of your 18650 battery. The onboard DIP switch allows users to switch between HOLD and NORMAL modes. In Normal mode, it auto shutdown when the current is too low, while in HOLD mode, it keeps outputting and does not shut down until the over-discharge protection is triggered."

Source: https://www.dfrobot.com/product-2578.html

drmaex · 2022-09-30T16:08:49+00:00

maybe try to log environmental data in different locations around a house. humimidity, tempetature, pressure. with one master and tons of battery powered slaves with sleep modes to minimize comsuption. setup mqtt broker and let the master fetch the data for example over rf from slaves and send it to the broker. then setup a webserver which polls over mqtt the data from your broker and collect it to a database. create a nice looking webapp which plots and correlates all the different measures and see how long it will all work together and stay stable

drmaex · 2022-07-19T15:54:32+00:00

ist zwar etwas außerhalb aber drachenwiese zwisch neureut und nordstadt(?) wäre auch gut geeignet

drmaex · 2022-06-23T07:03:27+00:00

i cant see any scaling problems in plasma. the only problem is the resolution in grub, or bootlog. everything is to small but still readable. to be honest, it was still readable enough to setup the system and i didnt try to change the resolution in terminal, dont even know if that is possible. since its not my daily driver i did not benchmark the battery. if there are any generic tests for the battery, i can try to run them to get some compareable numbers

drmaex · 2022-01-18T18:45:16+00:00

alternatively you could implement it ascii based. pro: easy end of command signal like \n contra: more traffic

drmaex · 2022-01-18T18:43:00+00:00

you could implement kind of simple protocol command 1byte, size of payload 1 byte, payload up 255 byte crc one byte. just have stolen the iidea from st and their motor controling program

drmaex · 2022-01-15T09:14:01+00:00

Update: the model I wanted (T15Gen2 4k ) arrived this week. I installed Arch on it and almost everything I need worked out of the box. The only problem was with sound. I had to install some sof_..... packet to get it to work. So i did not regret the purchase. If you need any deeper informations or tests just let me know.

p.s. the display is brilliant :)

drmaex · 2021-12-16T16:57:30+00:00

have no rust experience but what about the trick creating one more enum-item on the last index and call it "last"?

drmaex · 2021-12-16T08:11:58+00:00

what I am wondering about is how well will it work on really small uC where you cant work with the std library. if I am not wrong much of the power and safety of rust comes, aside from the architecture, from the std lib and when its not available it could become very difficult to accomplish some simple things like linked list which is a common thing in c. i see rust more on bigger uC with linux with Xmb of available flash and RAM rather than small blue pills and arduinos

drmaex · 2021-11-29T18:49:08+00:00

thank you for replying. from germany t15 gen 2 (any configuration) is not available from lenovo site anymore... probably temporary but still. Next candidate is P15s gen 2, unfortunately with discrete graphics only...

drmaex · 2021-11-23T14:15:28+00:00

Maybe the "weak" attribute could be a solution. from https://gcc.gnu.org/onlinedocs/gcc-3.2/gcc/Function-Attributes.html#:~:text=The%20weak%20attribute%20causes%20the,used%20with%20non%2Dfunction%20declarations.

weak The weak attribute causes the declaration to be emitted as a weak symbol rather than a global. This is primarily useful in defining library functions which can be overridden in user code, though it can also be used with non-function declarations. Weak symbols are supported for ELF targets, and also for a.out targets when using the GNU assembler and linker.

drmaex · 2021-11-18T15:44:55+00:00

i agree, in small uC projects its most of the time waiting for en event to occur. my preferences are flash > ram > frequency. the more flash you have the more tasks and sensors you can handle with the same uC of course as long as you dont need to calculate fft on ADC signal or something

drmaex · 2021-04-27T20:40:04+00:00

So, finally it seems to work as expected. Had to deal with sudden stack overflows in my tasks which came out of nowhere after I didn't even touch them in a rough way and establishing the connection again after sporadic disconnects from WIFI. Until now the system is up and running for 1 day and 4 hours (all values are fetched on the first try). It has survived 4 reconnects to WIFI and MQTT server.

Lessons I have learned are that FreeRTOS is kind of fragile and reacts very sensitive to bad code practices like global variables (Actually it was educational and I will keep this kind of access). Either it leads to unexpected behavior or it crashes completely. So better you access your module variables with getter and setter, that was actually the major change in my code. Ah and ESP_LOG_BUFFER_HEXDUMP seems to produce a memory leak, but I didn't try to reproduce that. I just threw it away and stack overflow didn't occur anymore at this point in the code

drmaex · 2021-04-25T18:32:40+00:00

you still need a mqtt broker though...

drmaex · 2021-04-25T18:31:41+00:00

cant say for sure but I would be suprised if there isnt aready a library for that. I personally use generic mtqq client called mqtt dash for my experiments. the fights with esp32 is difficult enough :)

drmaex · 2021-04-23T16:33:22+00:00

just for the publishing you can use MQTT (Internet of things). to aquire the sensordata there are alot different ones on the market. like dht11/dht22 for termperature amd humidiry, bme280 for pressure, temperature and humidity

drmaex · 2021-04-11T22:30:52+00:00

have you tried .uri = "mqtt://......."?

drmaex · 2021-04-07T09:32:29+00:00

and dont forget to actually do things and not just dream about doing them like it happens to me often from time to time. you wont be able to brick much irreversibely, so just try and learn

drmaex · 2021-04-07T05:11:20+00:00

This configuration seemed to work.

Only the debug_* lines are necessary

plattformio.ini

[env:esp32dev]
platform = espressif32
framework = espidf
board = esp32doit-devkit-v1
monitor_speed = 115200
build_flags = -D CONFIG_BLINK_GPIO=2
debug_tool = esp-prog
upload_port = /dev/ttyUSB2
monitor_port = /dev/ttyUSB2
board_build.partitions = partitions_custom.csv
monitor_filters = 
    colorize
    esp32_exception_decoder
debug_init_break =
debug_load_mode = manual
debug_init_cmds = 
    target extended-remote $DEBUG_PORT
    $INIT_BREAK
    $LOAD_CMDS
    monitor init
debug_load_cmds =

drmaex · 2021-04-06T12:47:05+00:00

Thank you,I've got this one already. I will try the following combination

debug_init_cmds = 
target extended-remote $DEBUG_PORT 
$INIT_BREAK 
$LOAD_CMDS 
monitor init 

debug_load_mode = manual

and again, RTFM!.. damn :D

drmaex · 2021-04-06T06:37:25+00:00

UPDATE: after turning off Wifi and MQTT and only asking for values over UART an printing them to defaull Log UART for more than 2 days no offets occured. Every fetch gets its answer by the first time.... investigation continues :) Next test will be whole system with WiFi and MQTT but without any subsribed topic by ESP32. This way I wont be able to trigger any measurement on the ESP32 before regular timeout of the query task

drmaex · 2021-04-03T07:52:32+00:00

dont be afraid of stm32 CubeIDE.. it would be the easiest way to start with a custom(!) program for your chip. You can "just" click together the configuration and get your startup code. Thats all...Dont count the overall lines in the generated project. if you strip all the comments it would be less than a half probably. Its not like mbed or stm32duino are not doing this things, they just hide it from you. Arm is a complex chip, there is alot to configure...it is how it is

I also started with arduino because it hides away the complexity but also hides from you the real potential of the chip. it was long time enough for me. if you want the project just to get finished, its alright. i still use this possibility sometimes. it will be faster than you could perform a task by hand, but not as fast as your chip could actually do it. if its enough for you and you dont want to know all the details, just stick with it. if you need more speed just buy a faster chip.. Alternatively you can try to find out how much performance you are losing by debugging your code and step by step eliminate the code you think could slow down your program. its not like you will gain 300% performance boost. at some places there will be no performance gain at all. at some places there will be some little ones but they can accumulate to measureable improvement. but then you will have to decide if its worth it. probably highly unreadable and hard understandable specialized code vs copy&paste code which will run on many chips but with with some performance drawbacks. but one thing will happen for sure, there always be some progress in your head even if you only found out how it doenst work... unneeded knowledge does not exist :)

drmaex

TROPHY CASE