Page 6 of 20
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sat Sep 28, 2013 1:18 pm
by hvxl
You can easily check for yourself what happens by simply disconnecting your thermostat. But here are the gory details: The gateway will repeatedly send the following sequence of messages:
- MsgID 0: Master and Slave Status flags
- MsgID 25: Boiler flow water temperature
- MsgID 1: Control Setpoint
- UserDefined
- MsgID 17: Relative Modulation Level
- MsgID 27: Outside temperature
- MsgID 28: Return water temperature
- MsgID 14: Maximum relative modulation level setting
- UserDefined
- MsgID 0: Master and Slave Status flags
- MsgID 25: Boiler flow water temperature
- MsgID 1: Control Setpoint
- MsgID 56: DHW Setpoint
- MsgID 57: Max CH water Setpoint
- UserDefined
- MsgID 18: Water pressure in CH circuit
The "UserDefined" slots are filled from the list of alternatives. If the gateway learns (or was told via the UI command) that some of the other messages are not supported by the boiler, it will fill those slots with messages from the list of alternatives as well. If the list of alternatives is empty, it sends MsgID 0.
Note: This list is not set in stone and may change in the future.
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sat Sep 28, 2013 2:59 pm
by sappien
Since I've flashed version 4 I don't get the Return water temperature.. (Remeha Calenta iSense)
00000000/00000000,20.00,00000011/00000011,100.00,0/0,19.00,0.00,1.10,20.70,29.80,0.00,17.80,0.00,65/40,66/20,50.00,30.00,4328,5264,2064,3520,618,684,5404,113
Bug? Or did I forget something?
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sat Sep 28, 2013 6:01 pm
by hvxl
The iSense doesn't request the return water temperature. To obtain that information from the boiler you have to add MsgID 28 to the list of alternatives (AA=28). You probably did that in the past, but that setting is lost when you flash the firmware.
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sat Sep 28, 2013 6:24 pm
by sappien
that rings a bell

Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sun Sep 29, 2013 7:22 pm
by Dickuk
hvxl wrote:You can easily check for yourself what happens by simply disconnecting your thermostat. But here are the gory details: The gateway will repeatedly send the following sequence of messages:
- MsgID 18: Water pressure in CH circuit
- MsgID 0: Master and Slave Status flags
- MsgID 25: Boiler flow water temperature
- MsgID 1: Control Setpoint
- UserDefined
- MsgID 17: Relative Modulation Level
- MsgID 27: Outside temperature
- MsgID 28: Return water temperature
- MsgID 14: Maximum relative modulation level setting
- UserDefined
- MsgID 0: Master and Slave Status flags
- MsgID 25: Boiler flow water temperature
- MsgID 1: Control Setpoint
- MsgID 56: DHW Setpoint
- MsgID 57: Max CH water Setpoint
- UserDefined
The "UserDefined" slots are filled from the list of alternatives. If the gateway learns (or was told via the UI command) that some of the other messages are not supported by the boiler, it will fill those slots with messages from the list of alternatives as well. If the list of alternatives is empty, it sends MsgID 0.
Note: This list is not set in stone and may change in the future.
That's great, thanks.
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Wed Oct 09, 2013 8:13 pm
by nlrb
Hi Schelte,
Just tried firmware version 4.0a9, but after the following sequence of events it doesn't respond to commands anymore. Last command it responds to is LA=X. After that no response on the command LB=R. (Note that my code was written for FW 3.4, so it doesn't recognize the responses and prints an error - you can ignore that).
Code: Select all
OTG: Sent command PR=A
OTG: Incoming data = PR: A=OpenTherm Gateway 4.0a9
OTG: otgHandleVersion cmd = PR: A=OpenTherm Gateway 4.0a9, version = 4.0a9
OTG: Sent command PR=M
OTG: Sent command PR=L
OTG: Sent command PR=T
OTG: Sent command PR=V
OTG: Sent command PR=W
OTG: Incoming data = PR: M=G
OTG: Error for cmd: GW; expected [0|1] but got PR: M=G
OTG: Incoming data = PR: L=FXOMPC
OTG: Sent command LA=X
OTG: Sent command LB=R
OTG: Sent command LC=O
OTG: Sent command LD=E
OTG: Incoming data = PR: T=1
OTG: Sent command IT=0
OTG: Incoming data = PR: V=3
OTG: Incoming data = PR: W=A
OTG: Incoming data = LA: X
OTG: Error: expected OK but got LA: X
OTG: Incoming data = T80000200
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Wed Oct 09, 2013 8:52 pm
by hvxl
I don't know exactly what your program does. It looks like it bombards the gateway with commands without waiting for a response. Don't do that. The gateway is not designed to cope with that. If it worked with 3.4, that was just luck. Of course the gateway should not hang if you do and I will look into it, but you may still find that some commands could be ignored because the gateway was not ready yet.
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Wed Oct 09, 2013 9:40 pm
by nlrb
Clear. It indeed worked with 3.4. But I'll implement a queue at the sending side.
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Thu Oct 10, 2013 9:58 pm
by hvxl
I managed to reproduce the problem you described. The problem was that the LED setting had to be written to EEPROM. That takes around 4 milliseconds. During that time the code didn't service the serial port. However, you continued to send more data which caused a buffer overrun. Subsequently the code failed to detect and handle that situation. So from that point onward the gateway would not receive any serial data anymore.
I checked the code of firmware 3.4 and confirmed that it would have the same problem. You say your script worked with 3.4. My guess is you only used it when the LEDs were already configured as you wanted. In that case the code detects no change is necessary and cleverly skips the EEPROM write operation.
Your method intrigued me, and now that responses can more easily be linked to their commands it makes sense to support it. So I started calculating: An EEPROM write takes 4 milliseconds. The shortest serial command is 4 characters + CR. Each character has a start and stop bit, adding up to a minimum of 50 bits for a command. At 9600 baud that takes 5.2 milliseconds. That means that the serial transmission of a possible next command takes long enough for the EEPROM write to complete.
So rather than just cleaning up when an overrun occurs, I decided it might be better to keep an eye on the serial interface while waiting for the EEPROM write to complete. As a result your bombardment of serial commands can now be handled by the gateway. The only time you need to allow the gateway some time is when you change the setback temperature. For that setting it may need to write 2 bytes to EEPROM, which takes 8 milliseconds.
But even if you immediately follow the SB command with another command, it will not hang up the serial interface. The command is just ignored, or leads to an error message. Sending a few LF characters after an SB command should provide the delay necessary for the gateway do its thing. Linefeeds are ignored by the gateway.
I can't think of any scenario that might still cause an overrun on the serial interface. But if it does happen, the code will now clean it up correctly.
These fixes are available in
firmware 4.0a10.
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Fri Oct 11, 2013 9:01 pm
by nlrb
hvxl wrote:I checked the code of firmware 3.4 and confirmed that it would have the same problem. You say your script worked with 3.4. My guess is you only used it when the LEDs were already configured as you wanted. In that case the code detects no change is necessary and cleverly skips the EEPROM write operation.
It worked with 3.4, but also my code checks the LED setting first before programming, as I didn't want to waste write cycles. Good to know that the FW already checks. But since I check, the LED write commands were only issued once and it worked in that case. But timing on the sender side could have been different (thread might have had some interruptions).
hvxl wrote:I can't think of any scenario that might still cause an overrun on the serial interface. But if it does happen, the code will now clean it up correctly.[/url]
Thanks for fixing. I've implemented a write queue anyway as I want the code to work with FW 3.4 as well.
Just tried this version and noticed that still some messages are prefixed with a counter.
Code: Select all
20:50:24.343355 R80750000 Read-Data CH pump starts: 0
20:50:24.492523 B70750000 Unk-DataId CH pump starts: 0
20:50:24.494418 117AC0090000
20:50:24.862522 T80190000 Read-Data Boiler water temperature: 0.00
20:50:25.010853 BC0193C80 Read-Ack Boiler water temperature: 60.50
20:50:25.410116 T80640000 Read-Data Remote override function: 00000000
20:50:25.411552 R80760000 Read-Data DHW pump/valve starts: 0
20:50:25.565124 B70760000 Unk-DataId DHW pump/valve starts: 0
20:50:25.566631 118A40640000
20:50:25.929178 T80000200 Read-Data Status: 00000010 00000000
20:50:26.076831 B40000200 Read-Ack Status: 00000010 00000000
20:50:26.462146 T80000200 Read-Data Status: 00000010 00000000
20:50:26.610259 B40000200 Read-Ack Status: 00000010 00000000
20:50:26.995309 T80000200 Read-Data Status: 00000010 00000000
20:50:27.150159 B40000200 Read-Ack Status: 00000010 00000000
20:50:27.528430 T80000200 Read-Data Status: 00000010 00000000
20:50:27.676016 B40000200 Read-Ack Status: 00000010 00000000
20:50:28.061934 T80000200 Read-Data Status: 00000010 00000000
20:50:28.209815 B40000200 Read-Ack Status: 00000010 00000000
20:50:28.594740 T10010A00 Write-Data Control setpoint: 10.00
20:50:28.749823 BD0010A00 Write-Ack Control setpoint: 10.00
20:50:29.139441 T90101500 Write-Data Room setpoint: 21.00
20:50:29.141287 R00770000 Read-Data DHW burner starts: 0
20:50:29.289846 BF0770000 Unk-DataId DHW burner starts: 0
20:50:29.291556 119A50101500
20:50:29.661147 T80190000 Read-Data Boiler water temperature: 0.00
20:50:29.808778 BC0193C80 Read-Ack Boiler water temperature: 60.50
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Fri Oct 11, 2013 9:24 pm
by hvxl
nlrb wrote:It worked with 3.4, but also my code checks the LED setting first before programming, as I didn't want to waste write cycles.
You may want to check your code then. Your log shows the LEDs are reported as FXOMPC. So LED C is set to O, yet your code still issues a LC=O command.
nlrb wrote:Just tried this version and noticed that still some messages are prefixed with a counter.
You mention that as if it is something I should know about. I don't. Obviously it's hard for me to fix problems I don't know about. So please report these issues when you see them. It looks like these are the default alternatives that your boiler doesn't support. They are printed as the gateway deletes them from the list. So it should stop pretty quickly.
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Fri Oct 11, 2013 9:43 pm
by nlrb
hvxl wrote:You may want to check your code then. Your log shows the LEDs are reported as FXOMPC. So LED C is set to O, yet your code still issues a LC=O command.
That was because in FW 3.4 the LED status was 4 characters and in FW 4.0 it is 6. So the strings didn't match and it executed a write.
nlrb wrote:You mention that as if it is something I should know about. I don't. Obviously it's hard for me to fix problems I don't know about. So please report these issues when you see them. It looks like these are the default alternatives that your boiler doesn't support. They are printed as the gateway deletes them from the list. So it should stop pretty quickly.
I thought that someone had already reported that (read that somewhere), but apparently I was mistaken. It indeed looks like the non supported alternatives.
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Fri Oct 11, 2013 10:39 pm
by hvxl
nlrb wrote:I thought that someone had already reported that (read that somewhere), but apparently I was mistaken. It indeed looks like the non supported alternatives.
Someone reported seeing outside temperatures. Although somewhat related, this is something else and requires its own fix.
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sun Oct 13, 2013 6:01 pm
by nlrb
I have the problem with 4.0a10 that the Max. relative modulation level gets set without using the MM command. The DD command seems to act as the MM command.
Code: Select all
17:51:29.250752 T9018164A Write-Data Room temperature: 22.29
17:51:29.399672 B5018164A Write-Ack Room temperature: 22.29
17:51:29.602571 AA: 13
17:51:29.782649 T00000300 Read-Data Status: 00000011 00000000
17:51:29.938138 BC000030A Read-Ack Status: 00000011 00001010
17:51:30.317180 T00000300 Read-Data Status: 00000011 00000000
17:51:30.463815 BC000030A Read-Ack Status: 00000011 00001010
17:51:30.847333 T00000300 Read-Data Status: 00000011 00000000
17:51:30.997566 BC000030A Read-Ack Status: 00000011 00001010
17:51:31.382513 T00000300 Read-Data Status: 00000011 00000000
17:51:31.539016 BC000030A Read-Ack Status: 00000011 00001010
17:51:31.916714 T00000300 Read-Data Status: 00000011 00000000
17:51:32.062621 BC000030A Read-Ack Status: 00000011 00001010
17:51:32.447964 T00000300 Read-Data Status: 00000011 00000000
17:51:32.596391 BC000030A Read-Ack Status: 00000011 00001010
17:51:32.980015 T90012C00 Write-Data Control setpoint: 44.00
17:51:33.136036 B50012C00 Write-Ack Control setpoint: 44.00
17:51:33.514835 T900E6400 Write-Data Maximum relative modulation level: 100.00
17:51:33.661871 BF00E6400 Unk-DataId Maximum relative modulation level: 100.00
17:51:34.044239 T80190000 Read-Data Boiler water temperature: 0.00
17:51:34.195537 BC0193080 Read-Ack Boiler water temperature: 48.50
17:51:34.580357 T00000300 Read-Data Status: 00000011 00000000
17:51:34.735415 BC000030A Read-Ack Status: 00000011 00001010
17:51:35.114772 T00000300 Read-Data Status: 00000011 00000000
17:51:35.260827 BC000030A Read-Ack Status: 00000011 00001010
17:51:35.646015 T00000300 Read-Data Status: 00000011 00000000
17:51:35.794460 BC000030A Read-Ack Status: 00000011 00001010
17:51:36.180173 T00000300 Read-Data Status: 00000011 00000000
17:51:36.324754 BC000030A Read-Ack Status: 00000011 00001010
17:51:36.715077 T00000300 Read-Data Status: 00000011 00000000
17:51:36.858656 BC000030A Read-Ack Status: 00000011 00001010
17:51:37.249403 T00000300 Read-Data Status: 00000011 00000000
17:51:37.393390 BC000030A Read-Ack Status: 00000011 00001010
17:51:37.784767 T00050000 Read-Data Application-specific flags: 00000000 0
17:51:37.932941 BC0050000 Read-Ack Application-specific flags: 00000000 0
17:51:38.316569 T90012C00 Write-Data Control setpoint: 44.00
17:51:38.472439 B50012C00 Write-Ack Control setpoint: 44.00
17:51:38.851122 T80190000 Read-Data Boiler water temperature: 0.00
17:51:38.998430 BC0193080 Read-Ack Boiler water temperature: 48.50
17:51:39.383800 T00000300 Read-Data Status: 00000011 00000000
17:51:39.531687 BC000030A Read-Ack Status: 00000011 00001010
17:51:39.916436 T00000300 Read-Data Status: 00000011 00000000
17:51:40.071347 BC000030A Read-Ack Status: 00000011 00001010
17:51:40.451080 T00000300 Read-Data Status: 00000011 00000000
17:51:40.596954 BC000030A Read-Ack Status: 00000011 00001010
17:51:40.982134 T00000300 Read-Data Status: 00000011 00000000
17:51:41.130246 BC000030A Read-Ack Status: 00000011 00001010
17:51:41.514713 T00000300 Read-Data Status: 00000011 00000000
17:51:41.670180 BC000030A Read-Ack Status: 00000011 00001010
17:51:42.049269 T80381400 Read-Data DHW setpoint: 20.00
17:51:42.195272 BC038001A Read-Ack DHW setpoint: 0.10
17:51:42.579635 T00395000 Read-Data Max CH water setpoint: 80.00
17:51:42.732936 BC03950FF Read-Ack Max CH water setpoint: 81.00
17:51:43.116114 T00395000 Read-Data Max CH water setpoint: 80.00
17:51:43.269485 BC03950FF Read-Ack Max CH water setpoint: 81.00
17:51:43.664909 T00395000 Read-Data Max CH water setpoint: 80.00
17:51:43.808224 BC0395000 Read-Ack Max CH water setpoint: 80.00
17:51:44.199266 T90012C00 Write-Data Control setpoint: 44.00
17:51:44.352181 B50012C00 Write-Ack Control setpoint: 44.00
17:51:44.734126 T80190000 Read-Data Boiler water temperature: 0.00
17:51:44.890132 BC0193080 Read-Ack Boiler water temperature: 48.50
17:51:45.267593 T00000300 Read-Data Status: 00000011 00000000
17:51:45.413806 BC000030A Read-Ack Status: 00000011 00001010
17:51:45.799718 T00000300 Read-Data Status: 00000011 00000000
17:51:45.947101 BC000030A Read-Ack Status: 00000011 00001010
17:51:46.336764 T00110000 Read-Data Relative modulation level: 0.00
17:51:46.487079 BC0112E00 Read-Ack Relative modulation level: 46.00
17:51:46.864683 T00000300 Read-Data Status: 00000011 00000000
17:51:47.011710 BC000030A Read-Ack Status: 00000011 00001010
17:51:47.397467 T00000300 Read-Data Status: 00000011 00000000
17:51:47.536274 BC000030A Read-Ack Status: 00000011 00001010
17:51:47.933773 T90012C00 Write-Data Control setpoint: 44.00
17:51:48.085138 B50012C00 Write-Ack Control setpoint: 44.00
17:51:48.464640 T00000300 Read-Data Status: 00000011 00000000
17:51:48.610963 BC000030A Read-Ack Status: 00000011 00001010
17:51:48.995297 T80190000 Read-Data Boiler water temperature: 0.00
17:51:49.144604 BC01931FF Read-Ack Boiler water temperature: 50.00
17:51:49.530178 T00000300 Read-Data Status: 00000011 00000000
17:51:49.683878 BC000030A Read-Ack Status: 00000011 00001010
17:51:50.073657 T00120000 Read-Data CH water pressure: 0.00
17:51:50.076393 R800D0000 Read-Data Fault buffer entry: 0 0
17:51:50.221803 B400D0000 Read-Ack Fault buffer entry: 0 0
17:51:50.225097 AF0120000 Unk-DataId CH water pressure: 0.00
17:51:50.595541 T00000300 Read-Data Status: 00000011 00000000
17:51:50.743404 BC000030A Read-Ack Status: 00000011 00001010
17:51:51.129721 T00000300 Read-Data Status: 00000011 00000000
17:51:51.274016 BC000030A Read-Ack Status: 00000011 00001010
17:51:51.664644 T00000300 Read-Data Status: 00000011 00000000
17:51:51.808475 BC000030A Read-Ack Status: 00000011 00001010
17:51:52.199233 T00000300 Read-Data Status: 00000011 00000000
17:51:52.342437 BC000030A Read-Ack Status: 00000011 00001010
17:51:52.733667 T90012C00 Write-Data Control setpoint: 44.00
17:51:52.882160 B50012C00 Write-Ack Control setpoint: 44.00
17:51:53.266695 T00000300 Read-Data Status: 00000011 00000000
17:51:53.421878 BC000030A Read-Ack Status: 00000011 00001010
17:51:53.800906 T80190000 Read-Data Boiler water temperature: 0.00
17:51:53.947652 BC0193100 Read-Ack Boiler water temperature: 49.00
17:51:54.332105 T00000300 Read-Data Status: 00000011 00000000
17:51:54.481091 BC000030A Read-Ack Status: 00000011 00001010
17:51:54.866717 T00000300 Read-Data Status: 00000011 00000000
17:51:55.020818 BC000030A Read-Ack Status: 00000011 00001010
17:51:55.399120 T00000300 Read-Data Status: 00000011 00000000
17:51:55.546727 BC000030A Read-Ack Status: 00000011 00001010
17:51:55.931651 T00000300 Read-Data Status: 00000011 00000000
17:51:56.080012 BC000030A Read-Ack Status: 00000011 00001010
17:51:56.464500 T00000300 Read-Data Status: 00000011 00000000
17:51:56.619772 BC000030A Read-Ack Status: 00000011 00001010
17:51:56.999599 T00000300 Read-Data Status: 00000011 00000000
17:51:57.145834 BC000030A Read-Ack Status: 00000011 00001010
17:51:57.530248 T00000300 Read-Data Status: 00000011 00000000
17:51:57.679559 BC000030A Read-Ack Status: 00000011 00001010
17:51:58.064658 T90012C00 Write-Data Control setpoint: 44.00
17:51:58.219251 B50012C00 Write-Ack Control setpoint: 44.00
17:51:58.597680 T00000300 Read-Data Status: 00000011 00000000
17:51:58.739041 BC000030A Read-Ack Status: 00000011 00001010
17:51:59.147402 T80190000 Read-Data Boiler water temperature: 0.00
17:51:59.299299 B40193180 Read-Ack Boiler water temperature: 49.50
17:51:59.679091 T00000300 Read-Data Status: 00000011 00000000
17:51:59.824962 BC000030A Read-Ack Status: 00000011 00001010
17:52:00.209316 T00000300 Read-Data Status: 00000011 00000000
17:52:00.358588 BC000030A Read-Ack Status: 00000011 00001010
17:52:00.743486 T00000300 Read-Data Status: 00000011 00000000
17:52:00.889711 BC000030A Read-Ack Status: 00000011 00001010
17:52:01.274870 T00000300 Read-Data Status: 00000011 00000000
17:52:01.418086 BC000030A Read-Ack Status: 00000011 00001010
17:52:01.809495 T00000300 Read-Data Status: 00000011 00000000
17:52:01.958277 BC000030A Read-Ack Status: 00000011 00001010
17:52:02.344795 T00000300 Read-Data Status: 00000011 00000000
17:52:02.488540 BC000030A Read-Ack Status: 00000011 00001010
17:52:02.878274 T90012C00 Write-Data Control setpoint: 44.00
17:52:03.023703 B50012C00 Write-Ack Control setpoint: 44.00
17:52:03.415285 T801C0000 Read-Data Return water temperature: 0.00
17:52:03.557783 BC01C0200 Read-Ack Return water temperature: 2.00
17:52:03.947724 T80190000 Read-Data Boiler water temperature: 0.00
17:52:04.097625 B40193180 Read-Ack Boiler water temperature: 49.50
17:52:04.482872 T00000300 Read-Data Status: 00000011 00000000
17:52:04.637284 BC000030A Read-Ack Status: 00000011 00001010
17:52:05.016367 T00000300 Read-Data Status: 00000011 00000000
17:52:05.157372 BC000030A Read-Ack Status: 00000011 00001010
17:52:05.548331 T00000300 Read-Data Status: 00000011 00000000
17:52:05.687753 BC000030A Read-Ack Status: 00000011 00001010
17:52:06.079036 T00000300 Read-Data Status: 00000011 00000000
17:52:06.222815 BC000030A Read-Ack Status: 00000011 00001010
17:52:06.616343 T00000300 Read-Data Status: 00000011 00000000
17:52:06.762942 BC000030A Read-Ack Status: 00000011 00001010
17:52:07.148391 T00000300 Read-Data Status: 00000011 00000000
17:52:07.288017 BC000030A Read-Ack Status: 00000011 00001010
17:52:07.679688 T10012B00 Write-Data Control setpoint: 43.00
17:52:07.822494 BD0012B00 Write-Ack Control setpoint: 43.00
17:52:08.213526 T001B0000 Read-Data Outside temperature: 0.00
17:52:08.368048 B601B0000 Data-Inv Outside temperature: 0.00
17:52:08.370907 A401B0980 Read-Ack Outside temperature: 9.50
17:52:08.748031 T80190000 Read-Data Boiler water temperature: 0.00
17:52:08.896335 B40193180 Read-Ack Boiler water temperature: 49.50
17:52:09.281190 T00000300 Read-Data Status: 00000011 00000000
17:52:09.426978 BC000030A Read-Ack Status: 00000011 00001010
17:52:09.812012 T00000300 Read-Data Status: 00000011 00000000
17:52:09.955944 BC000030A Read-Ack Status: 00000011 00001010
17:52:10.346596 T00000300 Read-Data Status: 00000011 00000000
17:52:10.486831 BC000030A Read-Ack Status: 00000011 00001010
17:52:10.877003 T00000300 Read-Data Status: 00000011 00000000
17:52:11.021950 BC000030A Read-Ack Status: 00000011 00001010
17:52:11.412124 T00000300 Read-Data Status: 00000011 00000000
17:52:11.556239 BC000030A Read-Ack Status: 00000011 00001010
17:52:11.946931 T00000300 Read-Data Status: 00000011 00000000
17:52:12.086284 BC000030A Read-Ack Status: 00000011 00001010
17:52:12.477510 T00000300 Read-Data Status: 00000011 00000000
17:52:12.621506 BC000030A Read-Ack Status: 00000011 00001010
17:52:13.011843 T10012B00 Write-Data Control setpoint: 43.00
17:52:13.155353 BD0012B00 Write-Ack Control setpoint: 43.00
17:52:13.558044 T801A0000 Read-Data DHW temperature: 0.00
17:52:13.561537 R00110000 Read-Data Relative modulation level: 0.00
17:52:13.697557 BC0113300 Read-Ack Relative modulation level: 51.00
17:52:13.700433 A701A0000 Unk-DataId DHW temperature: 0.00
17:52:14.108111 T80190000 Read-Data Boiler water temperature: 0.00
17:52:14.255023 BC01932FF Read-Ack Boiler water temperature: 51.00
17:52:14.639885 T00000300 Read-Data Status: 00000011 00000000
17:52:14.785788 BC000030A Read-Ack Status: 00000011 00001010
17:52:15.170443 T00000300 Read-Data Status: 00000011 00000000
17:52:15.314847 BC000030A Read-Ack Status: 00000011 00001010
17:52:15.704481 T00000300 Read-Data Status: 00000011 00000000
17:52:15.854851 BC000030A Read-Ack Status: 00000011 00001010
17:52:16.239489 T00000300 Read-Data Status: 00000011 00000000
17:52:16.395473 BC000030A Read-Ack Status: 00000011 00001010
17:52:16.774364 T00000300 Read-Data Status: 00000011 00000000
17:52:16.920402 BC000030A Read-Ack Status: 00000011 00001010
17:52:17.305130 T00000300 Read-Data Status: 00000011 00000000
17:52:17.454502 BC000030A Read-Ack Status: 00000011 00001010
17:52:17.839505 T10012B00 Write-Data Control setpoint: 43.00
17:52:17.994265 BD0012B00 Write-Ack Control setpoint: 43.00
17:52:18.383276 T00090000 Read-Data Remote override room setpoint: 0.00
17:52:18.386335 R00030000 Read-Data Slave configuration: 00000000 0
17:52:18.525450 B40031300 Read-Ack Slave configuration: 00010011 0
17:52:18.528339 AC0090000 Read-Ack Remote override room setpoint: 0.00
17:52:18.905196 T80190000 Read-Data Boiler water temperature: 0.00
17:52:19.053708 BC0193203 Read-Ack Boiler water temperature: 50.01
17:52:19.449174 T80640000 Read-Data Remote override function: 00000000
17:52:19.452073 R00110000 Read-Data Relative modulation level: 0.00
17:52:19.604887 BC0113500 Read-Ack Relative modulation level: 53.00
17:52:19.607748 AC0640001 Read-Ack Remote override function: 00000001
17:52:19.972372 T00000300 Read-Data Status: 00000011 00000000
17:52:20.119627 BC000030A Read-Ack Status: 00000011 00001010
17:52:20.505147 T00000300 Read-Data Status: 00000011 00000000
17:52:20.653310 BC000030A Read-Ack Status: 00000011 00001010
17:52:20.868048 DD: 13
17:52:21.036629 T00000300 Read-Data Status: 00000011 00000000
17:52:21.182928 BC000030A Read-Ack Status: 00000011 00001010
17:52:21.567482 T00000300 Read-Data Status: 00000011 00000000
17:52:21.710976 BC000030A Read-Ack Status: 00000011 00001010
17:52:22.102670 T00000300 Read-Data Status: 00000011 00000000
17:52:22.251861 BC000030A Read-Ack Status: 00000011 00001010
17:52:22.636658 T10012B00 Write-Data Control setpoint: 43.00
17:52:22.791459 BD0012B00 Write-Ack Control setpoint: 43.00
17:52:23.180741 T90101600 Write-Data Room setpoint: 22.00
17:52:23.183732 R800D0000 Read-Data Fault buffer entry: 0 0
17:52:23.322572 B400D0000 Read-Ack Fault buffer entry: 0 0
17:52:23.325352 A50101600 Write-Ack Room setpoint: 22.00
17:52:23.701942 T80190000 Read-Data Boiler water temperature: 0.00
17:52:23.850786 B40193280 Read-Ack Boiler water temperature: 50.50
17:52:24.234747 T00000300 Read-Data Status: 00000011 00000000
17:52:24.390954 BC000030A Read-Ack Status: 00000011 00001010
17:52:24.769434 T00000300 Read-Data Status: 00000011 00000000
17:52:24.916563 BC000030A Read-Ack Status: 00000011 00001010
17:52:25.301989 T00000300 Read-Data Status: 00000011 00000000
17:52:25.450085 BC000030A Read-Ack Status: 00000011 00001010
17:52:25.834170 T00000300 Read-Data Status: 00000011 00000000
17:52:25.989806 BC000030A Read-Ack Status: 00000011 00001010
17:52:26.369277 T00000300 Read-Data Status: 00000011 00000000
17:52:26.515920 BC000030A Read-Ack Status: 00000011 00001010
17:52:26.900105 T00000300 Read-Data Status: 00000011 00000000
17:52:27.049193 BC000030A Read-Ack Status: 00000011 00001010
17:52:27.436261 T00000300 Read-Data Status: 00000011 00000000
17:52:27.589407 BC000030A Read-Ack Status: 00000011 00001010
17:52:27.967339 T10012B00 Write-Data Control setpoint: 43.00
17:52:28.108859 BD0012B00 Write-Ack Control setpoint: 43.00
17:52:28.500298 T9018165D Write-Data Room temperature: 22.36
17:52:28.639491 B5018165D Write-Ack Room temperature: 22.36
17:52:29.048345 T80190000 Read-Data Boiler water temperature: 0.00
17:52:29.194680 B40193280 Read-Ack Boiler water temperature: 50.50
17:52:29.579651 T00000300 Read-Data Status: 00000011 00000000
17:52:29.728556 BC000030A Read-Ack Status: 00000011 00001010
17:52:30.114939 T00000300 Read-Data Status: 00000011 00000000
17:52:30.268406 BC000030A Read-Ack Status: 00000011 00001010
17:52:30.647201 T00000300 Read-Data Status: 00000011 00000000
17:52:30.792031 BC000030A Read-Ack Status: 00000011 00001010
17:52:31.179739 T00000300 Read-Data Status: 00000011 00000000
17:52:31.329280 BC000030A Read-Ack Status: 00000011 00001010
17:52:31.714228 T00000300 Read-Data Status: 00000011 00000000
17:52:31.867929 BC000030A Read-Ack Status: 00000011 00001010
17:52:32.246995 T00000300 Read-Data Status: 00000011 00000000
17:52:32.394932 BC000030A Read-Ack Status: 00000011 00001010
17:52:32.779887 T10012B00 Write-Data Control setpoint: 43.00
17:52:32.927452 BD0012B00 Write-Ack Control setpoint: 43.00
17:52:33.325439 T900E6400 Write-Data Maximum relative modulation level: 100.00
17:52:33.328147 R900E0D00 Write-Data Maximum relative modulation level: 13.00
17:52:33.478752 BF00E0D00 Unk-DataId Maximum relative modulation level: 13.00
17:52:33.481323 A500E6400 Write-Ack Maximum relative modulation level: 100.00
17:52:33.846444 T80190000 Read-Data Boiler water temperature: 0.00
17:52:33.992613 B40193280 Read-Ack Boiler water temperature: 50.50
17:52:34.377145 T00000300 Read-Data Status: 00000011 00000000
17:52:34.526362 BC000030A Read-Ack Status: 00000011 00001010
17:52:34.912457 T00000300 Read-Data Status: 00000011 00000000
17:52:35.066195 BC000030A Read-Ack Status: 00000011 00001010
17:52:35.444820 T00000300 Read-Data Status: 00000011 00000000
17:52:35.592047 BC000030A Read-Ack Status: 00000011 00001010
17:52:35.977739 T00000300 Read-Data Status: 00000011 00000000
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sun Oct 13, 2013 6:53 pm
by hvxl
nlrb wrote:I have the problem with 4.0a10 that the Max. relative modulation level gets set without using the MM command. The DD command seems to act as the MM command.
Confirmed. Any command consisting of two equal letters other than AA or TT will act as if the MM command was issued. Thanks for reporting. I will fix it for the next version.
You're doing an excellent job testing this thing. That bug could have stayed in there for years without me noticing. (You know there's no DD command, right?).