Anybody experienced CRC errors with Solar Assistant ?

[EPicTony]

Using SA with rs485, everything works but when you change any data you get a CRC error. The data changes ok. I think the CRC error happens when SA tries to read the changed parameter. Also in my automation (which works fine) you see the CRC errors in the log as shown here: (it says it failed to set but that's not true the values did change correctly) Any ideas ? SA bug ?

 

[TM48]

Cyclic redundancy check errors are usually errors associated with the under lying communication protocol in this case rs485. I wouldn't think SA implements that layer. More likely SA is reading that from the inverter and maybe caused by an incompatibility between the usb to rs485 adapter and the inverter. Without be able to snoop on the comms it maybe tough to resolve. Are you using twisted pair wiring with one side grounded or is it a single pair? Also how long is the wiring?

 

[EPicTony]

Cyclic redundancy check errors are usually errors associated with the under lying communication protocol in this case rs485. I wouldn't think SA implements that layer. More likely SA is reading that from the inverter and maybe caused by an incompatibility between the usb to rs485 adapter and the inverter. Without be able to snoop on the comms it maybe tough to resolve. Are you using twisted pair wiring with one side grounded or is it a single pair? Also how long is the wiring?

2 wires twisted, 3 ft length using this:

 

[TM48]

2 wires twisted, 3 ft length using this: View attachment 286423

So you're using two twisted pairs as in four actual wires two of which are grounded?

Edit: BTW how did you connect it to the inverter?

 

[EPicTony]

So you're using two twisted pairs as in four actual wires two of which are grounded?

Edit: BTW how did you connect it to the inverter?

No just 2 wires per inverter, GND not connected. The wires go to CT1 rj45 connector. It's rock solid no CRC errors ever during reads. CRC error once per write (when I change a parameter, or an automation writes a new value).

 

[TM48]

No just 2 wires per inverter, GND not connected. The wires go to CT1 rj45 connector. It's rock solid no CRC errors ever during reads. CRC error once per write (when I change a parameter, or an automation writes a new value).

Is that the center RJ top row? The 18kpv is documented as CT1 but 6000xp isn't. So it's the same? If so that's good to know.

 

[EPicTony]

This one (red circle)

 

[marionw]

Depending on the protocol being used between SA and your Inverter, SA builds a "buffer" that contains a number of "bytes" (might be a register address, function code etc and will also include the data SA is changing in the inverter).

If SA is using a Modbus-RTU formatted command then the last byte or last two bytes depending on protocol are a CRC calculated by SA that represents the data in the buffer. Not all inverters use the exact same Modbus-RTU formatting and in some cases the CRC calculation does noit use the same formula.

If SA is using the Modbus-Ascii protocol then the last byte is generally an EOI byte (end of information) and the bytes before the EOI are the CRC as calculated by SA.

Different protocols oftentimes use different CRC calculation formulas. It could be that for your inverter and the protocol SA is using SA is incorrectly calculating CRC before sending the "buffer" to the Inverter. I assume that when SA sends the buffer to the Inverter SA waits for a response and may be receiving the CRC error from the Inverter and the inverter rejected the command because of the CRC error.

Does the Inverter actually set the value being sent by SA? It also may be that SA is validating the Inverter response and is incorrectly verifying the response CRC.

 

[EPicTony]

Yes, the Inverter actually sets the value being sent by SA. I have verified this multiple times.
You will never see the CRC error until SA WRITES a value. It reads stuff all day long without any CRC errors.
I think I should report this to the SA developers.

 

[Quattrohead]

Report it to SA, they will fix it.

 

[EPicTony]

Report it to SA, they will fix it.

I did report it. FYI the latest beta ( 2025-03-19) still has the CRC errors...........

 

[chicagoandy]

Today I upgraded Sol-Ark firmware and I'm getting CRC errors on my RS485 connection (to my custom ESPHom3 module and HomeAssistant), but my RS232 connection to Solar Assistant is working fine.

So there might be something going on with the latest Sol-Ark firmware.

 

[chicagoandy]

Report it to SA, they will fix it.

Do you have a good path to do that? My experience with their support techs is a simple "oh, we don't support solar-assistant".

 

[Fisherguy66]

Do you have a good path to do that? My experience with their support techs is a simple "oh, we don't support solar-assistant".

I've had good responses from SA when I emailed them questions. Usually its pre-screened then if it warrants Pierre will respond otherwise the front end staff will try to answer general questions.

He did say there will probably be bugs in this new code, just give them time to iron them out once reported.

 

[EPicTony]

CRC errors no more... From SA support:"
Hello Anthony,

With Luxpower CRC error, the setting change does go through. The next beta version will show ''Saved'' instead of ''CRC error'' as it understands the response from the inverter.

Kind Regards,"

 

[EPicTony]

New beta 2025-03-28 fixes crc errors. Yippee !