e-puck2 PC side development - Revision history

WikiSysop: /* Visual Studio Code and LLM */

2026-09-25T10:57:17Z

Visual Studio Code and LLM

WikiSysop: /* Troubleshooting */

2026-09-25T10:52:43Z

Troubleshooting

← Older revision		Revision as of 10:52, 25 September 2026
Line 917:		Line 917:
	\| ''e-puck2: Stop robot'' fails with a port error \|\| The port is used by <code>Run current file</code> or the REPL: press <code>Ctrl+C</code> in that terminal (or <code>Ctrl+X</code> in the REPL) first.		\| ''e-puck2: Stop robot'' fails with a port error \|\| The port is used by <code>Run current file</code> or the REPL: press <code>Ctrl+C</code> in that terminal (or <code>Ctrl+X</code> in the REPL) first.
	\|-		\|-
	\| The e-puck2 tasks are missing in <code>Run Task...</code> \|\| The opened folder is not the one containing <code>.vscode</code> (check for a nested <code>~~epuck2-micropython-starter~~</code> folder), or the folder is in Restricted Mode: trust it from the ''Restricted Mode'' indicator in the status bar.		\| The e-puck2 tasks are missing in <code>Run Task...</code> \|\| The opened folder is not the one containing <code>.vscode</code> (check for a nested <code>epuck2_micropython_vscode_starter</code> folder), or the folder is in Restricted Mode: trust it from the <code>Restricted Mode</code> indicator in the status bar.
	\|-		\|-
	\| Red underlines on <code>import epuck2</code> \|\| Open the whole <code>~~epuck2-micropython-starter~~</code> folder (not a single file) so that the <code>typings</code> folder is used.		\| Red underlines on <code>import epuck2</code> \|\| Open the whole <code>epuck2_micropython_vscode_starter</code> folder (not a single file) so that the <code>typings</code> folder is used.
	\|-		\|-
	\| <code>/epuck2-micropython</code> is not in the command list \|\| Open the whole <code>~~epuck2-micropython-starter~~</code> folder (''File > Open Folder...''), not a single file.		\| <code>/epuck2-micropython</code> is not in the command list \|\| Open the whole <code>epuck2_micropython_vscode_starter</code> folder (<code>File > Open Folder...</code>), not a single file.
	\|-		\|-
	\| The generated code uses functions that do not exist \|\| The skill was not activated: start the message with <code>/epuck2-micropython</code>.		\| The generated code uses functions that do not exist \|\| The skill was not activated: start the message with <code>/epuck2-micropython</code>.

WikiSysop: /* Troubleshooting */

2026-09-25T10:50:19Z

Troubleshooting

← Older revision		Revision as of 10:50, 25 September 2026
Line 917:		Line 917:
	\| ''e-puck2: Stop robot'' fails with a port error \|\| The port is used by <code>Run current file</code> or the REPL: press <code>Ctrl+C</code> in that terminal (or <code>Ctrl+X</code> in the REPL) first.		\| ''e-puck2: Stop robot'' fails with a port error \|\| The port is used by <code>Run current file</code> or the REPL: press <code>Ctrl+C</code> in that terminal (or <code>Ctrl+X</code> in the REPL) first.
	\|-		\|-
	\| The e-puck2 tasks are missing in ''Run Task...'' \|\| The opened folder is not the one containing <code>.vscode</code> (check for a nested <code>epuck2-micropython-starter</code> folder), or the folder is in Restricted Mode: trust it from the ''Restricted Mode'' indicator in the status bar.		\| The e-puck2 tasks are missing in <code>Run Task...</code> \|\| The opened folder is not the one containing <code>.vscode</code> (check for a nested <code>epuck2-micropython-starter</code> folder), or the folder is in Restricted Mode: trust it from the ''Restricted Mode'' indicator in the status bar.
	\|-		\|-
	\| Red underlines on <code>import epuck2</code> \|\| Open the whole <code>epuck2-micropython-starter</code> folder (not a single file) so that the <code>typings</code> folder is used.		\| Red underlines on <code>import epuck2</code> \|\| Open the whole <code>epuck2-micropython-starter</code> folder (not a single file) so that the <code>typings</code> folder is used.

WikiSysop: /* Troubleshooting */

2026-09-25T10:49:46Z

Troubleshooting

← Older revision		Revision as of 10:49, 25 September 2026
Line 915:		Line 915:
	\| ''epuck2_tool.py requires Python 3.7'' or ''AttributeError'' in <code>epuck2_tool.py</code> \|\| The tasks start the helper with <code>python3</code> (Linux, macOS) or <code>python</code> (Windows): make sure this command runs Python 3 (check with <code>python --version</code>). Also make sure the file open in the editor is your MicroPython program, not the helper.		\| ''epuck2_tool.py requires Python 3.7'' or ''AttributeError'' in <code>epuck2_tool.py</code> \|\| The tasks start the helper with <code>python3</code> (Linux, macOS) or <code>python</code> (Windows): make sure this command runs Python 3 (check with <code>python --version</code>). Also make sure the file open in the editor is your MicroPython program, not the helper.
	\|-		\|-
	\| ''e-puck2: Stop robot'' fails with a port error \|\| The port is used by ''Run current file'' or the REPL: press ''Ctrl+C'' in that terminal (or ''Ctrl+X'' in the REPL) first.		\| ''e-puck2: Stop robot'' fails with a port error \|\| The port is used by <code>Run current file</code> or the REPL: press <code>Ctrl+C</code> in that terminal (or <code>Ctrl+X</code> in the REPL) first.
	\|-		\|-
	\| The e-puck2 tasks are missing in ''Run Task...'' \|\| The opened folder is not the one containing <code>.vscode</code> (check for a nested <code>epuck2-micropython-starter</code> folder), or the folder is in Restricted Mode: trust it from the ''Restricted Mode'' indicator in the status bar.		\| The e-puck2 tasks are missing in ''Run Task...'' \|\| The opened folder is not the one containing <code>.vscode</code> (check for a nested <code>epuck2-micropython-starter</code> folder), or the folder is in Restricted Mode: trust it from the ''Restricted Mode'' indicator in the status bar.

WikiSysop: /* Troubleshooting */

2026-09-25T10:48:14Z

Troubleshooting

← Older revision		Revision as of 10:48, 25 September 2026
Line 907:		Line 907:
	\| <code>mpremote</code> is not recognized \|\| Python is not in the PATH: reinstall Python enabling ''Add python.exe to PATH'', or run <code>python -m pip install mpremote</code>.		\| <code>mpremote</code> is not recognized \|\| Python is not in the PATH: reinstall Python enabling ''Add python.exe to PATH'', or run <code>python -m pip install mpremote</code>.
	\|-		\|-
	\| ''could not enter raw repl'' or no <code>>>></code> prompt \|\| Wrong port (try ~~the other~~ one), selector not in position 3, or the port is used by another program (close any serial terminal).		\| ''could not enter raw repl'' or no <code>>>></code> prompt \|\| Wrong port (try another one), selector not in position 3, or the port is used by another program (close any serial terminal).
	\|-		\|-
	\| Access denied to the serial port (Linux) \|\| <code>sudo adduser $USER dialout</code>, then log out and in again.		\| Access denied to the serial port (Linux) \|\| <code>sudo adduser $USER dialout</code>, then log out and in again.

WikiSysop: /* Configure the serial port */

2026-09-25T10:47:52Z

Configure the serial port

← Older revision		Revision as of 10:47, 25 September 2026
Line 725:		Line 725:
	"epuck2.port": "/dev/ttyACM1", // Linux		"epuck2.port": "/dev/ttyACM1", // Linux
	</pre>		</pre>
	:2. Run the task <code>e-puck2: REPL</code> (<code>Terminal > Run Task...</code>) and press Enter: the MicroPython prompt <code>>>></code> appears if the port is correct. If nothing happens, try ~~the other~~ port. Exit the REPL with <code>Ctrl+X</code>.<br/>		:2. Run the task <code>e-puck2: REPL</code> (<code>Terminal > Run Task...</code>) and press Enter: the MicroPython prompt <code>>>></code> appears if the port is correct. If nothing happens, try another port. Exit the REPL with <code>Ctrl+X</code>.<br/>
	The task <code>e-puck2: List serial ports</code> can be run to list all the serial ports available in the system.		The task <code>e-puck2: List serial ports</code> can be run to list all the serial ports available in the system.

WikiSysop: /* Ideas for further exercises */

2026-09-25T10:46:57Z

Ideas for further exercises

← Older revision		Revision as of 10:46, 25 September 2026
Line 900:		Line 900:
	* Clap to start and stop the robot using <code>get_mic_volume()</code>.		* Clap to start and stop the robot using <code>get_mic_volume()</code>.
	* Detect when the robot is lifted using the accelerometer and stop the motors.		* Detect when the robot is lifted using the accelerometer and stop the motors.

			===Troubleshooting===
			{\| class="wikitable"
			! Problem !! Solution
			\|-
			\| <code>mpremote</code> is not recognized \|\| Python is not in the PATH: reinstall Python enabling ''Add python.exe to PATH'', or run <code>python -m pip install mpremote</code>.
			\|-
			\| ''could not enter raw repl'' or no <code>>>></code> prompt \|\| Wrong port (try the other one), selector not in position 3, or the port is used by another program (close any serial terminal).
			\|-
			\| Access denied to the serial port (Linux) \|\| <code>sudo adduser $USER dialout</code>, then log out and in again.
			\|-
			\| The robot keeps moving after a program ends or is interrupted \|\| The main microcontroller keeps the last motor, LED and sound commands. Run the task ''e-puck2: Stop robot''; in your programs always stop the motors in a <code>finally</code> block.
			\|-
			\| ''epuck2_tool.py requires Python 3.7'' or ''AttributeError'' in <code>epuck2_tool.py</code> \|\| The tasks start the helper with <code>python3</code> (Linux, macOS) or <code>python</code> (Windows): make sure this command runs Python 3 (check with <code>python --version</code>). Also make sure the file open in the editor is your MicroPython program, not the helper.
			\|-
			\| ''e-puck2: Stop robot'' fails with a port error \|\| The port is used by ''Run current file'' or the REPL: press ''Ctrl+C'' in that terminal (or ''Ctrl+X'' in the REPL) first.
			\|-
			\| The e-puck2 tasks are missing in ''Run Task...'' \|\| The opened folder is not the one containing <code>.vscode</code> (check for a nested <code>epuck2-micropython-starter</code> folder), or the folder is in Restricted Mode: trust it from the ''Restricted Mode'' indicator in the status bar.
			\|-
			\| Red underlines on <code>import epuck2</code> \|\| Open the whole <code>epuck2-micropython-starter</code> folder (not a single file) so that the <code>typings</code> folder is used.
			\|-
			\| <code>/epuck2-micropython</code> is not in the command list \|\| Open the whole <code>epuck2-micropython-starter</code> folder (''File > Open Folder...''), not a single file.
			\|-
			\| The generated code uses functions that do not exist \|\| The skill was not activated: start the message with <code>/epuck2-micropython</code>.
			\|-
			\| Copilot shows only ''Auto'' in the model picker \|\| Expected with Copilot Free: manual model selection requires a paid Copilot plan or your own API key (option 3).
			\|}

WikiSysop: /* Debugging exercise: the robot gets stuck */

2026-09-25T09:22:29Z

Debugging exercise: the robot gets stuck

← Older revision		Revision as of 09:22, 25 September 2026
Line 894:		Line 894:
	* Describing the symptom precisely to the assistant ("when an obstacle is straight ahead it rotates left and right forever") gives much better answers than "it doesn't work".		* Describing the symptom precisely to the assistant ("when an obstacle is straight ahead it rotates left and right forever") gives much better answers than "it doesn't work".
	\|}		\|}

			====Ideas for further exercises====
			* Use the ToF sensor (<code>get_distance()</code>) to slow down smoothly in front of an obstacle.
			* Choose the behaviour with the selector (<code>get_selector()</code>): avoidance, wall following, follow an object.
			* Clap to start and stop the robot using <code>get_mic_volume()</code>.
			* Detect when the robot is lifted using the accelerometer and stop the motors.

WikiSysop: /* Ideas for further exercises */

2026-09-25T09:21:41Z

Ideas for further exercises

← Older revision		Revision as of 09:21, 25 September 2026
Line 873:		Line 873:
	\|		\|
	With <code>rotate_dir = 1</code> the code sets <code>left_speed = -ROTATE_SPEED</code> and <code>right_speed = +ROTATE_SPEED</code>: the robot rotates to the '''left''', not to the right as the comment says. So it turns '''towards''' the obstacle instead of away from it.<br/>		With <code>rotate_dir = 1</code> the code sets <code>left_speed = -ROTATE_SPEED</code> and <code>right_speed = +ROTATE_SPEED</code>: the robot rotates to the '''left''', not to the right as the comment says. So it turns '''towards''' the obstacle instead of away from it.<br/>

	~~====Ideas for further exercises====~~
	* Use the ToF sensor (<code>get_distance()</code>) to slow down smoothly in front of an obstacle.
	* Choose the behaviour with the selector (<code>get_selector()</code>): avoidance, wall following, follow an object.
	* Clap to start and stop the robot using <code>get_mic_volume()</code>.
	* Detect when the robot is lifted using the accelerometer and stop the motors.


	While it turns towards the obstacle, the obstacle moves from the front-left to the front-right sensors, <code>front_right</code> becomes bigger than <code>front_left</code> and the direction is reversed; then the same happens on the other side. The error in the sign creates a positive feedback around the centre: the robot oscillates forever (a live-lock).		While it turns towards the obstacle, the obstacle moves from the front-left to the front-right sensors, <code>front_right</code> becomes bigger than <code>front_left</code> and the direction is reversed; then the same happens on the other side. The error in the sign creates a positive feedback around the centre: the robot oscillates forever (a live-lock).

WikiSysop: /* Debugging exercise: the robot gets stuck */

2026-09-25T09:19:44Z

Debugging exercise: the robot gets stuck

← Older revision		Revision as of 09:19, 25 September 2026
Line 873:		Line 873:
	\|		\|
	With <code>rotate_dir = 1</code> the code sets <code>left_speed = -ROTATE_SPEED</code> and <code>right_speed = +ROTATE_SPEED</code>: the robot rotates to the '''left''', not to the right as the comment says. So it turns '''towards''' the obstacle instead of away from it.<br/>		With <code>rotate_dir = 1</code> the code sets <code>left_speed = -ROTATE_SPEED</code> and <code>right_speed = +ROTATE_SPEED</code>: the robot rotates to the '''left''', not to the right as the comment says. So it turns '''towards''' the obstacle instead of away from it.<br/>

			====Ideas for further exercises====
			* Use the ToF sensor (<code>get_distance()</code>) to slow down smoothly in front of an obstacle.
			* Choose the behaviour with the selector (<code>get_selector()</code>): avoidance, wall following, follow an object.
			* Clap to start and stop the robot using <code>get_mic_volume()</code>.
			* Detect when the robot is lifted using the accelerometer and stop the motors.


	While it turns towards the obstacle, the obstacle moves from the front-left to the front-right sensors, <code>front_right</code> becomes bigger than <code>front_left</code> and the direction is reversed; then the same happens on the other side. The error in the sign creates a positive feedback around the centre: the robot oscillates forever (a live-lock).		While it turns towards the obstacle, the obstacle moves from the front-left to the front-right sensors, <code>front_right</code> becomes bigger than <code>front_left</code> and the direction is reversed; then the same happens on the other side. The error in the sign creates a positive feedback around the centre: the robot oscillates forever (a live-lock).

← Older revision		Revision as of 10:57, 25 September 2026
Line 662:		Line 662:
	* [https://code.visualstudio.com/ Visual Studio Code]		* [https://code.visualstudio.com/ Visual Studio Code]
	* [https://www.python.org/downloads/ Python 3.9 or later] (only needed on the PC, to run the <code>mpremote</code> tool)		* [https://www.python.org/downloads/ Python 3.9 or later] (only needed on the PC, to run the <code>mpremote</code> tool)
	* The starter project: [https://projects.gctronic.com/epuck2/epuck2_micropython_vscode_starter.zip epuck2_micropython_vscode_starter.zip]		* The starter project: [https://projects.gctronic.com/epuck2/micropython/epuck2_micropython_vscode_starter.zip epuck2_micropython_vscode_starter.zip]
	* Optional, for the AI assistant: a free [https://github.com/signup GitHub account] or subscription		* Optional, for the AI assistant: a free [https://github.com/signup GitHub account] or subscription

Line 690:		Line 690:

	====Open the starter project====		====Open the starter project====
	# Download and unzip [https://projects.gctronic.com/epuck2/epuck2_micropython_vscode_starter.zip epuck2_micropython_vscode_starter.zip].		# Download and unzip [https://projects.gctronic.com/epuck2/micropython/epuck2_micropython_vscode_starter.zip epuck2_micropython_vscode_starter.zip].
	# In VS Code choose <code>File > Open Folder...</code> and select the <code>epuck2_micropython_vscode_starter</code> folder, the one that directly contains the <code>.vscode</code> folder (some unzip tools create a second folder with the same name around it).		# In VS Code choose <code>File > Open Folder...</code> and select the <code>epuck2_micropython_vscode_starter</code> folder, the one that directly contains the <code>.vscode</code> folder (some unzip tools create a second folder with the same name around it).
	# If asked, confirm that you trust the authors of the folder: tasks and settings are disabled in Restricted Mode.		# If asked, confirm that you trust the authors of the folder: tasks and settings are disabled in Restricted Mode.
Line 853:		Line 853:
	If the robot misbehaves, describe the observed behavior to the assistant (for example "it turns towards the obstacle instead of away from it") instead of just asking to "fix it": the diagnosis is part of the exercise.		If the robot misbehaves, describe the observed behavior to the assistant (for example "it turns towards the obstacle instead of away from it") instead of just asking to "fix it": the diagnosis is part of the exercise.
	====Debugging exercise: the robot gets stuck====		====Debugging exercise: the robot gets stuck====
	This is the code [https://projects.gctronic.com/epuck2/obstacle_avoidance_lights_first_attempt.py obstacle_avoidance_lights_first_attempt.py] we obtained the first time with Copilot ''Auto'' and the prompt above, without any change. To try it, copy it into a new file of the project, for example <code>debug_exercise.py</code>, and run it. <br/>		This is the code [https://projects.gctronic.com/epuck2/micropython/obstacle_avoidance_lights_first_attempt.py obstacle_avoidance_lights_first_attempt.py] we obtained the first time with Copilot ''Auto'' and the prompt above, without any change. To try it, copy it into a new file of the project, for example <code>debug_exercise.py</code>, and run it. <br/>
	It looks correct and it runs, but on the real robot something goes wrong: when an obstacle is straight ahead, the robot starts rotating to one side, then to the other side, and keeps switching forever, beeping at every change, without ever getting away.		It looks correct and it runs, but on the real robot something goes wrong: when an obstacle is straight ahead, the robot starts rotating to one side, then to the other side, and keeps switching forever, beeping at every change, without ever getting away.