From f5dce6e9cf4d71829337b4c110a54d1f5b54cf7d Mon Sep 17 00:00:00 2001
From: wkumik <wkumik@gmail.com>
Date: Wed, 12 Feb 2025 11:46:52 +0100
Subject: [PATCH] Update and rename fpv-openipc-alliance.md to
OpenIPC-Hardware-Standarisation-for-FPV.md
renamed the title for better SEO and understanding.
Changed the text a bit for the same purpose.
---
en/OpenIPC-Hardware-Standarisation-for-FPV.md | 25 +++++++++++++++++++
en/fpv-openipc-alliance.md | 24 ------------------
2 files changed, 25 insertions(+), 24 deletions(-)
create mode 100644 en/OpenIPC-Hardware-Standarisation-for-FPV.md
delete mode 100644 en/fpv-openipc-alliance.md
diff --git a/en/OpenIPC-Hardware-Standarisation-for-FPV.md b/en/OpenIPC-Hardware-Standarisation-for-FPV.md
new file mode 100644
index 0000000..851a9d9
--- /dev/null
+++ b/en/OpenIPC-Hardware-Standarisation-for-FPV.md
@@ -0,0 +1,25 @@
+# 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.
diff --git a/en/fpv-openipc-alliance.md b/en/fpv-openipc-alliance.md
deleted file mode 100644
index 92e09cc..0000000
--- a/en/fpv-openipc-alliance.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# OpenIPC Wiki
-[Table of Content](../README.md)
-
-OpenIPC Alliance for FPV
-------------------------
-
-### Introduction
-
-The OpenIPC team has decided to create an Alliance to promote and implement certain open circuit design standards for FPV system components.
-
-On this page we will inform everyone about all members of the Alliance and report on changes and supplement links to projects.
-
-
-### 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.
-
-<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>
-
-Connector type - **DF56L-26P-0.3SD**