Hardware & Software Setup Workflow
Proper installation and configuration of the SPH Engineering Integrated Systems requires methodical execution of hardware mounting, electrical integration, and software initialization procedures. This section provides step-by-step guidance through the complete setup workflow, from physical installation of components through final validation checks. Following this structured approach ensures reliable system operation and minimizes troubleshooting requirements during operational deployment.
Hardware Installation Procedures
Begin hardware installation with the aircraft powered down and battery removed. The SkyHub onboard computer mounts to the top plate of the DJI M300/M350 using the provided mounting bracket and vibration dampers. Position the unit to avoid interference with GPS antennas and ensure adequate ventilation around cooling vents. Route power cables through existing cable channels, connecting to the aircraft's power distribution board using the supplied XT30 or XT60 connectors depending on your platform configuration. Verify voltage output matches SkyHub specifications (typically 12-24V DC) before applying power. Secure all cable connections with cable ties, ensuring no loose wires can interfere with propeller movement or gimbal operation.
01
SkyHub Mounting and Power Connections
Install mounting bracket to top plate using M3 screws with thread-locker compound. Position SkyHub ensuring heat sink faces forward for optimal cooling during flight. Connect main power lead to aircraft power bus, verify polarity with multimeter before energizing system. Install backup power connection if redundant configuration is required for your operational profile.
02
TTF Sensor Installation
Mount True Terrain Following sensor to undercarriage using supplied bracket, ensuring sensor face is perpendicular to aircraft Z-axis within ±2 degrees. Position sensor forward of battery compartment to minimize prop wash interference. Connect sensor data cable (typically CAN or UART) to designated SkyHub port. Route cable away from motors and ESCs to prevent electromagnetic interference affecting measurements.
03
Obstacle Avoidance Sensor Array
Install forward-facing OA sensors to front landing gear arms at manufacturer-specified height and angle. Mount lateral sensors to left and right boom sections, ensuring unobstructed 120-degree field of view. Position upward sensor on top plate with clear sky visibility. Connect all sensors to SkyHub using labeled connectors, verifying each channel lights up during power-on self-test sequence.
04
Custom Payload Sensor Integration
Mount payload to gimbal interface or dedicated payload bay depending on sensor type and mission requirements. Establish data connection through appropriate interface—UART for serial sensors, Ethernet for IP-based cameras, or GPIO for trigger signals. Configure power delivery to match sensor specifications, using DC-DC converters if voltage conversion is required. Document all pin assignments and communication parameters for software configuration phase.
Software Configuration in UgCS-CPM
With hardware installation complete, power up the aircraft and establish connection to the SkyHub via Ethernet or Wi-Fi depending on your configuration. Launch UgCS-CPM version 4.3 on your ground station computer and initiate the device discovery process. The software should automatically detect the SkyHub and display its network address. If automatic discovery fails, manually enter the SkyHub IP address (default 192.168.1.100) to establish connection. Navigate to the System Configuration panel where you'll configure device recognition, communication protocols, and initial operating parameters.
Begin software setup by verifying firmware versions for all connected components. UgCS-CPM will query each device and display firmware information in the Device Manager panel. Ensure all components are running compatible firmware versions as specified in the release notes—version mismatches can cause communication failures or degraded performance. If firmware updates are required, follow the update sequence: SkyHub core firmware first, then sensor firmware, finally payload firmware. Never interrupt the update process or power cycle devices during firmware installation as this can result in bricked hardware requiring factory recovery procedures.
Configuration Checklist
- Device Recognition: Verify all sensors appear in device list with green status indicators
- Communication Protocol Setup: Configure baud rates, CAN bus IDs, and network addresses for each device
- Data Link Verification: Run built-in diagnostics to confirm sensor data streams are flowing correctly
- Coordinate System Alignment: Set reference frames for sensor measurements relative to aircraft body frame
- Update Rate Configuration: Define sensor sampling frequencies appropriate for mission requirements
- Telemetry Logging: Enable data recording for post-flight analysis and system validation
Safety and Validation Checks
System validation begins with the power-up sequence verification. With aircraft on stable ground surface, power on the system and observe the initialization sequence. SkyHub should complete boot within 45 seconds, indicated by solid green LED. Each sensor should perform a self-test, with status LEDs cycling through amber to green as tests complete. The UgCS-CPM interface will display initialization progress—any devices showing red status require troubleshooting before flight operations. Check the event log for error messages that may indicate configuration issues or hardware faults.
Execute sensor calibration procedures as specified for each component. Terrain-following sensors require ground reference calibration—place aircraft on known flat surface and run the calibration routine to establish zero offset. Obstacle avoidance sensors need field-of-view validation—walk around aircraft while sensors are active, confirming detection range and response time meet specifications. Custom payloads should be tested for data integrity by capturing sample measurements and verifying output format matches expected specifications. Document all calibration values and save configuration to persistent memory.
Pre-Flight Safety Verification
- Confirm all sensor health status indicators show green
- Verify GPS lock with adequate satellite count (12+ recommended)
- Test emergency stop response by triggering manual failsafe
- Validate home point is correctly set at takeoff location
- Confirm battery voltage sufficient for planned mission duration plus 20% reserve
- Check radio link quality and verify control authority transfer to UgCS-CPM
Fail-Safe Configuration
Configure multiple layers of fail-safe protection. Primary fail-safe: loss of ground station link triggers return-to-home with obstacle avoidance active. Secondary fail-safe: low battery threshold initiates automatic return when 30% capacity remains. Tertiary fail-safe: sensor failure detected triggers mission abort and controlled descent. Set geo-fence boundaries appropriate for operational area, with violation triggering immediate mission halt. Test each fail-safe mode on ground with propellers removed to verify correct system response.
Advanced Configuration & Operational Readiness
With hardware installed and basic software configuration complete, the final phase focuses on advanced feature configuration and comprehensive system validation. This section covers the specialized setup procedures for True Terrain Following and Obstacle Avoidance systems, along with payload validation protocols and operational readiness testing. Mastering these advanced configurations enables you to deploy DJI M300/M350 platforms for demanding autonomous missions requiring precision altitude control and dynamic obstacle response in complex operational environments.
True Terrain Following Configuration
True Terrain Following (TTF) represents one of the most sophisticated capabilities of the integrated system, enabling the aircraft to maintain constant height above ground level regardless of terrain variations. This feature is critical for low-altitude survey missions, powerline inspection, and any operation requiring consistent standoff distance from the ground surface. Configuration begins in the UgCS-CPM Terrain Following panel where you define altitude control parameters, sensor fusion settings, and safety boundaries that govern autonomous altitude adjustments during flight operations.
The altitude control logic operates on a predictive model that combines real-time sensor measurements with mission planning data. Set your target AGL height (typically 30-120 meters depending on mission requirements and sensor specifications) in the mission parameters. Configure the maximum climb and descent rates—conservative values like 2 m/s for climb and 3 m/s for descent provide smooth terrain tracking while maintaining adequate safety margins. The system uses a look-ahead algorithm that analyzes terrain profile ahead of the aircraft, pre-calculating altitude changes needed to maintain constant AGL as the aircraft advances along the mission path.
Terrain sensing validation ensures the TTF sensor provides accurate distance measurements across varying surface conditions. Test sensor performance over different terrain types expected in your operational area: bare earth, vegetation, water surfaces, and structures. Each surface type reflects ranging signals differently—vegetation may return weak signals while water can cause specular reflection issues. Configure the sensor filter settings to reject outlier measurements and set confidence thresholds appropriate for your terrain complexity. Enable terrain data logging during test flights to analyze sensor performance and refine filter parameters based on actual operational data.
TTF Safety Parameters
- Minimum AGL: 15m absolute floor regardless of target height
- Maximum Terrain Slope: 30° limit for safe tracking
- Sensor Valid Range: Reject measurements outside 1-200m window
- Emergency Climb Trigger: Sensor failure initiates 10m/s climb to safe altitude
- Terrain Database Fallback: Use DEM data if sensor reads invalid
Obstacle Avoidance System Configuration
The Obstacle Avoidance (OA) system provides critical safety enhancement for autonomous operations, particularly in GPS-challenged environments or areas with vertical obstacles like powerlines, towers, and vegetation. Configuration focuses on defining detection zones, establishing safety margins, and programming system behavior when obstacles are detected during mission execution. Access the OA Configuration panel in UgCS-CPM and begin by defining the detection envelope—the three-dimensional space around the aircraft that sensors actively monitor for obstacles.
Detection Zones
Configure forward detection zone extending 30-50 meters ahead with 60° horizontal field of view. Set lateral zones at 15 meters with 90° FOV for side obstacle awareness. Upward zone monitors 10 meters above aircraft for overhead clearance. Each zone has adjustable sensitivity—higher sensitivity detects smaller obstacles but increases false positive rate.
Safety Margins
Establish buffer zones around detected obstacles. Primary margin: 5 meters minimum clearance triggers path adjustment. Secondary margin: 3 meters triggers immediate stop and hover. Critical margin: 1.5 meters initiates emergency ascent maneuver. Margins scale with aircraft velocity—faster flight speeds require proportionally larger safety buffers.
Response Behavior
Define system actions when obstacles detected. Mode 1: Path adjustment—aircraft autonomously deviates around obstacle while continuing mission. Mode 2: Stop and alert—aircraft halts, notifies operator, awaits manual override. Mode 3: Automatic return—obstacle triggers mission abort and return-to-home. Select mode based on mission criticality and operational risk tolerance.
During autonomous flight, the OA system continuously evaluates sensor data against configured parameters, making millisecond-level decisions to maintain safe flight paths. The system can differentiate between static obstacles (buildings, trees) and dynamic obstacles (moving vehicles, other aircraft) through velocity vector analysis. Configure the obstacle persistence threshold to filter transient detections like birds or windblown debris—objects must be detected for minimum 0.5 seconds before triggering avoidance response. Test OA functionality in controlled environment by setting up obstacle course with known object positions, flying autonomous missions at various speeds and approach angles to validate detection reliability and response appropriateness.
Payload Sensor Validation and System Readiness Testing
Custom payload validation ensures third-party sensors integrate correctly with the mission execution framework. Begin by verifying payload data synchronization with aircraft telemetry—sensor timestamps must align with GPS time within 100 milliseconds for accurate geo-referencing of collected data. Configure trigger modes: free-run for continuous data collection, time-interval for scheduled sampling, or distance-interval for consistent ground spacing. Test each trigger mode, reviewing captured data to confirm timing accuracy and data completeness. Validate that sensor data logs include all required metadata: GPS coordinates, altitude, aircraft attitude, and timestamp for every sample.
Pre-Operational Flight Testing
Execute graduated test flight sequence before declaring system operational:
- Hover Test (5 min): Verify all systems stable in stationary flight, no sensor anomalies or unexpected warnings
- Manual Flight Test (10 min): Pilot flies basic pattern while monitoring UgCS-CPM displays for system health
- Simple Autonomous Mission (15 min): Execute basic waypoint mission without terrain following or obstacle avoidance active
- TTF Test Flight (20 min): Enable terrain following over known terrain, validate altitude tracking accuracy
- OA Test Flight (20 min): Fly mission with deliberate obstacle encounters, confirm detection and avoidance responses
- Full Mission Rehearsal (30 min): Execute representative operational mission profile with all systems active
Course Outcomes and Professional Competencies
Upon completing this training program, you will possess the technical competency to independently execute complete integration of SPH Engineering systems on DJI M300/M350 platforms. You'll understand the architecture of advanced UAV systems, can troubleshoot hardware and software issues, and have demonstrated ability to configure complex autonomous flight features safely and effectively. This knowledge base enables you to support sophisticated UAV operations including precision agriculture, infrastructure inspection, surveying and mapping, emergency response, and specialized sensor missions requiring autonomous flight in challenging environments.
Your preparation of DJI platforms for advanced missions ensures operational safety, mission reliability, and data quality. You'll bring confidence to mission planning knowing systems are properly configured with appropriate fail-safes and validated through comprehensive testing protocols. This expertise positions you as a valuable technical resource for organizations deploying enterprise UAV solutions, capable of bridging the gap between manufacturer specifications and operational requirements in real-world deployments where precision, reliability, and safety are non-negotiable.
Independent System Setup
Complete SPH Engineering Integrated Systems installation from hardware mounting through software configuration without external technical support. Troubleshoot common integration issues and optimize system performance for specific operational requirements.
Platform Preparation Confidence
Prepare DJI M300/M350 aircraft for demanding autonomous missions with full understanding of system capabilities, limitations, and safety margins. Make informed decisions about mission feasibility based on technical requirements and environmental conditions.
Operational Readiness
Deploy configured systems for autonomous, low-altitude, and sensor-based operations with confidence in system reliability and mission success probability. Execute comprehensive pre-flight validation ensuring aircraft meets operational standards.
Key Takeaways
System Reliability: Properly configured SPH Engineering Integrated Systems transform DJI platforms into mission-critical tools capable of autonomous operations in complex environments. Reliability stems from methodical installation, thorough configuration, and comprehensive validation—shortcuts in any phase compromise operational safety and mission success.
Safety First: Multiple layers of fail-safe protection, conservative operating margins, and thorough pre-flight testing create the foundation for safe autonomous operations. Understanding system behavior in failure modes and validating emergency response procedures protects both equipment and operational personnel.
Configuration Precision: Advanced features like True Terrain Following and Obstacle Avoidance require precise configuration matched to operational requirements and environmental conditions. Generic settings rarely deliver optimal performance—customization based on mission profile, terrain characteristics, and risk tolerance maximizes system effectiveness while maintaining appropriate safety margins.