2 |
3 |
4 |
5 |
--------------------------------------------------------------------------------
/wiki/index.md:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
--------------------------------------------------------------------------------
/wiki/ru/index.md:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
--------------------------------------------------------------------------------
/wiki/ru/hardware-hs303.md:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
--------------------------------------------------------------------------------
/backers.md:
--------------------------------------------------------------------------------
1 | ![OpenIPC logo][logo]
2 |
3 | ## OpenCollective backers
4 |
5 | [](https://opencollective.com/openipc#support)
6 |
7 |
8 | [logo]: https://openipc.org/assets/openipc-logo-black.svg
9 |
--------------------------------------------------------------------------------
/explanations.md:
--------------------------------------------------------------------------------
1 | ![OpenIPC logo][logo]
2 |
3 | ## List of explained abbreviations
4 |
5 | [][telegram]
6 |
7 |
8 | ### OpenIPC Bureau
9 |
10 | "OpenIPC Bureau" is a group of individuals (developers) and friendly teams under the umbrella of our community,
11 | working on integrating firmware for devices from various manufacturers and providing basic consultations and training.
12 |
13 | This work isn't commercial, but to speed things up, encourage people, and boost enthusiasm, it can be supported
14 | through donations via the [OpenCollective][opencollective] platform.
15 |
16 |
17 | [logo]: https://openipc.org/assets/openipc-logo-black.svg
18 | [opencollective]: https://opencollective.com/openipc
19 | [telegram]: https://openipc.org/our-channels
20 |
--------------------------------------------------------------------------------
/LICENSE.md:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2019-2025 OpenIPC
4 |
5 | Permission is hereby granted, free of charge, to any person obtaining a copy
6 | of this software and associated documentation files (the "Software"), to deal
7 | in the Software without restriction, including without limitation the rights
8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 | copies of the Software, and to permit persons to whom the Software is
10 | furnished to do so, subject to the following conditions:
11 |
12 | The above copyright notice and this permission notice shall be included in all
13 | copies or substantial portions of the Software.
14 |
15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21 | SOFTWARE.
22 |
--------------------------------------------------------------------------------
/store.md:
--------------------------------------------------------------------------------
1 | ![OpenIPC logo][logo]
2 |
3 | ## Alternative open firmware for your IP camera
4 | _(based on Buildroot)_
5 |
6 | [][telegram]
7 |
8 | ### Important
9 |
10 | This table will show orders placed in the [OpenIPC store](https://store.openipc.org) that have some problems.
11 | If your order is not here, you can rest assured for now.
12 | We take a very responsible approach to the delivery of all orders.
13 | The result is always delivery to the customer or a refund to the customer's card.
14 | However, there are intermediate situations, for example, when the goods are delayed at customs.
15 | In this case, we are powerless for some time (sometimes it is significant) and call on everyone to remain calm and wait for the situation to be resolved.
16 | Thank you for your understanding.
17 |
18 | ### Statuses
19 |
20 | **Last updated - 2024.12.09**
21 |
22 | | Order | Country | Existing problem | Current status | Actions taken or expected |
23 | |:-----:|:-------:|-------------------------|------------------------------------|----------------------------------------------------------|
24 | | | | | | |
25 | | XYZ | PG | The parcel was lost by the postal service or customs | | Re-send SSC338Q+IMX415 (1) |
26 |
27 | [logo]: https://openipc.org/assets/openipc-logo-black.svg
28 | [telegram]: https://openipc.org/our-channels
29 |
--------------------------------------------------------------------------------
/review2024.md:
--------------------------------------------------------------------------------
1 | ![OpenIPC logo][logo]
2 |
3 | ## Alternative open firmware for your IP camera
4 | _(based on Buildroot)_
5 |
6 | [][telegram]
7 |
8 | ### A 2024 Year of Innovation
9 |
10 | Welcome to a special edition highlighting the most impactful developments within the OpenIPC project over the past year.
11 | The community's dedication has driven significant progress, and we're excited to share these achievements with you.
12 |
13 | #### Key Developments in FPV section
14 |
15 | - AIO Devices Take Flight: OpenIPC led the charge in bringing All-In-One (AIO) devices to the forefront. Our team was the first to release AIO devices based on OpenIPC firmware, setting the trend for others.
16 | - MSPOSD Enhanced with VTX Menu: The Mario unit's base firmware now supports the latest MSPOSD, complete with a VTX menu. Updates are ongoing, and the new vtxmenu.ini is already in the configurator.
17 | - OpenIPC Ruby Emerges: A single developer's hard work brought OpenIPC Ruby to life.
18 | - mavfwd Gets an Upgrade: The updated mavfwd improves performance, fixing 1080p 120fps on the IMX335. AIO firmware users should update, and experimenting with "-a 15" could reduce traffic further.
19 | - Configurator Refined: A new "read camera settings" button simplifies setup. The configurator is a major reason 60% of users have switched to OpenIPC.
20 | - Strategic Partnerships: OpenIPC is gaining recognition! RunCam, Emax, and BetaFPV are now collaborating with OpenIPC, with new product launches in the works.
21 | - OpenHD Reconciliation: Prior misunderstandings with OpenHD have been resolved, paving the way for future collaboration.
22 | - Telemetry Port Update: Default telemetry ports have changed: 14750 for Venc builds, 14550 for external use on NVR. Update older firmware accordingly.
23 | - 40MHz Mode on the Horizon: The community is eager for PixelPilot to adopt 40MHz mode.
24 | - High Frame Rate Achieved: Radxa Zero 3W can now display 120fps.
25 | - Zoom Bash Script Integration: A zoom script with 30 levels and focus set to infinity is now part of the firmware.
26 |
27 |
28 | [logo]: https://openipc.org/assets/openipc-logo-black.svg
29 | [telegram]: https://openipc.org/our-channels
30 |
--------------------------------------------------------------------------------
/readme.md:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 | ## Alternative open firmware for your IP camera
8 | _(based on Buildroot)_
9 |
10 | [][telegram]
11 |
12 | ### Introduction
13 |
14 | OpenIPC is an open source operating system from the [open community][opencollective]
15 | targeting for IP cameras with ARM and MIPS processors from several manufacturers in
16 | order to replace that closed, opaque, insecure, often abandoned and unsupported
17 | firmware pre-installed by a vendor.
18 |
19 | OpenIPC [firmware][firmware] comes as binary pre-compiled files for easy
20 | installation by end-user. Also, we provide full access to the source files for
21 | further development and improvement by any capable programmer willing to
22 | contribute to the project. OpenIPC source code is released under one of the most
23 | simple open source license agreements, [MIT License][mit], giving users express
24 | permission to reuse code for any purpose, even as part of a proprietary software.
25 | We only ask you politely to contribute your improvements back to us and also be
26 | sure to contact us if you use our project for [commercial purposes][price]. We would
27 | be grateful for any feedback and suggestions. The use of the OpenIPC project and its
28 | components for military purposes is not permitted.
29 |
30 | Historically, OpenIPC [firmware][firmware] only supported SoC manufactured by
31 | HiSilicon, but as the development continues, the list of supported processors
32 | expands. Today, it also includes chips from _Ambarella_, _Anyka_, _Fullhan_, _Goke_,
33 | _GrainMedia_, _Ingenic_, _MStar_, _Novatek_, _SigmaStar_, _XiongMai_, and is
34 | expected to grow further.
35 |
36 | More information about the [project][project] is available in our [website][website]
37 | and on the [wiki][wiki].
38 |
39 |
40 |
41 |
42 |
43 | [price]: https://openipc.org/support-open-source
44 | [firmware]: https://github.com/openipc/firmware
45 | [logo]: https://openipc.org/assets/openipc-logo-black.svg
46 | [mit]: https://opensource.org/license/mit
47 | [opencollective]: https://opencollective.com/openipc
48 | [paypal]: https://www.paypal.com/donate/?hosted_button_id=C6F7UJLA58MBS
49 | [project]: https://github.com/openipc
50 | [telegram]: https://openipc.org/our-channels
51 | [website]: https://openipc.org
52 | [wiki]: https://github.com/openipc/wiki
53 |
--------------------------------------------------------------------------------
/fpv-faq.md:
--------------------------------------------------------------------------------
1 | ![OpenIPC logo][logo]
2 |
3 | ## Alternative open firmware for your IP camera
4 | _(based on Buildroot)_
5 |
6 | [][telegram]
7 |
8 | ### Table of contents
9 |
10 | - [Installing the calibration file for SSC338Q/SSC30KQ devices](#installing-the-calibration-file-for-ssc338qssc30kq-devices)
11 | - [Updating the device firmware from the SD card](#updating-the-device-firmware-from-the-sd-card)
12 |
13 |
14 | ### Installing the calibration file for SSC338Q/SSC30KQ devices
15 |
16 | - Take an SD card, delete all partitions on it, create one partition of 1 Gigabyte and format it as FAT32/VFAT.
17 | - Go to the OpenIPC repository [sensor-profiles](https://github.com/OpenIPC/sensor-profiles/) and download the file you need, for example [imx335_greg15.bin](https://github.com/OpenIPC/sensor-profiles/raw/master/files/imx335_greg15.bin).
18 | - Create a file named autoconfig.sh in Notepad++ for Windows or text editor in Linux with the following content:( dont forget to change the bin file name if youre using a different one from the example above)
19 | ```
20 | #!/bin/sh
21 | cp /mnt/mmcblk0p1/imx335_greg15.bin /etc/sensors/imx335_greg15.bin
22 | cli -s .isp.sensorConfig /etc/sensors/imx335_greg15.bin
23 | rm /mnt/mmcblk0p1/imx335_greg15.bin
24 | ```
25 | - Place both files on the SD card and insert it into the device.
26 | - If you did everything correctly, the system will see the SD card, write the calibration file and configure Majestic.
27 | - Reboot your device and enjoy.
28 | - You can thank the project via [OpenCollective](https://opencollective.com/openipc#category-CONTRIBUTE).
29 |
30 |
31 | ### Updating the device firmware from the SD card
32 |
33 | - Take an SD card, delete all partitions on it, create one partition of 1 Gigabyte and format it as FAT32/VFAT.
34 | - Go to the OpenIPC repository [Builder](https://github.com/OpenIPC/builder/) and download the firmware you need, for example [mario-aio](https://github.com/OpenIPC/builder/releases/download/latest/ssc338q_fpv_openipc-mario-aio-nor.tgz).
35 | - Unzip the archive and extract two files from it - rootfs.squashfs.ssc338 and uImage.ssc338q.
36 | - Download a [file](https://github.com/OpenIPC/firmware/raw/master/general/scripts/boot.scr) with commands for the bootloader, which will perform an automatic update firmware.
37 | - Place the three files on the SD card and insert it into the device and reboot it.
38 | - If you did everything correctly, you will be able to see in UART how U-Boot will start updating the firmware when it starts.
39 | - You can thank the project via [OpenCollective](https://opencollective.com/openipc#category-CONTRIBUTE).
40 |
41 |
42 |
43 |
44 |
45 |
46 | [firmware]: https://github.com/openipc/firmware
47 | [logo]: https://openipc.org/assets/openipc-logo-black.svg
48 | [mit]: https://opensource.org/license/mit
49 | [opencollective]: https://opencollective.com/openipc
50 | [paypal]: https://www.paypal.com/donate/?hosted_button_id=C6F7UJLA58MBS
51 | [project]: https://github.com/openipc
52 | [telegram]: https://openipc.org/our-channels
53 | [website]: https://openipc.org
54 | [wiki]: https://github.com/openipc/wiki
55 |
--------------------------------------------------------------------------------
/fpv-vendors.md:
--------------------------------------------------------------------------------
1 | ![OpenIPC logo][logo]
2 |
3 | ## Alternative open firmware for your IP camera
4 | _(based on Buildroot)_
5 |
6 | [][telegram]
7 |
8 | ### Description
9 |
10 | This table aims to promote the unification of standards between different vendors in the FPV community. By standardizing MIPI compatibility across various devices, manufacturers can enhance interoperability, streamline development, and improve the overall user experience. OpenIPC encourages vendors to align with open standards, ensuring better compatibility and support for the FPV ecosystem.
11 |
12 |
13 | ### List of OpenIPC FPV supported devices
14 |
15 | | Device name | Vendor | Processor | Sensor(s) | MIPI compatibility | WiFi |
16 | |:------------------------------|:---------:|:---------:|:----------------:|:------------------:|:----------------------------:|
17 | |[AIO Evolution v1.0](#) | [OpenIPC](https://openipc.org) | SSC338Q | IMX335 | openIPC | RTL8812AU |
18 | |[AIO Thinker Base v1.0](#) | [OpenIPC](https://openipc.org) | SSC338Q | IMX335 | openIPC | for external USB device |
19 | |[AIO Thinker Tiny v1.0](#) | [OpenIPC](https://openipc.org) | SSC338Q | IMX335 | openIPC | RTL8731BU |
20 | |[AIO Mario v1.0](#) | [OpenIPC](https://openipc.org) | SSC338Q | IMX335, (IMX415) | openIPC | |
21 | |[AIO Optimus v1.0](#) | [OpenIPC](https://openipc.org) | SSC338Q | IMX415 | openIPC | |
22 | |[AIO UltraSight v1.0](#) | [OpenIPC](https://openipc.org) | SSC338Q | IMX415 | openIPC | |
23 | | | | | | | |
24 | |[one](#) | [RunCam](https://www.runcam.com/) | SSC338Q | IMX ? | proprietary | |
25 | |[two](#) | [RunCam](https://www.runcam.com/) | SSC338Q | IMX ? | proprietary | |
26 | | | | | | | |
27 | |[one](#) | [Emax USA](https://emax-usa.com/) | SSC338Q | IMX ? | proprietary | |
28 | |[two](#) | [Emax USA](https://emax-usa.com/) | SSC338Q | IMX ? | proprietary | |
29 | | | | | | | |
30 | |[CrazyCat R2](#) | PocketFPV | SSC338Q | IMX ? | not compatible | |
31 | |[BigRookie R1](#) | PocketFPV | SSC338Q | IMX ? | not compatible | |
32 | | | | | | | |
33 | |[OIPC S338](#) | ElfinRC | SSC338Q | IMX ? | not compatible | |
34 | |[Mini IPC](https://www.youtube.com/watch?v=eQ_vbyScS4c) | ElfinRC | SSC338Q | IMX415 | not compatible | |
35 |
36 |
37 | [logo]: https://openipc.org/assets/openipc-logo-black.svg
38 | [telegram]: https://openipc.org/our-channels
39 |
--------------------------------------------------------------------------------
/fpv-basic.md:
--------------------------------------------------------------------------------
1 | ![OpenIPC logo][logo]
2 |
3 | # Alternative open firmware for your IP camera
4 | _(based on Buildroot)_
5 |
6 | [][telegram]
7 |
8 | ## Table of contents
9 |
10 | - [OpenIPC FPV Experts Administrative Board](#openipc-fpv-experts-administrative-board)
11 | - [Enthusiasts who offer their help](#enthusiasts-who-offer-their-help)
12 | - [List of OpenIPC repositories used in FPV](#list-of-openipc-repositories-used-in-fpv)
13 | - [List of OpenIPC FPV supported devices](#list-of-openipc-fpv-supported-devices)
14 |
15 |
16 | ## OpenIPC FPV Experts Administrative Board
17 |
18 | - Greg (cool flights and new features testing/experimentation)
19 | - Eduardo (technical support and documentation)
20 | - Joakim [steam-groundstations](https://github.com/OpenIPC/steam-groundstations)
21 | - Marios | [configurator](https://github.com/OpenIPC/configurator) | [telegram](https://t.me/Mario_FPV), [youtube](https://www.youtube.com/@mariofpv)
22 | - Mike Carr | [improver](https://github.com/OpenIPC/improver) | [telegram](https://t.me/mikecarr)
23 | - Petru Soroaga [rubyfpv](https://rubyfpv.com) [telegram](https://t.me/PetruSoroaga)
24 | - @Sakalva (sensors)
25 | - Tipo Man | [msposd](https://github.com/OpenIPC/msposd) | [github](https://github.com/tipoman9), [telegram](https://t.me/tipoman), [youtube](https://www.youtube.com/@tipoman9317)
26 | - CC zhouruixi |
27 |
28 |
29 | ## Enthusiasts who offer their help
30 |
31 | - Wojciech (good with websites, photoshop and graphic design)
32 | - Ron Zika (like to make infographic's)
33 |
34 |
35 | ## List of OpenIPC repositories used in FPV
36 |
37 | - [firmware](https://github.com/OpenIPC/firmware)
38 | - [builder](https://github.com/OpenIPC/builder)
39 | - [pixelpilot](https://github.com/OpenIPC/pixelpilot) ( OpenIPC android ground station app)
40 | - [fpv4win](https://github.com/OpenIPC/fpv4win)
41 | - [sbc-groundstations](https://github.com/OpenIPC/sbc-groundstations) ( pre-built image for sbc groundstations such as the radxa zero 3 or orange pi 5)
42 | - [configurator](https://github.com/OpenIPC/configurator) (toool to simplify the setup for openipc cameras and ground stations)
43 | - [improver](https://github.com/OpenIPC/improver)
44 | - [wfb-ng-openwrt](https://github.com/OpenIPC/wfb-ng-openwrt)
45 | - [devourer](https://github.com/OpenIPC/devourer) ( android user space driver for rtl8812 chipset based WiFi modules)
46 | - [mavfwd](https://github.com/OpenIPC/mavfwd)
47 | - [msposd](https://github.com/OpenIPC/msposd) - [issues](https://github.com/OpenIPC/msposd/issues), [roadmap](https://github.com/orgs/OpenIPC/projects/16/views/1)
48 | - [pyosd](https://github.com/OpenIPC/pyosd)
49 | - [pixelpilot_rk](https://github.com/OpenIPC/pixelpilot_rk) ( radxa zero 3 and ofher rk chip based decoder and video pipeline)
50 | - [steam-groundstations](https://github.com/OpenIPC/steam-groundstations)
51 | - [sensor-profiles](https://github.com/OpenIPC/sensor-profiles)
52 | - [silicon_research](https://github.com/OpenIPC/silicon_research)
53 | - [urllc-webui](https://github.com/OpenIPC/urllc-webui)
54 |
55 |
56 | | Repository | Issues | Roadmap | Curators |
57 | |:----------------------------------------------------------------------:|:-------------------------------------------------:|:-------------------------------------------------------------:|:------------------------------:|
58 | |[firmware](https://github.com/OpenIPC/firmware) |
59 | |[builder](https://github.com/OpenIPC/builder) |
60 | |[pixelpilot](https://github.com/OpenIPC/pixelpilot) |
61 | |[fpv4win](https://github.com/OpenIPC/fpv4win) |
62 | |[sbc-groundstations](https://github.com/OpenIPC/sbc-groundstations) |
63 | |[configurator](https://github.com/OpenIPC/configurator) |
64 | |[improver](https://github.com/OpenIPC/improver) |
65 | |[wfb-ng-openwrt](https://github.com/OpenIPC/wfb-ng-openwrt) |
66 | |[devourer](https://github.com/OpenIPC/devourer) |
67 | |[mavfwd](https://github.com/OpenIPC/mavfwd) |
68 | |[msposd](https://github.com/OpenIPC/msposd) |[yes](https://github.com/OpenIPC/msposd/issues) |[yes](https://github.com/orgs/OpenIPC/projects/16/views/1) |[TipoMan](https://t.me/tipoman) |
69 | |[pyosd](https://github.com/OpenIPC/pyosd) |
70 | |[pixelpilot_rk](https://github.com/OpenIPC/pixelpilot_rk) |
71 | |[steam-groundstations](https://github.com/OpenIPC/steam-groundstations) |
72 | |[sensor-profiles](https://github.com/OpenIPC/sensor-profiles) |
73 | |[silicon_research](https://github.com/OpenIPC/silicon_research) |
74 | |[urllc-webui](https://github.com/OpenIPC/urllc-webui) |
75 |
76 |
77 |
78 |
79 |
80 | [logo]: https://openipc.org/assets/openipc-logo-black.svg
81 | [telegram]: https://openipc.org/our-channels
82 |
--------------------------------------------------------------------------------
/principles.md:
--------------------------------------------------------------------------------
1 | ![OpenIPC logo][logo]
2 |
3 | ## Alternative open firmware for your IP camera
4 | _(based on Buildroot)_
5 |
6 | [][telegram]
7 |
8 |
9 | ### Organization
10 |
11 | The OpenIPC community brings together a large number of developers and interested users who contribute to improving existing and creating new firmware, adding functions, and supporting new processors.
12 |
13 | Our community is registered as an organization on the OpenCollective platform, as an organization on the GitHub, as well as on social networks such as YouTube, Twitter, Facebook and others.
14 |
15 | We give membership to the OpenIPC organization on GitHub if a person makes a few commits, PR, opens an Issue, and participates in our community.
16 |
17 | We give membership in the organization forever, regardless of whether the person continues to collaborate and develop the project or whether it was his temporary enthusiasm and initiative.
18 |
19 | OpenIPC is officially represented in 11 countries, has documented of our developments and protection of our brand name, which is already quite recognizable on the Internet.
20 |
21 | The main headquarters of our international organization is located in Sanremo, Italy.
22 |
23 |
24 | ### Platform
25 |
26 | If you carefully read first page of our website and the welcome message on GitHub, then on the title page you will find all the phrases that explain the essence of our project (the fact that no one reads it is not our fault, sorry).
27 |
28 | - [https://openipc.org](https://openipc.org)
29 | - [https://github.com/openipc](https://github.com/openipc)
30 |
31 | The essence of our project is to create an OPEN COMMUNITY (which we did all together) whose goal is the research and development of alternative OPEN firmware.
32 |
33 | We want to emphasize that we position our work as the final source code and compiled files of an OPEN OPERATING SYSTEM.
34 |
35 | We do not limit startup, do not introduce any codes, do not protect the bootloader, our kernels are open and clean, scripts are transparent, all components are built from source with some reasoned EXCEPTIONS.
36 |
37 | We strive to constantly look for open solutions, but if there are none, we DO NOT PROHIBIT the use of binary components.
38 |
39 | Each user has the right to choose and can refuse to use OpenIPC if he has an increased feeling of anxiety.
40 |
41 | However, we GUARANTEE that we do not and will never engage in any illegal activities, we will not infringe on the rights of users, but at the same time we will not violate the patent law and intellectual property of some companies if we cannot provide an alternative solution with the source code.
42 |
43 |
44 | ### Exceptions
45 |
46 | Exceptions mean the use in our work of components for which we do not have source codes.
47 | These are some kernel modules and libraries, for some processors (not all), as well as some sensor driver modules, old and new.
48 |
49 | Another exception is ONE of the THREE streamers that are available in our repositories, this is Majestic, which will be discussed below.
50 |
51 |
52 | ### Streamers
53 |
54 | By streamers we mean specialized complex applications that receive information from sensors and, after processing by the ISP, produce them in the form of RTSP, RTMP, RTP and other streams.
55 |
56 | At the moment, there are three streamers in the OpenIPC repositories, these are the fully open Mini and Venc, as well as Majestic.
57 |
58 | The first two streamers work on a limited list of processors, while Majestic is a universal combiner for all systems, which will be discussed below.
59 |
60 |
61 | ### Majestic
62 |
63 | If you go to the title page of our site, you will easily find a special block, at the top right, which shows the deep cooperation and integration of TWO projects, under a single name and the auspices of OpenIPC.
64 | You can think of this as OpenIPC + Majestic = OpenIPC
65 |
66 | Majestic is a closed source streamer that runs on all platforms supported by OpenIPC.
67 |
68 | This streamer is DEFAULT for most published firmware, but is not required for use. You can use Mini, Venc streamers in the firmware, modify and adapt them, or write any of your own if you have the experience and knowledge to do so.
69 |
70 | OpenIPC welcomes diversity and tries to support any endeavors that community members make and encourage them whenever possible.
71 |
72 | Thus, Majestic is not a panacea, but simply works at the moment everywhere, on any processors.
73 |
74 | If some other streamers appear and are published and compatibility is declared, then we will build firmware with them without any problems, as we are doing now with Mini and Venc.
75 |
76 | Majestic is closed for some reason and this has been posted multiple times, but I'll repeat it:
77 |
78 | - it contains some chip manufacturer SDK components for which we have signed an NDA and do not have the right to publish.
79 | - it contains some parts of code that were written with the help of sponsors (I do not mean those who contribute to OpenCollective) and which we also do not have the right to publish.
80 |
81 | For those who have doubts, they can look at the source code of the Mini streamer, add to it all the OPEN libraries that we have written together and published on GitHub over the years, as well as a few SDK components from chip manufacturers and we will get exactly the file that called Majestic.
82 |
83 | Yes, yes, Mini is the younger brother of Majestic and if no one wants to put effort into its code, especially among colleagues who criticize our project, then I think they will not have the strength to deal with Majestic, since it is more complex.
84 |
85 | Majestic code consists of:
86 | - 65-70% of the volume of our open libraries,
87 | - 20-25% of the proprietary SDK components,
88 | - 10-15% of this "glue" paid for by R&D sponsors.
89 |
90 | Any proposals to divide the code into dynamic libraries, unfortunately, will not work, since it greatly increases the volume and we will not be able to get the firmware to work on NOR flash 8 M, and it also complicates the interaction scheme of components and code and worsens stability. We tried to go this route and were forced to abandon it based on testing results.
91 |
92 | As for telemetry, we do collect it and it is written on the wiki on the Majestic streamer page.
93 | When you turn on the device, an ANIMAL request is sent to the DNS server, transmitting data about the processor used, sensor and version of the streamer, only for statistics and analysis.
94 | This is a kind of help for developers during research and debugging, nothing more.
95 | Telemetry can be disabled at any time in the configuration file `/etc/majestic.yaml`
96 |
97 |
98 | ### Source code of OpenIPC projects
99 |
100 | We support 85 repositories, which you can check out [here](https://github.com/orgs/OpenIPC/repositories?type=all)
101 |
102 | Please note that many of them are original, meaning we generate new content.
103 |
104 | We have more than a thousand likes (stars) and hundreds of forks of our repositories.
105 |
106 | Many of our repositories have no analogues and take part in other projects. Here are some of them:
107 |
108 | - [https://github.com/OpenIPC/ipctool](https://github.com/OpenIPC/ipctool)
109 | - [https://github.com/OpenIPC/smolrtsp](https://github.com/OpenIPC/smolrtsp)
110 | - [https://github.com/OpenIPC/mini](https://github.com/OpenIPC/mini)
111 | - [https://github.com/OpenIPC/openhisilicon](https://github.com/OpenIPC/openhisilicon)
112 | - [https://github.com/OpenIPC/silicon_research](https://github.com/OpenIPC/silicon_research)
113 | - [https://github.com/OpenIPC/osd](https://github.com/OpenIPC/osd)
114 | - [https://github.com/OpenIPC/devourer](https://github.com/OpenIPC/devourer)
115 | - [https://github.com/OpenIPC/configurator](https://github.com/OpenIPC/configurator)
116 | - [https://github.com/OpenIPC/snander-mstar](https://github.com/OpenIPC/snander-mstar)
117 | - [https://github.com/OpenIPC/firmware](https://github.com/OpenIPC/firmware)
118 | - [https://github.com/OpenIPC/builder](https://github.com/OpenIPC/builder)
119 | - [https://github.com/OpenIPC/coupler](https://github.com/OpenIPC/coupler)
120 |
121 |
122 | ### Hardware
123 |
124 | Our OpenIPC community found the strength to develop, make and release a test batch of URLLC video camera devices designed for robotics:
125 |
126 | - [https://store.openipc.org](https://store.openipc.org)
127 |
128 | We started with this direction because it was in enough demand to start and there were many enthusiasts there ready to try.
129 | But our next step is to establish partnerships with the factory and produce boards of standard size 38x38 on an ongoing basis.
130 | Some of the HARDWARE source code has already been published in our repository on GitHub.
131 |
132 | We also have our own record and our video camera with OpenIPC firmware descended to a depth of 1415 meters. I think this is one of the deepest and most far-reaching uses of our system.
133 |
134 |
135 | ### Offer
136 |
137 | We kindly ask all zealous fighters for open source who want to challenge and/or refute what is written above regarding NDAs and closed blobs - please send your revelations in the form of open free open source code and/or permission from vendors to use their proprietary components in our OpenIPC firmware.
138 |
139 |
140 | ### Summary
141 |
142 | The OpenIPC community has taken place, will continue to develop and will support all directions and all movements, preferring Open Source but not denying any other forms of cooperation, development and experimentation.
143 |
144 | Thank you all, friends, colleagues and partners!
145 |
146 |
147 |