# SIX / 01 — RICHMAP original drone

Created 2026-09-23 KST. This is an original, explorable educational concept, not a reconstruction of a branded drone.

## Design provenance

No commercial drone photographs, product CAD, downloaded drone meshes, brand logos or proprietary design files were used as visual design references or embedded assets. The longitudinal sculpted metal shell, six tapered carbon arms, paired close-coupled landing rails, forward optical pod and component layout were authored in `model.js`. Common multirotor engineering principles are shared with the field; this is not a claim that every individual feature is unprecedented or that registered designs worldwide have been exhaustively searched.

All meshes, carbon weave, roughness patterns, circuit artwork, labels, process fixtures and explanatory animations were written for this scene. The studio lighting environment reuses the project's independently authored light-panel generator. No generated or third-party bitmap photograph is presented as a real component.

## Public primary references

| Source | Used for | Not used |
| --- | --- | --- |
| [Hexcel, Prepreg Technology](https://www.hexcel.com/wp-content/uploads/2026/01/Prepreg_Technology-1.pdf), prepreg processing sections | Layup, release layer, breather, vacuum bag and cure roles | No figures, material recipes, stacking schedules or brand geometry copied |
| [Haas, End Milling Guide](https://www.haascnc.com/Community/haas-tooling-tips/guide-to-end-milling.html) | Material removal, contouring, machining and workholding principles | No toolpaths, equipment geometry or manufacturing instructions copied |
| [maxon, Introduction to Brushless DC Motors](https://www.maxongroup.com/medias/sys_master/8803451338782.pdf?attachment=true) | Stationary windings, permanent-magnet rotor, bearings and balancing | No proprietary winding architecture or CAD; the displayed outrunner is an independently authored example |
| [JLCPCB, SMT Assembly Process](https://jlcpcb.com/blog/smt-process-in-pcb-assembly) | Paste printing, placement, reflow and inspection sequence | No photographs, PCB layouts, machine code or brand production data |
| [PX4, Multicopter Configuration](https://docs.px4.io/main/en/config_mc/) | Geometry, sensor orientation, calibration and setup concepts | No firmware, certified configuration or actual calibration data |
| [PX4, Actuator Configuration and Testing](https://docs.px4.io/main/en/config/actuators) | Motor/output mapping, spin direction and propeller-free motor tests | No downloaded airframe design or claim that this concept is supported by PX4 |

These public references support engineering explanations. Their public availability is not treated as a license to redistribute their diagrams, images or code. Links are provided; the original reference assets are not included.

## Authored dimensions and physical scope

- Model coordinates are in meters. Six rotor centers lie on radius 0.27 m; opposite centers are 0.54 m apart. Propeller radius is 0.105 m. Adjacent center distance is 0.27 m, leaving 0.06 m between ideal rotor disks in the assembled plan view.
- The revision-2 canopy is approximately 0.293 m long and 0.140 m wide. Arms, fixtures, shell wall, cells, PCB, fasteners and optical details use authored proportions. They are not measured commercial parts.
- Blade thickness, twist, shape, stiffness and center of pressure are explanatory choices, not aerodynamic design results. No CFD, structural, thermal, fatigue, vibration, EMC or flightworthiness validation has been performed.
- The physical example uses assumed mass 1.8 kg and thrust coefficient k=8.5e-6 N·s²/rad². Ideal rotor thrust T=kω² is used to calculate illustrative RPM from force allocation. Rotor disks have alternating spin direction. Fore/aft and lateral force differences illustrate moments.
- Body attitude and height remain explanatory animations, not integrated flight dynamics. In high-speed mode rotor angles integrate the illustrative RPM (about 5,619 at nominal hover), with an authored optical exposure disk and ghost blades to avoid frame-rate aliasing. Exposure appearance is an approximation, not an aerodynamic computation. A separately labelled 60 RPM inspection mode reveals blade shape. Manufacturing scenes retain their own slow clock. Pausing restores physical blades; disassembly and calibration do not spin the propellers.
- The power module shows six hypothetical pouch cells and protection/support features. It does not specify a validated battery, safe series wiring, charger or cell-manufacturing process. PCB traces are non-functional authored graphics.

## Manufacturing scene scope

1. Design: parts separate to reveal assembly relationships. It does not solve structural constraints.
2. Composites: eight enlarged illustrative plies, release layer, breather and bag approach a tool. Layer count/thickness and consolidation travel are not a prescribed laminate. No actual pressure, thermal or cure solution is calculated.
3. Metal: a cutter moves above a stock/finished-part transition. This is a conceptual machining sequence, not subtractive geometry simulation or executable CNC code.
4. Motor: progressively visible windings and separated stator/rotor/bearings illustrate construction. The coil path is original and simplified. Pole/slot choice is illustrative.
5. Electronics: placement and schematic reflow/inspection zones represent assembly on an already fabricated PCB. PCB etching and semiconductor manufacture are upstream processes. No actual solder profile or inspection pass result is invented.
6. Final assembly: named parts move back to their attachment positions. Fastening, insulation and access are represented, not certified.
7. Calibration: propellers are hidden for the bench sequence; displayed axes and poses explain orientation. No sensor samples or successful calibration are fabricated.
8. Validation: test categories and an illustrative flight animation. This is not evidence that a physical SIX / 01 has been manufactured or flown.

## Editable files and libraries

- `model.js`: original named meshes, materials, part groups and process assemblies.
- `data.mjs`: parts, process descriptions, source links and ideal force allocation.
- `app.js`: rendering, selection, camera, timelines, process navigation and GLB export.
- `index.html`, `style.css`: responsive interface.
- GLB export writes current visible geometry in meter coordinates, excluding explanatory thrust arrows and optical rotor blur. Physical blades are restored in the export even while the fast rotor preview is running. It does not export JavaScript behavior or imply manufacturing-ready CAD.
- Three.js and bundled addons: MIT, `../cuda-atlas/vendor/LICENSE-three.txt`.
- Pretendard Variable: SIL OFL, `../supercar-concept/assets/LICENSE-Pretendard.txt`.

No affiliation or endorsement by the referenced organizations is implied.