KCS: Add ability to turn off saving output state to NVS?

[stian]

Hi, I’m working on a project using the KC868-A16 to drive a relay board, and I really appreciate the KCS firmware available for this device. However, I have a concern: it seems that every output change is saved to NVS storage, which could be an issue. I’ll be frequently changing the output state of the MOSFETs, and I’m worried about potentially wearing out the storage. There might be some balancing implemented but none the less having the option to not persist to NVS would be great.

To clarify, I don’t need the output or input states to persist in NVS; storing them in SRAM would be preferable. Since the KCS firmware source code isn’t publicly available, I can’t modify this behavior myself unless I write my own firmware (something I’m considering).


Does anyone have any thoughts on this?

[admin]

what's your means? if you enable KCS "remember output state" function, it just save last state, it don't cost many memory.

[stian]

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.

[admin]

   

[stian]

Hi thank you for taking the time to add the screenshot. This was one of the things I tried initially but as far as I can tell it will still persist the state to NVS. E.g. whether or not output 1, 2 etc is enabled or disabled (or whenever the state changes). I made some good progress with my own firmware so I think I might cover my own needs for now.

Quick question, are there any free GPIO pins available for UART? I think I can use the pins used for the 433 MHz receiver & transmitter (respectively)?


Thank you again for taking the time to answer me, I really appreciate it. Love your products!

[admin]

if you are using KC868-A16, 433M sender can use as free GPIO. But also there are 3 free GPIOs you can use for serial port.

[stian]

if you are using KC868-A16, 433M sender can use as free GPIO. But also there are 3 free GPIOs you can use for serial port.

Great, Where are the are the other 3 GPIO ports located?

[admin]

   

You can use these 3 gpios directly to test, if not work well, you can remove the pull up resistance. these 3 pins connect with ESP32's pin directly.