This IP configuration guide is intended for readers that have basic knowledge of networking like IP, Subnet Mask, router. Please refer to Understand TCP/IP addressing and subnetting basics.
The Subnet Mask are described in 255.255.0.0 and /16 notations. For now, Cyanview devices only support CIDR (/16, /24, ...) entry type. Please refer to this page for CIDR explanations.
Cyanview devices communication relies on IP Network.
The different connections that Cyanview devices uses are:
- Access other Cyanview devices by using their default IP.
- A Configuration Web UI allows RCP management via a computer's browser.
- Access Controlled Devices, RCP and Gateway must connect to supported IP devices like camera, router,... to control them.
- Internet Access for update, support, remote production purposes.
When configuring or adding IP addresses, always pay attention not to choose already used IP, see duplicate IP.
There are several ways to find your device's Network IP.
Deduce IP from the device Serial Number
The default IP and Subnet Mask of the Cyanview devices has the following pattern: IP= 10.192.x.y and Subnet Mask= 255.255.0.0 (or /16) where x, y are the two last numbers of the serial number.
- SN: CY-RCP-25-250
- IP: 10.192.25.250
- Subnet Mask: 255.255.0.0
RCP network Menu
The RCP network information are to be found in the RCP Menu Screen - Network.
Cyanview devices all have a default network configuration to allow them to communicate with each other. This default address can't be changed. Your network configuration must allow these IP addresses and range.
The factory default IP and Subnet Mask of the Cyanview devices is always:
- IP= 10.192.x.y
- Subnet Mask= 255.255.0.0 (or /16).
Your network configuration and topology must allow these addresses to communicate freely on their subnet with lowest latency possible.
It is also possible to add a PC in that subnet to access the Configuration Web UI. See RCP default IP direct access..
The RCP has several Web based configuration and dashboard UI see RCP Web UI section of RCP manual.
The RCP's main UI that you want access is the Configuration Web UI.
Depending on the network setup, RCP proposes different ways to access this Configuration Web UI.
Please refer to this link to understand What is DHCP.
Nothing to do for this configuration, the RCP will automatically make his Configuration Web UI available on a DHCP address provided by the router's DHCP server.
These IP can be found in RCP Menu Screen - Network](/docs/Manuals/RCP/ConfWebUI), use the DHCP one to access the Configuration Web UI.
A computer configured in DHCP can then access directly the RCP's Web Configuration UI by using the http://192.168.1.3 URL in your web browser.
If the DHCP Server supports it, Configuration Web UI can also be accessible via mDNS. This means you can access your device Configuration Web UI via a name of the following form: "cy-rcp-x-y.local". x, y being the two last digits of the RCP's IP (see find device IP).
The RCP's Web Configuration UI URL will be of the form http://cy-rcp-18-59.local.
The mDNS can be found directly in RCP Menu Screen - Network and is displayed on the RCP's boot screen.
Note: DHCP addresses are subject to change according the DHCP server's lease time. So the address of your Cyanview devices may change over time.
In more specific cases, computer can also access the Cyanview devices by being added a static IP in the DHCP range (see Add an IP procedure).
When no DHCP is available, use direct access to RCP's default IP address.
Cyanview devices all have a default network setup to allow them to communicate with each other. Add an IP in that subnet to your management computer to allow it to access the Configuration Web UI.
step 1 Use Find my IP procedure to find your RCP's default IP and subnet. In our example, IP = 10.192.18.59 and Subnet Mask = 255.255.0.0 (/16)
step 2 Choose an IP that can be added to the PC. In our example: IP = 10.192.18.60
step 3 Use the same subnet mask as the RCP: Subnet Mask = 255.255.0.0 (/16)
step 4 With the help of the links below, add the selected IP and Subnet Mask to your PC.
If your network setup only allows computers to connect into a specific subnet (172.16.0.0/24), the RCP can be added an IP address to make the Configuration Web UI available on that "computer subnet".
step 2 Choose an IP in the "computer subnet". In our example, IP = 172.16.0.115 and Subnet Mask = 255.255.255.0 (/24).
step 3 Add the IP and Subnet Mask to the RCP configuration.
step 4 You can now remove the IP address added in step 1.
step 5 All computer in the subnet can now access the RCP's Configuration Web UI via http://172.16.0.115 URL.
RCP needs to connect to the different IP devices of the production to control them.
IP devices like camera, router, switchers, PTZ,... are probably not using DHCP and are configured different subnets than the default Cyanview Device, the RCP can be added IP addresses to allow him to connect those devices.
In this case, an IP camera is in a different subnet, RCP must be added an IP and Subnet Mask to be able to access it.
step 1 Check your device's IP and subnet. In our example, IP Camera has IP = 10.10.115.1 and Subnet Mask = 255.255.255.0 (/24)
step 2 Choose an IP that can be added to the RCP. In our example: IP = 10.10.115.2
step 3 Use the same subnet mask as the camera's: Subnet Mask = 255.255.255.0 (/24)
The RCP now has 3 IP:
- IP: 192.168.1.2/24 DHCP Address to access the internet if DHCP server and router available.
- IP: 10.192.18.59/16 Default Address to access other cyanview devices.
- IP: 10.10.115.2/24 Additional Address to access IP devices in that subnet.
RCP needs to have an Internet access for different purposes:
- Application updates (see Product Update manual).
- Remote Production over Internet.
- Remote Support (see Remoete support manual).
If your network has a router that provides DHCP and Internet Access, RCP will automatically get an DHCP IP address and connect to Internet.
The RCP performs verifications of his network configuration. If a duplicated IP is added to his configuration, a Duplicate IP Found error message will displayed in the Connectivity Check section of the Admin page.
In the example below, the 192.168.1.212 IP added to the RCP is conflicting with a PC also with 192.168.1.212 IP.
You will then need to change the conflicting IP in the IP Connections settings.
An other solution is to change the IP of the conflicting device.