Runcam WifiLink v2 - OpenIPC more accessible than ever!

The State of Digital FPV Control Links

Closed Source Issues in FPV Technology

• The current digital FPV control links, such as those from DJI and Walknail, are criticized for being completely closed source and proprietary, limiting user modification and hardware compatibility.

• While HD0 offers some open-source components, it still retains closed-source elements. This partial openness is acknowledged but not sufficient for many users seeking full customization.

The Need for Open-Source Solutions

• Analog systems remain the only truly open-source option in FPV technology, allowing anyone to build their own video transmitters and receivers at a low cost despite their limitations in image quality and range.

• There is a call for an open-source digital FPV control link that could rival existing proprietary systems, similar to how Express LRS has impacted Crossfire.

Introduction to RunCam Wi-Fi Link V2

• The RunCam Wi-Fi Link V2 is introduced as an exciting product due to its open-source nature, running on either Open IPC or Ruby firmware.

• It aims to be user-friendly compared to previous products that required complex setups involving various hardware pieces and command-line operations.

Performance Expectations

• Initial skepticism about the performance of the RunCam Wi-Fi Link V2 is expressed; reviewers suggest it may not meet expectations as a reliable daily driver.

Overview of Video Receiver Features

• The video receiver can connect to goggles or ground stations via HDMI but does not include a display device itself.

• Users should be aware that the choice of display device significantly affects latency; this remains a challenge for Open IPC compared to DJI's offerings.

Antenna Considerations

• The included antennas with the device are noted as circular polarized while suggesting aftermarket directional antennas for better performance due to polarization matching requirements.

• A mix-up in antenna types shipped with the device raises concerns about optimal performance; users are encouraged to replace them with suitable options.

Power Supply and Connectivity Options

• The ground station includes a power cable compatible with XT60 connectors, allowing use of flight packs for power supply.

• An HDMI cable (mini-to-full size included), though users will likely need mini-to-mini cables for goggles since most have mini HDMI ports.

Build Quality Improvements

• Significant improvements in build quality from version 1 to version 2 of the transmitter are highlighted, addressing previous issues like poor assembly and placement of components.

Video Transmitter Overview

Design and Features

• The video transmitter features a professional design with a single board, an SD card slot, heat sinks, and a removable fan for cooling.

• It connects to the flight controller via a standard HD video transmitter port, eliminating the need for soldering.

• The included six-pin cable is standard for DJI transmitters; however, the yellow and black wires are not utilized in Open IPC setups.

Compatibility and Configuration

• The symmetrical pinout on both ends of the plug prevents damage from incorrect connections, unlike previous models.

• A long 13-inch cable is provided, which may be excessive for most applications; shorter alternatives could improve usability.

• An RJ45 port allows Ethernet connection to configure settings through terminal access; this may be confusing for non-tech users.

Performance Specifications

• Equipped with an IMX 415 sensor, it supports output resolutions of up to 1080p at 90 frames per second or 720p at 120 frames per second.

• Operates within a voltage range of 9 to 22 volts; caution against using higher voltages like 6S battery voltage is advised.

Mounting and Antenna Setup

• Designed with mounting lugs compatible with various frame types; double-sided tape can also be used if necessary.

• Antennas are shipped uninstalled; proper installation requires securing them with retention bars to prevent disconnection during use.

Moment of Truth: Testing the Video Transmitter

Initial Setup and Booting

• The video transmitter is connected to a flight controller powered by alligator clips, indicating it’s not yet installed in a quadcopter.

• Upon powering up, the system begins booting, displaying some Linux command line output before successfully establishing a signal.

• The OSD (On-Screen Display) functions correctly, showing battery status and confirming that the digital OSD works without additional plugins.

Ruby FPV vs. Open IPC

• A comparison between Ruby FPV and Open IPC reveals that Ruby FPV is more user-friendly and intuitive for users.

• The initial confusion arose from receiving pre-release hardware with Open IPC instead of Ruby FPV; this highlights the importance of clarity in product specifications.

• Users can easily navigate menus in Ruby FPV to adjust settings like radio links, contrasting with Open IPC's manual setup requirements.

User Experience Insights

• While acknowledging that Open IPC has numerous plugins, the speaker emphasizes their lack of knowledge about them compared to the straightforward interface of Ruby FPV.

• The ease of use in Ruby FPV allows users to troubleshoot issues through its menu system rather than resorting to complex command-line inputs.

Camera and Video Transmitter Mounting

• Discussion on mounting techniques shows practical challenges faced when integrating components into a quadcopter frame.

• The video transmitter is mounted using double-sided tape due to mismatched mounting hole sizes; this raises concerns about stability during flight.

Concerns About Design Features

• Placement of the receiver under the video transmitter poses risks during crashes; typically, it would be mounted above but is hindered by a fan design.

• There are rumors regarding overheating issues with video transmitters if output power is increased; caution is advised based on anecdotal evidence.

Quality Components Used

• High-quality aftermarket UFL pigtails are used for connections to SMA connectors and antennas, emphasizing performance enhancement through better materials.

Final Thoughts Before Flight Test

• Transitioning into future segments where flying tests will occur indicates anticipation for performance evaluation after thorough setup discussions.

Support the Creator How to Support My Work

Patreon Subscription

• The creator encourages viewers to support their work through Patreon, suggesting that even a small contribution of $2 a month can be valuable.

• Viewers are invited to subscribe at any amount they feel reflects the value they receive from the content. If they prefer to continue watching without subscribing, that's also acceptable.

• A link to the Patreon page is provided in the video description for those interested in supporting.

Open IPC and Ruby FPV Performance Testing Preparing for Flight

Initial Setup and Challenges

• The creator expresses anticipation about testing Open IPC performance but acknowledges potential scrutiny regarding results.

• Previous tests were unsuccessful, prompting the creator to seek help on the Open IPC Ruby FPV Runcam Telegram channel for troubleshooting advice.

Software Updates

• The current test uses Ruby 11.1, which is recommended over the default Ruby 10.8 shipped by Runcam for better performance.

• A tutorial on flashing hardware to Ruby 11.1 will be linked in the video description due to its complexity.

Configuration Settings Optimizing Video Settings

Vehicle and Video Configuration

• It's crucial that vehicle settings are correctly configured; specifically, ensuring that board type is set to Runcam V2 instead of Mario AIO.

• The creator emphasizes enabling bidirectional adaptive video link for improved range and reliability while acknowledging trade-offs with latency.

OSD Settings and Performance Monitoring

• Users have options between bidirectional mode (better penetration but variable latency) and one-way broadcast mode (lower consistent latency).

• Enabling specific OSD stats helps monitor radio performance; minimal red indicators signify good conditions while excessive red indicates issues.

Final Thoughts on Performance Metrics

• The importance of monitoring environmental noise levels is highlighted as it directly affects performance; users should aim for optimal green/white readings in their stats.

FPV Video Quality and System Performance

Overview of Video Transmission Settings

• The video transmission is set to a power level of 300 m, which is close to the maximum output for the Run Cam video transmitter. This is notably lower than DJI's typical output of 1.2 watts.

Comparison of Output Power Reporting

• Unlike DJI and Walknail, which report output power including antenna gain (e.g., 5dB), Open IPC provides a more straightforward measurement by reporting actual output power into the antenna.

Adaptive Link Metrics

• The HQ metric displayed in the upper right corner indicates video quality; maintaining this at HQ is crucial as drops to LQ or MQ signify deteriorating video quality.

Latency Observations

• The latency advertised by RunCam ranges from 50 to 80 milliseconds, significantly higher than competitors like DJI and Walknail (25-45 ms), with analog systems achieving even lower latencies around 15 ms.

Flight Experience and Link Stability

• Initial hopes are cautiously optimistic based on previous attempts that were unsuccessful. The pilot notes that link stability fluctuates during flight, particularly when flying behind obstacles.

Challenges with Signal Recovery

Issues Encountered During Flight

• When flying behind structures like houses or trees, signal recovery was slow; switching to angle mode did not help regain the link quickly after it was lost.

Directionality Sensitivity

• The directional antennas used show high sensitivity; there are considerations about switching to omni antennas despite potential reduced range due to their broader coverage capabilities.

Performance Evaluation of Open IPC

User Experience with Antenna Types

• Switching to omni antennas resulted in noticeable performance degradation, leading to stuttery video feed and difficulty in maintaining orientation during flight.

Aspirations for Open IPC Development

• There’s a strong desire for Open IPC to meet user expectations similar to Express LRS, which has become a leading control link due to its reliability from inception.

Comparative Analysis: Open IPC vs. Express LRS

Fundamental Differences in Development

• While Express LRS started as an effective control link that evolved into user-friendliness, Open IPC still struggles with fundamental performance issues before it can be considered reliable for daily use.

User Interface Considerations

• Ruby FPV offers an intuitive interface that simplifies configuration compared to other firmware options available for Open IPC hardware, making it accessible for users who may not be technically inclined.

Current State of Experimental Technology

Performance Readiness Assessment

• Despite significant advancements made by Runcam and Ruby FPV towards usability and functionality, the overall system remains experimental rather than ready for mainstream adoption.

RunCam Wi-Fi Link Hardware Review

Overview of RunCam Wi-Fi Link Hardware

• The RunCam Wi-Fi Link hardware is compact, easy to mount on goggles, and user-friendly without the need for 3D printing or extensive setup.

• The RunCam VTX air unit is described as a well-made, production-quality piece of equipment.

Performance Concerns

• Despite its appealing design, there are doubts about recommending this hardware due to performance issues compared to the Open IPC system.

• Observations indicate that all channels exhibit noise, raising concerns about the overall quality of the hardware rather than environmental factors.

Comparison with DIY Solutions

• DIY hardware solutions appear cleaner in terms of signal quality when compared to RunCam's offerings, suggesting potential flaws in the commercial product.

• For enthusiasts wanting to experiment with their setups, building a custom solution (like using Ratica and a Wi-Fi adapter) may be more rewarding than relying on current RunCam products.

Future Potential and Recommendations

• There is hope for future iterations of RunCam products to improve significantly; however, current versions do not meet daily usability standards yet.

• A tutorial will be provided for flashing firmware onto the device since standard methods have been disabled by RunCam. This could enhance functionality but requires additional effort from users.