• Date
    sktusing
  • Date
  • Replies 3 replies
  • Subscribers 189 subscribers
  • Views 1064 views
  • Users 0 members are here

Disabling OSC Tx or OSC Rx should close TCP connections

Currently, disabling OSC Tx and/or OSC Rx does not close TCP connections. This is a bit confusing, as the port stays open, but Eos does not transmit or act on incoming messages. Because of this, users are not notified that they're now unable to transmit or receive information from Eos.

It would be great if Eos just closed the connection.

  • Some users may be relying on the connection staying open so there is no delay between enabling OSC RX and messages coming in (waiting for the handshake).  

    This will require some consideration.  In the meantime I might output a "Closing" / "Opening" message as part of a toggle macro for OSC Rx / Tx.

  • Maybe there should an extra switch for enabling the additional TCP ports.
    The TCP port 3032 should used internal for remotes.
    The TCP port 3037 is for external remotes, both can enabled/disabled in ECU.

  • in reply to Matt Pumplin

    Possibly a better alternative to closing the socket may actually be for Eos to send these messages.

    At present on initial connect, you can flag 'able to communicate' from receipt of /show/name or something like that, but that message doesn't get sent after Rx/Tx is subsequently disabled, then enabled.

    If Eos always sent a message containing the Rx/Tx status on initial TCP connect, and every time either of those toggles was changed that would be super beneficial, as you could track the status from that. This should be sent regardless of the Rx/Tx setting.

Related

www.etcconnect.com