• Ready for review
  • 5. Exploring the Dashboard

    The Duckietown Dashboard is a browser-based interface for interacting with Duckietown robots.

     

    What you will need:

    What you will get:

    • Understanding of Dashboard functionalities, including:

      • diagnostics

      • sensing and actuation

      • development workflow

     

    By the end of this section you will be able to operate the Duckiedrone.

    💀 WARNING: DRONES ARE DANGEROUS AND SERIOUS PHYSICAL HARM CAN OCCUR!💀

    • DO NOT TRY TO CATCH A FALLING DRONE - LET IT CRASH!

    • DO NOT GET CLOSE TO A DRONE WHEN IT IS ARMED

    • DO NOT ARM A DRONE IF SOMEBODY IS AROUND IT

    • DO FOLLOW THESE INSTRUCTIONS CAREFULLY. ALWAYS USE JUDGEMENT AND IN CASE OF DOUBT, ASK A DUCKIETOWN STAFF MEMBER ON SLACK:

     

    For an introduction to the Duckietown Dashboard general features, you can view the Duckietown Library resources, e.g., Duckietown - daffy - Documentation Library

    The Duckiedrone Dashboard

    The Duckiedrone-specific components of the Dashboard are located in the:

    • Robot

    • Code Editor

    pages, accessible from the left (or top) navigation bars.

     

    Troubleshooting

     

    Problem: the Portainer page does not load with a “ hostname.local refuses to connect" error

    Solution: this is a known bug in the version of Portainer we must use for the Duckiedrone. The good news is that the error happens seldomly, and once it is solved, it will not happen again. To clear the error:

    • Open a terminal on your base station

      • Windows: press the Windows key, type cmd, open the command prompt

      • Mac: Press Ctrl+ Spacebar, type terminal, open terminal.app

      • Ubuntu: you should know how to do this

    • Make sure you are connected to your drone

    • Type ssh duckie@hostname.local

      • password is quackquack

      • say yes to whatever it asks regarding permissions and keys - don’t be alarmed by nasty messages of hacking attempts

    • Type (and execute by pressing enter after each line):

      • docker stop portainer

      • docker rm portainer

      • docker volume rm duckietown_portainer-data

      • dt-autoboot

    • Refresh the Dashboard > Portainer page. If the problem has not been solved, try again. It will eventually work.