Skip to content

Capabilities

Our engineering domains

Each domain rests on hands-on experience gained building real products. The areas below apply both to development from scratch and to work on existing systems.

SEDES / 01

Embedded software and firmware

Device software running under constrained memory, limited power and real-time deadlines.

  • A track record of shipping products on microcontroller families from six different vendors
  • Bare-metal and RTOS-based development on ARM Cortex-M
  • Ultra-low-power architectures: sleep modes, battery life budgeting, wake-up scheduling
  • Measurement chain: ultrasonic flow measurement, temperature sensing, time-to-digital conversion
  • Power-loss-resilient data storage and journaling on flash
  • Secure boot and signed over-the-air software updates
  • Vendor-independent portability through a hardware abstraction layer
  • End-to-end device-to-cloud flow design for connected (IoT) products
SEDES / 02

Device security and cryptography

A chain of trust in which a field device can prove its identity and runs only verified software.

  • Elliptic-curve signing and verification (ECDSA P-256) for the secure boot chain
  • Secure element integration; private keys are never held in controller memory
  • Device identity and certificate provisioning on the production line
  • Offline key management and certificate authority setup
  • A Cyber Resilience Act (EU 2024/2847) approach: software bill of materials, vulnerability disclosure
  • Authorised field intervention: signed authorisation tokens and mutual verification
SEDES / 03

Industrial platforms and backend

Services that collect, validate and make sense of data arriving from thousands of devices.

  • .NET-based services, PostgreSQL and row-level data isolation
  • Authorisation and data separation by organisation, region and team
  • Asynchronous data collection through message queues and event streams
  • Role and permission model, separation of duties, immutable audit trail
  • Data quality monitoring: missing readings, inconsistent values and latency detection
  • Reporting, data export and integration with external systems
SEDES / 04

Manufacturing and test software

Desktop applications that programme, calibrate and make devices traceable on the production line.

  • Production order management, serial number and batch traceability
  • Calibration station and automated test bench drivers
  • Device programming, readout and verification over the optical port
  • Recording of measurement results and production reporting
  • Windows desktop applications (WPF) and operator interfaces
  • A device registration flow that links manufacturing to the field
SEDES / 05

Geospatial systems

Components that process location data on your own infrastructure, without depending on external services.

  • Vector map serving from your own server
  • Routing and distance calculation
  • Geocoding and search
  • Asset and field crew positioning
  • Operation without external service costs or data sharing
SEDES / 06

Corporate web and business applications

Business software outside the measurement world, built with the same engineering discipline.

  • Multilingual corporate websites; statically generated, fast and easy to maintain
  • Invoicing, subscription and collection flows
  • Document generation and email delivery infrastructure
  • Application programming interface design and system integration

Hardware platforms

We are not tied to a single vendor

Thanks to a hardware abstraction layer, the same product software runs on microcontrollers from different vendors. When supply gets tight or costs need optimising, switching silicon does not mean rewriting the product firmware — which is exactly the lesson many manufacturers learned the expensive way in recent years.

Microcontroller families we have shipped products on

  • STMicroelectronics
  • NXP
  • Renesas
  • Microchip
  • Nuvoton
  • GigaDevice

Vendor names are used solely to indicate our areas of experience; they do not imply a partnership, authorisation or endorsement. All brand names belong to their respective owners.

Portable core

Measurement, tariff and protocol logic is isolated from the hardware; changing silicon affects only the abstraction layer.

Against supply risk

Being able to keep producing with a second-source part saves months on a product whose certification is already complete.

One maintenance line

Products running on different silicon are fed from one code base; a security patch is written once.

Ultra low power

Battery life is a software decision

The battery in a meter deployed to the field is usually never replaced; it is expected to last the product’s lifetime. What determines that is less the hardware than the decisions the software makes: how often the device wakes, how many milliseconds it stays awake, exactly when the radio turns on and how long it stays on.

  • Budgeting sleep current and selectively powering down peripherals
  • Balancing wake frequency against data resolution, by measurement
  • Shortening radio-on time; batching transmissions
  • Correcting clock drift without spending battery
  • Degrading functionality in stages at the low-battery threshold
  • Verifying energy consumption by measurement across the product lifetime

Current profile over a typical duty cycle

Sleep Measure Log Transmit Current Time
The diagram illustrates the structure of a duty cycle; it is not to scale and does not represent the values of any particular product.

Communication

From wireless to wired, up to the application layer

How a field device carries its data directly determines both project cost and coverage success. We have shipped products on all of the structures below; which one is right depends on device density, coverage conditions and the energy budget.

Wireless

For battery-powered devices that send data infrequently and are spread over a wide area.

  • NB-IoT
  • LoRaWAN

Wired

For in-building installations, industrial automation and local readout scenarios.

  • M-Bus
  • Modbus
  • CAN bus
  • Ethernet
  • Optical port (IEC 62056-21)

Application layer

For giving the data a standard model and exposing it to external systems.

  • DLMS/COSEM
  • REST API

Because the communication layer is abstracted, the same product software can support more than one bearer; when field conditions change, the measurement and tariff logic is left untouched.

Standards

Standards and protocols we work with

In industrial projects protocol conformance is not a preference but a precondition for certification. We have hands-on experience in the areas below.

DLMS/COSEM

Meter data model and communication

IEC 62056-21

Local readout over the optical port

M-Bus

Meter bus communication

UNI/TS 11291

Gas meter data model and event catalogue

TS EN 1434

Heat meters

EU 2024/2847

Cyber Resilience Act approach

This list shows standards we have worked with; it is not a declaration of conformity for any particular product. Certification scope is assessed per project.

Let’s work together

Let us talk about your next project

If you have a piece of hardware, a regulatory requirement or an integration that will not work, a short technical conversation usually clarifies the path.

Contact us