RH+SF
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Help
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    --- tags: robot, prework --- # Before You Start Before starting any project, there are some steps to take to ensure that you don't hit any problems and that things go smoothly. Here's our recommendations to ensure a successful robot build. ### Recommended Age and Prerequisite Skills This activity is best suited for ages 10 and up. There are no specific skills necessary to complete the project (and no prior knowledge of programming is assumed), though it takes a little bit of dexterity (or help from a patient adult) to assemble the chassis and connect the wires. ### Time Requirements **Build** - 1-2 hours **Programming** - 1-2 hours ### Tools and Materials 1. The [Red Hat Co.Lab Robot Kit](https://www.sparkfun.com/products/16424). 1. A computer -- with a web browser and access to the Internet *OR* a phone or tablet with the [Microsoft MakeCode app](https://www.microsoft.com/en-us/p/makecode-for-micro-bit/9pjc7sv48lcx?activetab=pivot:overviewtab) on it. 1. Electrical tape, paint marker or another way to mark parts -- this makes it easier to keep track of them *(not necessary, but helpful)* 1. Slip-joint pliers -- useful to grip parts during assembly (*not necessary, but helpful)* **Project checklist** ☑ Read Requirements and Assemble Tools ☐ Read the Instructions ☐ Identify the Parts ☐ Build Your Project ☐ Testing ☐ Show it off! ### Read the Instructions You know how people always say "Read all the instructions before starting?" It really does help. (Hint: try to familiarize and yourself with the parts you'll be using as you're reading through the instructions.) **Project checklist** ☑ Read Requirements and Assemble Tools ☑ Read the Instructions *(because you did, right?)* ☐ Identify the Parts ☐ Build Your Project ☐ Testing ☐ Show it off! ### Identify the Parts Chefs lay out the tools and ingredients they need to make a dish before they even start cooking because it helps them save time and avoid mistakes. This is called *mise en place*, a French term that means "everything in its place." When you're working on an engineering project, doing your own *mise en place* will help you too. You've already assembled your tools and materials, and read the instructions, so the remaining step is to lay out your "ingredients," or the parts of your project. As you're reading the instructions, lay each part out all the parts on your worktable, placing all parts of the same type together and counting them. ***Why?*** Well, unfortunately, sometimes instructions don’t do a great job of specifying which of the somewhat-similar-but-slightly-different parts you should use on a given step (and sometimes there aren’t pictures to help out). But if the instructions call for a certain number of that part, you can sometimes use the number of each part you received to help you figure out which part to use. Take a look at this picture, which should show almost the same pieces you have (you will also have some cool stickers, a 6” microUSB cord, 4 AA batteries, and 2 AAA batteries): -> [![alt text](https://cdn.sparkfun.com/r/600-600/assets/learn_tutorials/1/2/0/4/image34.jpg)](https://cdn.sparkfun.com/assets/learn_tutorials/1/2/0/4/image34.jpg) <- Suppose the instructions said: > Attach one side strut to each of the four corners of the bottom chassis. > (Don’t worry, these instructions will be more clear than that, we hope!) Even if you didn’t know which part was supposed to be the “side strut” (and how could you?), you could figure it out because there’s only one part that you have four of! This process also helps in case the manufacturer made a mistake and you’re missing a piece -- it’s easier if you find this out before you’re very-nearly-done and excited to show off your cool project. I even like to label my parts as I'm laying them out. It saves me a lot of time hunting around on my desk if everything is laid out and labeled with its name. I use a sheet of paper on top of my desk, which both helps protect my table and gives me a place to label my parts. The final result looks something like this: -> [![alt text](https://cdn.sparkfun.com/assets/learn_tutorials/1/2/0/4/image17.png)](https://cdn.sparkfun.com/assets/learn_tutorials/1/2/0/4/image17.png) <- ### Your Robot's Major Systems Your robot's anatomy has several major systems, which are similar to the ones that humans have: * **brains** -- your robot has a main brain, the micro:bit, and a "helper brain," the moto:bit, that allows the robor to do more. * **a chassis** - the "skeleton" of the robot that everything else (like the motors, wheels, and brains) gets attached to * **the drive assembly** - Not all robots move, but yours does, and "drive assembly" is the technical term for the parts of the robot that allow it to move (the motors and wheels). This is sort of like your muscle system. * **sensors** -- that allow your robot to "see." We'll add those sensors in this tutorial, but we'll program them and put them into use in a later tutorial. <!-- youtube(https://youtu.be/-Va7g1q24col) --> **TEST LINK** <!-- youtube(https://www.youtube.com/watch?v=EPZ64mnSwJw&feature=youtu.be) --> Let’s look a little more closely at the major parts -- organs, if you will -- of your robot's anatomy before we start building. #### The micro:bit Find your micro:bit -- the "brains" of your robot. The micro:bit is packed with functionality (some of which we'll use in later tutorials). Check out the Resources and Going Further section to learn more about this microcontroller and what you can do with it. For now, though, take a look at the features on the front -> [![alt text](image link for front)](https://cdn.sparkfun.com/assets/learn_tutorials/1/2/0/4/image12.png) <- and the back -> [![alt text](image link for back)](https://cdn.sparkfun.com/assets/learn_tutorials/1/2/0/4/image12.png) <- #### The SparkFun moto:bit The micro:bit is pretty powerful on its own, but it can do even more when you plug it into the moto:bit, a "carrier board" which acts like a helper brain. The moto:bit can communicate with motors and can relay information from sensors back to the micro:bit. It also has a power jack that lets you attach a larger battery pack, that both allows your robot to range untethered as well as giving it the extra power the motors need. This picture identifies the parts of the moto:bit that will be important while building your robot. -> [![alt text](https://cdn.sparkfun.com/assets/learn_tutorials/1/2/0/4/image12.png)](https://cdn.sparkfun.com/assets/learn_tutorials/1/2/0/4/image12.png) <- #### Robot Chassis Your robot's chassis (its "skeleton") is made out of laser-cut plastic parts that we're going to put together. ->![https://cdn.sparkfun.com//assets/parts/1/0/5/6/0/13301-Action01.jpg](https://cdn.sparkfun.com//assets/parts/1/0/5/6/0/13301-Action01.jpg)<- But before we can put the chassis together we need to snap out a few small parts from the two main pieces of the chassis. <div class="alert alert-warning"><b>NOTE:</b> Don’t use pliers (or hammers or drills or …). These should come out easily if you twist them a little in the frame as they are just held in by a thin piece.</div> <!-- youtube(https://youtu.be/-Va7g1q24co?t=192) --> You should end up with seven new-and-shiny pieces, like these ((new image is here: https://drive.google.com/file/d/1LWdfdQKBBaUM8M8gqi6W_6YzKnaTszF9/view?usp=sharing)): -> [![alt text](https://cdn.sparkfun.com/r/600-600/assets/learn_tutorials/1/2/0/4/image10.png)](https://cdn.sparkfun.com/assets/learn_tutorials/1/2/0/4/image10.png) <- #### A Note on Orientation Along with laying out, counting, identifying, and labeling all the parts in advance, I also like to do whatever I can to make things a little easier when I assemble projects. One way that I do that is by giving myself some obvious orientation clues when I’m working with parts that I might have a chance to put on upside down or backwards. The robot instructions reference (see the picture below) <ul> <li>the Top Chassis and the Bottom Chassis</li> <li>the “front” of the robot (the end the front bumper would be on if it had one) and the "back"</li> <li>the “top” of each chassis (the textured side) and the "bottom" (the smooth side)</li> <li>and the Left and Right of each chassis, which is relative to the “front”</li> </ul> -> [![robot orientation](https://cdn.sparkfun.com/r/600-600/assets/learn_tutorials/6/4/4/micro-bot_Kit_Tutorial_update-05-GIMPED.jpg)](https://cdn.sparkfun.com/r/600-600/assets/learn_tutorials/6/4/4/micro-bot_Kit_Tutorial_update-05-GIMPED.jpg) <- In order to help me avoid mistakes when assembling my robot, I mark the pieces that look similar so I can easily tell the top from the bottom, the front from the back, and the left from the right. This video shows how I marked the orientation of the chassis parts for my robot: <!-- youtube(https://youtu.be/-Va7g1q24co?t=268) --> You can mark your parts to show the orientation in any number of ways -- by writing on one corner of each piece with a paint pen, adding a sticker, or using some tape. The important thing is to do it consistently -- if you’re marking the upper lefthand corner, do that on *all* the pieces. Or if you’re using a green mark to indicate the top of the part and red to indicate the bottom, do *that* on all the pieces. My robot ended up looking like this: <!-- youtube(https://youtu.be/-Va7g1q24co?t=268) --> **[INSERT L / R PHOTO]** -- is here https://drive.google.com/file/d/1FmFqoSS2Ekkc0uqDArh89duEH8cR49TW/view?usp=sharing Since you have the neat stickers that came with your robot, you could use one of them to mark the front left corner (and remember which one you used!), put the other on the right front corner, then use a piece of tape to mark the Lower Chassis front left corner. This may sound like a lot to do before you start, but if you’ve ever tried to put something together and you can’t find the right part -- or worse, you had the right part, but you put it in the wrong place or upside-down -- this will make sense. **Project checklist** ☑ Read Requirements and Assemble Tools ☑ Read the Instructions ☑ Identify the Parts ☐ Build Your Project ☐ Testing ☐ Show it off!

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully