Platform Philosophy: From Prototype to Industrial Series

1. The Problem: The Gap Between Prototyping and Series Production

The modern market is flooded with various hardware platforms for prototyping (Raspberry Pi, Arduino, Adafruit Feather, etc.). This has led to fragmentation: developers create systems based on incompatible blocks. Consequently, it is virtually impossible to ensure a smooth and reliable transition from a working prototype to a serial industrial product. This issue is particularly critical when automating small industrial facilities or modernizing existing industrial devices and installations.

The Core Problem: This approach often leads users to create their own boards and debug their project from scratch after prototyping. This is an insane waste of time and money, which almost certainly outweighs any potential savings on the cost of the implemented hardware. Moreover, the user's overhead costs for supporting their custom developments can simply bankrupt them.

2. The Solution: I/O Standardization with the IoTextra Series

We decided to bridge this gap by creating the IoTextra series of Input/Output (I/O) modules. This is a standardized set of I/O blocks that can be reliably and easily integrated with the most popular hardware platforms. IoTextra includes modules with digital, analog, and combined (digital + analog) channels on a single PCB, ensuring flexibility and completeness of the solution.

3. Architectural Integration Paths

Our philosophy offers two clear architectural strategies for working with IoTextra modules:

A. Using IoTbase: For Maximum Integration and Serial Solutions

  • Goal: To achieve maximum utilization of the chosen hardware platform's capabilities, including the creation of multi-board, multi-channel solutions.
  • Solution: IoTbase modules act as carrier boards designed for integration with specific SoMs (System-on-Module) of various platforms (e.g., Raspberry PICO, Arduino Nano, etc.).
  • Assembly: A ready SoM is inserted into the IoTbase carrier module, to which one or more I/O modules from the IoTextra series are connected. This ensures flexible use of the platform's wired and wireless interfaces.

B. Using IoTsmart: For Rapid Development and Autonomous Nodes

  • Goal: To achieve maximum reduction of the path to implementation and ensure software compatibility for small and/or autonomous solutions.
  • Solution: For projects where the channels available on a single IoTextra module are sufficient, the user can install our IoTsmart module (based on a popular MCU, including RP2040, RP2350, ESP32) directly into the IoTextra module.
  • Communication: In this case, wireless interfaces are used for communication.

 

3. Standalone Value and Openness of IoTextra

While IoTextra modules are the core of the Make Things Happy platform, they are designed for maximum flexibility and are not part of a closed ecosystem. The modules can be used outside of our platform, surpassing many competitors in their technical characteristics, reliability, and quality.

To ensure openness and ease of adoption:

  • Our modules are always Open Hardware, and their schematics are published and always up-to-date.
  • We strive for excellence and frequently update our modules, including based on user requests, while understanding the importance of compatibility with preceding versions.
  • All IoTextra modules are well documented (including on GitHub).
  • They are accompanied by programming examples, particularly in Python.

This allows users to first familiarize themselves with individual IoTextra modules, evaluate their quality, and begin prototyping without the need to immediately adopt the entire architecture.

4. Software: IoTflow

To support the architectural approaches described above for creating IoT and IIoT projects, we have developed the Open Source software IoTflow.

  • Purpose: IoTflow allows configuring the firmware for the MCU (on IoTbase or IoTsmart modules) to control the IoTextra modules (via GPIO or I2C).
  • Node-RED Integration: IoTflow also allows creating a ready-made node for Node-RED, ensuring simple and fast communication via WiFi.
  • Compatibility: Node-RED nodes are often used in other software platforms, such as Blynk.