ReferenceCalibration and firmware
Calibration and firmware
Maintain an individual actuator, re-calibrate an arm, update drive firmware, calibrate head cameras and look after a robot's software.
MAKIINA arms and robots leave the factory calibrated and with their firmware loaded. You do not need anything on this page to use them. Come here after mechanical work on a joint, when a joint turns the wrong way, when a new firmware version ships, when a head camera has moved, or when you build a unit from bare actuators.
For an individual drive, go to Maintain an actuator below. Those steps use the Actuator Console; the arm and robot tools described first use the Robot Console.
Maintain a robot
The tools are on every unit's row in the Robot Console: Calibrate, Firmware and Software. A robot in your fleet also has Cameras in its page menu. For an arm on your PC the tools run on your PC. For a robot in your fleet they run on the robot's head computer and you use them from your browser, so your PC must be on the robot's network, and your account must be an owner or admin of the robot's organization (an operator sees only the status and logs on the Software page). The robot's Robot admin page opens the same tools with its device code. While Calibrate or Firmware holds a robot's buses, or Cameras its cameras, the robot shows Maintenance in the fleet list and accepts no sessions; its services come back when you close the tool.
Re-calibrate a unit
Each drive stores in its own memory which part and joint it is, its zero, its direction and its motor type. The calibration wizard writes those values. It does not write any file.
Re-zero only on purpose. Zeroing rewrites what the boards store, so the arm's reference pose changes for every program that uses it afterwards.
Put the unit at its zero pose
Switch the unit off. Put every joint on its alignment notch: an arm lies folded flat, the upper arm level and the elbow fully closed so the forearm lies back over it, as the wizard's 3D twin shows it. Open the gripper fully; a head looks straight ahead. Switch it on again. The drives start holding that pose, and everything the wizard stores is measured from it.
Walk the wizard
Open Calibrate on the unit's row, then Open the wizard. It has seven steps along the top; you can go back to any of them.
- Unit. Choose left arm, right arm or head. The wizard looks at every adapter for about a second and picks the one whose boards match.
- Boards. The boards found on that adapter, seven for an arm with a gripper. If one is missing, check its power and the CAN cable and sweep again.
- Identify. Press Nudge on a board: its joint moves by 5 degrees and back, a little more with every repeat. Choose which joint moved. The 3D view lights up the joint you are matching. Boards that already know their joint arrive filled in, so you only confirm them.
- Direction. Press Move +5° and watch the real joint. It must turn the way the 3D twin turns; if it turns the other way, press the other sign and move again. The sign is stored on the board the moment you press it. For the gripper, positive closes the fingers.
- Zero. Check the pose once more and press Zero now. Every board stores the pose it is holding as its zero and keeps holding, so nothing goes limp.
- Store. Store on the boards writes part, joint number, direction and the calibrated flag to every board.
- Done. The unit describes itself again: plug it into any PC with the SDK and it appears ready.
Then check the zero before anything moves. Open Control on the unit's row and look at the 3D twin with ARM off: it shows the measured joints, so it must show the pose the arm is in. If a joint of the twin points another way than the real one, do not arm: support the arm, click Torque off and walk the wizard again from Unit. If they still differ, write to sales@makiina.com.


Bus termination
The last board on a bus must terminate it: the gripper on a stock arm, or J6 when the arm has no gripper. The Identify step checks it and says so. The termination buttons on each board's row move it.
Update drive firmware
The Firmware page brings boards up to the firmware that ships with the software it runs on: the SDK kit on your PC, or the robot's own software for a robot in your fleet. A new firmware version arrives with a new SDK kit or with a robot software update. Open Firmware on the unit's row and let it scan the bus.

Every board is listed with its joint, firmware version, whether its motor controller started correctly (FOC), its motor preset and the plan for it. Flash loads the shipped image onto that one board; it takes about 17 seconds and the board restarts on its own. Preset only stores a new motor preset without flashing. Boot log shows what the board reported when it last started. The page also links the open source notices of the shipped firmware and says how to get its source.
- Each press flashes one board. Let it finish before you start the next.
- A flash keeps everything the board stores: part, joint number, zero, direction, preset and its compensation tables.
- Presets:
mediumfor J1 to J3,smallfor J4 to J6 and the gripper. A board with the wrong preset shows FOC failed; choose the right one and press Preset only. - Choose a .bin loads another image for the next flash, for example a newer one you received.
Two boards on one id
Each board takes its CAN id from its chip's serial number, and on rare occasions two boards on one bus draw the same id. The scan then shows 2 boards answer on this id. With firmware 2.05 on both, Resolve moves one of them to a free id. The Calibrate wizard refuses a bus in that state until it is resolved.
Calibrate the head cameras
A robot's two head cameras are calibrated at the factory, and every session sends that calibration to your PC. Calibrate them again when a camera or its mount has moved, a lens was replaced, or a camera cable went into the other port. The gripper cameras need no calibration.
Open any of the robot's pages, such as Software, and choose Cameras in the page menu at the top. That works on the robot's Robot admin page and in the Robot Console on your PC, with your PC on the robot's network. Everything runs on the robot. You need an A3 printer and something stiff and flat to glue the board on. The robot ends any session and takes none while it captures.

- Board. Press Print the board and print it at 100 % on A3. Measure the 100 mm bar to check the scale, then glue the board flat onto something stiff. Use matte paper and good light without glare; in a dark room, tick automatic exposure. Press Start the capture.
- Capture. Stand in front of the head with the board and move it slowly through the whole picture of both cameras: near and far, to every edge, turned left and right, leaned up and down. Hold it still for a moment and the robot saves a view by itself. Keep the whole board inside the picture. Each eye shows how much of its picture is covered and what is still missing. When both eyes say enough, press Enough: end the capture.
- Solve. Leave Camera pitch at the mount's angle (-60 means looking 60 degrees down) and press Solve. It takes a few minutes.
- Check. The page lists the stereo pairs used, the RMS reprojection error, the baseline, the eye order and the vertical misalignment after rectification, each good or not, with the pictures before and after rectification. When a line is not good, press Capture more. If eye order fails, the two camera cables are in each other's ports: write to MAKIINA support at sales@makiina.com.
- Save. Save to the robot stores the calibration on the robot. The next session uses it, and software updates keep it.
Backup downloads the robot's identity folder with its camera calibration; keep it with the robot's records. If the page says the calibration tools are not set up on the robot yet, press Set up the tools once. It takes about 3 minutes and needs internet on the robot.
Look after a robot's software
The Software page shows the computer a unit runs on: its name, system, free disk space and the software version it runs. For a robot in your fleet it also lists the robot's services with their state and logs, restarts a service, and reboots the robot (press and hold Reboot). Before a reboot, support the arms and click Torque off on the Control page. The Software page says a reboot drops the torque, but nothing sends that command: each drive keeps its last target while the robot restarts (Check the session and disconnect).

Update from this PC, at the top of a robot's page, is a tool for MAKIINA's developers; you update a robot with release files.
On a robot the same page installs software updates. Download the release file (makiina-robot-<version>.mkpkg) from the download page; you need no account for it. When the page says No releases are published yet, there is no update. Drop it on the page: the robot checks MAKIINA's signature, updates both of its computers, checks itself, and goes back to the version before when a check fails. Update the robot software has the steps; follow them rather than the short ones on the download page, since the device code is not on the robot's card. Updates never change the robot's operating system, kernel or bootloader version; a new SD card from MAKIINA does. They only keep one bootloader setting in place, SDRAM_BANKLOW=3, the memory setting the robot's system needs.
From Python
The tools use public functions you can call yourself, for example to check a bus before a long run:
from makiina.calibration.discovery import discover_bus
for b in discover_bus("candle", "207137C04845500F2:0"):
print(b.id, b.version, b.part, b.label, b.calibrated)The drive-level calls (zero, direction, part, joint number, preset, CAN id, firmware) are listed under Identity and calibration in the actuator reference.
Maintain an actuator
These tasks use the Actuator Console, opened with ActuatorConsole.bat on Windows or ./actuator_console.sh on Linux. Close other programs using the adapter first. For normal operation, start with Set up the actuator and First move. You do not need to repeat calibration to use a prepared actuator.
Set an actuator's size and zero

Size for this session and Motor preset are different. Selecting M or S for an unknown board tells the Console which model and conversion to use. Motor preset on Setup writes motor configuration to the board. Use the physical actuator's specification, not the rendered model, to identify a replacement board's motor.
- Select the actuator by its ID and open Setup.
- If commissioning a replacement board, choose the correct Motor preset, read the confirmation and allow the board to restart. Keep the output free: motor alignment can turn it. A changed pole-pair count clears the old alignment and zero.
- To define a new zero intentionally, support the mechanism and use Torque off if you need to position it by hand. Put it at the physical reference position you want to call zero.
- Press Zero here, check the actuator ID and position, then confirm Store the zero. Read the position again; it should be near 0 rad.
- Check Direction with a small positive move at low current. Change it only if the mechanism's positive direction should be reversed.
Standalone actuators need no Unit id or Joint. Assign those only when building a defined arm or head. Calibrate again clears motor alignment and restarts the board; it is a repair operation, not a normal startup step. An older M gearbox can use Old M: use 39 to 1 for the Console session; confirm the physical gearbox first.
Set the actuator bus termination
The actuator controller board already contains a 120 ohm termination resistor. Its Termination switch on Setup enables or disables that resistor through software; you do not need to add a resistor to the actuator.
With the adapter at one end of the CAN cable, check that its end is terminated according to the adapter's instructions. The Actuator Console switch controls the actuator board, not the adapter.
For one actuator, select it and enable Setup > Termination. In a chain, enable it only on the last actuator and disable it on intermediate boards. Do not add an external terminator at an end that is already terminated.

The actuator switch is stored on the board immediately. Check the bus message and rescan if communication is unreliable. The software reports board termination states; it cannot verify every external resistor or cable connection for you.
Resolve an actuator ID collision
On Discover, an ID collision means two drives answer at the same bus address. Do not flash that shared ID. Press Resolve and confirm the board move to a free ID. Both boards need firmware 2.05 or newer. Rescan and check that each now has a separate row before controlling them.
With older firmware, power off and disconnect one board. Update the one remaining, use Setup to give it a free CAN ID, then power off before reconnecting the other. Rescan when both are powered. Unit and joint assignments do not resolve a duplicate CAN address.
Update actuator firmware

- Select the actuator and open Firmware. Compare Running and Shipped. The shipped version belongs to your installed SDK kit; install a newer kit first if you need newer firmware.
- Keep the board powered and connected. Stop motion and support any attached load. The Console stops motion on the affected bus before flashing, and updates one board at a time across the PC.
- Use the shipped image for a normal update. Choose a .bin is for a specific firmware image you intend to install.
- Check Preset after a flash. Keep the existing correct preset. For an unconfigured board, select the preset for its physical motor.
- Press Flash, read the board ID and preset consequences in the confirmation, check the power acknowledgement, then confirm.
- Wait for Done. Check the running version and Boot report: the board should answer again and its FOC and encoder checks should pass.
A normal flash preserves zero, direction, identity, CAN ID and calibration tables. Selecting a preset with a different pole-pair count can clear the zero and motor alignment; the confirmation explains that exception. Do not change the preset merely because a firmware update is available.
If power or the cable is lost, restore it and press Rescan. A board waiting in its bootloader can be flashed again. If the Console says the adapter needs a restart, close it normally and reopen it before retrying.
Keep settings after maintenance
A board restart clears temporary tuning. Open Tuning, use Apply saved for that board, inspect readback and recheck the Control limits. If you changed motor size or gearing, review an old profile before applying it. Tune and save settings explains drafts, running values, PC profiles and exported files.