Typed command path
UI JSON commands become Protobuf messages, with defined paths for movement, mode, gait, joint angles and servo settings.
ARG Robotics
ARG Smart Robots
Four robot families built on one integrated, proven industrial ecosystem.
Integrated ARG ecosystem
Shared infrastructure across all robots
The robot family draws on shared ARG devices, industrial protocols, cloud services and AI. Sensors, controllers and software integration are selected for each model’s mission. Images are design renders; weight, speed, battery life and prices in the cards are design targets.
465
hardware devices
50+
industrial protocols
33+
AI services
5
cloud microservices
1000+
field installs
$0
infra cost
Shared advantages of every robot
Phoenix industrial brain
A proven PLC/DCS with 350 ACVs, 100 coupling rules, a BASIC interpreter and 128 dashboard widgets.
50+ industrial protocols
Speaks to any device: Modbus · SNMP · BACnet · KNX · PROFINET · HL7 … (80+ OIDs, 100+ registers).
33+ AI services + vision
Predictive maintenance (94%), anomaly detection and YOLO/face recognition — on-prem, with $0 AI cost.
Real predictive maintenance
The robot reads devices’ digital data and predicts failures — not just visual inspection.
100% indigenous, sanctions-proof
60–85% cheaper than imports, no Western dependency, locally made parts.
Offline + Persian + 1000+ installs
Offline (SLAM) navigation, full Persian support, and a 1000+ install support network.
NOVEXA / ROBOTHUB / FIRMWARE
From user interface to robot motion: a traceable path
In the Scout / RobotHub implementation, the user interface, communication gateway and motion controller have distinct responsibilities. The Hub carries telemetry and commands; firmware handles motion calculations and actuators.
- 01
Novexa
Control interface, robot state and user settings
HTTP / JSON
- 02
RobotHub
FastAPI, robot-scoped routing, request/response and telemetry fan-out
WebSocket / Protobuf
- 03
Firmware
Mode, gait, kinematics, IMU and servo control
ESP32 / NVS
- 04
Body & sensors
Joints, actuators and sensor data, according to model hardware
Motion / Feedback
Feedback returns from firmware and IMU through RobotHub to the user interface. Hub message acceptance is distinct from completed physical motion; responses and telemetry track the outcome.
Control and communication mechanisms
Telemetry & connectivity
RobotHub caches the latest message of each telemetry type and fans it out to UI subscribers. Ping/pong and last-seen tracking expose connection state.
Correlated requests
Correlation IDs match requests to the same robot’s response for firmware feature discovery, system information, and IMU calibration; the Protobuf contract also defines file-operation messages.
Servo calibration
Each servo has a PWM centre, direction, reference angle, conversion factor and travel limits. UI channel numbering is translated to firmware conventions; settings persist in device NVS.
Firmware motion & balance
REST, STAND and WALK modes, TROT and CRAWL gaits, and IMU input belong to the robot control layer. Hub balance-gain configuration is separate from motion-command generation.
Poses & feature discovery
Named poses are stored in the Hub. Feature responses describe firmware versions and camera, IMU, servo and other capabilities for compatible controls.
Select the robot for a defined mission
Operating terrain, payload, sensors, mission duration and existing-system integration define model selection and project scope. The RobotHub architecture describes the Scout implementation; each family’s capabilities depend on its configuration.