Differences

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

--- blog:lets-talk-about-duckietown [2025/01/15 07:18] – harley.lara
+++ blog:lets-talk-about-duckietown [2025/04/05 23:58] (current) – harley.lara
@@ Line 4: / Line 4: @@
 In April 2024 we received a batch of 12 Duckiebots with NVIDIA Jetson Nano 4GB (variant [[https://get.duckietown.com/products/duckiebot-db21?variant=41543707099311|DB21J]]) as part of the [[https://get.duckietown.com/products/classroom-kit-12|Classroom Kit (12)]]. The main motivation behind choosing duckietown as our educational robot was mainly based on two aspects:
-. Open Hardware and documentation: The fact that it is Open Hardware gives us the flexibility (in the future) to extend the capabilities of the robot with different sensors or actuators.
+  - Affordable hardware (initially we thought it was open hardware): The fact that it is Open Hardware gives us the flexibility (in the future) to extend the capabilities of the robot with different sensors or actuators.
-. Educational content: Duckietown offers a [[https://learning.edx.org/course/course-v1:ETHx+DT-01x+3T2023/home|MOOC on autonomous driving]], plus a series of exercises and notebooks called [[https://github.com/duckietown/duckietown-lx/|duckietown-lx]] as practical implementations of some concepts, this was the selling point to choose duckietown as it offloaded the amount of work required to prepare the material and exercises of a course from scratch, so it left us more freedom to focus on supporting students in their learning process instead of worrying about the material.
+  - Educational content: Duckietown offers a [[https://learning.edx.org/course/course-v1:ETHx+DT-01x+3T2023/home|MOOC on autonomous driving]], plus a series of exercises and notebooks called [[https://github.com/duckietown/duckietown-lx/|duckietown-lx]] as practical implementations of some concepts, this was the selling point to choose duckietown as it offloaded the amount of work required to prepare the material and exercises of a course from scratch, so it left us more freedom to focus on supporting students in their learning process instead of worrying about the material.
 ===== About the Hardware =====
@@ Line 37: / Line 37: @@
 With that preamble the following is a set of good things, and some things we consider not so good about the Duckietown software stack.
-**Software on students' laptops:** TBA
+**Software on students' laptops:**
+  * [[https://docs.duckietown.com/daffy/opmanual-duckiebot/setup/setup_laptop/setup_dt_shell.html|dts (Duckietown shell)]]
+  * [[https://docs.duckietown.com/daffy/opmanual-duckiebot/setup/setup_account/index.html|Setup Github Account and SSH keys]]
+  * The dts (Duckietown shell) **requires** [[https://docs.duckietown.com/daffy/opmanual-duckiebot/setup/setup_account/duckietown_accounts.html|Setup a Duckietown account and setup an access token]].
+  * [[https://docs.duckietown.com/daffy/opmanual-duckiebot/setup/setup_account/docker_accounts.html|Setup DockerHub account and DockerHub Access Token]]
-**Software on the robot:** TBA
+**Software on the robot:**
+The setup in the robot is like a blackbox, you get a pre-build image (see [[https://github.com/duckietown/duckietown-shell-commands/blob/e3b05f268bb9854b5207114b27bdbf280a661e48/disk_image/create/jetson_nano/private_command.py#L76-L79 | duckietown-shell-commands source code]]) and you burn it into the microSD. There is no information (as far as I know) how this image is configured, what tools it contains, modifications, patches etc.