Ankündigung

Einklappen
Keine Ankündigung bisher.

ISE Remote Access Verbindungsabbrüche

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

    ISE Remote Access Verbindungsabbrüche

    I am using an ISE Remote Access IP Interface to access my KNX installation. It works, but very frequent connection drops occur. Like every few seconds. Sometimes the connection lasts for a minute or so. It reconnects every time, but the GUI becomes unreliable and I am sure information is lost...

    The ISE has three IP tunneling interfaces and my (very naive) hunch is, that it is about those. In one of the logs of the ISE I have found "ERROR KnxStack.Ip.IpConnectionInfo, Failed to select the primary network interface. (KnxNetIp/IpConnectionInfoLinux.cpp:253)"

    Also, at times, the ETS reports that there are no more connections available, suggesting, that Edomi has taken all three.

    The anatomie of a reconnect with the following disconnect looks like this:

    Code:
    2018-12-28 18:18:17 198556 3139 OK CE > | DESCRIPTION_REQUEST an 192.168.1.2:3671 / Raw: 06100203000E0801c0a80107c350
    2018-12-28 18:18:17 209492 3139 OK CE < | DESCRIPTION_RESPONSE / Status: Ok / Name: ise KNX Remote Access / PA: 15.15.255 / MAC: a41163a009a9 / Raw: 06100204004636010200ffff0000007c12500031e000170ca4 1163a009a9697365204b4e582052656d6f7465204163636573 730000000000000000000a020201030204010701
    2018-12-28 18:18:17 219798 3139 OK CE > | CONNECT_REQUEST an 192.168.1.2:3671 / Raw: 06100205001A0801c0a80107c3500801c0a80107c351040402 00
    2018-12-28 18:18:17 240802 3139 OK CE < | CONNECT_RESPONSE / CE: 192.168.1.7:50000 - 192.168.1.2:3671 / DE: 192.168.1.7:50001 - 192.168.1.2:3671 / Tunnel-PA: 15.15.254 / ChannelID: 1 / Raw: 06100206001401000801c0a801020e570404fffe
    2018-12-28 18:18:17 251245 3139 OK CE > | CONNECTIONSTATE_REQUEST / Raw: 06100207001001000801c0a80107c350
    2018-12-28 18:18:17 262382 3139 OK CE < | CONNECTIONSTATE_RESPONSE / Raw: 0610020800080100
    ... some more of those, removed for the sake of brevity...
    2018-12-28 18:19:02 324173 3139 OK CE > | CONNECTIONSTATE_REQUEST / Raw: 06100207001001000801c0a80107c350
    2018-12-28 18:19:02 334753 3139 OK CE < | CONNECTIONSTATE_RESPONSE / Raw: 0610020800080100
    2018-12-28 18:19:03 414520 3139 ERROR DE < | TUNNELING_REQUEST / ErrMsg: Unbekannter Fehler / Raw: 06100420002304010000290a06048d69b0ef800241a8bce010 01020105008041ec1893
    2018-12-28 18:19:04 359622 3139 ERROR DE < | TUNNELING_REQUEST / ErrMsg: Unbekannter Fehler / Raw: 06100420002304010000290a06048d69b0ef800241a8bce010 01020105008041ec1893
    2018-12-28 18:19:05 327428 3139 OK CE > | CONNECTIONSTATE_REQUEST / Raw: 06100207001001000801c0a80107c350
    2018-12-28 18:19:05 338063 3139 OK CE < | CONNECTIONSTATE_RESPONSE / Raw: 0610020800080100
    2018-12-28 18:19:05 358669 3139 ERROR CE < | DISCONNECT_REQUEST / Raw: 06100209001001000801c0a801020e57
    2018-12-28 18:19:05 369152 3139 OK CE > | DISCONNECT_REQUEST / Raw: 06100209001001000801c0a80107c350
    2018-12-28 18:19:05 369483 3139 ERROR KNX-Verbindung verloren.
    Is Edomi equipped to deal with this scenario? What can I do?

    Sandro
    Zuletzt geändert von kordnas; 28.12.2018, 21:18.

    #2
    Seems there is a kind of incompatibilty between EDOMI and the ISE. I would probably try to install eibd on your EDOMI server and let eibd connect to your ISE and EDOMI to the eibd. There is a tutorial in the EDOMI wiki, how to install and configure eibd.

    Kommentar


      #3
      I have looked at the eibd installation. As the Telekom hasn't been able to provide internet access, I am currently stuck with a LTE hotspot and a router, which is not connected to the internet. The Edomi server, thus isn't able to access the internet and it's too much of a hassle to get the installation going from here.

      As much as I'd like to get this to work, I'll report, once the Edomi server is able to talk to the outside world

      Thanks

      Kommentar


        #4
        Wouldn't it be more feasible just to get Edomi up and running and solve remaining KNX related problems with your local telco, network admin or electrician?
        I mean: if Edomi is running fine all is cool. If your KNX installation ist not, it shouldn't be worth a thread in the Edomi forum?

        Kommentar


          #5
          Everything is working fine. It is just limited to my LAN

          So I see this this very much as a Edomi specific issue. The solution might be within Edomi, eibd or the ISE IP interface though. Or all of them. That I don't know

          Kommentar


            #6
            I was not able to let go of it and dug some more O:-)

            I noticed that the disconnect always happened at specific times. More specifically the log entries always showed up at 23, 44 and 59 seconds into the minute.

            Turns out, that some temperature values, that were being send onto the bus in 1 minute intervals were the culprit for the connection losses. What could be the explanation for this? Could that be a Sequence counter issue? Just closing the ETS, had not helped, prior to that.

            The idle connection seems stable now. But when I operate my visualization, disconnects still occur . There are no more regular telegramms and the ETS is shut down.

            Setting a KO to 1 and 0 in quick succession looks like this now (done twice). There was no noticeable delay in the execution of the write requests
            2019-01-04 23:29:35 435197 1504 OK DE > | TUNNELING_REQUEST:L_Data.req / Typ: Write / SeqCounter: 0 / PA: 1.0.5 / GA: 1/1/5 = 1 / Prio: 0 / Raw: 061004200015040100001100BCE010050905010081
            2019-01-04 23:29:35 447515 1504 OK DE < | TUNNELING_ACK / SeqCounter: 0 (0) / Raw: 06100421000a04010000
            2019-01-04 23:29:35 459359 1504 ERROR DE < | TUNNELING_REQUEST / ErrMsg: Unbekannter Fehler / Raw: 06100420001f040100002e0a0604008d40df800244d7bce010 050905010081
            2019-01-04 23:29:35 856571 1504 OK CE > | CONNECTIONSTATE_REQUEST / Raw: 06100207001001000801c0a80107c350
            2019-01-04 23:29:35 867579 1504 OK CE < | CONNECTIONSTATE_RESPONSE / Raw: 0610020800080100
            2019-01-04 23:29:35 920665 1504 OK DE > | TUNNELING_REQUEST:L_Data.req / Typ: Write / SeqCounter: 1 / PA: 1.0.5 / GA: 1/1/5 = 0 / Prio: 0 / Raw: 061004200015040101001100BCE010050905010080
            2019-01-04 23:29:35 931633 1504 OK DE < | TUNNELING_ACK / SeqCounter: 1 (1) / Raw: 06100421000a04010100
            2019-01-04 23:29:36 348330 1504 OK DE > | TUNNELING_REQUEST:L_Data.req / Typ: Write / SeqCounter: 2 / PA: 1.0.5 / GA: 1/1/5 = 1 / Prio: 0 / Raw: 061004200015040102001100BCE010050905010081
            2019-01-04 23:29:36 359181 1504 OK DE < | TUNNELING_ACK / SeqCounter: 2 (2) / Raw: 06100421000a04010200
            2019-01-04 23:29:36 467417 1504 ERROR DE < | TUNNELING_REQUEST / ErrMsg: Unbekannter Fehler / Raw: 06100420001f040100002e0a0604008d40df800244d7bce010 050905010081
            2019-01-04 23:29:36 723819 1504 OK DE > | TUNNELING_REQUEST:L_Data.req / Typ: Write / SeqCounter: 3 / PA: 1.0.5 / GA: 1/1/5 = 0 / Prio: 0 / Raw: 061004200015040103001100BCE010050905010080
            2019-01-04 23:29:36 735375 1504 OK DE < | TUNNELING_ACK / SeqCounter: 3 (3) / Raw: 06100421000a04010300
            2019-01-04 23:29:37 466476 1504 ERROR CE < | DISCONNECT_REQUEST / Raw: 06100209001001000801c0a801020e57
            2019-01-04 23:29:37 477744 1504 OK CE > | DISCONNECT_REQUEST / Raw: 06100209001001000801c0a80107c350
            2019-01-04 23:29:37 478650 1504 ERROR KNX-Verbindung verloren.
            For the last log, I have turned off the „automatic reconnect on sequence counter issues option“

            Regards
            Zuletzt geändert von kordnas; 05.01.2019, 08:09.

            Kommentar


              #7
              Based on what I learned I started over in another thread

              https://knx-user-forum.de/forum/proj...-schnittstelle

              Kommentar

              Lädt...
              X