Role & capabilities
- Remote hazardous-object inspection
- Manipulator handling
- CBRNe detection configuration
- Remote observation
- Primary domain
- Land
- System type
- Explosive-ordnance disposal robot
- Developer / manufacturer
- DRDO — Research and Development Establishment (Engineers)
- Origin / production countries
- India
- Other names
- ROV Daksh; Daksh ROV
- Variants / configurations
- Daksh; other DRDO Scout / Mini robots require separate profiles
- Operators / programme customers
- Current named-unit inventory not established by the cited technical publications
Evidence & current status
Official product literature supports the technical description; current fleet size and service acceptance by exact configuration are not established here. R&DE(E) is the developer; licensed production partners require separate confirmation.
Daksh is the remotely operated vehicle developed by India's Research and Development Establishment (Engineers), part of DRDO. It combines a mobile base, a manipulator and cameras so an operator can examine suspicious objects and perform hazardous handling tasks from a separate control station. DRDO's 2024 technical publication also describes an onboard chemical, biological, radiological, nuclear and explosive-detection capability.
The published system includes the robot, its master control station and a dedicated carrier vehicle. That distinction matters: a quoted remote-control range is the separation between robot and operator, not the distance the vehicle can drive on a battery. Similarly, the manipulator's degrees of freedom describe movement capability rather than how much every arm position can lift.
Daksh belongs to a broader Indian robotics effort, but it should not be merged with Scout, Mini or other DRDO robots simply because they appear in the same exhibition catalogue. The reviewed official technical material establishes a developed product and its advertised functions. It does not provide a current named-unit inventory, delivery total or configuration-by-configuration military acceptance record; those remain explicit research gaps.
Sourced specifications
Figures apply to the named configuration. Maximum values are not guaranteed operating performance.
| Specification | Reported value | Context & source |
|---|---|---|
| Configuration | Mobile remote robot, manipulator and master control station | Official DRDO technical description. Source ↗ |
| Mobility | Not established in the reviewed public sources. | Public data gap; no estimate or neighbouring variant value substituted. Source ↗ |
| Dimensions | Not established in the reviewed public sources. | Public data gap; no estimate or neighbouring variant value substituted. Source ↗ |
| Mass | Not established in the reviewed public sources. | Public data gap; no estimate or neighbouring variant value substituted. Source ↗ |
| Payload | Not established in the reviewed public sources. | Public data gap; no estimate or neighbouring variant value substituted. Source ↗ |
| Endurance | 3 hours | Official published figure; operating conditions not specified. Source ↗ |
| Range | Not established in the reviewed public sources. | Public data gap; no estimate or neighbouring variant value substituted. Source ↗ |
| Speed | Not established in the reviewed public sources. | Public data gap; no estimate or neighbouring variant value substituted. Source ↗ |
| Terrain / environment | Building access and stair-climbing capability described | No all-terrain autonomy implied. Source ↗ |
| Sensors | Multiple cameras; CBRNe instrumentation described | Sensor package configuration must be established. Source ↗ |
| Communications / control | Remote control up to 500 m line of sight | Control distance, not vehicle travel range. Source ↗ |
| Launch / deployment | Dedicated carrier transports robot and control system | Published system arrangement. Source ↗ |
Publication history
- — Added sourced land and maritime coverage with domain-specific evidence and limitations.
Suggest a correction to this entry →
Follow the evidence
Source types identify who makes the claim. Programme milestones and supplier statements should be read in context.