Mechanics + electronics + software

Connected products need to work as a system. Innovatio Brutalis combines mechanical design, electronics prototyping, firmware and user interfaces to move from an idea and system architecture to a working physical and connected prototype.

CAD and engineering provide the mechanical foundation, while embedded software and test tools support control and communication. Enclosures, brackets and other physical parts can be made using 3D printing, CO₂ laser cutting or CNC machining.

Panels, display windows and fixtures

Laser cutting can provide front panels, transparent display windows, internal panels, fixtures and other flat components for mechatronics prototypes. They can be combined with printed mechanics and embedded electronics. The right manufacturing method for each part of the prototype: material and process follow the component's function.

Explore laser-cut prototype parts in acrylic and other laser-suitable materials. These are possible process choices, not a claim that the existing valve-control project includes laser-cut parts.

ESP32 & Arduino

ESP32 prototyping and Arduino prototype development support proof of concept and functional prototypes. Hardware, firmware and the physical product can develop in parallel. Embedded systems are used to test the intended function before the design moves on to its next stage. The valve-control project's firmware is written in MicroPython on ESP32; Arduino describes the platform context, not an Arduino/C++ implementation.

Sensors & actuators

Sensor data capture and logging help establish how the prototype behaves. Actuator control lets the system affect its surroundings. Inputs, outputs and behaviour are defined for the actual use case.

Valve and actuator control

Valve control is a concrete application. Electronics and firmware need to work with the physical unit and its user interface. Any motor-control requirements are assessed per project; motor, load and performance specifications are not promised without supporting information.

E-ink and embedded user interfaces

E-ink and other displays provide local interfaces. What the user needs to see and how the device should be configured are system requirements, not an afterthought once the mechanics are complete.

RFID/NFC identification

RFID prototypes and NFC functionality can support identification. The intended function determines how identification interacts with the rest of the system. The valve-control example below uses RFID; no specific NFC implementation is claimed for that project.

BLE & Wi-Fi communication

Bluetooth Low Energy (BLE) development and Wi-Fi connected prototypes support wireless communication. The connection is selected according to the application's requirements. IoT prototypes can include wireless configuration, data capture and logging where needed.

iOS app integration

Communication with an iOS application is a concrete example of connecting a physical device with a mobile interface. Firmware, local interfaces and app communication need to be developed and tested together.

Proof of concept

A proof of concept checks whether the intended function and system architecture work. It is not necessarily a finished product, but should inform the next development decision.

Functional prototypes

Mechatronics prototyping brings mechanics, electronics, firmware, sensors, actuators and communication into a testable whole. Explore product development and prototyping for the complete development chain.

Testing & verification

Tests follow the system requirements: control, sensor readings, identification, display and app communication need to work for the intended use. Control and safety logic are defined and verified for the project. A prototype is not presented as a safety-certified or production-approved product.

Project example: ESP32/Arduino valve-control units

A concrete example is the development of valve-control units built around ESP32/Arduino, with firmware written in MicroPython on ESP32, an e-ink display, RFID functionality and wireless communication with an iOS application. BLE or Wi-Fi can be used depending on the application's requirements.

This example illustrates system integration. Component models, quantities, measured test values and delivery outcomes are not specified in the available project information. A full case study will be published when system requirements, testing and results are documented. See existing documented case studies (Swedish).

Based in Malmö, Sweden

Innovatio Brutalis works with businesses in Malmö, Skåne, southern Sweden and throughout Sweden. Describe the function, the physical part and how the device should communicate to discuss the next step.

Discuss your mechatronics or connected prototype.

Mechatronics & connected prototypes