@sbf said in SBFspot funktioniert nicht - Communication Error:
I've never heard of bricked inverters.
Now that I have more info I doubt if we have to spent more time to make SBFspot compatible with this old version of the protocol. If I have a trace log I can see if it possible in a short time frame.
But I took a closer look to the data and have some questions: In the output it looks like
each block occurs twice (when calling with -d5).
The first block is the raw data, the second is the unescaped version: when the data contains 0x7E it is converted to 0x7D + ...
0x7E is start/stop byte of packet (BT only)
What does getPacket(2) or getPacket(5) mean ?
To me it looks like byte 16 is the command - right ?
But what does this command mean ?
cmd is indeed at pos 16. If the meaning is known it is commented in the source code. The SMADATA2+ protocol is reverse engineered and a lot of its data is unknown.