VX-300R — Engine Design Dossier

The user wants me to "create a complete working model of a 300 CC engine" that is: - Ultra lightweight - Runs at very high RPM - For a drone - High endurance flight - Speeds above 400 km/h First, let me think about what the user actually needs. They can't physically build an engine through a chat interface. So what can I actually deliver? I'm a front-end engineer. The most valuable thing I can build is an interactive digital twin / engineering simulation model of this engine — a complete working *model* in the computational sense: a physics-based simulation with real thermodynamics, a live visualization of the engine running, adjustable parameters, performance curves (torque, power, BSFC vs RPM), thermal model, fuel consumption / endurance calculator for a 400+ km/h drone mission, and the engineering reasoning. So I should: 1. Clarify the engineering reality honestly — a 300cc engine spinning at very high RPM with ultra-light weight for a 400+ km/h drone. I should address the physics: to hit 400 km/h, you need serious power (drag scales with v³). Let me actually compute. Let me do the engineering math properly: **Aircraft/drone power requirement at 400 km/h (111.1 m/s):** Assume a sleek racing drone / record-attempt airframe: - Drag: P_req = 0.5 * ρ * v³ * Cd * A - ρ at altitude say sea level 1.225 kg/m³ - v = 111.1 m/s, v³ ≈ 1,371,742 m³/s³ - Assume CdA ≈ 0.035 m² (very slick: streamlined fuselage + wings; a streamliner like Speeder/race drones have CdA ~0.03-0.06) P = 0.5 * 1.225 * 1,371,742 * 0.035 ≈ 29,400 W ≈ 29.4 kW... plus propulsive efficiency ~75-80% for a prop at that speed, plus induced drag for a heavy craft. So shaft power needed ≈ 40-45 kW (54-60 hp) at cruise 400 km/h. Peak power for climb/accel: 55-65 kW (75-88 hp). A 300cc two-stroke can make ~75-95 hp at 9,500-11,000 rpm with tuned exhaust and injection. That's realistic: e.g., Vittorazi Cosmos 300 (300cc 2-stroke) makes ~100 hp. So a 300cc two-stroke at high RPM is the right architecture for this power density. Two-stroke makes sense for drones: fires every revolution, half the moving parts, light. With direct injection (DI) you fix the fuel scavenging loss problem → high endurance. High RPM: two-strokes rev high; with reed valve or DI + tuned pipe, 9,000-12,000 rpm achievable. Ultra light: 300cc two-stroke DI ~ 18-22 kg including injection. Aluminum/ forged pistons, crank, magnesium cases, Ti fasteners. High RPM considerations: mean piston speed. At 300cc single cylinder with 72mm bore × 73.7mm stroke (299.8cc), at 11,000 rpm: mean piston speed = 2 × stroke × N = 2 × 0.0737 × (11000/60) = 27 m/s — that's race engine territory (F1 ~26 m/s). Fine for a race 2-stroke with good materials. Actually let me compute displacement from bore/stroke properly: V = π/4 × B² × S. - B=76mm, S=66mm: π/4 × 76² × 66 = 0.7854 × 5776 × 66 = 0.7854 × 381,216 = 299,389 mm³ ≈ 299.4cc ✓ (oversquare = high rpm capable) At 11,500 rpm with stroke 66mm: MPS = 2×0.066×191.7 = 25.3 m/s. Power estimate for 2-stroke: BMEP for a well-ported DI 2-stroke ≈ 6-8 bar (2-strokes achieve maybe half-ish of 4-stroke BMEP because of scavenging losses; actually racing 2-strokes hit 7-9 bar BMEP... let's check: P = BMEP × Vd × N / (2×60) for 2-stroke (one power stroke per rev). With BMEP 7 bar = 700,000 Pa, Vd = 0.0003 m³, N=11500 rpm: P = 700000 × 0.0003 × 11500/120... wait formula: P (W) = BMEP(Pa) × Vd(m³) × (N/2 for 4-stroke, N for 2-stroke... per second). Power = BMEP × Vd × n_rev_per_sec / x where x=2 for four-stroke, 1 for two-stroke. So P = 700000 × 0.0003 × (11500/60) × 1 = 700000 × 0.0003 × 191.67 = 40,250 W ≈ 40.3 kW = 54 hp. Hmm, to get 75-95 hp from 300cc 2-stroke we need higher BMEP or higher rpm. Vittorazi Cosmos 300: 100 hp @ 10,000 rpm? Let me check BMEP needed: P=74.6 kW at 10000 rpm, P = BMEP × 0.0003 × 166.7 → BMEP = 74600/(0.0003×166.7) = 74600/0.05 = 1,492,000 Pa = 14.9 bar?? That seems too high for a 2-stroke. Hmm, actually maybe the Cosmos 300 makes ~100hp... Actually I recall Vittorazi Cosmos 300 makes about 100 hp at 10,500. That would be 14+ bar BMEP — plausible only for a very highly tuned racing 2-stroke (GP500 bikes made ~180hp from 500cc at 12,000+ rpm → 2 cylinders: per cylinder 90hp/250cc. BMEP = 90×745.7/(0.00025 × 12200/60) = 67113/(0.00025×203.3)=67113/0.0508 = 1.32 MPa = 13.2 bar). Yes! GP500 2-strokes ran ~13-14 bar BMEP. So it IS achievable with tuned exhaust, big transfer ports, etc. OK so 12-13 bar BMEP at 10,500-11,500 rpm for a racing DI 2-stroke 300cc single → ~70-75 kW (~95-100 hp). That's the design point. Torque: T = P/ω = 75000/(11500×2π/60) = 75000/1204 = 62.3 N·m. Weight: ultra-light 2-stroke 300cc single, magnesium crankcase, aluminum cylinder with Nikasil, forged piston, DI system. Comparable: Vittorazi Cosmos 300 is 17.4 kg dry (engine only). With DI add ~2 kg → ~19-20 kg. Power-to-weight: 75 kW / 20 kg = 3.75 kW/kg = ~4.6 hp/kg. Good. A tuned racing version could be 16-17 kg. Drone application: ducted prop vs open prop at 400 km/h. At 111 m/s, prop tip speeds get high; a small high-disc-loading prop with high pitch, maybe 2-blade 24-26 inch, driven at 1:1 or via reduction. Actually at 400 km/h, direct drive with small prop: airspeed 111 m/s; prop must have inflow ~ prop efficiency ~0.78-0.82 with good prop at high pitch. Small 26" (0.66m) prop at 11,000 rpm: tip speed = π×0.66×(11500/60) ≈ 39.7 m/s tangential + 111 axial → resultant huge, Mach issue: tip relative speed = sqrt(111² + 39.7²) = 117.9 m/s → M=0.34 at sea level — fine! Actually wait that's fine. But disc loading: thrust needed = drag + weight component. In level flight thrust ≈ drag = P_prop/v = 60kW×0.8/111 = 432 N. Disc area of 0.66m prop = 0.342 m². Ideal induced power = T×vi, vi = sqrt(T/(2ρA)) = sqrt(432/(2×1.225×0.342)) = sqrt(432/0.838) = sqrt(515.6)=22.7 m/s. Ideal power = 432×(111+22.7)... in forward flight the induced velocity drops; use momentum theory in forward flight — roughly fine. Anyway I don't need to over-derive; I'll build a calculator in the tool. **What to actually build:** An interactive "digital twin" engineering model — a single HTML file that contains: 1. **A live, animated engine cross-section** — canvas-rendered two-stroke engine with piston, crank, connecting rod, ports (transfer, exhaust, boost), reed valve or DI injector, spark — animating with the actual set RPM, showing port opening/closing via the port timing diagram. This is the signature visual. Maybe two views: cross-section animation + real-time P-V / pressure-crank angle diagram computed from an actual thermodynamic model (two-stroke ideal cycle with scavenging, tuned pipe pressure wave effects). 2. **Physics engine model**: - Torque/power curves vs RPM built from a quasi-static model: BMEP curve shaped by volumetric efficiency curve (which peaks where the tuned pipe is "on the pipe"), mechanical efficiency, etc. - Mean piston speed, piston acceleration, inertial loads - Heat/thermal: basic steady-state temps - Fuel consumption: BSFC curve, fuel burn at a given power setting, endurance calculation with a fuel tank size. 3. **Drone mission simulator**: - Inputs: airframe drag area CdA, prop diameter/pitch/efficiency, mass (airframe + engine + fuel), battery for avionics/electric systems, fuel capacity. - Compute required power at target speed (400+ km/h), engine throttle point, RPM, fuel burn, endurance time, range. Show whether the target speed is achievable and the max achievable speed. - Maybe a speed-vs-power curve. 4. **Parametric sliders**: bore/stroke (with displacement locked ~300cc?), compression ratio, RPM target, redline, exhaust tuned length (tuned pipe RPM!), etc. The tuned pipe length calculation is a lovely authentic detail: L = (Ed × Vs × 60)/(N × 4)... the classic formula for pipe length based on exhaust duration and speed of sound. 5. **Specification sheet**: full engineering spec — materials, dimensions, port timing (2-stroke port timing chart), ignition, DI system, cooling, weight breakdown table. Design language: I want this to feel like an engineering design-review console / technical drawing, not a generic dashboard. Aesthetic direction: dark "blueprint/CAD" environment — but avoid the generic dark dashboard feel. I could go for a technical-document aesthetic: off-white paper / engineering drawing sheet with grid, ink-line drawings, monospace/technical fonts, red accents like redline markings. That would be memorable and distinct: "engine design dossier" — like a race-engine build sheet with a live simulator embedded. Hmm — live canvas animation works beautifully on a dark background though. Alternative: A "test cell" aesthetic — dark charcoal, amber/ivory instrumentation, like an engine dyno control room. I need to avoid low-contrast gray-on-dark. I could do near-black background with warm ivory text and a single signature accent (signal orange/red for redline). Typography: a distinctive technical font. Available via Google Fonts: "IBM Plex Mono" + "Space Grotesk"? Or something more distinctive: "Archivo" / "Archivo Expanded"? For a technical drawing feel: "Sometype Mono", "JetBrains Mono", "IBM Plex Mono" are monos. Headline: maybe "Saira Condensed" / "Barlow Condensed" (motorsport feel) — condensed grotesque reads very "race engineering". Let me use "Big Shoulders" (condensed, industrial) for display + "IBM Plex Mono" for data. Big Shoulders Display is quite distinctive and industrial-motorsport. Layout idea (avoiding uniform card grids): - A large hero: left — huge title "PROJECT" + engine designation (e.g., "ST-300R" — call it something like "HELIOSTAT 300R"? Better: give it a plausible program name: "VECTOR 300" or "VORAX-300R"). Right/center — the live engine cross-section animation, big. - Below/beside: the live gauges (RPM tach with redline, power output, thrust, temps) integrated around the canvas like an instrument strip — but arranged asymmetrically, not equal cards. - A technical spec sheet in a two-column dossier format with rules and leader lines. - Performance curves section: torque/power vs RPM chart drawn on canvas with the current operating point marker, plus the pressure-volume diagram live. - Mission calculator: sliders + computed outputs (endurance, range, max speed) with a big readout. - Build notes: engineering narrative explaining the design decisions (why 2-stroke DI, tuned pipe length, materials, weight budget table). Interactivity plan (must all work): - Throttle control (drag or slider + keyboard) → engine RPM responds with realistic spool dynamics (inertia), power follows the torque curve, sound? I could add engine sound via WebAudio (synthesized engine hum whose frequency = firing frequency = RPM/60 for single-cylinder 2-stroke, with harmonics and noise). That's a fantastic signature moment — a throttle that revs the engine with sound. Must have a mute toggle and start only on user gesture (autoplay policy). I'll add a "START ENGINE" button that starts audio + animation. - Tune the pipe: a slider for exhaust length → shifts the power peak RPM (the "on the pipe" RPM), updating the torque curve live. Lovely authentic detail. - Compression ratio slider → affects torque and knock limit (show margin). - Bore/stroke: keep displacement ~300cc fixed; slider adjusts bore-stroke ratio → stroke changes → mean piston speed at given RPM changes → redline recommendation changes (warn if MPS > 26 m/s). - Mission sliders: cruise speed target (300-450 km/h), CdA, prop diameter, mass, fuel load → outputs endurance/range/max speed. The drone target: 400 km/h. - Live P–V diagram (indicator diagram) with scavenging compression modeled. - Maybe an animated "port timing diagram" (small circle diagram with exhaust/transfer/scavenging sectors) that animates with crank rotation. Let me think about scope realistically. This is a big build but I should make it excellent and complete. Single HTML file, vanilla JS + canvas. I'll structure: **Sections:** 1. Header strip: program name, designation, class (FAI-ish), status. Big condensed title. 2. Hero: live engine cutaway canvas (large, ~60% width) + right column: tachometer + throttle + start button + key live numbers. Below the canvas: a thin strip of live telemetry (power, torque, MPS, EGT, fuel flow). 3. "Design basis" — the engineering math: required power derivation, why two-stroke DI, BMEP target. Presented as a dossier with computed numbers (some computed live from the model). 4. Performance model: torque & power curves (canvas chart) with operating point; tuned-pipe slider & comp ratio; PV diagram live. 5. Weight & build: weight budget table (crankcase, cylinder, piston, crank, DI, ignition, pipe, etc., with live total), materials list, port timing table. 6. Drone mission module: airframe params sliders, endurance/range computation, max speed, a small mission profile visualization (speed vs time? or a simple drag-power curve chart with 400 km/h target line). 7. Footer notes. Actually, let me reconsider the layout to keep it cohesive and not a card-pile. I'll use a "technical dossier" grid with hairline rules separating sections, numbered sections (01, 02, 03...), consistent header rows. Dark background #101113 or so, ivory #ECE7DC text, one accent: signal orange #FF4D00 (redline) and maybe a secondary muted teal for curves? Keep it: ink ivory + orange + a dim gray for secondary. Curves in ivory, operating point in orange, redline zone orange. Let me now do the engine physics model carefully so the numbers are defensible. **Engine definition (baseline):** - Architecture: single-cylinder, two-stroke, direct injection (gasoline), water-cooled? For ultra light, air-cooled is lighter but high specific output needs liquid cooling. A 300cc making ~75 kW needs liquid cooling honestly (GP500 bikes were water-cooled). Let's spec: liquid-cooled, 4.2 kg cooling system including pump/rad? That adds weight. Alternatively accept ~70 kW. Let me pick: water-cooled, Nicasil-plated aluminum bore. - Bore × stroke: 76 × 66 mm → 299.4 cc. - BMEP target at peak: 12.5 bar @ 11,000 rpm: P = BMEP × Vd × N/60 (2-stroke) = 1.25e6 × 0.0002994 × 183.33 = 68.6 kW = 92 hp. Torque = 68600/(11000×0.10472) = 68600/1151.9 = 59.6 N·m. - Mean piston speed @11,000: 2×0.066×183.33 = 24.2 m/s. Good for endurance-ish. - Redline 11,800 rpm (MPS 26.0 m/s). - Dry weight target: 16.8 kg (engine) + pipe 1.9 kg + radiator/pump 2.6 kg + DI system 2.3 kg → system ~21-23 kg. Let me build the weight table to sum to something like: crankcase 3.1, cylinder 1.8, head 0.9, piston+ring 0.34, crankshaft 2.6, conrod 0.44, ignition 0.6, DI injector+rails 1.6, water pump 0.5, misc fasteners 0.7 → engine core ≈ 12.6 kg? Hmm, that's aggressive. Vittorazi Atom 80 (80cc) weighs 7.7kg... scale: 300cc 2-stroke ~ most powerful paramotor engine Cosmos 300 = 17.4 kg I believe. Racing 125cc 2-strokes (water-cooled) weigh ~17-19 kg complete? Actually a modern 125GP engine ~ 17 kg complete with pipe. 300cc single at ~20-24 kg complete is credible. I'll spec engine core 17.2 kg, +DI 2.1, +cooling 2.8, +pipe 2.0 → 24.1 kg complete, and note a "sprint" variant at 21 kg. Power-to-weight 68.6 kW / 24.1 = 2.85 kW/kg ≈ 3.8 hp/kg. Good and honest. - Compression ratio (trapped CR): 12.5:1 for DI 2-stroke (racing 2-strokes run ~11.5-13:1 with DI possible). - Port timing (typical race 2-stroke): exhaust opens 82° BBDC (duration 196°), transfers open 58° BBDC (duration 116°), boost port 63°. Blowdown = 24°. Numbers should be plausible. - Tuned pipe: header length formula: L = (Ed × Vs × 60)/(N × 360)... let me recall the standard tuned pipe length formula: L = (Ed × Vs × 60) / (N × 360) where Ed = exhaust duration in degrees, Vs = speed of sound in exhaust gas (~ 500-570 m/s hot), N = rpm. That gives the distance from piston to the middle of the belly? Actually the classic formula (from Gordon Jennings "Two-Stroke Tuner's Handbook") for the distance from the piston crown to the midpoint of the diffuser: L1 = Ed × Vs × 60/(N × 360)? Let me sanity check: Ed=196°, Vs=520 m/s, N=11,000: L = 196 × 520 × 60/(11000 × 360) = 196×520×60 = 6,115,200; /3,960,000 = 1.544 m. That's piston-to-belly-center for ~11k rpm — plausible for a race 125 (~0.9-1.0m at 12k, with shorter duration ~192: at 12500: 192×520×60/(12500×360)=5,990,400/4,500,000=1.33m). Yes plausible. I'll implement that with Vs depending on EGT (Vs = sqrt(γ R T)). EGT ~ 700°C = 973K → Vs = sqrt(1.35 × 287 × 973) ≈ sqrt(376,900) ≈ 614 m/s. Hmm with γ=1.33, R=287: sqrt(1.33×287×973) = sqrt(371,258)=609. Jennings used ~Vs=515 m/s at moderate EGT. I'll compute Vs from EGT live and show pipe length adjusting with EGT and target peak RPM — that's a nice interactive: "pipe builder" slider for target peak rpm → required header length. And conversely, in the engine sim, the pipe length setting shifts the torque curve peak. **Torque curve model:** Define BMEP(RPM) as a skewed curve: base + peak factor × Gaussian-ish in log-rpm or shaped function centered at N_peak (pipe tuned rpm). Two-strokes have a sharp power band; before "on the pipe" torque is poor. I'll model: bMEP(N) = BMEP_MAX × [0.42 + 0.58 × exp(−((ln(N/Npk))²)/(2σ²))] × derate − pumping/friction? Better: model FMEP (friction) separately: - IMEP(N) from volumetric/charging efficiency: ηvol(N) shaped similarly. IMEP_MAX ~ 14.5 bar. - FMEP(N) = a + b×N + c×N² scaled with displacement: e.g., FMEP = 0.35 + (N/1000)×0.03 + ((N/1000)²)×0.0035 bar? At 11,000: 0.35+0.33+0.42=1.1 bar. Plausible for 2-stroke with DI pump drag. - BMEP = IMEP − FMEP. - Output torque = BMEP×Vd/(4π)?? No: torque = BMEP × Vd / (2π × cycles_per_rev)... For 2-stroke: work per rev = BMEP×Vd; torque = BMEP×Vd/(2π). So T = 1.25e6 × 0.0002994/(2π) = 59.6 N·m ✓ matches earlier. Peak RPM (pipe tuned) adjustable 8,000–13,000 via pipe length slider (and display required pipe length from a formula, consistent mapping). The torque curve shifts; total delivered power at operating point computed by matching prop load: the engine doesn't run wherever you want — with a fixed prop, RPM settles where engine power = prop power. But for a drone with a governor/ECU you can hold RPM. I'll implement "governed" mode: throttle sets target RPM (within limits), ECU holds it, fuel flow & power follow from the torque available at that RPM × throttle. Simplest honest model: throttle t ∈ [0,1]; available torque curve T_avail(N); prop load torque T_load(N) = P_prop_at... For dynamic sim: dN/dt = (T_engine − T_load − T_loss)/I. T_engine = t × T_avail(N). Prop load: T_prop = P_air(N)/ω with P_air = k×N³ (prop power ∝ rpm³) scaled so that at N_prop_rated, P_air = rated prop power. The steady state finds equilibrium. With throttle you move the equilibrium up. That's realistic and satisfying: revving against the prop load. Inertia I ≈ 0.02 kg·m² (crank + prop). Let me compute: prop 26" ~ 0.4 kg at r~0.3m: I_prop ≈ 0.4×0.09×... for a blade distributed, I ≈ (1/3)mL² ≈ 0.4×0.1=0.04? Let's use I = 0.045 kg·m² combined, gives spool-up times of ~1s. Fine. Prop power: P_prop_air = Cp × ρ × n³ × D⁵ where n in rev/s, D diameter, Cp ≈ 0.055 for a race prop (adjusted for forward speed? For simplicity in the static sim, model static-ish prop load; the mission calc handles forward flight separately with prop efficiency). At D=0.66 m, n=183 rev/s: P = 0.055×1.225×183.3³×0.66⁵ = 0.055×1.225×6.16e6×0.1252 = 0.055×1.225×771,300 ≈ 51,950 W. Hmm that would mean static power at full 11k rpm = 52 kW, so equilibrium RPM lower than 11k unless throttle full... Fine— equilibrium will sit around 10.5k at full throttle with this Cp. I'll compute Cp from the prop slider so that the rated point (prop pitch/rpm) loads the engine ~ at its peak power around the pipe peak. Actually simpler: give a "prop load" slider (pitch) and let equilibrium move. But for UX, better: "governor on" default — ECU holds target RPM by modulating fuel (like real drone ECUs). Then throttle = target RPM, and displayed power = engine power at that RPM from the curve (times mechanical assumptions), fuel from BSFC. The dynamic mode (governor off / free throttle) is a fun toggle. Hmm, scope. I'll implement free-rev dynamics with prop load — it's more visceral (you hear it come "on the pipe" as the equilibrium passes through the dip). Let me include both: a small toggle "GOVERNOR / FREE". Hmm, wait. Actually for the hero interaction, the cleanest visceral thing: throttle lever controls target; the engine spools with realistic lag; when you blip it, the sound sweeps. Whether load-limited or governed, behavior is similar in feel. I'll implement governor mode: N moves toward target with rate limit (spool-up limited by torque surplus); power output = torque_curve(N)×ω × throttle-scaled? Under governor, at partial load the ECU just runs the mixture/throttle (DI 2-strokes often use throttle body) so delivered torque ∝ throttle. So dynamics: dN/dt = (t×T_avail(N) − T_load(N))/I. Same equation! The only difference is in steady state: governor shows target achieved (if capable), free shows equilibrium. Honestly just use the one dynamic equation with prop load; at partial throttle equilibrium sits lower. When throttle=1, equilibrium is where T_avail = T_load → near peak. That IS realistic behavior for a fixed-pitch prop. Good — one model, no toggle needed. But I'll display "prop load line" on the torque chart showing the intersection → very informative and authentic (the load line crossing the torque curve). **Pressure model for the PV / indicator diagram:** Model the in-cylinder pressure vs crank angle for the 2-stroke with: - Blowdown/expand from exhaust opening, scavenging at ~1.1-1.3 bar slightly above ambient, compression from port closure (at 76° ATDC... transfers close 58° ATDC; actual trapped compression starts when both ports closed ~ 58° ATDC), then combustion (Wiebe function) from ignition (say 17° BTDC) over 45°, peak pressure ~ 85-110 bar, expansion to exhaust opening. Draw live PV loop with current crank position dot. This is a great visual. Simplify but keep it shape-accurate: - θ in [0°,180°] BDC-to-BDC (since 2-stroke, one rev; but drawing needs full 720°? No—2-stroke full cycle is 360°. PV loop over 360°, with scavenging/charge part at bottom near BDC.) - Compression: p = p_trapped × (V_bdc_trapped/V)^1.32 approx from transfer close. - Combustion: add heat via Wiebe: p rises with polytropic + burned fraction × (p_Peak multiplier)... I'll do a simple two-zone hack: pressure = motored pressure × (1 + f(θ)×k) during combustion, tuned so peak lands ~95 bar at ~12.5 CR. Honest enough for an indicator diagram. - Also show the crank-slider animation synchronized, port open/closed shaded on a small circular port-timing diagram. **Sound synthesis (WebAudio):** Firing frequency = N/60 Hz (single 2-stroke, one per rev). At 11,000 → 183 Hz. Build: oscillator (sawtooth) at f, plus sub at f/2? Actually engine firing pulse train: use a periodic buzz: combine sawtooth at f with detuned second saw at f×1.01 for beating, lowpass filter with cutoff rising with throttle, plus filtered noise for intake/exhaust rush. Gain modulated by throttle. Add slight distortion via waveshaper. Keep it tasteful, default volume moderate, explicit mute. Engine start: starter whirr (rising osc) then catch. This is a big wow factor. Must handle AudioContext resume on click. **Charts:** - Torque & power vs RPM (canvas, with load line, operating point dot, redline shading, peak marker). - PV indicator diagram (canvas). - Drag-power curve for the drone: P_req(v) curve with 400 km/h target line and operating point. - Maybe a live time-trace strip (EGT/FF) — optional; skip to control scope. Instead, live telemetry numbers updating. **Port timing diagram**: circle with crank angle sectors for exhaust (red), transfers (ivory), blowdown marked; rotating needle synced to the engine. Small canvas next to engine. This reinforces craft. **Numbers panel (weight budget)** — a table where each row is a component with material; total sums; a horizontal bar showing mass distribution? Keep it as a clean dossier table with a total row. Add live thrust/weight math for the aircraft: power-to-weight etc. **Mission calculator:** Inputs: - Cruise speed v (slider 200–480 km/h) - CdA (0.02–0.10 m²) - Prop diameter (0.45–0.90 m) - Prop efficiency (derived or slider 0.70–0.85) - Airframe mass (6–14 kg) - Fuel load (3–12 L) - Altitude maybe (0–3000 m, affects ρ) Computed: - P_req_shaft = 0.5ρ v³ CdA / η_p + induced term: P_ind = ... For a fixed-wing drone: drag = 0.5ρv²(Cd0 A + k CL² S). Need wing area & AR for induced. To keep honest yet compact: model as "equivalent CdA at cruise including induced" but let user set CL-based term? Simpler: two inputs — parasite CdA and wing area S with assumed e/AR (fixed AR=7, e=0.85, Cd0=0.030 for wing). Hmm, a 400 km/h drone: is it fixed-wing or multicopter-quadplane? At 400 km/h it must be essentially a fixed-wing racing plane (or a "speed drone" like therecord attempts — actually the "Fastest drone" records ~460 km/h by XLR/V3 with tiny wings or quad racers? DRL-style racers are quadcopters ~140 km/h. The 460 km/h record (DRL RacerX? no that's 263 km/h) — the ~480 km/h was a " Peregreen 2" by Mayman? Actually "Peregreen 2" quad drone hit 470 km/h with tiny wings providing lift at speed. At 400 km/h a quad with tilted props in "pylon" mode: lift from small wings, props tilted back. I'll design the vehicle as a "speed drone": tractor prop, small wing, quad-copter motors for hover takeoff (electric), main engine for cruise — a hybrid: ICE for cruise endurance + electric for hover. That's actually how you'd do an endurance speed drone: gas engine for cruise (endurance), small battery+motors for VTOL. I'll mention this architecture in the dossier: "cruise by 300cc 2-stroke; VTOL by 4× electric pods (battery sized for 90 s hover)". Power math for cruise (fixed wing): P_shaft = D_total × v / η_p D_total = 0.5 ρ v² S (Cd0 + CL²/(π e AR)) CL = 2 W g/(ρ v² S) — trim to level flight. Use: W = airframe 9 kg + powerplant (engine system 24 + pipe? included + fuel) + electric VTOL system (motors+battery ~3.5 kg). Total AUW ~ 38-40 kg. Wing S = 0.35 m², AR 7, Cd0 0.028? For a sleek fuselage, fuselage CdA ~0.012; wing profile drag Cd0×S ≈ 0.028×0.35 = 0.0098 → total Cd0 area ≈ 0.022. Plus tail. Let's let user tune CdA directly (parasite) and set S and AR fixed with sliders maybe. Outputs: P_req at target speed; engine load %; fuel flow = P_shaft × BSFC(load, rpm); endurance = fuel_L × 0.72 kg/L ÷ FF; range = endurance × v. Also max speed solving P_avail = P_req. BSFC model: BSFC = BSFC_base × (1 + 0.35×(1−load)²)?? For 2-stroke DI, best BSFC ~ 300-340 g/kWh (DI 2-strokes reach ~290-330). Cruise at 45 kW would burn 45×0.32×... 45 kW × 0.33 g/Wh = 14.85 g/s = 53.4 kg/h = 74 L/h!! That's huge. Hmm — high power cruise: at 400 km/h you're burning ~74 L/h?! With 8 L fuel: endurance = 8/74 = 6.5 min = 0.108 h → range = 43 km?? Wait that can't be right... 400 km/h × 0.108 h = 43 km. Hmm. That's the brutal physics of going 400 km/h: 60 kW to the shaft is enormous fuel flow. Wait, check: BSFC 0.33 kg/kWh × 60 kW = 19.8 kg/h. In L/h (0.74 kg/L): 26.7 L/h. I made an arithmetic error: 0.33 g/Wh = 330 g/kWh = 0.33 kg/kWh. 60 kW → 19.8 kg/h → 26.8 L/h. 8 L → 17.9 min → range = 119 km. OK that's more sensible. High-speed dash is short-legged; endurance flying is done slower. The mission module should show this trade: a "best endurance speed" (minimum power speed) and "best range speed". At 400 km/h you burn ~27 L/h; endurance at best-endurance speed (~180-220 km/h) might be 2× longer. This is honest engineering: I'll present the trade chart (power vs speed, fuel flow vs speed) and let the mission calc show both dash and cruise profiles. Great educational angle and makes the tool feel genuinely engineered, not fake. Actually, let me reconsider whether ~40-60 kW at 400 km/h is right. v=111.1 m/s. Parasite power = 0.5×1.225×111.1³×0.022 (parasite CdA) = 0.5×1.225×1,371,742×0.022 = 18,505 W parasite. Induced: CL = 2×38×9.81/(1.225×12343×0.35) = 745.6/(1.225×12343×0.35)=745.6/5291.9=0.141. CDi = 0.141²/(π×0.85×7)=0.0199/18.7=0.00106. D_ind = 0.5×1.225×12343×0.35×0.00106 = 0.5×1.225×12343 = 7560; ×0.35 = 2646; ×0.00106 = 2.80 N → tiny. P_ind = 2.8×111.1/0.8 = 390 W. Total ~18.9 kW air power /0.8 η_p = 23.6 kW shaft?! Hmm that's way less than 60. Let me recheck: 0.5ρv³CdA: v³=1,371,742. 0.5×1.225=0.6125. ×1,371,742 = 840,192. ×0.022 = 18,484 W. Yes ~18.5 kW parasite at 111 m/s with CdA 0.022. So a clean 40 kg machine needs only ~24 kW (~32 hp) at 400 km/h — that's 31% load. Then fuel flow = 23.6×0.34 (BSFC rises at low load; DI 2-stroke at part load with throttling... unthrottled DI 2-stroke BSFC at 30% load maybe 0.42) = 9.9 kg/h = 13.4 L/h. 8 L → 36 min → range 240 km at 400 km/h. Hmm OK. But wait — is CdA 0.022 realistic? For a streamliner motorcycle at Bonneville, CdA ~0.09-0.12 m²?? No wait — for a streamlined motorcycle CdA ≈ 0.19-0.25? Hmm. A sleek plane fuselage 2m long, 0.3m wide: frontal area ~0.07 m², Cd~0.12 → CdA 0.0084. Wing: Cd0 0.010 (laminar) × 0.35 = 0.0035. Tail surfaces ~0.002. Interference/cooling drag add 30% → total ≈ 0.019. Yeah CdA ~0.02 is achievable for a clean speed drone. Race drones (quad with fairing) CdA more like 0.03-0.05 without wing lift → power at 400: 0.5×1.225×1,371,742×0.035 = 29.4 kW air; but quad at 400 km/h also needs lift: props tilted, disc area small → very high induced power. That's why record drones (~470 km/h, Peregreen 2 used ~ big power). Fine — my hybrid winged design is the sensible engineering answer and I'll justify it in the dossier. So peak engine 68.6 kW gives top speed: solve 0.5ρv³CdA/η + induced ≈ 68.6×0.95 (prop efficiency at high speed ~0.82)... find v where 0.6125×v³×0.022/0.82 ≈ 65 kW → v³ = 65,000×0.82/(0.6125×0.022)= 53,300/0.013475 = 3,956,000 → v = 158 m/s = 569 km/h (drag-limited). So max speed ~560 km/h in a dive-ish; level ~ realistic with thrust available. Cool — the design has margin above the 400 km/h target, which I'll display ("202% of target" or a margin readout). OK. Now the **weight budget** — make it concrete: - Crankcase (magnesium AZ91, cast + machined): 2.95 kg - Cylinder (aluminum 6061-T6, Nikasil bore, liquid-jacketed): 1.55 kg - Cylinder head (aluminum, squish band): 0.62 kg - Piston (forged 4032 + 1 ring, DLC): 0.31 kg - Wrist pin (Ti): 0.058 - Connecting rod (Ti, split big end): 0.42 - Crankshaft (built-up, pressed, hardened): 2.45 - Main bearings ×2: 0.21 - Ignition (CDI + trigger): 0.35 - DI system (injector, pump, rail, ECU): 2.30 - Water pump + thermostat: 0.42 - Oil injection? skip (premix). Lubrication premix 1:50 — mention fuel premix. - Fasteners/hardware (Ti): 0.55 - Cooling (radiator, hoses, coolant, fan?): 2.35 - Tuned pipe (thin-wall steel/ti): 1.95 - Engine mounts (CF/alloy): 0.48 - Fluids/coolant: 0.6? Total: 2.95+1.55+0.62+0.31+0.058+0.42+2.45+0.21+0.35+2.30+0.42+0.55+2.35+1.95+0.48 = 14.966 + coolant 0.5 ≈ 15.5 kg. That's the "installed powerplant" — very aggressive but defensible for a race program. Complete engine core without cooling/pipe ≈ 10.7 kg for 300cc — hmm, GP500 engines 250cc twin ~ 20+ kg complete... but those included gearboxes. Direct-drive 2-stroke without gearbox is much lighter (paramotor engines ~ 300cc at 17 kg). 15.5 kg complete for a purpose-built 300cc is ambitious but within race-engineering credibility (add note: "target; proven equivalent: 17.4 kg production 300cc class"). Good. Power-to-weight: 68.6 kW / 15.5 kg = 4.43 kW/kg = 6.0 hp/kg. Strong but race-plausible. **Numbers to lock in the sim:** - Peak BMEP 12.4 bar @ Npk (pipe-tuned) default 10,800. - IMEP ~ 13.5 bar (FMEP ~1.1). - Torque peak ~ 59 N·m; power peak ~ 68-70 kW at ~11,200 (power keeps rising past torque peak). - Prop: D 0.64 m, 2-blade CF, load Cp such that full-throttle equilibrium ≈ 11,000. **UI micro-interactions:** - START/STOP engine (audio+animation; animation can run without audio) - Throttle: vertical lever (drag or wheel) — signature interaction; with detents display % and target RPM. - Ignition cut (kill switch) — fun. - Sliders update curves instantly. - Number readouts with tabular numerals. - Keyboard: hold Space for full throttle? Nice: "HOLD SPACE = WOT". I'll add. **Charts implementation:** plain canvas 2D, devicePixelRatio-aware, redraw on rAF only when engine running or params change. The engine cutaway redraws every frame while running (and while scrubbing). Keep perf fine. **Engine cutaway drawing** — the crown jewel. Side cross-section, stylized technical-line aesthetic (ink lines on dark, orange accents for hot gas, ivory metal outlines). Elements: - Crankcase outline, cylinder above, head. - Crankshaft: circle + counterweight rotating; connecting rod from crankpin to piston pin; piston as rectangle with ring grooves; cylinder walls; ports: exhaust port on left cylinder wall (opens at EO timing), transfer ports on right (or two sides), boost port. As piston moves down past port edges, ports open — animate colored gas: exhaust pulses (orange) flowing out the exhaust pipe when EO open, transfer charge (cool ivory/blue?) flowing in when transfers open. Use simple particle flows or gradient plumes — but I avoid gratuitous gradients; gas plume with alpha shapes is functional visualization, fine if subtle. - Spark: draw spark flash at ignition angle for a few degrees. - DI injector at head spraying a cone near TDC-ish (injection timing ~ 45-60° BTDC). - Reed/crankcase compression: 2-stroke crankcase — show under-piston compression plume pushed through transfers. - Tuned pipe silhouette to the left with return wave marker? Could overdo; keep pipe stub + label header length dimension line tied to the pipe slider — dimension callouts on the drawing that update live: bore, stroke, port heights, pipe length. Technical-drawing dimension lines (thin lines + arrows + mono text) that update with sliders = strong craft signature. I'll draw the engine in a "sheet" style: faint blueprint-ish grid (very subtle, not blueprint-blue since I want warm ivory on charcoal — use faint grid in low-alpha ivory) with dimension callouts. This will look like a living engineering drawing. Text/labels in the canvas: small mono labels (BORE 76.0, STROKE 66.0, TDC/BDC markers, port opening angles). **Layout plan (asymmetric, dossier-like):** ``` ┌ masthead: designation | class | status | audio toggle ├ 01 — THE MACHINE: big canvas cutaway (left ~62%) | control column (right): tach + throttle + START + kill │ + under canvas: telemetry strip (RPM/PSI/EGT/FF/MPS + PV inset + port-timing inset?) ├ 02 — DESIGN BASIS: prose + live-derived numbers (why 2-stroke DI; required power at 400; margin) with small inline computed values ├ 03 — PERFORMANCE MAP: torque/power chart (big) | right rail: pipe length slider (target peak RPM), CR, load-line readout, BSFC map mini? ├ 04 — MASS & BUILD: weight budget table + total; port timing table; materials notes ├ 05 — AIRFRAME & MISSION: sliders (CdA, wing, mass, fuel, speed target) + P–v curve chart + big endurance/range/max-speed readouts + verdict line ("TARGET 400 km/h: PASS, margin …") └ footer: assumptions & disclaimers (model vs physical prototype honesty note) ``` Avoid equal cards; use hairline separators and numbered section heads in condensed caps. Section headers like "01 / THE MACHINE". Fonts: "Big Shoulders Display" (or "Big Shoulders" new API name: family=Big+Shoulders+Display) — hmm Google Fonts renamed to "Big Shoulders" with optical sizes; "Big Shoulders Display" still resolves? To be safe use "Saira Condensed" (definitely exists) for display + "IBM Plex Mono" for data/body-ish + maybe "Archivo" for body. Let me pick: display "Saira Condensed" (600/700), data "IBM Plex Mono", body "Archivo" (light 300/400). Hmm, Saira Condensed is nice industrial. Alternatively "Barlow Condensed". Saira feels more techy. Go: Saira Condensed + IBM Plex Mono + Archivo. Colors: - bg: #0E0F11 (near-black, slightly warm?) Let's use #101112 with subtle texture? Flat is fine. - panel ink lines: rgba ivory 0.14 for hairlines - text: #E9E4D8 (ivory), secondary #9A958A, faint #6A655C — careful about contrast; keep secondary ≥ #98938a on #101112 → contrast ratio ok (~5+). - accent: #FF4D00 signal orange for redline/throttle/hot gas - data curves: ivory; load line: dashed orange; secondary curve: #7FB4A8?? Adding a desaturated teal as the second curve color (power vs torque) — keep restrained: torque ivory solid, power orange? Power = the money curve; make power orange solid, torque ivory. Redline zone = orange alpha fill. - success/pass: use ivory+orange only; "PASS" in orange. Keep 2-color discipline. Maybe a single green ONLY for "PASS" verdict? I'd rather keep discipline: verdict in orange with check glyph. Fine. Icons: use lucide via CDN? For a technical dossier I barely need icons — mute toggle, maybe arrows. I can inline a few SVGs (play, volume, zap) — inline SVG icons are fine ("use an icon library for small icons" — inline lucide-style SVG paths hand-set is fine and dependency-light; or just include lucide CDN). I'll inline minimal SVGs (speaker, power, gauge) to avoid CDN flakiness beyond fonts. **Honesty framing:** The user asked to "create a complete working model". I'll open the reply by reframing: a physical engine can't be fabricated in chat, so I'm delivering the complete engineering model — the same artifact an actual program starts from: validated simulation + spec. I'll note this briefly and confidently, not apologetically. Also flag the honest engineering trade: endurance at 400 km/h vs slower cruise. Also important correction to their framing: "300 CC, ultra light, very high RPM, drone, 400 km/h, high endurance" — high endurance AND 400 km/h AND piston twin? I'll be straight: the physics of v³ drag means 400 km/h costs ~4× the fuel of 200 km/h. The model shows max endurance ~ around 180-220 km/h and gives dash capability at 400+ with the fuel carried. And note: for a 2-stroke, "very high RPM" has a sweet spot ~10.5-11.5k (MPS limit); I'll let the model show why higher RPM isn't free. Now — code. This is large. Let me carefully draft the structure. ```html VX-300R — Engine Design Dossier

machine + controls

design basis

performance map

mass & build

mission

My drone engine