But as soon as I put batteries in Darfon, RS485 and inverter into the LIB - inverter switches to SUB mode, and shows "warning 60" - battery is not allowed to charge or discharge.

 

My idea is switching off the current limiting option might help to fix the low charge current issue. Didn't try that yet though to be sure.

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.

 

 

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.

Thank you for the explanation. Will keep it definitely on.
LIC and PYL are giving me the warning 61 - no communication. Despite I'm switching the protocol in the battery to pylontech. I tried the RS485-1 and CAN ports, with the cables crimped accordingly to the inverter and battery pinouts.  And along with the Darfon, I've got once communication established via Growatt protocol and LIC setting but it showed me error 04 - battery low, despite it was fully charged. Now I can't repeat that again. The battery has many protocols in the list for RS485 and for the CAN. But not sure which one is compatible with my Axioma Energy SMPPT BFP 5600 (I think it's a rebrand of Expert MKS 4). The battery has the separate Voltronic Power RS485 protocol in the list. But that one also gives error 61.
May be also the firmware is outdated because it is 52.00 for Main CPU and 30.05 for the Secondary CPU.
My installer said he made it working on the other place with Axioma and Pylontec via CAN but it didn't worked in my case.   

Edited September 28, 20232 yr by DM_UA

 

Thank you for the explanation. Will keep it definitely on.
LIC and PYL are giving me the warning 61 - no communication. Despite I'm switching the protocol in the battery to pylontech. I tried the RS485-1 and CAN ports, with the cables crimped accordingly to the inverter and battery pinouts.  And along with the Darfon, I've got once communication established via Growatt protocol and LIC setting but it showed me error 04 - battery low, despite it was fully charged. Now I can't repeat that again. The battery has many protocols in the list for RS485 and for the CAN. But not sure which one is compatible with my Axioma Energy SMPPT BFP 5600 (I think it's a rebrand of Expert MKS 4). The battery has the separate Voltronic Power RS485 protocol in the list. But that one also gives error 61.
May be also the firmware is outdated because it is 52.00 for Main CPU and 30.05 for the Secondary CPU.
My installer said he made it working on the other place with Axioma and Pylontec via CAN but it didn't worked in my case.   

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 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.

Thanks, will try to do that.
But the BMS is not the Seplos, as Seplos software can't communicate to it. I wrote to them and they said - no it not their thing. Also, neither BMStool or BMSmodtool was able to connect. Seplos tool connected only once via RS485 and showed the manufacturer site www.vkingner.com. That site is not responding to anything, phone, mail, etc.
Only the TOPBMS software was able to connect via RS232. The BMS showed the model VK48100_ZWN_V15.50 and it's the same that is used in the Taico batteries. It was confirmed by their representative to me. And they confirmed also that TOPBMS is the proper software for RS232 with these batteries. So Darfon, RS485 and LIB was the Taico's suggestion.
I use the RS485-2 A and B only for the parallel connection of the batteries and they communicate that way, as I see in the RS232 monitoring software.
Also the battery have separate RS485-1 and separate CAN connections assigned for the inverter communication, at least it is stated in the manual. 

 

Thanks, will try to do that.
But the BMS is not the Seplos, as Seplos software can't communicate to it. I wrote to them and they said - no it not their thing. Also, neither BMStool or BMSmodtool was able to connect. Seplos tool connected only once via RS485 and showed the manufacturer site www.vkingner.com. That site is not responding to anything, phone, mail, etc.
Only the TOPBMS software was able to connect via RS232. The BMS showed the model VK48100_ZWN_V15.50 and it's the same that is used in the Taico batteries. It was confirmed by their representative to me. And they confirmed also that TOPBMS is the proper software for RS232 with these batteries. So Darfon, RS485 and LIB was the Taico's suggestion.
I use the RS485-2 A and B only for the parallel connection of the batteries and they communicate that way, as I see in the RS232 monitoring software.
Also the battery have separate RS485-1 and separate CAN connections assigned for the inverter communication, at least it is stated in the manual. 

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

 

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

Yes, I wrote to them earlier but no answer so far. 
Interesting that there is separate protocols RS485 in the BMS list that should work with Voltronic inverters  - Darfon and VoltronicPower. And last one doesn't work at all, with error 61. 

 

Edited September 30, 20232 yr by DM_UA

 

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.

 

This didn't worked either. But, good news - I switched the RS485 to Pylontech and tried to connect monitoring software via RS485-1. And Pmodbmstool worked. It shows 2 packs as single battery with 200AH, but shows cells on only for the master battery. Still it doesn't show the second battery as separate pack. And when I made same for the second battery (switch protocol to Pylontech) the software didn't connected and showed "abnormal" connection status. I suspect that may be the reason in the dip switches. I made as were recommended in manual for master and slave ( for the Master - all switches OFF, and for Slave 1 - ON OF OF OF). And made RS485 ADDRESS for Master in software settings as 0.
But I read that some for some BMS it is also important for pass through communication to have correct dip switch settings on each battery, as it has influence on the boud rate. So If inverter see the first battery but doesn't see the second, it may cause issue, I guess. Because when connected under the Darfon it see batteries as Group1 Pack1. Not sure but supposed to be Group1 Pack2, as there are 2 batteries.

Another good news - I connected to the inverter with Multisibconrol monitoring software and it showed  Inverter as 054/MKS2-5600. So now I suspect that my Axioma's hardware inside is Axpert MKS2 with new touchscreen from MKS4. But all it's connectors are exactly as MKS4 - COM, BMS, mini USB...
I wanted to use Multisibcontrol to monitor batteries via Pylontech protocol, but didn't succeed. 

Edited September 30, 20232 yr by DM_UA

 

Interesting that there is separate protocols RS485 in the BMS list that should work with Voltronic inverters  - Darfon and VoltronicPower. And last one doesn't work at all, with error 61. 

To be honest that is not surprising. My BMS was also sold as being compatible with voltronic inverters over RS485, but it never was. It also has a bunch of different protocols for CAN and RS485, but the RS485 never worked due to hardware issues, they only got that working on later versions of the BMS.

 

 

I made as were recommended in manual for master and slave ( for the Master - all switches OFF, and for Slave 1 - ON OF OF OF). And made RS485 ADDRESS for Master in software settings as 0.
But I read that some for some BMS it is also important for pass through communication to have correct dip switch settings on each battery, as it has influence on the boud rate. So If inverter see the first battery but doesn't see the second, it may cause issue, I guess. Because when connected under the Darfon it see batteries as Group1 Pack1. Not sure but supposed to be Group1 Pack2, as there are 2 batteries.

You are correct, the dip switches are used for unique addressing of the batteries on the rs485 network and are necessary to see the packs properly, but there have also been a lot of issues with them. What I have seen is that the dips are also used to indicate that there are multiple batteries. I know it goes against the manual, but I would try the master dip on 1000 and slave on 0100.

One would expect the comms to work with the BMS protocol set to pylontech and inverter set to PYL, using the RS485 battery port. If that doesn't work then there is likely an issue with the protocol implementation on the BMS.

 

One would expect the comms to work with the BMS protocol set to pylontech and inverter set to PYL, using the RS485 battery port. If that doesn't work then there is likely an issue with the protocol implementation on the BMS.

Doesn't work that way either. Most likely the protocol isn't implemented in the proper way. Because the BMS sets bulk and float at 52.5V (Batteries are 15S) and in the same time the manual says - 54.7V, and in the BMS settings I see that Battery Full V setting is 54V. So inverter doesn't read the data from the BMS correctly.

Will try another dip switch settings. I saw in the Volta batteries ( I actually found the topbms software recommendation on their page and it worked  ) that the 2 first dip switches changes the CAN from 500K to 250K speed. And it's definitely has impact. Addressing Master also sits on same pins. So it's another adventure.

I've got response from the TOPBMS - www.cleverbms.com today. They said that they pretty sure that my bms is not their, just similar, and they refuse to provide any advises, because they afraid that my bms might be damaged because of some manipulations they might recommend. But they insisted that if BMS responded to their RS232 software and doesn't communicate properly to Voltronic - so they sure it is not able to communicate to Voltronic in particular. May be they can communicate to the other inverters but not to Voltronic.

I'm more and more looking to the side of Solar Assistant now. Because I definitely see that I can pull data from the battery via RS232 or RS485 and can connect to the inverter via RS232. If I will not find the solution in direct communication will go to the Solar Assistant.     

Edited October 1, 20232 yr by DM_UA

Checked the dip switches in different positions for different addresses. And there appeared the complete mess. 
So master is definitely 0000. Otherwise no pass through monitoring is possible in RS232. 
But the dip switches settings doesn't appear in the BMS settings. Unless changed in the TOPBMS software, they are not changing there. If switches 3 and 4 are OFF, RS485 bms address shows as 1, no matter what. If they are ON - RS485 BMS address shows as 2. If any of the switches 1 or 2 are ON - Pmodbmstool doesn't see anything and shows "abnormal". It see the BMS only if 1 and 2 OFF. But 3 and 4 can be ON and it still see battery in RS485-1 port. Still, if Master dip set 0000 and slave 1000 - Pmodbmstool see 1 battery and its cells but capacity is combined from 2 batteries. So it makes sense for Inverter communication. On the other addresses no combined capacity and only one battery shown, which cable is connected to.
Another strange thing - Multisibcontrol doesn't see inverter today. WatchPower works as usual. 
And battery is alarming if RS485 protocol changed to Growatt, SRNE, Infinisolar, etc and Pmodbustool connected via RS485-1 on that time. So these are not compatible I guess.

Edited October 1, 20232 yr by DM_UA

 

Still, if Master dip set 0000 and slave 1000 - Pmodbmstool see 1 battery and its cells but capacity is combined from 2 batteries. So it makes sense for Inverter communication.

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.

 

Another strange thing - Multisibcontrol doesn't see inverter today. WatchPower works as usual. 
And battery is alarming if RS485 protocol changed to Growatt, SRNE, Infinisolar, etc and Pmodbustool connected via RS485-1. So these are not compatible I guess.

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.

Hi help me please i need software for Pylontech Bms FB100C1 

 

thank you IDA 

 

Hi help me please i need software for Pylontech Bms FB100C1 

thank you IDA 

Perhaps @BritishRacingGreen can help you out, he's the only one I know of who has worked on these BMS.

 

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, Junlee manual says nothing about the baud rate. But the Volta's manual (their BMS uses same software for RS232) has something on that. I attached the page from the manual. So it's even more confusing now. I wrote the email to Solar Assistant yesterday with all this story, hope they have the solution. 

 

Perhaps @BritishRacingGreen can help you out, he's the only one I know of who has worked on these BMS.

Sorry , I have only some experience with the PYL US3000C BMS hardware  , I cannot relate to the one in question.

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.

Edited October 5, 20232 yr by DM_UA