Good day,I have a problem reading the charger current. 777 is listed in the modbus TCP address list, but venus reports an error.
Do you have any idea where the problem is?
Thank you
asked
Modbus TCP address 777 problem
UPDATE 2022-02-08: solved with todays official release of Venus OS v2.82.
Hi all, I explain this - and the good news is that we're putting this register back. We shouldn't have removed it. Its coming back in v2.82. Perhaps released tomorrow, and if not then, then latest next week.
We broke register 777 during Venus OS v2.80 development. I expect @Pavel Richter to be running a beta version. (please check, and make sure that is what you want!); hence already noticing it in November last year.
More information about beta version is here; https://www.victronenergy.com/live/ccgx:beta-testing
Apologies for the confusion about this!
Is reading of other modbus addresses working successfully? I have the same issue with the reading of addresses (3704,3705) related to trackers current on MPPT´s 450/100. It looks like some kind of FW issue. No MPPT tracker currents are possible to read on addresses listed in the register overview. Or at least I have not found any which would provide tracker current information.
My 450/100 is at ID 100 which is strange but I can read 771-777 and 3700-3705 without any problems. But current always returns 0.
450/100 firmware v1.05
GX firmware v2.80~16-large-21
Hi Shaneyake, correct, 3704,3705 returns 0. But I have two 450/100, so as described in the register list, 777 is not available for multiple VE.can systems. Voltage readings on 3700,3701 are without problems. I´m running FW 2.73 on Cerbo and v1.05 on MPPT´s.
Now I tried v2.80-29 on Cerbo, and getting error on asking for registers 3704, 3705 
Hi
Yes. the address is 233 and 235.
I use octo GX and these IDs are also written in the list. directly in GX.
The FW version is 2.80 -21-large-23.
It is strange that reading other values goes without problems.
Same result here. 150/85 mppt at Id 223. Requesting from 776 onwards throws an error bc 777.
I don't know if PV Current shouldn't be available or if that's an error. I suppose that is difficult to manage adding new registers.
@mvader (Victron Energy) shouldn't be possible to add empty "placeholders" to those isolated "holes" in the register list? That way one could request the required complete list in one row and avoid using several connections and simultaneous requests. I think that's bad for the system.
For getting the complete com.victronenergy.system, you need 7 connections/requests (and gridLossAlarm is also broken)
Not sure of the details on this but I noticed this issue today, previously I had been using address 777 for PV current, now not available. The MODBUS TCP Register document has been updated, Version 2.70 included PV current at 777, however in the the latest version 2.80 its been removed.
thanks for the anwers.
I tried 2.82 and it works. But is there a version of OS LARGE 2.82?
