Ankündigung

Einklappen
Keine Ankündigung bisher.

Raspberry 3 - Siemens USB/KNX Interface Verbindungsprobleme

Einklappen
X
 
  • Filter
  • Zeit
  • Anzeigen
Alles löschen
neue Beiträge

    Raspberry 3 - Siemens USB/KNX Interface Verbindungsprobleme

    So Leute,

    nachdem ich es geschafft habe endlich knxd zum laufen zu bekommen habe ich jetzt aber trotzdem ein Problem.
    Folgendes ist verbaut:
    Raspberry PI 3 -> Siemens USB-Interface N148/11

    Die Konfigurationsdatei die aktuell geladen ist:

    Code:
    # configuration for knxd.service
    
    #KNXD_OPTS="-e 0.0.1 -E 0.0.2:8 -u /tmp/eib -b ip:"
    
    #KNXD_OPTS="--eibaddr=1.1.128 --client-addrs=1.1.129:8 -d -D -T -R -S -i --listen-local=/tmp/knx -b usb:"
    
    #KNXD_OPTS="-e 0.0.100 -E 0.0.101:7 -D -T -R -S -i 6720 -b usb:1:4:0:0"
    
    KNXD_OPTS="-e 1.1.128 -E 1.1.128:8 -DTRS -b usb:"
    
    
    
    
    
    
    
    # configuration for knxd.service using new configuration format in /etc/knxd.ini
    
    # use only this line if you used knxd_args to convert your old startup options
    
    # KNXD_OPTS=/etc/knxd.ini
    
    
    
    
    # The default options are "-u /tmp/eib -b ip:"
    
    # which tell knxd to route between all of
    
    #  /tmp/eib (legacy socket (-u))
    
    #  multicast client (-b ip:).
    
    # knxd's own bus address is 0.0.1; it will assign 0.0.2…0.0.9 to clients.
    
    # The knxd.socket file also tells knxd to listen to
    
    #  /run/eib (socket activation via systemd)
    
    #  TCP port 6720 (socket activation via systemd)
    
    # You *need* the -e option. Clients cannot connect without "-E".
    
    
    
    
    # You can read knxd's logs with
    
    # $ journalctl -u knxd --since "10 min ago"
    
    # (or whatever). See the manpage for details.
    
    # You need to be a member of the "adm" group.
    
    # Add "-f9 -t1023" to the beginning of the command line for extensive logging.
    
    
    
    
    # *** DO NOT use "-u" / "-u /run/knx" or "-i" / "-i 6720" here.
    
    # Systemd already does that on behalf of knxd, via 'knx.socket'.
    
    
    
    
    # *** DO NOT use both "-RS" and "-b ip:" (unless you specify a
    
    # different multicast address on one of them). You'd create a loop.
    
    
    
    
    # If you have KNX hardware on a serial port or USB, add the appropriate
    
    # "-b TYPE:…" option. In this case, you probably want to set up a multicast
    
    # server, not a client (i.e. use "-D -T -R -S", not "-b ip:").
    
    # DO NOT use both.
    
    #
    
    # If your KNX hardware is a KNX/IP gateway that doesn't do multicast,
    
    # use "-b ipt:192.168.1.2" (or its DNS name) to talk to it.
    
    #
    
    # KNX MUST NOT have more than one path between any two devices. Thus,
    
    # you need to make sure that the KNX/IP gateway does not route multicast
    
    # before you use both "-S" and "-b ipt:".
    
    
    
    
    # The default bus address of knxd is 0.0.1. If that's in use in your KNX
    
    # network (or if you run more than one knxd on your network), set a
    
    # different address, for example "-e 7.0.99".
    
    
    
    
    # You should have a block of free addresses on your KNX bus which knxd can
    
    # assign to clients: "-E 7.0.100:28" will use 7.0.100 through 7.0.127.
    
    # If no such range is given, or if it's full, knxd uses its own address.
    
    # That mostly works, but separate addresses are much better.
    
    
    
    
    # Run `knxd --help` to get a complete list of available options and drivers.
    An sich funktioniert es, jedoch schaut mein Log so aus:

    Code:
    Dez 06 09:27:47 openHABianPi systemd[1]: knxd.service: Service hold-off time over, scheduling restart.
    
    Dez 06 09:27:47 openHABianPi systemd[1]: Stopped KNX Daemon.
    
    Dez 06 09:27:47 openHABianPi systemd[1]: Starting KNX Daemon...
    
    Dez 06 09:27:47 openHABianPi systemd[1]: Started KNX Daemon.
    
    Dez 06 09:27:53 openHABianPi systemd[1]: Stopping KNX Daemon...
    
    Dez 06 09:27:54 openHABianPi systemd[1]: Stopped KNX Daemon.
    
    Dez 06 09:27:54 openHABianPi systemd[1]: Starting KNX Daemon...
    
    Dez 06 09:27:54 openHABianPi systemd[1]: Started KNX Daemon.
    
    Dez 06 09:28:03 openHABianPi knxd[2633]: E00000059: [22:A.usb] EMI_common: send while waiting (15)
    
    Dez 06 09:28:13 openHABianPi knxd[2633]: E00000055: [15:A.usb] Driver timed out trying to send (A.usb)
    
    Dez 06 09:28:13 openHABianPi systemd[1]: knxd.service: Main process exited, code=exited, status=1/FAILURE
    
    Dez 06 09:28:13 openHABianPi systemd[1]: knxd.service: Unit entered failed state.
    
    Dez 06 09:28:13 openHABianPi systemd[1]: knxd.service: Failed with result 'exit-code'.
    
    Dez 06 09:28:23 openHABianPi systemd[1]: knxd.service: Service hold-off time over, scheduling restart.
    
    Dez 06 09:28:23 openHABianPi systemd[1]: Stopped KNX Daemon.
    
    Dez 06 09:28:23 openHABianPi systemd[1]: Starting KNX Daemon...
    
    Dez 06 09:28:23 openHABianPi systemd[1]: Started KNX Daemon.
    
    Dez 06 09:29:17 openHABianPi knxd[2686]: E00000059: [22:A.usb] EMI_common: send while waiting (17)
    
    Dez 06 09:29:27 openHABianPi knxd[2686]: E00000055: [15:A.usb] Driver timed out trying to send (A.usb)
    
    Dez 06 09:29:27 openHABianPi knxd[2686]: F00000105: [15:A.usb] Link down, terminating
    
    Dez 06 09:29:27 openHABianPi systemd[1]: knxd.service: Main process exited, code=exited, status=1/FAILURE
    
    Dez 06 09:29:27 openHABianPi systemd[1]: knxd.service: Unit entered failed state.
    
    Dez 06 09:29:27 openHABianPi systemd[1]: knxd.service: Failed with result 'exit-code'.
    
    Dez 06 09:29:37 openHABianPi systemd[1]: knxd.service: Service hold-off time over, scheduling restart.
    
    Dez 06 09:29:37 openHABianPi systemd[1]: Stopped KNX Daemon.
    
    Dez 06 09:29:37 openHABianPi systemd[1]: Starting KNX Daemon...
    
    Dez 06 09:29:37 openHABianPi systemd[1]: Started KNX Daemon.
    
    Dez 06 09:29:43 openHABianPi knxd[2746]: E00000059: [22:A.usb] EMI_common: send while waiting (3160372)
    
    Dez 06 09:29:53 openHABianPi knxd[2746]: E00000055: [15:A.usb] Driver timed out trying to send (A.usb)
    
    Dez 06 09:29:54 openHABianPi knxd[2746]: F00000105: [15:A.usb] Link down, terminating
    
    Dez 06 09:29:54 openHABianPi systemd[1]: knxd.service: Main process exited, code=exited, status=1/FAILURE
    
    Dez 06 09:29:54 openHABianPi systemd[1]: knxd.service: Unit entered failed state.
    
    Dez 06 09:29:54 openHABianPi systemd[1]: knxd.service: Failed with result 'exit-code'.
    
    Dez 06 09:30:04 openHABianPi systemd[1]: knxd.service: Service hold-off time over, scheduling restart.
    
    Dez 06 09:30:04 openHABianPi systemd[1]: Stopped KNX Daemon.
    
    Dez 06 09:30:04 openHABianPi systemd[1]: Starting KNX Daemon...
    
    Dez 06 09:30:04 openHABianPi systemd[1]: Started KNX Daemon.
    Sprich die Verbindung wird ständig unterbrochen und neu aufgebaut.

    Hat jemand dafür eine Erklärung?

    Oder muss ich in meiner Konfigurationsdatei was ändern?

    #2
    Hallo,
    Ich versuche gerade auch mal wieder von eibd auf den neuesten knxd umzustellen und habe ein sehr ähnliches Problem.
    Threads dazu gibt es mittlerweile hier und auf git mehrere. Soweit ich es verstehe versteht sich knxd nur schlecht
    mit USB Schnittstellen. Bei mir ist es Hager und Merten. Geht beides nicht. Bisher konnte das Problem wohl
    nicht gefunden werden. Wenns was Neues gibt belehrt mich bitte eines Besseren. Gruß,

    Michael

    Kommentar


      #3
      Hallo alle zusammen,

      ich wollte mal nachfragen, ob es in dieser Sache schon Neuigkeiten gibt. Ich habe dasselbe Problem mit einer Feller USB/KNX Schnittstelle am Raspi 3. Interessanterweise tritt das Problem immer nur nach dem Start meines python Programms auf. Ich starte den Service dann manuell wieder (systemd start knxd.service) und danach meine Applikation. 3-5 Versuche später läuft's dann und funktioniert auch ohne weitere Probleme. Sehr seltsam! Mit dem Vorgänger (eibd) des knxd trat dieses Problem übrigens nie auf.

      Fyi: Das steht dann immer im daemon.log:
      ...
      Feb 15 14:13:16 raspi_56 systemd[1]: Started KNX Daemon.
      Feb 15 14:13:22 raspi_56 knxd[1544]: E00000059: [23:C.usb] EMI_common: send while waiting (1993512900)
      Feb 15 14:13:32 raspi_56 knxd[1544]: E00000055: [15:C.usb] Driver timed out trying to send (C.usb)
      Feb 15 14:13:32 raspi_56 knxd[1544]: F00000105: [15:C.usb] Link down, terminating
      Feb 15 14:13:32 raspi_56 systemd[1]: knxd.service: Main process exited, code=exited, status=1/FAILURE
      Feb 15 14:13:32 raspi_56 systemd[1]: knxd.service: Unit entered failed state.
      Feb 15 14:13:32 raspi_56 systemd[1]: knxd.service: Failed with result 'exit-code'.
      ...

      Fehler tritt mit 0.14.25 und 0.14.29 auf.

      Wolfgang

      p.s. Die emi timeoutvelängerung habe ich aktiviert.

      Kommentar

      Lädt...
      X