Explore historical accessibility and field-operation projects, clinical-display concepts and new ODM workflow evaluation. Confidant and Falcon 007 Pro are historical references, not overseas-ready products, and no test samples are available. Similar applications require a new ODM project with NRE, development time and project budget.
Telecommunications facility — illustrative scene context.
Each workflow distinguishes product or architecture evaluation from historical development experience. Confidant and Falcon 007 Pro require new ODM development for similar applications; neither provides an overseas-ready product or test samples. Configuration, software, validation, compliance and acceptance criteria are scoped per project.
2021 mainland-China assistive project; historical reference for new ODM development.
Confidant →Historical face-recognition and vehicle-traffic-recognition development reference.
Falcon 007 Pro →Project-configured near-eye display for compatible clinical video workflows.
BB Medical →Historical Type-C audio/video configuration for new ODM evaluation.
Falcon 007 Pro →Historical optional thermal-view configuration; similar applications need new ODM development.
Falcon 007 Pro →Display-free ODM evaluation for robotics and VLA training datasets.
XY-DC Reference Architecture →Confidant is a historical custom AI assistive project developed in 2021 for a disabled persons' federation in mainland China, for mainland-China use. Its historical configuration combines a front camera, two front-facing obstacle sensors, a GPS module/antenna and a handheld controller, with scene descriptions, spoken Q&A, obstacle alerts, route prompts and selected recognition tasks. It is not an overseas-ready product and no test samples are available. Similar applications require a new ODM project with NRE, development time and project budget. Discuss a new assistive ODM project.
View historical project reference
Two front-facing obstacle sensors support spoken alerts; no numeric range is published from the supplied sheet.
The vision-language assistant can describe a scene and respond to spoken questions; outputs can be incomplete or inaccurate.
Printed text, common objects and selected currency can be recognised under suitable conditions.
Spoken route and deviation prompts depend on map coverage, positioning and connectivity.
Optional recognition is limited to enrolled contacts and requires consent, privacy controls and applicable-law review.
Training, user testing, data governance and project acceptance are required for each deployment.
Historical Confidant OCR and obstacle functions are not a plug-in SDK for K900; a similar solution requires separate architecture, integration and validation work. Confidant is an assistive aid. It does not replace a white cane, guide dog, orientation-and-mobility training or user judgement, and must not be used as the sole navigation or safety aid.
Historical field-operation project reference, including face-recognition and vehicle-traffic-recognition development experience. No overseas-ready product or test samples. Similar applications require a new ODM project with NRE, development time and project budget. Historical configurations included near-eye display, first-person capture and linked-compute workflows. New capture, networking, storage and coordination functions require their own hardware, software and acceptance review. Discuss a new field-operation ODM project.
View historical project reference
34° FOV with ≥82% reference optical transmittance.
First-person capture for approved documentation and assistance workflows.
Supplier-sheet reference: 20–30 face captures/sec and 3–5 recognition results/sec.*
Type-C linked terminal integration; application and network dependent.
External 5000mAh battery; more than 4 hours under reference full-function conditions.*
Enabled only for an approved project, region, customer and lawful use case.
*Throughput and runtime values come from the supplied product sheet and are reference figures, not guarantees. Actual results depend on the model, integration, workload, environment, network, battery condition and test method. Recognition and sensitive-data functions require project, regional, privacy, legal and customer review.
For compatible ultrasound and other video sources, BB Medical brings a 1920×1080 @ 60 Hz reference feed into the wearer’s line of sight. The source, adapter, cable, user fit, intended use and regulatory boundary must be verified in the final project configuration.
1920×1080 @ 60 Hz Micro-OLED; confirm final source timing and image path.
Product-sheet field of view; confirm fit and usable image area on the final sample.
Excludes the data cable; fit and comfort require user evaluation.
<20 ms in the supplied sheet; measure the complete final signal chain.
Rear support, tension control and display-arm position require individual fit checks.
>19 mm eye relief, ≥15×9.5 mm eyebox and 500 nit eye-side brightness.
A project-configured display platform, not a stand-alone diagnostic or treatment device. Intended use, compatibility, certification or registration status, and market authorization must be confirmed with official project documents.
The historical Falcon 007 Pro configuration used a Type-C linked phone, terminal or external compute module for first-person capture and remote-coordination development. It is not an overseas-ready product and no test samples are available. Similar applications need a new ODM project with NRE, development time and budget; application, network, security, storage and acceptance requirements must be reviewed for the new integration.
Project-scoped video and audio through the selected terminal and application.
Connection to an approved phone, terminal or external compute module.
Application and network integration for approved remote-assistance workflows.
Storage, access, retention and security requirements defined during project scoping.
The historical Falcon 007 Pro sheet illustrates night-search support, first-person capture and an optional 220×160 thermal module. This is development reference material, not an overseas-ready product or a source of test samples. A similar solution requires new ODM work, NRE, development time and project budget; operating range, accuracy, visibility, environmental suitability and procedures need new validation.
220×160 plug-in module; project configuration and validation required.
1.3MP reference camera for approved documentation and assistance workflows.
Type-C linked phone, terminal or compute module selected by the project.
Environment, user training, data handling and acceptance method defined before use.
Display-free is the point. Robotics teams, dataset operators and vision-language-action teams can scope egocentric data capture around the XY-DC Reference Architecture. This display-free ODM evaluation direction has no waveguide, projector or near-eye display; it is separate from the eight product entries and two historical project references.
Evaluate rigidly mounted forward stereo cameras, sensor-level trigger alignment and the ISP/MIPI integration path. Define how frame timestamps and inertial samples relate to the capture clock. Document the sensor and host interfaces, then measure synchronization error and timestamp behavior on the agreed prototype.
Define intrinsics, extrinsics, distortion and rectification outputs, serial-number association and machine-readable delivery. Scope the calibration station, tooling and line integration as project work. Agree calibration procedures, output formats, acceptance criteria and repeatability checks before committing production delivery.
Evaluate wrist, body-worn or tool-mounted companion capture modules as separate development items. Define the relationship between head-unit and companion clocks, reconnection behavior and cumulative drift. Measure alignment and drift across the intended recording duration and wireless conditions; no synchronization accuracy is published.
Model concurrent camera capture, encoding, storage and periodic upload against the requested working-shift duty cycle. Review battery architecture, heat paths, fit and the resulting weight budget together. Validate recording duration and thermal behavior under the agreed workload and environment before confirming device specifications.
Evaluate an externally visible mechanical camera shutter and a mechanical microphone mute. Define how each control changes capture state and how the wearer and people nearby can verify that state. Review the physical controls and capture-state behavior alongside the project owner's consent, retention and intended-use requirements; hardware alone does not establish deployment compliance.
Evaluate secure-element signing at capture, key ownership, controlled provisioning and verification by the receiving system. Include relevant cryptographic and intended-use review in project definition. Agree the threat model and recording-integrity checks, then validate the signing and verification path on the selected hardware and software.
The six areas above are proposed engineering requirements. Sensor selection, synchronization accuracy, calibration outputs, sustained runtime, privacy hardware and signing support require feasibility review and project validation. No fixed device specification or production-readiness claim is published for this architecture.
C100 remains the camera + dual-eye display platform with Android apps running on the glasses and two connectivity modes: direct Wi-Fi through a compatible router or phone hotspot, or BLE through a phone app to VLM/LLM/cloud services. In BLE mode, image/audio travels to the phone app and results return through the app and BLE for glasses audio playback and display; LLM/VLM inference runs off-device. C100 is at EVT3 with functional CNC prototypes and customizable industrial design; contact SmartXY to request the SDK development package. C100 Android SDK/Demo availability and paid development policy. XY-DC addresses a separate display-free capture requirement.
Enterprise and consumer projects can share selected optics, compute, interaction and frame-engineering building blocks. What transfers depends on the approved platform, validation evidence, regional requirements and customer scope.
Define the use case, performance targets, data controls and required validation evidence.
Reuse only confirmed hardware, software and industrial-design modules. Historical Confidant and Falcon configurations are references for new development, not ready-to-use modules.
Revalidate configuration, certification, quality and manufacturability before launch.
Review application requirements and project-scoping notes for your industry or route to market. The linked guides do not change the product and historical-project boundaries described above.
Start with a measurable job. Review camera access, readable guidance, connectivity, software ownership and the evidence needed to accept an industrial pilot.
Read the project guideReview hearing and optical-channel requirements, acoustic scenarios and market compliance scope.
Read the project guideDefine the sport, display information and intended-use requirements for your project.
Read the project guideReview carrier-channel, app, service and bundle requirements.
Read the project guideDiscuss a product-appropriate OEM/ODM route. For applications similar to Confidant or Falcon 007 Pro, start a new ODM project with NRE, development time and project budget; historical units are not overseas-ready products or available as test samples. Agree the evidence, integration, validation and regional requirements before launch.