Ankündigung

Einklappen
Keine Ankündigung bisher.

- √ - Proplems Eibd on Raspberry?

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

    - √ - Proplems Eibd on Raspberry?

    Hello.
    I've installed the EIBD on my raspberry pi with wheezy, newest build...
    Done like described here:
    SourceForge.net: Install Eibd/Linknx/knxweb - linknx
    When coming to the line, where i can test the EIBD i get an error.
    I connect using TCP/IP, by doing "eibd -d -D -S -T -i ipt:192.168.1.10:3671"
    I don't get any errors, so i think it accepts my command. But sometimes i get an error "eibd: error when loading shared libraries: libpthsem.so.20", depending on which directory i am in when executing the eibd command - is that correct? If i am in the pthsem-2.0.8 it works.
    I try to use the groupswrite to send a ON/OFF command to my KNX installation:
    groupswrite ip:127.0.0.1 1/0/0 1 i get reply: "Send Request" - and nothing happens.
    groupswrite ip:127.0.0.1 1/0/0 1 1 i get reply: "usage: groupswrite url eibaddr val: Succes"
    But nothing happens - please help

    #2
    Hi

    Execute "ldconfig" on the command line, then try again. If it is not enough, we need more info about your installation (directories where EIBD and PTHSEM are installed, etc).

    Cheers, Martin

    Kommentar


      #3
      Zitat von Sipple Beitrag anzeigen
      Hi

      Execute "ldconfig" on the command line, then try again. If it is not enough, we need more info about your installation (directories where EIBD and PTHSEM are installed, etc).

      Cheers, Martin
      Hello. I've tried the ldconfig under root, it took a moment, then i tried to start eibd with the command as described and the: "groupswrite ipt:localhost 1/0/0 1 1 it says "usage: groupswrite url eibaddr val: succes" But still nothing happens.

      My system is a Raspberry PI with Wheezy installed.

      the pthsem-2.0.8 folder is placed under pi@raspberrypi~$ - The EIBD installation folder do i not know, i ran theese commands:

      apt-get install gcc g++ make
      apt-get install liblog4cpp5-dev
      apt-get install libesmtp-dev
      apt-get install libmysqlclient-dev
      apt-get install liblua5.1-0-dev
      apt-get install dpkg
      apt-get install libcurl4-openssl-dev
      apt-get install build-essential file autoconf dh-make debhelper devscripts fakeroot gnupg


      And theese for the pthsem:
      $ wget http://downloads.sourceforge.net/sou...m_2.0.8.tar.gz

      $ tar -xzvf pthsem_2.0.8.tar.gz
      $ cd pthsem-2.0.8/
      $ ./configure
      $ make
      (sudo) $ make install
      $ export LD_LIBRARY_PATH=/usr/local/lib
      $ cd ..

      Kommentar


        #4
        delete the "1" at the end and use ip: instead of ipt in the groupswrite command.

        e.g groupswrite ip:localhost 2/1/17 1

        should work

        Kommentar


          #5
          Zitat von Sipple Beitrag anzeigen
          delete the "1" at the end and use ip: instead of ipt in the groupswrite command.

          e.g groupswrite ip:localhost 2/1/17 1

          should work
          I've tried... doesn't work....

          I've read somewhere, that i need to add a route to the multicast address 224.xxx.xx? is that true?

          Kommentar


            #6
            No. Not if you use an IP Interface with Tunneling (that's the meaning of "ipt" in the eibd start command. What does

            ps -ef | grep eib

            show?

            Kommentar


              #7
              Zitat von Sipple Beitrag anzeigen
              No. Not if you use an IP Interface with Tunneling (that's the meaning of "ipt" in the eibd start command. What does

              ps-ef | grep eib

              show?
              if i do ps ef | grep eibd i get:


              pi@raspberrypi ~ $ ps ef | grep eib
              3226 pts/0 S+ 0:00 \_ grep --color=auto eibTERM=xterm SHELL=/bin/bash SSH_CLIENT=192.168.50.125 50117 22 SSH_TTY=/dev/pts/0 USER=pi LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00i=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01r=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42w=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31: *.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:* .tlz=01;31:*.txz=01;31:*.zip=01;31:*.z=01;31:*.Z=0 1;31:*.dz=01;31:*.gz=01;31:*.lz=01;31:*.xz=01;31:* .bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.t z=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war= 01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.ace=01 ;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31 :*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35: *.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*. xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.p ng=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pc x=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v =01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4= 01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01 ;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35 :*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35: *.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xw d=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv= 01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00 ;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00; 36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36 :*.ra=00;36:*.wav=00;36:*.axa=00;36:*.oga=00;36:*. spx=00;36:*.xspf=00;36: MAIL=/var/mail/pi PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games PWD=/home/pi LANG=en_GB.UTF-8 SHLVL=1 HOME=/home/pi LOGNAME=pi SSH_CONNECTION=192.168.50.125 50117 192.168.50.6 22 _=/bin/grep

              Kommentar


                #8
                MINUS ef!

                ps -ef | grep eib

                example output:

                Code:
                root      2688     1  0 Feb13 ?        03:10:30 /usr/bin/eibd -e 1.1.242 -c -S -D -i -T -d -u --pid-file=/var/run/eibd.pid ipt:192.168.178.39
                root     16575 16527  0 16:43 pts/1    00:00:00 grep eib

                Kommentar


                  #9
                  Zitat von Sipple Beitrag anzeigen
                  MINUS ef!

                  ps -ef | grep eib
                  Sorry... Comes here:


                  pi@raspberrypi ~ $ ps -ef | grep eibd
                  root 3021 1 0 14:25 ? 00:00:02 eibd -d -D -S -T -i ipt:192.168.50.10:3671
                  pi 3230 3083 0 15:43 pts/0 00:00:00 grep --color=auto eibd

                  Kommentar


                    #10
                    ok, eibd is running. Stop it with kill -9 3021 and then restart the following way:

                    eibd -e 1.1.242 -c -S -D -i -T -d -u --pid-file=/var/run/eibd.pid ipt:192.168.50.10


                    Then check again with ps -ef | grep eib.
                    If it is running, then try the groupswrite again. Post the complete terminal in- and output from the kill command to the groupswrite if it doesn't work.

                    Kommentar


                      #11
                      Zitat von Sipple Beitrag anzeigen
                      ok, eibd is running. Stop it with kill -9 3021 and then restart the following way:

                      eibd -e 1.1.242 -c -S -D -i -T -d -u --pid-file=/var/run/eibd.pid ipt:192.168.50.10


                      Then check again with ps -ef | grep eib.
                      If it is running, then try the groupswrite again. Post the complete terminal in- and output from the kill command to the groupswrite if it doesn't work.
                      It still doesn't work... here's a copy/paste from SSH


                      pi@raspberrypi ~ $ sudo kill -9 3021
                      pi@raspberrypi ~ $ ps -ef | grep eibd
                      pi 3249 3083 0 17:21 pts/0 00:00:00 grep --color=auto eibd
                      pi@raspberrypi ~ $ eibd -e 1.1.242 -c -S -D -i -T -d -u --pid-file=/var/run/eibd.pid ipt:192.168.50.10
                      pi@raspberrypi ~ $ ps -ef | grep eibd
                      pi 3251 1 0 17:21 ? 00:00:00 eibd -e 1.1.242 -c -S -D -i -T -d -u --pid-file=/var/run/eibd.pid ipt:192.168.50.10
                      pi 3253 3083 0 17:21 pts/0 00:00:00 grep --color=auto eibd
                      pi@raspberrypi ~ $ groupswrite ip:localhost 1/0/0 0
                      Send request
                      pi@raspberrypi ~ $ groupswrite ip:localhost 1/0/0 1
                      Send request
                      pi@raspberrypi ~ $


                      I haven't done any chmods during the installation....

                      Kommentar


                        #12
                        looks exactly as it is supposed to look.

                        have you checked with the ETS busmonitor whether the write request appears on the knx bus? What is the groupaddress 1/0/0 in your knx system?

                        On the other hand: you asked in athother thread which is better: linknx or smarthome.py.
                        Forget linknx. smarthome.py together with smartVISU is by far the best combination for a RPi and it will solve your eibd problem anyway, since there is a perfect image for the RPi.

                        https://github.com/mknx/smarthome/wiki/SmartHome.pi

                        Kommentar


                          #13
                          Zitat von Sipple Beitrag anzeigen
                          looks exactly as it is supposed to look.

                          have you checked with the ETS busmonitor whether the write request appears on the knx bus? What is the groupaddress 1/0/0 in your knx system?

                          On the other hand: you asked in athother thread which is better: linknx or smarthome.py.
                          Forget linknx. smarthome.py together with smartVISU is by far the best combination for a RPi and it will solve your eibd problem anyway, since there is a perfect image for the RPi.

                          https://github.com/mknx/smarthome/wiki/SmartHome.pi
                          Yes i checked my bus monitor, the telegram doesn't show up at all... the 1/0/0 in a bit on/off...

                          Okay, thanks - that answered my question in the other thread... The only reason for installing eibd standalone was for the linknx - but if smarthome is better, then i simply just install that image to my sd card right now

                          Kommentar


                            #14
                            Zitat von Sipple Beitrag anzeigen
                            looks exactly as it is supposed to look.

                            have you checked with the ETS busmonitor whether the write request appears on the knx bus? What is the groupaddress 1/0/0 in your knx system?

                            On the other hand: you asked in athother thread which is better: linknx or smarthome.py.
                            Forget linknx. smarthome.py together with smartVISU is by far the best combination for a RPi and it will solve your eibd problem anyway, since there is a perfect image for the RPi.

                            https://github.com/mknx/smarthome/wiki/SmartHome.pi
                            This is very very strange....
                            I've installed the image you linked to, on my PI, booted everthing looks fine, changed
                            # /etc/default/eibd
                            #EIB_ARGS="--daemon --Server --Tunnelling --Discovery --GroupCache --listen-tcp"
                            #EIB_ADDR="0.0.1"
                            #EIB_IF="tpuarts:/dev/ttyAMA0"

                            TO
                            # /etc/default/eibd
                            #EIB_ARGS="--daemon --Server --Tunnelling --Discovery --GroupCache --listen-tcp"
                            #EIB_ADDR="0.0.1"
                            EIB_IF="ipt:192.168.50.10"

                            Then stopped and started eibd again:

                            admin@smarthome:
                            /usr/smarthome$ groupswrite ip:localhost 1/0/0 0
                            Send request
                            admin@smarthome:/usr/smarthome$


                            Nothing happens...

                            Currently my IP Router does also connect with a Siemens PLC doing some KNX logic, but that shouldn't have anything to say?

                            Kommentar


                              #15
                              I've found the problem...

                              When trying to connect from ETS4 to my IP interface, i must select 224.0.23.12 over KNX IP Routing.... If i select traditionally TCP and the IP adress i get an reply saying that the interface is alive, but doesn't allow any more connections...

                              Then i tried disconnect the Siemens PLC rebooted the IP interface and then it all works, if i connect from my PC to ETS via KNX/IP Routing, and not traditional IP....

                              Does that make any sense? Can't the IP Router have more than 1 connecteD?

                              Kommentar

                              Lädt...
                              X