DM_UA

Hello everyone. You just need to try. It won't flash with incompatible firmware.

I wanted to throw away the Wi-Fi and just connect the Solar Vampir instead. But it has a different protocol than the MAX II. I'm currently talking to the Vampir admin. I want to get this whole thing working.

Yes, I also monitor Solarassistent. But now it can connect to the inverter via Wi-Fi. But it doesn't connect to this one. But it does connect to the Voltronic MAX II 11000W. And I want to install a Solar Vampir, too, and I need another RS-232 port. Now I'm wondering how to solve this.

Yes, try it. I had the same firmware as you. I had to dance with a tambourine near the inverter. I re-flashed it and forgot about it. One DSP 25.09 didn't work. It also started throwing errors with my settings. I reverted it back and forgot about it. I just wanted to research the firmware and choose a good one. Now I'm on 25.11 and everything is fine.

Hi. I had the same problem with these firmware versions. And the representatives couldn't provide me with anything. Try updating to the new version. The latest one. It worked for me. It works without any issues.

To save readers' time, the two files in the Eissa's post before last are for Ultra main firmware version 25.10 (left/first), and Ultra display version 12.18 (right/second). Don't confuse 12.1x for Ultra with 12.2x and 12.3x (etc?) for Max and other models.

Probably the final update on my situation. Today I've got the Raspberry and installed the Solar Assistant. Connected USB socket of the inverter directly to the USB on the Raspberry, and the batteries connected via RS232. No issues at all. Up and running. Solar assistant see all data from the paralleled batteries, 2 separate packs, with voltage, SOC and temperature. Temperature, however is wrong - 10 degrees lower than it is.  Also Assistant see all data from the inverter. Just plug and play.
In a while I'm expecting to get RS485 converter for the JK BMS on my third battery so all data will be in one place. Not perfect as if inverter would see the batteries directly, but better than it is was only voltage based. 
Also, another, probably important thing. The Solar Assistant wasn't able to connect to WIFI made on the mesh system devices. Only to the regular Wifi router. I had similar situation with the home security system before/ so just connected it to the other network made with plain router. 
It's because of some security protocols incompatibility, in mesh for such devices like Raspberry, etc. Even if you plug the Raspberry to the ethernet port of the mesh system device. Strange but that's what I've noticed.

Bummer it turned into such a mess, I'm out of ideas. I guess these are the correct dip settings and they match the manual. The manual also suggests that the dips are only used for addressing, nothing else like baud rate etc. There certainly seems to be something wrong with the protocol implementation somewhere. Solar Assistant might be the only way forward if they support your battery.
Possibly something gone wrong with all the dip changes and testing, maybe it'll come right after shutting everything off for 5 mins and restarting.

Yes, that is definitely not a seplos. It seems it is almost working via the RS485-1 port, but maybe there is an error in the protocol implementation, you might need a firmware update for the BMS which should be quite easy as you have the pc software working. Perhaps you can try to get hold of them via this site: https://www.cleverbms.com/ or maybe via their Aliexpress store: https://www.aliexpress.us/item/3256804556606243.html

It sounds to me like you might have a seplos BMS in your battery, like my Shoto battery. The thing with this BMS is that you can't use the RS485A & B ports, those are only for battery to battery comms, as you had it working with the bms software over RS232, the batteries then communicate over RS485 with each other. These ports can be used for inverter comms only if you have something like solar assistant in-between.
Only the CAN port on the battery can be used for direct inverter comms, but the problem is that the inverter expects RS485 if you select PYL, LIB or LIC. Voltronic only uses CAN for the Weco and Soltaro settings. This is probably why your installer got it working with the Axioma, because he used CAN.
I suspect you should be able to get it working on a growatt if you select the growatt protocol on the battery and use the CAN port to connect to the inverter, not RS485.

It looks like you have an issue with the communication to the inverter, either through the wrong battery port or the cable is incorrect or you need to use the PYL or LIC setting. I would be very carfeul turning off the current limiting if there are no (or faulty) comms to the inverter or the inverter will try to push too many amps into the battery when it is full. Current limiting should only take effect once the battery is over 95% and is there to allow the battery to balance. If comms are working the BMS should tell the inverter to reduce the current to 10A, but if there are no comms the current limiting is there to protect the battery. This is why the inverter throws an error and won't charge if there is a comms issue, so it doesn't damage the battery.

Esener, Taico, Volta, Junlee, GenixGreen, The BMS comes from www.vkingner.com, or www.cleverbms.com 
the software to connect via RS232 - TOPBMS 6.1
 

Esener, Taico, Volta, Junlee, GenixGreen, The BMS comes from www.vkingner.com, or www.cleverbms.com 
the software to connect via RS232 - TOPBMS 6.1