Octopus IoT
DATAWARE OCTOPUS IOT
Device handling system · Ver 1.0 Alpha · Supervisor 0.26.07.27

Octopus IoT is the DATA WARE central platform for IoT devices, sensors, cameras and edge nodes. It monitors presence and telemetry in real time, assigns devices along the Supervisor → Producer → Customer → User hierarchy, exposes remote Linux/Windows shells and handles field photos and video. It supports OTA (Over-the-Air) EDGE updates and includes custom device-control systems.

MQTT / Kafka ready OTA Over-the-Air Multi-tenant Sensors + Camera Remote shell Custom devices

linux almalinux WIN10 WIN11 html5


Download the presentation



DATAWARE OCTOPUS IOT FEATURES


Overview. One hub for every device.


A single console for edge nodes, sensors and cameras. It monitors presence and telemetry in real time, assigns devices along the Supervisor → Producer → Customer → User hierarchy, exposes remote Linux/Windows shells and handles field photos and video.

• MQTT / Kafka ready
OTA Over-the-Air
• Multi-tenant (Producer / Customer / User)
• Sensors + camera
• Remote Linux and Windows CMD shell
• Custom devices

Octopus Supervisor dashboard

Organization. Supervisor → Producer → Customer → User.


Supervisor — central SystemAdmin console: dashboard, connected devices, statistics, camera, producer and customer master data.
Producer — organization that manages devices (e.g. DataWare Producer) and assigns them to its customers.
Customer — site / end customer (e.g. Haupt Pharma srl) with dedicated devices and site-user management.
User — operational accounts for a customer (e.g. Operator): access to the functions allowed on the tenant.

Microsoft SSO login

Measurement sources. Sensor readings from PLCs, industrial PCs and industrial Raspberry boards.


Ingests readings from PLCs, Windows industrial PCs and industrial Raspberry boards (bus, USB-TTL, Modbus, edge agent) and normalizes them into Octopus telemetry with the same Supervisor → Producer → Customer → User hierarchy.

1 PLC

Acquisition from line controllers (registers, digital/analog I/O, Modbus/OPC gateway or serial bridge). Measurements flow into Octopus as device telemetry, with Online / Stale / Offline status and assignment to the plant customer.

2 Industrial PCs

Windows hosts in cabinet or rack: sensor reading via USB-TTL / COM (e.g. DHT22 with CP2102 + MCU bridge), local service publishing to Kafka on the same topics as the Raspberry. Remote Windows CMD shell from the Supervisor console.

3 Industrial Raspberry

Linux aarch64 edge (industrial Pi or hardened Zero 2 W): C++ agent for environmental sensors and camera, keepalive, commands and Linux remote shell. Ideal for sensor zones and MQTT gateways close to the machine.

Source Typical interface What Octopus shows
Process PLC Modbus / OPC / I/O + gateway Device with process measurements, presence and last values
Windows industrial PC USB-TTL (COM) + Delphi/agent service CONNECTED device, CMD shell, telemetry and optional camera
Industrial Raspberry RevPi Compact (DIN) · GPIO / I2C · C++ agent CONNECTED device, DI/DO/AI/AO I/O, Linux shell, photo/video, statistics
Serial sensor connectivity

Buses and serial ports — a natural bridge to PLCs, USB-TTL converters and cabinet peripherals.

DHT22 wiring on PC via USB-TTL

Industrial PC example — DHT22 → ESP-01S → CP2102 USB-TTL → Windows service to Octopus/Kafka.

Architecture. From sensor to dashboard.


ESP32 zones read sensors (e.g. BME280 via I2C) and drive relays via GPIO; the Raspberry gateway publishes/subscribes MQTT; Octopus shows status, commands, camera and statistics.

Layer Components Role
Dashboard Octopus Supervisor Visualization, commands, master data, camera, statistics
Gateway Raspberry Pi + MQTT broker Message hub between edge and platform
Edge zone ESP32 + BME280 + Relay Temperature / humidity / pressure and local actuation
Device host Pi Zero 2 W / Windows USB-TTL DHT22 C++ or Delphi sensors, camera, remote shell
MQTT ESP32 Raspberry wiring schema

Devices. Connected, assigned, controllable.


Live device inventory with Online / Stale / Offline status, Producer and Customer assignment, and quick actions:

Edit — update metadata and organizational assignment
Command — open the remote shell on the device (Linux or Windows CMD)
Camera — last photo, gallery and last-minute video
Info — technical detail and presence

Connected devices list

Industrial edge. Revolution Pi Compact.


DIN-rail controller based on Raspberry Pi Compute Module: DI/DO/AI/AO, dual Ethernet, RS485/Modbus. Reads sensors and drives outputs from the cabinet, with Linux shell and telemetry to Octopus. DIN-rail housing 90 × 160.6 × 58 mm, typical 24 V DC supply, IP20.

Revolution Pi Compact
Category Detail
Digital 8 × 24 V DC inputs (EN 61131-2 type I/III) · 8 high-side outputs, max 500 mA each / 2 A total
Analog 8 × 0–10 V inputs (up to 16 bit) · 2 × 0–10 V outputs, short-circuit proof
Network & field 2× Ethernet RJ45 (separate MACs) · RS485 on terminals (Modbus RTU/TCP as standard)
Compute BCM2837B0 quad-core 1.2 GHz · 1 GB RAM · 8 GB eMMC · full Linux root
Environment −20…+55 °C operation · EMC EN 61000-6-2 / 6-4 · CE / RoHS

Why in Octopus

A CONNECTED device with industrial I/O telemetry, Linux remote shell and the same Kafka/MQTT flows as other edge nodes: ideal when you need a “cabinet Raspberry” instead of a PC or a closed PLC.

What you can do

Read sensors on AI/DI, drive DO/AO, talk Modbus, develop in Python/Node-RED/C and manage presence, commands and diagnostics from the Supervisor dashboard.

Revolution Pi DO KUNBUS module

I/O expansion — RevPi DO module example (KUNBUS): high-side digital outputs up to 0.5 A, PiBridge / fieldbus.


Remote shell. Linux and Windows from the browser.


Remote terminal on the device without a desktop VPN: diagnostics, commands, logs and maintenance from the Supervisor browser, session bound to the selected device. Includes OTA (Over-the-Air) EDGE updates: edge firmware and software can be updated remotely, with no on-site intervention, across Linux and Windows fleets.

Linux remote shell

Linux shell — Debian aarch64 on a C++ device: cwd, presence, help / status / disconnect commands.

Windows CMD remote shell

Windows CMD — Delphi USB-TTL host: CMD session with persistent directory and Octopus built-ins.


Camera. Photo, gallery, one-minute video.


View the latest photo, browse the JPEG archive in the database and build an MP4 of the last minute of frames, with resolution selectable from Supervisor. Ideal for area monitoring, event documentation and emergency support.

Last device photo

Last picture — live snapshot with refresh and size/time metadata.

Device photo gallery

Pictures — tens of thousands of frames with pagination.

Last-minute video

Last minute video — compiles MP4 from JPEG (e.g. 36 frames @ 1 fps).


Custom devices. Tailored sensor examples.


We build custom device-control systems, with a flexible edge for legacy and custom hardware:

Temperature / humidity — DHT22, BME280 and USB-TTL variants
Camera — area monitoring, event documentation, emergency support
Serial ports — custom integrations on industrial buses and adapters

Serial connectivity for custom hardware

Analytics & multi-tenant. Statistics, Producer, Customer.


Analyze time series (avg / min / max) for humidity, temperature and other measurements; manage Producer, Customer and User (Operator) with the Supervisor → Producer → Customer → User hierarchy.

Device statistics

Device assignment

Edit assignment — name, Device ID, MAC, Producer and Customer in one form.

Producers management

Producers — code, name, Active flag; Edit / Customers / Delete actions.

Customers management

Customers — customers per producer, Operator users and dedicated access management.


Contact us. Demo with no obligation.


For Octopus IoT demos, device sizing at operational sites or Supervisor console activation (telemetry, camera, remote shell, OTA and dashboards), the DATA WARE team is available.

Do you already have sensors or hosts in the field? We build custom device-control systems and OTA updates for EDGE fleets.