Network settings

On this page you can adjust the network settings of the CoCon engine and configure the camera protocol which to sent from the CoCon engine to the camera tracking system. Here you are also able to enable the API.

Figure 1-70 Network settings page

Network information

You can configure the following network parameters:

Parameter

Description

Hostname Is the name of the CoCon engine.
IP address The IP address to access the engine, default value is 192.168.0.100. When you change the IP address, you need to restart the engine to complete the action.
Subnet mask Default subnet is 255.255.0.0
Gateway The access point to another network.

Camera protocol

Camera protocol is disabled by default. When you enable the camera protocol you can configure the following parameters:

Parameter

Description

Camera protocol Select the protocol you want to use. Two protocols are available: TLVCAM 1 and TLVCAM 2. These are the most commonly used camera protocols that are also provided with CoCon. For more information on camera protocols see the appendix.
Network protocol Both TCP/IP and UDP are provided.
Port This is the port on the client where the camera protocol is either sent to (UDP) or where the third party client has to listen to on the CoCon engine (TCP)

IP address

When you select UDP you need to specify the IP address of the destination (third-party).

Commands for TLVCAM1 protocol

All commands sent for this protocol start with a ‘%’ sign. The last character is a character that states the end of the transmission. Just before the end of transmission character, there are four characters within the command sent to the camera control which account for the CRC checksum. The CRC checksum is in uppercase hexadecimal form while all other numbers are in decimal form.

The protocol is described as follows: STX ‘%’ data CRC ETX with:

All commands sent by the protocol, need to be acknowledged by the camera system! For UDP connection this is not necessary. The protocol will retransmit the command up to 3 times if no acknowledge is received. The acknowledge frame is 1byte long and holds the value 0x06.

We will adopt a certain notation to explain the messages sent. All separate entities in a message are represented between curly brackets. If the contents of such an entity is also between quotes (‘ ‘) then this means that this is a literal string. Otherwise it describes the logical entity. A logical entity will also contain a number between brackets. This number states how many characters the entity will exist of. If the subtext 1+ is attached to the entity between curly brackets, then this means that one or more occurrences of this entity may occur.

Whenever a microphone of a delegate or the microphone of the president is activated, then a command is sent to the camera control. Whenever an active microphone is deactivated, another command is sent to the camera control.

The remaining commands are control commands.

Examples

Commands for TLVCAM2 protocol (Philips)

All commands sent by this protocol start with a ‘$’ sign or ‘&’ and commands are terminated with a CR(0xd) and LF(0xa).

Examples

REST API

The CoCon Core API provides a subset of commands that are available on the CoCon API. The CoCon Core API has the same communication protocol and command structure as the CoCon API which allows third-party programmers to simply change the IP address from the CoCon Room Server PC to the Plixus Engine. By default the API is disabled.

Default TCP port for API connection is port 8890

The following TCP ports are reserved for the CoCon system, do NOT use for camera control: 5011, 5012, 5111, 6011, 6012, 6101, 6111, 6212, 6312 and 8890.