Agenda
- Request oi-sensor-client instance on the rPLC client
- Adjust security
- Test that oi-sensor instance works using OPC UA client
Requirements
- rPLC coupler with attached camera to it
- an account on Rapid.Space with proper configuration
Goal
This how to explains how to setup an oi-sensor-client instance at rPLC coupler which forwards video stream to oi-sensor instance at ORS.
Request oi-sensor-client instance on the rPLC coupler
Please make sure that you follow this tutorial and you have created accordingly needed configuration at Rapid.Space for your rPLC coupler!
Please use following tutorial to request a new oi-sensor-client instance. Please use any title for "<YOUR-INSTANE-TITLE>" but make sure that your instance is allocated to the computer which represents the real rPLC coupler!
Please make sure that you setup the proper arguments so that oi-sensor-client instance connects to proper oi-sensor instance. There parameters are:
- ipv4 which should be the IPv4 of the oi-sensor instance running at ORS
- camera which should be the index (integer) of the connected camera to the rPLC coupler
Adjust security
Note: this step is needed to be done only once at every coupler instance.
You need to allow respective slapuserX access to video linux security group. This is not yet automated by SlapOS. Please issue following command (but replace "X" with your slapuser index) :
root@stm32mp1-5:~# usermod -a -G video slapuserX
Test that coupler software instance works
The oi-sensor at ORS itself to which we forward video stream to is an OPC-UA server which anyone can access over IPv4 (or IPv6). Usually any OPC-UA enabled client can be used. Below you can see an image using UaExperts client. What is important to notice is the shape OPC UA node value. In the picture below it is 0 (i.e. nothing detected).
