Page 1 of 1

solved: wrong exhaus temp (possible OTGW bug?)

PostPosted: Sun Feb 05, 2017 8:58 am
by rpav
Exhaust temperature in the OTGW Summary page is wrong. The exhaust temperature is one of the value needed to compute Boiler Efficiency.
The value obtained by OTGW is between 0.00 and 0.18 while the value displayed by OT Master (QAA73) is more reasonable.

Currently on my system:
QAA73 Exh. Temp: 43 °C
OTGW Exh. Temp: 0.18 °C

The freq. of Exh. Temp in Summary table also varies from 1 to 25 (is it OK?)

The system is Geminox THRi 2-17 DC Boiler as OT Slave (Siemens LMU64 3.03) and QAA73 as OT Master (ver. 1.05), OTGW 4.2.4 and otmonitor 4.3 running on Linux-Armhf.

One other user already reported the same problem, unfortunately no solution has been found: viewtopic.php?f=75&t=10041&p=72218&hilit=exhaust#p72218

For reference, there is current OTGH summary table of my system, otmonitor log upon request:

Hex Dec Dir Description Freq Value
05 5 Read Application-specific flags 51246 00000000 132
19 25 Read Boiler water temperature 24 51.47
12 18 Read CH water pressure 250 1.51
01 1 Write Control setpoint 25 48.28
08 8 Write Control setpoint 2 25 38.39
15 21 Write Date 299 Feb 5
14 20 Write Day of week and time of day 299 Sun 08:26
38 56 Write DHW setpoint 11 52.00
30 48 Read DHW setpoint boundaries 250 65 10
1A 26 Read DHW temperature 24 52.09
21 33 Read Exhaust temperature 25 0.18
1F 31 Read Flow temperature CH2 24 38.20
02 2 Write Master configuration 250 00000000 4
7E 126 Write Master product version 250 1 1
31 49 Read Max CH setpoint boundaries --- 89 20
39 57 Read Max CH water setpoint 250 89.00
0E 14 Write Maximum relative modulation level 250 100.00
81 129 Write MessageID 129 24 2574
82 130 Write MessageID 130 24 20819
89 137 Write MessageID 137 --- 526
1B 27 Read Outside temperature 24 1.94
11 17 Read Relative modulation level 24 45.00
06 6 Read Remote parameter flags 250 00000111 00000111
1C 28 Read Return water temperature 24 38.62
10 16 Write Room setpoint 24 22.00
10 16 Read Room setpoint --- 17.16
17 23 Write Room Setpoint CH2 24 22.00
18 24 Write Room temperature 24 20.58
03 3 Read Slave configuration 250 00101001 4
7F 127 Read Slave product version 250 100 1
00 0 Read Status 6 00010011 00101010
16 22 Write Year 299 2017

Thank you for help with this issue.
Roman

Re: wrong exhaus temp (possible OTGW bug?)

PostPosted: Sun Feb 05, 2017 10:20 am
by hvxl
You are right. While all other temperature values are in f8.8 format, the exhaust temperature is s16. This is easily fixed by changing the format on line 1895 of otmonitor.tcl. Patch attached.

The frequency is a simple calculation of the time the application has been running divided by the number of times the message was seen. When OTMonitor has just started these values can be a bit off. Accuracy should improve when more messages have been received.

Re: solved: wrong exhaus temp (possible OTGW bug?)

PostPosted: Mon Feb 06, 2017 10:08 am
by rpav
Schelte,
thank you for _very_ quick response. I confirm that patched version of otmonitor 4.3 works as expected - exhaust temperature is correct now.
Best regards,
--
Roman

Re: solved: wrong exhaus temp (possible OTGW bug?)

PostPosted: Mon Mar 13, 2017 3:13 pm
by butyl
Shettle,
I would like to fix the Exhaust temperature format and make some changes to otmonitor for me. Can you send me step by step procedure how to compile otmonitor from source code for Raspberry pi please?
Thank you.

Re: solved: wrong exhaus temp (possible OTGW bug?)

PostPosted: Mon Mar 13, 2017 5:39 pm
by hvxl

Re: solved: wrong exhaus temp (possible OTGW bug?)

PostPosted: Mon Mar 13, 2017 7:05 pm
by butyl
Schelte,
thank you for your guide, I will try it. Perhaps It would be useful to add link of this guide to main menu.
And, I am very sorry for my terrible typo. :oops:

Butyl

Re: solved: wrong exhaus temp (possible OTGW bug?)

PostPosted: Mon Mar 20, 2017 5:09 pm
by Bororo
goedendag Schelte,
will you please update compiled files on the main website?
(for those of us without tcl knowledge).
Or would you be so kind (or anybody) and tell me how to apply this patch to otgw source directory?
many thanks in advance.

Re: solved: wrong exhaus temp (possible OTGW bug?)

PostPosted: Mon Mar 20, 2017 6:11 pm
by butyl
Bororo,
would you prefer patched source file or compiled application?

Re: solved: wrong exhaus temp (possible OTGW bug?)

PostPosted: Tue Mar 21, 2017 9:53 pm
by Bororo
Hi Butyl, If I can choose I would like to have patched source :idea:
Many thanks in advance.

Re: solved: wrong exhaus temp (possible OTGW bug?)

PostPosted: Tue Mar 21, 2017 11:30 pm
by hvxl
You're kidding, right? You can't change 4 characters yourself? No Tcl knowledge is needed. You just need to look at the provided information for 2 seconds to be able to implement the fix.

Re: solved: wrong exhaus temp (possible OTGW bug?)

PostPosted: Wed Mar 22, 2017 6:58 am
by Bororo
Seriously, I'm not kidding. When I was looking into patch provided I was not sure, if this file should be somehow incorporaded into source code, but I don't know how.
I assume it's necessary to change value format for register 33, but not sure what this code is for: @@ -1892,7 +1892,7 @@

--- otmonitor.tcl.orig 2017-02-05 09:49:32.288370130 +0100
+++ otmonitor.tcl 2017-02-05 09:49:55.844495934 +0100
@@ -1892,7 +1892,7 @@
register 30 {f8.8} "Solar collector temperature"
register 31 {f8.8} "Flow temperature CH2"
register 32 {f8.8} "DHW2 temperature"
-register 33 {f8.8} "Exhaust temperature"
+register 33 {s16} "Exhaust temperature"
register 34 {f8.8} "Boiler heat exchanger temperature"
register 35 {u8 u8} "Boiler fan speed and setpoint"
register 77 {nu u8} "Relative ventilation"

Re: solved: wrong exhaus temp (possible OTGW bug?)

PostPosted: Wed Mar 22, 2017 7:50 am
by butyl
OK. No problem. Here you are.
I patched ID30 too.

Re: wrong exhaus temp (possible OTGW bug?)

PostPosted: Wed Mar 22, 2017 8:28 am
by hvxl
If you don't know what to do with a patch file, then just follow the written instructions:
hvxl wrote:While all other temperature values are in f8.8 format, the exhaust temperature is s16. This is easily fixed by changing the format on line 1895 of otmonitor.tcl.

So on line 1895 of otmonitor.tcl change "f8.8" to "s16". It's no rocket science.