FAQs on Darsi Pro Compute Box

1. What is Darsi Pro?

+

Darsi™ Pro is an Edge AI compute box based on the NVIDIA® Jetson Orin™ NX, suitable for mobility and AI vision applications. This production-ready compute platform supports multiple sensors, including cameras, LiDAR, and radar, and provides reliable hardware for edge computing.

2. What cameras does the Darsi™ Pro compute box support?

+

The Darsi™ Pro compute box supports e-con Systems' broad range of GMSL cameras, Ethernet cameras and USB cameras.

3. What is the power input range for the compute box, and what protection mechanisms are implemented?

+

The Darsi™ Pro compute box supports an input voltage of 24V, accommodating various vehicle battery configurations. Based on the hardware requirements, it can be designed from range of 8V to 36V DC. The system incorporates comprehensive protection circuitry, including reverse polarity protection, input surge protection, inrush current limiting, and battery-percentage-based power management.

4. How much power does the compute box consume?

+

The Darsi™ Pro compute box typically consumes 25W.

5. How does the power management MCU work within the system?

+

The power management MCU serves as the main controller for shutdown, soft reboots, sleep and wake-up functions, and power operating modes. Furthermore, in the event of a failure, the power management MCU acts as a watchdog to guarantee appropriate recovery.

6. What are the specifications for the USB interface?

+

The system has two USB 3.0 ports, allowing up to 5 Gbps speeds for data transfer.

7. What PCIe expansion capabilities are provided?

+

M.2 connectors are available for modular expansion. The NVMe SSD utilizes four dedicated PCIe lanes, while other slots support Wi-Fi modules and LTE/5G connectivity modules based on specific application needs.

8. How is Ethernet connectivity configured, and what PoE options are available?

+

The vision box includes three 1Gbps Ethernet ports—two supporting Power over Ethernet (PoE) and one standard Ethernet port without PoE.

9. What CAN bus capabilities are provided for vehicle integration?

+

The system includes three CAN interfaces designed for integration with vehicle control systems.

10. How is sensor fusion handled across multiple sensor types?

+

The compute box is designed to support sensor fusion across LiDAR, RADAR, and camera systems. The use of the GNSS module is being assessed to provide a PPS (Pulse Per Second) master signal generator for sensor synchronization. The implementation strategy includes attaching trigger timestamps to the framebuffer to ensure precise time synchronization across all connected sensors.

Read Blog: What Sensor Fusion Architecture Offers for NVIDIA Orin NX-Based Autonomous Vision Systems - e-con Systems

11. What cellular connectivity options are available in the Compute box?

+

Both eSIM and physical SIM slots are provided to connect external antennas for optimal signal reception.

12. Is an IMU included in the system?

+

Yes, there is an Inertial Measurement Unit (IMU) to determine the spatial orientation and motion characteristics.

13. What is the base software platform for the compute box?

+

The compute box runs a Linux image built on NVIDIA's L4T (Linux for Tegra) BSP for NVIDIA® Orin™ NX module series. This approach provides long-term support and production-grade reliability.

14. What is the function of CloVis Central in managing this system?

+

CloVis Central™ is a device management platform based on the cloud and acts as a unified platform for feature updates, system upgrades, and fleet maintenance.

15. What OTA update architecture is supported?

+

The architecture supports secure Over-The-Air updates for both the base system and containerized applications. Integration with third-party update services such as Azure IoT is under consideration.

16. What secure boot mechanisms are used?

+

The compute box uses the NVIDIA® Secure Boot built into the Jetson platform hardware. All bootloader and kernel images are encrypted for prevention against unauthorized or compromised firmware execution. A hardware-based UUID is optionally used to enable authentication of the device.

Read Blog: What is Secure Boot and How Does it Safeguard Edge AI Vision Deployments? - e-con Systems

17. What network security and remote access protections exist?

+

Remote access is secured through password-based or key-based authentication. The system includes provisions for integrating TPM version 2.0 or equivalent secure components in future versions.

18. How is device lockdown managed?

+

Device lockdown is implemented through multiple security mechanisms:

  • Root shell access is disabled in production configurations.
  • Software reflashing can be performed only by authenticated users.
  • A fail-safe mode ensures the system can recover to a secure operational state during critical failures or security incidents.

19. What functional safety mechanisms are implemented?

+
  • MCU-based hardware watchdog to detect and recover from system hangs or boot faults
  • Software health monitoring with recovery mechanisms for cameras
  • Controlled power sequencing
  • Critical event logging for diagnostics
  • Optional GPIOs or error pins signaling for external health monitoring

20. What software validation processes are defined?

+

Software validation encompasses extended runtime stability testing (soak test/burn-in), boot/reboot cycle validation, watchdog and fault recovery verification, peripheral stress testing, and CPU/GPU stress testing to ensure system robustness under all operational conditions.

21. What is the size and structure of the enclosure?

+

The vision box has dimensions of 326 x 179 x 110 mm in a rugged box PC form factor. The enclosure features an aluminum body with gasketed ends for IP protection.

22. What ingress protection rating is achieved?

+

The system is designed to achieve IP67 certification, providing protection against dust ingress and temporary water immersion.

23. What emissions and environmental compliance standards are met?

+

The vision box complies with FCC Part 15 Class A and CISPR25 standards. Environmental compliance includes RoHS 3 and REACH requirements.

24. What industry-specific certifications are targeted?

+

The product targets compliance with ISO16750 road vehicle environmental conditions and testing standards, along with IP67 ingress protection, ensuring suitability for automotive and industrial mobile applications.

25. What hardware validation testing is planned?

+

The validation includes thermal cycling tests, vibration and mechanical shock testing as per road vehicle standards, and comprehensive EMC (Electromagnetic Compatibility) and ESD (Electrostatic Discharge) testing.

26. What is the software support lifecycle?

+

The product includes a 5-year software update lifecycle, covering security patches, feature updates, and platform maintenance.