-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathMIRO_setup
161 lines (95 loc) · 5.31 KB
/
MIRO_setup
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
##### ROS SETUP ON YOUR COMPUTER #####
Considering that you have the ubuntu version 16.04, Please proceed as follows:
NOTE:
CPIT means Copy and Paste In Terminal
Workstation means your computer
Whereever you find <Put_Here_something> then replace it entirely with that something.
Example:
export MIRO_PATH_MDK=~/<Put_Here_NameOf_MDK_Directory_In_WorkStation>
Then you can simply do:
export MIRO_PATH_MDK=~/mdk
CRITICAL POINT:
HARDWARE:
While removing and inserting batteries in MIRO (recommended for your ease and also safety of the robot),
please put the robot upside down in your lap [as can be seen in the image here - https://consequential.bitbucket.io/Technical_Platform_Body_shell.html].
please hold down the battery cover with one hand while using the screw driver in the other hand.
please do not use excessive strength when tightening the screw.
Also keep in mind the following - https://consequential.bitbucket.io/Demonstrator_Commissioning_Before_You_Start.html
When charging MIRO's batteries, note that a full charge can take 9.5 to 10 hours (If the left and right blue LED's are active on the charging box then it means that the batteries are charging)
SOFTWARE:
If,
Intention is to use the simulation of MIRO in Gazebo & Ubuntu is running on a virtual machine
then,
For users of Virtual Machine. DO NOT enable 3D acceleration (In VM settings) for gazebo to work properly.
Else,
No problem in using simulation of MIRO in Gazebo
#########################################################################
1. INSTALLATION of ROS Kinetic (MIRO needs ROS Kinetic) [Link for details if interested: http://wiki.ros.org/ROS/Tutorials/InstallingandConfiguringROSEnvironment]
------> Check if your configration of ubuntu repositories are proper as shown in the screenshot (link below)
http://gazebosim.org/tutorials?tut=ros_installing
------> Setup your sources list (CPIT)
sudo sh -c 'echo "deb http://packages.ros.org/ros/ubuntu $(lsb_release -sc) main" > /etc/apt/sources.list.d/ros-latest.list'
------> Setup your keys (CPIT)
sudo apt-key adv --keyserver hkp://ha.pool.sks-keyservers.net:80 --recv-key 421C365BD9FF1F717815A3895523BAEEB01FA116
------> Update your debian package index (CPIT)
sudo apt-get update
------> Do full installation (CPIT)
sudo apt-get install ros-kinetic-desktop-full
------> Initialize ROSDep (first step) (CPIT)
sudo rosdep init
------> Initialize ROSDep (second step) (CPIT)
rosdep update
------> Environment setup (first step) (CPIT)
echo "source /opt/ros/kinetic/setup.bash" >> ~/.bashrc
------> Environment setup (second step) (CPIT)
source ~/.bashrc
------> Dependencies for building packages (CPIT)
sudo apt-get install python-rosinstall python-rosinstall-generator python-wstool build-essential
------> Check if installed correctly (CPIT)
rosversion ros
2. Install gazebo_ros_pkgs (If interested in using simulation mode) (link below)
http://gazebosim.org/tutorials?tut=ros_installing&cat=connect_ros
3. Download the MIRO Developer kit and MIRO android app from here (link below)
http://labs.consequentialrobotics.com/miro/mdk/
------> Make a new directory called 'lib' in your 'home' directory
------> Move the recently downloaded directory 'MDK-170906' to 'lib'
------> Go to the mdk directory in lib .. From there
------> Type this command in terminal (It creates a symlink) (CPIT)
ln -s $PWD ~/mdk
------> Inside terminal of Workstation type (CPIT)
sudo nano ~/.bashrc
------> Add the lines below and modify '<>' parts
# cofiguration
export MIRO_PATH_MDK=~/mdk
export ROS_IP=<Put_Here_IP_Of_Your_WorkStation>
export ROS_MASTER_URI=http://localhost:11311
# make our custom messages available to ROS/python
export ROS_PACKAGE_PATH=$MIRO_PATH_MDK/share:$ROS_PACKAGE_PATH
export PYTHONPATH=$MIRO_PATH_MDK/share:$PYTHONPATH
# usual Gazebo setup
source /usr/share/gazebo/setup.sh
# announce MIRO resources to Gazebo
export GAZEBO_RESOURCE_PATH=$MIRO_PATH_MDK/share:${GAZEBO_RESOURCE_PATH}
5. Lets bring MIRO to Life
------> In a new terminal type (CPIT)
roscore
------> In a new terminal type (CPIT)
ssh root@<Put_Here_IP_Of_MIRO_Found_In_Android_App>
------> MIRO's SSH entry password is
MIROOpen1
6. Configuring the MIRO, so that it can locate the ROS Master (your Workstation): Not necessary to make static IP for MIRO. Simply, before connecting with MIRO using SSH, check MIRO's IP address in MIRO android app
------> Inside terminal of MIRO type (CPIT)
sudo nano ~/.profile
------> Change ROS_MASTER_IP as the IP address of your workstation. To check the IP address of your workstation open a new terminal window and type in:
#.. bla bla (line simply for your reference)
#.. bla bla (line simply for your reference)
#.. bla bla (line simply for your reference)
ROS_MASTER_IP=<Put_Here_IP_(OfYourWorkstation)_ForConnectingWith_ROS_Master>
7. Testing if all is working (Be careful if MIRO is on the table, it is going to move during tests; it can fall)
------> Run sample python code (link below)
https://consequential.bitbucket.io/Developer_Examples_Python_Command-line_Client.html
------> Run sample C++ code (link below)
https://consequential.bitbucket.io/Developer_Examples_C++_Command-line_Client.html
------> Run Python GUI for Complete access to MIRO sensors and actuators (link below)
https://consequential.bitbucket.io/Developer_Examples_Python_GUI_Client.html
=============