BMS seplos + Hybrid luxpower

[duyvietstar]

Hello every one,
I use hydrid luxpower with battery ( diy with seplos bms), i modify baterry capacity in software, but in luxpower didn't recieve full capacity of battery ( my case use 105Ah cell), luxpowwer only receive 50Ah.
Have you encountered this problem yet? How does it handle?

 

[automatikdonn]

Hello every one,
I use hydrid luxpower with battery ( diy with seplos bms), i modify baterry capacity in software, but in luxpower didn't recieve full capacity of battery ( my case use 105Ah cell), luxpowwer only receive 50Ah.
Have you encountered this problem yet? How does it handle?

Mine does the same thing. For whatever reason it shows 50ah per pack. Pack chaining does seem to work.

I'm thinking there may be a setting in the battery that can fix this.

Have you asked Seplos?

 

[olexandr.makhanets]

Hello every one,
I use hydrid luxpower with battery ( diy with seplos bms), i modify baterry capacity in software, but in luxpower didn't recieve full capacity of battery ( my case use 105Ah cell), luxpowwer only receive 50Ah.
Have you encountered this problem yet? How does it handle?

Hi! How did you fix the issue?

 

[swwils]

Mine is the same when the LUX is set to PYLON and the Seplos v3 to PYLON_CAN, shows a 305aH pack as 200ah or a multiple of 50ah. I cant make much sense of it because I thought ID 0x379 was lux capacity and charge and discharge amps are sent with ID 0x351 for all CAN protocol types.

Maybe @Sleeper85 can comment with their expertise. I need to test with "STD" on the lux and "SMA_CAN" on the seplos which might have better luck.

 

[ChrisG]

Does everything else work between the Seplosv3 and Lux? No issues with 100% SOC stopping charging even though batteries are not full?

 

[SwwilsSolarMan]

Does everything else work between the Seplosv3 and Lux? No issues with 100% SOC stopping charging even though batteries are not full?

I've not got it fully setup to try yet.

 

[houseofancients]

Mine is the same when the LUX is set to PYLON and the Seplos v3 to PYLON_CAN, shows a 305aH pack as 200ah or a multiple of 50ah. I cant make much sense of it because I thought ID 0x379 was lux capacity and charge and discharge amps are sent with ID 0x351 for all CAN protocol types.

Maybe @Sleeper85 can comment with their expertise. I need to test with "STD" on the lux and "SMA_CAN" on the seplos which might have better luck.

Are you sure you are not reffering to the max discharge amps ?
The is a switch to half the discharge amps when the are not multiple batteries in the comm chain

 

[SwwilsSolarMan]

Are you sure you are not reffering to the max discharge amps ?
The is a switch to half the discharge amps when the are not multiple batteries in the comm chain

I just switched the inverter to "STD" and the Seplos V3 to "SMA_CAN" and lux power now reads batt capacity properly.

As far as I can see there is no lux setting for the V3.

 

[ChrisG]

I just switched the inverter to "STD" and the Seplos V3 to "SMA_CAN" and lux power now reads batt capacity properly.

As far as I can see there is no lux setting for the V3.

Looks like Pylon and Lux are #0?

 

[SwwilsSolarMan]

Looks like Pylon and Lux are #0?

With the inverter set to "PYLON" and the Seplos V3 on "PYLON_CAN" the capacity is not read properly and is like OPs issue.

 

[ChrisG]

With the inverter set to "PYLON" and the Seplos V3 on "PYLON_CAN" the capacity is not read properly and is like OPs issue.

I have EG4 6000xp (LuxPower) and was hoping that #0 would give all the info when I get my v3’s. Guess it would be the same problem so Inwould need to choose a protocol line SMA or GoodWe.

 

[SwwilsSolarMan]

Are you sure you are not reffering to the max discharge amps ?
The is a switch to half the discharge amps when the are not multiple batteries in the comm chain

Which switch is that in the V3? Mine reports roughly half the amps I metered but the calibration always times out.

 

[houseofancients]

Which switch is that in the V3? Mine reports roughly half the amps I metered but the calibration always times out.

V3 , can't remember, personally haven't touched V3 since initial testing and staying very clear from them

 

[ChrisG]

V3 , can't remember, personally haven't touched V3 since initial testing and staying very clear from them

@houseofancients why are you staying clear from the V3? Any other recommendation. I'm definitely NOT gong to new JKs

 

[swwils]

V3 , can't remember, personally haven't touched V3 since initial testing and staying very clear from them

I quite like my V3 once I got it setup.

Back to OP's discussion, I still cannot work out why the lux doesn't read the capacity properly when its set to "PYLON" battery type. Does the lux do that strange thing where pylon is appended to every message?

Can anyone else confirm the V3 doesn't have the Luxpowertek battery CAN protocol available in the BMS studio?

 

[ChrisG]

I quite like my V3 once I got it setup.

Back to OP's discussion, I still cannot work out why the lux doesn't read the capacity properly when its set to "PYLON" battery type. Does the lux do that strange thing where pylon is appended to every message?

Can anyone else confirm the V3 doesn't have the Luxpowertek battery CAN protocol available in the BMS studio?

I will say that I'm using @Sleeper85 's ESP32 code right now and until he added very specific LuxPower messages to CAN and split it off from Pylon, I did not have the proper battery configuration in the monitoring tools, but really didn't matter outside of a visual annoyance. Additionally when he added the the LuxPower spec, I started receiving all the battery cell and temp information in the monitoring tool.

 

[swwils]

I will say that I'm using @Sleeper85 's ESP32 code right now and until he added very specific LuxPower messages to CAN and split it off from Pylon, I did not have the proper battery configuration in the monitoring tools, but really didn't matter outside of a visual annoyance. Additionally when he added the the LuxPower spec, I started receiving all the battery cell and temp information in the monitoring tool.

View attachment 245151

Can you link me? It would be handy to have that as I run a home assistant integration on the inverter and it pulls date from there.

Oh wait, I am getting this data to the inverter using "STD" and "SMA_CAN", you can see exactly where I switched it over from pylon.

 

[ChrisG]

So looks like it's working? I wouldn't even worry about LuxPower protocol on v3, will try the same when mine arrive.

 

[swwils]

So looks like it's working? I wouldn't even worry about LuxPower protocol on v3, will try the same when mine arrive.

As far as I can tell fully working. I haven't tried error passing yet, but no reason it wouldn't work.

I haven't done a full discharge on this pack yet to make the SOC accurate.

 

[houseofancients]

@houseofancients why are you staying clear from the V3? Any other recommendation. I'm definitely NOT gong to new JKs

1. Got one of the first version, displayed some odd behavior in MOSFETs , SOC , didn't trust it
2. The active balancer wasn't integrated, and had at that point no way to set a proper start and stop voltage
3. Doesnt play with my 10c , not my 10e's ( and not about to replace 10 of them)
4.software at that point was.. well let's call it "less than good " in my mind
5. Petpieve.. came to find out they abandoned their engineers and the V3 are in fact bought in somewhere, thought that was a stupid move

Pretty much sums it up

 

[ChrisG]

As far as I can tell fully working. I haven't tried error passing yet, but no reason it wouldn't work.

I haven't done a full discharge on this pack yet to make the SOC accurate.

If you don’t mind, please provide an update when you can.

 

[swwils]

If you don’t mind, please provide an update when you can.

Will be some time, I had to assemble the pack before I could finish top balance, so now I will top balance manually and get the full charge discharge soc learn in.

Since the lux only uses SOC, I'm happy to use a super low overall pack alarm to stop the charge.

 

[swwils]

@ChrisG I have now started using this lux 6k + seplos V3 as my primary battery, so up and running.

I've encountered a few quirks but nothing too bad.

1. The active balancer is pretty slow, it's OK- But only when floating, the lux doesn't like doing floating you you need to adjust params for it specifically which kind of renders it moot if you have a decent top balance.

2. I had a "battery failure" Comms error with STD and SMA_CAN so I've switched to PYLON and Pylon_CAN which reports capacity wrong but I don't mind. I will investigate this more.

3. If you use the wrong firmware on the Seplos V3 charge/discharge amps is reported as exactly 1/2 of what it should be. The "numeral" method in the software does not work to identify which board you have, you must do it by eye.

4. I am using battery pack overvoltage as a 100% soc reset at 3.45 * 16v = 55.2v. Then using cell over voltages as appropriate. IF I need to balance I will just bump this to 56v for a few cycles to being the back in line passively.

5. At the low end I have it cell for the cell under voltage to trigger min soc.

6. Lux has a "hidden" charge voltage limit setting that must be set properly.

7. Lux has some "hidden" float logic that I am not bothering with in my application. But it essentially stops cycling.

Hope this helps. I will try contact seplos to support lux can in V3.

 

[ChrisG]

@ChrisG I have now started using this lux 6k + seplos V3 as my primary battery, so up and running.

I've encountered a few quirks but nothing too bad.

1. The active balancer is pretty slow, it's OK- But only when floating, the lux doesn't like doing floating you you need to adjust params for it specifically which kind of renders it moot if you have a decent top balance.

2. I had a "battery failure" Comms error with STD and SMA_CAN so I've switched to PYLON and Pylon_CAN which reports capacity wrong but I don't mind. I will investigate this more.

3. If you use the wrong firmware on the Seplos V3 charge/discharge amps is reported as exactly 1/2 of what it should be. The "numeral" method in the software does not work to identify which board you have, you must do it by eye.

4. I am using battery pack overvoltage as a 100% soc reset at 3.45 * 16v = 55.2v. Then using cell over voltages as appropriate. IF I need to balance I will just bump this to 56v for a few cycles to being the back in line passively.

5. At the low end I have it cell for the cell under voltage to trigger min soc.

6. Lux has a "hidden" charge voltage limit setting that must be set properly.

7. Lux has some "hidden" float logic that I am not bothering with in my application. But it essentially stops cycling.

Hope this helps. I will try contact seplos to support lux can in V3.

It does so help, thank you very much!!!! Does the inverter hold the charge at 55.2v for any time or does it stop charging right away when it hits 100%? I'm assuming it does based on your process to increase V for a few cycles.

 

[swwils]

It does so help, thank you very much!!!! Does the inverter hold the charge at 55.2v for any time or does it stop charging right away when it hits 100%? I'm assuming it does based on your process to increase V for a few cycles.

No it charges to the pack over volt limit, then sets 100% soc and stops charging. Which I've temporarily set a bit higher to give the cells a chance to balance above 3.45v untill they reach 3.5v as my manual top balance was only to within about 20mV.

I have no idea what the absorption or float logic is in the lux

The BMS automatically limits current I think at 99% soc, so this gives you a small amount of time to balance at the top end.

I just want to cycle between 2.9 - 3.3v but you might like a more aggressive profile.