Connected hardware

Software for connected hardware, sensors and automation

DIGI117 builds the software around connected devices: the platform that provisions and registers them, the pipeline that carries their data, the links to plant and business systems, and the apps operators watch. Integrations are read-mostly by default. Safety functions and interlocks stay in the certified controller; we do not write safety-rated control or motor firmware.

  • 4 service linesfrom device platform to operator apps
  • Open protocolsMQTT, CoAP, LoRaWAN, OPC UA, Modbus
  • Read-mostlywrites only to points agreed in writing
  • Safety stays putin the certified controller

Talk to an engineer Building robots? Robotics

Service lines

Four service lines for the software around the device

For makers of sensors, meters, appliances and industrial devices, and for the companies that run them. Each line is scoped and quoted in writing after a short review of one product line or one site.

H-01

Connected device platforms

Device provisioning, a fleet registry, companion apps and the cloud back end for connected products: sensors, meters, appliances and industrial devices. Each device gets an identity at the factory or on first start, and every customer sees only their own devices.

H-02

Sensor data and telemetry

Ingest from MQTT, CoAP, LoRaWAN and cellular gateways, time-series storage, dashboards and alerts that reach the right person, and data retention set per country, written down per field.

H-03

Industrial automation integration

Links between PLCs, SCADA and MES and your business systems through OPC UA, Modbus and MQTT, with edge gateways on site. Read-mostly by default: we read tags and registers, and write only to the points you and your integrator agree in writing.

H-04

Monitoring and supervisory control apps

HMI-style dashboards, remote monitoring, alarms and operator workflows. Safety functions and interlocks stay in the certified controller, owned by the hardware maker or integrator. DIGI117 does not write safety-rated control or motor firmware.

Robots rather than devices? The ten robotics lines, from fleet consoles to ROS 2 moves, are on the Robotics page.

Scope

What we build, what stays with the hardware

A device that works on the bench still needs a way to be registered and updated, a path for its data, links to the systems the customer already runs, and screens for the people who watch it. That software is our work.

We start read-mostly. An integration reads first; a write to a controller happens only for named points, agreed in writing with you and your integrator, and logged. Anything that keeps people or equipment from harm stays in the controller, where it was designed and certified.

Who does what

  • DIGI117: device platforms, telemetry, integrations and operator apps, with their records
  • The hardware maker or integrator: safety functions, interlocks, safety-rated control and motor firmware
  • Accredited test labs: testing and certification
  • Your counsel: legal opinions and filings
  • You: decisions, keys and the final say on every release

Open protocols

The standards we build on, in their makers' words

We work with the published protocols your devices and controllers already speak. Each line links the organization that maintains it.

ProtocolWhat its maker saysWhere we use it
MQTT"MQTT is a Client Server publish/subscribe messaging transport protocol." OASIS, MQTT Version 5.0Telemetry from devices and gateways; links between edge and cloud
CoAP"designed for machine-to-machine (M2M) applications such as smart energy and building automation." IETF, RFC 7252Small, battery-powered devices on constrained networks
LoRaWAN"designed to connect battery operated ‘things’ to the internet" LoRa AllianceSensors spread over a site or a region, through network servers and gateways
OPC UA"a platform independent service-oriented architecture" OPC FoundationReading from PLCs and SCADA, and links to MES and business systems
ModbusSpecifications and implementation guides from the Modbus OrganizationOlder controllers, meters and drives, usually through an edge gateway

How an engagement starts

One product line or one site, one review, then a written plan

  1. NDA first. Then tell us about the device or the site: what it runs, what it talks to and where its data goes today
  2. A short review of one product line or one site: we read the code and the data path, and list every controller and system it touches
  3. Written findings, ranked by risk, with the parts that belong to the hardware maker, the integrator, a lab or counsel marked as theirs
  4. A written plan and quote per service line, with the people on the job named before you sign
  5. Build in your repositories, weekly demos, then handover with a runbook, or we stay on

Before the NDA

  • A short call on the device, the site and the deadline
  • A check against the restricted lists below
  • No access to code, data or controllers until the NDA is signed

Who we do not work for

Makers on the US Entity List, on US or Canadian sanctions lists, or on the US Section 1260H list. We check before the NDA.

Market entry

Engineering here, market entry at Norvoya

DIGI117 builds the software. Norvoya, our front office, handles North American market entry. Robocho, our robotics database and AI, keeps the facts.

Bringing a connected product to the US or Canada? Norvoya plans the entry with you, coordinates the labs, counsel and partners, and reports to you in writing. DIGI117 builds the software the launch needs.

Visit Norvoya

Robotics

Software for robots: fleet consoles, signed updates, apps, data, integrations and ROS 1 to ROS 2 moves, in ten service lines.

See the robotics lines

Built for hardware importers

A market-access lookup for robots and connected devices: search by brand, model or serial, six dated checks per product, five languages, served from the edge.

Read the build

Questions

Do you write PLC logic, safety functions or motor firmware?

No. Safety functions, interlocks, safety-rated control and motor firmware stay in the certified controller, with the hardware maker or integrator who owns it. We build the software around it and agree the interface with them in writing.

Will your software write to our controllers?

Only where you and your integrator agree it in writing, point by point, and every write is logged. By default our integrations read.

Do you certify devices?

No. Accredited test labs test and certify, and regulators grant authorizations. We build the software and the engineering records the lab and your counsel ask for.

Which protocols?

MQTT, CoAP, LoRaWAN, OPC UA and Modbus, plus cellular gateways and the APIs of the business systems you already run. If your devices speak something else, tell us on the first call.

How long does it take?

The review comes first; the plan after it gives dates per service line, in writing.

Bring one product line or one site. We start there.

Send what the devices are, what they talk to and where the data should go. After the NDA, we review it and reply with what we would do first.

Contact us Robotics

Reply within one business day · Not legal advice