Troubleshoot the dual arm system

Find the symptom, then work down its list. Most setup problems come from the network, a mistyped code, or a robot that is still starting. A single arm kit has its own list in Set up a single arm kit.

The robot shows OFFLINE

The robot reports to MAKIINA Cloud over the internet. On your account's Robots page it shows Online now within about a minute of starting when:

• the head Pi's network cable is in and your router gives it an address;
• your network lets it reach the internet (it needs no open ports, but a guest network or a network that blocks all outgoing traffic keeps it offline).

Switch the robot off and on again if it stays offline. The Robot admin page still works on your network meanwhile, and so do updates from it.

The claim code is refused

Confirm your email address first. Your account's address is not confirmed yet, and such an account cannot add a robot. Open the link in the mail MAKIINA Cloud sent you and press CONFIRM MY EMAIL ADDRESS, then press ADD THE ROBOT again: the code was not used up. No mail? Press SEND THE LINK AGAIN in the banner at the top of the account console, and look in the spam folder. Confirm your email address has the steps.

That code does not work. Check the 12 letters: claim codes have no vowels and no digits, and dashes do not matter. If it still fails, the code was used already, or a newer code replaced it. Ask the person who gave it to you, or write to MAKIINA at sales@makiina.com.

After ten wrong tries in an hour you have to wait before you can try again.

The robot is not in your list after the claim. You chose another organization in the claim step. The Robots page groups robots by organization when you belong to more than one.

The Organization page says No organization yet. A new account has no organization until it adds its first robot. Add the robot as in Create your organization and add the robot: that step makes the organization. To join an organization that exists already, ask its admin for an invitation.

The SDK kit or the VR app does not download

The download page says Sign in to download. The SDK kit and the VR app download only from your MAKIINA account: sign in at cloud.makiina.com/account, open SDK and press GET DOWNLOAD LINK. Robot software updates download from the download page without an account.

The link says it has expired, or curl says returned error: 410. A download link works for 24 hours. Press GET DOWNLOAD LINK again for a new one.

The link says it is not valid, or curl says returned error: 404. Part of it was lost when you copied it. Copy the whole link again with COPY LINK, and put it in quotes when you give it to curl. When the page says This SDK file is no longer published, that kit is no longer offered: get a new link, for the kit the SDK page shows now.

PowerShell says A parameter cannot be found that matches parameter name 'f'. In Windows PowerShell, curl is another command. Type curl.exe -f -o makiina-sdk.zip "<the link>" instead.

The zip is only a few hundred bytes and does not unzip. curl ran without -f and saved the error message as the zip. Open the file in a text editor to read it, then fetch the kit again with curl -f -o makiina-sdk.zip "<the link>" (curl.exe in Windows PowerShell).

A session does not start

An error names makiina.dll (Windows). It says Could not find module '...\makiina.dll' (or one of its dependencies) when you press Control. The PC lacks the Microsoft Visual C++ Redistributable (x64), which the SDK needs for every session. Install vc_redist.x64.exe and press Control again.

Troubleshooting covers sign in problems, a robot left in a session, and maintenance mode. A robot whose fleet row reads ROBOT INCOMPLETE has a part that did not answer at start: see A robot says ROBOT INCOMPLETE.

Software or SSH access does not open

The top bar says reaching the robot's console, same network needed. The Robot Console on your PC reaches the robot's Software, SSH access and device code over your local network. Put the PC on the robot's network (the same router or switch, not a guest network) and open the page again. Driving does not need this; it works from anywhere.

Your account is an operator or viewer. Only owners and admins of the robot's organization open these pages with their account, and only they see the device code (Only owners and admins of the robot's organization see its device code.). Ask an owner of your organization for the admin role, or for the device code to use the Robot admin page.

The Robot admin page does not open

The Robot admin page answers only on the robot's network, at http://<robot name>.local:8726, with the name on the robot's card, even after you give the robot a new name in your account (Use the Robot admin page).

The browser cannot find acme-robot-02.local, or the name of your robot. Some PCs and networks do not resolve .local names. Find the robot in your router's list of devices and open http://<that address>:8726. Check that your computer is on the same network as the robot, not on a guest network.

The page does not load at all. The robot is still starting (give it a minute after switching on), its network cable is loose, or the robot is off. Check the cable at both ends of the head Pi.

The device code is refused. The page says to check it on the card in the box; the card has no device code. Check the code letter by letter against the one your account shows; dashes and lower case do not matter. After ten wrong codes in a minute the robot ignores your PC for five minutes. A robot that changed owner has a new code: find it again.

The page asks for the device code again. The code was kept for that tab only (Remember it on this browser unticked), someone clicked Forget the device code here, or the robot changed owner and has a new code.

The page says the robot changed owner. It was claimed or moved while the page was open. Reload the page and do the step again.

You do not know the device code. It is not on the card. An owner or admin finds it with their account, on the robot's network: Find the device code. With SSH access, this prints it on the head Pi:

~/repos/.venv/bin/python -m makiina.console --show-device-code

SSH does not let you in

SSH cannot find the robot, or the connection times out. Your computer is not on the robot's network. Use a computer on the robot's network, or your own VPN into that network. The robot's .local names use the name on its card, not a new name from your account. If your PC does not resolve .local names, use the address from your router.

Permission denied (publickey). The robot does not have your key, or SSH offers another key than the one you added. Open SSH access for the robot in the Robot Console and check that your key is listed on head Pi and gripper Pi. If you keep the key somewhere else than .ssh/id_ed25519, name it: ssh -i <your private key> aql@acme-robot-02.local.

Your key worked before. The robot changed owner, or was added to an account after you added the key: both reset the keys to the MAKIINA factory key. Add your key again.

An update is refused or goes back

The page names the reason; When the file is refused lists each one and what to do. If the robot went back to its previous version after an update, it works as before: send the message from the page to MAKIINA support at sales@makiina.com.

The Software page says the robot runs a version that cannot install release files yet. The robot runs software from before release files. Write to MAKIINA support at sales@makiina.com: they update it once, and from then on release files work.

A camera shows no picture

A camera feed says not detected. Now and then a camera does not answer when the robot is switched on, and it stays dark until the next start. A restart of its computer brings it back; switching the power off and on is a cold start again and may not.

• A head camera: in the cockpit, support the arms and click Torque off, then open the session card (click the connection readout in the top bar) and press Reboot robot. The head Pi restarts and is back in about a minute.
• A gripper camera: sign in to the gripper Pi over SSH (Add your SSH keys) and run sudo reboot.

It stays dark after two restarts. The camera or its ribbon cable needs a look. Write to MAKIINA support at sales@makiina.com and say which camera: left or right of the head, or which gripper.

Every feed is dark. See Video and the 3D view.

The head video stutters

At the robot's starting bitrates both head camera modes send the same, 8000 kbit/s per camera, so switching the mode does not lighten the load. On a slow network, for example over the internet when the top bar shows the relay path, lower the bitrate and stay in full res: there a picture that a lost packet damages is whole again within a few frames, in the foveated mode only after up to about 10 s.

• In the cockpit, click the rate in the header of the Cameras card and lower Full res bitrate (per camera).
• In the VR app, lower PER CAM under FULL RES BITRATE (LIVE, KBPS).
• In Python, robot.control.set_video_bitrate(4000), in kbit/s.

The robot keeps the new bitrate for later sessions.

Ask for help

Write to sales@makiina.com with the robot's name, what you did, and the exact message the page showed. The version the robot runs is on its Software page.