Viewing 15 posts - 1 through 15 (of 66 total)
  • Author
    Posts
  • xxxxxx
    Participant
      Post count: 68

      xxx

      • This topic was modified 1 year, 4 months ago by RoellerRoeller.
      • This topic was modified 11 months, 2 weeks ago by xxxxxx.
      m00m00
      Participant
        Post count: 40

        I can’t really help with the baos device as I never used it, but regarding the slow download:
        What do you define as slow? Some devices can take 30-90 seconds for a full download because KNX is a slow (but resilient) bus.

        Are you using the baos 773 as an IP interface for programming the bus? The device supports long frames which means its the fastest way of programming.

        I don’t think you need NAT for a local communication from ETS to the integrated IP Interface of the baos 773. (If that’s what you’re trying to do) you should be able to connect via IP tunneling if you enter the IP.
        Are you sure you entered the correct IP?

        Edit: you can use a tool like advanced IP scanner to verify the IP you are trying to connect to is really the weinzierl 773. I don’t know if this device has KNX Secure, that could also be an issue (KNX IP secure could interfere with you trying to connect)

        • This reply was modified 1 year, 5 months ago by m00m00.
        sinn3rsinn3r
        Participant
          Post count: 367

          ETS6 manages connections to the bus per project, with ETS5 this was a ETS-wide setting.
          In the top right of your opened project there is a dropdown (showing “automatic” by default) which shows the way ETS will connect to the bus.
          There are usually 2 ways to do so:
          a) directly to the lan interface (ETS should list this with the found IP address of the KNX lan interface and the port 3671
          b) by multicasting to the network via your local lan interface of the computer (which shows something like 224.0.23.12)
          The second way is usually the easiest way to connect, but because of your vitualized windows machine the virtual network settings may interfere with that. Be sure to have the network of the virtualization to connect to your local lan network and not block multicast or broadcast.
          I never used the BAOS 773 (which is an IP router, not just an IP interface) but it looks like an interesting device, offering access to all group addresses by web service. When using Home Assistant, ioBroker, gira Homeserver, … you won’t need that though.

          And yes, welcome to the slow world of KNX ;)
          Full application updates (or the first programming) may take a while, up to 90 seconds are not a rare thing. Later you can send updates to the devices which is faster. Firmwareupdates over the KNX bus can be even slower, for example my weather station takes 7 or 8 minutes for an update!

          xxxxxx
          Participant
            Post count: 68

            xxx

            • This reply was modified 1 year, 5 months ago by xxxxxx.
            • This reply was modified 1 year, 5 months ago by xxxxxx.
            • This reply was modified 1 year, 5 months ago by xxxxxx.
            • This reply was modified 11 months, 2 weeks ago by xxxxxx.
            sinn3rsinn3r
            Participant
              Post count: 367

              Multi-Touch Pro: Hmm, I never saw it in action but the screen resolution looks not very good. At least it seems to be fast responding.
              As for the price, I don’t think it’s expensive compared to other devices of this type, but I think vendors need to pay alot of money to KNX.

              Hacking KNX: When portforwarding port 3671 from the internet to your KNX IP router, your whole installation can be “hacked”, in fact they do not hack the devices but set random device passwords and you cannot program the devices anymore. And yes