Pronounce [rɪəʊ lɪv].
The RIO live is a mix between:
- A CI0 : it has the serial ports, display and buttons
- A RCP : it has all the protocols inside, same web UI
It is a standalone device, for:
- Lens control
- USB cameras ( mirrorless, etc. )
- WiFi LAN control
- Polecam, etc.
That you can link with a RCP for the remote shading.
Compared to a CI0, which is a slave device:
- the RIO Live is a standalone device, if you unplug RCP, the camera/lens is still controlled
- the link between a RCP and a RIO Live is more robust on unreliable networks ( WiFi, etc. )
- configuration is totally different, you configure on RIO web UI and import on RCP
Compared to CI0, the RIO Live was designed for bigger cameras. Where you don't have PoE. And we wanted it as small as possible and PoE is taking a lot of space.
So RIO Live is not PoE, you can power it using 12V DC from:
- D-Tap (from camera, battery, etc.)
DC IN voltage is between 10V and 24V.
The input voltage will be directly applied to the camera so if you power from batteries, make sure the camera does support the higher battery voltage as well. For thermal reasons, camera consumption should not exceed 12W by port.
The RIO and RCP will communicate together over IP.
The RIO Live camera configuration is exactly the same as RCP.
You can access your RIO Live configuration page following this guide.
Once there, the setup is similar to the RCP web UI
And you can follow any integration guide from this website, it applies to RCP as well as RIO.
To setup RIO with a RCP:
- Setup the camera on your RIO web UI
- Setup a tag/group in your RIO
- Setup the same tag/group in your RCP
- Import the camera from your RIO in your RCP
From there, you will have control of the camera from your RCP.
You can find more information about this pairing on this page.
The REMI is the way RCP/RIO Live are paired and work together.