NCSolarGarage
13.2kW Off-Grid
- Joined
- Sep 23, 2021
- Messages
- 213
Interesting, I tried to copy them and all I got was disconnected and unknown or unavailable ?
Care to share the contents of your file ?I created one from scratch. I only have those 6 parameters in it right now. I'm building off the data that flygeek decoded. I am able to poll all the registers and get values back, but matching up the returned values with the right parameter name is the part that's tough for me.
requests:
- start: 0x2298
end: 0x229B
mb_functioncode: 0x03
- start: 0x3130
end: 0x3157
mb_functioncode: 0x03
parameters:
- group: Solar
items:
- name: "PV1 Power"
class: "power"
state_class: "measurement"
uom: "W"
scale: 1
rule: 1
registers: [0x3132]
icon: 'mdi:solar-power'
- name: "PV1 Voltage"
class: "voltage"
state_class: "measurement"
uom: "V"
scale: 0.1
rule: 1
registers: [0x3130]
icon: 'mdi:solar-power'
- name: "PV1 Current"
class: "current"
uom: "A"
scale: 0.1
rule: 1
registers: [0x3131]
icon: 'mdi:solar-power'
- name: "Battery Voltage"
class: "voltage"
state_class: "measurement"
uom: "V"
scale: 0.01
rule: 1
registers: [0x2299]
icon: 'mdi:battery'
- name: "Battery Current"
class: "current"
state_class: "measurement"
uom: "A"
scale: 0.1
rule: 2
registers: [0x229A]
icon: 'mdi:battery'
- name: "Daily Production"
class: "energy"
state_class: "measurement"
uom: "kWh"
scale: .001
rule: 1
registers: [0x3153]
icon: 'mdi:solar-power'
- name: "Daily Consumption"
class: "energy"
state_class: "total_increasing"
uom: "kWh"
scale: .001
rule: 1
registers: [0x3157]
icon: 'mdi:lightning-bolt-outline'
I had that in the beginning when I hooked up my first string. It saw volts but was not producing any serious power.Anyone with upgraded firmware having problems? PV is reporting only 10% of what it should be. Average of 300 watts in full sun where I normally pull 3000. Still have the battery issue, will not discharge while the grid is connected (self use mode should be using battery before grid).
LCD 1.03.12
CPU 1.04.10
PV1 Voltage | 0x3130 |
PV1 Amperage | 0x3131 |
PV1 Wattage | 0x3132 |
PV2 Voltage | 0x3133 |
PV2 Amperage | 0x3134 |
PV2 Wattage | 0x3135 |
PV3 Voltage | 0x3136 |
PV3 Amperage | 0x3137 |
PV3 Wattage | 0x3138 |
PV4 Voltage | 0x3139 |
PV4 Amperage | 0x313A |
PV4 Wattage | 0x313B |
Not sure what you mean?did you try power cycle where it totally went dark, no switch off batter/grid & pv ?
So what fixed it in the end for you was switching mppt inputs?hooked them up to other mppt input and it started producing power as expected.
I think it was in a weird state. In my case I shut everything down and hooked up different panels.Not sure what you mean?
So what fixed it in the end for you was switching mppt inputs?
- name: "PV1 Voltage"
class: "voltage"
state_class: "measurement"
uom: "V"
scale: 0.1
rule: 1
registers: [0x3130]
icon: 'mdi:solar-power'
- name: "PV1 Current"
class: "current"
uom: "A"
scale: 0.1
rule: 1
registers: [0x3131]
icon: 'mdi:solar-power'
Just did a reboot, PV started coming in at 900w then dropped back down to the 150 range after a few minutes ?For some weird reason the inverter just doesn't do it's job very well. and you need to reset that behavior somehow.
But even if you were on grid, the EPS mode would not be activated unless the grid went down. So would be the same as off grid. Then again the BMS would kick off when battery reached low voltage cut off. I have an issue of the inverter picking back up after I hit Battery Low DOD on the grid. Seems to be ok when the Insulation Detection morning test thing is disabled? My thoughts are there is an bug in that area of the settings.Is PV Power set to 100? (Idk what that value does)
I'm on firmware
and everything is working fairly well. The only bug that I've found so far, is that the EPS does not turn off when battery reaches "Batt End Voltage". I'm not sure if its supposed to, but I can't determine what that value controls. Maybe its only used with grid power? I'm off-grid.
- LCD Version:V1.03.11
- CPU1 Software Version:V2.04.11
Try a test with arc detection disabled.Just did a reboot, PV started coming in at 900w then dropped back down to the 150 range after a few minutes ?
Just checked settings arc enable is already set to disabledTry a test with arc detection disabled.
strange, very strange. Since it all happened after a firmware upgrade, could you upgrade to the version I posted and see how it behaves tomorrow?1 from before the upgrade and 1 from after:
Note the spike to 1.5 amps today when i did the reset
I have another array on pv2
I tried to get some results with pysolarmanv5@fromport I believe you have multiple strings (I only have 1 hooked up right now), these are the values you need for the other strings
PV1 Voltage 0x3130 PV1 Amperage 0x3131 PV1 Wattage 0x3132 PV2 Voltage 0x3133 PV2 Amperage 0x3134 PV2 Wattage 0x3135 PV3 Voltage 0x3136 PV3 Amperage 0x3137 PV3 Wattage 0x3138 PV4 Voltage 0x3139 PV4 Amperage 0x313A PV4 Wattage 0x313B
So just copy the 'blocks' of code that i posted above for the PV1 input, and change the register value and title to those in this post.
I edited the basic_client to include the right data:
modbus = PySolarmanV5( "192.168.42.192", 17917xxxxx, port=8899, mb_slave_id=1, verbose=False
/usr/src/pysolarmanv5/examples# python3 ./basic_client.py
Traceback (most recent call last):
File "/usr/src/pysolarmanv5/examples/./basic_client.py", line 44, in <module>
main()
File "/usr/src/pysolarmanv5/examples/./basic_client.py", line 17, in main
print(modbus.read_input_registers(register_addr=33022, quantity=6))
File "/usr/local/lib/python3.9/dist-packages/pysolarmanv5/pysolarmanv5.py", line 347, in read_input_registers
modbus_values = self._get_modbus_response(mb_request_frame)
File "/usr/local/lib/python3.9/dist-packages/pysolarmanv5/pysolarmanv5.py", line 262, in _get_modbus_response
modbus_values = rtu.parse_response_adu(mb_response_frame, mb_request_frame)
File "/usr/local/lib/python3.9/dist-packages/umodbus/client/serial/rtu.py", line 190, in parse_response_adu
function = create_function_from_response_pdu(resp_pdu, req_pdu)
File "/usr/local/lib/python3.9/dist-packages/umodbus/functions.py", line 132, in create_function_from_response_pdu
function_code = pdu_to_function_code_or_raise_error(resp_pdu)
File "/usr/local/lib/python3.9/dist-packages/umodbus/functions.py", line 118, in pdu_to_function_code_or_raise_error
raise error_code_to_exception_map[error_code]
umodbus.exceptions.IllegalDataAddressError: The data address received in the request is not an allowable address for
the server.
/usr/src/pysolarmanv5/examples# python3 ./register_scan.py
Scanning input registers
Traceback (most recent call last):
File "/usr/src/pysolarmanv5/examples/./register_scan.py", line 31, in <module>
main()
File "/usr/src/pysolarmanv5/examples/./register_scan.py", line 14, in main
val = modbus.read_input_registers(register_addr=x, quantity=1)[0]
File "/usr/local/lib/python3.9/dist-packages/pysolarmanv5/pysolarmanv5.py", line 347, in read_input_registers
modbus_values = self._get_modbus_response(mb_request_frame)
File "/usr/local/lib/python3.9/dist-packages/pysolarmanv5/pysolarmanv5.py", line 262, in _get_modbus_response
modbus_values = rtu.parse_response_adu(mb_response_frame, mb_request_frame)
File "/usr/local/lib/python3.9/dist-packages/umodbus/client/serial/rtu.py", line 190, in parse_response_adu
function = create_function_from_response_pdu(resp_pdu, req_pdu)
File "/usr/local/lib/python3.9/dist-packages/umodbus/functions.py", line 138, in create_function_from_response_pdu
return function.create_from_response_pdu(resp_pdu, req_pdu)
File "/usr/local/lib/python3.9/dist-packages/umodbus/functions.py", line 738, in create_from_response_pdu
read_holding_registers.data = list(struct.unpack(fmt, resp_pdu[2:]))
struct.error: unpack requires a buffer of 2 bytes
Just ran a bunch of tests enabling / disabling features like arc/leak/insulation detection. Every time I reset the solar input, it would climb to ~2KW and then drop to 200 W after a few seconds.strange, very strange. Since it all happened after a firmware upgrade, could you upgrade to the version I posted and see how it behaves tomorrow?
very weird indeedTHEN I tried disabling the grid (just by shutting off the breaker pre-inverter) and BOOM she starts working properly.
My firmware version is higher than your version, probably because it is has the parallel option.Any suggestions to get it operating properly while on grid? Ideally I don't revert to older firmware but I can try that if necessary.
I do have a Parallel option, #15 in the main setup menu.very weird indeed
One of the settings maybe?
My firmware version is higher than your version, probably because it is has the parallel option.
I downgraded to your version, saw the parallel option was no longer availalble and went back to my version.
I don't think you have anything to loose by switching back & forth