mirror of https://github.com/OpenIPC/wiki.git
26 lines
1.7 KiB
Markdown
26 lines
1.7 KiB
Markdown
# OpenIPC Wiki
|
|
[Table of Content](../README.md)
|
|
|
|
OpenIPC Alliance for FPV
|
|
------------------------
|
|
|
|
### OpenIPC Hardware Standardization for FPV
|
|
|
|
#### Introduction
|
|
The OpenIPC team has established the OpenIPC Initiative to drive the standardization and unification of FPV hardware. This initiative aims to create open circuit design standards that enhance compatibility, improve interoperability, and support the broader adoption of MIPI-based solutions in the FPV ecosystem.
|
|
|
|
This page provides updates on Initiative members, reports on industry developments, and offers links to relevant projects and resources.
|
|
|
|
#### Standardized Sensor Interface Connector
|
|
The first major step toward FPV hardware standardization is defining a universal connector between OpenIPC AIO mainboards ("UltraSight," "Thinker," "Mario") and OpenIPC sensor modules (IMX307, IMX335, IMX347, IMX415). This unified approach ensures seamless integration and reliability across different components.
|
|
|
|
It is important to note that third-party sensor modules from other manufacturers are **not compatible** with OpenIPC hardware. Using non-standard components may result in hardware damage and system failure.
|
|
|
|
<p align="left">
|
|
<img src="https://github.com/OpenIPC/wiki/blob/master/images/fpv-openipc-alliance/openipc-alliance-fpv-sensor-pinout.jpg?raw=true"/>
|
|
</p>
|
|
|
|
**Standard Connector Type:** - **DF56L-26P-0.3SD**
|
|
|
|
By adopting and adhering to these FPV hardware standards, the OpenIPC Initiative fosters a more robust, reliable, and forward-thinking FPV ecosystem. Manufacturers who follow these standards can ensure full compatibility with OpenIPC hardware and benefit from community-driven support. However, we cannot guarantee support for devices that do not adhere to these specifications.
|