Skip to content

Start typing to search the documentation.

↑↓to navigateto open

Bambu Lab setup

Prepare a supported Bambu Lab printer for local connection to Pluraprint.

Choose the guide for your printer: P1S, H2S, or H2D.

Pluraprint uses a local connection through your site’s agent. You enter the printer’s IP Address, Serial Number, and Access Code in Add Printer.

Prepare the printer

Use Bambu Lab’s illustrated LAN-mode guide for the controls on your printer. Menu labels can change with firmware. Keep the printer and agent on a network where they can reach one another; ask your IT team to reserve the printer’s address so it stays consistent.

Firmware with Bambu Lab authorization controls may also require Developer Mode for third-party local control. Review Bambu Lab’s third-party integration guidance with support if the option or expected behavior differs. Ask support to confirm compatibility before a fleet-wide firmware update.

The LAN access code is a printer credential, not your Bambu account password or the account-binding PIN. Enter it only in the connection form. Do not include it, the printer’s address, or its serial number in shared screenshots.

If the printer’s LAN access code changes, update its Access Code in Pluraprint and save. Updated connection settings take effect on the next printer operation.

Check the connection

After adding the printer, confirm that its status updates and materials reflect what is loaded. Map any unknown material before sending a job that needs it.

ProblemWhat to check
OfflinePower, current IP address, LAN settings, and the site’s agent status.
MQTT connection refused: Not authorizedRe-enter the printer’s current LAN access code exactly and save, then check for a successful status update.
Status works but jobs do not startConfirm firmware compatibility and local-control settings with support.
Connection drops after a restartAsk IT to check whether the printer’s address changed.
No H-series camera imageCheck LAN Mode Liveview on the printer. See your model guide.

If these checks do not resolve it, contact support with the model, firmware version, site name, and on-screen error.

Last updated