Add a Master and Slave option to Behringer Wing module

[antotor]

Hello! I use Companion and Wing module, and well be great! Response function - very useful and i use it every day. But Wing - can't send correct data in real time, if count of clients more than 1.

My idea is simply. If we have one Wing and two or more clients. We enable option "Master" on one is client, after that - all data from other clients send through "Master" client. On other clients we enable option "Slave" and type IP adress "Master" client.

Big thank you for companion!

[josephdadams]

Could you use Companion Satellite to accomplish this?

[istnv]

The limitation is in the WING itself and also affects the Behringer remote programs. You can only connect 1 client (iPad, PC, Companion). @josephdadams That would allow multiple Streamdecks, but would kick off any iPads, etc. I have thought about doing something like this because of the limitation. I am swamped for the next few days, though. I may be able to build a variation of the generic-tcp-serial that is tcp<->tcp. The concept is the same. The WING module would need to allow a port # entry to divert the communication through the server. I do not have a WING to test, but adding the port number should not affect the rest of the module.

[antotor]

Could you use Companion Satellite to accomplish this?

What is companion satellite? I use few instances of stream deck and companion (7 item). We use stream deck and companion as intercom panels.

UPD. I install companion Satellite and test it. Its nice solution for us, but have 2 problems. 1 - its insecure solution, all users have all buttons and can use it. 2 - its not a fail safe solution. If main computer with installed Companion is crash - all network dont work.

[antotor]

The limitation is in the WING itself and also affects the Behringer remote programs. You can only connect 1 client (iPad, PC, Companion). @josephdadams That would allow multiple Streamdecks, but would kick off any iPads, etc. I have thought about doing something like this because of the limitation. I am swamped for the next few days, though. I may be able to build a variation of the generic-tcp-serial that is tcp<->tcp. The concept is the same. The WING module would need to allow a port # entry to divert the communication through the server. I do not have a WING to test, but adding the port number should not affect the rest of the module.

Sounds like a good plan! I ready to test it)

[istnv]

Looking over this, it is not as simple as I thought. This module 'subscribes' to the console data, where the console automatically sends data to the module when things change on the console. The server/concentrator would need to filter the data to know if a client wants these notifications.

[antotor]

Looking over this, it is not as simple as I thought. This module 'subscribes' to the console data, where the console automatically sends data to the module when things change on the console. The server/concentrator would need to filter the data to know if a client wants these notifications.

May be send all data to clients? And filter on clients?

[istnv]

There is no way to filter the iPad or other such control programs. The data flow used by the companion module might crash the iPad.

[antotor]

There is no way to filter the iPad or other such control programs. The data flow used by the companion module might crash the iPad.

Hello! We don't use iPad, only PC. But we need this option for use Companion with Wing. Please, create this option.

[Spartan-II-117]

this should no longer be required on recent firmware