Need a new search?

If you didn't find what you were looking for, try a new search!

Viewing 3 results - 211 through 213 (of 213 total)
  • Author
    Search Results
  • EfeeEfee
    Participant
      Post count: 13

      okay, komme nun zumindest über den Browser an den Server ran. Neues Projekt übertragen.
      Im EIB bekomme ich ein “?” bei der Phys. Adresse. Hab ich die im ETS nicht gescheit konfiguriert? oder es liegt halt wirklich and der MDT Schnittstelle.

      Naja, einen kleinen SChritt weiter zumindest.

      Danke euch.

      Gruß
      Efee

      hs815hs815
      Participant
        Post count: 1
        #756 In reply to: Firmware Experte 4 |

        Hy Gedia,

        i figured out, that with new kernel you dont nee dhc or hdb anymore..

        it just works with sda…

        thats what i did:

        i updated my old HS3 (on kvm) to the new 4.0
        the major change was the harddisk is now sda and no longer hdc
        i use a suse11.3 64bit (know its not the newest).
        created 4 partitions:
        /dev/sda1               1         132     1060258+  82  Linux swap / Solaris
        /dev/sda2             133        1177     8393962+  83  Linux
        /dev/sda3            1178        1309     1060290    6  FAT16
        /dev/sda4            1310        1441     1060290    6  FAT16

        then i extracted the firmware file from experte 4 (zip) for HS3
        (because i works with my old mac-address)
        therefor i unpacked the inird with
        gzip -dc ../INITRD | cpio -id
        to a dir..

        then i copied the hs dir to the rootpath of my linux
        and when i started i needed to install some python-packages..
        but first i copied all the python-dirs to my linux /usr/lib/python
        there is a PIL dir which is needed..

        then i can start it. With a script.

        *****************************************
        PYTHONPATH=/usr/lib/python/PIL
        export PYTHONPATH
        TZ=CET-1CEST,M3.5.0/2:00,M10.5.0/3:00
        export TZ
        hwclock –hctosys –utc
        setserial /dev/ttyS0 autoconfig
        setserial /dev/ttyS1 autoconfig

        #only needed for serial transfer 1 time:
        #/hs/bin/hs_main trans
        #killall -9 python

        /hs/bin/hs_main main
        reboot
        *********************
        The communication for the first time I did with a nullmodem cable to windows8
        The serialport on the new hs was ttys0…. It also changed…
        Now it works fine…

        on original HS4-hardware there are
        15MB
        110MB
        870MB
        870MB

        all dos formatted, but the do something strange with turbodisk..
        and then start it with loadlin to a ram -image. with busybox

        borkenborken
        Participant
          Post count: 2
          #730 In reply to: HS and USB interface |

          The problem, at least when running the HS as a VM, is that the HS connects to the wrong USB-device.  I also read the posts that this should be possible to alter.

          However, since I was starting the HS by ISO-file mount to the virtual CD-rom, I was not able to edit the file needed (no access to the linux system before the HS main starts.

          A workaround is to make your own KNX IP-GW, by using a Raspbarry PI and the EIBD software. I got that to work, at least I managed to use the ETS to program the KNX-bus through that IP-gw. The HS can then talk to this IP-GW over multicast.

        Viewing 3 results - 211 through 213 (of 213 total)