Connect the NWT Device
Use the Android tablet and OTG to complete serial detection, permission prompts and device handshake so the on-site hardware chain is verified before measurement.
This page explains preparation, normalization, signal recognition and record retention without exposing patient screenshots, treatment records or private identities.
把准备、采集、识别与留存整理成更易理解的流程分镜。
把异常提示、重测规则与下载说明放到显性位置,减少理解成本。
Workflow Steps
围绕临床现场的使用节奏组织流程卡片,让准备、采集、识别与留存形成一条清晰路径。
Use the Android tablet and OTG to complete serial detection, permission prompts and device handshake so the on-site hardware chain is verified before measurement.
Capture the empty-load Normalize baseline first, then compare and correct later live sweeps against that baseline to stabilize the measurement origin.
Collect spectrum curves continuously at a fixed step size, display the S-parameter trace in real time and automatically identify the resonance valley.
Convert resonance frequency into orthodontic force with the six-parameter sensor model, save locally first and then synchronize to Django on demand.
Protocol Layer
The public site does not expose clinical data. It explains preparation, collection, recognition and calculation as understandable workflow modules.
Handshake
Confirm the NWT device is ready before the rest of the measurement chain begins.
Sweep
The system reads sweep data in a fixed byte structure so later recognition starts from stable input.
Normalize
Baseline acquisition and delta processing provide a more stable reference for later spectrum recognition.
Force Model
Resonance frequency and calibration parameters are linked so signal recognition flows into readable force interpretation.
Safety & Boundary
A public workflow page should explain not only steps, but also when to recheck connection, redo baseline capture or return to support entry points.
Boundary
This page explains preparation, normalization, sweep recognition and record retention without exposing any real patient or treatment records.
Warning
Connection interruption, verification failure or abnormal results should always trigger visible guidance for field users.
Support
Download, FAQ and contact support belong to the public layer, while business processing remains inside authorized terminals and controlled systems.