x026A telegram

[PhillyGilly]

Hallo @norberts1 Danke fúr die fantastike EMS2 infos. I have an SM200 solar module and have been helping @Proddy to get the data from the EMS2 telegrams into MQTT. My SM200 sent this x026A telegram in test mode. B0 00 FF 00 02 6A 03 03 03 03 01 03 03 03 03 03 01 03 I agree with you that byte 10 represents Solar Pump but also believe that byte 4 is the cylinder selector valve VS2. Also the values 01/03/04 are test/off/on. This is further documented here: https://emsesp.github.io/docs/#/SM100 I hope this helps. mfG

[norberts1]

Hallo @PhillyGilly sorry for that late answer. I was busy with other stuff. Regarding that telegram-type: x026A I have only that Solar-Pump information at byte 10. In my system I'm using that Bosch/Junkers MS100 modul for solar-handling connected to that main-controller CW400. From that MS100 modul I get that 0x26A like: B0 00 FF 02 02 6A 03 00 00 03 03 00 00 00 03 5d -->> MesID 874 with offset 2. Keep in mind that I handle that telegrams as Message-ID's and not telegram-types (its's a bit easier to talk about) and also Junkers/Bosch internal handling is done like this. (that calculation of message-ID's is defined in my document). Any way, regarding that MesID 874 (FF xx 02 6A) I haven't more information and no MS200 modul. But that payload-decoding is independent of the used modul (MS100/200 or SM100/200), only the MessageID itself is important. The difference between MS200 and MS100 is only that MS200 can handle 2 solarcircuit's and is using 2 messageID's like:

1. Solar-system: 874 (FF xx 02 6A payload) and
2. Solar-system: 875 (FF xx 02 6B payload). Please check it out in your system, I can't. Perhaps your SM200 is also using 2 different device-ID's for that messages like: 0x30 and 0x31 but I'm not sure. But anyway, only the messageID is important and not the device-ID (modul) of the sender. You can test this with the EMS-ESP softwares using not the default 'ServiceKey:0x0B' but another one like :0x0D (Modem / Esaycom) and it works if you recompile that software. I did this check on my system already and I can run my hardware in parallel on the same heater-bus with a different device-ID :-) Hopefully a step forward. mfG

[PhillyGilly]

Hello @norberts1 thank you for your comments/suggestions. I have a Worcester Bosch Sense II controller which I believe is the same as your Bosch CW400 this is connected to MM200 and MS200 modules. The MM200 is essentially two MM100 devices in one box and has two device ID 0x28 and 0x29. It controls my two wW systems independently. The MS200 has only has one device ID 0x30. In comparison with the MS100 it can deal with more complex arrangements of roof panels and multiple wW storage devices, but in practice it is only controlling one hot glycol system. So the MS200 is not two MS100 together. My actual config is 1B as shown below, so that means I am using PS1, VS1, TS1, TS2 and TS5. Ms200 1BD(GHK).pdf I have the idea that the 0262 contains all the temperature infos (TS1 to TS8 and IS1, IS2) and the 026A contains all the pump and valve infos (PS1 to PS5, VS1, VS2, OS1, OS2). I'm not in a position to try the alternate service key now, and my system is currently off awaiting a valve replacement. I will run tests and post findings in March. mfG

[norberts1]

Hallo @PhillyGilly. Yes, that 0262 (MsgID 866) is assigned for that temperatur-values. More details you can find in my documentation in the HT3/doc-folder. See also this: Also that Solar-Options (B,C,D,G) are defined there, but I'm not sure they are fitting to your system. It should be 1B as you mentioned but I can't assign that senor-values: (PS1), VS1, TS1, TS2 and TS5 to that telegram. Perhaps you are able to do this. Did you already checked your modul MS200 regarding that hardware conntection of sensors? mfG

[norberts1]

@PhillyGilly it seems to be ok now, so I'll close this item.