Open settings with the Settings tile on the hub. All sections sit as chips across the top — icons only on a phone — in two groups. The title reads Settings with the robot's name and serial, the device and the app version.
Power, Payload setup. They open even without a robot, but anything that acts on the robot needs it connected. While the in-app simulator is selected they are dimmed.Gamepad, App settings. They always open.On every settings screen the logo at the top left returns to the hub, and the gamepad button next to it goes straight to the control screen. That button works only while a robot is connected or the sim is running.
Gamepad is covered in Gamepad.Calibration, Robot Check and Software update are on the Maintenance screen.This page covers Power, Payload setup and App settings. Operators can use all of them, and rows that need developer mode are marked.
This section switches the auxiliary rails you use day to day. The toggles show the actual PDU state the robot reports, so a change can take about a second to show up. Until the first rail state arrives, the toggles stay disabled.
12 V toggles (one tap): Speaker amp (12V), CCTV (12V), Thermal (12V), IR LED (12V).
48 V rails (two-step): ARM · ADDON (48V) and EXTERN (48V) each show the live voltage and a Turn off / Turn on button. Pressing it opens Turn this off? or Turn this on?. Confirm to switch.
WARNING
ARM · ADDON (48V) is one PDU port shared by the arm and the add-on. Turning it off also cuts arm power — make sure the arm is stopped first.
Camera, comm, Vision PC, and LEGS (48 V) power, along with LiDAR and system reboot, are not here — switching any of them off breaks the connection or drops the robot. They live in Maintenance (developer mode).
On CAN-FD robots this section lists ports instead of rails: CCTV (12V · LAN2), Thermal · PTZ (12V · LAN3), Front 12V (IR LED), Rear 12V (IR LED), Speaker amp (one tap) and ARM · ADDON (48V) (two-step). Each row shows the live state, voltage and current, and stays locked until the port state has been received.
Payload Configuration describes what is mounted on the robot so the walking dynamics can account for it.
Set Payload and confirm with Apply (Get re-reads the slots from the robot and discards your edits). The confirmation shows the number of mounted slots and the totals; unchecked slots are sent with mass 0. The new values reach the walking dynamics right away, ramped in over one to two seconds.Help expands a short guide above the table. Robots without the payload slot API show a notice asking for a robot software update instead.
These settings belong to the app, not the robot.
| Row | Options |
|---|---|
Theme | Dark / Light |
Language / 언어 | Korean / English — applies immediately |
Joystick sensitivity | Slider — input response curve |
Keep screen on | Toggle — keeps the screen awake while controlling |
Deadzone | Slider — center range ignored by the joystick |
Gyro widget | Toggle — roll/pitch attitude display |
Fullscreen | Toggle — browser only |
Low-signal warning | Toggle — top warning banner when Wi-Fi signal drops below Warning threshold (slider, shown while enabled) |
Warning beep (Notify BEEP) | Toggle — short beep on warnings (web only) |
Low battery beep | Toggle — beeps when the robot battery is low; Warning beep (Notify BEEP) must be on (web only) |
UI scale | Desktop app only — Auto, 100 % to 200 % |
The Developer mode toggle is in the profile menu — the round button at the top right. As a guest, turn on Developer mode and enter the password. Turning it off puts you back at the operator level. While you are logged in with an access code (Log in with access code in the same menu) the toggle is not shown, because the account decides the level.
Developer mode adds the developer sections of Maintenance, the developer rows above, and the Position control group in the Select motion grid.