Orion 2 BMS with Zombiverter

[Rustybkts]

I have followed all Damien's videos with relish but haven't seen anything regarding the integration of an Orion BMS or any BMS in the video's or the forum.
I note that there are three BMS choices in the parameters but no Orion.
Has anyone used an Orion with the Zombiverter as otherwise, I will need to wire a relay cutout in the charging circuit which is a bit heavy handed to say the least.

[LRBen]

I've used Orion BMS in a couple conversions with Zombie. What I usually do is to configure Orion to send the BMS messages in the same format as SIMP BMS then just use that as the BMS option.

[Rustybkts]

I've used Orion BMS in a couple conversions with Zombie. What I usually do is to configure Orion to send the BMS messages in the same format as SIMP BMS then just use that as the BMS option.

That's great.
I have used the CAN messaging a lot on my Evora conversion to enable the CAN instruments.
Where do I find the SIMP BMS message format as I'm new to the Openinverter site.

[LRBen]

That's great.
I have used the CAN messaging a lot on my Evora conversion to enable the CAN instruments.
Where do I find the SIMP BMS message format as I'm new to the Openinverter site.

They should be on the simp BMS manual here https://github.com/Tom-evnut/SimpBMS

I believe they are also the same as Victron canbus IDs.

[Rustybkts]

Hi LRBen,

Any chance of publishing the CAN messages between Orion and Zombiverter as I couldn't find them on the link above.
Cheers

[tom91]

Victron canbus IDs

You can turn on the victron CAN in the Orion software

[Rustybkts]

You can turn on the victron CAN in the Orion software

Hi, I am still having issues with Zombiverter reading the Orion with Victron inverter CAN comms enabled.
I note from the SimpBMS manual that many CAN frames when selecting Victron inverter are not used by SimpBMS and a few are missing or blank where data should be.

Is there a list anywhere of the frames the Zombi is looking for when SimpBMS is selected.

[tom91]

g issues with Zombiverter reading the Orion with Victron inverter CAN comms enabled.

Explain what are you trying to have it do?

Very little is coded in the Zombie in terms of BMS interactions.

What is handled by the Zombieverter and what is handled by the Orion 2.

[Rustybkts]

As the Leaf BMS is now not communicating with the Leaf PDM, I assume that the Zombie has taken the role over to control the Leaf charger.
I can see various BMS limits in the Zombie Spot Values which stay at zero and need a bit more info to fix the issue.
The Orion Victron Inverter CAN frames may not be complete for the Zombie hence why I mentioned if there is a list anywhere of the actual frames the Zombie requires when set to SimpBMS.

[tom91]

So the BMS can do the following:

Code: Select all

0x351
 chargeCurrentLimit = data[2] | (data[3] << 8);

0x373 
      int minCell = data[0] | (data[1] << 8);
      int maxCell = data[2] | (data[3] << 8);
      int minTemp = data[4] | (data[5] << 8);
      int maxTemp = data[6] | (data[7] << 8);

      minCellV = minCell / 1000.0;
      maxCellV = maxCell / 1000.0;
      minTempC = minTemp - 273;
      maxTempC = maxTemp - 273;

These are the messages from the BMS to the Zombie, the zombie then compares the cell voltages and temperatures to the BMS Params in the Zombie. If these are out of spec it will stop charging.

The chargecurrentlimit sent by the BMS is 0 it will also stop charging.

There are no dynamic interactions between the info from the BMS and what the zombie does, it only allows charging or it does not allow it.

The chargers will try follow the BMS Chargecurrentlimit and the Pwrspnt, which is written bij charge interfaces. The Nissan PDM limits itself by the CP signal.

Ofcourse you can also program all sorts of limits by using CAN SDO to map Params to CAN frames from the BMS. https://openinverter.org/wiki/CAN_communication

[Rustybkts]

So the BMS can do the following:

Code: Select all

0x351
 chargeCurrentLimit = data[2] | (data[3] << 8);

0x373 
      int minCell = data[0] | (data[1] << 8);
      int maxCell = data[2] | (data[3] << 8);
      int minTemp = data[4] | (data[5] << 8);
      int maxTemp = data[6] | (data[7] << 8);

      minCellV = minCell / 1000.0;
      maxCellV = maxCell / 1000.0;
      minTempC = minTemp - 273;
      maxTempC = maxTemp - 273;

These are the messages from the BMS to the Zombie, the zombie then compares the cell voltages and temperatures to the BMS Params in the Zombie. If these are out of spec it will stop charging.

The chargecurrentlimit sent by the BMS is 0 it will also stop charging.

There are no dynamic interactions between the info from the BMS and what the zombie does, it only allows charging or it does not allow it.

The chargers will try follow the BMS Chargecurrentlimit and the Pwrspnt, which is written bij charge interfaces. The Nissan PDM limits itself by the CP signal.

Ofcourse you can also program all sorts of limits by using CAN SDO to map Params to CAN frames from the BMS. https://openinverter.org/wiki/CAN_communication

Thanks for that answer. The Orion doesn't add frame 0x373 so I will add that in to the messages.
Thanks