- √ - Beta-Tester für ebus-daemon / libebus gesucht.

[modenet]

hi, I'm trying ebus-daemon with vwmon but I see that I can't request some values, otherwise ebus-daemon hang:

get ci cir2_set_temp

2014-05-11 13:05:27.786 [bas event] >>> get ci cir2_set_temp
2014-05-11 13:05:27.786 [bas event] type: 3 msg: ff15b509030d0500
2014-05-11 13:05:27.830 [bus event] getBus success
2014-05-11 13:05:27.923 [bus trace] success
terminate called after throwing an instance of 'std:ut_of_range'
what(): basic_string::substr
Annullato (core dump creato)

2014-05-11 13:10:57.904 [bas event] >>> get sens out
2014-05-11 13:10:57.904 [bas event] type: 3 msg: ffecb509030d0600
2014-05-11 13:10:57.924 [bus event] getBus success
2014-05-11 13:10:58.019 [bus trace] success
terminate called after throwing an instance of 'std:ut_of_range'
what(): basic_string::substr
Annullato (core dump creato)

[Gast]

Show us your configuration for those commands

[modenet]

vaillant_get.csv:get;ci;cir2_set_temp;Heizkreis2-Solltemperatur;3;15;B509;3;0D0500;1;-;sd;1,2;d2c;1.000;°C;-;-;;;;;;;;;;;;;;;;;;;;;;;;

get;sens;out;Sensor Kollector1;3;EC;B509;3;0D0600;2;kol1;sd;1,2;d2c;1; grad;-;kol1;sensor;sd;3;hex;-;-;-;Sensor Vorhanden;;;;;;;;;;;;;;;;;

I attached my csv

[Gast]

Your configuration files seems to be from early version of ebusd.

The column "msg type: 1=BROAD, 2=MM, 3=MS" was changed from numeric to alphanumeric.

Just change 3 too MS.

vaillant_get.csv:get;ci;cir2_set_temp;Heizkreis2-Solltemperatur;3;15;B509;3;0D0500;1;-;sd;1,2;d2c;1.000;°C;-;-;;;;;;;;;;;;;;;;;;;;;;;;
vaillant_get.csv:get;ci;cir2_set_temp;Heizkreis2-Solltemperatur;MS;15;B509;3;0D0500;1;-;sd;1,2;d2c;1.000;°C;-;-;;;;;;;;;;;;;;;;;;;;;;;;

get;sens;out;Sensor Kollector1;3;EC;B509;3;0D0600;2;kol1;sd;1,2;d2c;1;grad;-;kol1;sensor;sd;3;hex;-;-;-;Sensor Vorhanden;;;;;;;;;;;;;;;;;
get;sens;out;Sensor Kollector1;MS;EC;B509;3;0D0600;2;kol1;sd;1,2;d2c;1;grad;-;kol1;sensor;sd;3;hex;-;-;-;Sensor Vorhanden;;;;;;;;;;;;;;;;;

[modenet]

what's happen to ebus-daemon project on github?

[Gast]

what's happen to ebus-daemon project on github?

hi,

thanks for testing.

the sources of the ebus-daemon project is migrated into ebusd.

the new version of ebusd will soon be released as v0.2.0

this thread can be closed now.

[johnm]

I've just checked out libebus and ebusd from github and started with a simple ebus_scan. Somehow I managed to get the daemon (running in foreground mode) into a state where it didn't react anymore. No more log entries were shown and the scan command did not finish.

The bus seemed to be okay, since the room controller still showed the data when browsing through the menus.

I could try to reproduce the behaviour. Is there a way to get enough debug info to you, so you can have a look at this?

[Gast]

For testing, please use the latest version of ebusd. I've added today Vaillant specific features.

ad scan:
You can start ebusd in foreground with retries = 0. (./ebusd -f -r 0)
ebusd seems to crash when too much traffic is present, and he has too little time for the execution of "normal" bus telegrams.
Therefore ebusd_scan waits about 2 seconds after each sent address.
For each wrong address (no target), ebusd returns a timeout. (~10000µs)

Which hardware do you use?

Can you run ebusd with valgrind?

Possible solutions could be:
* increase the waiting time or
* increase input buffer size

./ebusd_scan -s pi
05:   'Joh. Vaillant GmbH & Co.'   ident: 'VD600'   sw: '02.18' hw: '75.01'   s/n: 'xxxxxxxxxxxxxxxxxxxxxxxxxxxx'   item: 'xxxxxxxxxx'

2014-06-09 22:04:10.954 [bas event] >>> hex ms 09070400
2014-06-09 22:04:10.955 [bas trace]  type: ms msg: ff09070400
2014-06-09 22:04:10.971 [bus trace]  getBus success
2014-06-09 22:04:11.019 [bus trace]  -6: read timeout
2014-06-09 22:04:11.022 [bus trace]  retry number: 1
2014-06-09 22:04:11.034 [bus trace]  getBus success
2014-06-09 22:04:11.083 [bus trace]  -6: read timeout
2014-06-09 22:04:11.085 [bus trace]  retry number: 2
2014-06-09 22:04:11.095 [bus trace]  getBus success
2014-06-09 22:04:11.144 [bus trace]  -6: read timeout
2014-06-09 22:04:11.146 [bas error]  -6: read timeout
2014-06-09 22:04:11.146 [bas event] <<< -6: read timeout