Hello @upnorthandpersonal , could you pls explain a bit about the reasoning behind choosing 125LET (vs using 160LET for example or 180LET).
My understanding is this will provide a shortcircuit protection and also limit current so that some other fuse or breaker may stop the current in case of...
@v_green57 another thing , I noticed you have a RPI2 zero (like me), I set mine to use as low current as possible (by disabling the not needed hardware via /boot/config.txt), in case it helps you (and whoever else read this )..
[root@pi2z ~]# cat /boot/config.txt|grep -v '^#'
uart_2ndstage=1...
@v_green57 - Thank you for providing the info and confirming 3201(D1) is not showing up a real fault.
On the same note RPI2Z tweaks.. I also tried to disable unneeded init functions from kernel to speed up booting. My kernel is 5.15.X , and my kernel command line (related to speedup booting)...
@v_green57 I see that you have some Epevers as well , can you pls list which value you see in D1 on 3201 register during no-charge,float, boost? Thank you :)
Ah.. reading docs on epevermodbus / driver.py :
fault": bool(
extract_bits(register_value, 1, 0b1)
), # this does not seem to be functioning correctly. Fault status is returned when no fault.
Hi again . I was looking at your DIY battery and for the BMS to outside link (the 2xblack 7AWG wires) , maybe we can remove the
extra bussbar for a better contact ? I took a picture of blue wires going to B- by mistake , but the idea remains)
Hi,
On my Epever xtra 4415 , I see weird value for bit D1 on 0x3201 register (based on modbus pdf documents , Charging equip status , 0=normal , 1=fault).
Everytime when there is float(1) or bulk(2) (which is read from D3-2 on 0x3201 ), I see D1=1, which indicates Fault . When it goes back to...
Hi @upnorthandpersonal . You mentionated using Grafana for tracking.. I would like to know if the modbus protocol is known for the solar charger MUST PC18-10015F , I tried searching online without success.