Draw Me Bot Not Connecting
If your DexArm robot does not appear in the DrawMeBot port list on your Mac -- or one of multiple bots refuses to be recognized -- this article walks through the connection diagnostics in the order our support team uses them.
Quick Diagnostics
- Check the USB cable. Many robot connection issues are caused by a charge-only cable that does not carry data. Always use the cable supplied with the robot.
- Open DrawMeBot on the Mac and look at the port list. Each connected DexArm should show a port (typically
/dev/cu.usbserial-...or similar). If a robot is missing, the issue is upstream. - For Mac M1/M2/M3 hosts: confirm the macOS version is supported. Apple Silicon Macs require recent USB serial drivers.
- Power-cycle the robot. Switch the DexArm off, wait 10 seconds, switch it back on.
Common Issues
Robot Does Not Appear in DrawMeBot Port List
Problem: You connect the DexArm to the Mac via USB, but the robot does not show up in DrawMeBot's port list. With multiple robots, one or two appear, and one is missing.
Cause: Almost always a USB cable, port, or hub problem. This was the exact pattern Remy Biggers reported in February 2026 -- two of three bots showed port numbers, one did not.
Solution:
- Quit DrawMeBot completely. From the macOS menu bar, choose DrawMeBot > Quit DrawMeBot.
- Unplug all robot arms from the Mac and the powered USB hub. Wait 10 seconds.
- Reopen DrawMeBot. Then plug in the missing robot first -- before reconnecting the others. Confirm it appears in the port list.
- Reconnect the remaining robots one at a time, waiting for each to appear before plugging in the next.
- If the robot still does not appear, swap its USB cable with a known-working cable from one of the other bots. If the issue follows the cable, replace the cable. If the issue stays with the port, it is a Mac USB port problem.
Tip: Plug the robot directly into the Mac (not through the powered USB hub) for the first connection test. This isolates whether the hub is the problem.
USB Cable Is Charge-Only, Not Data
Problem: A new or replacement cable does not work even though the robot powers on.
Cause: Many USB cables -- especially those bundled with chargers -- carry power only and do not pass data. The DexArm needs a true USB data cable to communicate with the Mac.
Solution:
- Use the cable that shipped with your DexArm.
- If you need a replacement, look for a cable explicitly labeled USB data cable or USB-A to USB-C/Micro data. Cables sold as "fast charge" are not always data cables.
- Test by plugging a phone into the cable -- if the phone shows up as a removable drive on the Mac, the cable carries data.
Multiple Robots, USB Hub Power Problem
Problem: When you have two or three bots connected through a powered USB hub, one or more drop off the port list intermittently.
Cause: The hub is not delivering enough power, the hub's wall adapter is not plugged in, or the hub itself is faulty.
Solution:
- Confirm the powered USB hub is plugged into a wall socket -- not just powered from the Mac. (This was the first thing support asked Rick Taylor in March 2026.)
- Use the powered USB hub Foto Master supplied -- third-party hubs are sometimes underpowered for three robots.
- Spread the load. Plug one robot directly into the Mac and the other two through the hub.
- Try the robot in a different USB port on the Mac to rule out a single bad port.
macOS Power Management Drops the Robot
Problem: The robot connects fine at the start of the event, but drops off after the Mac sits idle for a few minutes.
Cause: macOS energy-saver settings cut power to USB ports during low activity.
Solution:
- Open System Settings > Battery > Options (on MacBook) or System Settings > Energy Saver (on Mac mini/Studio).
- Disable Put hard disks to sleep when possible.
- Set the display sleep timer to Never for the duration of the event.
- Disable Automatic graphics switching if your Mac has that option.
See Robot Stops Mid-Drawing for the related screensaver issue.
Driver / Apple Silicon Issues
Problem: Robot does not appear on a brand-new M1, M2, or M3 Mac that has never run DrawMeBot before.
Cause: macOS Apple Silicon requires the correct USB serial driver, and Gatekeeper may have blocked it on first install.
Solution:
- Open System Settings > Privacy & Security.
- Scroll to the Security section and look for a message about a blocked driver or extension. Click Allow.
- Restart the Mac.
- Reopen DrawMeBot, plug the robot in, and check the port list.
- If the driver is still not loading, reinstall DrawMeBot from your Cloud Dashboard > Licenses page. See DMBot Getting Started for the install walkthrough.
Robot Powers On but Behaves Erratically
Problem: The robot is connected, but it doesn't respond to commands or move to the wrong positions.
Cause: The robot was bumped or moved out of its calibrated position.
Solution:
- Run the Draw Bounds test in DrawMeBot to verify the robot reaches the corners of its drawing area.
- If the bounds are wrong, recalibrate using the DMBot Calibration guide.
- Make sure no one has accidentally repositioned the robot's base.
Was this helpful?
Related articles
Photos Taken But Not Printing
Quick Checks First Is the printer powered on with the ready light solid? Is paper loaded with the ribbon from the same box? Is the USB cable connected between the printer and booth
Booth Computer Running Slowly at Events
Common Causes Windows Update downloading in the background Antivirus scanning during the event Low disk space on the system drive Too many hours without a restart — memory buildup
How to Export All Event Data
This article explains how to export photos, videos, guest contact data, survey results, and event statistics from Foto Master Cloud.Exporting Photos and Videos Log in to cloud.foto
License Activated but Events List is Empty
You logged in successfully, your Cloud Licenses tab shows your license as Activated, but when you open FMX (or your booth software) the events list is empty -- nothing to select, n
License Activation Issues
Activating your Foto Master software should take just a minute or two. If something isn't working, this page walks through the fixes step by step. Before anything else, confirm whi