UI not connected to hub

• Hub is not running

• Hub and computer the UI is on are not on the same network.

1. Check that hub PC is turned on.

2. Check that both hub and UI computers are on the same network.

3. If you’ve tried the above, try rebooting the hub.

Hub nodes not starting

• If hub shows it is disconnected refer to the above problem.

• If hub shows it is connected.

  • Hub & UI on mismatched versions.

  • Hub disconnected from UI and UI did not update status.

  • Communications lost between hub and UI even though they are connected.

1. Check that both hub and UI are fully updated.

2. Restart UI to see if hub is still connected.

3. Reboot Hub and try again.

Printers not appearing in “My Printers” list.

• Scanner node not running on hub.

• Printers & hub on different networks.

1. Check that the nodes are running in the hub watcher panel of the UI.

2. Check which network the printers are on / that they are connected to a network to make sure it is the same as the Hub/UI.

3. Reboot the hub/UI

Hub gets stuck on “uploading to hub” step when uploading file.

• There was a known bug where if you didn’t have any models selected in the workspace (all models grayed out), that the hub would get stuck on this step.

• Select a model and try again.

• If the problem persists, try the following problem.

Hub gets stuck on any other step when uploading file.

There are several known/theorized reasons why this can happen.

• There is a known bug where the hub nodes don’t always shut down when you click the “Stop” or “Kill HUB Nodes” buttons in the hub watcher UI panel, resulting in duplicate nodes being spun up the next time you tell them to start.

• Bad connection between UI/Hub or Hub/Printers. It is possible this is the case if it is getting stuck on the “Uploading to hub” or “Uploading to Printers” steps.

• Issue with model: Errors in 3D models can cause them to fail the chunking or interweaving steps. We have error handling that should notify you when this has occurred, but if it is getting stuck in these steps it may be the cause.

• If you have already Started/Killed the hub nodes without restarting the hub, try rebooting the hub.

• Try opening your model in another program that can detect model errors.
  Unfortunately the AMBOTS UI does not have this feature built in.

  • 3D builder in Windows.

  • PrusaSlicer.

Printer has motor driver error (specifically seven blinks of error light on driver)

There are many reasons this could happen, but here are the most likely ones.

• Wire disconnected between the motor and driver.

  • Likely the connector closest to the motor.

• Printer crashed into something.

  • Maybe a print

  • Maybe cable harness bundle got out of place and in the way of the joints.

• Check to see if any wires are loose on the motor cable.

  • If so you will need to re-crimp a new connector pin on the wire.

• If the printer crashed into something, resetting the driver should fix the error so that the arm can move again, though you may have a separate problem as to why it crashed.

Printer not homing arm joints

• Check to see if one of the drivers has an error and shut down, if so, also refer to the above.

• Endstop switch disconnected / noise on switch line.

• If the arm is stopping before it is hitting the switch.
  or

• If the arm is hitting the switch, then erroring out the driver.

1. Check the wiring for the switch closest to the switches.

   1. A wire may have lost connection.

2. Try pressing the switch by hand to see if the axis indicator lights up in Duet UI.

   1. If not, the switch has been disconnected somewhere.

Filament Errors even when printing normally.

• Filament sensor disconnected.

• Filament momentarily stopped extruding.

• Check to see if the lights are still on on the side of the filament sensor.

• Run ‘M591 D0’ on the Duet UI to see if it tells you that there was a reading out of bounds.

BLTouch unresponsive or deploying when not commanded to.

• There are interference issues with the Duet and BLTouch. We are not certain how much of it is an issue with the wiring harness or Duet board itself.

• Check to make sure the BLTouch pin is not bent.

• Unplug the BLTouch from the cable and plug it back in.