Differences

This shows you the differences between two versions of the page.

--- poppy_software [2016/07/25 13:13]
mai ssh odroid
+++ poppy_software [2019/05/17 13:08] (current)
mai [Control the robot] spelling
@@ Line 47: / Line 47: @@
 The poppy humanoid has an embedded [[odroid xu 4]], where these libraries have been installed (pypot and poppy-humanoid).
 You can log to the computer by ssh using the network labo-sid: odroid@poppy1 (mdp: odroid)
+The new Poppy from february 2017 has a Rasberry Pi 3 instead of odroid xu 4. As the ethernet port is not available, the connexion to the Rasberry Pi is done using Wifi. If your wifi network is not known by the robot, you need to plug a keyboard to the Rasberry Pi and use the touchscreen to configure the new connexion.
+Once the computer and the robot are in the same network, you can log to the robot using ssh: poppy@poppy.local (mdp: poppy).
+Note that if you want to manage the wifi networks configurations of the robot in ssh, you need to modify the file: /etc/wpa_supplicant/wpa_supplicant.conf.
 ===== First program =====
@@ Line 146: / Line 150: @@
 You have several ways to control the Poppy robot, using pre-built Pypot methods/class:
-  * Setting the //goal_position// attribut: the joint will immediately try to go as close to the goal as possible (given the angle limits) w.r.t the maximum speed allowed on this joint (which is set via the //moving_speed// attribut). This will not take the //present_speed// attribut of the joint into account;
+  * Setting the //goal_position// attribute: the joint will immediately try to go as close to the goal as possible (given the angle limits) w.r.t the maximum speed allowed on this joint (which is set via the //moving_speed// attribute). This will not take the //present_speed// attribute of the joint into account;
-  * Setting the //goal_speed// attribut: the joint will immediately set the speed of the joint to the given value, replacing the current //goal_position// with the angle limit corresponding to the speed direction;
+  * Setting the //goal_speed// attribute: the joint will immediately set the speed of the joint to the given value, replacing the current //goal_position// with the angle limit corresponding to the speed direction;
   * Using the //goto_position(goal,time)// method: this will actually set the //goal_position// to the given goal value, and also set the //moving_speed// of the joint to (goal - present_position)/t;
-  * Using the higher level //MovePlayer// class: this class implements a //LoopPrimitive// in order to update frequently the //goal_position// attribut of the joint (N.B: the //moving_speed// attribut __**is not modified**__ by the class when playing the motion and the robot __**will keep in mind the last //moving_speed//**__ sent).
+  * Using the higher level //MovePlayer// class: this class implements a //LoopPrimitive// in order to update frequently the //goal_position// attribute of the joint (N.B: the //moving_speed// attribute __**is not modified**__ by the class when playing the motion and the robot __**will keep in mind the last //moving_speed//**__ sent).
-If the //moving_speed// attribut is set to 0, then the joint will move at full speed (N.B: If you're unsure of the //moving_speed// you sent last to the robot and want to play a movement using //MovePlayer//, it is **__recommended__** to initially set the //moving_speed// of all the involved joints to 0.0).
+If the //moving_speed// attribute is set to 0, then the joint will move at full speed (N.B: If you're unsure of the //moving_speed// you sent last to the robot and want to play a movement using //MovePlayer//, it is **__recommended__** to initially set the //moving_speed// of all the involved joints to 0.0).