NODERIQ hardware cards / EV1
Four hardware profiles connect mission compute, local vision, physical buses and precision sensing. Choose the role, check the space and qualify the complete integration.
EV1 provides defined dimensions, interface allocations and bench procedures. The images visualise the specified architecture; manufactured-board evidence, electrical release and completed NODERIQ integration remain to be established.
One platform, distinct hardware roles
NQ-C100
100 × 80 mm
Mission compute
A compact compute-carrier profile for mobile robots and observation platforms that need local perception, storage and a clear handoff to a separate machine controller.
NQ-V80
80 × 50 mm
Camera-local intelligence
A low-profile camera-processing board architecture for inspection heads, fixed observation nodes and lightweight robotic perception modules.
NQ-L70
70 × 50 mm
Robot and sensor I/O
A compact I/O bridge profile for observing CAN and serial devices, aligning service records and connecting existing controllers to mission-level software.
NQ-S50
50 × 35 mm
Precision and inertial sensing
A small acquisition profile combining four simultaneous analog channels with inertial observation for compact instruments and distributed robotic sensing.
Mechanical comparison
PCB outline, assembled height and installation reserve describe different things. The reserve leaves initial room for connectors, cable bends and service; the actual enclosure and harness still need a fit check.
| Card | PCB outline | Assembly | Installation reserve | Power allocation |
|---|---|---|---|---|
| NQ-C100 | 100 × 80 mm | 40 mm | 120 × 110 × 60 mm | 45 W |
| NQ-V80 | 80 × 50 mm | 18 mm | 100 × 80 × 35 mm | 10 W |
| NQ-L70 | 70 × 50 mm | 16 mm | 90 × 80 × 30 mm | 4 W |
| NQ-S50 | 50 × 35 mm | 12 mm | 70 × 60 × 25 mm | 1 W |
These are EV1 design allocations and screening criteria, not measured operating ratings. Component peak performance and certifications do not transfer to a custom board.
Custom integration
Share the machine envelope, supply, sensor types, bus interfaces, environment and the controller that retains physical authority. We can use those requirements to scope a carrier, sensing front end, harness and qualification plan.
AERA and MIRA remain separate observation-device programmes. A card profile does not establish compatibility with either airframe or acceptance for unattended operation.
