Hi,
I've searched a bit for this but not found any info.
Non-volatile memory (survives power cycle or reset) will often have a maximum number of writes before the chip "wears out". It can be 1 million writes on some micro-processors, but may vary.
Writing once per minuite for 1 year will total half a million writes.
I'm trying to maximise the solar export as I only have a G98 (3.68kW) export capacity. So looking to setup automations in HA to play with forced discharge, feed in first, self use depending on weather, battery soc and time of day.
With 6kW of solar, if I just use self use, the battery tops up early morning and then the solar panel output is throttled to 3.68kW wasting the additional capacity.
I do not intend to write every minuite, but want to know if there is a limit to be aware of.
Are all work mode, battery parameters saved to non-volatile memory?
H1-5.0-E inverter
Thanks all
Chris
Fox H1-5.0-E, 5kW inverter with 6kW solar, 17kWh battery. Home assist via RS485 waveshare converter. Heat pump, Zappi charger.
Only the engineers will know the specifications, and they won't reveal that.
The 10 year warranty I have does not have me worried about the number of writes.
Reminds me of posts gone by about SSD's failing, turns out they live longer than the scary stories at the beginning.
Battery cell technology in EV cars won't last, be dead in 100,000 miles etc, turns out not to be the case.
The 10 year warranty I have does not have me worried about the number of writes.
Reminds me of posts gone by about SSD's failing, turns out they live longer than the scary stories at the beginning.
Battery cell technology in EV cars won't last, be dead in 100,000 miles etc, turns out not to be the case.
I believe that there is some sort of a rate-limit on how frequently it will commit changes to the flash memory. Based on text I've seen in the firmware update notes and the modbus documentation.
TBH I'm not very comfortable with how the force-charge and force-discharge have been implemented in the home assistant modbus integration, if I understand it correctly it will keep resending the command every 20 seconds or so (based on how the remote-control countdown timer changes)? Compared to how the cloud schedule controls the inverter, with a countdown timer set to one hour rather than 20sec.
TBH I'm not very comfortable with how the force-charge and force-discharge have been implemented in the home assistant modbus integration, if I understand it correctly it will keep resending the command every 20 seconds or so (based on how the remote-control countdown timer changes)? Compared to how the cloud schedule controls the inverter, with a countdown timer set to one hour rather than 20sec.
This will be write cycles on the same area of the chip. If wear levelling is in place, potentially by the chip itself, it'll spread the writes out, then as it comes to read it back it knows where the most write of that data has been written.
This is a problem however if the memory chip is near full, since it can't find free areas to write to to level it out, or it reads data on an area which hasn't been written much to move it to an area which has been written to a lot, so that area can be worn instead.
Of course if wear levelling is not in place, the same area will probably be written to over and over.
This is a problem however if the memory chip is near full, since it can't find free areas to write to to level it out, or it reads data on an area which hasn't been written much to move it to an area which has been written to a lot, so that area can be worn instead.
Of course if wear levelling is not in place, the same area will probably be written to over and over.