PCBA PARTNER
EN
English中文Deutsch日本語Français

Beauty electronics · Camera-guided lighting

AI nail-lamp electronics.Vision, light and control.

A camera-guided nail-curing design that connects nail segmentation, individually controlled LED channels and timed local control. Explore the electronics behind the lighting system.

  • 109-channel lighting architecture
  • STM32 local control
  • Camera-to-light mapping
  • USB-C & battery power design
KiCad three-dimensional design view of the nail-lamp STM32 control board and its vision, driver and guard interfaces
Control-board design view · Vision, LED-driver and hardware-guard interfaces

Separate vision from real-time control.

The architecture gives image processing, LED timing and hardware gating distinct responsibilities. The screen requests an operation; local control determines when lighting is permitted.

Camera-to-light control path
VISION & OPTICAL MAPPING
CAMERATimestamped framesHand position and nail regions
SEGMENTATIONNail contoursPixel-level lighting boundaries
CALIBRATIONChannel permitsMatch full light footprints

The mapping must account for wavelength, hand height, optical spread and motion. A detected rectangle alone is not a lighting boundary.

LOCAL CONTROL & LED DRIVE
UART LINKFrame validationSequence, age and CRC checks
STM32G071Timed state machineStart, qualify, run and stop
7 × TLC5940112 driver outputs109 lighting channels allocated

The local controller owns the timer and channel data. Three unused outputs remain off.

POWER & HARDWARE GATING
INPUTUSB-C power designContract and current budgeting
ENERGY4S battery architectureCharging and system-load allocation
GUARDIndependent gatingWatchdog and output-disable path

Power allocation, temperature inputs and fault signals form part of the illumination decision.

VISION PROCESSING

Find the nail contour

The software interface accepts a nail-probability map and a measured footprint for each light channel. A channel is permitted only when its complete mapped footprint falls inside the selected nail region.

LED CHANNEL CONTROL

Independent light commands

Seven 16-channel TLC5940 drivers provide a 112-output chain. The 109-channel allocation leaves three outputs disabled; brightness commands are bounded by the available power budget.

LOCAL TIMING

Keep exposure timing local

The control logic includes 9, 15 and 20-second intervals. Explicit start, stable-frame qualification, timed completion and latched faults keep the operating sequence independent of screen refresh.

HARDWARE GATING

A separate path to turn light off

The GUARD interface separates the lighting request from hardware permission. Watchdog recovery, output blanking, reset behavior and temperature inputs belong in one defined control sequence.

POWER MANAGEMENT

Budget the whole system

USB-C input power is shared by the processor, display, lighting and charging. The charge-current calculation reserves system power before allocating the remainder to the battery.

DISPLAY & CONNECTIVITY

Make controls fit the product

The user interface can bring together mode selection, countdown, battery information and fault messages. Display dimensions, camera optics and connectivity are selected around the enclosure and product brief.

Follow the signals through the board.

These images are exported from the editable KiCad designs. The local controller and LED driver use separate interfaces for data, timing, power and output permission.

KiCad PCB routing view: Local controller · top copper
PCB DESIGN VIEWLocal controller · top copperSTM32 control, vision UART, driver chain, buttons, charger and GUARD connections.
KiCad PCB routing view: 16-channel LED driver · top copper
PCB DESIGN VIEW16-channel LED driver · top copperTLC5940 routing with serial control, channel outputs and power connections.

A lighting decision has several checks.

The image-processing path proposes which channels may be used. The controller checks freshness, configuration, power and hardware permission before applying that decision.

01 / RECOGNITION

Contour, confidence and stability

Use segmentation rather than a bounding box. High-confidence regions, an inward margin and consecutive stable frames define the software input to optical mapping.

02 / LIGHT MAPPING

Match the whole footprint

Compare each channel’s calibrated optical envelope with the nail region. Wavelength, hand height, camera alignment and motion allowance determine the envelope.

03 / FRAME VALIDATION

Reject outdated commands

The versioned UART interface binds challenges, sessions, calibration identity and CRC to fresh lighting commands. The V4 operator bridge adds explicit start, stop and mode requests. Invalid, stale or mismatched data clears lighting permission.

04 / LOCAL EXECUTION

Start deliberately. Stop predictably.

The controller progresses through arming, qualification and timed operation. A stop request or fault returns the outputs to the off state; a recovered fault requires a new start.

Optics and electronics define the result together.

A useful product brief connects the desired curing behavior to measurable optical, thermal and electrical requirements. Those requirements guide LED selection, board layout and the software calibration.

OPTICAL DESIGN

Wavelength, coverage and dose

Define the 365/405 nm light-source arrangement, nail-side coverage, allowed hand positions and gel-specific curing requirements. LED count alone does not define curing performance.

MECHANICAL DESIGN

Start with the hand space

Camera position, LED angles, reflections, enclosure clearances and service access determine where boards and wiring can sit. Share the internal geometry together with the industrial design.

POWER & THERMAL

Treat charging and lighting as one load case

Specify adapter power, battery capacity, peak lighting demand and ambient temperature together. Source switching and charge termination need to account for the system load.

BUILD PLANNING

Review cost against the production quantity

Compare board consolidation, connector count, sourcing and test time at the required volume. Material choices and assembly scope follow the agreed electrical and optical requirements.

From a camera frame to a controlled light channel.从一帧图像,到每一路灯光。

Understand what each board does, how the software reaches a lighting decision, and how to review the R6 files. This is a documented engineering design; measured calibration and product qualification remain separate work.了解八块电路板如何分工、软件怎样形成照射决策,以及 R6 资料应该从哪里看起。本页讲解已有工程设计,实测标定与整机验证的进度在下方单独说明。

What happens during one operating cycle?一次工作循环怎样完成?

The camera proposes where light may be used. The STM32 owns the exposure timer and output decision, while a separate guard path provides hardware permission. The screen displays the controller’s reported state.摄像头和视觉程序提出“哪些位置可以照射”;STM32 掌握计时与输出决策,独立保护链提供硬件许可。屏幕显示控制器回传的状态。

  1. Prepare the system准备系统

    The controller checks configuration, power, temperature, driver readiness and the required cooling/guard conditions before qualification can complete.控制器先检查配置、电源、温度、驱动就绪以及所需散热和保护条件,满足前置条件后才能完成运行资格检查。

  2. Capture a fresh frame采集新图像

    The vision side processes a timestamped camera frame and estimates nail contours. Low confidence, movement or missing input must not become a new lighting permit.视觉端处理带时间信息的图像并估计甲面轮廓。低置信度、移动或图像缺失,不能被当作新的照射许可。

  3. Map the full light footprint映射完整光斑

    For each channel, compare the calibrated footprint with the selected nail region and its inward margin. A point or a bounding rectangle is insufficient.逐路把已标定的完整光斑与甲面有效区域及向内余量比较。仅判断灯珠中心点或识别框落在甲面上并不够。

  4. Validate the request校验操作与报文

    A matched V4 transaction binds the request to the current challenge, session and calibration identity. Local checks can still refuse it.配对的 V4 事务把请求与当前挑战、会话及标定身份绑定。即使报文有效,本地条件不满足时仍会拒绝。

  5. Run with a local timer本地计时运行

    After an explicit start and qualification, the MCU controls the channel mask and interval. The UI reads remaining time from the MCU rather than inventing its own countdown.明确启动且资格检查完成后,MCU 执行通道掩膜和照射时段。界面从 MCU 读取剩余时间,不以自行倒计时代表实际照射状态。

  6. Finish or remove permission结束或撤销许可

    Completion, a stop request, an expired vision lease or a fault removes lighting permission. A recovered fault requires a deliberate new start.计时完成、停止请求、视觉租约过期或故障会撤销照射许可。故障条件恢复后,仍需重新明确启动。

Eight boards, with different jobs.八块板,各自负责什么?

These are the eight board identities in the published CAD/CAM set. Review each board’s own schematic, BOM and fabrication folder; do not combine manufacturing files merely because two boards share a connector pitch.下列名称对应公开 CAD/CAM 中的八块板。每块板都应结合自己的原理图、BOM 和加工目录阅读,不能仅因连接器间距相同而混用加工或线束资料。

Battery protection · BMS电池保护板 · BMS

Battery-pack protection circuitry is separate from the main charging and system-power functions. Review its protection paths and the published U3 ordering-code correction with the battery design.负责电池包保护相关电路,与主电源板的充电和系统供电职责分开。应结合电池方案检查保护路径,并阅读公开 BOM 中 U3 订货号的勘误。

Local controller · control_C8_rear_exit本地控制板 · control_C8_rear_exit

The STM32G071 connects physical controls, vision UART, driver timing and guard/status interfaces. It owns the operating state, exposure timer and the final software decision to permit light.STM32G071 连接实体按键、视觉串口、驱动时序及保护/状态接口,负责工作状态、照射计时和软件侧最终许可判断。

Display adapter · display_adapter显示转接板 · display_adapter

Routes the display-side connections, including RGB signals, backlight and touch-related interfaces. Signal matching in CAD does not establish the final FPC contact side or assembled screen compatibility.承接显示侧连接,包括 RGB、背光和触摸相关接口。CAD 中信号相符,不代表最终 FPC 接触面、插接方向和屏幕总成已经匹配验证。

Seven-bank driver · driver_7bank七组驱动板 · driver_7bank

Seven 16-output TLC5940 devices form the 112-output driver chain. Serial data, timing and output blanking connect the MCU’s channel decisions to the emitter board.七颗 16 路 TLC5940 组成 112 路驱动链。串行数据、时序与输出消隐,把 MCU 的通道决策送到发光板。

109-channel emitter · emitter_7bank109 路发光板 · emitter_7bank

Carries 218 discrete LED packages arranged as 109 series pairs. Board geometry, LED angle and the enclosure determine the optical footprint that must later be measured.安装 218 颗分立 LED,组成 109 组串联通道。板上位置、灯珠角度及外壳共同决定后续必须测量的实际光斑。

Independent guard · independent_guard独立保护板 · independent_guard

Provides a hardware permission/disable path alongside software control. Its watchdog, fault behavior and real turn-off response must be checked on the assembled hardware.在软件控制之外提供硬件许可/禁止输出路径。看门狗、故障行为及实际关灯响应,需要在装配后的硬件上验证。

Main power · power_main_series_characterization主电源板 · power_main_series_characterization

Brings together the USB-C input, charging/system-power paths and power-status interfaces. Source capability, load allocation and battery charging must be reviewed as one system.承接 USB-C 输入、充电/系统供电路径及电源状态接口。适配器能力、整机负载分配和电池充电,需要作为同一个系统核算。

Vision carrier · vision_carrier_display_aux视觉载板 · vision_carrier_display_aux

Connects the RV1106/Core1106 processing module with the camera, display and auxiliary interfaces. Linux preprocessing, inference and HMI integration belong to this side of the architecture.连接 RV1106/Core1106 处理模组与相机、显示和辅助接口。Linux 图像预处理、推理和界面集成属于这一侧的职责。

What do “109 channels” and the power figures mean?109 路、218 颗 LED 和功耗分别指什么?

Channel count is not LED-package count通道数不等于灯珠封装数

Each channel has one 360–370 nm LED and one 400–410 nm LED in series. The same current passes through both; this circuit cannot independently pulse the two bands. The last three of the 112 driver outputs have no emitter load and remain disabled.每路由一颗 360–370 nm LED 与一颗 400–410 nm LED 串联,两颗流过同一电流,本电路不能分别给两个波段独立脉冲。112 路驱动中的最后三路没有发光负载,保持关闭。

An electrical estimate, not optical output电功耗估算与光输出是两件事

The archived review calculates a nominal 39.06 mA per channel. For all 109 channels on, that is about 4.26 A; at the 9.0 V EVT rail target, about 38.3 W on the LED rail. These are nominal accounting figures, not an approved operating profile or a measured limit.归档审查采用每路名义 39.06 mA 计算。109 路同时导通时约为 4.26 A;按 9.0 V EVT 灯路目标电压估算,灯路约为 38.3 W。这些是名义功率核算,不是已批准的工作曲线或实测限值。

The 38.3 W estimate includes the LED-rail load and driver conduction loss, but excludes converter loss, logic/switching overhead, camera, display, fan, MCU and battery charging. PWM can reduce average demand while simultaneous peak current still matters. Adapter power, battery runtime, temperature rise and curing performance therefore need separate measurements.上述 38.3 W 包含灯路负载与驱动导通损耗,但不含转换损耗、逻辑/开关额外损耗、相机、显示、风扇、MCU 及电池充电。PWM 可以降低平均负载,但同时导通的峰值电流仍须单独核对。因此,适配器功率、电池续航、温升及固化效果都需要另外测量。

How vision becomes a channel map.视觉识别怎样转换为通道许可?

Recognition answers “where is the nail?” Calibration answers “where does this channel actually illuminate?” Both are required. A model file and an offline score alone do not establish accuracy with the final camera, lens or hand position.识别回答“甲面在哪里”,标定回答“这一通道实际照到哪里”,两者缺一不可。只有模型文件和离线分数,并不能证明最终相机、镜头与手部位置下的准确性。

  1. Keep one coordinate contract统一坐标合同

    The measurement importer uses the 192 × 144 full-frame model coordinate grid. This is a model-space contract, not a claim about camera sensor resolution. Cropping, rotation, mirroring and preprocessing must match the archived model/pose identity.测量导入器使用 192 × 144 的全画幅模型坐标网格。这是模型空间的约定,不代表相机传感器分辨率。裁剪、旋转、镜像和预处理必须与归档模型/姿态身份一致。

  2. Measure each series pair逐路测量串联灯对

    Capture each channel’s combined illuminated area, including both wavelength contributions and scatter. The two LEDs cannot be treated as independently commanded sources; band-specific measurements need a separately validated measurement method.每路应测量两颗 LED 合成的照射区域,包含两个波段的贡献和散射。不能假设两颗 LED 可以分别受控点亮;分波段测量需要另行验证的测量方法。

  3. Compare envelopes, not centers比较光斑包络而非中心点

    Map the complete footprint into the selected nail region, with margins for optical spread, hand height, camera alignment and motion. Stable frames and confidence checks precede a lighting decision.把完整光斑映射到甲面有效区域,考虑光学扩散、手部高度、相机对准和移动余量;稳定帧与置信度检查在照射决策之前完成。

  4. Review measurements independently独立审查实测结果

    The public 109-channel template contains no actual measurements. Its importer checks structure and identity using synthetic test data; measured_and_approved and coverage_complete remain false, so the current runtime rejects the resulting unapproved candidate.公开的 109 路模板没有实际测量数据。导入器用合成数据检查结构与身份,measured_and_approved 和 coverage_complete 仍为 false,当前运行时会拒绝生成的未批准候选。

  5. Bind calibration to the assembled design把标定绑定到装配版本

    After measurement and engineering acceptance, retain the camera, model, board and optical geometry identities with the calibration. Changes to LED selection, camera position or the enclosure can invalidate the measured mapping.实测和工程验收完成后,标定应保留相机、模型、板卡及光学结构身份。更换灯珠、移动相机或改变外壳,都可能使原先测得的映射失效。

Who can start, stop and report a fault?谁负责启停、计时和故障处理?

The operator bridge sends requests; it does not grant qualification. The engineering modes are 9, 15 and 20 seconds. These intervals describe the implemented controller modes and are not gel-specific curing recommendations.操作桥接发送请求,不授予运行资格。工程模式包含 9、15、20 秒,这些时间表示已实现的控制器模式,并非针对某种甲油胶的固化建议。

IDLE待机
Outputs are off; the operator can request a mode or a new start.输出关闭,可请求选择模式或重新启动。
ARMING准备
Required system and cooling conditions must be ready before the sequence proceeds.进入后续流程前,所需系统与散热条件必须就绪。
QUALIFY资格检查
Fresh visual input and the local permission conditions must satisfy the control sequence.新鲜视觉输入及本地许可条件必须符合控制顺序。
RUNNING运行
The MCU owns the countdown and channel output; a stop or disqualifying condition removes permission.MCU 掌握倒计时和通道输出;停止或条件失效会撤销许可。
DONE完成
The timed interval has ended and outputs are off.计时时段结束,输出关闭。
FAULT故障
A failed condition is latched; restoring the condition does not automatically restart light.锁存失效条件;条件恢复不会自动重新照射。

Current MCU and vision sources use paired V4 messaging. Epoch, nonce, calibration identity, reserved mask bits and CRC are checked. Stop and mode requests carry a zero lighting mask. Physical button rules take priority, and a queued UI request is not the same as MCU acceptance.当前 MCU 与视觉源码使用配对的 V4 报文,检查 epoch、nonce、标定身份、掩膜保留位及 CRC。停止与模式请求携带全零照射掩膜。实体按键规则优先,界面显示请求已排队不等于 MCU 已接受。

The documented challenge lease is 50 ms, with separate link/processing budgets. It is a software design deadline, not a measured end-to-end turn-off time. Real camera/NPU scheduling, UART timing and physical output-disable response still need target-hardware tests. The public engineering firmware retains its qualification locks.协议记录的挑战租约为 50 ms,并分别规定链路与处理预算。这是软件设计期限,不是已经测得的端到端关灯时间。实际相机/NPU 调度、串口时序和硬件禁止输出响应仍需目标机测试;公开工程固件继续保留资格锁。

Which download should you open first?资料应该怎样下载和阅读?

Use the complete collection for integration and cross-package checks. The six smaller ZIPs are convenient topic views; they are not extra boards or independent products. Keep source identities, licenses and the file index with the files you share.整机集成和跨包检查优先使用完整资料包。六个较小 ZIP 便于按专业阅读,不代表额外板卡或独立产品。转交资料时,应同时保留源身份、许可说明和文件目录。

Hardware engineer硬件工程师

Start with CAD, the one-set BOM and each board’s separate CAM directory. The 906 fitted positions include the 218 LEDs; BOM quantities are net quantities, not supplier MOQ or purchasing quantities. Read the BMS U3 correction together with the archived design.先看 CAD、一套净量 BOM 和逐板独立 CAM 目录。906 个实装位号已包含 218 颗 LED;BOM 数量是净用量,不是供应商 MOQ 或采购数量。BMS U3 勘误应与归档设计一起阅读。

Software engineer软件工程师

Start with Software/MCU, Software/Vision and Linux integration notes. Keep MCU, vision and calibration identities paired. Linux overlay sources are included; complete boot images and proprietary vendor runtime are not distributed here.先看 Software/MCU、Software/Vision 和 Linux 集成说明,保持 MCU、视觉与标定身份配对。包内提供 Linux 覆盖层源码,不分发完整启动镜像或厂家专有运行库。

Mechanical / harness engineer结构与线束工程师

Review Mechanical and Harness together with Harness/R6-addendum/READ-FIRST.txt. The addendum updates binding information without issuing a new PCB revision. Check contact orientation, wire order, lengths, crimp process and continuity on real assemblies.结合 Mechanical、Harness 与 Harness/R6-addendum/READ-FIRST.txt 阅读。增补文件更新绑定信息,不代表发布了新版 PCB;接触方向、线序、长度、压接工艺及导通仍需在实际装配件上核对。

Reviewer / manufacturing partner评审与制造合作方

Start with the public README, file-index.json and SHA256SUMS.txt, then the board-specific records and test-access notes. Open each KiCad board as its own project and keep its project-relative libraries.先阅读公开 README、file-index.json 和 SHA256SUMS.txt,再看逐板检查记录及测试接入说明。每块 KiCad 板作为独立项目打开,并保留项目相对路径的库表。

For an offline integrity check, extract the complete ZIP and run python3 VERIFY-PUBLIC.py from its root. Follow the README for host-test dependencies and paths. These checks verify files and software behavior; they do not drive the device or certify an assembled unit.做离线完整性检查时,先解压完整 ZIP,再在根目录执行 python3 VERIFY-PUBLIC.py。主机测试的依赖和路径按 README 准备。这些检查验证文件与软件行为,不会因此证明设备动作或整机合格。

What is documented, and what still needs measurement?哪些已有资料,哪些仍待实测?

Available in the published collection公开包已提供

Editable board/schematic files, board-specific fabrication exports and BOMs; MCU and vision source, model/preprocessing identities, host checks, a calibration import format, harness bindings, mechanical context and Linux integration notes.可编辑板卡与原理图、逐板加工输出和 BOM;MCU 与视觉源码、模型/预处理身份、主机检查、标定导入格式、线束绑定、结构参考与 Linux 集成说明。

Remaining product acceptance整机仍需完成的验收

Factory DFM for the actual stackup and copper, final screen/FPC and harness first articles, target BSP/camera/NPU/display/UART integration, measured 109-channel optics and motion response, thermal/power/charging/fault tests, and assembled-unit checks.实际叠层和铜厚下的工厂 DFM、最终屏幕/FPC 与线束首件、目标 BSP/相机/NPU/显示/串口联调、109 路光学和移动响应实测、热/电源/充电/故障测试及整机装配检查。

The page and downloadable files show the engineering implementation and its record trail. They do not establish prototype performance, regulatory compliance, a validated curing recipe or manufacturing release. Record acceptance against the exact hardware, software and calibration revision used for the test.本页与下载文件展示工程实现及其证据链,不代表样机性能、合规认证、已验证固化配方或制造放行。验收记录应绑定测试时实际使用的硬件、软件与标定版本。

Questions that usually need a clearer answer.几个容易混淆的问题。

Why use a separate MCU when Linux can run the camera and screen?Linux 能运行相机和屏幕,为什么还需要独立 MCU?

Camera inference, graphics and storage have different scheduling demands. The design separates those tasks from local timing, driver output and fault handling. Separation makes responsibilities explicit; the actual deadlines still require hardware measurement.相机推理、界面绘制与存储的调度需求不同。该设计把它们与本地计时、驱动输出和故障处理分开,使责任清楚;实际期限是否满足,仍须通过硬件测量确认。

Does 109-channel control guarantee that only the nail is illuminated?109 路独立控制,是否就能保证只照到甲面?

Channel count gives control granularity. Selective illumination also depends on optical spread, geometry, calibration, segmentation confidence and hand motion. The current public measurement template is unapproved, so this result has not been established for the assembled product.通道数提供控制颗粒度;选择性照射还取决于光斑扩散、几何关系、标定、分割置信度和手部移动。当前公开测量模板未获批准,不能据此宣称整机已经达到这一效果。

Can the 365 nm and 405 nm LEDs be dimmed separately?365 nm 与 405 nm 灯珠能分别调光吗?

Not in this series-pair circuit. The two devices share the channel current and command. Independent spectral control would require an electrical redesign and new power, optical and calibration review.当前串联灯对电路不能分别调光,两颗共用该通道的电流与命令。要独立控制两个波段,需要修改电气设计,并重新审查功耗、光学和标定。

Can the design be built directly from the downloads?下载后可以直接交工厂生产吗?

The files support engineering review and preparation. Manufacturing still needs board-by-board DFM, approved material and assembly choices, harness/screen matching and a defined test plan. Nominal CAD geometry and host-test passes do not replace those steps.这些文件可用于工程审查和打样准备。制造仍需逐板 DFM、物料与装配选项确认、线束/屏幕匹配及明确的测试方案。名义 CAD 几何和主机测试通过不能替代这些步骤。

Source notes for this explanation本节说明依据

The following paths are inside the complete R6 collection. They describe the archived reference; later overlay notes are kept separate from the original source identities.以下路径位于完整 R6 资料包中,描述归档参考版本;后续覆盖层说明与原始源身份分别保留。

  • README-public.md
  • Evidence/LED-channel-pairing/READ-FIRST.txt
  • Evidence/LED-power-accounting/READ-FIRST.txt
  • Calibration/Paired-LED-import/READ-FIRST.txt
  • Software/Vision/操作请求接口与V4协议.txt
  • Software/READ-FIRST.txt
  • Software/MCU/README.txt
  • CAD/DISPLAY-HARNESS-LOGICAL-CONTRACT.json
  • Harness/R6-addendum/READ-FIRST.txt
  • Linux/README-integration.txt
  • Evidence/Factory-feature-review/工厂加工能力待确认清单.md
  • Manufacturing/Test-access/FACTORY-TEST-READ-FIRST.txt

109 channels. Eight boards. One technical collection.109 路照射,8 块电路板,一套技术资料。

Explore editable circuits, firmware, vision algorithms and assembly interfaces, with source identities and per-file checksums.查看可编辑电路、固件、视觉算法及装配接口,附源文件身份和逐文件校验值。

One set contains 906 fitted component positions. The one-set BOM includes the BMS U3 ordering-code correction. Vendor SDK components are referenced through official sources; retain the included license notices.一套包含 906 个实装位号。BOM 已附 BMS U3 订货号勘误;厂家 SDK 组件提供官方获取入口,使用时请保留附带许可说明。

Battery protection电池保护板

R6 Battery protection top copper and silkscreen CAD view
Show bottom copper查看底层铜箔R6 Battery protection bottom copper and silkscreen CAD view
KiCad drawing · click to view original SVGKiCad 图纸 · 点击查看 SVG 原图

Local controller本地主控板

R6 Local controller top copper and silkscreen CAD view
Show bottom copper查看底层铜箔R6 Local controller bottom copper and silkscreen CAD view
KiCad drawing · click to view original SVGKiCad 图纸 · 点击查看 SVG 原图

Display adapter显示转接板

R6 Display adapter top copper and silkscreen CAD view
Show bottom copper查看底层铜箔R6 Display adapter bottom copper and silkscreen CAD view
KiCad drawing · click to view original SVGKiCad 图纸 · 点击查看 SVG 原图

Seven-bank LED driver七组 LED 驱动板

R6 Seven-bank LED driver top copper and silkscreen CAD view
Show bottom copper查看底层铜箔R6 Seven-bank LED driver bottom copper and silkscreen CAD view
KiCad drawing · click to view original SVGKiCad 图纸 · 点击查看 SVG 原图

109-channel emitter109 路发光板

R6 109-channel emitter top copper and silkscreen CAD view
Show bottom copper查看底层铜箔R6 109-channel emitter bottom copper and silkscreen CAD view
KiCad drawing · click to view original SVGKiCad 图纸 · 点击查看 SVG 原图

Independent guard独立保护板

R6 Independent guard top copper and silkscreen CAD view
Show bottom copper查看底层铜箔R6 Independent guard bottom copper and silkscreen CAD view
KiCad drawing · click to view original SVGKiCad 图纸 · 点击查看 SVG 原图

Main power主电源板

R6 Main power top copper and silkscreen CAD view
Show bottom copper查看底层铜箔R6 Main power bottom copper and silkscreen CAD view
KiCad drawing · click to view original SVGKiCad 图纸 · 点击查看 SVG 原图

Vision carrier视觉载板

R6 Vision carrier top copper and silkscreen CAD view
Show bottom copper查看底层铜箔R6 Vision carrier bottom copper and silkscreen CAD view
KiCad drawing · click to view original SVGKiCad 图纸 · 点击查看 SVG 原图

Your beauty-electronics project

Define your next nail-lamp controller.

Share the lighting concept, camera and screen requirements, power source, enclosure dimensions and expected quantity. Start with a product brief or attach your existing design files.

Files are optional to start. The inquiry link includes this project reference.