Skip to main content

Guided Diagnostics

Use Settings > System > Troubleshooting as a superadmin before collecting raw logs or changing printer settings. Run one small, observed print only after the relevant checks pass.

1. Check the server​

Choose Check server. Review each result and its suggested next step. A server check is not proof that ODIN can reach a printer or start a print.

After an upgrade, also confirm the expected version at /health and ready: true at /health/ready. If first-time setup appears unexpectedly, check that the existing data volume is still mounted before proceeding.

2. Check the saved printer​

Select the intended printer and choose Check printer. Verify the saved address, credentials and LAN settings if authentication or connection checks fail. Protocol coverage varies; an unsupported diagnostic does not establish that the printer is healthy or broken.

For Bambu LAN printing, confirm LAN access and the access code on the printer itself. Firmware may require Developer Mode for third-party printing. Allow ODIN's host/container to reach the printer across any VLAN boundary.

3. Test protected file transfer (Bambu LAN only)​

This disposable transfer diagnostic is available for saved Bambu printers only. For other protocols, use the supported connection check and provide its results to support; disabled transfer controls do not mean the printer failed.

With the Bambu printer idle, select the disposable-transfer confirmation and choose Test file transfer. This uploads a small diagnostic file, verifies its contents and attempts to remove it. It does not start a print. Review any cleanup warning.

A successful MQTT connection or FTPS login does not prove file transfer works. Bambu FTPS uses a separate protected passive data connection: the firewall must allow the negotiated data connection to the printer, not only the control port. Use the failed stage and your printer/network configuration to investigate; do not open unrelated hosts or expose the printer to the internet.

4. Try one complete workflow​

Slice a small file for the actual printer, installed nozzle, plate and loaded material. For a Bambu pilot, use a sliced .gcode.3mf, not a raw model.

In Education mode, use one test student in the intended class or club. Submit once, review as the authorized teacher, select an authorized printer, refresh AMS tray information and explicitly map the source material to a suitable tray. Schedule and dispatch through the authorized operator workflow. Observe startup and completion, then confirm both the job and student submission complete.

If a start request times out, inspect the physical printer and retained dispatch state before taking another action. Do not repeatedly click start, create a duplicate job, reset the submission or clear a retained dispatch record to force a retry.

5. Prepare a support report​

In Troubleshooting:

  1. Describe what happened, including the step, time, ODIN version and submission/job ID where relevant.
  2. Select optional recent logs only when needed.
  3. Choose Preview support report and review the contents.
  4. Choose Download report and attach the JSON to your support email or existing support thread.

Open email draft opens your mail application. ODIN does not automatically send the email or attach the downloaded report. Check the attachment yourself.

Do not include passwords, printer access codes, license keys, tokens or student information. Review the downloaded report before sharing it; automated filtering is not a substitute for that review. If support requests additional logs, use the smallest relevant time window from Docker Logs.