Eos Family Consoles

Eos Family Disabling OSC Tx or OSC Rx should close TCP connections

Date sktusing
Date Tue, Mar 8 2022 7:53 PM
Replies 3 replies
Subscribers 189 subscribers
Views 1065 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.

Top Replies

dsmurfin over 2 years ago in reply to Matt Pumplin +1

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…

Parents

sstaub over 2 years ago

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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

sstaub over 2 years ago

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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

No Data

Top

Related