(11-05-2024, 12:19 AM)admin Wrote: what's your means? if you enable KCS "remember output state" function, it just save last state, it don't cost many memory.
I don't see any setting for this in KCS?
For reference:
Code:
I (12925) tcp server: A new client[cli_sockfd=54] is connected from 10.0.0.4
I (46466) web socket: Handshake done, the new connection was opened
I (52290) NVS: save board state success.
I (53193) NVS: save board state success.
I (54113) NVS: save board state success.
This is what I'm referring to, that it's saving the state every time there is a state change on the output. I'm not concerned with how much memory it's using but rather that it's using NVS, doesn't this mean it gets saved to flash? I want to avoid wearing out the flash as much as possible.
Hope this makes sense.
By the way writing my own firmware wasn't as difficult as I thought so this might be the solution for me for now as I primarily only care about the output's as they will be used to drive a bunch of relays.