I installed Luke's Lab's Pika Hotend in my P1S with the copper plated 0.5mm nozzle on 2026-05-09. ## Calibration ### Pika 0.5 FIN Copper Plated Nozzle | Brand | Type | Color | Rotation Distance | Orca Temp | Orca PA Pattern ([Ellis' info](https://ellis3dp.com/Print-Tuning-Guide/articles/pressure_linear_advance/pattern_method.html) | Orca Flow Rate (YOLO) [OrcaWiki](https://www.orcaslicer.com/wiki/calibration/flow_ratio_calib.html?h=flow) | Extrusion Multipler ([Elli's info](https://ellis3dp.com/Print-Tuning-Guide/articles/extrusion_multiplier.html)) | Orca Retraction (PA/EM is more important...) | Max Volumetric Speed [OrcaSlicer Wiki](https://www.orcaslicer.com/wiki/calibration/volumetric_speed_calib.html) | Orca Cornering | Last Updated | | -------- | ---- | ----- | ----------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | -------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | -------------- | ------------ | | Overture | PETG | White | N/A | | | 0.95 | | | 45 is conservative value; ~60 was failure. | | 2026-05-10 | | | | | | | | | | | | | | Overture PETG Profile was default = 11.5mm^3/s Bambu PETG HF default = 21 mm^3/s max flow rate attempt 1 min: 10 max: 40 step: 0.5 ## 0.5mm Nozzle on P1S Tricks ### Why you're stuck The P1S firmware only knows about four nozzle sizes — 0.2, 0.4, 0.6, and 0.8 mm. That list is hardcoded; the "Accessories → Nozzle" menu won't ever offer 0.5. On top of that, the printer runs a nozzle-diameter sanity check at the start of every job (`M862.1 P[nozzle_diameter]`), and on newer firmware also a separate hotend/nozzle ID check via `M972 S14` / `M1002 gcode_claim_action : 72`. If what you sliced doesn't match what the printer thinks is installed, it aborts the print. So there are really two problems to solve: tell the printer something plausible, and stop the start-up checks from rejecting the job. ### The fix **1. On the printer, set the nozzle to 0.6 mm.** Settings → Accessories → Nozzle Diameter → 0.6mm. Pick 0.6 rather than 0.4 — if the printer ever decides to enforce a max volumetric flow based on the menu setting, you'd rather it allow more than your real nozzle can do than less. Match the material (stainless vs hardened) too. **2. In OrcaSlicer, edit the printer's start G-code** to remove or neutralize the nozzle check. Open Printer Settings → Machine G-code → Machine start G-code. Find the line that looks like: ``` M862.1 P[nozzle_diameter] ... ``` Either delete it, comment it out with a `;`, or change it to a hardcoded `M862.1 P0.6` so it matches what the printer's menu says rather than what you sliced with. **3. If you're on recent firmware (≥1.08-ish) and the printer still bails out**, also comment out the nozzle-type detection lines in the start G-code: ``` ; M1002 gcode_claim_action : 72 ; M972 S14 P0 T5000 ``` **4. Send the job in LAN/developer mode** — turn on LAN-only mode and Developer Mode on the printer screen. This bypasses Bambu Connect's own slice-time validation that can reintroduce the same complaint. Sending via SD card works too and is the most foolproof if you keep hitting cloud-side rejections. ### Things to double-check on your slicer profile Since you cloned a profile to get to 0.5, make sure these are sane for the bigger orifice, since OrcaSlicer won't auto-adjust them all: - Layer height range: ~0.15–0.35 mm is reasonable for a 0.5 - Line widths: default to ~0.5 mm, with outer wall maybe 0.45 and infill 0.55–0.6 - Max volumetric speed: re-run the calibration; a 0.5 sits between the 0.4 and 0.6 limits and the printer is happy to over-extrude if you don't cap it - Pressure advance / flow ratio: recalibrate from scratch — values from the 0.4 profile will be wrong ### A small heads-up A firmware update can reintroduce the check or add new ones (this has already happened a couple of times on the X1/P1 line and the H2D), so if a future update breaks your workflow, the start-G-code edits are the first place to look. Some people keep a "known good" firmware version pinned for exactly this reason. [Claude is AI and can make mistakes. Please double-check cited sources.](https://support.anthropic.com/en/articles/8525154-claude-is-providing-incorrect-or-misleading-responses-what-s-going-on)