Buyer pains we hear most

  • Bus interop testing across multiple protocols and vendors
  • Long product life with limited service access
  • Gateway devices need provisioning, OTA, and per-unit identity
  • EMC for mains-near installations is a frequent fail point

Typical product traits

  • KNX, BACnet, Modbus, DALI, or Matter communication
  • Mains and low-voltage mixed boards
  • Sensor inputs (PIR, temperature, light)
  • DIN-rail, wall-mount, or recessed enclosure

Regulatory environment

Building automation product standard

EN 50090 series

EMC for residential and light industrial

EN 55014 / EN 61000-6-3

Low Voltage Directive

2014/35/EU

Test plan considerations

  • Bus interop test against reference master per protocol
  • Sensor accuracy test against calibrated source
  • Mains isolation hipot per unit
  • OTA update path verified for gateway products

Frequently asked questions

Can you load and provision firmware in production?

Yes. Firmware loading runs on the line through dedicated programming fixtures. We support SWD, JTAG, UART, and USB-DFU interfaces, multi-image programming (bootloader, application, file system), and signed bootloader chains. When the customer test plan calls for functional test alongside flashing, the unit moves on to a partner test house with the firmware already loaded.

How do you handle embedded software and secure provisioning?

We support X.509 certificate enrollment, secure-element key injection (ATECC608, NXP EdgeLock), eFuse and OTP programming, and provisioning to AWS IoT Core, Azure DPS, and custom PKI. Private keys can be HSM-generated and never exposed to host systems.

What lead times can we expect?

New product introduction takes about 4 to 8 weeks depending on component availability and test fixture readiness. Repeat batches typically run on a 3 to 5 week cadence once tooling and test plan are in place.

Quote building automation

Send your product files and a short description. We respond within one business day.