OTGW switching from Monitor to Gateway mode "by itself"

This Forum is about the Opentherm gateway (OTG) from Schelte

Moderator: hvxl

OTGW switching from Monitor to Gateway mode "by itself"

Postby emmeesse68 » Tue Feb 10, 2015 12:35 am

Hi all,

I managed to build an OTGW and run OTMonitor as a daemon on a 64-bit debian box after repackaging the executable by means of an 64 bit tclkit.

Now it's all running smooth but for a thing that keeps puzzling me. I tried accessing the webpage using my Windows 8.1 laptop and found the OTGW running in gateway mode. So I ran the GUI from the Windows laptop, connecting to the TCP port I configured as a relay on the debian box. I was able to connect and set the mode to "monitor". But when I closed the GUI and the webpage and reopened them, I found the OTGW running in gateway mode again... what could it be?

Strangely it seems that opening the GUI on the debian machine itself would not change the gateway mode, but if I access the webpage (from the debian box or the Windows laptop, it doesn't matter) it will cause the OTGW to switch to Gateway mode.

Since I'm trying to diagnose communications between my Ferroli BlueHelix Pro boiler and the "evil R8810" (EvoHome OT module), I would like the OTGW to interfere as little as possible, thus I'd prefer it to stay in monitor mode, but the little daemon seems to be enjoying to switch back to Gateway mode...

So I checked my logs, but couldn't spot those spontaneous changes to gateway mode. I can see when I switch it back to monitor mode (some "Command: GW=0"), but later I see the inquiry "Command: PR=M" returning "PR: M=G" without anything obviouslu meaning a switch to gateway mode. But maybe I'm not looking for the right thing... ideas?

BTW I have a few errors 03 (10 in 24 hours) and some more errors 04 (127 in the same 24 hour period). Is it meaning I have to check the reference voltage and maybe play a little around with that? Is it safe to alter it? Might it be related to the monitor mode issue?

Thanks a lot

M
emmeesse68
Starting Member
Starting Member
 
Posts: 45
Joined: January 2015

Re: OTGW switching from Monitor to Gateway mode "by itself"

Postby hvxl » Tue Feb 10, 2015 5:57 pm

At 09:06 and 11:31 the gateway was reset. That puts it back in gateway mode. Based on the available information it's impossible to say what caused the reset, but it's highly unlikely that accessing the otmonitor built-in web server with a browser has anything to do with it. That's probably just coincidence.

A few errors is nothing to worry about. You can try to change the voltage reference, but I don't expect that will improve things. If you keep an eye on the message log while you are adjusting the reference voltage, it's quite safe to do. If you set it too high or too low you may miss a few messages. Then just put it back.

The errors are unrelated to the monitor mode issue.
Schelte
hvxl
Senior Member
Senior Member
 
Posts: 1195
Joined: June 2010

Re: OTGW switching from Monitor to Gateway mode "by itself"

Postby emmeesse68 » Wed Feb 11, 2015 6:18 pm

Thanks Shelte, I'll try fine-tuning reference voltage to see if the errrors could be reduced.

...how do you tell my gateway was reset at 9.06 and 11.31? Just don't know what to look for in the logs...

Today I tried this:
- logged into my debian box and opened the GUI OTMonitor connected to the daemon on the box itself via relay TCP socket.
- opened the "options/miscellaneous" to find it in "gateway mode".
- Clicked a couple times on the "monitor" button. It finally accepted and switched to "monitor" mode.
- closed the GUI
- opened it back. Monitor mode was conserved.
- opened a browser on the debian box, connected do 12.0.0.1:8080 and logged in with my user/password.
- went to "resources" "getting gateway settings", and selected "gateway mode". Obtained this: Result = PR: M=G
- opened back the GUI, it was set effectively back into gateway mode.

So, if the revert to gateway mode is due to a gateway reset, I assume my gateway gets reset when I connect through a web browser...

Anyway, looking at the log I still can't find what happened nor spot out those resets. If you think it could be any helpful I can upload a few minutes of the last log, including the described sequence, just tell me how it's best (this forum as an attachment or the OTGW site as a log upload).

Thanks again...

M
emmeesse68
Starting Member
Starting Member
 
Posts: 45
Joined: January 2015

Re: OTGW switching from Monitor to Gateway mode "by itself"

Postby hvxl » Wed Feb 11, 2015 9:16 pm

Sorry, I meant 00:09:06 and 00:11:31. When the gateway powers up or resets, it reports "OpenTherm Gateway 4.2". I see such reports at those times. The reset actually happens about a second before that; the gateway waits one second for new firmware before printing its banner.

You only request the gateway mode via the web browser at 00:09:57, almost a minute after the reset. So, using the browser doesn't cause the reset. The times would be much closer if that was the case.

Is the gateway close to you when you work at your computer? Maybe when you move the mouse to start up the browser, you jiggle some cables of the gateway. Or your hand just comes close to the gateway and causes some interference that leads to a reset.

In any case, watch the otmonitor log window closely and notice what you did one second before you see an "OpenTherm Gateway 4.2" report.

Please attach logs for investigation of issues to the appropriate forum topic. The log upload page on the web site is intended for obtaining equipment details while things are operating normally.
Schelte
hvxl
Senior Member
Senior Member
 
Posts: 1195
Joined: June 2010

Re: OTGW switching from Monitor to Gateway mode "by itself"

Postby emmeesse68 » Wed Feb 11, 2015 11:32 pm

Okay, I did some more experiments and actually ypu're right, it might not depend on the web session, or it's not direct and immediate.

Here is a piece of log (cut out a lot of ordinary OT messages):

- here, I set monitor mode from the GUI (relay TCP):
...
21:48:07.435013 T00050000 Read-Data Application-specific flags: 00000000 0

21:48:07.962835 Command (via relay server, from [::1]:33782): GW=0
21:48:07.975832 GW: 0
21:48:08.477977 T00050000 Read-Data Application-specific flags: 00000000 0
21:48:08.587176 BC0050000 Read-Ack Application-specific flags: 00000000 0
...

Here, I opened the web interface using Iceweasel (a firefox clone found natively on my debian box) and checked correctly OTGW was still in monitor mode:

...
21:49:12.739078 T80190000 Read-Data Boiler water temperature: 0.00
21:49:12.852632 B40193F00 Read-Ack Boiler water temperature: 63.00
21:49:13.230007 Command (via websocket from 127.0.0.1:56212): PR=M
21:49:13.245065 PR: M=M
21:49:13.277990 T10014100 Write-Data Control setpoint: 65.00
21:49:14.320991 T10014100 Write-Data Control setpoint: 65.00
21:49:14.399448 BD0014100 Write-Ack Control setpoint: 65.00
21:49:14.860372 T90181400 Write-Data Room temperature: 20.00
21:49:14.961324 B50181400 Write-Ack Room temperature: 20.00
21:49:15.400989 T10101400 Write-Data Room setpoint: 20.00
21:49:15.524244 BD0101400 Write-Ack Room setpoint: 20.00
21:49:15.940041 T00000300 Read-Data Status: 00000011 00000000
21:49:16.016748 BC000030A Read-Ack Status: 00000011 00001010
21:49:16.480678 T00050000 Read-Data Application-specific flags: 00000000 0

Here I didn't cut any logs and it appears the OTGW was reset. More than a Whole second is actually missing ( 21:49:16.480678 to 21:49:17.872595), probably due to the fw upgrade window timeout.

21:49:17.872595 OpenTherm Gateway 4.2

It doesn't appear here, but there's a "funny" character between the timestamp and the "OpenTherm Gateway 4.2" message, that appears to be an "EOT" when wiewed with Notepad++ on my Windows laptop.

21:49:18.066281 T80190000 Read-Data Boiler water temperature: 0.00
21:49:18.196187 BC0194000 Read-Ack Boiler water temperature: 64.00
21:49:18.607194 T10014100 Write-Data Control setpoint: 65.00
21:49:18.757972 BD0014100 Write-Ack Control setpoint: 65.00
21:49:19.147409 T801C0000 Read-Data Return water temperature: 0.00
21:49:19.251429 BC01C3800 Read-Ack Return water temperature: 56.00
21:49:19.687986 T00110000 Read-Data Relative modulation level: 0.00
21:49:19.813161 BC0110000 Read-Ack Relative modulation level: 0.00
21:49:20.229533 T00090000 Read-Data Remote override room setpoint: 0.00
21:49:20.375481 BF0090000 Unk-DataId Remote override room setpoint: 0.00
21:49:20.386819 AC0090000 Read-Ack Remote override room setpoint: 0.00
21:49:20.602729 Command (via websocket from 127.0.0.1:56212): PR=M
21:49:20.617698 PR: M=G
21:49:20.769167 T00050000 Read-Data Application-specific flags: 00000000 0
21:49:20.868965 BC0050000 Read-Ack Application-specific flags: 00000000 0

In the end, via browser the OTGW is recognised to be set in gateway mode, probably because of the reset.

Now, what could it be possibly causing those resets?

- my OTGW is connected via the Prolific USB to my Debian box;
- I'm not touching the OTGW nor the Linux box nor any of the wiring. I'm actually accessing everything by menas of my Windows laptop, a meter away, via wifi. So, no cables are even touched.
- I can see those reset messages (OpenTherm Gateway 4.2 preceededd by the EOT character) only when I'm working with the interface, mostly the web than the GUI, independently if I run them locally or remotely. I tried opening the GUI on my Windows box and on the Linux box (via remote xwindow server) and noted that upon connecting one, the "reset" log appears - but not Always. Opening the web UI could trigger a reset, but not Always - and not immediately.

I scanned my previous logs, resets appear only at times where I might have been connecting some UI (nothing happened when I was away or just not watching OTMonitor... )

I ran out of ideas for further tests... Maybe I have a buggy executable (I built it with a tclkit-8.6.3-linux-amd64 and an sdx-20110317.kit from the web, since the 32-bit executable wouldn't run on my 64-bit debian neither after I tried to add 32-bit environment plus all the libraries). Maybe I have built a buggy OTGW... I'll try to rule out the possibility maybe connecting it to my Windows laptop (prolific drivers are an issue but luckily I found some old ones that run on Win 8.1).

Any other ideas?

Thanks again,

M
emmeesse68
Starting Member
Starting Member
 
Posts: 45
Joined: January 2015

Re: OTGW switching from Monitor to Gateway mode "by itself"

Postby emmeesse68 » Thu Feb 12, 2015 5:10 pm

Addendum: I noticed that there's no need for the GUI or the web app to be opened to cause the reset.

Wether the GUI or the web app is open, no resets take place when the OTGW is in gateway mode. As far as I don't try setting OTGW in monitor mode, I can open/close the GUI or the web app as much as I want withot those resets being triggered.

But when I set the OTGW into monitor mode (i know only the GUI to do this), after a while (whitin a couple of minutes), the OTGW would self-reset (even if I close the GUI). Then, if I didn't close it, the GUI would still believe the OTGW is in monitor mode (as it appears, it doesn't check again until I close and reopen it) but the web interface would return the status to be in gateway mode.

That would explain what earlier I misunderstood to be a relationship between resets and the GUI usage, since every time I opened the GUI I also tried to set my OTGW in monitor mode.

Now I could as well change the topic subject to "why my OTGW doesn't want ro stay in monitor mode?"

The question is the same (what could be causing these resets??) but the possible cause is shifting from the GUI to the OTGW itself when it's in monitor mode...

Anyone else experiencing something similar?

Cheers

M
emmeesse68
Starting Member
Starting Member
 
Posts: 45
Joined: January 2015

Re: OTGW switching from Monitor to Gateway mode "by itself"

Postby hvxl » Thu Feb 12, 2015 5:20 pm

I added a new command to firmware version 4.2.2 that will let you obtain the reason for the last reset via the PR=Q command. Possible reasons are:
    P=Power on
    B=Brown out (supply voltage dropped below 4.35V)
    E=External reset (using the reset button)
    C=By command (GW=R)
    S=BREAK condition on the serial interface
    L=Stuck in a loop (same message received 64 times in a row)
Try loading this firmware. Then, after the gateway spontaneously resets itself again, run the PR=Q command and see what the reason was. That should help us narrow down the possible causes.
Schelte
hvxl
Senior Member
Senior Member
 
Posts: 1195
Joined: June 2010

Re: OTGW switching from Monitor to Gateway mode "by itself"

Postby hvxl » Thu Feb 12, 2015 5:34 pm

Based on your latest update I managed to reproduce the situation. PR=Q reports: PR: Q=L
So, apparently there's something wrong with the code that checks for repeated messages in monitor mode. I will look into it.
Schelte
hvxl
Senior Member
Senior Member
 
Posts: 1195
Joined: June 2010

Re: OTGW switching from Monitor to Gateway mode "by itself"

Postby emmeesse68 » Thu Feb 12, 2015 6:06 pm

Thanks Schelte,

I loaded your new firmware and can confirm the PR: Q=L response on my OTGW as well.

Another thing I noticed, when I manage to put my OTGW in monitor mode, quite ofteen I read duplicate messages from the thermostat, and it doesn't happen in gateway mode. A piece of log (copied from the gui), from me setting the OTGW into monitor mode, to OTGW resetting:

17:57:28.918790 Command: GW=0
17:57:28.936986 GW: 0
17:57:29.294874 T80190000 Read-Data Boiler water temperature: 0.00
17:57:30.340719 T80190000 Read-Data Boiler water temperature: 0.00
17:57:31.383841 T80190000 Read-Data Boiler water temperature: 0.00
17:57:31.480622 BC0193B00 Read-Ack Boiler water temperature: 59.00
17:57:31.924377 T10014400 Write-Data Control setpoint: 68.00
17:57:32.967818 T10014400 Write-Data Control setpoint: 68.00
17:57:33.029111 BD0014400 Write-Ack Control setpoint: 68.00
17:57:33.507707 T00000300 Read-Data Status: 00000011 00000000
17:57:33.587057 BC000030A Read-Ack Status: 00000011 00001010
17:57:34.047309 T00000300 Read-Data Status: 00000011 00000000
17:57:34.152751 BC000030A Read-Ack Status: 00000011 00001010
17:57:34.587007 T00050000 Read-Data Application-specific flags: 00000000 0
17:57:35.631541 T00050000 Read-Data Application-specific flags: 00000000 0
17:57:35.700070 BC0050000 Read-Ack Application-specific flags: 00000000 0
17:57:36.170709 T80190000 Read-Data Boiler water temperature: 0.00
17:57:37.212763 T80190000 Read-Data Boiler water temperature: 0.00
17:57:37.317284 BC0193B00 Read-Ack Boiler water temperature: 59.00
17:57:37.752791 T10014400 Write-Data Control setpoint: 68.00
17:57:37.879348 BD0014400 Write-Ack Control setpoint: 68.00
17:57:38.293560 T00000300 Read-Data Status: 00000011 00000000
17:57:38.371564 BC000030A Read-Ack Status: 00000011 00001010
17:57:38.834122 T00050000 Read-Data Application-specific flags: 00000000 0
17:57:38.934403 BC0050000 Read-Ack Application-specific flags: 00000000 0
17:57:39.373526 T80190000 Read-Data Boiler water temperature: 0.00
17:57:39.496603 BC0193B00 Read-Ack Boiler water temperature: 59.00
17:57:39.914377 T10014400 Write-Data Control setpoint: 68.00
17:57:39.987831 BD0014400 Write-Ack Control setpoint: 68.00
17:57:40.456462 T00000300 Read-Data Status: 00000011 00000000
17:57:41.500636 T00000300 Read-Data Status: 00000011 00000000
17:57:41.605411 BC000030A Read-Ack Status: 00000011 00001010
17:57:42.042683 T00000300 Read-Data Status: 00000011 00000000
17:57:42.168446 BC000030A Read-Ack Status: 00000011 00001010
17:57:42.582028 T00000300 Read-Data Status: 00000011 00000000
17:57:42.661554 BC000030A Read-Ack Status: 00000011 00001010
17:57:43.122712 T00000300 Read-Data Status: 00000011 00000000
17:57:44.167029 T00000300 Read-Data Status: 00000011 00000000
17:57:44.278392 BC000030A Read-Ack Status: 00000011 00001010
17:57:44.706390 T00050000 Read-Data Application-specific flags: 00000000 0
17:57:44.770535 BC0050000 Read-Ack Application-specific flags: 00000000 0
17:57:45.247476 T80190000 Read-Data Boiler water temperature: 0.00
17:57:45.332683 B40193C00 Read-Ack Boiler water temperature: 60.00
17:57:45.787787 T10014400 Write-Data Control setpoint: 68.00
17:57:45.895090 BD0014400 Write-Ack Control setpoint: 68.00
17:57:46.329141 T00000300 Read-Data Status: 00000011 00000000
17:57:46.388190 BC000030A Read-Ack Status: 00000011 00001010
17:57:46.869416 T00000300 Read-Data Status: 00000011 00000000
17:57:46.949614 BC000030A Read-Ack Status: 00000011 00001010
17:57:47.409102 T00000300 Read-Data Status: 00000011 00000000
17:57:48.452674 T00000300 Read-Data Status: 00000011 00000000
17:57:48.567282 BC000030A Read-Ack Status: 00000011 00001010
17:57:48.994525 T00050000 Read-Data Application-specific flags: 00000000 0
17:57:49.093999 BC0050000 Read-Ack Application-specific flags: 00000000 0
17:57:49.535229 T80190000 Read-Data Boiler water temperature: 0.00
17:57:50.578297 T80190000 Read-Data Boiler water temperature: 0.00
17:57:50.676662 B40193C00 Read-Ack Boiler water temperature: 60.00
17:57:51.120542 T10014400 Write-Data Control setpoint: 68.00
17:57:52.162696 T10014400 Write-Data Control setpoint: 68.00
17:57:52.255243 BD0014400 Write-Ack Control setpoint: 68.00
17:57:52.701990 T00000300 Read-Data Status: 00000011 00000000
17:57:52.785559 BC000030A Read-Ack Status: 00000011 00001010
17:57:53.241584 T00000300 Read-Data Status: 00000011 00000000
17:57:53.348608 BC000030A Read-Ack Status: 00000011 00001010
17:57:53.780989 T00000300 Read-Data Status: 00000011 00000000
17:57:53.841289 BC000030A Read-Ack Status: 00000011 00001010
17:57:54.321606 T80383000 Read-Data DHW setpoint: 48.00
17:57:54.401851 B40383000 Read-Ack DHW setpoint: 48.00
17:57:54.861976 T80394600 Read-Data Max CH water setpoint: 70.00
17:57:54.965270 B40394600 Read-Ack Max CH water setpoint: 70.00
17:57:55.404197 T900E6400 Write-Data Maximum relative modulation level: 100.00
17:57:56.445788 T900E6400 Write-Data Maximum relative modulation level: 100.00
17:57:56.513391 B500E6400 Write-Ack Maximum relative modulation level: 100.00
17:57:56.988064 T00050000 Read-Data Application-specific flags: 00000000 0
17:57:57.074462 BC0050000 Read-Ack Application-specific flags: 00000000 0
17:57:57.529685 T80190000 Read-Data Boiler water temperature: 0.00
17:57:57.637849 B40193C00 Read-Ack Boiler water temperature: 60.00
17:57:58.069950 T10014400 Write-Data Control setpoint: 68.00
17:57:58.130072 BD0014400 Write-Ack Control setpoint: 68.00
17:57:58.611293 T90181400 Write-Data Room temperature: 20.00
17:57:58.692164 B50181400 Write-Ack Room temperature: 20.00
17:57:59.151192 T00050000 Read-Data Application-specific flags: 00000000 0
17:58:00.195161 T00050000 Read-Data Application-specific flags: 00000000 0
17:58:00.309260 BC0050000 Read-Ack Application-specific flags: 00000000 0
17:58:00.736395 T80190000 Read-Data Boiler water temperature: 0.00
17:58:01.779792 T80190000 Read-Data Boiler water temperature: 0.00
17:58:01.855846 B40193C00 Read-Ack Boiler water temperature: 60.00
17:58:02.321707 T10014400 Write-Data Control setpoint: 68.00
17:58:03.365956 T10014400 Write-Data Control setpoint: 68.00
17:58:03.473481 BD0014400 Write-Ack Control setpoint: 68.00
17:58:03.905407 T00000300 Read-Data Status: 00000011 00000000
17:58:04.951064 T00000300 Read-Data Status: 00000011 00000000
17:58:05.995460 T00000300 Read-Data Status: 00000011 00000000
17:58:07.038223 T00000300 Read-Data Status: 00000011 00000000
17:58:08.081731 T00000300 Read-Data Status: 00000011 00000000
17:58:09.126605 T00000300 Read-Data Status: 00000011 00000000
17:58:09.239475 BC000030A Read-Ack Status: 00000011 00001010
17:58:09.667422 T00050000 Read-Data Application-specific flags: 00000000 0
17:58:10.711908 T00050000 Read-Data Application-specific flags: 00000000 0
17:58:10.785192 BC0050000 Read-Ack Application-specific flags: 00000000 0
17:58:11.253225 T80190000 Read-Data Boiler water temperature: 0.00
17:58:11.348533 BC0193D00 Read-Ack Boiler water temperature: 61.00
17:58:11.793652 T10014400 Write-Data Control setpoint: 68.00
17:58:12.838157 T10014400 Write-Data Control setpoint: 68.00
17:58:12.963880 BD0014400 Write-Ack Control setpoint: 68.00
17:58:13.378024 T10101400 Write-Data Room setpoint: 20.00
17:58:13.456913 BD0101400 Write-Ack Room setpoint: 20.00
17:58:13.918430 T801C0000 Read-Data Return water temperature: 0.00
17:58:14.020250 BC01C3200 Read-Ack Return water temperature: 50.00
17:58:14.458127 T00000300 Read-Data Status: 00000011 00000000
17:58:14.582891 BC000030A Read-Ack Status: 00000011 00001010
17:58:14.997970 T00050000 Read-Data Application-specific flags: 00000000 0
17:58:15.075117 BC0050000 Read-Ack Application-specific flags: 00000000 0
17:58:15.537040 T80190000 Read-Data Boiler water temperature: 0.00
17:58:15.637249 BC0193D00 Read-Ack Boiler water temperature: 61.00
17:58:16.076869 T10014400 Write-Data Control setpoint: 68.00
17:58:16.200202 BD0014400 Write-Ack Control setpoint: 68.00
17:58:16.617615 T00110000 Read-Data Relative modulation level: 0.00
17:58:16.692674 BC0110000 Read-Ack Relative modulation level: 0.00
17:58:17.159018 T00090000 Read-Data Remote override room setpoint: 0.00
17:58:17.254606 BF0090000 Unk-DataId Remote override room setpoint: 0.00
17:58:17.699382 T00090000 Read-Data Remote override room setpoint: 0.00
17:58:17.817577 BF0090000 Unk-DataId Remote override room setpoint: 0.00
17:58:18.238267 T00090000 Read-Data Remote override room setpoint: 0.00
17:58:18.310535 BF0090000 Unk-DataId Remote override room setpoint: 0.00
17:58:18.780326 T801A0000 Read-Data DHW temperature: 0.00
17:58:18.872011 B401A3300 Read-Ack DHW temperature: 51.00
17:58:19.320182 T00050000 Read-Data Application-specific flags: 00000000 0
17:58:19.434764 BC0050000 Read-Ack Application-specific flags: 00000000 0
17:58:19.861729 T80190000 Read-Data Boiler water temperature: 0.00
17:58:20.904849 T80190000 Read-Data Boiler water temperature: 0.00
17:58:20.980617 BC0193E00 Read-Ack Boiler water temperature: 62.00
17:58:21.445181 T10014400 Write-Data Control setpoint: 68.00
17:58:22.488802 T10014400 Write-Data Control setpoint: 68.00
17:58:23.532303 T10014400 Write-Data Control setpoint: 68.00
17
:58:23.652862 BD0014400 Write-Ack Control setpoint: 68.00
17:58:24.072630 T00000300 Read-Data Status: 00000011 00000000
17:58:25.117423 T00000300 Read-Data Status: 00000011 00000000
17:58:26.162452 T00000300 Read-Data Status: 00000011 00000000
17:58:27.205921 T00000300 Read-Data Status: 00000011 00000000
17:58:27.309259 BC000030A Read-Ack Status: 00000011 00001010
17:58:27.746012 T00050000 Read-Data Application-specific flags: 00000000 0
17:58:27.872249 BC0050000 Read-Ack Application-specific flags: 00000000 0
17:58:28.287290 T80190000 Read-Data Boiler water temperature: 0.00
17:58:29.329905 T00050000 Read-Data Application-specific flags: 00000000 0
17:58:29.418934 BC0050000 Read-Ack Application-specific flags: 00000000 0
17:58:29.870448 T80190000 Read-Data Boiler water temperature: 0.00
17:58:29.981595 BC0193E00 Read-Ack Boiler water temperature: 62.00
17:58:30.410344 T10014400 Write-Data Control setpoint: 68.00
17:58:30.473982 BD0014400 Write-Ack Control setpoint: 68.00
17:58:30.949479 T001B0000 Read-Data Outside temperature: 0.00
17:58:31.036051 BC01B0600 Read-Ack Outside temperature: 6.00
17:58:31.489084 T80130000 Read-Data DHW flow rate: 0.00
17:58:31.596749 B40130000 Read-Ack DHW flow rate: 0.00
17:58:32.030085 T00120000 Read-Data CH water pressure: 0.00
17:58:33.075424 T00120000 Read-Data CH water pressure: 0.00
17:58:34.119898 T00000300 Read-Data Status: 00000011 00000000
17:58:34.199931 BC000030A Read-Ack Status: 00000011 00001010
17:58:34.661176 T00050000 Read-Data Application-specific flags: 00000000 0
17:58:35.704107 T00050000 Read-Data Application-specific flags: 00000000 0
17:58:35.817886 BC0050000 Read-Ack Application-specific flags: 00000000 0
17:58:36.244433 T80190000 Read-Data Boiler water temperature: 0.00
17:58:36.310092 BC0193E00 Read-Ack Boiler water temperature: 62.00
17:58:36.784491 T10014400 Write-Data Control setpoint: 68.00
17:58:37.826585 T10014400 Write-Data Control setpoint: 68.00
17:58:39.172398 OpenTherm Gateway 4.2.2
emmeesse68
Starting Member
Starting Member
 
Posts: 45
Joined: January 2015

Re: OTGW switching from Monitor to Gateway mode "by itself"

Postby hvxl » Thu Feb 12, 2015 8:58 pm

It looks like the boiler doesn't always understand the messages it receives and then doesn't answer, so the thermostat repeats the request a second later. This can happen because in monitor mode the gateway passes the signal levels straight through from the thermostat to the boiler, using the timings generated by the thermostat. In gateway mode, it cleans up the signal timings. So, apparently your thermostat isn't producing a clean enough signal for the boiler to recognize without fail.
Schelte
hvxl
Senior Member
Senior Member
 
Posts: 1195
Joined: June 2010

Re: OTGW switching from Monitor to Gateway mode "by itself"

Postby emmeesse68 » Thu Feb 12, 2015 9:21 pm

That's why I refer to it as "the evil R8810" :-)

I have (more than) a few suspicion that my unit is faulty, not easy to be certain of because Honeywell hides really well after selling... they had the reseller tell me they don't distribute the R8810 in Italy, after they put it in the official listing AND I bought one... :?

[/rant]
emmeesse68
Starting Member
Starting Member
 
Posts: 45
Joined: January 2015

Re: OTGW switching from Monitor to Gateway mode "by itself"

Postby emmeesse68 » Thu Feb 12, 2015 9:25 pm

...that's why I'm trying to keep my OTGW in monitor mode... record a few hours of reliable logging establish wether my "evil R8810" is to be sent back to Honeywell asking for a replacement - or I have to look for something else...
emmeesse68
Starting Member
Starting Member
 
Posts: 45
Joined: January 2015

Re: OTGW switching from Monitor to Gateway mode "by itself"

Postby hvxl » Thu Feb 12, 2015 9:51 pm

Before you make claims towards Honeywell based on data you gather using the gateway, there is one thing you should be aware of: Opto-coupler OK1A may have a negative effect on the signal to the boiler. Depending on variations in the used components it may introduce different delays for rising and falling flanks. To check this, use test #4 of the diagnostic firmware. If the timings differ much, you can play with different values for R8 to correct that.
Schelte
hvxl
Senior Member
Senior Member
 
Posts: 1195
Joined: June 2010

Re: OTGW switching from Monitor to Gateway mode "by itself"

Postby hvxl » Thu Feb 12, 2015 9:58 pm

Try firmware 4.2.3. That should stay in monitor mode.
Schelte
hvxl
Senior Member
Senior Member
 
Posts: 1195
Joined: June 2010

Re: OTGW switching from Monitor to Gateway mode "by itself"

Postby emmeesse68 » Thu Feb 12, 2015 10:48 pm

...aren't you a fast coder, Schelte? :-)

Firmware 4.2.3 up 'n running, you hit the nail, after some 20 minutes it didn't reset and it's still in monitor mode.

I remember performing the diagnostic test #4 a few days ago but, silly me, I didn't note the results. I think I'll let your new firmware run overnight and maybe have a run with diagnostics in the morning.

By the way, I'm not trying to take Honeywell to court or something :-), I'm just getting some evidence to decide myself whether to send my R8810 back for a checkup (that could last... more than one day!) through the reseller, or else. Since they're trying to talk me into reverting to on/off control (that would be a significant loss, in my opinion, in terms of optimisation) I just need to check what's going on, the Whole EvoHome thing is costing a lot of money and would be a shame not to make the most out of it, leveraging the OT modulating and reporting functionalities (even if EvoHome seems not to leverage those reporting functionalities itself).

Meanwhile, OTGW has been running in monitor mode for more than 30 minutes without resetting. That's good...

Thanks again

M
emmeesse68
Starting Member
Starting Member
 
Posts: 45
Joined: January 2015

Next

Return to Opentherm Gateway Forum

Who is online

Users browsing this forum: No registered users and 1 guest