Skip to main content
SoTech

Connect hardware to software

Embedded systems and hardware integration.

Sensors, devices, and equipment that need software to talk to. Or software that needs to talk to equipment in the field.

01Overview

For physical products with software inside them, and for operational software that reads from drills, probes, sensors, and other site equipment. We work from the chip inside the device up to the cloud it reports to.

  • Software embedded in devices
  • Reading data from sensors and equipment
  • Wireless connections, including where signal is patchy
  • Sending equipment data to the cloud
  • Updates delivered to devices over the air

Technologies

  • Embedded C
  • IoT
  • Sensors
  • Bluetooth
  • Over-the-air updates

02Situations

Where we usually come in.

  • Your equipment produces data that someone writes down by hand.

  • You are building a physical product and need the software inside it.

  • You have sensors in the field and no reliable way to get readings back to the office.

  • Your device works, but its software is out of date and nobody can update it.

03How it works

How a project runs.

  1. 01

    Understand the hardware

    Datasheets, protocols, and the device on a bench in front of us. We find out what it can tell us.

  2. 02

    Prove the connection

    A small working prototype that reads real data from the real device, before anything bigger is built.

  3. 03

    Build the full system

    Device software, connectivity, and the tools that store and show the data, built to cope with patchy signal.

  4. 04

    Deploy and maintain

    Field trials, updates delivered over the air where the hardware supports it, and support once devices are out in the world.

04Questions

Common questions.

Can you work with equipment we did not design?
Often, yes. Many devices share their data over serial, USB, Bluetooth, or a network connection. We will tell you early whether it is practical.
What happens when there is no signal on site?
Readings are stored on the device and sent when a connection returns, so nothing is lost.
Who owns the code?
You do, once it is paid for. The code, hosting, and domains sit in accounts you control, so if you ever move on from us you take everything with you. The only exception is our own general-purpose tooling, which you get a permanent licence to use.

Sounds like your situation?

The project planner takes about five minutes. A quick message also works. Either way, we reply within two working days.