I am setting up a SMA Sunny Island 6048us as a grid tied back up with Sunny boy, Data Manager M, EVE 105ah Lifepo4 16s test bank (EVE 280k x64 Main Bank), Midnite Solar Classic and Orion bms. I have the system up and I hit a few brick walls along the way and would like some help understanding what I did wrong.
Well assuming equipment from the same manufacturer would be able to send and receive data was asinine, so I will start from the top. I found the documents for the 6.0H can interface on google and SI wants the can to transmit on 11-bit identifiers: 0x351, 0x355, and 0x356 for battery data and 0x35A, 0x35B, 0x35E, and 0x35F for alarms, warnings, data on the bms-battery. I found that SI will run with data just on 0x355, it really just wants SOC and it will use its default settings for rest of the settings from my tests. I never kept the system up long with data just on 355 but it was nice for testing . Here is a snapshot of live data over the CAN network, I am only transmitting on 0x351, 0x355, and 0x356.
I used REC's bms guide to convert over the Orion defaults to what the SI wants i.e SOC from my Orion was sending over in 1 byte form and Orion wants 2 byte form so I have to divide by 2 or it wants 1v reading and Orion is sending .1 so X10 and so on. After getting all the conversions done I powered up the system and most things are communicating and the system seems stable. 12 hours later the first error Lobatmon 3, so what happened is my SI did not get SOC and it defaulted to 0% which shuts down the inverter then it turns on in 1 second. After looking into the issue I found that the soc randomly in not being received....
So the REC manual says "CAN messages are sent each measuring cycle with 100 ms interval between" The SI version of the REC bms says "CAN messages are send every 250ms" and the SI manual says "Values to Sunny Island must not be sent out faster than every 200msec (inhibit time)" Thanks for the clear answer guys........... Victron equipment uses the same CAN messages 0x351, 0x355, and 0x356 with a few changes in readings but sends every 100ms. So I started playing with times and the best I can do is starting at 250ms and spacing the three messages 250ms,350ms,and 450ms. The SI will still give me a error lobatmon 1 but would not shut down the inverter. Has anyone here gotten the SI to receive all custom can messages with no errors? Or how I would trigger lobatmon if its not the SOC reading. What I am guessing is the SI wants the messages in a certain order and randomly within the 60sec window of the SI monitoring 0x355 the SOC is being rejected but idk. I also got a Victron Smart Shunt because I knew if I failed with the Orion I could convert over SOC with the shunt to the SI using raspberry pi method and may still explore this rout for just SOC.
I hope someone here has played with the CAN on the SI and can help me out, till then just trial and error. I have only had a few days to play with the system and will post more.
Well assuming equipment from the same manufacturer would be able to send and receive data was asinine, so I will start from the top. I found the documents for the 6.0H can interface on google and SI wants the can to transmit on 11-bit identifiers: 0x351, 0x355, and 0x356 for battery data and 0x35A, 0x35B, 0x35E, and 0x35F for alarms, warnings, data on the bms-battery. I found that SI will run with data just on 0x355, it really just wants SOC and it will use its default settings for rest of the settings from my tests. I never kept the system up long with data just on 355 but it was nice for testing . Here is a snapshot of live data over the CAN network, I am only transmitting on 0x351, 0x355, and 0x356.
I used REC's bms guide to convert over the Orion defaults to what the SI wants i.e SOC from my Orion was sending over in 1 byte form and Orion wants 2 byte form so I have to divide by 2 or it wants 1v reading and Orion is sending .1 so X10 and so on. After getting all the conversions done I powered up the system and most things are communicating and the system seems stable. 12 hours later the first error Lobatmon 3, so what happened is my SI did not get SOC and it defaulted to 0% which shuts down the inverter then it turns on in 1 second. After looking into the issue I found that the soc randomly in not being received....
So the REC manual says "CAN messages are sent each measuring cycle with 100 ms interval between" The SI version of the REC bms says "CAN messages are send every 250ms" and the SI manual says "Values to Sunny Island must not be sent out faster than every 200msec (inhibit time)" Thanks for the clear answer guys........... Victron equipment uses the same CAN messages 0x351, 0x355, and 0x356 with a few changes in readings but sends every 100ms. So I started playing with times and the best I can do is starting at 250ms and spacing the three messages 250ms,350ms,and 450ms. The SI will still give me a error lobatmon 1 but would not shut down the inverter. Has anyone here gotten the SI to receive all custom can messages with no errors? Or how I would trigger lobatmon if its not the SOC reading. What I am guessing is the SI wants the messages in a certain order and randomly within the 60sec window of the SI monitoring 0x355 the SOC is being rejected but idk. I also got a Victron Smart Shunt because I knew if I failed with the Orion I could convert over SOC with the shunt to the SI using raspberry pi method and may still explore this rout for just SOC.
I hope someone here has played with the CAN on the SI and can help me out, till then just trial and error. I have only had a few days to play with the system and will post more.
Last edited:
