software_setup_ap
This is an old revision of the document!
Table of Contents
Software Overview and Setup
HUBO Software Architecture
Commands are given through the GUI which are passed over to Shared Memory.
If the command is a low-level function it can be passed straight to Daemon, but if it is a higher-level function which requires additional processing the command must go through AL first, return to Shared Memory, then be passed to Daemon.
From Daemon, the commands are sent either to Gazebo (simulator) or the physical HUBO. Commands can only be sent one or the other. I don't know why, ask KAIST HUBO lab members or something.
Software Setup with Qt
- Start a new session
- Include PODO GUI, Daemon, PODO Launcher .pro files in your session
- Rebuild on new computers
- Launch PODO first, then the rest
Sending Gazebo Commands
Gazebo is run on a sepearte PC to simulate HUBO, the motion PC. In order to run the simulation you have to
- Open a terminal and start a ROS masternode
- Launch the drc_hubo launch file in the drc_podo_connector directory
- Check that the motion PC is connected to the simulator PC by checking the IP address
software_setup_ap.1478384408.txt.gz · Last modified: by alvaropintado