diff --git a/en/fpv-openipc-alliance.md b/en/fpv-openipc-alliance.md index 92e09cc..851a9d9 100644 --- a/en/fpv-openipc-alliance.md +++ b/en/fpv-openipc-alliance.md @@ -4,21 +4,22 @@ OpenIPC Alliance for FPV ------------------------ -### Introduction +### OpenIPC Hardware Standardization for FPV -The OpenIPC team has decided to create an Alliance to promote and implement certain open circuit design standards for FPV system components. +#### 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. -On this page we will inform everyone about all members of the Alliance and report on changes and supplement links to projects. +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. -### Interface connector for the sensor - -The first component to be standardized will be the connector between the any OpenIPC AIO main board ("UltraSight", "Thinker", "Mario") and the any OpenIPC sensor module (IMX307, IMX335, IMX347, IMX415). - -We draw your attention to the fact that other modules of the other companies are **INCOMPATIBLE** and will definitely cause damage to your devices. +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.