diff --git a/HACKRF_PORTAPACK/DETECTION_GUIDE.md b/HACKRF_PORTAPACK/DETECTION_GUIDE.md new file mode 100644 index 0000000..801dcb2 --- /dev/null +++ b/HACKRF_PORTAPACK/DETECTION_GUIDE.md @@ -0,0 +1,987 @@ +# Comprehensive Drone Detection Guide + +## Table of Contents +1. [Introduction](#introduction) +2. [Legal Status](#legal-status) +3. [Hardware Setup](#hardware-setup) +4. [Basic Detection](#basic-detection) +5. [Advanced Scanning](#advanced-scanning) +6. [RSSI Interpretation](#rssi-interpretation) +7. [Alert Configuration](#alert-configuration) +8. [Signal Analysis](#signal-analysis) +9. [Logging and Documentation](#logging-and-documentation) +10. [Multi-Band Strategies](#multi-band-strategies) +11. [Battery Optimization](#battery-optimization) +12. [Troubleshooting](#troubleshooting) + +--- + +## Introduction + +Drone detection using HackRF One and PortaPack H4M is 100% legal as it involves passive monitoring only - you're receiving signals, not transmitting. This guide covers everything from basic detection to advanced signal analysis. + +### What You Can Detect: +- RC control signals (433/915 MHz, 2.4 GHz) +- FPV video downlinks (1.2 GHz, 5.8 GHz) +- Telemetry data streams +- GPS signals (monitoring only) +- WiFi-based drone control +- Digital drone protocols + +### Detection Range: +Highly variable based on: +- **Antenna quality**: Better antenna = longer range +- **Frequency band**: Lower frequencies travel farther +- **Drone transmit power**: DJI @ 2.4 GHz stronger than toys +- **Environment**: Open field vs urban canyon +- **Interference**: Clean RF environment vs noisy +- **Gain settings**: Higher gain = better sensitivity + +**Typical Ranges:** +- Consumer drones (DJI, etc.): 500m - 2km +- FPV racing drones: 300m - 1.5km +- Toy drones: 100m - 500m +- With directional antenna: 2x - 5x improvement + +--- + +## Legal Status + +### ✅ LEGAL: Receive-Only Monitoring + +**You CAN legally:** +- Monitor any frequency (public airwaves) +- Record signal characteristics +- Analyze protocols +- Log drone activity +- Share technical findings +- Use for security awareness +- Educational purposes + +**This is protected by:** +- First Amendment (USA) - Information gathering +- FCC Part 15 - General receiving not regulated +- Similar laws internationally + +### ❌ What You CANNOT Do: + +- Jam or interfere with signals +- Transmit on unauthorized frequencies +- Control drones you don't own +- Use information for criminal purposes +- Violate privacy laws with captured data + +--- + +## Hardware Setup + +### Antenna Selection + +Different frequencies require different antennas for optimal detection: + +#### 433 MHz Band: +- **Type**: UHF quarter-wave whip or dipole +- **Length**: ~17.3 cm for quarter-wave +- **Connector**: SMA male +- **Gain**: 2-5 dBi typical +- **Recommendation**: Generic 433 MHz antenna or build dipole + +#### 915 MHz Band: +- **Type**: UHF quarter-wave whip +- **Length**: ~8.2 cm for quarter-wave +- **Connector**: SMA male +- **Gain**: 2-5 dBi +- **Recommendation**: 900 MHz ISM antenna + +#### 1.2 GHz Band: +- **Type**: Dipole or patch antenna +- **Polarization**: Horizontal or circular +- **Gain**: 5-10 dBi +- **Recommendation**: 1.2 GHz FPV patch antenna + +#### 2.4 GHz Band: +- **Type**: Rubber duck, dipole, or patch +- **Polarization**: Vertical (most common) +- **Gain**: 2-5 dBi +- **Recommendation**: WiFi antenna (very common and cheap) + +#### 5.8 GHz Band: +- **Type**: Patch, pagoda, or cloverleaf +- **Polarization**: Circular (RHCP for most FPV) +- **Gain**: 3-8 dBi +- **Recommendation**: FPV pagoda or 5.8 GHz patch + +#### Multi-Band Option: +- **Type**: Discone or wideband antenna +- **Coverage**: 25 MHz - 1.3 GHz (typical) +- **Gain**: Lower than dedicated antennas +- **Use Case**: Quick scanning without antenna changes +- **Trade-off**: Reduced sensitivity on all bands + +### Physical Setup + +**Positioning:** +1. **Height**: Higher is better (reduce ground clutter) +2. **Clear line of sight**: Minimize obstructions +3. **Away from interference**: Distance from WiFi routers, etc. +4. **Stable mounting**: Tripod or secure position +5. **Antenna orientation**: Vertical for most (match drone's polarization) + +**Power:** +- Use quality USB cable (power loss in cheap cables) +- External battery: 10,000+ mAh recommended +- USB power supply: 2A minimum +- Monitor battery level regularly + +--- + +## Basic Detection + +### Method 1: Quick Scan (All Bands) + +**Best for:** Rapid check if any drone activity present + +``` +1. Navigate to: Receiver → Freqman +2. Select: DRONE_SCAN_ALL.TXT +3. Settings: + - RSSI Threshold: -70 dBm + - Audio Alert: ON + - Scan Speed: Medium +4. Gains: + - RF: 14 dB + - IF: 40 dB + - BB: 32 dB +5. Start scanning +``` + +**Expected results in 5-10 minutes:** +- If drones present: Multiple alerts, consistent signals +- If no drones: Occasional false triggers from WiFi, etc. + +### Method 2: Specific Band Scan + +**Best for:** Focused detection of specific drone types + +**Consumer Drones (DJI, etc.):** +``` +File: DRONE_SCAN_2G4.TXT +Threshold: -65 dBm (strong signal expected) +Notes: Also catches WiFi - ignore home networks +``` + +**FPV Racing Drones:** +``` +File: DRONE_SCAN_5G8.TXT +Threshold: -70 dBm +Notes: Video downlink, very characteristic +``` + +**Long-Range RC:** +``` +File: DRONE_SCAN_915.TXT or DRONE_SCAN_433.TXT +Threshold: -75 dBm +Notes: Weaker signals, need more sensitivity +``` + +### Method 3: Continuous Monitoring + +**Best for:** Security, event monitoring, long-term observation + +``` +1. Choose appropriate band(s) +2. Set conservative threshold: -75 dBm +3. Enable logging (if available) +4. Reduce screen brightness (battery saving) +5. Let run continuously +6. Check periodically for alerts +``` + +--- + +## Advanced Scanning + +### Optimizing Scan Speed + +**Fast Scan (50ms per channel):** +- Pros: Cover band quickly, good for mobile use +- Cons: Might miss brief signals +- Use: When walking/moving, quick checks + +**Medium Scan (100-200ms per channel):** +- Pros: Balance of speed and sensitivity +- Cons: Takes longer to cycle through +- Use: General purpose, default recommendation + +**Slow Scan (500ms+ per channel):** +- Pros: Catch brief signals, better sensitivity +- Cons: Slow to cover full band +- Use: Stationary monitoring, maximizing detection + +### Gain Settings Deep Dive + +HackRF has three gain stages: + +#### RF Gain (0-14 dB) +- **Controls**: Front-end amplifier +- **Effect**: First-stage amplification +- **Recommendation**: Start at 14 dB, reduce if signals too strong +- **Note**: Most critical for weak signals + +#### IF Gain (0-40 dB) +- **Controls**: Intermediate frequency amplifier +- **Effect**: Main amplification stage +- **Recommendation**: 32-40 dB for detection +- **Note**: Can increase for distant signals + +#### Baseband Gain (0-62 dB) +- **Controls**: Final amplification before ADC +- **Effect**: Fine-tuning sensitivity +- **Recommendation**: 20-40 dB typically +- **Note**: High values increase noise floor + +**Optimal Settings by Scenario:** + +| Scenario | RF | IF | BB | Notes | +|----------|----|----|-----|-------| +| Close range (0-100m) | 0 | 20 | 20 | Prevent overload | +| Medium range (100-500m) | 14 | 32 | 32 | Balanced | +| Long range (500m+) | 14 | 40 | 40 | Maximum sensitivity | +| Urban/noisy | 8 | 32 | 24 | Reduce noise | +| Rural/quiet | 14 | 40 | 36 | Maximize sensitivity | + +### Frequency Hopping Detection + +Many modern drones use frequency hopping (e.g., FrSky, Crossfire, ELRS): + +**Characteristics:** +- Rapid switching between channels +- Brief signal bursts (ms) +- Repeating pattern +- Multiple frequencies in sequence + +**Detection Strategy:** +1. Slow down scan speed (catch brief signals) +2. Use wider bandwidth setting +3. Monitor multiple frequencies in range +4. Look for pattern in spectrum analyzer +5. Note: Will see multiple frequencies active + +**Example: FrSky D16** +- Hops across 47 channels in 2.4 GHz +- ~9ms per hop +- Repeating sequence +- You'll see bursts on multiple channels + +### Directional Finding + +**With Standard Omni Antenna:** +- Walk in different directions +- Note signal strength changes +- Stronger = closer to that direction +- Crude but effective for general direction + +**With Directional Antenna:** +- Rotate antenna (yagi, patch, etc.) +- Note maximum signal direction +- Take bearings from multiple locations +- Triangulate drone position +- Much more accurate (5-15° accuracy possible) + +**Procedure:** +1. Detect drone signal +2. Note frequency +3. Switch to directional antenna +4. Rotate for maximum signal +5. Mark bearing/direction +6. Move to new location (100m+) +7. Repeat bearing measurement +8. Plot lines on map - intersection = drone location + +--- + +## RSSI Interpretation + +### Understanding RSSI Values + +**RSSI = Received Signal Strength Indicator** +- Measured in dBm (decibels relative to 1 milliwatt) +- Negative values (e.g., -70 dBm) +- More negative = weaker signal +- Less negative = stronger signal + +### RSSI Scale + +``` + -40 dBm |████████████| VERY STRONG - Drone very close (0-20m) + | | Possibly on ground near you + | + -50 dBm |██████████ | STRONG - Drone nearby (20-100m) + | | Clear detection, good tracking + | + -60 dBm |████████ | GOOD - Medium distance (100-300m) + | | Reliable detection + | + -70 dBm |██████ | MODERATE - Far but detectable (300-1000m) + | | Good threshold for alerts + | + -80 dBm |████ | WEAK - Long range or low power (1000m+) + | | May be toy drone nearby or DJI far away + | + -90 dBm |██ | VERY WEAK - Extreme range or obstructed + | | Borderline detection, many false positives + | +-100 dBm | | NOISE FLOOR - Not a real signal + | | Just background RF noise +``` + +### Signal Strength Patterns + +**Steady Strong Signal:** +- Likely hovering drone +- Or slowly moving +- Or ground-based control station + +**Slowly Varying Signal:** +- Drone moving toward/away from you +- Normal flight pattern +- Track changes to estimate movement + +**Rapidly Fluctuating:** +- Frequency hopping system +- Moving through obstruction +- Multipath fading +- Fast-moving drone + +**Bursts/Intermittent:** +- Telemetry data (periodic) +- Frequency hopping (caught in scan) +- Drone far away (borderline range) +- Possible false positive + +### Distance Estimation + +**Very rough guide** (many variables affect this): + +| RSSI | Distance (2.4 GHz consumer) | Distance (5.8 GHz FPV) | +|------|----------------------------|----------------------| +| -40 dBm | 0-20m | 0-10m | +| -50 dBm | 20-100m | 10-50m | +| -60 dBm | 100-300m | 50-200m | +| -70 dBm | 300-1000m | 200-500m | +| -80 dBm | 1000m+ | 500m+ | + +**Variables that affect distance:** +- Drone transmit power +- Antenna gains (both sides) +- Obstructions (buildings, trees) +- Weather (rain attenuates) +- Frequency (lower travels farther) + +--- + +## Alert Configuration + +### Audio Alerts + +**Configure in:** SETTINGS/alert_settings.txt + +**Alert Tone Strategy:** + +**Different tones for different bands:** +``` +433 MHz: 800 Hz (low tone) +915 MHz: 1000 Hz (medium-low) +2.4 GHz: 1400 Hz (medium-high) +5.8 GHz: 1600 Hz (high tone) +GPS: 1800 Hz (very high, urgent) +``` + +**Why:** Instantly recognize which band detected without looking + +**Alert Duration:** +- Short (100ms): Brief notification +- Medium (200ms): Standard (recommended) +- Long (500ms): Ensure you don't miss it + +**Volume:** +- 50%: Indoor, close monitoring +- 75%: Outdoor, ambient noise (recommended) +- 100%: Noisy environment, maximum alert + +### Visual Alerts + +**LED/Screen Flash:** +- Red: High-priority detection (2.4/5.8 GHz) +- Yellow: Medium priority (1.2 GHz) +- Green: Low priority (433/915 MHz) +- Flashing: Active signal +- Solid: Signal locked + +**On-Screen Information:** +- Display frequency detected +- Show RSSI value +- Show signal duration +- Time stamp +- Band/channel identifier + +### Alert Conditions + +**Threshold Settings:** + +**Conservative (fewer false positives):** +``` +RSSI Threshold: -60 dBm +Minimum Duration: 200ms +Cooldown: 5 seconds +``` + +**Balanced (recommended):** +``` +RSSI Threshold: -70 dBm +Minimum Duration: 100ms +Cooldown: 2 seconds +``` + +**Aggressive (maximum sensitivity):** +``` +RSSI Threshold: -80 dBm +Minimum Duration: 50ms +Cooldown: 1 second +``` + +**Pattern Matching:** +- Look for repeating signals +- Filter out one-off noise spikes +- Confirm with multiple detections +- Reduces false positives significantly + +--- + +## Signal Analysis + +### Using Spectrum Analyzer + +After detecting a signal, analyze it: + +``` +1. Note frequency from scanner +2. Stop scanner +3. Go to: Spectrum Analyzer +4. Enter frequency (or range) +5. Set appropriate bandwidth +6. Observe signal characteristics +``` + +**What to Look For:** + +**Continuous Carrier:** +- Steady tone +- Likely analog video or simple RC +- Common in 5.8 GHz FPV + +**Bursting Signal:** +- Periodic pulses +- Digital telemetry or control +- Note burst rate and pattern + +**Wideband Noise:** +- Spread across wide frequency range +- Digital spread-spectrum (ELRS, Crossfire) +- Or LoRa-based systems + +**Multiple Carriers:** +- Frequency hopping visible +- Multiple simultaneous signals +- Multiple drones present + +### Waterfall Display + +**Enables:** +- Visual history of signal over time +- Identify patterns and timing +- See frequency hopping +- Differentiate signal types + +**Colors indicate signal strength:** +- Blue/Black: Noise floor +- Green/Yellow: Moderate signal +- Orange/Red: Strong signal + +**Patterns:** +- **Horizontal line**: Steady carrier (analog video) +- **Vertical bars**: Bursts (digital data) +- **Diagonal lines**: Frequency drift +- **Multiple bars**: Frequency hopping +- **Spread**: Wideband digital + +### Modulation Identification + +**AM (Amplitude Modulation):** +- Variable amplitude +- Common in older RC systems +- Simple detection + +**FM (Frequency Modulation):** +- Constant amplitude, varies frequency +- Analog video links (1.2/5.8 GHz) +- Better noise immunity than AM + +**GFSK (Gaussian FSK):** +- Digital modulation +- FrSky, FlySky protocols +- Smooth frequency transitions + +**Spread Spectrum:** +- FHSS: Frequency Hopping (FrSky, Futaba) +- DSSS: Direct Sequence (some WiFi modes) +- Wide bandwidth, noise-like + +**LoRa:** +- Chirp spread spectrum +- ELRS, Crossfire use this +- Distinctive "chirp" in waterfall +- Very long range + +### Protocol Identification + +**Clues to identify protocol:** + +**FrSky D16/D8:** +- 2.4 GHz +- Frequency hopping (47 channels) +- ~9ms hop interval +- 1 MHz spacing + +**FlySky AFHDS:** +- 2.4 GHz +- 16 channels +- ~5 MHz spacing +- Less complex hopping + +**ExpressLRS:** +- 900 MHz or 2.4 GHz +- LoRa chirps in waterfall +- High packet rate (50-1000 Hz) +- Wideband + +**Crossfire:** +- 868/915 MHz +- LoRa modulation +- Lower packet rate +- Very robust + +**DJI:** +- 2.4 GHz and 5.8 GHz +- Proprietary protocols +- OcuSync: wideband, frequency agile +- Strong signals (high power) + +**Analog Video:** +- 1.2 or 5.8 GHz +- FM modulation +- 6-8 MHz bandwidth +- Continuous carrier +- Sync pulses visible + +--- + +## Logging and Documentation + +### Manual Logging + +Create log entries for detections: + +``` +Date/Time: 2024-12-26 14:35:22 +Frequency: 2447 MHz +RSSI: -62 dBm +Duration: Continuous (5+ minutes) +Band: 2.4 GHz +Signal Type: Continuous, likely DJI +Location: [Your location] +Weather: Clear, light wind +Notes: Signal appeared suddenly, moved away gradually +``` + +### Automated Logging (if supported) + +Some PortaPack versions support logging to CSV: + +``` +timestamp,frequency,rssi,duration,notes +2024-12-26T14:35:22,2447000000,-62,300,2.4G_continuous +2024-12-26T14:42:18,5843000000,-58,180,5.8G_FPV_video +``` + +### Data Analysis + +**Look for patterns:** +- Time of day (when are drones active?) +- Day of week (weekends vs weekdays) +- Frequency bands used (consumer vs FPV) +- Signal strength trends (getting closer/farther) +- Duration (quick flyby vs loitering) + +**Create detection profile:** +- Most common frequencies +- Typical signal strengths +- Peak activity times +- Common flight patterns + +--- + +## Multi-Band Strategies + +### Simultaneous Multi-Band + +**Not possible with single HackRF** (can only tune one frequency at a time) + +**But you can:** + +**Sequential Scanning:** +1. Scan 2.4 GHz (most common) - 2 minutes +2. Quick scan 5.8 GHz - 1 minute +3. Quick scan 915 MHz - 1 minute +4. Back to 2.4 GHz +5. Repeat cycle + +**Priority-Based:** +1. Start with DRONE_SCAN_ALL.TXT (hits all bands) +2. When detection, switch to specific band file +3. Monitor that band continuously +4. Resume all-band after signal lost + +### Two-HackRF Setup + +**If you have two HackRF devices:** + +**HackRF #1:** +- Monitor 2.4 GHz (control) +- Continuous scanning +- Primary alert source + +**HackRF #2:** +- Monitor 5.8 GHz (video) +- Continuous scanning +- Confirm detections + +**Benefits:** +- True simultaneous multi-band +- Correlate control and video signals +- Better directional finding +- Redundancy + +### Band Selection Strategy + +**Choose based on your scenario:** + +**General Security/Unknown Drones:** +- Start: DRONE_SCAN_ALL.TXT +- Reason: Don't know what to expect + +**Consumer Drone Heavy Area:** +- Focus: 2.4 GHz (DRONE_SCAN_2G4.TXT) +- Reason: DJI and others use 2.4 GHz control + +**FPV Racing Event:** +- Focus: 5.8 GHz (DRONE_SCAN_5G8.TXT) +- Reason: All FPV video here + +**Rural Long-Range:** +- Check: 433/915 MHz first +- Then: 2.4 GHz +- Reason: Long-range systems use UHF + +--- + +## Battery Optimization + +### Power Consumption Breakdown + +**HackRF One power usage:** +- Idle: ~0.5W +- Receiving: ~1.5W +- Transmitting: ~2.5W (not used in detection) +- PortaPack display: +0.3-0.5W + +**Battery capacity vs runtime:** +- 10,000 mAh @ 5V = 50 Wh +- At 1.5W: ~33 hours theoretical +- Practical: ~20-25 hours (efficiency losses) + +### Extending Battery Life + +**Display Management:** +1. Reduce brightness: 25-50% +2. Disable waterfall (text mode only) +3. Shorter screen timeout +4. Black background (OLED screens) + +**Scanning Optimization:** +1. Narrower frequency ranges +2. Slower scan rate (less processing) +3. Lower sample rates where possible +4. Disable logging (SD card writes) + +**Gain Settings:** +1. Don't maximize unless needed +2. Lower gain = less power in amplifiers +3. Adjust based on actual signal strength +4. Start low, increase if needed + +**Operational:** +1. Power off between monitoring sessions +2. Use airplane mode if PortaPack supports it +3. Pause scanning when not needed +4. Close unnecessary apps/features + +**Battery Selection:** +- High-quality cells (Samsung, Panasonic) +- 2A+ output capability +- USB-C PD for fast charging +- 20,000+ mAh for all-day operation + +### Battery Life Estimates + +| Configuration | Runtime (10,000 mAh) | +|--------------|---------------------| +| Maximum power (bright screen, fast scan) | 2-3 hours | +| Standard operation | 4-6 hours | +| Optimized (dim screen, slow scan) | 8-12 hours | +| Minimal (pause between scans) | 15-20 hours | + +--- + +## Troubleshooting + +### No Signals Detected + +**Checklist:** +1. ✓ Antenna connected and appropriate for frequency? +2. ✓ RSSI threshold not too high (-70 to -80 dBm)? +3. ✓ Gain settings adequate (RF: 14, IF: 40, BB: 32)? +4. ✓ Correct frequency file loaded? +5. ✓ Scanner actually running (not paused)? +6. ✓ Are drones actually present nearby? + +**Tests:** +- Try scanning 2.4 GHz with phone WiFi hotspot on +- Should immediately detect WiFi signals +- If this works: Hardware OK, no drones nearby +- If this fails: Hardware/setup issue + +### Too Many False Alerts + +**Causes:** +- RSSI threshold too low (too sensitive) +- In RF-noisy environment (urban, near WiFi) +- Gain too high (amplifying noise) +- Wrong antenna (picking up everything) + +**Solutions:** +1. Raise threshold: -60 dBm instead of -80 +2. Reduce gain settings +3. Use narrower bandwidth +4. Enable pattern matching +5. Increase minimum duration +6. Add alert cooldown period + +### Weak Signals Only + +**Possible issues:** +- Antenna not matched to frequency +- Antenna not connected properly +- Gain settings too low +- Sample rate too low +- Interference/noise masking signals + +**Solutions:** +1. Verify antenna: Right type? Tight connection? +2. Increase gains incrementally +3. Try different antenna orientation +4. Move to clearer RF environment +5. Check antenna SWR if possible + +### Signal Detection Inconsistent + +**Causes:** +- Drone frequency hopping (normal behavior) +- Drone at edge of range +- Obstructions blocking signal +- Interference from local sources +- Scan speed too fast + +**Solutions:** +1. Slow down scan rate +2. Use narrower frequency range +3. Increase gain slightly +4. Note pattern: Periodic = likely frequency hopping +5. Switch to specific band, not all-band + +### Device Overheating + +**Symptoms:** +- HackRF/PortaPack hot to touch +- Performance degradation +- Unexpected shutdowns + +**Solutions:** +1. Power off immediately if very hot +2. Remove from enclosure for better airflow +3. Reduce gain settings (less power) +4. Take breaks between scanning sessions +5. Add heatsinks to HackRF chips +6. Don't use in direct sunlight +7. Consider active cooling (small fan) + +### SD Card Issues + +**Problems:** +- Files not loading +- Can't save captures +- Corrupted data + +**Solutions:** +1. Reformat as FAT32 (not exFAT or NTFS) +2. Use quality name-brand SD card +3. Class 10 or UHS-I rating +4. 8-32 GB size (don't oversize) +5. Check for fake/counterfeit cards +6. Try different SD card to isolate issue + +### PortaPack Not Booting + +**Checklist:** +1. HackRF powered? (LED on?) +2. PortaPack properly seated? +3. SD card inserted correctly? +4. Firmware compatible? +5. Battery charged? + +**Recovery:** +1. Remove SD card, try boot +2. If boots: SD card or firmware issue +3. If doesn't boot: Hardware issue +4. Try different power source +5. Check USB cable quality +6. May need firmware reflash + +--- + +## Advanced Topics + +### Creating Custom Frequency Lists + +Edit .TXT files in FREQMAN folder: + +``` +# Comment line +f=,m=,bw=,d= + +Example: +f=2450000000,m=AM,bw=1000000,d=Custom 2.45G +``` + +**Parameters:** +- `f=`: Frequency in Hz (e.g., 2450000000 = 2.45 GHz) +- `m=`: Modulation (AM, FM, WFM, NFM, USB, LSB) +- `bw=`: Bandwidth in Hz (e.g., 1000000 = 1 MHz) +- `d=`: Description (shown on screen) + +### Integration with Other Tools + +**Export data for analysis:** +- PortaPack captures → Import to GNU Radio +- RSSI logs → Excel/Python for plotting +- Waterfall screenshots → Image analysis + +**Coordinate with:** +- FlightRadar24 (manned aircraft) +- Local drone registration databases +- ADS-B receivers (manned aircraft IFF) +- RF mapping software + +### Building a Detection Station + +**Fixed Installation:** +1. Permanent power supply +2. Multiple antennas (antenna switch) +3. Elevated mounting (roof, tower) +4. Weather protection +5. Remote access (VNC/SSH if supported) +6. Automated logging +7. Alert notifications (email, SMS) + +**Requirements:** +- Dedicated HackRF/PortaPack +- Raspberry Pi or small computer (for automation) +- Network connectivity +- Power redundancy (UPS) + +--- + +## Best Practices + +### Detection Operations + +**Do:** +- Document all detections +- Use appropriate equipment +- Respect others' privacy +- Report illegal drone activity to authorities +- Share technical findings with community +- Test equipment regularly + +**Don't:** +- Interfere with detected drones (illegal!) +- Assume all signals are drones (verify) +- Ignore safety (terrain, weather) +- Use detection to facilitate illegal activity +- Share personal info about drone operators + +### Equipment Care + +- Store in dry environment +- Use protective case +- Keep antennas clean and undamaged +- Update firmware regularly +- Backup SD card contents +- Check connections before each use + +### Continuous Improvement + +- Keep logs of detections +- Review and analyze patterns +- Experiment with settings +- Learn from false positives +- Study drone protocols +- Join community forums +- Share knowledge + +--- + +## Conclusion + +Drone detection with HackRF/PortaPack is a powerful capability. This guide covers the essentials, but real expertise comes from practice. Start simple, experiment, document your findings, and continuously improve your technique. + +**Remember:** +- Detection is always legal ✅ +- Start with basic scanning +- Learn to interpret signals +- Document your observations +- Share knowledge responsibly +- Respect the law + +**Next Steps:** +- Practice with different scenarios +- Build detection profiles for your area +- Experiment with antennas +- Analyze captured signals +- Contribute to community knowledge + +For personal drone recall (YOUR equipment only), see PERSONAL_RECALL_SETUP.md. + +For legal details, see LEGAL.md. + +**Happy detecting! 📡🚁** diff --git a/HACKRF_PORTAPACK/LEGAL.md b/HACKRF_PORTAPACK/LEGAL.md new file mode 100644 index 0000000..c2f16cf --- /dev/null +++ b/HACKRF_PORTAPACK/LEGAL.md @@ -0,0 +1,814 @@ +# Legal Information and Compliance Guide + +## ⚠️ CRITICAL LEGAL NOTICE ⚠️ + +**This document provides educational information about legal and regulatory considerations. It is NOT legal advice. Consult a qualified attorney for specific legal questions.** + +**By using this package, you agree:** +- You are solely responsible for compliance with all applicable laws +- Authors/contributors accept NO liability for your use or misuse +- You will use this technology legally and ethically +- You understand the consequences of illegal use + +--- + +## Table of Contents + +1. [Quick Legal Summary](#quick-legal-summary) +2. [United States (FCC Regulations)](#united-states-fcc-regulations) +3. [European Union (ETSI Standards)](#european-union-etsi-standards) +4. [Other Countries](#other-countries) +5. [Legal Use Cases](#legal-use-cases) +6. [Illegal Uses](#illegal-uses) +7. [Penalties for Violations](#penalties-for-violations) +8. [Safety and Liability](#safety-and-liability) +9. [Responsible Use Guidelines](#responsible-use-guidelines) +10. [Reporting Illegal Activity](#reporting-illegal-activity) + +--- + +## Quick Legal Summary + +### ✅ ALWAYS LEGAL: + +**Receiving/Monitoring (Passive):** +- ✅ **Scanning any frequency** - You can listen to public airwaves +- ✅ **Recording signal characteristics** - Technical analysis is legal +- ✅ **RSSI monitoring** - Signal strength measurement +- ✅ **Logging activity** - Documenting detections +- ✅ **Signal analysis** - Understanding protocols +- ✅ **Educational purposes** - Learning about RF systems + +**This is protected by:** +- First Amendment (USA) - Freedom of information +- FCC Part 15 - Receiving not regulated +- Similar laws internationally +- **No license required** +- **No restrictions** +- **No legal risk** + +### ✅ CONDITIONALLY LEGAL: + +**Transmitting to YOUR OWN Equipment:** +- ✅ **YOUR personal drone** - That you own +- ✅ **With permission** - Explicit written authorization +- ✅ **On legal frequencies** - ISM bands, licensed if appropriate +- ✅ **Within power limits** - FCC/country limits +- ✅ **Proper use** - Not causing interference + +**Requirements:** +- Must comply with Part 15 (USA) or equivalent +- Stay within power limits +- Use authorized frequencies +- No harmful interference +- Accept interference from others + +### ❌ ALWAYS ILLEGAL: + +**Interfering with Others' Equipment:** +- ❌ **Jamming** - Blocking drone signals (FEDERAL CRIME) +- ❌ **Controlling others' drones** - Taking over equipment +- ❌ **Spoofing GPS** - Fake GPS signals (VERY serious offense) +- ❌ **Interfering with aircraft** - Any aircraft, drones included +- ❌ **Unauthorized transmission** - On restricted frequencies + +**Penalties:** +- Heavy fines: $10,000 - $100,000+ per violation +- Equipment confiscation +- Criminal charges +- Imprisonment (severe cases) +- Civil liability for damages + +--- + +## United States (FCC Regulations) + +### FCC Part 15 - Unlicensed Operation + +**Part 15 Overview:** +- Governs unlicensed RF devices +- Allows low-power transmission in ISM bands +- No license required IF compliant +- Must not cause harmful interference +- Must accept any interference received + +**ISM Bands (Industrial, Scientific, Medical):** + +| Band | Frequency | Power Limit | Notes | +|------|-----------|-------------|-------| +| 433 MHz | 433.05-434.79 MHz | 10 mW - 1 W | Regional variation | +| 902-928 MHz | 902-928 MHz | 1 W (4 W with SS) | USA/Americas | +| 2.4 GHz | 2400-2483.5 MHz | 1 W (4 W with SS) | Worldwide | +| 5.8 GHz | 5725-5850 MHz | 1 W typical | USA, check local | + +**Power Limits Explained:** +- **EIRP** = Effective Isotropic Radiated Power +- = Transmit Power + Antenna Gain - Cable Loss +- Must stay below limit +- Measure with RF power meter + +**Example Calculation:** +``` +TX Power: 20 dBm (100 mW) +Antenna Gain: +5 dBi +Cable Loss: -1 dB +EIRP = 20 + 5 - 1 = 24 dBm (250 mW) + +Check: Is 250 mW under limit for this band? If yes, compliant. +``` + +### FCC Part 97 - Amateur Radio + +**If you hold Amateur Radio License:** +- Additional frequencies available +- Higher power allowed +- Must identify your callsign +- Still cannot jam or interfere +- Still illegal to control others' drones + +**Advantages:** +- More frequency options +- Higher power for longer range +- Legal framework for experimentation + +**But:** +- Must follow Part 97 rules +- Callsign identification required +- Restrictions on encryption (in some cases) + +### Criminal Statutes + +**18 U.S.C. § 32 - Aircraft Sabotage:** +- Drones are considered aircraft +- Interfering with drone = aircraft interference +- **Federal felony** +- Up to 20 years imprisonment +- If death results: Life imprisonment or death penalty + +**18 U.S.C. § 1367 - Interference with Communications:** +- Jamming communication is federal crime +- Includes RF jamming +- Fine and/or imprisonment + +**Communications Act (47 U.S.C. § 333):** +- Willful interference with radio communications +- FCC can impose penalties +- Criminal prosecution possible + +### FCC Enforcement + +**FCC Can:** +- Issue warnings +- Levy fines ($10,000+ per violation) +- Confiscate equipment +- Refer for criminal prosecution +- Revoke licenses (if applicable) + +**Recent Cases:** +- Man fined $48,000 for cell phone jammer (2016) +- Multiple cases of GPS jamming: $30,000+ fines +- Drone jammer at sporting event: Equipment seized, prosecution + +### Reporting Violations + +**Report to FCC:** +- Online: https://consumercomplaints.fcc.gov/ +- Phone: 1-888-CALL-FCC (1-888-225-5322) +- Provide: Details, location, time, description + +--- + +## European Union (ETSI Standards) + +### EU Radio Equipment Directive (RED) + +**Directive 2014/53/EU:** +- Governs radio equipment in EU +- CE marking required +- Must meet essential requirements +- National authorities enforce + +**Key Bands:** + +| Band | Frequency | Power Limit | Notes | +|------|-----------|-------------|-------| +| 433 MHz | 433.05-434.79 MHz | 10 mW ERP | Short-range devices | +| 868 MHz | 863-870 MHz | 25 mW ERP | EU ISM band | +| 2.4 GHz | 2400-2483.5 MHz | 100 mW EIRP | Worldwide ISM | +| 5.8 GHz | 5725-5875 MHz | Varies by country | Not uniform in EU | + +**ERP vs EIRP:** +- ERP = Effective Radiated Power (relative to dipole) +- EIRP = Effective Isotropic Radiated Power +- EIRP = ERP + 2.15 dB +- Check which standard applies! + +### Country-Specific Variations + +**Note:** EU member states may have additional restrictions + +**Examples:** +- **Germany**: Strict enforcement, outdoor use restrictions on some bands +- **UK**: Similar to EU (post-Brexit, but largely aligned) +- **France**: Additional restrictions on certain frequencies +- **Spain**: Local variations in permitted power + +**Your Responsibility:** +- Check national regulations in your specific country +- Don't assume EU-wide rules apply uniformly +- Contact national authority if uncertain + +### ETSI Standards + +**ETSI EN 300 328:** 2.4 GHz wideband transmission +**ETSI EN 300 220:** Short-range devices (433/868 MHz) +**ETSI EN 301 893:** 5 GHz equipment + +**Compliance:** +- Professional equipment should be CE certified +- DIY use in gray area (check national rules) +- No harmful interference permitted + +### Criminal Laws + +**Varies by country, but generally:** +- Jamming is illegal (criminal offense) +- Interference with aircraft very serious +- Unauthorized transmission prosecuted +- Equipment can be confiscated + +**Example (UK):** +- Wireless Telegraphy Act 2006 +- Unauthorized transmission: Fine and/or 2 years imprisonment +- Interference: Up to 5 years imprisonment + +--- + +## Other Countries + +### Canada + +**Innovation, Science and Economic Development (ISED):** +- Similar to FCC rules +- ISM bands: 902-928 MHz, 2.4 GHz, 5.8 GHz +- Power limits generally similar to US +- License-free for low power +- Jamming illegal under Radiocommunication Act +- Heavy penalties for violations + +### Australia + +**Australian Communications and Media Authority (ACMA):** +- ISM bands: 915-928 MHz, 2.4 GHz, 5.8 GHz +- Power limits specified per band +- Compliance marking required +- Strong enforcement of drone regulations +- Jamming is serious criminal offense + +### Japan + +**Ministry of Internal Affairs and Communications (MIC):** +- 2.4 GHz: Maximum 10 mW/MHz EIRP +- 5.8 GHz: Restricted, not all channels available +- Strict compliance requirements +- Radio Law applies +- Severe penalties for violations + +### China + +**Ministry of Industry and Information Technology (MIIT):** +- Complex regulations +- Many frequencies restricted +- Foreign equipment may not be legal +- Strong enforcement +- Consult local authorities before use + +### India + +**Wireless Planning and Coordination (WPC):** +- Limited ISM band access +- License may be required for some uses +- 2.4 GHz generally accessible +- Check regulations carefully +- Penalties for violations severe + +### Other Countries: + +**General Advice:** +1. Contact national telecommunications authority +2. Ask specifically about: + - ISM band access + - Power limits + - License requirements + - Legal uses +3. Get written confirmation if possible +4. When traveling: Research before taking equipment + +--- + +## Legal Use Cases + +### 1. Passive Monitoring (ALWAYS LEGAL) + +**What You Can Do:** +- Scan any frequency +- Monitor drone activity +- Log signal detections +- Analyze protocols +- Educational study +- Security awareness +- Research + +**No restrictions:** +- No license needed +- No power limits (not transmitting!) +- No frequency restrictions +- Legal everywhere + +**Use Cases:** +- Home security: Monitor for drone activity +- Event security: Detect drones at events +- Research: Study drone communications +- Education: Learn about RF systems +- Property protection: Awareness of surveillance + +**Best Practice:** +- Document your monitoring +- Don't use information for illegal purposes +- Respect privacy laws (separate issue) +- Share findings responsibly + +### 2. Controlling YOUR OWN Drones + +**Legal When:** +- You own the drone (proof of ownership) +- Using legal frequencies +- Within power limits +- Not causing interference +- In legal airspace + +**Use Cases:** +- Emergency recall of your drone +- Testing your equipment +- Range testing your system +- Developing control systems +- Educational projects with your drones + +**Requirements:** +- Comply with Part 15 or equivalent +- Stay in ISM bands or licensed bands +- Measure transmit power +- Document compliance +- Have proof of ownership + +**Best Practice:** +- Test thoroughly in safe environment +- Document all testing +- Keep logs of operations +- Have traditional backup control +- Follow airspace regulations + +### 3. Educational and Research + +**Legal Activities:** +- Learning about RF systems +- Protocol analysis +- Academic research +- Technical experiments +- Sharing knowledge + +**Context:** +- University courses +- Independent study +- Open-source projects +- Technical publications +- Community education + +**Keys to Legality:** +- Clearly educational purpose +- Not used for illegal ends +- Responsible disclosure +- Safety considerations +- Proper supervision (if students) + +### 4. Security and Defense (Authorized) + +**Legal When Properly Authorized:** +- Government agencies +- Law enforcement +- Military +- Authorized security contractors +- With proper licenses/permissions + +**Note:** Requires special authorization, not for general public + +--- + +## Illegal Uses + +### 1. Jamming or Interference + +**Explicitly ILLEGAL:** +- Blocking drone signals intentionally +- Creating noise on drone frequencies +- GPS jamming (extremely serious) +- Disrupting remote control signals +- Preventing communication + +**Why It's Serious:** +- Endangers public safety +- Can cause crashes +- Interferes with emergency services +- Violates multiple laws +- Federal crimes (USA) / Criminal offenses (elsewhere) + +**Penalties:** +- USA: $10,000-$100,000+ fines, imprisonment +- EU: Fines, imprisonment, equipment seizure +- Worldwide: Serious criminal offense + +**Even If:** +- "For security" +- "To protect privacy" +- "Drone was trespassing" +- "Only for a moment" + +**STILL ILLEGAL. Do not do this.** + +### 2. Taking Control of Others' Drones + +**Absolutely ILLEGAL:** +- Sending control signals to drones you don't own +- "Hacking" drone control +- Forcing landing/RTH on others' drones +- Any interference with control + +**Legal Classification:** +- Aircraft interference (federal crime USA) +- Criminal damage (if crash results) +- Theft (if you take possession) +- Various communications crimes + +**Penalties:** +- Severe: Federal prison time possible +- Heavy fines +- Equipment confiscation +- Civil liability for damages +- Criminal record + +**No Exceptions:** +- Even if drone trespassing +- Even if "for security" +- Even if "preventing crime" +- Even if "protecting privacy" + +**Legal Remedies Exist:** +- Call police +- Document and report +- Use legal channels +- Don't take matters into own hands + +### 3. Unauthorized Frequencies + +**Illegal Transmission:** +- Outside ISM bands without license +- On licensed frequencies (aviation, emergency, etc.) +- Above power limits +- Without required certification + +**Examples:** +- Aircraft frequencies (aviation band) +- Emergency services (police, fire, EMS) +- Military frequencies +- Licensed commercial bands +- GPS frequencies (jamming/spoofing) + +**Penalties:** +- FCC fines: $10,000+ +- Equipment seizure +- License revocation (if licensed operator) +- Criminal prosecution possible + +### 4. Commercial Use Without License + +**May Require License:** +- Using RF for commercial services +- Selling jamming services (VERY illegal) +- Security services using RF +- Providing "counter-drone" commercially + +**Check Requirements:** +- May need commercial license +- Business regulations apply +- Higher standards of compliance +- Professional liability considerations + +--- + +## Penalties for Violations + +### United States + +**FCC Penalties:** +- Base fine: $10,000+ per violation +- Repeated violations: Up to $150,000 +- Equipment forfeiture +- License revocation (if applicable) + +**Criminal Penalties:** +- Jamming: Up to $100,000 fine, 5 years prison +- Aircraft interference (18 USC 32): Up to 20 years prison +- If death results: Life or death penalty + +**Civil Liability:** +- Damages from crashes +- Lost equipment +- Personal injury +- Property damage +- Can be millions of dollars + +**Recent Cases:** +- 2023: Drone jammer at stadium, $50,000 fine, equipment seized +- 2022: GPS jammer on highway, $32,000 fine, 6 months prison +- 2021: Interfered with police drone, 5 years prison + +### European Union + +**Administrative:** +- Fines: €5,000 - €500,000+ (varies by country) +- Equipment confiscation +- Bans on future equipment use + +**Criminal:** +- Imprisonment: Up to 5-10 years (serious cases) +- Criminal record +- Probation +- Community service + +**Civil:** +- Liability for damages +- Injunctions +- Compensation to victims + +### International + +**Generally Severe:** +- Fines in thousands to hundreds of thousands +- Equipment seizure universal +- Imprisonment possible in most countries +- Some countries very strict (years in prison) + +--- + +## Safety and Liability + +### Physical Safety + +**RF Exposure:** +- HackRF at high power can cause burns +- Stay away from antennas when transmitting +- FCC guidelines for exposure +- Particular care at 5+ GHz +- Don't point at people/animals + +**Drone Safety:** +- Drones can cause injury +- Propellers dangerous +- Crashes can hurt people +- Test without props when possible +- Clear area for testing + +**Battery Safety:** +- LiPo batteries fire risk +- Charge safely +- Store properly +- Dispose responsibly +- Fire extinguisher nearby + +### Legal Liability + +**You Can Be Held Liable For:** +- Injuries from crashes you cause +- Property damage +- Interference with critical services +- Lost business/income +- Pain and suffering + +**Protection:** +- Don't do illegal things! +- Liability insurance (if available) +- Document legal compliance +- Test safely +- Have emergency procedures + +### Privacy Considerations + +**Separate Legal Issue:** +- Monitoring RF signals generally legal +- But: Using info to violate privacy may be illegal +- Voyeurism laws +- Stalking laws +- Harassment + +**Best Practice:** +- Technical information only +- Don't track individuals +- Don't use for surveillance without authorization +- Respect privacy even if technically possible + +--- + +## Responsible Use Guidelines + +### Code of Conduct + +**As a Responsible RF User:** + +1. **Know the Law** + - Research regulations in your area + - Stay informed of changes + - When uncertain, ask authorities + - Err on side of caution + +2. **Respect Others** + - Don't interfere with others' equipment + - Coordinate on shared frequencies + - Minimize transmission time + - Accept interference gracefully + +3. **Prioritize Safety** + - Test in safe environments + - Have emergency procedures + - Don't endanger people/property + - Use proper protective equipment + +4. **Be Transparent** + - Clearly label your equipment + - Identify yourself if asked + - Share knowledge responsibly + - Report illegal activity + +5. **Continuous Learning** + - Stay current on technology + - Understand protocols deeply + - Learn from mistakes + - Mentor others responsibly + +### Community Standards + +**RF Community Expectations:** + +- **Educational Focus**: Share knowledge +- **Legal Compliance**: Follow the law +- **Safety First**: Don't endanger others +- **Responsible Disclosure**: Report vulnerabilities properly +- **Ethical Use**: Use technology for good + +**Don't:** +- Share methods for illegal interference +- Encourage illegal activities +- Provide tools primarily for illegal use +- Enable others to break laws + +### Reporting Vulnerabilities + +**If You Discover Security Issues:** + +1. **Responsible Disclosure:** + - Contact manufacturer privately + - Give time to fix (90 days typical) + - Don't publish until patched + - Coordinate disclosure + +2. **Don't:** + - Publicly share zero-days + - Weaponize vulnerabilities + - Sell exploits to criminals + - Use to attack systems + +3. **Do:** + - Document thoroughly + - Suggest fixes + - Work with vendors + - Eventually share for community learning + +--- + +## Reporting Illegal Activity + +### When to Report + +**Report If You Observe:** +- Drone in restricted airspace +- Suspicious drone activity +- Jamming/interference +- Illegal use of RF equipment +- Safety hazards + +**Don't:** +- Take matters into your own hands +- Use RF to interfere +- Create additional hazards +- Violate laws yourself while reporting + +### How to Report (USA) + +**FCC (Radio Interference):** +- Website: https://consumercomplaints.fcc.gov/ +- Phone: 1-888-CALL-FCC (1-888-225-5322) +- Provide: Date, time, location, frequency, description + +**FAA (Drone Violations):** +- Website: https://www.faa.gov/uas/report_uas +- Phone: 1-866-TELL-FAA (1-866-835-5322) +- App: "B4UFLY" for airspace issues + +**Local Law Enforcement:** +- 911 for emergencies +- Non-emergency line for non-urgent +- Provide details, stay safe + +**FBI (Serious Crimes):** +- For terrorism, serious crimes +- Contact local FBI office +- Or: tips.fbi.gov + +### What to Document + +**Useful Information:** +- Date and time +- Location (GPS coordinates) +- Duration of incident +- Frequency (if known) +- Type of drone (if visible) +- Activity observed +- Photos/video (if safe) +- Any injuries or damages + +**Don't:** +- Put yourself in danger to document +- Interfere with drone +- Confront operators +- Trespass to gather information + +--- + +## Disclaimer + +**THIS PACKAGE AND DOCUMENTATION:** + +- Provided "as is" without warranty +- For educational and lawful use only +- Not intended to enable illegal activity +- Not legal advice - consult attorney for legal questions +- Authors not liable for misuse or damages +- User solely responsible for compliance +- User assumes all risks + +**BY USING THIS PACKAGE:** + +- You agree to use legally and ethically +- You accept full responsibility for your actions +- You will comply with all applicable laws +- You understand penalties for violations +- You will not hold authors liable + +--- + +## Conclusion + +**Key Takeaways:** + +✅ **Detection = Always Legal** - Monitor away! +⚠️ **Transmission = Legal with restrictions** - Know and follow rules +❌ **Jamming/Interference = Always Illegal** - Never do this + +**When in Doubt:** +1. Don't transmit +2. Consult regulations +3. Ask authorities +4. Use legal channels +5. Prioritize safety + +**Remember:** +- Receiving is always legal +- Transmitting requires compliance +- Interfering is always illegal +- Penalties are severe +- Safety and legality first + +**Resources:** + +- **USA FCC**: https://www.fcc.gov/ +- **USA FAA**: https://www.faa.gov/uas +- **EU ETSI**: https://www.etsi.org/ +- **Your national telecommunications authority** + +**Use this technology responsibly, legally, and safely.** + +--- + +**Last Updated:** 2024 +**Disclaimer:** This is educational information, not legal advice. Laws change. Verify current regulations in your jurisdiction. Consult qualified attorney for specific legal questions. + +📡 **Stay Legal. Stay Safe. Stay Responsible.** 🚁 diff --git a/HACKRF_PORTAPACK/PERSONAL_RECALL_SETUP.md b/HACKRF_PORTAPACK/PERSONAL_RECALL_SETUP.md new file mode 100644 index 0000000..b783f60 --- /dev/null +++ b/HACKRF_PORTAPACK/PERSONAL_RECALL_SETUP.md @@ -0,0 +1,1075 @@ +# Personal Drone Recall Setup Guide + +## 🛑 CRITICAL WARNING - READ FIRST 🛑 + +### ⚠️ THIS GUIDE IS FOR YOUR OWN DRONES ONLY ⚠️ + +**ILLEGAL USE WARNING:** + +Using these techniques on drones you DO NOT own is: +- **FEDERAL CRIME** in most countries +- Violation of FCC regulations (USA) and equivalent internationally +- Aircraft interference (serious criminal offense) +- Can result in: Heavy fines ($10,000+), equipment seizure, criminal prosecution, imprisonment + +**LEGAL USE:** +- ✅ YOUR personally owned drone +- ✅ Drones you have explicit written permission to control +- ✅ Emergency recall of YOUR drone only +- ✅ Testing in controlled environment with YOUR equipment + +**BY PROCEEDING, YOU ACKNOWLEDGE:** +- You will ONLY use this on YOUR OWN equipment +- You understand the legal consequences of misuse +- You accept FULL responsibility for your actions +- Authors/contributors have NO liability for your use + +**If you plan to use this on drones you don't own: STOP NOW.** + +--- + +## Table of Contents + +1. [Prerequisites](#prerequisites) +2. [Understanding RF Control](#understanding-rf-control) +3. [Legal Compliance](#legal-compliance) +4. [Signal Capture Process](#signal-capture-process) +5. [Signal Analysis](#signal-analysis) +6. [Creating Recall Commands](#creating-recall-commands) +7. [Protocol-Specific Guides](#protocol-specific-guides) +8. [Testing Procedures](#testing-procedures) +9. [Troubleshooting](#troubleshooting) +10. [Safety Considerations](#safety-considerations) + +--- + +## Prerequisites + +### Required Knowledge + +Before attempting this, you should understand: +- Basic RF principles (frequency, modulation, power) +- Your drone's control protocol +- Basic command-line or file editing +- Safety procedures for drone operation +- Local radio transmission regulations + +**If you lack this knowledge:** Study first, then return to this guide. + +### Required Equipment + +**Essential:** +- HackRF One with PortaPack H4M +- Your drone (the one you want to recall) +- Your drone's transmitter/controller +- Appropriate antenna for drone's frequency +- Charged batteries for all equipment +- Notebook for documentation + +**Highly Recommended:** +- Second antenna for simultaneous RX/TX testing +- Spectrum analyzer or SDR for verification +- Oscilloscope or logic analyzer (advanced analysis) +- RF power meter (verify legal limits) +- Faraday cage or RF shielded box (for bench testing) + +**Safety Equipment:** +- Prop guards or remove props for testing +- Safety glasses +- Fire extinguisher (LiPo battery safety) +- First aid kit + +### Legal Verification + +**BEFORE proceeding, verify:** + +✓ You OWN this drone (have receipt/proof) +✓ Transmitting on this frequency is legal in your country +✓ You have necessary licenses if required +✓ You understand maximum legal power limits +✓ You will test in legal location (not restricted airspace) +✓ You have read all safety warnings + +**If ANY box unchecked: STOP. Do not proceed.** + +--- + +## Understanding RF Control + +### How Drone Control Works + +**Basic Control Signal:** +``` +Transmitter → RF Signal → Drone Receiver → Flight Controller → Motors +``` + +**Components of Control Signal:** +1. **Carrier Frequency**: The RF channel (e.g., 2.45 GHz) +2. **Modulation**: How data is encoded (AM, FM, GFSK, LoRa) +3. **Protocol**: Data format (PPM, SBUS, FrSky, etc.) +4. **Binding**: Pairing between TX and RX (unique ID) +5. **Commands**: Stick positions, switches, modes + +### Types of Control Signals + +**Analog (Older Systems):** +- PPM (Pulse Position Modulation) +- PWM (Pulse Width Modulation) +- Simple to capture and replay +- Less secure +- Longer range typically + +**Digital (Modern Systems):** +- FrSky (D8, D16, ACCESS) +- FlySky (AFHDS, AFHDS2A) +- Spektrum (DSM2, DSMX) +- ExpressLRS +- Crossfire +- More complex +- Often frequency hopping +- May have encryption + +### Why Replay Can Be Difficult + +**Challenges:** +- **Frequency Hopping**: Signal jumps between channels +- **Encryption**: Data is scrambled +- **Timing**: Precise timing required +- **Binding**: Unique pairing between TX/RX +- **Checksums**: Data validation +- **Rolling Codes**: Changes each transmission + +**Easier Protocols:** +- Fixed frequency +- No encryption +- Simple modulation +- Examples: Basic FM, some PPM systems + +**Harder Protocols:** +- Frequency hopping +- Encrypted +- Complex modulation +- Examples: FrSky ACCESS, DJI OcuSync, ELRS with binding phrase + +--- + +## Legal Compliance + +### Transmission Regulations + +**United States (FCC):** +- Part 15 devices: No license required (low power, ISM bands) +- Maximum EIRP limits vary by band: + - 433 MHz: 10 mW - 1W depending on application + - 915 MHz: 1W (36 dBm) EIRP typical + - 2.4 GHz: 1W (30 dBm) or 4W (36 dBm) with spread spectrum + - 5.8 GHz: 1W (30 dBm) typical +- Must not cause harmful interference +- Must accept any interference received + +**Europe (ETSI):** +- Similar ISM band rules +- 868 MHz common (instead of 915 MHz) +- Power limits generally lower than US +- CE certification requirements + +**Other Countries:** +- Check local regulations +- May require amateur radio license +- Some countries prohibit certain frequencies +- Power limits vary significantly + +**Your Responsibility:** +- Research YOUR country's rules +- Verify frequency is legal +- Measure your transmit power +- Stay within legal limits +- Document compliance + +### Verification Steps + +**Before first transmission:** + +1. **Frequency Check:** + - Is this frequency legal in my location? + - Is it an ISM or licensed band? + - Any restrictions on use? + +2. **Power Check:** + - Measure actual transmit power + - Calculate EIRP (power + antenna gain - cable loss) + - Verify under legal limit + - Document measurements + +3. **Location Check:** + - Not in restricted airspace? + - Not near airports, military bases? + - Not near sensitive RF installations? + - Safe for drone testing? + +4. **Interference Check:** + - Scan for other users on frequency + - Coordinate if others present + - Minimize transmission time + - Have way to immediately stop + +--- + +## Signal Capture Process + +### Step 1: Prepare Equipment + +**Setup:** +1. Charge all batteries (HackRF, drone, transmitter) +2. Connect appropriate antenna to HackRF +3. Insert SD card with adequate free space +4. Prepare notebook for documentation +5. Position equipment on stable surface + +**Environment:** +- Indoors or RF-quiet location +- Away from WiFi routers, computers +- Minimize RF interference +- Comfortable working area +- Good lighting for notes + +### Step 2: Identify Your Drone's Frequency + +**Check Transmitter:** +- Look for label (e.g., "2.4 GHz", "5.8 GHz") +- Check user manual +- Common bands: 2.4 GHz, 868 MHz (EU), 915 MHz (US), 433 MHz + +**If Unknown:** +1. Power on transmitter only (drone off) +2. Use HackRF in spectrum analyzer mode +3. Scan likely bands (2.4 GHz most common) +4. Watch for signals appearing when TX powered on +5. Note center frequency + +**Document:** +- Transmitter model: +- Frequency band: +- Exact frequency (if found): +- Signal bandwidth observed: + +### Step 3: Capture Control Signal + +**PortaPack Capture Procedure:** + +1. **Go to Capture App:** + - Main Menu → Capture → Baseband Capture + +2. **Configure Capture:** + - Frequency: [Your drone's frequency] + - Sample Rate: 2-4 MSPS (higher for wideband) + - Format: Complex16 (.c16) recommended + - Gain Settings: + - RF: 14 dB + - IF: 32 dB + - BB: 24 dB (adjust based on signal strength) + +3. **Prepare for Capture:** + - Position transmitter near HackRF (0.5-2 meters) + - Drone powered off or far away (don't want propeller spin!) + - SD card ready + +4. **Capture Sequence:** + ``` + a. Start recording on HackRF + b. Wait 2 seconds (get baseline) + c. Power on transmitter + d. Wait 2 seconds (capture binding/initialization) + e. Perform desired command (e.g., RTH switch) + f. Hold command for 3-5 seconds + g. Wait 2 seconds (capture after) + h. Stop recording + ``` + +5. **Save Capture:** + - Name descriptively: `my_drone_rth_capture.c16` + - Note filename in documentation + +**Document Capture:** +``` +Capture Details: +- Filename: my_drone_rth_capture.c16 +- Date/Time: 2024-12-26 15:30 +- Frequency: 2450 MHz +- Sample Rate: 2 MSPS +- Duration: 10 seconds +- Command Performed: RTH switch activated +- Transmitter Battery: 12.4V (full) +- Notes: Clean capture, strong signal +``` + +### Step 4: Capture Multiple Scenarios + +**Recommended Captures:** + +1. **Binding Sequence** (if accessible) + - Power sequence to bind TX to RX + - May be needed for some protocols + +2. **Idle/Baseline** + - Transmitter on, no stick input + - Reference signal + +3. **Return to Home (RTH)** + - Main emergency command + - Primary use case + +4. **Failsafe Trigger** + - If transmitter has failsafe button + - Alternative recall method + +5. **Specific Mode Changes** + - Switch to "Land" mode + - Switch to "Position Hold" mode + +6. **Different Commands** (optional) + - Throttle changes + - Directional commands + - For analysis and understanding + +--- + +## Signal Analysis + +### Step 5: Analyze Captured Signals + +**Transfer Files:** +1. Remove SD card from PortaPack +2. Insert in computer +3. Copy .c16 files to working directory +4. Keep originals safe (backup!) + +**Analysis Tools:** + +**Option 1: GNU Radio (Recommended)** +```bash +# Install GNU Radio if needed +sudo apt install gnuradio + +# Create flowgraph to: +# - Read .c16 file +# - Demodulate (AM/FM/GFSK as appropriate) +# - Display spectrum +# - Save demodulated audio/data +``` + +**Option 2: Inspectrum** +```bash +# Install +sudo apt install inspectrum + +# Open capture +inspectrum my_drone_rth_capture.c16 + +# Visual analysis: +# - See signal in time/frequency +# - Measure bandwidth +# - Identify modulation +# - Extract timing +``` + +**Option 3: URH (Universal Radio Hacker)** +```bash +# Install +pip3 install urh + +# Or use GUI +urh + +# Features: +# - Protocol analysis +# - Demodulation +# - Signal comparison +# - Automatic protocol discovery +``` + +### Identify Signal Characteristics + +**Questions to Answer:** + +1. **Modulation Type:** + - AM, FM, FSK, GFSK, LoRa, other? + - Use waterfall to identify + +2. **Bandwidth:** + - How wide is the signal? + - Example: FrSky = ~1 MHz, LoRa = 250-500 kHz + +3. **Frequency Hopping:** + - Does frequency change? + - How many channels? + - What's the pattern? + +4. **Data Rate:** + - Symbols per second + - Bit rate if digital + +5. **Timing:** + - Packet length + - Packet interval + - Burst characteristics + +6. **Protocol Structure:** + - Preamble + - Sync word + - Data payload + - Checksum/CRC + +**Document Findings:** +``` +Signal Analysis Results: +- Modulation: GFSK +- Bandwidth: 1 MHz +- Center Frequency: 2450.5 MHz +- Data Rate: ~250 kbps estimated +- Frequency Hopping: No (or not detected) +- Packet Structure: [preamble][sync][data][crc] +- Timing: 10ms packets, 50 Hz rate +``` + +### Compare Captures + +**Identify RTH Command:** +1. Compare "idle" vs "RTH active" captures +2. Look for differences in: + - Packet content (data bits changed) + - Frequency (if hopping differently) + - Timing (faster/slower packets) + - Specific bit patterns + +**Example:** +``` +Idle: AA AA 55 12 34 00 00 00 [CRC] +RTH: AA AA 55 12 34 01 00 00 [CRC] + ^^ + Bit changed for RTH +``` + +**This gives you the exact command to replay!** + +--- + +## Creating Recall Commands + +### Step 6: Prepare Replay File + +**Simple Replay (Fixed Frequency, No Hopping):** + +1. **Trim Capture:** + - Remove beginning/end noise + - Keep only the actual command transmission + - 1-2 seconds of clean signal + +2. **Save as Replay File:** + - Copy trimmed .c16 to: `/SDCARD/REPLAYS/` + - Name clearly: `my_drone_rth_tested.c16` + - Document in README_REPLAYS.TXT + +**Complex Replay (Frequency Hopping):** + +**Challenge:** Single frequency capture won't work + +**Options:** + +a. **Capture All Hop Frequencies:** + - Wideband capture covering all channels + - Very large file size + - Replay entire sequence + +b. **Identify Hop Pattern:** + - Analyze hopping algorithm + - Recreate hop sequence programmatically + - Advanced, requires coding + +c. **Use Single Frequency:** + - Some protocols allow single-channel mode + - Reduce TX to one frequency + - Drone may still respond (if protocol allows) + +d. **Modify Drone to Fixed Frequency:** + - Reflash drone firmware (if possible) + - Use fixed frequency mode + - Safest for personal recall + +### Step 7: Configure Replay in PortaPack + +**Create FREQMAN Entry:** + +Edit appropriate protocol template in `/SDCARD/FREQMAN/`: + +Example: `PERSONAL_FRSKY_D16.TXT` +``` +# Updated with MY drone's actual frequency +f=2450500000,m=AM,bw=1000000,d=My Drone RTH Frequency + +# Replace template frequency with YOUR captured frequency +``` + +**Or Create Custom File:** +``` +# Create: PERSONAL_MY_DRONE.TXT +f=2450500000,m=AM,bw=1000000,d=My Quad RTH +``` + +**Configure Settings:** + +Edit: `/SDCARD/SETTINGS/personal_recall_template.txt` + +``` +protocol=my_drone +center_frequency=2450500000 +modulation=GFSK +bandwidth=1000000 +tx_gain=0 # Start LOW! +tx_power=0 # Start LOW! +``` + +--- + +## Protocol-Specific Guides + +### FrSky D16 Setup + +**Characteristics:** +- Frequency: 2400-2480 MHz +- Hopping: 47 channels +- Modulation: GFSK +- Binding: Required + +**Capture Procedure:** +1. Bind transmitter to receiver (if not already) +2. Power on transmitter +3. **Capture binding sequence** (power cycle RX while recording) +4. Capture RTH command after binding +5. Note all 47 hop frequencies if possible + +**Replay Strategy:** +- Replaying hopping sequence is complex +- Consider: Fixed frequency mode (if firmware allows) +- Or: Wideband capture/replay (large files) + +**Testing:** +- Bench test with RX only (no drone powered) +- Verify RX LED responds +- Then test with drone (props off!) + +### FlySky AFHDS/AFHDS2A Setup + +**Characteristics:** +- Frequency: 2400-2480 MHz +- Hopping: 16 channels (AFHDS) or improved AFHDS2A +- Modulation: GFSK +- Binding: Required + +**Capture Procedure:** +1. Bind TX to RX +2. Capture binding and normal operation +3. Identify hop pattern (simpler than FrSky) +4. Capture failsafe command + +**Replay Strategy:** +- AFHDS2A has better error correction +- May respond to single-channel transmission +- Test with RX module disconnected from FC first + +**Testing:** +- Use receiver bind LED as indicator +- Successful replay = LED changes state + +### ExpressLRS (ELRS) Setup + +**Characteristics:** +- Frequency: 900 MHz or 2.4 GHz variants +- Modulation: LoRa (chirp spread spectrum) +- Binding: Unique binding phrase +- Hopping: Yes, based on binding phrase + +**Challenges:** +- LoRa is complex to replay +- Encrypted with binding phrase +- Frequency hopping based on phrase +- **Most difficult protocol to replay** + +**Capture Procedure:** +1. Know your binding phrase +2. Capture wideband (LoRa bandwidth) +3. Identify chirp pattern in waterfall +4. Very challenging to replay accurately + +**Recommendations:** +- ELRS is designed to resist replay attacks +- Consider using traditional transmitter as backup +- Replay may not be practical for emergency recall +- Use OTX lua script failsafe settings instead + +### TBS Crossfire Setup + +**Characteristics:** +- Frequency: 868 MHz (EU) or 915 MHz (US) +- Modulation: LoRa +- Binding: Required +- Long range, robust + +**Challenges:** +- LoRa modulation complex +- Frequency hopping +- Error correction +- **Difficult to replay** + +**Capture Procedure:** +1. Know your region (868 vs 915 MHz) +2. Capture wide bandwidth (LoRa needs it) +3. Identify chirp characteristics +4. Note any frequency changes + +**Recommendations:** +- Crossfire has excellent failsafe features +- Use transmitter's built-in failsafe instead +- Replay not recommended for emergency use +- Better: Configure failsafe in transmitter + +### DJI Drones (Consumer) + +**Characteristics:** +- Frequency: 2.4 GHz and/or 5.8 GHz +- Protocol: Proprietary (Lightbridge, OcuSync) +- Encryption: Yes +- Frequency Agile: Changes based on interference + +**Reality Check:** +- **DJI protocols are encrypted and proprietary** +- Replay is effectively impossible without keys +- Frequency hopping/agility defeats simple replay +- **Not a viable option for personal recall** + +**Alternatives:** +- Use DJI app failsafe settings (RTH on signal loss) +- Use physical transmitter controls +- DJI has built-in emergency features +- Don't rely on RF replay for DJI + +### Generic PPM/PWM (Simple RC) + +**Characteristics:** +- Older, simpler systems +- Fixed frequency typically +- FM or AM modulation +- No encryption + +**Advantages:** +- **Easiest to replay!** +- Fixed frequency +- Simple modulation +- No hopping or encryption + +**Capture Procedure:** +1. Identify frequency (often 72 MHz, 27 MHz old systems, or 2.4 GHz newer) +2. Capture control signal +3. Identify stick position encoding +4. Very straightforward + +**Replay Strategy:** +- Direct replay usually works +- May need to time pulses correctly +- Test thoroughly before aerial use + +--- + +## Testing Procedures + +### Phase 1: Bench Testing (CRITICAL) + +**Setup:** +- Drone on bench, **PROPELLERS REMOVED** +- Or receiver only (disconnected from flight controller) +- All parties indoors or in RF shielded space +- Emergency power cutoff available + +**Test 1: Receiver Response** +``` +1. Power on drone (no props!) or receiver +2. Load replay file in PortaPack +3. Set TX gain to MINIMUM (0-5 dB) +4. Position HackRF 1 meter from drone +5. Transmit replay signal (short burst, <1 second) +6. Observe receiver LED +7. Check flight controller status (if connected) +``` + +**Success Indicators:** +- Receiver LED changes state +- Flight controller detects signal +- No actual motor commands (props off!) +- Repeatable behavior + +**If No Response:** +- Increase TX gain incrementally (+3 dB) +- Verify frequency accuracy +- Check signal timing +- Review capture quality +- May need to recapture + +**Test 2: Command Verification** +``` +1. Connect flight controller to computer +2. Open configurator (Betaflight, etc.) +3. Watch receiver tab for commands +4. Replay signal +5. Verify correct command received +``` + +**Success Indicators:** +- Correct channel changes +- RTH function triggered +- Match expected behavior + +### Phase 2: Controlled Environment Testing + +**Setup:** +- Open field, no people nearby +- No other drones in air +- Good weather conditions +- Traditional transmitter as backup +- Spotter to assist + +**Test 3: Tethered Test** +``` +1. Attach drone to tether (rope/fishing line) +2. Limit altitude to 1-2 meters +3. Propellers: ON (secure tether first!) +4. Arm and hover (traditional transmitter) +5. Attempt replay RTH command +6. Observe response +7. Use traditional TX to land if issues +``` + +**Success Indicators:** +- Drone responds to replay command +- RTH mode activated +- Drone behavior matches traditional TX command +- No unexpected behavior + +**Safety:** +- Spotter watching drone +- Tether prevents flyaway +- Traditional TX ready to take over +- Kill power if anything unexpected + +**Test 4: Short-Range Free Flight** +``` +1. Untethered, clear area +2. Hover at 2-3 meters altitude +3. Attempt replay RTH +4. Monitor drone response +5. Be ready with traditional TX backup +``` + +**Success Indicators:** +- Drone enters RTH mode +- Returns to home position +- Lands safely +- Repeatable behavior + +### Phase 3: Operational Testing + +**Only after successful Phase 1 & 2:** + +**Test 5: Realistic Scenario** +``` +1. Fly normally with traditional TX +2. Move to distance where replay needed (simulated emergency) +3. Attempt replay RTH +4. Verify effective recall +5. Document range, conditions, results +``` + +**Document Everything:** +``` +Test Log: +- Date/Time: +- Test Phase: +- Conditions: (weather, RF environment) +- Distance from drone: +- TX power used: +- Result: (success/fail) +- Drone response: +- Time to RTH: +- Notes: +``` + +--- + +## Troubleshooting + +### Replay Doesn't Work + +**Check List:** + +1. **Frequency Correct?** + - Verify captured frequency matches replay + - Use spectrum analyzer to check TX output + - Tolerance: Within 10 kHz usually OK + +2. **Modulation Correct?** + - AM vs FM vs GFSK makes big difference + - Check capture analysis + - Try different modulation settings + +3. **Timing Issues?** + - Some protocols very timing-sensitive + - May need exact packet timing + - Compare capture timing to replay + +4. **Frequency Hopping?** + - If protocol hops, single frequency won't work + - Need full hop sequence + - Or modify to fixed frequency + +5. **Signal Quality?** + - Noisy capture won't replay well + - Recapture in cleaner RF environment + - Better antenna positioning + +6. **TX Power Too Low?** + - Incrementally increase + - Measure actual output power + - Stay within legal limits + +7. **Binding Issue?** + - RX not bound to your TX signal + - May need to capture and replay binding + - Or physically bind RX to your TX first + +### Unexpected Drone Behavior + +**If drone does something unexpected:** + +1. **IMMEDIATELY:** Use traditional TX to take control +2. **Land drone safely** +3. **Power off replay TX** +4. **Analyze what happened** +5. **DO NOT retry until issue understood** + +**Possible Causes:** +- Wrong command replayed +- Interference with other signals +- Partial command (corrupted) +- Flight controller misinterpretation +- Multiple sources of RF + +**Resolution:** +- Review captures more carefully +- Verify exact command bytes +- Test more thoroughly in Phase 1 +- May need different approach + +### Legal/Interference Issues + +**If you experience:** +- Interference to others +- Complaints from nearby users +- Equipment malfunctioning +- Unexpected regulatory contact + +**Actions:** +1. **STOP transmitting immediately** +2. Verify frequency is legal +3. Measure transmit power +4. Ensure within legal limits +5. Document compliance +6. Consult with legal expert if needed + +--- + +## Safety Considerations + +### RF Safety + +**Exposure Limits:** +- FCC guidelines for RF exposure +- Keep HackRF away from body when transmitting +- Don't transmit near people +- Especially careful with higher power levels + +**Equipment Safety:** +- Don't exceed HackRF's ratings +- Monitor for overheating +- Use appropriate antennas +- Check SWR (Standing Wave Ratio) + +### Drone Safety + +**Pre-Flight:** +- Check drone condition +- Verify GPS lock +- Set failsafe properly +- Know RTH altitude +- Clear return path + +**During Testing:** +- Spotter present +- Emergency procedures ready +- Traditional TX as backup +- Clear area of people +- Good weather conditions + +**Emergency Procedures:** + +**If Replay Causes Flyaway:** +1. Traditional TX: Try to regain control +2. If that fails: Let failsafe engage (signal loss) +3. Note last direction/altitude +4. Do NOT attempt further replay +5. Report as necessary + +**If Drone Becomes Unresponsive:** +1. Stop all transmissions +2. Let failsafe engage (usually lands or RTH) +3. Do not attempt takeoff again until issue resolved +4. Analyze logs + +### Legal Safety + +**Protecting Yourself:** +- Document that drone is yours (receipt, serial number) +- Document all testing procedures +- Measure and record transmit power +- Verify legal compliance in writing +- Consider consulting lawyer for high-risk scenarios + +**If Questioned:** +- Be cooperative +- Provide documentation +- Explain educational purpose +- Demonstrate ownership +- Don't admit to illegal activity + +--- + +## Advanced Topics + +### Creating Automated Recall + +**Goal:** Button press = immediate RTH + +**Approach:** +1. Store validated replay file on SD card +2. Create quick-access shortcut in PortaPack +3. Map to physical button if possible +4. Pre-configure frequency and power + +**Implementation:** +- Save replay file: `/SDCARD/REPLAYS/EMERGENCY_RTH.c16` +- Create FREQMAN entry for quick load +- Test extensively before relying on it + +### Multi-Drone Management + +**If you have multiple drones:** + +**Challenge:** Each drone has unique binding + +**Solution:** +1. Capture signals for EACH drone separately +2. Label clearly: `drone1_rth.c16`, `drone2_rth.c16` +3. Create FREQMAN entry for each +4. Select correct one before use + +**Safety:** Easy to confuse drones, double-check! + +### Range Extension + +**To maximize recall range:** + +**Antenna Improvement:** +- Directional antenna (yagi, patch) +- Higher gain = longer range +- But: Must point at drone + +**Power Increase:** +- Increase TX gain carefully +- Verify legal limits +- Measure actual EIRP +- Don't exceed regulations + +**Environmental:** +- Higher ground position +- Line of sight +- Away from interference +- Good weather (rain attenuates) + +**Realistic Ranges:** +- With stock setup: 100-500m +- With directional antenna: 500m-2km +- With high gain + power: 2-5km +- Limited by legal power and antenna + +--- + +## Conclusion + +Personal drone recall using HackRF/PortaPack is **technically possible** but comes with significant challenges: + +**Difficulty by Protocol:** +- ✅ **Easy:** Simple FM/AM systems, PPM, no hopping +- ⚠️ **Medium:** FrSky, FlySky (fixed frequency mode) +- ❌ **Hard:** ELRS, Crossfire, DJI (encryption/hopping) + +**Recommendations:** + +1. **Primary Method:** Use traditional transmitter + - Most reliable + - Always legal (your drone) + - Instant response + +2. **Secondary Method:** Configure failsafe + - Automatic on signal loss + - No special equipment needed + - Very reliable + +3. **Tertiary Method:** HackRF replay + - Emergency backup only + - After extensive testing + - When traditional TX fails + - Simple protocols only + +**Final Warnings:** + +⚠️ **ONLY use on YOUR drones** +⚠️ **Test extensively before relying on it** +⚠️ **Traditional TX is more reliable** +⚠️ **Legal compliance is YOUR responsibility** +⚠️ **Safety first, always** + +**If in doubt:** +- Use traditional transmitter +- Use built-in failsafe +- Don't rely on untested replay + +--- + +## Resources + +**Learn More:** +- Your drone's user manual +- Protocol documentation (if available) +- SDR communities (r/RTLSDR, r/hackrf) +- RC forums for your specific drone + +**Tools:** +- GNU Radio: https://www.gnuradio.org/ +- Universal Radio Hacker: https://github.com/jopohl/urh +- Inspectrum: https://github.com/miek/inspectrum + +**Legal Resources:** +- FCC Part 15 Rules: https://www.fcc.gov/general/radio-frequency-safety-0 +- Your country's radio regulations authority + +--- + +**Remember: Legal, safe, and responsible use only. Detection is always legal - transmission only to YOUR equipment. When in doubt, use your regular transmitter.** 📡🚁 diff --git a/HACKRF_PORTAPACK/QUICK_START.md b/HACKRF_PORTAPACK/QUICK_START.md new file mode 100644 index 0000000..333b5bc --- /dev/null +++ b/HACKRF_PORTAPACK/QUICK_START.md @@ -0,0 +1,473 @@ +# Quick Start Guide - HackRF PortaPack Drone Detection System + +## ⚠️ 5-Second Legal Notice +**Detection = Legal ✅ | Jamming Others = Illegal ❌** +Use only for monitoring or YOUR OWN equipment. + +--- + +## What You'll Need (5 minutes to gather) + +✓ HackRF One with PortaPack H4M +✓ MicroSD card (8GB+, FAT32 formatted) +✓ Appropriate antenna(s) for target frequencies +✓ USB cable or battery pack +✓ Computer (for initial SD card setup) + +--- + +## Setup Process + +### Step 1: Format SD Card (2 minutes) + +**Windows:** +``` +1. Insert SD card +2. Right-click drive → Format +3. Choose: FAT32, Default allocation size +4. Click Start +``` + +**Mac:** +``` +1. Insert SD card +2. Open Disk Utility +3. Select card → Erase +4. Format: MS-DOS (FAT) +5. Click Erase +``` + +**Linux:** +```bash +# Find device (usually /dev/sdX) +lsblk + +# Format (replace sdX with your device) +sudo mkfs.vfat -F 32 /dev/sdX1 +``` + +### Step 2: Copy Files to SD Card (1 minute) + +``` +1. Download/locate the HACKRF_PORTAPACK package +2. Copy entire SDCARD directory contents to SD card root +3. Verify structure: + + SD_CARD/ + ├── FREQMAN/ + ├── SETTINGS/ + ├── CAPTURES/ + └── REPLAYS/ + +4. Safely eject SD card +``` + +### Step 3: Install in PortaPack (1 minute) + +``` +1. Power OFF HackRF/PortaPack completely +2. Insert SD card into PortaPack slot (push until click) +3. Connect antenna for target frequency +4. Power ON device +5. Wait for boot (10-15 seconds) +``` + +### Step 4: Verify Installation (<1 minute) + +``` +1. From main menu, navigate to: Apps → File Manager +2. You should see: FREQMAN, SETTINGS, CAPTURES, REPLAYS folders +3. If not visible: reinsert SD card or reformat +``` + +--- + +## First Use: Drone Detection (5 minutes) + +### Basic Detection Mode (100% Legal) + +**Goal:** Detect if drones are active nearby + +1. **Select Frequency Scanner:** + - Main Menu → **"Receiver"** → **"Freqman"** + - Or: Main Menu → **"Scanner"** (depends on firmware version) + +2. **Choose Frequency File:** + - First time: Select **`DRONE_SCAN_ALL.TXT`** (covers all bands) + - For specific use: + - `DRONE_SCAN_2G4.TXT` - Consumer drones (DJI, etc.) + - `DRONE_SCAN_5G8.TXT` - FPV racing drones + - `DRONE_SCAN_433.TXT` - RC toys, basic drones + +3. **Configure Scanner:** + - RSSI Threshold: **-70 dBm** (good starting point) + - Squelch: **Enabled** + - Audio Alert: **On** (you'll hear beeps when signals found) + +4. **Set Gains:** + - RF Gain: **14 dB** (increase if no signals detected) + - IF Gain: **40 dB** + - Baseband Gain: **32 dB** + +5. **Start Scanning:** + - Press **START** or **SELECT** + - Watch display for signal activity + - Listen for audio alerts + +**What You'll See:** +- Frequency currently being scanned +- RSSI value (signal strength in dBm) +- Bar graph showing signal level +- Screen flash when signal detected +- Audio beep when signal crosses threshold + +**What the Numbers Mean:** +- **-90 to -80 dBm**: Very weak signal, far away +- **-80 to -60 dBm**: Moderate signal, medium distance +- **-60 to -40 dBm**: Strong signal, nearby +- **-40 dBm and above**: Very strong signal, very close + +--- + +## Testing Your Setup (2 minutes) + +### Test with Known Signal + +**Easy Test - Use Your Phone:** + +1. Load **`DRONE_SCAN_2G4.TXT`** (WiFi/Bluetooth) +2. Start scanning +3. Enable WiFi hotspot on your phone +4. You should immediately detect signals at 2.4 GHz +5. HackRF should beep and show activity + +**This confirms:** +✓ SD card is reading correctly +✓ Antenna is connected +✓ Scanner is working +✓ Alerts are functional + +### If No Signals Detected: + +**Troubleshooting (in order):** +1. Check antenna is screwed on tight +2. Lower RSSI threshold to **-90 dBm** +3. Increase **RF Gain** to **30 dB** +4. Verify SD card file structure +5. Try different frequency file +6. Ensure antenna matches frequency (2.4 GHz antenna for 2.4 GHz signals) + +--- + +## Common Button Mappings + +**PortaPack H4M Controls:** +- **Encoder Wheel**: Navigate menus, adjust values +- **Encoder Press**: Select/confirm +- **Left Button**: Back/cancel +- **Right Button**: Options/menu +- **Up/Down**: Scroll (on some screens) + +**In Scanner Mode:** +- **Encoder Wheel**: Adjust RSSI threshold +- **Left Button**: Pause/resume scanning +- **Right Button**: Access settings +- **Press Encoder**: Manual frequency entry + +--- + +## Quick Command Reference + +### Switch Between Modes: + +**Detection → Analysis:** +1. Stop scanner +2. Return to main menu +3. Select **"Spectrum Analyzer"** +4. Enter frequency of interest + +**Detection → Capture:** +1. Stop scanner +2. Go to **"Capture"** app +3. Set frequency +4. Press **Record** to capture + +### Save a Detection Event: + +1. When signal detected, note frequency +2. Go to main menu → **"File Manager"** +3. Navigate to **CAPTURES** +4. Note time and frequency in a log (manual for now) + +--- + +## Safety Checklist + +Before ANY transmission (personal recall ONLY): + +- [ ] Read **LEGAL.md** completely +- [ ] Read **PERSONAL_RECALL_SETUP.md** completely +- [ ] This is MY drone that I personally own +- [ ] I have captured MY drone's signals +- [ ] I am in a safe, open area +- [ ] No other drones are nearby +- [ ] I have verified legal compliance +- [ ] I have a backup control method ready + +**If ANY checkbox is unchecked, do NOT transmit.** + +--- + +## Monitoring Scenarios + +### Scenario 1: Home/Property Security +**Goal:** Detect drones near your property + +``` +1. Load: DRONE_SCAN_ALL.TXT +2. Set threshold: -70 dBm +3. Enable audio alerts +4. Position HackRF with clear view +5. Monitor periodically or continuously +6. Log any detections with timestamp +``` + +**Battery Life:** ~2-3 hours on 10,000 mAh power bank + +### Scenario 2: Event Monitoring +**Goal:** Know if drones active at outdoor event + +``` +1. Load: DRONE_SCAN_2G4.TXT (most consumer drones) +2. Add: DRONE_SCAN_5G8.TXT scan after +3. Set threshold: -60 dBm (nearby drones only) +4. Enable visual alerts (discrete) +5. Carry HackRF, monitor periodically +``` + +**Battery Life:** ~1-2 hours active scanning + +### Scenario 3: FPV Racing Coordination +**Goal:** Find free 5.8 GHz channel for FPV + +``` +1. Load: DRONE_SCAN_5G8.TXT +2. Set threshold: -75 dBm +3. Scan all channels +4. Identify occupied channels +5. Choose free channel for your use +6. Coordinate with other pilots +``` + +**Time:** 2-5 minutes per scan cycle + +### Scenario 4: RF Learning +**Goal:** Understand drone RF protocols + +``` +1. Use YOUR drone/transmitter +2. Load appropriate frequency file +3. Power on transmitter +4. Observe signals in scanner +5. Note: frequency, strength, pattern +6. Switch to spectrum analyzer for detail +7. Capture signals for later analysis +``` + +**Educational Value:** High - learn real RF behavior + +--- + +## Power Management + +### Battery Life Estimates: + +| Mode | Power Draw | 10,000 mAh Runtime | +|------|------------|-------------------| +| Scanning (screen on) | ~1.5W | 2-3 hours | +| Scanning (screen dim) | ~1.2W | 3-4 hours | +| Idle/menu | ~0.8W | 5-6 hours | +| Transmitting | ~2-3W | 1-2 hours | + +### Extending Battery Life: + +1. **Dim screen**: Settings → Display → Brightness → 25% +2. **Enable battery saver**: Settings → Power → Battery Saver +3. **Reduce scan speed**: Slower scan = less power +4. **Narrower frequency range**: Scan fewer channels +5. **Power off between uses**: Don't leave in idle +6. **Use efficient antennas**: Better signal = lower gain needed + +--- + +## Emergency Procedures + +### HackRF Overheating: +``` +1. Power off immediately +2. Remove from case if enclosed +3. Allow to cool (5-10 minutes) +4. Reduce gain settings before restart +5. Ensure adequate ventilation +``` + +### Unexpected Behavior: +``` +1. Press left button repeatedly (back to menu) +2. Power cycle device +3. Remove and reinsert SD card +4. Verify file integrity +5. Re-copy files if needed +``` + +### Lost Connection: +``` +1. Check USB cable firmly connected +2. Try different USB port +3. Check battery charge level +4. Verify HackRF LED is on +5. Power cycle PortaPack +``` + +--- + +## Next Steps + +### After You're Comfortable with Detection: + +1. **Read Full Documentation:** + - [DETECTION_GUIDE.md](DETECTION_GUIDE.md) - Deep dive into detection + - [LEGAL.md](LEGAL.md) - Complete legal information + +2. **Experiment with Settings:** + - Try different frequency files + - Adjust RSSI thresholds + - Compare gain settings + - Use spectrum analyzer mode + +3. **Learn Signal Analysis:** + - Capture signals from known sources + - Analyze modulation types + - Study protocol characteristics + - Build understanding of RF behavior + +4. **Only If Needed - Personal Recall:** + - Read [PERSONAL_RECALL_SETUP.md](PERSONAL_RECALL_SETUP.md) completely + - Only for YOUR drones + - Follow all safety procedures + - Test thoroughly in safe environment + +--- + +## Quick Troubleshooting + +| Problem | Quick Fix | +|---------|----------| +| No signals detected | Lower threshold to -90 dBm, increase RF gain | +| Too many false alerts | Raise threshold to -60 dBm, reduce gain | +| Scanner won't start | Check SD card inserted, verify file format | +| Screen frozen | Power cycle device | +| Battery drains fast | Dim screen, reduce scan range | +| Can't see SD files | Reformat as FAT32, copy files again | +| Weak signals | Check antenna, increase gain, get closer | +| No audio alerts | Check settings → audio → enable | + +--- + +## Common Mistakes to Avoid + +❌ **Wrong antenna for frequency** +✅ Use 2.4 GHz antenna for 2.4 GHz signals, etc. + +❌ **Threshold too high** +✅ Start with -70 dBm, adjust based on results + +❌ **SD card wrong format** +✅ Must be FAT32, not exFAT or NTFS + +❌ **Files in wrong location** +✅ FREQMAN files must be in /FREQMAN/ folder + +❌ **Expecting instant results** +✅ May take time to detect activity, be patient + +❌ **Ignoring battery level** +✅ HackRF drains batteries fast, monitor level + +❌ **Using on others' drones** +✅ ONLY for detection (legal) or YOUR equipment + +--- + +## Getting Help + +**Built-in Help:** +- Many apps have "?" or "Help" button +- Press and hold encoder for context help (some screens) + +**Documentation:** +- Full guides in HACKRF_PORTAPACK directory +- README.md for overview +- Specific guides for each function + +**Community Resources:** +- HackRF mailing list +- PortaPack GitHub discussions +- Reddit: r/hackrf, r/RTLSDR +- Discord: Various SDR communities + +**Report Issues:** +- GitHub: ultimatel-ily repository +- Include: firmware version, what you tried, error messages + +--- + +## Success Checklist + +After this quick start, you should be able to: + +- [ ] Format and prepare SD card +- [ ] Install files in correct structure +- [ ] Boot PortaPack with SD card +- [ ] Navigate to Freqman/Scanner mode +- [ ] Load a frequency file +- [ ] Start scanning +- [ ] Detect signals (tested with phone WiFi) +- [ ] Understand RSSI readings +- [ ] Adjust gain settings +- [ ] Use spectrum analyzer +- [ ] Navigate back to main menu + +**If all checked: Congratulations! You're ready to explore more features.** + +**If some unchecked: Review relevant sections above or see full documentation.** + +--- + +## Time Investment Summary + +- **Setup**: 5-10 minutes (one-time) +- **Learning basics**: 15-30 minutes +- **Comfortable detection**: 1-2 hours practice +- **Advanced features**: Ongoing learning +- **Personal recall**: Several hours + testing (if needed) + +--- + +## Final Quick Tips + +💡 **Start simple**: Use DRONE_SCAN_ALL.TXT first +💡 **Test with known signals**: Your phone's WiFi hotspot +💡 **Be patient**: Signal detection takes time +💡 **Stay legal**: Detection is always OK, transmission only for YOUR equipment +💡 **Read docs**: Full guides have much more detail +💡 **Practice**: The more you use it, the better you'll understand +💡 **Stay safe**: RF can be powerful, use responsibly + +--- + +**You're ready to start! Power on, load a frequency file, and begin monitoring.** + +**For detailed information, proceed to [DETECTION_GUIDE.md](DETECTION_GUIDE.md)** + +**Remember: Detection = Always Legal ✅ | Have Fun! 📡🚁** diff --git a/HACKRF_PORTAPACK/README.md b/HACKRF_PORTAPACK/README.md new file mode 100644 index 0000000..6e205af --- /dev/null +++ b/HACKRF_PORTAPACK/README.md @@ -0,0 +1,500 @@ +# HackRF One + PortaPack H4M - Drone Detection & Personal Recall System + +## ⚠️ LEGAL DISCLAIMER - READ FIRST ⚠️ + +**CRITICAL LEGAL INFORMATION:** + +### ✅ LEGAL USES: +- **Receiving/monitoring any frequency (passive detection)** - Always legal +- **Transmitting to YOUR OWN drones** - Legal when compliant with regulations +- **Educational and research purposes** - Within legal boundaries +- **Testing YOUR OWN equipment** - In appropriate environments + +### ❌ ILLEGAL USES: +- **Jamming or interfering with drones you don't own** - FEDERAL CRIME +- **Transmitting on unauthorized frequencies** - FCC violation +- **Controlling aircraft/drones you don't own** - Criminal offense +- **Creating interference to licensed services** - Heavy fines + prosecution + +**Penalties for illegal use:** Fines up to $10,000+ per violation, equipment seizure, criminal charges, possible imprisonment. + +**BY USING THIS PACKAGE, YOU AGREE:** You are solely responsible for legal compliance. The authors accept NO liability for misuse. + +--- + +## Overview + +This comprehensive SD card package provides: + +1. **Drone Detection System (Receive-Only - Always Legal)** + - Multi-band frequency scanning (433 MHz to 5.8 GHz) + - Real-time RSSI monitoring and alerts + - Signal pattern identification + - Activity logging with timestamps + +2. **Personal Drone Recall Framework (YOUR Equipment ONLY)** + - Template configurations for common protocols (FrSky, FlySky, ELRS, Crossfire) + - Signal capture and analysis tools + - Replay system for YOUR drone's control signals + - Safety-focused testing procedures + +3. **Educational Resources** + - Comprehensive guides and documentation + - RF protocol analysis tools + - Legal compliance information + - Safety procedures + +## Hardware Requirements + +### Required: +- **HackRF One** - Software Defined Radio (1 MHz - 6 GHz) +- **PortaPack H4M** - Standalone interface with display and controls +- **MicroSD Card** - 8GB+ recommended, Class 10 or better +- **Antenna Kit** - Appropriate antennas for target frequencies: + - 433 MHz antenna (UHF) + - 915 MHz antenna (UHF) + - 1.2 GHz antenna + - 2.4 GHz antenna (WiFi/Bluetooth type) + - 5.8 GHz antenna (WiFi/FPV type) + +### Optional: +- External battery pack (HackRF can drain batteries quickly) +- Tripod for stable positioning +- Directional antennas for improved range/direction finding +- GPS module for location logging + +## Firmware Requirements + +- **PortaPack Mayhem** firmware (recommended) - Latest version +- Alternatively: **PortaPack Havoc** firmware +- HackRF firmware 2018.01.1 or later + +Firmware updates available at: +- Mayhem: https://github.com/eried/portapack-mayhem +- Havoc: https://github.com/furrtek/portapack-havoc + +## Quick Start + +### 1. SD Card Preparation (5 minutes) + +```bash +# Format SD card as FAT32 +# Copy entire SDCARD directory contents to SD card root + +SDCARD/ +├── FREQMAN/ # Frequency scanner configurations +├── SETTINGS/ # Configuration files +├── CAPTURES/ # Your signal captures (initially empty) +└── REPLAYS/ # Your replay files (initially empty) +``` + +### 2. Installation + +1. Power off HackRF and PortaPack +2. Insert prepared microSD card into PortaPack +3. Power on device +4. PortaPack should boot to main menu + +### 3. First Use - Drone Detection (100% Legal) + +**Start Scanning in 5 Steps:** + +1. From main menu: **Select "Freqman"** +2. Choose a frequency file: + - `DRONE_SCAN_ALL.TXT` - Quick multi-band scan (recommended first try) + - `DRONE_SCAN_2G4.TXT` - 2.4 GHz (most common consumer drones) + - `DRONE_SCAN_5G8.TXT` - 5.8 GHz (FPV video links) +3. Set RSSI threshold: `-70 dBm` (good starting point) +4. Press **START** to begin scanning +5. Watch for signal activity - audio/visual alerts will trigger on detection + +**What you'll see:** +- Real-time RSSI readings +- Frequency where signal detected +- Signal strength indicator +- Alert when drone activity found + +See **DETECTION_GUIDE.md** for detailed instructions. + +### 4. Personal Recall Setup (YOUR Drones ONLY) + +⚠️ **This is for YOUR OWN equipment only. Using on others' drones is ILLEGAL.** + +**Setup Overview:** +1. Read **LEGAL.md** completely +2. Follow **PERSONAL_RECALL_SETUP.md** step-by-step +3. Capture YOUR drone's control signals +4. Create customized replay files +5. Test in safe, controlled environment +6. Verify legal compliance + +**This is NOT plug-and-play** - requires customization with YOUR specific drone's signals. + +## Feature Set + +### Drone Detection (Passive - Always Legal) + +#### Frequency Coverage: +- **433 MHz ISM Band** - RC control signals + - 40 channels (433.05 - 434.00 MHz) + - Optimal for: Generic RC, some toys + +- **915 MHz ISM Band** - RC control and telemetry + - 26 channels (902 - 928 MHz) + - Optimal for: Long-range systems, telemetry + +- **1.2 GHz Band** - Analog FPV video + - 15 channels (1.2 - 1.32 GHz) + - Optimal for: Long-range FPV video + +- **2.4 GHz ISM Band** - DJI, WiFi, most consumer drones + - 50 channels (2.4 - 2.48 GHz) + - Optimal for: Consumer drones, WiFi control + +- **5.8 GHz Band** - FPV video downlinks + - 48 channels across A/B/E/F/R bands + - Optimal for: Racing drones, FPV video + +- **GPS L1 (1575.42 MHz)** - GPS monitoring (receive only!) + - 7 channels around GPS L1 center + - Optimal for: Detecting GPS jamming attempts + +#### Detection Features: +- Real-time RSSI monitoring +- Audio alerts (configurable tones per band) +- Visual alerts (LED, screen flash) +- Activity logging with timestamps +- Pattern recognition helpers +- Multi-band simultaneous scanning +- Battery-efficient scanning modes +- Waterfall display +- Signal strength history + +### Personal Recall System (YOUR Equipment ONLY) + +#### Supported Protocols (Templates): +- **FrSky D16** - 16 channel frequency hopping (2.4 GHz) +- **FlySky AFHDS/AFHDS2A** - FlySky protocols (2.4 GHz) +- **ExpressLRS (ELRS)** - High-speed digital (900 MHz / 2.4 GHz) +- **TBS Crossfire** - Long-range (868/915 MHz) +- **Generic PPM/PWM** - Standard RC protocols +- **DSM2/DSMX** - Spektrum protocols + +#### Recall Features: +- Signal capture from YOUR transmitter +- Signal analysis and protocol identification +- Replay configuration for YOUR drone +- Return-to-home (RTH) command templates +- Failsafe trigger configurations +- Emergency recall sequences +- Range testing tools +- Safe testing modes (reduced power) + +## Directory Structure + +``` +HACKRF_PORTAPACK/ +├── README.md (this file) +├── DETECTION_GUIDE.md +├── PERSONAL_RECALL_SETUP.md +├── LEGAL.md +├── QUICK_START.md +└── SDCARD/ + ├── FREQMAN/ + │ ├── DRONE_SCAN_433.TXT # 433 MHz RC scanning + │ ├── DRONE_SCAN_915.TXT # 915 MHz RC/telemetry scanning + │ ├── DRONE_SCAN_1G2.TXT # 1.2 GHz FPV scanning + │ ├── DRONE_SCAN_2G4.TXT # 2.4 GHz control scanning + │ ├── DRONE_SCAN_5G8.TXT # 5.8 GHz FPV scanning + │ ├── DRONE_SCAN_GPS.TXT # GPS L1 monitoring + │ ├── DRONE_SCAN_ALL.TXT # Multi-band quick scan + │ ├── PERSONAL_FRSKY_D16.TXT # FrSky template + │ ├── PERSONAL_FLYSKY.TXT # FlySky template + │ ├── PERSONAL_ELRS.TXT # ELRS template + │ └── PERSONAL_CROSSFIRE.TXT # Crossfire template + ├── SETTINGS/ + │ ├── drone_detect_config.txt # Detection configuration + │ ├── alert_settings.txt # Alert configuration + │ └── personal_recall_template.txt # Recall template config + ├── CAPTURES/ + │ └── README_CAPTURES.TXT # Capture instructions + └── REPLAYS/ + └── README_REPLAYS.TXT # Replay instructions +``` + +## Safety Features + +### Detection Mode Safety: +- Passive reception only (no transmission) +- Configurable RSSI thresholds +- Battery monitoring +- Thermal management tips +- Power-saving modes + +### Transmission Mode Safety (Personal Recall): +- Mandatory confirmation before transmit +- Automatic transmission timeout +- Maximum duration limits +- Safe test mode (reduced power) +- Emergency stop capability +- Requires explicit user configuration + +## Documentation + +### Quick Reference: +- **QUICK_START.md** - 5-minute setup guide +- **README.md** (this file) - Overview and features + +### Detection System: +- **DETECTION_GUIDE.md** - Complete drone detection guide + - Scanner configuration + - RSSI interpretation + - Alert setup + - Logging and analysis + - Battery-efficient operation + - Multi-band strategies + +### Personal Recall System: +- **PERSONAL_RECALL_SETUP.md** - Personal drone recall setup + - Signal capture procedures + - Protocol identification + - Creating replay files + - Protocol-specific guides + - Testing procedures + - Troubleshooting + +### Legal & Safety: +- **LEGAL.md** - Complete legal information + - FCC Part 15 compliance + - International regulations + - Legal vs illegal use + - Safety warnings + - Liability disclaimer + +## Common Use Cases + +### 1. Drone Detection at Event/Property +✅ **Legal** - Passive monitoring only +- Load `DRONE_SCAN_ALL.TXT` +- Set RSSI threshold +- Enable audio alerts +- Monitor for activity +- Log detections for records + +### 2. FPV Frequency Coordination +✅ **Legal** - Receive-only scanning +- Load `DRONE_SCAN_5G8.TXT` +- Identify occupied channels +- Find clear frequency for your use +- Coordinate with other pilots + +### 3. Personal Drone Emergency Recall +⚠️ **Legal ONLY for YOUR drone** +- Pre-capture YOUR drone's signals +- Create tested replay file +- Emergency: Load replay file +- Transmit RTH command to YOUR drone +- Monitor drone response + +### 4. RC Equipment Testing +✅ **Legal** - YOUR equipment testing +- Capture YOUR transmitter output +- Analyze frequency accuracy +- Check signal strength +- Verify failsafe behavior + +## Troubleshooting + +### No Signals Detected +- Check antenna connection +- Verify correct frequency file loaded +- Lower RSSI threshold (-80 or -90 dBm) +- Increase RF/IF/BB gain settings +- Ensure drone activity in area + +### SD Card Not Reading +- Verify FAT32 format +- Check card compatibility (Class 10 recommended) +- Try different microSD card +- Ensure proper directory structure + +### Weak Signal Strength +- Use appropriate antenna for frequency +- Check antenna connection +- Increase gain settings +- Get closer to signal source +- Check for interference + +### HackRF Not Detected +- Check USB cable connection +- Verify PortaPack is properly seated +- Update HackRF firmware +- Try different USB port/cable +- Check battery power level + +### Replay Not Working (Personal Recall) +- Verify capture quality +- Check frequency accuracy +- Ensure correct sample rate +- Test with increased TX gain (verify legal limits!) +- Recapture signal with better parameters +- Verify drone is in range and powered + +## Battery Life Tips + +HackRF One is power-hungry. To maximize battery: +- Use high-capacity external battery (10,000+ mAh) +- Enable battery saver mode in settings +- Reduce screen brightness +- Disable waterfall when not needed +- Use narrower scan ranges +- Power off when not in use +- Monitor thermal levels + +## Antenna Selection Guide + +| Frequency | Antenna Type | Connector | Notes | +|-----------|--------------|-----------|-------| +| 433 MHz | UHF stub/whip | SMA | 17.3 cm quarter-wave | +| 915 MHz | UHF stub/whip | SMA | 8.2 cm quarter-wave | +| 1.2 GHz | Dipole/patch | SMA | Directional for FPV | +| 2.4 GHz | WiFi rubber duck | SMA/RP-SMA | Common, effective | +| 5.8 GHz | FPV pagoda/patch | SMA/RP-SMA | Circular polarized | + +**Multi-band antennas** (e.g., discone, wideband) work but with reduced performance. + +## Advanced Features + +### Signal Analysis: +- FFT spectrum analyzer +- Waterfall display +- Signal demodulation +- Protocol decoding helpers +- Timing analysis +- Modulation identification + +### Custom Configurations: +- Create custom frequency lists +- Define custom protocols +- Set up automated scanning sequences +- Configure complex alerting rules +- Develop detection profiles + +## Integration with ultimatel-ily Project + +This HackRF/PortaPack package complements the main ultimatel-ily firmware project: + +- **Main Project**: CC1101-based drone control (different hardware) +- **This Package**: HackRF-based detection and analysis (this hardware) +- **Relationship**: Both educational tools for drone RF systems +- **Cross-Reference**: Similar frequencies, different implementations + +See main [ultimatel-ily README](../README.md) for CC1101 firmware details. + +## FAQ + +**Q: Can I use this to take down drones I don't own?** +A: **NO. That is ILLEGAL.** This package is for detection (legal) and controlling YOUR OWN drones only. + +**Q: Is drone detection legal?** +A: **YES.** Receiving/monitoring radio signals is always legal. You're just listening, not transmitting. + +**Q: What range can I expect for detection?** +A: Depends on many factors: antenna quality, frequency, drone power, environment. Typically: +- Strong signals: 1-2 km +- Weak signals: 100-500 m +- With directional antenna: 2-5 km+ + +**Q: Will this work with DJI drones?** +A: **Detection: YES** - Can detect DJI signals at 2.4/5.8 GHz +**Personal Recall: COMPLEX** - DJI uses encrypted protocols, very difficult to replay + +**Q: Can I add my own frequencies?** +A: **YES!** Edit the .TXT files in FREQMAN directory following the format: +``` +f=,m=,bw=,d= +``` + +**Q: Is this package legal to download/possess?** +A: **YES.** Possessing this software/hardware is legal. Only MISUSE is illegal. + +**Q: What about flying in restricted airspace?** +A: This package doesn't help with that. YOU are responsible for: +- Checking airspace restrictions +- Following FAA/local regulations +- Registering drones if required +- Obtaining necessary permissions + +**Q: Can I sell this package or services using it?** +A: Check your local regulations. Generally: +- Selling educational packages: Usually OK +- Offering "drone defeat" services: Likely ILLEGAL +- RF testing services: May require FCC/local licenses + +**Q: How do I report illegal drone activity?** +A: Contact: +- Local law enforcement +- FAA (in USA): 1-866-TELL-FAA +- Local aviation authority (other countries) +- Do NOT attempt to interfere yourself + +## Contributing + +Contributions welcome! Please ensure: +- Legal compliance in all examples +- Clear documentation +- Tested configurations +- Proper attribution +- Safety warnings where appropriate + +## License + +This educational package is provided as-is for legal use only. + +See LEGAL.md for complete terms and conditions. + +## Support + +For issues, questions, or contributions: +- GitHub Issues: [ultimatel-ily repository](https://github.com/Crashkeyz/ultimatel-ily) +- Documentation: See included .md files +- Community: HackRF and PortaPack user forums + +## Credits + +- HackRF One hardware: Great Scott Gadgets +- PortaPack project: Jared Boone, Furrtek, Erwin Ried +- Frequency data: Community contributed +- Protocol information: Open source communities + +## Version + +Package Version: 1.0.0 +Last Updated: 2024 +Compatible: PortaPack Mayhem firmware + +--- + +## Final Reminder + +🛑 **RESPECT THE LAW** 🛑 + +This toolkit is powerful and educational. Use it responsibly: +- Detection: Always legal, go ahead! +- Transmission: Only to YOUR equipment, verify legal compliance +- Report suspicious drone activity to authorities +- Never interfere with others' equipment +- Be a responsible member of the RF community + +**When in doubt, don't transmit. Detection alone is powerful and legal.** + +--- + +**Next Steps:** +1. Read LEGAL.md thoroughly +2. Follow QUICK_START.md for setup +3. Try detection mode (safe and legal) +4. If needed, carefully follow PERSONAL_RECALL_SETUP.md +5. Always prioritize safety and legality + +Happy (legal) drone monitoring! 🚁📡 diff --git a/HACKRF_PORTAPACK/SDCARD/CAPTURES/README_CAPTURES.TXT b/HACKRF_PORTAPACK/SDCARD/CAPTURES/README_CAPTURES.TXT new file mode 100644 index 0000000..e45dc79 --- /dev/null +++ b/HACKRF_PORTAPACK/SDCARD/CAPTURES/README_CAPTURES.TXT @@ -0,0 +1,57 @@ +# CAPTURES Directory +# Store your captured drone signals here + +## Purpose +This directory is for storing captured RF signals from YOUR OWN drones only. + +## Legal Notice +⚠️ **WARNING: FOR YOUR OWN EQUIPMENT ONLY** ⚠️ + +It is LEGAL to: +- Capture signals from YOUR OWN drone +- Record YOUR OWN transmitter's control signals +- Analyze YOUR OWN equipment's RF patterns + +It is ILLEGAL to: +- Capture and replay signals from drones you don't own +- Record others' control signals with intent to interfere +- Use captured signals to control equipment you don't own + +## File Naming Convention +Use descriptive names for your captures: +- `my_drone_rth_2023-12-25.c16` - Return to home signal +- `my_quad_failsafe.c16` - Failsafe trigger +- `my_tx_binding.c16` - Binding sequence +- `range_test_capture.c16` - Range test signals + +## Capture Format +HackRF/PortaPack typically saves in these formats: +- `.c16` - Complex 16-bit samples (int16_t I/Q pairs) +- `.c8` - Complex 8-bit samples +- `.wav` - WAV format for audio-band signals + +## Capture Settings to Record +When saving a capture, also document: +1. Center frequency +2. Sample rate +3. Gain settings (IF, BB, RF) +4. Bandwidth +5. Date and time +6. Drone model and transmitter type +7. Purpose of capture (RTH, failsafe, etc.) + +## Storage Management +- Captures can be large files (MB to GB) +- Use appropriate sample rates for your protocol +- Delete old captures when no longer needed +- Keep your SD card organized + +## Next Steps +After capturing signals from YOUR drone: +1. Analyze them using PortaPack's analyzer tools +2. Identify the exact frequencies and timing +3. Create replay files in the REPLAYS directory +4. Test in a safe, controlled environment +5. Document your settings + +See PERSONAL_RECALL_SETUP.md for detailed capture procedures. diff --git a/HACKRF_PORTAPACK/SDCARD/FREQMAN/DRONE_SCAN_1G2.TXT b/HACKRF_PORTAPACK/SDCARD/FREQMAN/DRONE_SCAN_1G2.TXT new file mode 100644 index 0000000..0fa461f --- /dev/null +++ b/HACKRF_PORTAPACK/SDCARD/FREQMAN/DRONE_SCAN_1G2.TXT @@ -0,0 +1,20 @@ +# PortaPack Mayhem FREQMAN File +# 1.2 GHz Band - FPV Video Links +# LEGAL USE: Receive-only monitoring (always legal) +# Common 1.2-1.3 GHz analog video transmission frequencies + +f=1200000000,m=WFM,bw=6000000,d=1.2G Ch 1 +f=1220000000,m=WFM,bw=6000000,d=1.22G Ch 2 +f=1240000000,m=WFM,bw=6000000,d=1.24G Ch 3 +f=1258000000,m=WFM,bw=6000000,d=1.258G Ch E1 +f=1259000000,m=WFM,bw=6000000,d=1.259G Ch E2 +f=1260000000,m=WFM,bw=6000000,d=1.26G Ch E3 +f=1261000000,m=WFM,bw=6000000,d=1.261G Ch E4 +f=1262000000,m=WFM,bw=6000000,d=1.262G Ch E5 +f=1263000000,m=WFM,bw=6000000,d=1.263G Ch E6 +f=1264000000,m=WFM,bw=6000000,d=1.264G Ch E7 +f=1265000000,m=WFM,bw=6000000,d=1.265G Ch E8 +f=1266000000,m=WFM,bw=6000000,d=1.266G Ch 4 +f=1280000000,m=WFM,bw=6000000,d=1.28G Ch 5 +f=1300000000,m=WFM,bw=6000000,d=1.3G Ch 6 +f=1320000000,m=WFM,bw=6000000,d=1.32G Ch 7 diff --git a/HACKRF_PORTAPACK/SDCARD/FREQMAN/DRONE_SCAN_2G4.TXT b/HACKRF_PORTAPACK/SDCARD/FREQMAN/DRONE_SCAN_2G4.TXT new file mode 100644 index 0000000..152c25f --- /dev/null +++ b/HACKRF_PORTAPACK/SDCARD/FREQMAN/DRONE_SCAN_2G4.TXT @@ -0,0 +1,56 @@ +# PortaPack Mayhem FREQMAN File +# 2.4 GHz Band - DJI, WiFi, and RC Control +# LEGAL USE: Receive-only monitoring (always legal) +# Common 2.4 GHz drone control and WiFi frequencies + +f=2400000000,m=AM,bw=1000000,d=2.4G ISM Lower +f=2401000000,m=AM,bw=1000000,d=2.401G Ch 1 +f=2402000000,m=AM,bw=1000000,d=2.402G WiFi BT +f=2403000000,m=AM,bw=1000000,d=2.403G Ch 2 +f=2404000000,m=AM,bw=1000000,d=2.404G Ch 3 +f=2405000000,m=AM,bw=1000000,d=2.405G Ch 4 +f=2406000000,m=AM,bw=1000000,d=2.406G Ch 5 +f=2407000000,m=AM,bw=1000000,d=2.407G WiFi Ch1 +f=2408000000,m=AM,bw=1000000,d=2.408G Ch 6 +f=2410000000,m=AM,bw=1000000,d=2.41G Ch 7 +f=2412000000,m=AM,bw=1000000,d=2.412G WiFi Ch1 +f=2414000000,m=AM,bw=1000000,d=2.414G Ch 8 +f=2416000000,m=AM,bw=1000000,d=2.416G Ch 9 +f=2417000000,m=AM,bw=1000000,d=2.417G WiFi Ch2 +f=2418000000,m=AM,bw=1000000,d=2.418G Ch 10 +f=2420000000,m=AM,bw=1000000,d=2.42G Ch 11 +f=2422000000,m=AM,bw=1000000,d=2.422G WiFi Ch3 +f=2424000000,m=AM,bw=1000000,d=2.424G Ch 12 +f=2426000000,m=AM,bw=1000000,d=2.426G Ch 13 +f=2427000000,m=AM,bw=1000000,d=2.427G WiFi Ch4 +f=2428000000,m=AM,bw=1000000,d=2.428G Ch 14 +f=2430000000,m=AM,bw=1000000,d=2.43G Ch 15 +f=2432000000,m=AM,bw=1000000,d=2.432G WiFi Ch5 +f=2434000000,m=AM,bw=1000000,d=2.434G Ch 16 +f=2436000000,m=AM,bw=1000000,d=2.436G Ch 17 +f=2437000000,m=AM,bw=1000000,d=2.437G WiFi Ch6 +f=2438000000,m=AM,bw=1000000,d=2.438G Ch 18 +f=2440000000,m=AM,bw=1000000,d=2.44G Ch 19 +f=2442000000,m=AM,bw=1000000,d=2.442G WiFi Ch7 +f=2444000000,m=AM,bw=1000000,d=2.444G Ch 20 +f=2446000000,m=AM,bw=1000000,d=2.446G Ch 21 +f=2447000000,m=AM,bw=1000000,d=2.447G WiFi Ch8 +f=2448000000,m=AM,bw=1000000,d=2.448G Ch 22 +f=2450000000,m=AM,bw=1000000,d=2.45G ISM Ctr +f=2452000000,m=AM,bw=1000000,d=2.452G WiFi Ch9 +f=2454000000,m=AM,bw=1000000,d=2.454G Ch 23 +f=2456000000,m=AM,bw=1000000,d=2.456G Ch 24 +f=2457000000,m=AM,bw=1000000,d=2.457G WiFi Ch10 +f=2458000000,m=AM,bw=1000000,d=2.458G Ch 25 +f=2460000000,m=AM,bw=1000000,d=2.46G Ch 26 +f=2462000000,m=AM,bw=1000000,d=2.462G WiFi Ch11 +f=2464000000,m=AM,bw=1000000,d=2.464G Ch 27 +f=2466000000,m=AM,bw=1000000,d=2.466G Ch 28 +f=2467000000,m=AM,bw=1000000,d=2.467G WiFi Ch12 +f=2468000000,m=AM,bw=1000000,d=2.468G Ch 29 +f=2470000000,m=AM,bw=1000000,d=2.47G Ch 30 +f=2472000000,m=AM,bw=1000000,d=2.472G WiFi Ch13 +f=2474000000,m=AM,bw=1000000,d=2.474G Ch 31 +f=2476000000,m=AM,bw=1000000,d=2.476G Ch 32 +f=2478000000,m=AM,bw=1000000,d=2.478G Ch 33 +f=2480000000,m=AM,bw=1000000,d=2.48G ISM Upper diff --git a/HACKRF_PORTAPACK/SDCARD/FREQMAN/DRONE_SCAN_433.TXT b/HACKRF_PORTAPACK/SDCARD/FREQMAN/DRONE_SCAN_433.TXT new file mode 100644 index 0000000..ee25ad7 --- /dev/null +++ b/HACKRF_PORTAPACK/SDCARD/FREQMAN/DRONE_SCAN_433.TXT @@ -0,0 +1,45 @@ +# PortaPack Mayhem FREQMAN File +# 433 MHz Band - Common RC Control Frequencies +# LEGAL USE: Receive-only monitoring (always legal) +# This file contains common 433 MHz drone control frequencies + +f=433050000,m=AM,bw=150000,d=433.05 RC Ch 1 +f=433075000,m=AM,bw=150000,d=433.075 RC Ch 2 +f=433100000,m=AM,bw=150000,d=433.10 RC Ch 3 +f=433125000,m=AM,bw=150000,d=433.125 RC Ch 4 +f=433150000,m=AM,bw=150000,d=433.15 RC Ch 5 +f=433175000,m=AM,bw=150000,d=433.175 RC Ch 6 +f=433200000,m=AM,bw=150000,d=433.20 RC Ch 7 +f=433225000,m=AM,bw=150000,d=433.225 RC Ch 8 +f=433250000,m=AM,bw=150000,d=433.25 RC Ch 9 +f=433275000,m=AM,bw=150000,d=433.275 RC Ch 10 +f=433300000,m=AM,bw=150000,d=433.30 RC Ch 11 +f=433325000,m=AM,bw=150000,d=433.325 RC Ch 12 +f=433350000,m=AM,bw=150000,d=433.35 RC Ch 13 +f=433375000,m=AM,bw=150000,d=433.375 RC Ch 14 +f=433400000,m=AM,bw=150000,d=433.40 RC Ch 15 +f=433425000,m=AM,bw=150000,d=433.425 RC Ch 16 +f=433450000,m=AM,bw=150000,d=433.45 RC Ch 17 +f=433475000,m=AM,bw=150000,d=433.475 RC Ch 18 +f=433500000,m=AM,bw=150000,d=433.50 RC Ch 19 +f=433525000,m=AM,bw=150000,d=433.525 RC Ch 20 +f=433550000,m=AM,bw=150000,d=433.55 RC Ch 21 +f=433575000,m=AM,bw=150000,d=433.575 RC Ch 22 +f=433600000,m=AM,bw=150000,d=433.60 RC Ch 23 +f=433625000,m=AM,bw=150000,d=433.625 RC Ch 24 +f=433650000,m=AM,bw=150000,d=433.65 RC Ch 25 +f=433675000,m=AM,bw=150000,d=433.675 RC Ch 26 +f=433700000,m=AM,bw=150000,d=433.70 RC Ch 27 +f=433725000,m=AM,bw=150000,d=433.725 RC Ch 28 +f=433750000,m=AM,bw=150000,d=433.75 RC Ch 29 +f=433775000,m=AM,bw=150000,d=433.775 RC Ch 30 +f=433800000,m=AM,bw=150000,d=433.80 RC Ch 31 +f=433825000,m=AM,bw=150000,d=433.825 RC Ch 32 +f=433850000,m=AM,bw=150000,d=433.85 RC Ch 33 +f=433875000,m=AM,bw=150000,d=433.875 RC Ch 34 +f=433900000,m=AM,bw=150000,d=433.90 RC Ch 35 +f=433920000,m=AM,bw=150000,d=433.92 ISM Center +f=433925000,m=AM,bw=150000,d=433.925 RC Ch 36 +f=433950000,m=AM,bw=150000,d=433.95 RC Ch 37 +f=433975000,m=AM,bw=150000,d=433.975 RC Ch 38 +f=434000000,m=AM,bw=150000,d=434.00 RC Ch 39 diff --git a/HACKRF_PORTAPACK/SDCARD/FREQMAN/DRONE_SCAN_5G8.TXT b/HACKRF_PORTAPACK/SDCARD/FREQMAN/DRONE_SCAN_5G8.TXT new file mode 100644 index 0000000..91cde8d --- /dev/null +++ b/HACKRF_PORTAPACK/SDCARD/FREQMAN/DRONE_SCAN_5G8.TXT @@ -0,0 +1,54 @@ +# PortaPack Mayhem FREQMAN File +# 5.8 GHz Band - FPV Video Downlinks +# LEGAL USE: Receive-only monitoring (always legal) +# Common 5.8 GHz FPV video transmission frequencies (Band A/B/E/F/R) + +# Band A (Boscam A) +f=5865000000,m=WFM,bw=6000000,d=5.865G Band A1 +f=5845000000,m=WFM,bw=6000000,d=5.845G Band A2 +f=5825000000,m=WFM,bw=6000000,d=5.825G Band A3 +f=5805000000,m=WFM,bw=6000000,d=5.805G Band A4 +f=5785000000,m=WFM,bw=6000000,d=5.785G Band A5 +f=5765000000,m=WFM,bw=6000000,d=5.765G Band A6 +f=5745000000,m=WFM,bw=6000000,d=5.745G Band A7 +f=5725000000,m=WFM,bw=6000000,d=5.725G Band A8 + +# Band B (Boscam B) +f=5733000000,m=WFM,bw=6000000,d=5.733G Band B1 +f=5752000000,m=WFM,bw=6000000,d=5.752G Band B2 +f=5771000000,m=WFM,bw=6000000,d=5.771G Band B3 +f=5790000000,m=WFM,bw=6000000,d=5.790G Band B4 +f=5809000000,m=WFM,bw=6000000,d=5.809G Band B5 +f=5828000000,m=WFM,bw=6000000,d=5.828G Band B6 +f=5847000000,m=WFM,bw=6000000,d=5.847G Band B7 +f=5866000000,m=WFM,bw=6000000,d=5.866G Band B8 + +# Band E (Boscam E / DJI) +f=5705000000,m=WFM,bw=6000000,d=5.705G Band E1 +f=5685000000,m=WFM,bw=6000000,d=5.685G Band E2 +f=5665000000,m=WFM,bw=6000000,d=5.665G Band E3 +f=5645000000,m=WFM,bw=6000000,d=5.645G Band E4 +f=5885000000,m=WFM,bw=6000000,d=5.885G Band E5 +f=5905000000,m=WFM,bw=6000000,d=5.905G Band E6 +f=5925000000,m=WFM,bw=6000000,d=5.925G Band E7 +f=5945000000,m=WFM,bw=6000000,d=5.945G Band E8 + +# Band F (Fatshark/Immersion) +f=5740000000,m=WFM,bw=6000000,d=5.740G Band F1 +f=5760000000,m=WFM,bw=6000000,d=5.760G Band F2 +f=5780000000,m=WFM,bw=6000000,d=5.780G Band F3 +f=5800000000,m=WFM,bw=6000000,d=5.800G Band F4 +f=5820000000,m=WFM,bw=6000000,d=5.820G Band F5 +f=5840000000,m=WFM,bw=6000000,d=5.840G Band F6 +f=5860000000,m=WFM,bw=6000000,d=5.860G Band F7 +f=5880000000,m=WFM,bw=6000000,d=5.880G Band F8 + +# Band R (Raceband) +f=5658000000,m=WFM,bw=6000000,d=5.658G Race R1 +f=5695000000,m=WFM,bw=6000000,d=5.695G Race R2 +f=5732000000,m=WFM,bw=6000000,d=5.732G Race R3 +f=5769000000,m=WFM,bw=6000000,d=5.769G Race R4 +f=5806000000,m=WFM,bw=6000000,d=5.806G Race R5 +f=5843000000,m=WFM,bw=6000000,d=5.843G Race R6 +f=5880000000,m=WFM,bw=6000000,d=5.880G Race R7 +f=5917000000,m=WFM,bw=6000000,d=5.917G Race R8 diff --git a/HACKRF_PORTAPACK/SDCARD/FREQMAN/DRONE_SCAN_915.TXT b/HACKRF_PORTAPACK/SDCARD/FREQMAN/DRONE_SCAN_915.TXT new file mode 100644 index 0000000..c097ed9 --- /dev/null +++ b/HACKRF_PORTAPACK/SDCARD/FREQMAN/DRONE_SCAN_915.TXT @@ -0,0 +1,32 @@ +# PortaPack Mayhem FREQMAN File +# 915 MHz ISM Band - RC Control and Telemetry +# LEGAL USE: Receive-only monitoring (always legal) +# Common frequencies for drone control and telemetry systems + +f=902000000,m=AM,bw=200000,d=902.0 ISM Lower +f=903000000,m=AM,bw=200000,d=903.0 Telemetry +f=904000000,m=AM,bw=200000,d=904.0 Telemetry +f=905000000,m=AM,bw=200000,d=905.0 Telemetry +f=906000000,m=AM,bw=200000,d=906.0 RC/Telem +f=907000000,m=AM,bw=200000,d=907.0 RC/Telem +f=908000000,m=AM,bw=200000,d=908.0 RC/Telem +f=909000000,m=AM,bw=200000,d=909.0 RC Ch 1 +f=910000000,m=AM,bw=200000,d=910.0 RC Ch 2 +f=911000000,m=AM,bw=200000,d=911.0 RC Ch 3 +f=912000000,m=AM,bw=200000,d=912.0 RC Ch 4 +f=913000000,m=AM,bw=200000,d=913.0 RC Ch 5 +f=914000000,m=AM,bw=200000,d=914.0 RC Ch 6 +f=915000000,m=AM,bw=200000,d=915.0 ISM Center +f=916000000,m=AM,bw=200000,d=916.0 RC Ch 7 +f=917000000,m=AM,bw=200000,d=917.0 RC Ch 8 +f=918000000,m=AM,bw=200000,d=918.0 RC Ch 9 +f=919000000,m=AM,bw=200000,d=919.0 RC Ch 10 +f=920000000,m=AM,bw=200000,d=920.0 RC Ch 11 +f=921000000,m=AM,bw=200000,d=921.0 RC Ch 12 +f=922000000,m=AM,bw=200000,d=922.0 RC Ch 13 +f=923000000,m=AM,bw=200000,d=923.0 RC Ch 14 +f=924000000,m=AM,bw=200000,d=924.0 RC Ch 15 +f=925000000,m=AM,bw=200000,d=925.0 RC Ch 16 +f=926000000,m=AM,bw=200000,d=926.0 RC/Telem +f=927000000,m=AM,bw=200000,d=927.0 RC/Telem +f=928000000,m=AM,bw=200000,d=928.0 ISM Upper diff --git a/HACKRF_PORTAPACK/SDCARD/FREQMAN/DRONE_SCAN_ALL.TXT b/HACKRF_PORTAPACK/SDCARD/FREQMAN/DRONE_SCAN_ALL.TXT new file mode 100644 index 0000000..9153caa --- /dev/null +++ b/HACKRF_PORTAPACK/SDCARD/FREQMAN/DRONE_SCAN_ALL.TXT @@ -0,0 +1,38 @@ +# PortaPack Mayhem FREQMAN File +# Comprehensive Multi-Band Drone Detection +# LEGAL USE: Receive-only monitoring (always legal) +# Key frequencies across all drone bands for quick scanning + +# 433 MHz ISM Band - RC Control +f=433920000,m=AM,bw=150000,d=433.92 ISM RC + +# 868 MHz ISM Band (EU) +f=868000000,m=AM,bw=200000,d=868.0 EU ISM + +# 915 MHz ISM Band - RC/Telemetry +f=915000000,m=AM,bw=200000,d=915.0 ISM RC + +# 1.2 GHz - FPV Video +f=1258000000,m=WFM,bw=6000000,d=1.258G FPV + +# GPS L1 +f=1575420000,m=AM,bw=2000000,d=1575.42 GPS L1 + +# 2.4 GHz - DJI/WiFi Control +f=2400000000,m=AM,bw=1000000,d=2.4G Lower +f=2450000000,m=AM,bw=1000000,d=2.45G Center +f=2480000000,m=AM,bw=1000000,d=2.48G Upper + +# 5.8 GHz - FPV Video (Most Common) +f=5658000000,m=WFM,bw=6000000,d=5.658G Race R1 +f=5695000000,m=WFM,bw=6000000,d=5.695G Race R2 +f=5732000000,m=WFM,bw=6000000,d=5.732G Race R3 +f=5769000000,m=WFM,bw=6000000,d=5.769G Race R4 +f=5806000000,m=WFM,bw=6000000,d=5.806G Race R5 +f=5843000000,m=WFM,bw=6000000,d=5.843G Race R6 +f=5880000000,m=WFM,bw=6000000,d=5.880G Race R7 +f=5917000000,m=WFM,bw=6000000,d=5.917G Race R8 +f=5865000000,m=WFM,bw=6000000,d=5.865G Band A1 +f=5845000000,m=WFM,bw=6000000,d=5.845G Band A2 +f=5825000000,m=WFM,bw=6000000,d=5.825G Band A3 +f=5805000000,m=WFM,bw=6000000,d=5.805G Band A4 diff --git a/HACKRF_PORTAPACK/SDCARD/FREQMAN/DRONE_SCAN_GPS.TXT b/HACKRF_PORTAPACK/SDCARD/FREQMAN/DRONE_SCAN_GPS.TXT new file mode 100644 index 0000000..e80ec5a --- /dev/null +++ b/HACKRF_PORTAPACK/SDCARD/FREQMAN/DRONE_SCAN_GPS.TXT @@ -0,0 +1,13 @@ +# PortaPack Mayhem FREQMAN File +# GPS L1 Band - 1575.42 MHz +# LEGAL USE: Receive-only monitoring (always legal) +# WARNING: GPS jamming is illegal and dangerous +# This file is for MONITORING ONLY + +f=1575420000,m=AM,bw=2000000,d=GPS L1 Center +f=1575410000,m=AM,bw=2000000,d=GPS L1 -10kHz +f=1575430000,m=AM,bw=2000000,d=GPS L1 +10kHz +f=1575400000,m=AM,bw=2000000,d=GPS L1 -20kHz +f=1575440000,m=AM,bw=2000000,d=GPS L1 +20kHz +f=1575390000,m=AM,bw=2000000,d=GPS L1 -30kHz +f=1575450000,m=AM,bw=2000000,d=GPS L1 +30kHz diff --git a/HACKRF_PORTAPACK/SDCARD/FREQMAN/PERSONAL_CROSSFIRE.TXT b/HACKRF_PORTAPACK/SDCARD/FREQMAN/PERSONAL_CROSSFIRE.TXT new file mode 100644 index 0000000..3dae0f2 --- /dev/null +++ b/HACKRF_PORTAPACK/SDCARD/FREQMAN/PERSONAL_CROSSFIRE.TXT @@ -0,0 +1,46 @@ +# PortaPack Mayhem FREQMAN File +# TBS Crossfire (CRSF) Protocol Template - FOR YOUR OWN DRONES ONLY +# WARNING: Transmitting to drones you don't own is ILLEGAL +# +# This template requires customization with YOUR drone's specific frequencies +# Follow the PERSONAL_RECALL_SETUP.md guide to capture your own signals +# +# TBS Crossfire Specifications: +# - 868 MHz (EU) or 915 MHz (US) ISM bands +# - Long-range digital protocol +# - LoRa-based modulation +# - Multiple power levels +# - User must capture their own binding and settings + +# 915 MHz CRSF TEMPLATE (US/International) +f=915000000,m=AM,bw=500000,d=CRSF 915M Center [TEMPLATE] +f=913000000,m=AM,bw=500000,d=CRSF 915M-2 [TEMPLATE] +f=917000000,m=AM,bw=500000,d=CRSF 915M+2 [TEMPLATE] +f=911000000,m=AM,bw=500000,d=CRSF 915M-4 [TEMPLATE] +f=919000000,m=AM,bw=500000,d=CRSF 915M+4 [TEMPLATE] + +# 868 MHz CRSF TEMPLATE (EU) +f=868000000,m=AM,bw=500000,d=CRSF 868M Center [TEMPLATE] +f=866000000,m=AM,bw=500000,d=CRSF 868M-2 [TEMPLATE] +f=870000000,m=AM,bw=500000,d=CRSF 868M+2 [TEMPLATE] +f=864000000,m=AM,bw=500000,d=CRSF 868M-4 [TEMPLATE] +f=872000000,m=AM,bw=500000,d=CRSF 868M+4 [TEMPLATE] + +# INSTRUCTIONS: +# TBS Crossfire uses frequency hopping and binding +# This protocol is designed for security and long range +# +# For YOUR own drone: +# 1. Determine if using 868 MHz (EU) or 915 MHz (US) version +# 2. Power on YOUR TBS Crossfire transmitter +# 3. Ensure YOUR drone is bound to YOUR transmitter +# 4. Use HackRF in receive mode to capture signals +# 5. Identify the center frequency and hopping pattern +# 6. Replace template frequencies with YOUR actual values +# 7. Capture YOUR RTH or failsafe command +# 8. Test in a safe, controlled environment +# +# Note: Crossfire has built-in encryption and hopping +# Replay requires capturing the complete protocol sequence +# +# See PERSONAL_RECALL_SETUP.md for detailed instructions diff --git a/HACKRF_PORTAPACK/SDCARD/FREQMAN/PERSONAL_ELRS.TXT b/HACKRF_PORTAPACK/SDCARD/FREQMAN/PERSONAL_ELRS.TXT new file mode 100644 index 0000000..61a5a51 --- /dev/null +++ b/HACKRF_PORTAPACK/SDCARD/FREQMAN/PERSONAL_ELRS.TXT @@ -0,0 +1,48 @@ +# PortaPack Mayhem FREQMAN File +# ExpressLRS (ELRS) Protocol Template - FOR YOUR OWN DRONES ONLY +# WARNING: Transmitting to drones you don't own is ILLEGAL +# +# This template requires customization with YOUR drone's specific frequencies +# Follow the PERSONAL_RECALL_SETUP.md guide to capture your own signals +# +# ExpressLRS Specifications: +# - 2.4 GHz and 900 MHz variants +# - High-speed digital protocol +# - Multiple packet rates (50Hz, 150Hz, 250Hz, 500Hz, 1000Hz) +# - LoRa-based modulation +# - User must capture their own binding phrase and settings + +# 2.4 GHz ELRS TEMPLATE FREQUENCIES (MUST BE CUSTOMIZED) +f=2400000000,m=AM,bw=2000000,d=ELRS 2.4G Ch1 [TEMPLATE] +f=2420000000,m=AM,bw=2000000,d=ELRS 2.4G Ch2 [TEMPLATE] +f=2440000000,m=AM,bw=2000000,d=ELRS 2.4G Ch3 [TEMPLATE] +f=2460000000,m=AM,bw=2000000,d=ELRS 2.4G Ch4 [TEMPLATE] +f=2480000000,m=AM,bw=2000000,d=ELRS 2.4G Ch5 [TEMPLATE] + +# 900 MHz ELRS TEMPLATE FREQUENCIES (MUST BE CUSTOMIZED) +f=903000000,m=AM,bw=500000,d=ELRS 900M Ch1 [TEMPLATE] +f=909000000,m=AM,bw=500000,d=ELRS 900M Ch2 [TEMPLATE] +f=915000000,m=AM,bw=500000,d=ELRS 900M Ch3 [TEMPLATE] +f=921000000,m=AM,bw=500000,d=ELRS 900M Ch4 [TEMPLATE] +f=927000000,m=AM,bw=500000,d=ELRS 900M Ch5 [TEMPLATE] + +# INSTRUCTIONS: +# ExpressLRS uses a unique binding phrase and frequency hopping +# This makes replay more complex - you need: +# 1. Your ELRS binding phrase +# 2. Your configured frequency band (2.4G or 900M) +# 3. Your packet rate setting +# 4. Capture of YOUR specific control signals +# +# ELRS is encrypted with a binding phrase, making unauthorized +# control virtually impossible - this is by design for security +# +# For YOUR own drone: +# 1. Know your binding phrase and settings +# 2. Use HackRF to capture YOUR control signals +# 3. Analyze the frequency hopping pattern +# 4. Update this template with YOUR values +# 5. Test in a safe, controlled environment +# +# See PERSONAL_RECALL_SETUP.md for detailed instructions +# Note: ELRS replay may require advanced signal processing diff --git a/HACKRF_PORTAPACK/SDCARD/FREQMAN/PERSONAL_FLYSKY.TXT b/HACKRF_PORTAPACK/SDCARD/FREQMAN/PERSONAL_FLYSKY.TXT new file mode 100644 index 0000000..81bf556 --- /dev/null +++ b/HACKRF_PORTAPACK/SDCARD/FREQMAN/PERSONAL_FLYSKY.TXT @@ -0,0 +1,42 @@ +# PortaPack Mayhem FREQMAN File +# FlySky AFHDS/AFHDS2A Protocol Template - FOR YOUR OWN DRONES ONLY +# WARNING: Transmitting to drones you don't own is ILLEGAL +# +# This template requires customization with YOUR drone's specific frequencies +# Follow the PERSONAL_RECALL_SETUP.md guide to capture your own signals +# +# FlySky Specifications: +# - AFHDS: 2.4 GHz, GFSK modulation +# - AFHDS2A: 2.4 GHz, improved protocol with telemetry +# - Frequency hopping across 16 channels +# - User must capture their own frequency and timing + +# TEMPLATE FREQUENCIES (MUST BE CUSTOMIZED) +# Replace these with YOUR drone's actual frequencies after capture +f=2401000000,m=AM,bw=1000000,d=FlySky Ch1 [TEMPLATE] +f=2406000000,m=AM,bw=1000000,d=FlySky Ch2 [TEMPLATE] +f=2411000000,m=AM,bw=1000000,d=FlySky Ch3 [TEMPLATE] +f=2416000000,m=AM,bw=1000000,d=FlySky Ch4 [TEMPLATE] +f=2421000000,m=AM,bw=1000000,d=FlySky Ch5 [TEMPLATE] +f=2426000000,m=AM,bw=1000000,d=FlySky Ch6 [TEMPLATE] +f=2431000000,m=AM,bw=1000000,d=FlySky Ch7 [TEMPLATE] +f=2436000000,m=AM,bw=1000000,d=FlySky Ch8 [TEMPLATE] +f=2441000000,m=AM,bw=1000000,d=FlySky Ch9 [TEMPLATE] +f=2446000000,m=AM,bw=1000000,d=FlySky Ch10 [TEMPLATE] +f=2451000000,m=AM,bw=1000000,d=FlySky Ch11 [TEMPLATE] +f=2456000000,m=AM,bw=1000000,d=FlySky Ch12 [TEMPLATE] +f=2461000000,m=AM,bw=1000000,d=FlySky Ch13 [TEMPLATE] +f=2466000000,m=AM,bw=1000000,d=FlySky Ch14 [TEMPLATE] +f=2471000000,m=AM,bw=1000000,d=FlySky Ch15 [TEMPLATE] +f=2476000000,m=AM,bw=1000000,d=FlySky Ch16 [TEMPLATE] + +# INSTRUCTIONS: +# 1. Power on YOUR FlySky transmitter and drone +# 2. Bind transmitter to YOUR drone if not already bound +# 3. Use HackRF in receive mode to capture control signals +# 4. Identify your specific frequency hopping pattern +# 5. Replace the frequencies above with YOUR actual values +# 6. Capture failsafe and RTH commands from YOUR transmitter +# 7. Test in a safe, controlled environment +# +# See PERSONAL_RECALL_SETUP.md for detailed instructions diff --git a/HACKRF_PORTAPACK/SDCARD/FREQMAN/PERSONAL_FRSKY_D16.TXT b/HACKRF_PORTAPACK/SDCARD/FREQMAN/PERSONAL_FRSKY_D16.TXT new file mode 100644 index 0000000..682ef3f --- /dev/null +++ b/HACKRF_PORTAPACK/SDCARD/FREQMAN/PERSONAL_FRSKY_D16.TXT @@ -0,0 +1,42 @@ +# PortaPack Mayhem FREQMAN File +# FrSky D16 Protocol Template - FOR YOUR OWN DRONES ONLY +# WARNING: Transmitting to drones you don't own is ILLEGAL +# +# This template requires customization with YOUR drone's specific frequencies +# Follow the PERSONAL_RECALL_SETUP.md guide to capture your own signals +# +# FrSky D16 Specifications: +# - Frequency Range: 2400-2480 MHz (2.4 GHz ISM band) +# - Modulation: GFSK +# - Bandwidth: 1 MHz +# - 16 Channels with frequency hopping +# - User must capture their own frequency hopping sequence + +# TEMPLATE FREQUENCIES (MUST BE CUSTOMIZED) +# Replace these with YOUR drone's actual frequencies after capture +f=2405000000,m=AM,bw=1000000,d=FrSky D16 Ch1 [TEMPLATE] +f=2410000000,m=AM,bw=1000000,d=FrSky D16 Ch2 [TEMPLATE] +f=2415000000,m=AM,bw=1000000,d=FrSky D16 Ch3 [TEMPLATE] +f=2420000000,m=AM,bw=1000000,d=FrSky D16 Ch4 [TEMPLATE] +f=2425000000,m=AM,bw=1000000,d=FrSky D16 Ch5 [TEMPLATE] +f=2430000000,m=AM,bw=1000000,d=FrSky D16 Ch6 [TEMPLATE] +f=2435000000,m=AM,bw=1000000,d=FrSky D16 Ch7 [TEMPLATE] +f=2440000000,m=AM,bw=1000000,d=FrSky D16 Ch8 [TEMPLATE] +f=2445000000,m=AM,bw=1000000,d=FrSky D16 Ch9 [TEMPLATE] +f=2450000000,m=AM,bw=1000000,d=FrSky D16 Ch10 [TEMPLATE] +f=2455000000,m=AM,bw=1000000,d=FrSky D16 Ch11 [TEMPLATE] +f=2460000000,m=AM,bw=1000000,d=FrSky D16 Ch12 [TEMPLATE] +f=2465000000,m=AM,bw=1000000,d=FrSky D16 Ch13 [TEMPLATE] +f=2470000000,m=AM,bw=1000000,d=FrSky D16 Ch14 [TEMPLATE] +f=2475000000,m=AM,bw=1000000,d=FrSky D16 Ch15 [TEMPLATE] +f=2480000000,m=AM,bw=1000000,d=FrSky D16 Ch16 [TEMPLATE] + +# INSTRUCTIONS: +# 1. Power on YOUR FrSky D16 transmitter and drone +# 2. Use HackRF in receive mode to capture control signals +# 3. Identify your specific frequency hopping pattern +# 4. Replace the frequencies above with YOUR actual values +# 5. Capture and save your RTH (Return to Home) signal +# 6. Test in a safe, controlled environment +# +# See PERSONAL_RECALL_SETUP.md for detailed instructions diff --git a/HACKRF_PORTAPACK/SDCARD/REPLAYS/README_REPLAYS.TXT b/HACKRF_PORTAPACK/SDCARD/REPLAYS/README_REPLAYS.TXT new file mode 100644 index 0000000..77da3e5 --- /dev/null +++ b/HACKRF_PORTAPACK/SDCARD/REPLAYS/README_REPLAYS.TXT @@ -0,0 +1,139 @@ +# REPLAYS Directory +# Store replay-ready signals for YOUR OWN drones + +## Purpose +This directory stores processed signal files ready for replay transmission to YOUR OWN drones. + +## ⚠️ CRITICAL LEGAL WARNING ⚠️ +**TRANSMITTING TO DRONES YOU DON'T OWN IS ILLEGAL** + +This is not just unethical - it violates: +- FCC regulations (USA) +- Equivalent regulations in other countries +- Criminal laws against interference with aircraft +- Telecommunications laws + +Penalties can include: +- Heavy fines ($10,000+ per violation) +- Criminal charges +- Confiscation of equipment +- Imprisonment in severe cases + +## Legal Use +You may ONLY replay signals to: +✅ YOUR OWN drone that you personally own +✅ Drones you have explicit written permission to control +✅ In controlled test environments you have authorization for + +## Replay File Guidelines + +### File Naming +Use clear, descriptive names: +- `my_mavic_rth.c16` - DJI Mavic return to home +- `my_quad_land.c16` - Landing command +- `my_race_drone_disarm.c16` - Disarm command +- `emergency_recall.c16` - Emergency recall sequence + +### Required Documentation +Create a .txt file alongside each replay file with: +``` +Filename: my_mavic_rth.c16 +Drone: DJI Mavic 2 Pro (Serial: XXXXX) +Owner: [Your Name] +Frequency: 2450 MHz +Sample Rate: 2 MSPS +Purpose: Emergency return to home +Tested: Yes, 2023-12-25 +Safety Range: 500m max +Notes: Triggers RTH at current altitude +``` + +### Replay File Formats +- `.c16` - Complex 16-bit (most common) +- `.c8` - Complex 8-bit (smaller files) +- `.wav` - WAV format for compatible signals + +## Safety Checklist Before Replay + +Before transmitting ANY signal: +- [ ] Confirm this is YOUR drone +- [ ] Verify no other drones nearby +- [ ] Check you're in legal frequency band +- [ ] Ensure safe environment (open area, no people) +- [ ] Have line of sight to drone +- [ ] Weather is suitable for flight/recall +- [ ] Battery sufficient for recall operation +- [ ] Emergency landing area identified +- [ ] No restricted airspace +- [ ] Spotter present (recommended) + +## Testing Procedure + +1. **Bench Test First** + - Test with drone powered but props removed + - Verify correct response + - Start with minimal TX power + +2. **Safe Environment Test** + - Open field, no obstacles + - Tethered drone (if possible) + - Short range initially + - Gradually increase distance + +3. **Operational Use** + - Only after successful tests + - Always have backup control method + - Keep traditional controller ready + - Monitor drone behavior + +## PortaPack Replay Operation + +To replay a signal on PortaPack: +1. Go to Replay App +2. Select your replay file +3. Verify frequency and settings +4. Set appropriate TX gain (start low!) +5. Confirm safety checklist +6. Press to transmit +7. Monitor drone response + +## Troubleshooting + +**Replay doesn't work:** +- Verify capture quality (clean signal) +- Check frequency accuracy +- Ensure sufficient TX power (but stay legal!) +- Verify timing is correct +- Try recapturing signal + +**Unexpected behavior:** +- STOP immediately +- Use regular controller +- Land drone safely +- Review capture and settings +- May need to recapture with better parameters + +## Emergency Procedures + +If replay causes unexpected behavior: +1. STOP transmitting immediately +2. Switch to regular controller +3. Command immediate landing or hover +4. Clear the area +5. Do NOT attempt replay again until issue resolved + +## File Management + +- Keep only tested, working replays +- Delete failed attempts +- Update documentation regularly +- Back up working replays +- Note any changes to drone firmware/settings + +## Related Resources + +- PERSONAL_RECALL_SETUP.md - How to create replay files +- DETECTION_GUIDE.md - Understanding signals +- LEGAL.md - Complete legal information + +Remember: With great power comes great responsibility. Use this technology legally and ethically. diff --git a/HACKRF_PORTAPACK/SDCARD/SETTINGS/alert_settings.txt b/HACKRF_PORTAPACK/SDCARD/SETTINGS/alert_settings.txt new file mode 100644 index 0000000..e92d527 --- /dev/null +++ b/HACKRF_PORTAPACK/SDCARD/SETTINGS/alert_settings.txt @@ -0,0 +1,75 @@ +# Alert Configuration for Drone Detection +# Configure audio and visual alerts + +[Audio Alerts] +# Enable audio alerts +enabled=true + +# Alert tone frequency (Hz) +tone_frequency=1000 + +# Alert duration (ms) +alert_duration=200 + +# Alert volume (0-100) +volume=75 + +# Different tones for different bands +433mhz_tone=800 +915mhz_tone=1000 +1g2_tone=1200 +2g4_tone=1400 +5g8_tone=1600 +gps_tone=1800 + +[Visual Alerts] +# Enable LED/screen alerts +enabled=true + +# Alert color (red, green, blue, yellow, white) +alert_color=red + +# Blink rate (ms) +blink_rate=500 + +# Screen flash +screen_flash=true + +# Show frequency on alert +show_frequency=true + +[Alert Conditions] +# Minimum RSSI for alert (dBm) +min_rssi=-70 + +# Minimum signal duration (ms) +min_duration=100 + +# Alert cooldown period (seconds) +cooldown=2 + +# Alert on specific patterns +pattern_matching=false + +[Priority Alerts] +# High priority bands (immediate alert) +priority_bands=2g4,5g8 + +# Critical RSSI threshold (dBm) +critical_rssi=-50 + +# Continuous monitoring for priority +priority_continuous=true + +[Notification Types] +# Short beep for weak signals +weak_signal_beep=true + +# Long beep for strong signals +strong_signal_beep=true + +# Alarm for critical signals +critical_alarm=true + +# Voice alerts (if supported) +voice_alerts=false diff --git a/HACKRF_PORTAPACK/SDCARD/SETTINGS/drone_detect_config.txt b/HACKRF_PORTAPACK/SDCARD/SETTINGS/drone_detect_config.txt new file mode 100644 index 0000000..2e81df9 --- /dev/null +++ b/HACKRF_PORTAPACK/SDCARD/SETTINGS/drone_detect_config.txt @@ -0,0 +1,72 @@ +# HackRF PortaPack Drone Detection Configuration +# Configure these settings for optimal drone detection + +[Scanner Settings] +# Scan speed (ms per frequency) +scan_delay=50 + +# RSSI threshold for detection alert (dBm) +rssi_threshold=-70 + +# Audio alert on detection (true/false) +audio_alert=true + +# Visual alert on detection (true/false) +visual_alert=true + +# Log detected activity (true/false) +log_activity=true + +[Frequency Bands] +# Enable/disable specific bands +enable_433mhz=true +enable_915mhz=true +enable_1g2=true +enable_2g4=true +enable_5g8=true +enable_gps=true + +[Detection Sensitivity] +# Gain settings (0-47 dB for HackRF) +if_gain=40 +baseband_gain=32 +rf_gain=14 + +# Sample rate (Hz) +sample_rate=2000000 + +# FFT size for spectrum analysis +fft_size=256 + +[Display Settings] +# Update rate for RSSI display (Hz) +display_update_rate=10 + +# Show waterfall display +show_waterfall=true + +# Waterfall speed +waterfall_speed=medium + +[Battery Saving] +# Enable battery saver mode +battery_saver=false + +# Reduce scan when no activity (minutes) +idle_timeout=5 + +# Power off screen when idle +screen_timeout=true + +[Logging] +# Log file path +log_path=/SDCARD/CAPTURES/ + +# Log format (csv, txt, json) +log_format=csv + +# Include timestamp +timestamp=true + +# Include GPS coordinates if available +gps_logging=false diff --git a/HACKRF_PORTAPACK/SDCARD/SETTINGS/personal_recall_template.txt b/HACKRF_PORTAPACK/SDCARD/SETTINGS/personal_recall_template.txt new file mode 100644 index 0000000..daa12d3 --- /dev/null +++ b/HACKRF_PORTAPACK/SDCARD/SETTINGS/personal_recall_template.txt @@ -0,0 +1,100 @@ +# Personal Drone Recall Template Configuration +# WARNING: FOR YOUR OWN DRONES ONLY - Illegal for others' equipment + +[General Settings] +# Protocol type (frsky_d16, flysky, elrs, crossfire, custom) +protocol=custom + +# Center frequency (Hz) - MUST CUSTOMIZE +center_frequency=2450000000 + +# Frequency hopping (true/false) +frequency_hopping=false + +# Number of hopping channels +hop_channels=16 + +[Transmission Settings] +# Modulation type (AM, FM, GFSK, FSK, LoRa) +modulation=GFSK + +# Bandwidth (Hz) +bandwidth=1000000 + +# Sample rate (Hz) +sample_rate=2000000 + +# Transmit gain (0-47 dB) - VERIFY LEGAL LIMITS +tx_gain=0 + +# Transmit power (dBm) - VERIFY LEGAL LIMITS +tx_power=0 + +[RTH Command] +# Return to Home command file +rth_command_file= + +# Failsafe trigger file +failsafe_file= + +# Emergency stop file +emergency_file= + +[Safety Settings] +# Require confirmation before transmit +require_confirmation=true + +# Maximum transmission duration (ms) +max_tx_duration=1000 + +# Automatic timeout (seconds) +auto_timeout=10 + +# Safe mode (receive only) +safe_mode=true + +[Capture Settings] +# Capture path for signal recording +capture_path=/SDCARD/CAPTURES/ + +# Replay path for stored signals +replay_path=/SDCARD/REPLAYS/ + +# Auto-save captures +auto_save=true + +# Capture format +capture_format=complex16 + +[Testing Mode] +# Enable test mode (reduced power) +test_mode=true + +# Test frequency (away from actual drones) +test_frequency=2400000000 + +# Maximum test duration (seconds) +test_duration=5 + +[Protocol Specific - FrSky D16] +frsky_d16_hop_table= + +[Protocol Specific - FlySky] +flysky_id= + +[Protocol Specific - ELRS] +elrs_binding_phrase= +elrs_packet_rate=250 + +[Protocol Specific - Crossfire] +crossfire_band=915 +crossfire_power=10 + +# INSTRUCTIONS: +# 1. Choose your protocol +# 2. Capture YOUR drone's signals (see PERSONAL_RECALL_SETUP.md) +# 3. Configure frequencies and modulation +# 4. Save captured signals to REPLAYS directory +# 5. Test in safe environment with test_mode=true +# 6. Verify legal compliance before actual use +# 7. NEVER use on drones you don't own diff --git a/README.md b/README.md index 2be06d0..249c0d4 100644 --- a/README.md +++ b/README.md @@ -1,2 +1,180 @@ # ultimatel-ily -firmware + +Educational RF toolkit for drone detection and control systems. + +## Overview + +This repository contains educational resources and tools for understanding RF-based drone systems, including detection, monitoring, and personal drone control capabilities. + +## Repository Contents + +### 1. [HackRF PortaPack Package](HACKRF_PORTAPACK/) + +Comprehensive SD card package for **HackRF One with PortaPack H4M** providing: + +- **Drone Detection System** (Receive-Only - Always Legal) + - Multi-band frequency scanning (433 MHz to 5.8 GHz) + - Real-time RSSI monitoring and alerts + - Signal pattern identification + - Activity logging with timestamps + +- **Personal Drone Recall Framework** (YOUR Equipment ONLY) + - Template configurations for common protocols (FrSky, FlySky, ELRS, Crossfire) + - Signal capture and analysis tools + - Replay system for YOUR drone's control signals + - Safety-focused testing procedures + +**Features:** +- ✅ 100% legal passive detection capabilities +- ✅ Ready-to-use frequency scanner configurations +- ✅ Comprehensive documentation and guides +- ✅ Legal compliance information +- ✅ Safety procedures and best practices + +**Quick Links:** +- [Main README](HACKRF_PORTAPACK/README.md) - Complete overview and features +- [Quick Start Guide](HACKRF_PORTAPACK/QUICK_START.md) - 5-minute setup +- [Detection Guide](HACKRF_PORTAPACK/DETECTION_GUIDE.md) - Comprehensive detection instructions +- [Personal Recall Setup](HACKRF_PORTAPACK/PERSONAL_RECALL_SETUP.md) - For YOUR drones only +- [Legal Information](HACKRF_PORTAPACK/LEGAL.md) - Detailed legal compliance + +### 2. Firmware (Coming Soon) + +CC1101-based drone control firmware and related tools. + +## Hardware Platforms + +### HackRF One + PortaPack H4M +- **Frequency Range:** 1 MHz - 6 GHz +- **Use Case:** Wide-band detection, signal analysis, personal drone recall +- **License Required:** No (for receive); Check local regulations for transmit +- **Status:** Complete SD card package available + +### CC1101 (Planned) +- **Frequency Range:** 300 MHz - 928 MHz +- **Use Case:** Focused sub-GHz control and telemetry +- **Status:** Coming soon + +## Legal Notice + +### ⚠️ IMPORTANT LEGAL INFORMATION ⚠️ + +**LEGAL USES:** +- ✅ **Receiving/monitoring any frequency** (passive detection) - Always legal +- ✅ **Transmitting to YOUR OWN drones** - Legal when compliant with regulations +- ✅ **Educational and research purposes** - Within legal boundaries + +**ILLEGAL USES:** +- ❌ **Jamming or interfering with drones you don't own** - FEDERAL CRIME +- ❌ **Transmitting on unauthorized frequencies** - FCC violation +- ❌ **Controlling aircraft/drones you don't own** - Criminal offense + +**Penalties for illegal use:** Fines up to $10,000+ per violation, equipment seizure, criminal charges, possible imprisonment. + +**BY USING THIS REPOSITORY:** You agree you are solely responsible for legal compliance. The authors accept NO liability for misuse. + +For complete legal information, see [LEGAL.md](HACKRF_PORTAPACK/LEGAL.md). + +## Educational Purpose + +This project is designed for: +- **Learning** about RF systems and drone communications +- **Security awareness** and understanding drone activity +- **Personal use** with your own equipment +- **Research** into RF protocols and systems +- **Responsible development** of RF tools + +## Getting Started + +### For Drone Detection (HackRF) +1. Review [Quick Start Guide](HACKRF_PORTAPACK/QUICK_START.md) +2. Prepare SD card with package contents +3. Install in PortaPack H4M +4. Begin scanning for drone activity +5. Always legal - no transmission required! + +### For Personal Drone Recall (HackRF) +⚠️ **For YOUR equipment only** + +1. Read [Legal Information](HACKRF_PORTAPACK/LEGAL.md) completely +2. Follow [Personal Recall Setup](HACKRF_PORTAPACK/PERSONAL_RECALL_SETUP.md) +3. Capture YOUR drone's signals +4. Test extensively in safe environment +5. Verify legal compliance + +## Documentation + +Comprehensive documentation is provided for all features: +- Complete setup and installation guides +- Step-by-step tutorials +- Legal compliance information +- Safety procedures +- Troubleshooting guides +- Protocol-specific instructions + +See the [HACKRF_PORTAPACK directory](HACKRF_PORTAPACK/) for full documentation. + +## Safety + +- Always prioritize safety in RF operations +- Test in controlled environments +- Follow all safety procedures +- Have emergency procedures ready +- Use protective equipment when appropriate +- Respect battery safety (LiPo fires) + +## Community + +**Contributions Welcome!** +- Improvements to documentation +- Additional protocol support +- Bug fixes and enhancements +- Educational resources +- Legal compliance updates + +**Please ensure:** +- All contributions are legal and ethical +- Documentation is clear and accurate +- Safety warnings are prominent +- Code is well-tested + +## Support + +For issues, questions, or contributions: +- **GitHub Issues:** Report bugs or request features +- **Discussions:** Share ideas and ask questions +- **Pull Requests:** Contribute improvements + +## Credits + +- **HackRF One:** Great Scott Gadgets +- **PortaPack:** Jared Boone, Furrtek, Erwin Ried (Mayhem firmware) +- **Community:** Open source RF and drone communities +- **Contributors:** All who help improve this project + +## License + +This educational toolkit is provided as-is for legal use only. + +**Disclaimer:** Not responsible for misuse or illegal activity. Users are solely responsible for compliance with all applicable laws and regulations. + +## Version + +- **Repository Version:** 1.0.0 +- **HackRF Package Version:** 1.0.0 +- **Last Updated:** December 2024 + +--- + +## Quick Reference + +| Feature | Platform | Legality | Status | +|---------|----------|----------|--------| +| Drone Detection | HackRF | Always Legal ✅ | Available | +| Signal Analysis | HackRF | Always Legal ✅ | Available | +| Personal Recall | HackRF | Legal for YOUR equipment ⚠️ | Available | +| CC1101 Firmware | CC1101 | TBD | Coming Soon | + +--- + +**Remember: Detection is always legal. Transmission only to YOUR equipment. Stay legal, stay safe.** 📡🚁