OpenIPC, the cheapest digital long-range FPV system in the world

Sparkyws · 12 December 2023 16:21

Introducing OpenIPC, the cheapest digital long-range FPV system in the world

https://openipc.org/

Sparkyws · 12 December 2023 16:54

Sparkyws · 13 December 2023 13:26

Just a note that OpenIPC is not just for installing an IP camera as an FPV camera

It maybe useful to anyone that wants to hack ip security cameras with a open source firmware

Why OpenIPC Firmware?

First of all, OpenIPC Firmware brings you freedom. With OpenIPC on your camera you are the master of your streams. You have full access to the system and can control what, where, and how you want your camera to behave. There are no backdoors, no botnets, no crypto-mining malware, no keyloggers, no password sniffers, nothing you could possibly expect in a closed binary system with no access to its source code.

As for the Firmware capabilities, we strive to provide universal support for a wide range of cameras, thus we are focused on basic functionality first, allowing end-users to upgrade their cameras’ firmware and stream video and audio (where supported) without too much hassle.

We have some interesting bits though. Our Firmware supports external IPEYE cloud storage, streaming video to Youtube and Telegram, using SOCKS5 proxy, setting up a Virtual Tunnel, and more.

There are also several projects focused on specialized equipment, such as a camera to be mounted on a drone, for mounting on construction helmets, for use in surveying tools, for medical research of the organs of vision, underwater fishing, etc.

Sparkyws · 17 December 2023 18:40

github.com

OpenIPC/wiki/blob/master/en/fpv.md

# OpenIPC Wiki
[Table of Content](../README.md)

Using OpenIPC as a budget video link for FPV system
---------------------------------------------------

<p align="center">
  <img src="https://github.com/OpenIPC/wiki/blob/master/images/fpv-logo.jpg?raw=true" alt="Logo"/>
</p>

In 2015, German enthusiast Befi [pitched the idea of an OpenSource drone](https://befinitiv.wordpress.com/wifibroadcast-analog-like-transmission-of-live-video-data/), where he proposed to use ordinary WiFi adapters, the number of which has already reached several billion pieces worldwide, and the price has dropped so much that they have become the most affordable types of digital transceivers.

The key idea was not the WiFi adapters themselves, but an unconventional method of using them: refusing to establish a network connection and switching to broadcast mode, when one adapter acts as a transmitter of a digital signal, while the second one is a receiver.

It was suggested to take a budget SBC Raspberry Pi, connect a camera to it via MIPI interface and a USB WiFi dongle from among the recommended ones, and on the other side on the receiver - a similar WiFi module with HDMI monitor. In this case, instead of the traditional UDP protocol for low-latency video transmission, a lower-level protocol was used for flexible data management: bandwidth control, transmitter power, and the ability to recover data if the packet was [partially corrupted](https://en.wikipedia.org/wiki/Error_detection_and_correction) during transmission. One of the technical problems is that not every WiFi adapter is able to work in this low-level mode, moreover: you almost always have to install special drivers that exist only for Linux.

The receiver in this mode operates in the so-called `monitor mode`, where it receives and transmits to the operating system each packet of a given WiFi channel, where it decides whether to decode or discard it. The WiFi transmitter adapter must operate in `injection mode`, where the operating system kernel does not actually participate in the network packet generation prescribed by the ISO network model. Some adapters support both modes, some support only some one, so may only stand on the transmitter or receiver side.

<p align="center">
  <img src="https://befinitiv.files.wordpress.com/2015/04/dscf11161.jpg" alt="The first ever drone controlled by Wifibroadcast" />

This file has been truncated. show original

Nidge · 18 December 2023 09:48

I have a “drone” being delivered later this week which might have a lot of the requirements for OpenIPC already installed, or configured to run on it. It’s certainly not a subject for the faint of heart and I may have to tailor back my medication to reach the required cognitive level.

Yith · 18 December 2023 11:45

It looks really interesting… I have considered looking into trying it myself… but why bother when I already have HDZero and Walksnail!

If I was stuck on analog I’d certainly be trying it out as I do love to tinker, but I just don’t have the time what with all the other stuff I have going on…

It’ll be very interesting to hear/see how you get on!

What “drone” is it you’ve got coming?

Nidge · 18 December 2023 11:57

Time isn’t too much of an issue for me. For instance I’m currently sat here on the sofa playing “Jetwash Simulator” of all things on the PS5. Being in the right mindset to see a project to full fruition is another matter.

The drone is the Intel Aero Drone. Essentially it’s a full blown Unix PC that flys, originally produced for SUAS developers.

bmsleight · 2 January 2024 19:42

I’ve order a compatible camera. Anything where you have to use u-boot and ssh has got to be fun.
￡21.62 2.8mm lens, 12v cable.

I think old laptop can be used a ground station like OpenHD. Latency is claimed better.

in our Glass-to-Glass tests, we got about 80ms latency for 1080p@60 (on mid-budget cameras), and about 60 ms for 720p@60 and about 100 ms for 1080p@30 (for the most budget cameras)

Sparkyws · 2 January 2024 21:02

github.com

CurryKitten/wiki/blob/master/en/A-step-by-step-guide-for-an-FPV-setup.md

# A step-by-step installation guide for an FPV setup

When considering installing OpenIPC for FPV use, we can basically break the process down into 6 key steps.

1. Flashing the Camera and groundstation with OpenIPC
2. Connecting additional hardware (wifi adapters and BECS)
3. Generating and installing the key pairing for WFB-NG
4. Editing wfb.conf to set the correct wifi channel
5. Configuring vdec.conf on the groundstation
6. Configuring the majestic.yaml file on the camera
7. Testing out the configuration
8. Video tutorial and next steps

Parts 1 and 2 covers the setup of the hardware - although there are many substeps involved, so you can consider this the "hard bit".  Although the software side of things (steps 3 - 6) has more steps, it's essentially editing some files and thus we can consider that the "easy bit"

### Hardware Requirements
For this step-by-step guide, I'm using specific hardware, and although the procedure to flash cameras and groundstations are broadly the same, each one can be quite different in terms of the UART connection you can use, as well as the chip set and memory being different - so make sure you check this carefully for your devices.  On a basic level, you'll need a groundsation, a camera, 2 wifi adapters, up to 4 UBECS and an FTDI board.

As a reference for my camera, I ordered an SSC338 based board with a Sony IMX415 sensor.

This file has been truncated. show original

Sparkyws · 2 January 2024 21:15