Skip to main content

Machine is stuck on a pulsing white dot

What to try before contacting support

R
Written by Roy Raanani

If the display is stuck on a pulsing white dot (or a loading bar that never finishes), the machine did not finish starting because the Dial cannot talk to it over the internal network. That network is not home Wi-Fi.

Try reconnecting to the machine from the app

Establishing a new connection via the Mobile Companion App is often enough to reset connectivity and let the Dial connect.

  1. Open the Meticulous app.

  2. Go to Gear → Settings → + Setup Machine.

  3. The machine should appear with a blue DISCOVERED tag beside it, indicating it has been identified for pairing via Bluetooth.

  4. Connect to the machine.

  5. Connect it to the Wi-Fi network.

Try switching to the previous software version

If the initialization issue is due to an incomplete software update, you can always revert the machine to the previous installed version. This video shows the sequence.

  1. Turn the machine on and wait until the progress bar reaches approximately halfway - or until you first see the white dot. Then turn the machine off.

  2. Repeat this on/off process 4 times.

  3. Turn the machine on once more and leave it on so it can fully initialize. Wait about 10–15 minutes.

Install a new software image via a USB key

Many issues have already been solved via a newer software version. If you're unable to boot to install it, we can send you a link to download the latest software version and instructions on how to load it onto a USB key.

  1. Use a USB-A stick with a USB-C adapter if you can. USB-C 3.1 sticks are not supported.

  2. Power the machine on first, then plug the USB into the USB-C port on the back, next to the power cord.

  3. After about 10 seconds you should hear a chime and see progress on the display. If you hear nothing, leave it for about 10–15 minutes.

  4. Remove the USB, then power-cycle the machine.

Once it is running, connect Wi-Fi on the machine, then Report an Issue so we have the logs. If that fails, pull logs manually.

Did this answer your question?