Cyanview remote control allows you to control all the camera we control locally, but from any remote location using our cloud, IP tunnel or any VPN solution.
The generic concept is that we link together all the devices in a group protected by a password.
Then, each device can:
- export any camera to allow other devices in my group to control them
- import any camera available in the groups
You can do the setup that on any of this Cyanview device:
- RCP :
- can setup camera locally and share it (export)
- can shade remote camera (import)
- can mix import/export if you need to have both local and remote control of your cameras
- RIO :
- same as an RCP (can import or export cameras)
- but no local shading capability
- has 2 physical port to connect cameras on it
- NIO :
- same as a RIO
- has 16 GPIO
- but no physical camera connector
CI0 can be linked to any RCP/RIO/NIO to extend the number and type of camera you need to control. So a CI0 behind a RIO allows you to control 4 serial cameras.
All the cameras are controlled locally (by the RCP, RIO, etc.). But we have our own protocol designed to be robust and low latency that connects all our devices together.
This link can be established between devices locally or using the cloud.
The cloud is hosted in Europe and USA to have reduced latency and is free of charge. There is an automatic detection to put your devices on the correct server based on your location.
Configure your cameras
The configuration is done locally on each device (RCP, RIO, NIO) by accessing their web interface, if you need help, you can follow this guide.
The first step is to configure your cameras on each device.
- On my RCP I configured 1 cameras:
- On my RIO I configured 1 camera:
Configure your groups
If both devices are connected to internet, they will use the cloud to talk to each other. If they can discover each other, they will connect directly, for example in a VPN. This use discovery with broadcast.
On each device, you will navigate to the
And in the right panel, inside the
Shared Camera Control, enter your
- Enter a tag name in the text box
- Click on
This tag acts like a password. Everybody that knows it can connect to your group.
On my RCP, I have (2 tags :
mytag, shared with my RIO and a second one
4YGJ4G1W4, not used here):
On my RIO, I have (2 tags :
mytag, shared with my RCP and a second one
2PFLVV32R, not used here):
One device can be associated to multiple groups.
Once setup on all devices, you can now see status of all the devices in your "groups":
- On the RCP:
- On the RIO:
I see here two icons:
- Cloud : means this device can be reached by the cloud
- Ethernet : means this device can be reached using a local link
Pay attention that group names could be guessable and act as a password. So try to make them as secure as possible and not share with anybody that shouldn't access your cameras.
You can now on any device in your group import any camera of any device.
On my RCP (18-4), I can setup a 2n camera:
- Click on the
+in the camera block, a new panel will appear on the right
GeneralConfigure a Number and a Name
Cyanviewfor the brand and
Importedas the model.
Your setup (on your RCP) should looks like:
The format is the following:
Link type can either be:
Ifor Internet, preferred (Internet link is available, devices are discovered using the cloud, internet required)
Dfor Direct, advanced (Direct link is available, devices are discovered without the cloud)
Mfor Manual, advanced (Link is manually set between RCP and RIO)
Once configured, you should see something similar:
Here, on my RCP, I imported the cam
camB from my RIO
cy-rio-15-4 using the cloud link
Usually, the delay in this kind of setup is not from the control. You can expect latency from 10ms to 100ms depending on your internet connectivity. But it come from the video encoding/buffering. A nice solution is to mix remote camera head control with our VP4 to have the best of both world:
- Remote control on the camera head with some latency (with RIO, etc.)
- Local shading using the VP4 without any latency (because it is on the incomming video signal)