Skip to content

Commit

Permalink
Review
Browse files Browse the repository at this point in the history
  • Loading branch information
MariekeGO committed Jan 7, 2025
1 parent 8b150b0 commit 2c1106c
Show file tree
Hide file tree
Showing 2 changed files with 54 additions and 75 deletions.
54 changes: 23 additions & 31 deletions connector/doc/Sony_CNA-2.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,28 +4,27 @@ uid: Connector_help_Sony_CNA-2

# Sony CNA-2

Sony CNA-2 is a camera control network adaptor that is able to monitor, configure and control your Sony system cameras anywhere with Network.
It is able to run productions to get the most out of your system cameras and visualize grouping functions and settings for SR-Live and Networked Live.
Sony CNA-2 is a camera control network adaptor that is able to monitor, configure, and control Sony system cameras anywhere within the network. It is able to run productions to get the most out of the system cameras and visualize grouping functions and settings for SR-Live and Networked Live.

## About

### Version Info

|Range |Features |Based on |System Impact |
|---------|---------|---------|---------|
|1.0.0.x [SLC Main] |<ul><li>System Camera management</li><li>Webhook listening capabilities</li></ul> |- |- |
| Range | Features | Based on | System Impact |
|--------------------|----------------------------------------------------------------|----------|---------------|
| 1.0.0.x [SLC Main] | - System camera management<br>- Webhook listening capabilities | - | - |

### Product Info

|Range |Supported Firmware |
|---------|---------|
|1.0.0.x |v1.0820 |
| Range | Supported Firmware |
|---------|--------------------|
| 1.0.0.x | v1.0820 |

### System Info

|Range |DCF Integration |Cassandra Compliant |Linked Components |Exported Components |
|---------|---------|---------|---------|---------|
|1.0.0.x |No |Yes |- | |
| Range | DCF Integration | Cassandra Compliant | Linked Components | Exported Components |
|---------|-----------------|---------------------|-------------------|---------------------|
| 1.0.0.x | No | Yes | - | - |

## Configuration

Expand All @@ -37,26 +36,22 @@ This connector uses an HTTP connection and requires the following input during e

HTTP CONNECTION:

- **IP address/host**: [The polling IP or URL of the destination.]
- **IP port**: [The IP port of the destination. (default: *443*)]
- **Device address**: [The bus address of the device. If the proxy server has to be bypassed, specify *BypassProxy*.]
- **IP address/host**: The polling IP or URL of the destination.
- **IP port**: The IP port of the destination (default: *443*).
- **Device address**: The bus address of the device. If the proxy server has to be bypassed, specify *BypassProxy*.

### Initialization

In the **Communication Settings** page, you will need to provide a username and a password to login in to the device.
On the **Communication Settings** page, you will need to provide a username and a password to log in to the device.

#### Webhook Listener

This connector uses a HTTP listener and requires the following configuration inside the element:
This connector uses an HTTP listener and requires the following configuration within the element:

WEBHOOK LISTENER:

- **Webhook IP**: [The IP where the webhooks will be listened.]
- **Webhook port**: [The port where the webhooks will be listened. (default: *50000*, needs to be opened in the firewall)]

### Redundancy

There is no redundancy defined.
- **Webhook IP**: The IP used to listen to webhooks.
- **Webhook port**: The port used to listen to webhooks (default: *50000*; needs to be opened in the firewall).

### Web Interface

Expand All @@ -66,15 +61,12 @@ The web interface is only accessible when the client machine has network access

This connector uses REST API calls to communicate with the device.

It has two communication modes, GMCS and MCS.
In GMCS mode, you can configure up to 10 different domains with 3 tables each, one for CCU device information, one for CCU Assignment information, and one for RCP Assignment information.
The domains can be enabled/disabled in the *GMCS Communication Settings* table in the **Communication Settings** page.
This will also impact if that domain is polled and displayed or not.
It has two communication modes, GMCS and MCS.

- In **GMCS** mode, you can configure up to 10 different domains with 3 tables each, one for CCU device information, one for CCU Assignment information, and one for RCP Assignment information. The domains can be enabled/disabled in the **GMCS Communication Settings** table on the **Communication Settings** page. This will also affect whether a domain is polled and displayed or not.

When in MCS mode, you will only have access to one domain with the same 3 tables.
- When in **MCS** mode, you will only have access to one domain with the same 3 tables.

For both modes, a matrix for CCU Assignments and another for RCP Assignments is available.
- For both modes, a matrix for CCU assignments and another for RCP assignments is available.

The Webhook communication is responsible for receiving updates on connections made, so it is important to make sure that you provide valid Webhook connection parameters.
An incorrect configuration will lead to tables and matrices only being updated every 15 minutes.
Please also make sure that the Webhook port is opened in the Firewall. If not, no Webhook communication will be received.
The webhook communication is responsible for receiving updates on connections made, so it is important to make sure that you provide valid webhook connection parameters. An incorrect configuration will lead to tables and matrices only being updated every 15 minutes. It is also important to ensure that the webhook port is opened in the firewall, as otherwise no webhook communication will be received.
75 changes: 31 additions & 44 deletions connector/doc/Sony_MLS-X1.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,32 +4,29 @@ uid: Connector_help_Sony_MLS-X1

# Sony MLS-X1

The Modular Live System (MLS-X1) is a production switcher platform.
It is reconfigurable to meet a wide range of live production requirements, it provides processing power and scalability to enhance your production environments.
The Modular Live System (MLS-X1) is a production switcher platform. It can be configured to meet a wide range of live production requirements, and it provides processing power and scalability to enhance production environments.

The MLS-X1 inherits the operability, reliability and capability of Sony other professional switchers.
It uses multiple smaller processing units that can be rapidly configured according to the requirements of any production.
With the MLS-X1 you’ve got the power to cater for large-scale events – including multi-programme and multi-format productions – plus the agility to meet future demands.
The MLS-X1 inherits the operability, reliability, and capability of other Sony professional switchers. It uses multiple smaller processing units that can be rapidly configured according to the requirements of any production. This allows you to cater for large-scale events, including multi-program and multi-format productions, and it provides the agility to meet future demands.

## About

### Version Info

|Range |Features |Based on |System Impact |
|---------|---------|---------|---------|
|1.0.0.x [SLC Main] |<ul><li>System monitoring through SNMP</li><li>System configuration through gRPC</li></ul> |- |- |
| Range | Features | Based on | System Impact |
|--------------------|-------------------------------------------------------------------------|----------|---------------|
| 1.0.0.x [SLC Main] | - System monitoring through SNMP<br>- System configuration through gRPC | - | - |

### Product Info

|Range |Supported Firmware |
|---------|---------|
|1.0.0.x |- |
| Range | Supported Firmware |
|---------|--------------------|
| 1.0.0.x | - |

### System Info

|Range |DCF Integration |Cassandra Compliant |Linked Components |Exported Components |
|---------|---------|---------|---------|---------|
|1.0.0.x |Yes |Yes |- | |
| Range | DCF Integration | Cassandra Compliant | Linked Components | Exported Components |
|---------|-----------------|---------------------|-------------------|---------------------|
| 1.0.0.x | Yes | Yes | - | - |

## Configuration

Expand All @@ -41,45 +38,36 @@ This connector uses a Simple Network Management Protocol (SNMP) connection and r

SNMP CONNECTION:

- **IP address/host**: [The polling IP or URL of the destination.]
- **IP port**: [The IP port of the destination. (default: *161*)]

- **IP address/host**: The polling IP or URL of the destination.
- **IP port**: The IP port of the destination (default: *161*).

SNMP Settings:

- **Get community string**: [The community string used when reading values from the device. (default: *public*)]
- **Set community string**: [The community string used when setting values on the device. (default: *private*)]

- **Get community string**: The community string used when reading values from the device (default: *public*).
- **Set community string**: The community string used when setting values on the device (default: *private*).

### Initialization

This connector also uses gRPC (Google Remote Procedure Call) to manage and configure the system.
It will use up to 5 gRPC connections to gather information and to configure the different systems.
This connector also uses gRPC (Google Remote Procedure Call) to manage and configure the system. It will use up to 5 gRPC connections to gather information and to configure the different systems, which will need to be configured in the element.

#### Manager gRPC Connection

In the **MLS Manager** page, you will need to configure the following parameters:

Manager gRPC Connection:
On the **MLS Manager** page, configure the following parameters for the Manager gRPC connection:

- **IP address/Hostname**: [The IP of the destination. (default: *Polling Ip*)]
- **IP port**: [The IP port of the destination. (default: *31042*)]
- **Username**: [The login username.]
- **Password**: [The login password.]
- **IP address/Hostname**: The IP of the destination (default: *Polling IP*).
- **IP port**: The IP port of the destination (default: *31042*).
- **Username**: The login username.
- **Password**: The login password.

#### Logical Switcher gRPC Connection

In the **Logical Switcher** page, you will need to configure the following parameters (the IP address is the one obtained in the *System Configurations* table in the **MLS Manager** page):
On the **Logical Switcher** page, configure the following parameters:

Logical Switcher gRPC Connection:

- **IP port**: [The IP port of the destination. (default: *9181*)]
- **Username**: [The login username.]
- **Password**: [The login password.]

### Redundancy

There is no redundancy defined.
- **IP port**: The IP port of the destination (default: *9181*). You can obtain this from the **System Configurations** table on the **MLS Manager** page.
- **Username**: The login username.
- **Password**: The login password.

### Web Interface

Expand All @@ -92,22 +80,21 @@ The web interface is only accessible when the client machine has network access
- **Product Information**: This page displays the **Product Information**, **Modules**, and **Remote Maintenance** tables.
- **Traps**: This page displays the **Traps Destination** table.
- **Alarms**: This page displays the **Error Status** table. This table is cleared when a "Coldstart" trap is received.
- **XVS Control**: This page allows you to check which XVS element is connected to which the XVS via the **Control Interfaces** table. There is a **Resubscribe** button to reset all the created subscriptions.
- **Subscriptions**: This page allows you to check all the created subscriptions by this element.
- **XVS Control**: This page allows you to check which XVS element is connected to which XVS via the **Control Interfaces** table. There is a **Resubscribe** button to reset all the created subscriptions.
- **Subscriptions**: This page allows you to check all the subscriptions created by this element.
- **Agent MIB**: This page displays the **Agent MIB Categories** and **Agent MIB Products** tables.
- **Switcher Information**: This page displays the **Switcher Reference Information**, **Switcher Temperature Information**, **Switcher Fan Information**, **Switcher Power Sensors**, **Switcher SSD Information**, and **Switcher Battery Information** tables.
- **MLS Manager**: This page displays the **MLS Manager** gRPC connection credentials and state, as well as some system configurations.
- **MLS Manager**: This page displays the **MLS Manager** gRPC connection credentials and state, as well as some system settings.
- **Logical Switcher**: This page displays the **Logical Switcher** gRPC connections. It also displays some information about each connection and connected device.

## Dataminer Connectivity Framework
## DataMiner Connectivity Framework

The **1.0.0.x** range of the Sony MLS-X1 connector supports the usage of DCF.

**DCF can also be implemented through the DataMiner DCF user interface and through third-party DataMiner connectors (e.g. a manager).**

DCF can also be implemented through the DataMiner DCF user interface and through third-party DataMiner connectors (e.g. a manager).

### Interfaces

#### Dynamic interfaces

- The Interfaces table is available with type **inout**.
- In the Interfaces table, dynamic interfaces are available with type **inout**.

0 comments on commit 2c1106c

Please sign in to comment.