Changes for page Humanoid Robot

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -9,7 +9,7 @@
9	9
10	10	Next to their unsuitability for taking walks, the abovementioned humanoid robots also have facial features and movements which lie in the uncanny valley [[(Mori et al., 2012)>>https://doi.org/10.1109/MRA.2012.2192811]]. This may cause unexpected modals of interaction with the robot that cannot be accounted for.
11	11
12		-[[Miro>>https://www.miro-e.com/robot]], on the other hand, is a small robot dog with wheels. We ultimately chose MiRo because it has all the necessary features to facilitate walks, without any downsides. Next to this, a dog is automatically associated with taking a walk. Also, the robot dog has dog like features, allowing it to respond to touch, make noises and move certain parts to resemble a dog. Its dog-like appearance and its ability to act like a dog will allow the dog to become a companion. More research on why a dog-like robot could be a suitable robotic partner can be found in the [[Robotic partner>>https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group02/view/Foundation/Human%20Factors/Robotic%20Partner/]] section.
	12	+[[MiRo>>https://www.miro-e.com/robot]], on the other hand, is a small robot dog with wheels. We ultimately chose MiRo because it has all the necessary features to facilitate walks, without any downsides. Next to this, a dog is automatically associated with taking a walk. Also, the robot dog has dog like features, allowing it to respond to touch, make noises and move certain parts to resemble a dog. Its dog-like appearance and its ability to act like a dog will allow the dog to become a companion. More research on why a dog-like robot could be a suitable robotic partner can be found in the [[Robotic partner>>https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group02/view/Foundation/Human%20Factors/Robotic%20Partner/]] section.
13	13
14	14	=== Working with MiRo ===
15	15	==== MiRo's capabilities ====
...	...	@@ -26,9 +26,9 @@
26	26	=====Programming difficulties=====
27	27	The creators of MiRo have set up MiRoCloud to allow people to determine the behaviour of MiRo. When using Mirocloud, there are two possibilities: using the block-based programming method 'Blockly', or coding the behaviour in Python. Blockly is mainly created for the purpose of teaching children how to program. The ease of use that this brings severely hinders the capabilities of MiRo, as you can only execute blocks in sequence. You can also start creating MiRo's behaviour in Blockly and then convert this to Python code, but we noticed that Blockly does not always create runnable code. For example, if one is using arrays/lists, Blockly can accidentally place NaN when trying to access an item from the list. You can also write the behaviour in Python directly, but unfortunately, the environment is a Sandbox. You can not use external modules (and thus not import things), so only basic Python code can be used. Furthermore, we have noticed that MiroCloud breaks a lot, either on the PC itself or in connecting with the robot. A lot of the time, MiroCloud will give an error when trying to send code to the Robot (such as 'camera's can't be accessed'). MiroCloud also gives an error on Chromium-based browsers, which can be solved by using Firefox. Finally, we have tried to get the robot to make sounds ,but we were only able to send specific Hertz ranges to the robot for a certain amount of time. Unfortunately, we were not able to get a sound that resembled a dog.
28	28
29		-The other option for controlling MiRo is to not use the MiroCloud system, but to try to install the MDK and use it. Unfortunately, this proved to be very difficult. A set-up guide can be found [[here >> http://labs.consequentialrobotics.com/miro-e/docs/index.php?page=Developer_Install_Steps_Install_MDK]]. When it has been installed, it is difficult to use the MDK as accessing the robot and coding it is very difficult. Unfortunately, we did not manage to get this running after a number of tries, and instead focused on developing the idea of our solution further.
	29	+The other option for controlling MiRo is to not use the MiroCloud system, but to try to install the MDK and use it. Unfortunately, this proved to be very difficult. A set-up guide can be found [[here>>http://labs.consequentialrobotics.com/miro-e/docs/index.php?page=Developer_Install_Steps_Install_MDK]]. When it has been installed, it is difficult to use the MDK as accessing the robot and coding it is very difficult. Unfortunately, we did not manage to get this running after a number of tries, and instead focused on developing the idea of our solution further.
30	30
31	31
32	32	=====Wizard of Ozzing=====
33		-The MiRo robot can be controlled with certain PS4 controllers. We have noticed that PS5 controllers will also work but the head can't be controlled as that one is mapped to the triggers and they need to be held in the middle to keep the head of the MiRo in the middle. Pairing the MiRo with a controller can be used by following the steps on the following page: [[PS4 Setup >> http://labs.consequentialrobotics.com/miro-e/docs/index.php?page=Husbandry_MIROapp_Home_page_Remote_settings_dialog]]. On this page, one can also found which controllers can be used. The controls are on the following page: [[PS4 Controls >> http://labs.consequentialrobotics.com/miro-e/docs/index.php?page=Husbandry_MIROapp_Controller_manager_Remote_controller]]
	33	+The MiRo robot can be controlled with certain PS4 controllers. We have noticed that PS5 controllers will also work but the head can't be controlled as that one is mapped to the triggers and they need to be held in the middle to keep the head of the MiRo in the middle. Pairing the MiRo with a controller can be used by following the steps on the following page: [[PS4 Setup>>http://labs.consequentialrobotics.com/miro-e/docs/index.php?page=Husbandry_MIROapp_Home_page_Remote_settings_dialog]]. On this page, one can also found which controllers can be used. The controls are on the following page: [[PS4 Controls>>http://labs.consequentialrobotics.com/miro-e/docs/index.php?page=Husbandry_MIROapp_Controller_manager_Remote_controller]]
34	34