modbus: epsolar tracer bn protocol issue

[corbolais]

PROBLEM DESCRIPTION

Reading telemetry off of a epsolar tracer bn mppt pv controller via modbus. Generally, it's somewhat working. The esp is reporting data via web ui and mqtt. Getting - amongst other values - PV-array voltage and current. As soon as battery voltage is requested, PV voltage and current stays at 0V, 0A, no matter what order the requests are specified in in the script.
W/o battery voltage:

Battery
EPSOLAR I_bat:	0.05 A
EPSOLAR T_bat:	12.81 °C
EPSOLAR V_batMaxDay:	30.46 V
EPSOLAR V_batMinDay:	25.44 V
PV
EPSOLAR V_pvIn:	44.00 V
EPSOLAR I_pvIn:	0.03 A
EPSOLAR P_pvIn:	1.68 W
EPSOLAR E_genDay:	0.02 kWh
EPSOLAR T_ctrl:	18.48 °C

With battery voltage (and battery capacity, it's the same if C_batt is omitted though):

Battery
EPSOLAR I_bat:	0.04 A
EPSOLAR T_bat:	12.81 °C
EPSOLAR V_batMaxDay:	30.46 V
EPSOLAR V_batMinDay:	25.44 V
PV
EPSOLAR V_pvIn:	0.00 V
EPSOLAR I_pvIn:	0.00 A
EPSOLAR P_pvIn:	1.40 W
EPSOLAR E_genDay:	0.02 kWh
EPSOLAR T_ctrl:	18.52 °C
EPSOLAR V_bat:	0.00 V
EPSOLAR C_bat:	2805.00 %

The issue here is: V_pvIn 0V, I_pvIn 0A, V_bat 0V. And of course the battery capacity of 2805%.

The esp-07 got 1M of RAM, I initially assumed this to be the issue. While this couldn't be verified with a 4M (i.e. esp-12f) module yet, former discussions in this regard suggest the RAM available is not the underlying issue.

REQUESTED INFORMATION

• Read the Contributing Guide and Policy and the Code of Conduct
• Searched the problem in issues
• Searched the problem in discussions
• Searched the problem in the docs
• Searched the problem in the chat
• Device used (e.g., Sonoff Basic): esp-07
• Tasmota binary firmware version number used: 9.4.0.3
  • Pre-compiled
  • Self-compiled
• Provide the output of command: Backlog Template; Module; GPIO 255:

18:08:21.575 MQT: stat/esp07-48/RESULT = {"NAME":"modbus","GPIO":[0,0,0,0,0,0,0,0,0,0,0,0,0,0],"FLAG":0,"BASE":18}
18:08:21.794 MQT: stat/esp07-48/RESULT = {"Module":{"0":"tf-modbus"}}
18:08:22.047 MQT: stat/esp07-48/RESULT = {"GPIO0":{"0":"None"},"GPIO1":{"0":"None"},"GPIO2":{"0":"None"},"GPIO3":{"0":"None"},"GPIO4":{"0":"None"},"GPIO5":{"0":"None"},"GPIO9":{"0":"None"},"GPIO10":{"0":"None"},"GPIO12":{"0":"None"},

• Provide the output of this command: Status 0:

18:17:13.334 MQT: stat/esp07-48/STATUS = {"Status":{"Module":0,"DeviceName":"esp07","FriendlyName":["esp07"],"Topic":"esp07","ButtonTopic":"0","Power":0,"PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":1,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0,"InfoRetain":0,"StateRetain":0}}
18:17:13.343 MQT: stat/esp07-48/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota/release/tasmota.bin","RestartReason":"Software/System restart","Uptime":"0T00:23:22","StartupUTC":"2021-05-27T15:53:51","Sleep":50,"CfgHolder":4617,"BootCount":11,"BCResetTime":"2021-05-27T15:33:45","SaveCount":36,"SaveAddress":"FB000"}}
18:17:13.351 MQT: stat/esp07-48/STATUS2 = {"StatusFWR":{"Version":"9.4.0.3(tasmota)","BuildDateTime":"2021-05-27T17:48:26","Boot":5,"Core":"2_7_4_9","SDK":"2.2.2-dev(38a443e)","CpuFrequency":80,"Hardware":"ESP8266EX","CR":"376/699"}}
18:17:13.371 MQT: stat/esp07-48/STATUS4 = {"StatusMEM":{"ProgramSize":628,"Free":372,"Heap":18,"ProgramFlashSize":1024,"FlashSize":1024,"FlashChipId":"1440D8","FlashFrequency":40,"FlashMode":3,"Features":["00000809","87DBC587","042EC001","08009FCF","010013C0","C010B989","00004004","00001000","00000020"],"Drivers":"1,2,3,4,5,6,7,8,9,10,12,15,16,18,19,22,24,26,27,29,30,35,37,45","Sensors":"1,3,4,5,6,7,8,9,10,12,24,53,58"}}
18:17:13.412 MQT: stat/esp07-48/STATUS11 = {"StatusSTS":{"Time":"2021-05-27T18:17:13","Uptime":"0T00:23:22","UptimeSec":1402,"Vcc":3.427,"Heap":16,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1}}}

TO REPRODUCE

The script used:

>D
r="1,0104"
>B
->sensor53 r
>M 1
+1,3,m,0,115200,EPSOLAR,1,5,r010431000002,r010431020002,r010431100002,r010433020002,r0104330c0002,r0104331b0002,r0104331a0001,r0104311a0001
1,=hBattery
;%r%02UUuu@i6:1,C_bat,%%,C_bat,2;,r0104311a0001
;%r%02UUuuxxxx@i6:100,V_bat,V,V_bat,2;,r0104331a0001
%r%04UUuuxxxx@i5:100,I_bat,A,I_bat,2
%r%04UUuu@i2:100,T_bat,°C,T_bat,2
%r%04UUuu@i3:100,V_batMaxDay,V,V_batMaxDay,2
%r%04xxxxUUuu@i3:100,V_batMinDay,V,V_batMinDay,2
1,=hPV
%r%04UUuuxxxx@i0:100,V_pvIn,V,V_pvIn,2
%r%04xxxxUUuu@i0:100,I_pvIn,A,I_pvIn,2
%r%04ssssSSSS@i1:100,P_pvIn,W,P_pvIn,2
%r%04ssssSSSS@i4:100,E_genDay,kWh,E_genDay,2
%r%04xxxxUUuu@i2:100,T_ctrl,°C,T_ctrl,2
%r%02UUuu@i6:100,V_bat,V,V_bat,2
%r%02UUuu@i7:1,C_bat,%%,C_bat,2
#

Comment the last two pattern matches and all values display as expected. Note that it is not allowed to mix and match standard requests and binary requests, i.e. r0104331b0002,0104331a is not working. Is this intentional? IIRC, some examples given on the tasmota-modbus web page show exactly this mix and match of std and bin requests.

EXPECTED BEHAVIOUR

Any number of values queried should result in the values being reflected in the web ui/mqtt msg. In particular, if querying an additional value such as battery voltage everything should show up in the ui/mqtt. Querying a particular register should not result in other values not being displayed. Right now, I get to choose between either PV array voltage and current or battery voltage. It is worth noting, the PV array values are returned as 4 byte whereas battery voltage is a 2 byte return. The data is there for tasmota/modbus to parse (see next paragraph) but tasmota/modbus just won't show it.

ADDITIONAL CONTEXT

Using sensor53 d1, it is obvious the data is getting in. I.e. > 01 04 31 1a 00 01 1e f1 (remaining battery capacity) is answered by : 01 04 02 00 64 b8 db (100%), which is correct. Same for > 01 04 33 1a 00 01 1f 49 (battery voltage) and : 01 04 02 0a eb ff df (27.95V).

18:02:02.284 > 01 04 31 10 00 02 7e f2 
18:02:02.330 : 01 04 04 05 00 07 4c f8 8d 
18:02:02.782 > 01 04 33 02 00 02 df 4f 
18:02:02.826 : 01 04 04 0b e6 09 f0 1e 43 
18:02:03.280 > 01 04 33 0c 00 02 be 8c 
18:02:03.325 : 01 04 04 00 02 00 00 5a 44 
18:02:03.780 > 01 04 33 1b 00 02 0e 88 
18:02:03.824 : 01 04 04 00 04 00 00 ba 45 
18:02:04.504 > 01 04 33 1a 00 01 1f 49 
18:02:04.548 : 01 04 02 0a ea 3e 1f 
18:02:04.998 > 01 04 31 1a 00 01 1e f1 
18:02:05.041 : 01 04 02 00 64 b8 db 
18:02:05.491 > 01 04 31 00 00 02 7f 37 
18:02:05.610 : 01 04 04 10 b0 00 03 be a2 
18:02:06.001 > 01 04 31 02 00 02 de f7 
18:02:06.049 : 01 04 04 00 6f 00 00 cb 99 
18:02:06.837 > 01 04 31 10 00 02 7e f2 
18:02:06.880 : 01 04 04 05 01 07 4b e8 8f 
18:02:07.298 > 01 04 33 02 00 02 df 4f 
18:02:07.343 : 01 04 04 0b e6 09 f0 1e 43 
18:02:07.844 > 01 04 33 0c 00 02 be 8c 
18:02:07.887 : 01 04 04 00 02 00 00 5a 44 
18:02:08.342 > 01 04 33 1b 00 02 0e 88 
18:02:08.385 : 01 04 04 00 05 00 00 eb 85 
18:02:08.838 > 01 04 33 1a 00 01 1f 49 
18:02:08.882 : 01 04 02 0a eb ff df

[corbolais]

Just submitted the issue and had another look at the web ui:

Battery
EPSOLAR I_bat:	0.05 A
EPSOLAR T_bat:	12.63 °C
EPSOLAR V_batMaxDay:	30.46 V
EPSOLAR V_batMinDay:	25.44 V
PV
EPSOLAR V_pvIn:	39.68 V
EPSOLAR I_pvIn:	0.03 A
EPSOLAR P_pvIn:	1.40 W
EPSOLAR E_genDay:	0.02 kWh
EPSOLAR T_ctrl:	17.30 °C
EPSOLAR V_bat:	0.00 V
EPSOLAR C_bat:	2813.00 %

V_pvIn and I_pvIn are there, reasonable values at that. V_bat and C_bat are still missing or bad numbers though.