An aesthetic device is a consumer-facing product with medical-device discipline: a capacitive touch panel, one or more handpieces, an interlock chain that must never be bypassed, and a treatment log the clinic can print. The control board is usually the least visible and most constrained part of the BOM.
What the device requires
- Pulse generation is not a Linux task. IPL lamp triggering, RF burst envelopes and energy dosage are microsecond-level events on an MCU, FPGA or dedicated driver ASIC.
- Panel and skin contact feedback. The operator needs a live view of fluence, spot size, skin temperature and remaining shots.
- Interlock. Handpiece presence, contact sensor, key switch and footswitch form a chain that the host only observes.
- Cost and size. These products are built in the hundreds to low thousands per year; the electronics have to be cheap, small and quiet.
Recommended configuration
| Function | Recommended TOPEET part |
|---|---|
| Console HMI, treatment log, USB export | iTOP-RK3506 Single Board Computer: three Cortex-A7 plus a Cortex-M0, two CAN FD channels, two 100 Mbit Ethernet ports, 512 MB DDR3, 38 x 38 mm module |
| Imaging handpiece or skin-analysis camera | iTOP-RK3562 Single Board Computer with 1 TOPS NPU and two MIPI-CSI ports on the carrier |
| Multi-handpiece console with a large panel | iTOP-RK3568 Single Board Computer |
| Panel | 10.1-inch Capacitive HMI Panel or 7-inch Capacitive HMI Panel |
| Camera for a skin-imaging handpiece | OV5695 5 MP MIPI Camera Module |
Why the RK3506 is the default: it boots Linux or RT-Thread, drives MIPI-DSI or parallel RGB panels up to 1280 x 1280, carries two CAN FD channels for handpiece and driver boards, and costs a fraction of an application-class SoC. Its Cortex-M0 core can host the interlock watchdog so the display side cannot mask a fault.
Interface checklist
- Handpiece: CAN FD to the driver board, with a separate hard-wired enable line.
- Contact and temperature sensing: on the MCU, reported to the host over the same bus.
- Panel: MIPI-DSI for a slim head, parallel RGB for a fixed console.
- Cooling: PWM fan control with tachometer feedback; IPL heads dissipate a lot in a small volume.
- Service: USB for log export and a UART debug header inside the enclosure, never on the outside.
What we would validate with you
Panel latency against the handpiece trigger, EMC behaviour when the lamp fires next to the display ribbon, thermal margin at the panel backlight, and the boot time from cold to ready-to-fire.
Documents
English datasheets, schematics and BSP sources are in the resource portal behind registration. Ships with a 12-month warranty and email engineering support.
Frequently asked questions
Can the control board generate the IPL or RF pulse itself?
No. IPL lamp triggering, RF burst envelopes and energy dosage are microsecond-level events that belong on an MCU, FPGA or dedicated driver ASIC. The board runs the console HMI, the treatment log, USB export and the panel.
Which board fits a multi-handpiece console?
The iTOP-RK3568 with a large panel for a multi-handpiece console, the iTOP-RK3562 (1 TOPS NPU, two MIPI-CSI ports on the carrier) for an imaging handpiece or skin-analysis camera, and the iTOP-RK3506 (three Cortex-A7 plus a Cortex-M0, two CAN FD, two 100 Mbit Ethernet, 38 x 38 mm) for a compact console HMI.
What is validated before the device ships?
Panel latency against the handpiece trigger, EMC behaviour when the lamp fires next to the display ribbon, thermal margin at the panel backlight, and the boot time from cold to ready-to-fire.
0 comments