ebusd icon indicating copy to clipboard operation
ebusd copied to clipboard
verified publisher icon john30

Adapter 3 WLAN latency setup

Open salvq opened this issue 4 years ago • 1 comments

I am seeing errors on ebus communications while using Adapter 3, is it possible to troublehoot from the log whether they are related to WiFi connection or latency setup ?

Adapter 3 version with following setup:

  • Connected to WLAN via WEMOS
  • Ebusd docker running on QNAP
  • Wemos settings image
  • Docker compose file
version: '3'

services:
  ebusd:
    image: john30/ebusd:latest
    container_name: ebusd-wlan
    restart: unless-stopped
    network_mode: host
    volumes:
      - /share/Container/ebusd:/ebusd
    command: -f --scanconfig --configpath=/ebusd/ebusd-configuration/ebusd-2.1.x/en -d enh:192.168.3.3:9999 -l /var/log/ebusd.log --logareas=all --loglevel=debug --httpport=8080 --accesslevel=* --latency=10 --mqtthost=192.168.1.106 --mqttport=1883 --mqttuser=XXX --mqttpass=YYY --mqttjson --mqtttopic=ebusd/%circuit/%name

I can see messages like [bus debug] ERR or [bus error] , are those related to Wireless connection or latency setup ?

Thanks

ebusd-wlan | 2021-10-28 12:27:19.244 [bus debug] send/receive symbol latency 10 ms
ebusd-wlan | 2021-10-28 12:27:19.244 [update info] sent MS cmd: 3115b503020001 / 0affffffffffffffffffff
ebusd-wlan | 2021-10-28 12:27:19.245 [update notice] sent poll-read f47 currenterror QQ=31: -;-;-;-;-
ebusd-wlan | 2021-10-28 12:27:19.246 [bus debug] notify request: done
ebusd-wlan | 2021-10-28 12:27:19.246 [bus debug] switching from send response ACK to send SYN
ebusd-wlan | 2021-10-28 12:27:19.259 [bus debug] send/receive symbol latency 11 ms
ebusd-wlan | 2021-10-28 12:27:21.339 [mqtt debug] publish ebusd/bai/SetMode {
ebusd-wlan |      "hcmode": {"value": "auto"},
ebusd-wlan |      "flowtempdesired": {"value": 32.5},
ebusd-wlan |      "hwctempdesired": {"value": 60.0},
ebusd-wlan |      "hwcflowtempdesired": {"value": null},
ebusd-wlan |      "disablehc": {"value": 0},
ebusd-wlan |      "disablehwctapping": {"value": 0},
ebusd-wlan |      "disablehwcload": {"value": 0},
ebusd-wlan |      "remoteControlHcPump": {"value": 0},
ebusd-wlan |      "releaseBackup": {"value": 0},
ebusd-wlan |      "releaseCooling": {"value": 0}}
ebusd-wlan | 2021-10-28 12:27:21.341 [mqtt debug] publish ebusd/f47/currenterror {
ebusd-wlan |      "0": {"name": "error", "value": null},
ebusd-wlan |      "1": {"name": "error", "value": null},
ebusd-wlan |      "2": {"name": "error", "value": null},
ebusd-wlan |      "3": {"name": "error", "value": null},
ebusd-wlan |      "4": {"name": "error", "value": null}}
ebusd-wlan | 2021-10-28 12:27:22.707 [bus debug] ERR: SYN received during receive command, switching to ready
ebusd-wlan | 2021-10-28 12:27:22.816 [update info] received MS cmd: 1008b5110101 / 093b3b0080ff750000ff
ebusd-wlan | 2021-10-28 12:27:22.817 [update notice] received read bai Status01 QQ=10: 29.5;29.5;-;-;58.5;off
ebusd-wlan | 2021-10-28 12:27:22.988 [bus debug] ERR: read timeout during receive command ACK, switching to skip
ebusd-wlan | 2021-10-28 12:27:24.710 [update info] received MS cmd: 1008b5110102 / 06033c78468c8c
ebusd-wlan | 2021-10-28 12:27:24.710 [update notice] received read bai Status02 QQ=10: auto;60;60.0;70;70.0
ebusd-wlan | 2021-10-28 12:27:25.018 [bus info] poll cmd: 3108b509030d1700
ebusd-wlan | 2021-10-28 12:27:25.019 [bus debug] start request 31

ebusd-wlan | 2021-10-28 12:27:36.180 [main debug] performing regular tasks
ebusd-wlan | 2021-10-28 12:27:36.373 [mqtt debug] publish ebusd/bai/Status01 {
ebusd-wlan |      "0": {"name": "temp1", "value": 29.5},
ebusd-wlan |      "1": {"name": "temp1", "value": 29.5},
ebusd-wlan |      "2": {"name": "temp2", "value": null},
ebusd-wlan |      "3": {"name": "temp1", "value": null},
ebusd-wlan |      "4": {"name": "temp1", "value": 58.5},
ebusd-wlan |      "5": {"name": "pumpstate", "value": "off"}}
ebusd-wlan | 2021-10-28 12:27:36.374 [mqtt debug] publish ebusd/bai/FlowTempDesired {
ebusd-wlan |      "temp": {"value": 32.50}}
ebusd-wlan | 2021-10-28 12:27:37.013 [bus info] poll cmd: 3108b509030d4400
ebusd-wlan | 2021-10-28 12:27:37.014 [bus debug] start request 31
ebusd-wlan | 2021-10-28 12:27:37.014 [bus debug] arbitration start with 31
ebusd-wlan | 2021-10-28 12:27:37.094 [bus debug] arbitration won
ebusd-wlan | 2021-10-28 12:27:37.095 [bus debug] arbitration delay 5 micros
ebusd-wlan | 2021-10-28 12:27:37.095 [bus debug] switching from ready to send command
ebusd-wlan | 2021-10-28 12:27:37.132 [bus error] device status: eBUS comm error: framing
ebusd-wlan | 2021-10-28 12:27:37.132 [bus debug] notify request: ERR: read timeout
ebusd-wlan | 2021-10-28 12:27:37.132 [bus error] poll bai WP failed: ERR: read timeout
ebusd-wlan | 2021-10-28 12:27:37.133 [bus debug] ERR: read timeout during send command, switching to skip
ebusd-wlan | 2021-10-28 12:27:38.733 [update info] received MS cmd: 1008b5100900004178ffff00ff00 / 0101
ebusd-wlan | 2021-10-28 12:27:38.734 [update notice] received update-write bai SetMode QQ=10: auto;32.5;60.0;-;0;0;0;0;0;0
ebusd-wlan | 2021-10-28 12:27:41.386 [mqtt debug] publish ebusd/bai/SetMode {
ebusd-wlan |      "hcmode": {"value": "auto"},
ebusd-wlan |      "flowtempdesired": {"value": 32.5},
ebusd-wlan |      "hwctempdesired": {"value": 60.0},
ebusd-wlan |      "hwcflowtempdesired": {"value": null},
ebusd-wlan |      "disablehc": {"value": 0},
ebusd-wlan |      "disablehwctapping": {"value": 0},
ebusd-wlan |      "disablehwcload": {"value": 0},
ebusd-wlan |      "remoteControlHcPump": {"value": 0},
ebusd-wlan |      "releaseBackup": {"value": 0},
ebusd-wlan |      "releaseCooling": {"value": 0}}
ebusd-wlan | 2021-10-28 12:27:42.747 [update info] received MS cmd: 1008b5110101 / 093b3b0080ff750000ff
ebusd-wlan | 2021-10-28 12:27:42.748 [update notice] received read bai Status01 QQ=10: 29.5;29.5;-;-;58.5;off
ebusd-wlan | 2021-10-28 12:27:43.010 [bus info] poll cmd: 3108b509030d3f00
ebusd-wlan | 2021-10-28 12:27:43.011 [bus debug] start request 31
ebusd-wlan | 2021-10-28 12:27:43.011 [bus debug] arbitration start with 31
ebusd-wlan | 2021-10-28 12:27:43.072 [bus debug] arbitration won
ebusd-wlan | 2021-10-28 12:27:43.072 [bus debug] arbitration delay 5 micros
ebusd-wlan | 2021-10-28 12:27:43.072 [bus debug] switching from ready to send command
ebusd-wlan | 2021-10-28 12:27:43.082 [bus debug] send/receive symbol latency 9 ms
ebusd-wlan | 2021-10-28 12:27:43.128 [bus debug] send/receive symbol latency 45 ms
ebusd-wlan | 2021-10-28 12:27:43.140 [bus debug] send/receive symbol latency 11 ms
ebusd-wlan | 2021-10-28 12:27:43.150 [bus debug] send/receive symbol latency 10 ms
ebusd-wlan | 2021-10-28 12:27:43.161 [bus debug] send/receive symbol latency 10 ms
ebusd-wlan | 2021-10-28 12:27:43.173 [bus debug] send/receive symbol latency 12 ms
ebusd-wlan | 2021-10-28 12:27:43.183 [bus debug] send/receive symbol latency 9 ms
ebusd-wlan | 2021-10-28 12:27:43.183 [bus debug] switching from send command to send command CRC
ebusd-wlan | 2021-10-28 12:27:43.194 [bus debug] send/receive symbol latency 10 ms
ebusd-wlan | 2021-10-28 12:27:43.194 [bus debug] switching from send command CRC to receive command ACK
ebusd-wlan | 2021-10-28 12:27:43.198 [bus debug] switching from receive command ACK to receive response
ebusd-wlan | 2021-10-28 12:27:43.243 [bus debug] switching from receive response to receive response CRC
ebusd-wlan | 2021-10-28 12:27:43.244 [bus debug] switching from receive response CRC to send response ACK
ebusd-wlan | 2021-10-28 12:27:43.255 [bus debug] send/receive symbol latency 10 ms
ebusd-wlan | 2021-10-28 12:27:43.255 [update info] sent MS cmd: 3108b509030d3f00 / 0101
ebusd-wlan | 2021-10-28 12:27:43.256 [update notice] sent poll-read bai extWP QQ=31: on
ebusd-wlan | 2021-10-28 12:27:43.256 [bus debug] notify request: done
ebusd-wlan | 2021-10-28 12:27:43.256 [bus debug] switching from send response ACK to send SYN
ebusd-wlan | 2021-10-28 12:27:43.269 [bus debug] send/receive symbol latency 12 ms

salvq avatar Oct 28 '21 12:10 salvq

some of the bus error messages are related to framing during arbitration which should be normal. as long as you can retrieve values from the devices, this is expected

john30 avatar Oct 29 '21 17:10 john30