OPEN BLUETOOTH REALITY · REFERENCE CASE 002 · ZX-D36 / UART-TTL · 2026-06-09
TTL DATA.
WIRELESS REALITY LINK.
A small UART/TTL byte stream crossed a mature BLE bridge, reached another UART endpoint in both directions, survived a power cycle through automatic binding, and later reached an iPhone notification path. The value is not a new Bluetooth protocol; it is a low-cost reusable way to make ordinary serial devices addressable to GenAI work.
这次成功比“蓝牙已连接”更重要：一端 TTL/UART 发出的原始数据，经 BLE 传输后，在另一端重新成为 UART 数据；随后又证明绑定、重启自动重连和手机端 Notify。它是非常小、非常便宜、但可继续组合的 Reality Brick。
PUBLIC C0-001 · Recovered chat evidence + vendor-document research baseline. No supplier SDK/source bundle is republished here.
HISTORICAL ENGINEERING PASS · 2026-06-09
ZX-D36 master → BLE → ZX-D30 slave → UART, then back again.
Accepted physical/data path
Windows / COM6 → ZX-D36 UART → BLE → ZX-D30 → COM7, and the reverse direction, both with exact text payload readback.
PERSISTENCE PASS
Connection became a reusable link, not a one-time manual demo.
The recovered session records the D36 binding sequence against the D30 MAC:
AT+BONDMAC=C8478100274C → AT+BONDMODE=0 → AT+AUTOCON=2
After restart / power cycle, the pair automatically reconnected and the LEDs remained continuously on, matching the connected-state behavior documented for the module family. This turns “manual connection worked once” into a much more useful capability: a small serial link that can return after power loss without a human repeating the scan sequence.
PHONE PATH · LATER SAME SESSION
PC UART data also reached an iPhone BLE subscriber.
The later test used the ZX-D30 as BENNY_BLE_001. LightBlue on iPhone subscribed to characteristic FFE1; the HP Windows PC sent HELLO_FROM_PC into the D30 serial port, and the iPhone displayed the notification. A final reverse iPhone→TTL/PC test is not recorded as completed, so the public acceptance state remains one-way for this phone branch.
WHAT THE ZX-D36 DOCUMENTS ADD NOW
The rushed experiment can now be turned into a reproducible baseline.
THE VOLTAGE / WIRING PITFALL
“TTL module” does not mean every pin accepts 5 V.
REPRODUCIBILITY GATES
Future engineers should prove one layer at a time.
Power + level
Identify bare module vs carrier board; verify supply and 3.3 V UART logic before connecting.
UART PASS
9600 / 8N1 baseline; send AT with the documented line ending and confirm OK.
Role + scan
Set one endpoint to master, scan and record MAC/name/RSSI instead of guessing identity.
BLE connected
Verify CONNECTED / STATE / LED evidence separately from payload data.
Transparent data
Send a unique payload in each direction and read back the exact bytes on the opposite UART.
Restart persistence
Bind, power-cycle and prove automatic reconnection before calling the link reusable.
Phone / browser
Prove the GATT characteristic path separately; do not infer it from module-to-module transparent success.
MCP adapter later
Only after UART/BLE Reality is stable should a Local Edge expose bounded higher-level tools to AI.
SOURCE PACK · PRIVATE RESEARCH INVENTORY
The uploaded vendor bundle is useful for continuation, but not a public mirror.
The supplied ZX-D36 archive contains Android test apps, BLE/SPP sample source packages, iOS BLE reference source, a WeChat mini-program package, Altium/PADS PCB footprints, 8051 and STM32 UART examples, a JavaScript serial example and vendor debug tools, plus the manuals. HSIMC records the archive hash and inventory privately so later engineers know what existed without silently republishing third-party source or binaries.
Uploaded archive SHA256
dc83b7102e79b716808cf97cf546deefe3b8e746b6b974dec14b76e3bc9bf7e6
WHY THIS MATTERS TO GENAI
UART is one of the cheapest bridges from old physical devices into new AI work.
Thousands of mature sensors, instruments, controllers and embedded boards already speak UART/TTL. They do not need new AI silicon. A small Bluetooth bridge can make their byte stream locally wireless; a phone, browser or Local Edge can then translate those bytes into a bounded capability for Work, Evidence and future MCP exposure.
Reusable pattern
Legacy UART Device → 3.3 V TTL → Bluetooth Bridge → Local Adapter → Structured State / Tool → LLM or e-Person → Human Acceptance.
The 2026-06-09 D36↔D30 success is reconstructed from the original chat's user-observed test results; the raw PowerShell/serial log file has not yet been independently recovered into the public package. The uploaded ZX-D36 manuals validate the D36 feature/configuration model, but do not document the historical ZX-D30 firmware. Cross-model behavior must therefore remain a historical reference, while future reproducibility should record each endpoint's exact firmware, voltage, UART settings, service/characteristics and payload readback.