Test on your own printer
This guide is for people helping us test the Android app on real printers. Most printer types here have never been tried on a real machine, so what you find is exactly what we need. Work through the tiers in order and stop whenever you like.
The quickest way to test, from the next update: the app's Test Mode runs these checks for you, step by step, and sends the results from inside the app. See Test the Android app. This guide remains for testing by hand.
This guide is for app version 0.1.1 or newer. Open Settings, then About & credits, and check the version. If you have 0.1.0, wait for the update from Google Play before you start (it installs automatically); the steps below use features that 0.1.0 does not have.
Please read this first. The Bambu Lab, OctoPrint, PrusaLink and Snapmaker U1 (stock firmware) support, and in the next update Elegoo on Elegoo firmware, Creality and Flashforge, was built from the makers' published documentation or open-source code and tested only against emulators or simulated printers. It may misbehave on a real printer. So: stay at the printer for anything that moves it, use the small test print below, know where your printer's own stop or power switch is, and do not test while a print you care about is running. You are always free to stop after any tier.
What you need
- An Android phone with the app installed from the closed test. If you have not joined yet, see Test the Android app.
- Your printer, on the same network as the phone (or reachable over Tailscale).
- The printer's details, kept to yourself: for Bambu Lab, LAN mode turned on plus the serial number and access code; for PrusaLink, the PrusaLink password; for OctoPrint, an API key; for Klipper (including a Centauri Carbon on COSMOS), the printer's address (and API key if Moonraker asks for one); for Elegoo on Elegoo firmware, the address (a Centauri Carbon 2 also needs its access code); for Flashforge, the serial number and access code; for Creality, the address.
- The 20 mm test cube (a plain cube, about 10 to 15 minutes to print). Save it on your phone.
- A little of your usual PLA.
Tier 0: set up
- Open the app. Go to Settings and tap Run self-check. Every line should pass. If any fails, note which.
- In Settings, open About & credits and note the version number.
Tier 1: connect and read status (nothing moves)
- In Settings, tap Add printer. Either use Scan network, or choose your printer type and type the address. Pick the type that matches your printer: Bambu Lab, Prusa Link, OctoPrint, Generic Klipper (also for a Centauri Carbon on COSMOS), Snapmaker U1 (stock), Snapmaker U1 (PAXX), or in the next update Elegoo, Creality or Flashforge.
- The app should connect. On Home, check the printer state, the temperatures and (when a print runs) the progress agree with the printer's own screen.
- If your printer has a camera and the app offers one, check that the picture loads.
- Reconnect: turn the phone's Wi-Fi off for about ten seconds, then on. The app should reconnect without you re-entering anything.
- Optional: in Settings turn on Background print alerts and check the ongoing notification appears.
Tier 2: slice the test cube (nothing moves)
- Edit the printer (or use the wizard's slicing step) and choose your model in Slicing profile. Use the search box. The full list is long; pick your exact model. If it is not there, choose the closest one and tell us. For a machine of your own, see the custom-built Klipper section below.
- Open Prepare, tap Add models and pick the test cube.
- Tap Slice. It should finish in well under a minute.
- Look at the result: the cube should sit inside a bed of the right size and shape, and the print time and filament weight should look plausible for a small cube. If the bed looks wrong for your machine, stop here and tell us. Do not print.
Tier 3: send the file, then print (stay at the printer)
Only continue if Tier 2 looked right.
- 3a, send the file. Tap Continue on the result, confirm Printer is ready (the bed is clear), and let the app send the file. Check the file now shows in the printer's own file list or screen. The print has not started. You can stop here.
- 3b, start the print. When you are ready and standing by the printer, tap Start print and confirm. Watch the first layer all the way. It should heat, home, and print a cube. On Creality and Flashforge printers the app sends the file but doesn't start it yet: start it on the printer's screen. A multi-colour file is refused on Bambu printers for now.
- While it runs: Pause, wait for the printer to actually stop, then Resume, then Cancel. After each, check the printer did what the app said. After cancelling, the heaters should turn off and the printer return to idle.
- Did the cube come out right? Was it the right size (20 mm)?
Extra checks for your printer type
Bambu Lab (LAN mode)
- Setup needs LAN mode, the serial number and the access code. Tell us if anything about setup was unclear or failed.
- The first connection saves the printer's certificate. If the app ever warns the certificate changed, note when.
- Newer models (P2S, H2D, H2S and other H2 models): please do Tier 1 and report before going further, because control on these is the least certain. The app may connect and read status but fail on controls or on sending the file. That is a useful result.
- When you scan the network, the model text the app shows next to your printer (in brackets) helps us preselect the right profile in future. Please include it in your report.
PrusaLink
- Setup uses your PrusaLink password. Note your printer model and the PrusaLink or firmware version.
- The app has no camera for PrusaLink printers, so skip that item.
- Check the file lands in the storage you expect (for example USB or the SD card).
Custom-built Klipper printers
- Choose Generic Klipper and do Tier 1 and the controls: connecting, status, temperatures, files, macros, jog, pause, resume and cancel. Klipper is the best-tested path, and your reports here are very useful.
- Set up your own machine before slicing. The generic profile is a 250 × 250 mm bed with the origin at a corner and a start sequence that calls
START_PRINT EXTRUDER_TEMP=… BED_TEMP=…. If that is not your printer, edit the printer, choose Generic Klipper as the slicing profile, and turn on Custom machine. Enter your bed width, depth and height, say whether the origin is at a corner or the centre, and put your own start and end G-code in the boxes (for example yourPRINT_STARTandPRINT_ENDmacros; slicer placeholders such as[nozzle_temperature_initial_layer]work). The nozzle stays 0.4 mm for now. - In Tier 2, check the bed in the preview matches your printer before you send anything. If your printer needs settings the custom machine cannot express (a different nozzle size, an odd bed shape), tell us and stop before printing.
- Please tell us how it went and what was missing: nozzle size, bed shape, anything else your printer needs. That decides what we add next.
Snapmaker U1 on stock firmware
- Choose Snapmaker U1 (stock). On the Control tab, Bespok3d / remote screen should appear.
- Tapping Probe daemon only reads and changes nothing. It fails if the Bespok3d daemon is not installed, which is normal on a stock U1.
- Advanced, optional: the enrollment step installs software on the printer over SSH. It has never been run on real hardware. Only try it if you are comfortable recovering a printer, the printer is idle, and you have noted your firmware version first. Tell us before you do it if you can.
- This does not apply to PAXX (extended) firmware, where Bespok3d is not supported.
Tell us what happened
Please send one report per printer, using either:
- the report form on GitHub (needs a free GitHub account), or
- an email to support@nozzleitall.com with the same details: app version, phone and Android version, printer make, model and firmware, how you connected, how each tier went, and what you saw where it did not go well.
Never post or send a serial number, access code, password or API key. The report form is public. Blur them in screenshots. We will never ask for them.
What we do with your report
A printer type is marked "Verified on hardware" on the Supported printers page once a test result from a real printer of that type and firmware has been reviewed and accepted; the results are on the compatibility page. Reports of problems are just as valuable: they are how we fix them. Thank you.
Not sure about a step, or something does not match what you see? Email support@nozzleitall.com and we will fix the guide.