Remote access & firmware
Routine jobs you run from your PC over the network. First connect your PC to the robot and check that the robot answers a ping.
To start or view the cameras, see Start and view the cameras.
ssh works in PowerShell on Windows 10/11 and in any Ubuntu terminal. The first time you connect to a robot, type yes to trust it.
Connect to the Orin or Thor
On Marvin Pro, Luna, and Skye, the AI controller (NVIDIA Orin or Thor) is at 6.6.7.100. The factory logins are below. If your robot was delivered with a different password, use that one.
| Controller | User | Default password |
|---|---|---|
| Tianzhun (Orin) | nvidia | nvidia |
| Lingjing Thor | user | 1 |
- Terminal:
ssh nvidia@6.6.7.100(Thor:ssh user@6.6.7.100) - Remote desktop: connect to
6.6.7.100with NoMachine.
Use NoMachine without a monitor
If no monitor is plugged into the Orin or Thor, NoMachine shows a black screen. To connect without a monitor, log in over SSH and run:
sudo systemctl stop display-manager
sudo /etc/NX/nxserver --restart
Then connect with NoMachine again. This lasts until the Orin or Thor restarts, so run it again after each power-up.
Check the Apex teleoperation version
The Apex robot-side packages run on the Orin or Thor. Log in (ssh nvidia@6.6.7.100) and run:
dpkg -l kernelmind-apex
The last line of the output is the kernelmind-apex package: ii at the start means it's installed, and the third column is its version. If you see no packages found matching kernelmind-apex, Apex isn't installed on that computer. Record the version before you update, and match the desktop app and headset APK to it (Install Apex teleoperation). On an Ubuntu operator computer, the same command shows the desktop app's version.
Check the controller firmware version
The x86 motion controller prints its firmware version when its control service starts. You need it to choose the matching Marvin Platform build script and SDK.
If Marvin Platform already connects to the robot, it shows the controller version at the bottom of its window, so you don't need to restart anything; see Connect & read robot status. Otherwise, restart the control service as follows.
stop.sh stops the controller. Before you run it, disable the arms, make sure no software is commanding the robot, and keep the E-stop within reach.
-
Log in to the x86 controller as
root. The password ispasswd.Robot Command Marvin Pro, Luna, Skye ssh root@6.6.7.190Marvin ssh root@192.168.1.190(firmware 1003) orssh root@6.6.7.190(firmware 1004) -
Restart the control service:
cd /home/FUSION/Shell./stop.sh./start.sh -
start.shprints the firmware version. Write it down, then typeexit.
If you can't log in
| Message | What to check |
|---|---|
Connection timed out or No route to host | Your PC isn't on the robot's network. See Connect your PC. |
Permission denied | The user name or password is wrong. Use nvidia for the Orin/Thor and root for the x86 controller. |
| NoMachine shows a black screen | No monitor is plugged into the Orin or Thor. See Use NoMachine without a monitor. |
REMOTE HOST IDENTIFICATION HAS CHANGED | You've connected to a different robot at the same address before. Run ssh-keygen -R 6.6.7.100 (or the address you used), then connect again. |