<aside> ℹ️

This page is for COGS 5.11 and later. Using an earlier version? See TCP (before 5.11).

</aside>

COGS can send and receive low-level messages over the TCP protocol with other machines on your network, such as projectors, show controllers, media servers or custom-built props.

Each machine COGS talks to is set up as a TCP device. A device can either be connected to by COGS, or connect to COGS itself and stay connected.

Enable TCP

In the Build view, open Show Settings and switch on TCP under Features. A TCP panel appears on the left.

01-enable-tcp.png

The TCP panel

02-tcp-panel.png

Enabled Enable or Disable the TCP engine.
Listening port The port COGS listens on for incoming TCP connections. Default 12090.
Message delimiter string The characters that mark the end of each incoming message. Default \n (new line). See Message delimiter below.
Listening on The addresses other machines can use to connect to COGS. Click the clipboard icon to copy one.

Devices

Add a device for each machine you want to talk to. Click Add device and enter a name.

03-add-device.png

Then choose who opens the connection with Connection from:

05-connection-from.png

Connection from: COGS Connection from: Device
Who connects COGS connects to the device The device connects to COGS on the listening port
Settings Address (IP or hostname) and port IP address only
Connection A new connection for each message, closed once it is sent Kept open. COGS sends messages back over the same connection
Status light None Green when connected, red when not
Receive messages No (replies are ignored) Yes, and they can be filtered by device
Typical use Projectors, displays, media servers and other equipment with a TCP control port Custom props, controllers and scripts which connect to COGS and stay connected

Connection from COGS

Set the Address and Port the device is listening on.

04-device-cogs.png