Skip to content

Waterloo Steel:Demo Launch Instruction

jaku-jaku edited this page Feb 21, 2023 · 4 revisions

Table of Contents

[Last generated: Tue 21 Feb 2023 12:29:35 EST]


1. Waterloo Steel Demo

1.1 Powering on the robot

  1. Turn on the robot by twisting two power knobs for Base and WAM

  2. Power on the steam deck controller

  3. Launch the joystick controller by touching [Launch UWARL Summit Controller] App Icon

1.2 Launching the Camera

$ ssh uwarl-orin@192.168.1.10
$ roslaunch waterloo_steel_supervisor multi_intel_camera.launch

🚨 If the launch is not successful:

  1. Check the hardware USB C cable connections to both cameras
  2. [Ask Jack if you need to] Launch individual cameras separately for the system to register individual camera IDs

1.3 Launching WAM

# 1. connect to jetson
$ ssh uwarl-orin@192.168.1.10
# 2. start a tmux session
$ tmux 
### TIPS:
# create multiple windows with:
# [ctrl + b] then ["] : split horizontal
# [ctrl + b] then [%] : split vertical
# [ctrl + b] then [arrow-keys] : switch window selection
# [ctrl + b] then [:] and [type: set mouse on] : to enable mouse selection and scroll and window adjustment

# 3. launch wam node:
$ roslaunch wam_node wam_node.launch
### WAM Activation Instruction:
# 1. release all E-stops
# 2. [shift & activate] on control pendant (the one with E-stop inside the cabinet)
# 3. [Enter] on the keyboard to confirm default home-position
# Now, you will hear the gear activating

### TIPS:
# launch other nodes: 1.2 camera & 1.4 demo node in different tmux windows

# 4. detach to keep running in background and independent from your laptop terminal:
# [ctrl + b] then [:] and [type: dettach]

1.4 Launching Demo Node

$ roslaunch waterloo_steel_supervisor waterloo_steel_demo.launch
# command to perform demo:
$ rosservice call /waterloo_steel/start_demo "demo_id: 2"

1.5 Check Demo Rosbag Records:

$ ls ~/.ros/bagfiles/waterloo_steel_demo/session_{id}/

A. Troubleshoot

A.1 Deck Controller Cannot Launch:

🚨 If the controller app quit after launching, it is likely due to the following issues:

  1. The deck is not connected to summit wifi "SUMMIT_STEEL_171102A_5G"

    πŸ› οΈ Connect to the wifi manually at the status bar

  2. The summit is not hardware ready:

    πŸ› οΈ Please reset (engage and release) the E-Stop at the rear of the SUMMIT base

  3. There is no ros core in the network OR any other detailed issues β†’ The Summit Base ROS Controller and ROS Core were not launched successfully nor enabled:

    πŸ› οΈ Please SSH into the summit base and troubleshoot from there:

    # SSH into adlink mxe211 (summit)
    $ ssh uwarl@192.168.1.11
    
    # check if summit bringup is successful
    $ systemctl status --user roscorelaunch@waterloo_steel_summit_bringup:waterloo_steel_summit.launch
    
    # [DEBUG] - print out last msg (double-check time-stamp):
    $ journalctl --user --user-unit=roscorelaunch@waterloo_steel_summit_bringup:waterloo_steel_summit.launch > log.txt
    # [DEBUG] - Live Stream:
    $ journalctl --follow --user --user-unit=roscorelaunch@waterloo_steel_summit_bringup:waterloo_steel_summit.launch
    
    # stop/restart
    $ systemctl stop/restart --user roscorelaunch@waterloo_steel_summit_bringup:waterloo_steel_summit.launch
    
    # You may want to check if the workspace is at the right target, and built successfully:
    $ check_ws_status
    $ build_ws
    $ src_all

> Back To Top <

Clone this wiki locally