Device setup
A Device represents a physical or logical source of data, such as a PLC, OPC-UA server, Modbus endpoint, SMB server, camera, or screen stream. Create the Device first, then create Data streams for tag/register/file values when the protocol supports them.
Add a device
- Open
/admin/core/device/. - Select Add device.
- Enter a clear Name, such as
Line 1 PLCorPress OPC-UA Server. - Select the Type. For PLCs, use
PLC. - Select the Protocol.
- Fill in Host, Port, and protocol-specific fields.
- Set Poll interval if this device needs its own polling rate. Use
0to use the system default. - Save the device.
Common fields
| Field | Meaning |
|---|---|
| Name | Human-readable device name shown in lists and Data stream selection. |
| Type | Device category. Use PLC for OPC-UA, FEnet, MELSEC, and Modbus PLCs. Use Camera for V4L2 cameras and PC for VNC screen streams unless Reshenie gives a different value. |
| Protocol | Communication protocol used by the device. |
| Host | IP address, hostname, or serial port path depending on protocol. |
| Port | TCP port for network devices, or baudrate for Modbus RTU. |
| Manufacturer | Optional. For Modbus RTU, this can be used as a text encoding hint. |
| Module | Optional protocol-specific value. For MELSEC, use it for PLC type/module. |
| Poll interval | Polling interval in seconds. 0 uses the default interval. |
| Metadata | JSON hints for protocol options such as Modbus unit, byteorder, or wordorder. |
OPC-UA
Use OPC-UA when the equipment exposes tags through an OPC-UA server.
| Field | Value |
|---|---|
| Type | PLC |
| Protocol | OPC-UA |
| Host | OPC-UA server IP or hostname |
| Port | Usually 4840 |
| OPC-UA discovery endpoint | Select or enter an endpoint suffix only when the server requires one |
| OPC-UA timestamp preference | Use the default unless Reshenie or the equipment vendor requires a specific timestamp |
After saving, use the OPC-UA browser tool from the Device or Data admin page to find available nodes.
MELSEC
Use MELSEC for Mitsubishi PLC communication.
| Field | Value |
|---|---|
| Type | PLC |
| Protocol | MELSEC |
| Host | PLC IP address |
| Port | Usually 5000 |
| Module | PLC type/module, for example Q, when provided by Reshenie or the PLC vendor |
Register examples for Data streams include D16000 and bit addresses such as M0.
FEnet
Use FEnet for compatible PLCs that expose FEnet register access.
| Field | Value |
|---|---|
| Type | PLC |
| Protocol | FEnet |
| Host | PLC IP address |
| Port | Usually 2004 |
Register examples for Data streams include %MD100 for word/dword data and %MX1 for bit data.
Modbus TCP
Use Modbus TCP when the device is reachable over Ethernet.
| Field | Value |
|---|---|
| Type | PLC |
| Protocol | Modbus |
| Host | Device IP address or hostname |
| Port | Usually 502 |
| Metadata | Optional JSON, for example {"unit": 1, "byteorder": "big", "wordorder": "little"} |
Modbus RTU
Use Modbus RTU when the device is connected through a serial adapter.
| Field | Value |
|---|---|
| Type | PLC |
| Protocol | Modbus |
| Host | Serial port path such as /dev/ttyUSB0 |
| Port | Baudrate, for example 9600 |
| Manufacturer | Optional encoding hint, default utf-8 |
| Metadata | Optional JSON, for example {"unit": 1, "parity": "N", "stopbits": 1, "bytesize": 8} |
If the serial port does not appear, confirm the USB adapter is connected to the DataStone appliance and contact Reshenie support.
SMB
Use SMB when DataStone needs to read files from a Windows or SMB-compatible file server.
| Field | Value |
|---|---|
| Type | PC or another appropriate category |
| Protocol | SMB |
| Host | SMB server IP address or hostname |
| Port | Usually 445 |
| SMB auth protocol | Use Negotiate by default; use NTLM for legacy servers when required |
| Require signing | Keep enabled unless the server does not support signing |
After saving the SMB device, use the SMB browser tool from the Data admin page to select file paths.
VNC
Use VNC when DataStone needs to stream a remote desktop or HMI screen. VNC is read-only streaming for now; do not configure it for keyboard, mouse, or write-back control unless Reshenie explicitly enables that in your deployment.
| Field | Value |
|---|---|
| Type | Usually PC |
| Protocol | VNC |
| Host | VNC server IP address or hostname |
| Port | Usually 5900 |
| Metadata | Required stream settings such as {"frame_width": 1280, "frame_height": 720, "frame_fps": 10}. Add "password": "<password>" only when the VNC server requires one. |
After saving, verify that the stream opens in the viewing workflow provided by Reshenie. VNC devices usually do not need Data streams because the output is a visual stream, not a numeric tag or register.
V4L2
Use V4L2 for a camera connected directly to the DataStone appliance, such as a USB camera exposed by Linux as /dev/video0. V4L2 is read-only streaming for now.
| Field | Value |
|---|---|
| Type | Camera |
| Protocol | V4L2 |
| Host | Linux camera path, for example /dev/video0 or /dev/v4l/by-id/... |
| Port | Unused for V4L2 capture. Keep a non-negative value such as 0. |
| Metadata | Required stream settings, for example {"frame_width": 1280, "frame_height": 720, "frame_fps": 15} |
If the camera path does not appear or the stream does not open, confirm the camera is connected to the DataStone appliance and ask Reshenie to check device permissions and supported camera modes.