Bind Issue

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

Moderator: hvxl

Bind Issue

Postby scanxtaz » Mon Nov 18, 2019 6:53 pm

Hey,

I've an opentherm gateway connected to my boiler for a while now. (Remeha Boiler with Remeha wireless thermostat)
I didn't really used it (personal issue prevented me to go further) but I tried it with a laptop when I bought it (a year ago) and I was able to read the messages sent on the bus.
Laptop was not suitable, so I had the plan, at that time, to move to a raspberry (more convenient).

Now that I've a couple of days to work on it, I'd like to restart this project.

I do remember that on the laptop with a X session, the gateway was perfectly behaving, but today, I'd like to go for the pi, the system does not work at all.

When I try to start otmonitor-ahf now on my rasp, it doesn't want to communicate with the boiler, even worth, it totally broke the communication between the thermostat and the boiler.

When I'm starting the monitor (regardless monitor or gateway mode), it's constantly looping on a "slave" message :

Code: Select all
14:57:43.811493  BD002010B  Write-Ack   Master configuration: 00000001 11
                               - Smart power: supported (1)
14:57:44.720127  T1002010B  Write-Data  Master configuration: 00000001 11
                               - Smart power: supported (1)
14:57:44.812483  BD002010B  Write-Ack   Master configuration: 00000001 11
                               - Smart power: supported (1)
14:57:45.721248  T1002010B  Write-Data  Master configuration: 00000001 11
                               - Smart power: supported (1)
14:57:45.813606  BD002010B  Write-Ack   Master configuration: 00000001 11
                               - Smart power: supported (1)
14:57:46.722368  T1002010B  Write-Data  Master configuration: 00000001 11
                               - Smart power: supported (1)
14:57:46.815979  BD002010B  Write-Ack   Master configuration: 00000001 11
                               - Smart power: supported (1)
14:57:47.736984  T1002010B  Write-Data  Master configuration: 00000001 11
                               - Smart power: supported (1)


I've already tried to restart the boiler, I see something moving between the lines, but not that much changes :

Code: Select all
15:02:48.787520  T1002010B  Write-Data  Master configuration: 00000001 11
                               - Smart power: supported (1)
15:02:48.901143  BD002010B  Write-Ack   Master configuration: 00000001 11
                               - Smart power: supported (1)
15:02:50.840172  OpenTherm Gateway 4.2.5
15:02:50.842189  Command: SC=15:02/1
15:02:50.844513  Command: SR=21:11,18
15:02:50.846944  Command: SR=22:7,227
15:02:50.869015  SC: 15:02/1
15:02:50.884136  SR: 21:11/18
15:02:50.898004  SR: 22:7/227
15:02:50.910371  BD002010B  Write-Ack   Master configuration: 00000001 11
                               - Smart power: supported (1)


my last try is to change the firmware to the diagnose one, and now, I'm facing a strange issue (that I guess is related, like Dr House, I don't believe in coincidence :) )

Code: Select all
invalid command name "bind"
    while executing
"bind Diag <$n> [namespace code {cursor %W}]"
    ("foreach" body line 2)
    invoked from within
"foreach n {
   1 Double-1 Triple-1 B1-Motion B1-Enter B1-Leave ButtonRelease-1
    } {
   bind Diag <$n> [namespace code {cursor %W}]
    }"
    (in namespace eval "::diag" script line 6)
    invoked from within
"namespace eval diag {
    variable fileevent ""
    namespace export diagnostics

    # Make sure the cursor doesn't move
    foreach n {
   1 Double-1 ..."
    (file "/usr/sbin/otmonitor-ahf/lib/tcl8/8.6/diagnostics-1.0.tm" line 1)
    invoked from within
"source -encoding utf-8 /usr/sbin/otmonitor-ahf/lib/tcl8/8.6/diagnostics-1.0.tm"
    ("package ifneeded diagnostics 1.0" script)
    invoked from within
"package require diagnostics"
    (procedure "process" line 28)
    invoked from within
"process [append data $line]"
    (procedure "receive" line 6)
    invoked from within
"receive"


Coiuld you please help me ?
scanxtaz
Starting Member
Starting Member
 
Posts: 4
Joined: November 2019

Re: Bind Issue

Postby hvxl » Thu Nov 21, 2019 5:36 pm

The error message is related to loading the diagnostic firmware, not to your original problem. You didn't mention it, but I suppose on your raspberry pi you run otmonitor with the --daemon option. When otmonitor sees the "Opentherm gateway diagnostics - Version 1.1" message, it wants to pop up a diagnostics window. When running without a GUI, that will obviously fail. That's the reason for the error message.

I will admit that otmonitor shouldn't throw an error in this situation. But on the other hand there is not much use to run a GUI-less otmonitor in combination with the diagnostic firmware. In this configuration I would suggest to stop otmonitor and use a serial terminal program (minicom, screen, putty, or other) to talk to the otgw.

Now for your original problem: It looks like the thermostat doesn't receive or doesn't understand the response from the otgw. While you have the diagnostic firmware running, test #4 may provide some clues. Otherwise try the opentherm interfaces section of the troubleshouting instructions.
Schelte
hvxl
Senior Member
Senior Member
 
Posts: 1223
Joined: June 2010

Re: Bind Issue

Postby scanxtaz » Fri Nov 22, 2019 9:49 am

Indeed, running in Daemon mode.

Thanks hvxl to answer this thread, I must admit I'm a little bit lost :) I'll put a screen on the raspberry and then try to run the diagnose mode and let you know.

Thanks for your help, I'll also add some leds on the Gateway, in order to see what's goin'on clearer (when no screen).

Keep you updated.
scanxtaz
Starting Member
Starting Member
 
Posts: 4
Joined: November 2019

Re: Bind Issue

Postby scanxtaz » Fri Nov 22, 2019 12:19 pm

Thanks hvxl,

It runs much better now, I've installed lightdm, and even the daemon works properly now, without changing something.


Many many thanks to you and this wonderful job !
scanxtaz
Starting Member
Starting Member
 
Posts: 4
Joined: November 2019

Re: Bind Issue

Postby hvxl » Sat Nov 23, 2019 4:53 pm

The presence of lightdm has no influence on otmonitor in daemon mode. You are probably just not running into the situation anymore where otmonitor tries to pop up the diagnostics screen.
Schelte
hvxl
Senior Member
Senior Member
 
Posts: 1223
Joined: June 2010


Return to Opentherm Gateway Forum

Who is online

Users browsing this forum: No registered users and 1 guest