Avenxor designs and manufactures purpose-built embedded systems for medical devices, industrial automation, and mission-critical equipment. Our work covers the full hardware-firmware stack: schematic and PCB design, microcontroller firmware in C and C++, real-time control loops, sensor integration, and the safety architecture that lets a device be certified for clinical use. We build to IEC 60601 (medical electrical safety), IEC 62304 (medical device software lifecycle), and ISO 13485 (quality management) from the first design review — not as a retrofit before audit. Production systems include neonatal incubators with dual-thermistor PID control, phototherapy units with eye-safe LED interlocks, and 220 V industrial power supplies with Modbus telemetry. Devices we ship are running in hospitals and factories across Indonesia, with 100% field uptime over six years. Every project arrives with full traceability documentation, hardware design files, firmware source, and a tested maintenance procedure — because medical-grade work assumes the device outlives the original team.
What standards does Avenxor build embedded medical devices to?
Every embedded medical project is engineered to IEC 60601 (general electrical safety), the relevant IEC 60601-2-x collateral (such as -2-19 for incubators or -2-50 for phototherapy), IEC 62304 (software lifecycle), and ISO 13485 (quality management) — built in from the first design review, not retrofitted before audit.
Do you handle PCB layout and firmware in-house, or only one of them?
Both. Avenxor covers schematic capture, multi-layer PCB layout with EMC-aware routing, microcontroller firmware in C and C++, real-time control, sensor and protocol integration, and bring-up. A single team owns the device end-to-end.
What microcontrollers and toolchains do you support?
We design with STM32, NXP i.MX RT, ESP32, and Nordic nRF families depending on power, connectivity, and certification requirements. Toolchains include GCC ARM, IAR, ESP-IDF, and Zephyr RTOS — selected to match each device safety class and supply-chain longevity.
Can you make existing medical devices interoperable (HL7, DICOM, SDC)?
Yes. We add HL7 FHIR, DICOM, and IEEE 11073 / SDC interoperability to both new and legacy embedded products, so they integrate cleanly with hospital information systems, PACS, and operating room device networks without replacing the underlying hardware.
How long does a typical embedded medical project take from spec to first prototype?
First functional prototype usually lands in 10 to 14 weeks for a device of moderate complexity. Full design-control documentation, EMC pre-compliance testing, and clinical-evaluation-ready firmware follow over the next 3 to 6 months.
Do you transfer hardware design files and firmware source to the client?
Yes. Every embedded engagement ships with complete hardware design files (schematic, BOM, Gerber, manufacturing notes), firmware source code, build instructions, and a tested maintenance procedure — so the device can outlive the original engineering team.
Have a embedded systems challenge?
Let's talk.
Most engagements start with a 30-minute call. Describe the problem — we'll tell you honestly if we're the right team.