[Bug]: it shows the PV power incorrectly

[skavzik]

Is there an existing issue for this?

• I have searched the existing issues

Used Hardware?

Wemos D1 Mini

What happened?

I have a solar inverter (Victor MAX 10.2) with two MPPTs. so all the values are correct except for the generation of energy from solar panels. as I understand it, the data comes from only one mppt tracker. I tried using the native wifi module, it gives two sets of values for each mppt

Screenshots / Fotos

Steps To Reproduce

No response

Version

1.x.x and above

Relevant livejson output

{"EspData":{"Device_name":"Solar2MQTT","ESP_VCC":2.997,"Wifi_RSSI":-62,"sw_version":"1.2.0-Pre4","Free_Heap":18056,"HEAP_Fragmentation":17,"json_memory_usage":1429,"json_capacity":2048,"runtime":29879,"ws_clients":1,"detect_protocol":2},"DeviceData":{"AC_in_rating_voltage":230,"AC_in_rating_current":44.3,"AC_out_rating_voltage":230,"AC_out_rating_frequency":50,"AC_out_rating_current":44.3,"AC_out_rating_apparent_power":200,"AC_out_rating_active_power":200,"Battery_rating_voltage":48,"Battery_re-charge_voltage":49,"Battery_under_voltage":48,"Battery_bulk_voltage":55.5,"Battery_float_voltage":55.5,"Battery_type":"User","Current_max_AC_charging_current":20,"Current_max_charging_current":50,"Input_voltage_range":"Appliance","Output_source_priority":"Solar first","Charger_source_priority":"Solar + Utility","Parallel_max_num":1,"Machine_type":"Off Grid","Topology":"Transformerless","Output_mode":0,"Battery_re-discharge_voltage":54,"PV_OK_condition_for_parallel":0,"PV_power_balance":1,"Max_charging_time_at_CV_stage":49,"Operation_Logic":10,"Max_discharging_current":44,"Device_Model":"VMII-NXPW5KW","Protocol_ID":"PI30"},"LiveData":{"AC_in_Voltage":231,"AC_in_Frequenz":50,"AC_out_Voltage":231,"AC_out_Frequenz":50,"AC_out_VA":716,"AC_out_Watt":685,"AC_out_percent":7,"Inverter_Bus_Voltage":423,"Battery_Voltage":53.2,"Battery_Charge_Current":0,"Battery_Percent":50,"Inverter_Bus_Temperature":38,"PV_Input_Current":0,"PV_Input_Voltage":0,"Battery_SCC_Volt":0,"Battery_Discharge_Current":0,"Status_Flag":10000,"Battery_voltage_offset_fans_on":0,"EEPROM_Version":0,"PV_Charging_Power":0,"Device_Status":10,"Battery_Load":0,"PV_Input_Power":0,"Inverter_Operation_Mode":"Line","Time_until_absorb_charge":0,"Time_until_float_charge":0,"Tracker_temperature":0,"Inverter_temperature":36,"Battery_temperature":38,"Transformer_temperature":33,"Fan_speed":30,"Inverter_charge_state":"No charging","Fault_code":"Ok"}}

What browsers are you seeing the problem on?

no Issue with the Browser or WebUI

[softwarecrash]

What says the RAW section of the mqtt Data?

Please try to use PC Software watchpower and Connect the Inverter with the serial cable tonthe PC, then right click on the taskbar Icon of watchpower and enable debug, this will create a Bunch of Files, that i need.

[skavzik]

Thanks, here's all the data.
But there is no data for the second mppt in them.

debug.zip

[softwarecrash]

in the log data is nothing about the second mppt, so there is no data for it. the second dmppt data normal comes with the QPIGS2 comand.

[skavzik]

I agree.
But if you look at the output of the wifi device, then it is there.

[softwarecrash]

without knowing the query comand send by the wifi dongle there is no way to get this data

[skavzik]

Do you have any ideas how to extract them from there?

[softwarecrash]

it need a "middleman" grab of the serial comunication, on amazon/ebay they exsist some cheap logic analyzers that will work with saleae software

[skavzik]

I ordered an analyzer, and I'll be back as soon as I collect the data.
thanks

[softwarecrash]

you can try to send over the custom comand QPIGS0 and QPIGS1 some datasheets have wiered descriptions. eventualy your device will answer on this

[skavzik]

I've tried these commands, but they don't work for me.
thanks

[skavzik]

Session 3.zip
I recorded the communication of the wifi module with the inverter using Saleae Logic. But I don't know how to interpret it correctly.

[softwarecrash]

thats interesting, your wifi dongle talks over modbus, but your device can answer on pi serial.

[skavzik]

I am not sure about this, most likely I did not choose the right interpreter. or have you already managed to decode the information?

[softwarecrash]

you have selected the right interpreter 05,03 at start is reading holding registers, thats typical for modbus communication

@all-solutions @bigdigital can you check this for usable data?

[skavzik]

@softwarecrash Is there any way I can help force solutions to the problem?

[softwarecrash]

@skavzik you can ask your seller or vendor for a communication Protocol.

So the solar2 read the Data over pi30 serial, but Not all Data Provided

Your WiFi dongle and the capture tells modbus communication, so its possible to build in this, but we need the prototocol sheet

[bigdigital]

This is a PowMr POW-HVM protocol.
According to salae capture it requests at 2400 baud, deviceid 5, starting from 4501 register - 45 registers in a row
I recently added as a test this protocol https://github.com/bigdigital/Solar2MQTT/blob/merge-remote/src/modbus/device/pow-hvm/pow-hvm.h so you can try it
here is the registers maps

[skavzik]

@bigdigital How do I activate this protocol on my device?

[bigdigital]

Try this version of solar2mqtt if everything correct it should autodetect your device . take note to the connection pins on esp. This project use 13 as tx, 12 rx. If it would not work, contact me in discord for debugging (this protocol was not tested on the real device yet).

[skavzik]

RX -> D6
TX -> D7

[bigdigital]

aha, it autodected the qpiri because this device support this command. it is possible to change protocol manually. In webserial console send "setp 6" you should see Change protocol to: MODBUS_POW_HVM

[skavzik]

After switching the protocol, the connection is lost, and after updating the page, it looks like communication is taking place using the old protocol (2)

[bigdigital]

please try this version should be fixed a protocol change. If not contact me in discord . https://discord.com/invite/pAArqVsVS4

[essergey]

I have a POVMR 6.2, I also tried Pre2.0.0-Pre6a to switch to modus, but it didn’t switch.