SOFTWARE FOR DEVICES AND MACHINES

Embedded software and hardware integration for devices and machines

Do you have hardware, a prototype or an existing device, but not a complete software team?

Renau Digital can take responsibility for an agreed scope: device logic, integration with components, HMI, diagnostics, and deploying and verifying the software on the physical device.

We can own the full agreed software scope or support your team with a selected layer of the project.

We work with embedded Linux / Yocto, RTOS and microcontroller software. We select technologies according to the device architecture, available hardware resources and project requirements.

When to bring Renau Digital into your project

01

You have a prototype or a defined hardware platform

The device already exists, but it lacks the software layer needed to move the product forward. Data from components, process logic, the user interface and service functions need to work together.

We can start with a limited scope that verifies the key assumptions, then develop the solution in stages.

02

You are developing an existing device

The product works, but its logic needs to be reorganised, functionality extended, the HMI replaced, diagnostics added or the next version prepared.

We review the available code, documentation, platform and constraints. This allows us to identify what can be extended and what needs to be rebuilt.

03

You are missing part of the software expertise

You have your own hardware or software team, but need an external team for a specific layer: device logic, integration, HMI or service functions.

We agree the scope and boundaries of responsibility before work starts.

04

The individual layers do not work as one system

A sensor provides data, the logic needs to interpret it correctly, and the HMI should show the operator the actual state of the device.

We can organise the dependencies between these layers and take responsibility for how they work together within the agreed scope.

See how we prototype device software

CASE STUDY / TRIOXYGENE

Trioxygene – software running on a physical device

For Trioxygene, we developed software for a device that treats objects with ozone inside an enclosed chamber.

Read the full Trioxygene case study

The scope brought together:

  • service workflow logic and control
  • integration with device components
  • data from the O₃ sensor
  • software handling of door states, locks and process components
  • a touchscreen HMI for users
  • operating variants with and without payment
  • diagnostics, configuration and service views
  • software updates
  • local operation of core functions without a continuous internet connection

The interface guides users through program selection, chamber preparation and each stage of the cycle. At the same time, it displays the state determined by the device logic and data from its components.

The project used Linux / Yocto and a local backend/API. The software was implemented and tested on the physical Trioxygene ozone device.

Device software and logic

Calling a function does not by itself mean that an operation can start or has completed correctly.

Starting a process may depend on component states, a sensor value, a closed door, an active lock or completion of the previous stage. If the device is in an invalid state, it should respond according to the agreed logic and provide the operator with the information they need.

For critical processes, we define:

  • device states and transitions
  • conditions for starting and completing operations
  • data required to make decisions
  • responses to invalid or incomplete signals
  • situations that require operator action
  • functions available to users, operators and service staff

Design decisions follow the actual machine process, the available hardware and Renau Digital’s agreed responsibility. The scope can also include backend/API development and communication between the device and the backend. We define how these elements work with control logic and the HMI according to the device architecture and operating workflow.

Hardware integration and HMI

Device software needs to work with the actual inputs, outputs and components. An interface is not enough if the information it shows does not match the real state of the machine.

Depending on the project, the integration scope may include:

  • sensors and measurement data
  • device inputs and outputs
  • actuators
  • doors, locks and access conditions
  • touchscreens
  • terminals
  • other agreed peripherals

We work within the interfaces, documentation and platform provided by the client or their hardware partner.

The HMI should show the device state, not just the last click

Hardware → device logic → HMI

The interface should display a state confirmed by the logic and available data. This includes readiness to start, the current process stage, component statuses, operation completion and situations that require operator action.

Renau Digital can own the HMI as part of a wider software scope, or focus on the interface and interaction logic layer.

We develop HMIs ranging from lightweight microcontroller interfaces to advanced touchscreen panels running on embedded Linux. We adapt the interface to the platform’s resources, the way the device is operated and the needs of users, operators and service staff.

See our HMI and embedded UI work

Diagnostics, service and deployment on the physical device

Once deployed, a device needs to be maintainable and diagnosable. Operators and service staff should know its current state and have access to the data required to analyse a problem.

The scope may include:

  • device state overview
  • input and output data
  • sensor and component statuses
  • events and diagnostic information
  • configuration parameters
  • operator and service views
  • version identification
  • an agreed software update method

Not every project needs every function. We adapt diagnostics and service access to how the device is used and maintained.

Verification on the physical device

A working screen or demonstrator does not confirm that the entire device behaves correctly.

We deploy and verify the agreed scope on physical hardware. We check the process flow, responses to available signals, and how the device logic and HMI work together.

We can work:

  • on a device or prototype delivered to Renau Digital
  • on a comparable platform
  • remotely on a device that remains at the client’s site
  • together with the client’s hardware team or another technical partner

The working model depends on access to the device, documentation and interfaces, and on whether tests can be performed safely.

See how we work remotely on a client device

Clear responsibility boundaries

Renau Digital can take responsibility for the agreed device software scope or for a selected layer of an existing solution.

Renau Digital’s scope may include

  • process and device state logic
  • integration with agreed components
  • HMI and interaction logic
  • diagnostics and service functions
  • configuration and updates
  • deployment of the agreed scope on the physical device

The client or specialist partners may remain responsible for

  • electronics and PCB
  • mechanics and power systems
  • hardware design and production
  • product certification
  • EMC
  • functional safety
  • other regulatory requirements

At the start of the project, we agree the interfaces between teams, available materials and responsibility for each part of the solution.

Do you have hardware, a prototype or an existing device and need a software team?

We will assess whether we can take responsibility for a larger part of the device software, a selected layer or an initial stage that verifies the key assumptions.

Tell us briefly:

  • what the device does
  • the current stage of the project
  • what hardware is already available
  • what currently works
  • what software support you need

This website uses cookies and similar technologies to analyse traffic and protect the contact form from spam.

For more information, see our Privacy Policy.