Skip to main content

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

  1. Open /admin/core/device/.
  2. Select Add device.
  3. Enter a clear Name, such as Line 1 PLC or Press OPC-UA Server.
  4. Select the Type. For PLCs, use PLC.
  5. Select the Protocol.
  6. Fill in Host, Port, and protocol-specific fields.
  7. Set Poll interval if this device needs its own polling rate. Use 0 to use the system default.
  8. Save the device.
Placeholder: Add Device form in DataStone Admin
Screenshot placeholder: Add Device form.

Common fields

FieldMeaning
NameHuman-readable device name shown in lists and Data stream selection.
TypeDevice 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.
ProtocolCommunication protocol used by the device.
HostIP address, hostname, or serial port path depending on protocol.
PortTCP port for network devices, or baudrate for Modbus RTU.
ManufacturerOptional. For Modbus RTU, this can be used as a text encoding hint.
ModuleOptional protocol-specific value. For MELSEC, use it for PLC type/module.
Poll intervalPolling interval in seconds. 0 uses the default interval.
MetadataJSON 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.

FieldValue
TypePLC
ProtocolOPC-UA
HostOPC-UA server IP or hostname
PortUsually 4840
OPC-UA discovery endpointSelect or enter an endpoint suffix only when the server requires one
OPC-UA timestamp preferenceUse the default unless Reshenie or the equipment vendor requires a specific timestamp
Placeholder: OPC-UA Device form fields
Screenshot placeholder: OPC-UA Device fields.

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.

FieldValue
TypePLC
ProtocolMELSEC
HostPLC IP address
PortUsually 5000
ModulePLC 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.

Placeholder: MELSEC Device form fields
Screenshot placeholder: MELSEC Device fields.

FEnet

Use FEnet for compatible PLCs that expose FEnet register access.

FieldValue
TypePLC
ProtocolFEnet
HostPLC IP address
PortUsually 2004

Register examples for Data streams include %MD100 for word/dword data and %MX1 for bit data.

Placeholder: FEnet Device form fields
Screenshot placeholder: FEnet Device fields.

Modbus TCP

Use Modbus TCP when the device is reachable over Ethernet.

FieldValue
TypePLC
ProtocolModbus
HostDevice IP address or hostname
PortUsually 502
MetadataOptional JSON, for example {"unit": 1, "byteorder": "big", "wordorder": "little"}
Placeholder: Modbus TCP Device form fields
Screenshot placeholder: Modbus TCP Device fields.

Modbus RTU

Use Modbus RTU when the device is connected through a serial adapter.

FieldValue
TypePLC
ProtocolModbus
HostSerial port path such as /dev/ttyUSB0
PortBaudrate, for example 9600
ManufacturerOptional encoding hint, default utf-8
MetadataOptional 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.

FieldValue
TypePC or another appropriate category
ProtocolSMB
HostSMB server IP address or hostname
PortUsually 445
SMB auth protocolUse Negotiate by default; use NTLM for legacy servers when required
Require signingKeep 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.

FieldValue
TypeUsually PC
ProtocolVNC
HostVNC server IP address or hostname
PortUsually 5900
MetadataRequired stream settings such as {"frame_width": 1280, "frame_height": 720, "frame_fps": 10}. Add "password": "<password>" only when the VNC server requires one.
Placeholder: VNC Device form fields
Screenshot placeholder: VNC Device fields.

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.

FieldValue
TypeCamera
ProtocolV4L2
HostLinux camera path, for example /dev/video0 or /dev/v4l/by-id/...
PortUnused for V4L2 capture. Keep a non-negative value such as 0.
MetadataRequired stream settings, for example {"frame_width": 1280, "frame_height": 720, "frame_fps": 15}
Placeholder: V4L2 Device form fields
Screenshot placeholder: V4L2 Device fields.

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.