SOREL CAN BUS Interface (SCBI) #20598
-
Sorel is a manufacturer of difference controllers for heating and solar systems that use CAN Bus protocol It would be possible to adapt this driver (xsns_87_mcp2515.ino) so the Sorela library showed bellow could be used to translate Sorel CAN Bus messages? Kind regards |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 6 replies
-
the sml driver supports CAN reading and writing on an ESP32 native can interface. there is an example in the docs |
Beta Was this translation helpful? Give feedback.
-
So, I have built a tasmota32 firmware with smart meter interface feature and made the following set-up: ESP32 + CAN transceiver + Sorel controller Configuration module tasmota is: GPIO14(CLK), GPIO13(MOSI) and GPIO12(MISO) Scripting to get the values from the solar controller overwhelmed me, should be something like: `>D
#` I found also this script for the same solar controller. May be it help to get the reads. I appreciate any light. |
Beta Was this translation helpful? Give feedback.
-
Thank you. I have already purchased the item. I'll come back when I have the correct hardware setup. |
Beta Was this translation helpful? Give feedback.
-
Hi gemu, I have already received the can transceiver, I have tried the following script and executed in the console: sensor53 d1, without success. I don´t receive any telegram in the console.
|
Beta Was this translation helpful? Give feedback.
-
you must compile with additional option |
Beta Was this translation helpful? Give feedback.
-
Thank you. Now I can read the telegrams in the console :
|
Beta Was this translation helpful? Give feedback.
-
How I can define the Meter Metrics: I get the following dump in the console:
I think that line: I apreciate any help |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Summary: Compile firmware with If decoding works you should see a stream of CAN telegrams with regular updates at least every 20sec. Script:
|
Beta Was this translation helpful? Give feedback.
normally the specs of your meter should say how the telegrams are composed:
10012480 is the ID of the telegram, the 05 is length of payload.
now you have 5 bytes payload:
in case your payload is a a word with 0802 (08020000)
you define a decoder with e.g unsigned word (defined with UUuu)
1,100124800500uuUU@10,Temp S1,C,tmpS1,1
see the docs about the decoder options
you should know the byte order and format of your payload
10 is the scaling factor from your sorel docs