• View
• Edit
• History
• Print

Lab 4: Wimp Mode in C

Write a program in C to replicate the Create's Wimp Mode.

• Your code should demonstrate the proper use of at least on function that you define and call at least twice in the main function
• Please do not use Create Opcodes to replicate the Wimp Mode.
• This lab is an individual assignment, so I should see YOUR code, not a copy of someone else's. However, you should HELP EACH OTHER work out bugs!!
• Make sure you implement all of the wimp mode functions!
• Bonus (up to + 10%): Feel free to "add a twist" to the Wimp Mode if you like!! (intentional customization only!!) After you master the basic wimp mode code, can you find a way to impress us with a SuperWimp???

Deliverables:

• Demonstrate your program at the beginning of class on Wednesday, November 21 (or in Robotics class or after school on Monday or Tuesday if you are traveling for the holiday on Wednesday)
• Hand in the following STAPLED items at the beginning of class on Wednesday (or prior) in this order:
  • Typed results/conclusions for the lab, no longer than 1/2 of a page.
  • A flowchart for your coded process
  • A copy of your neatly commented code (with line numbers showing)--you should not have any extraneous code (from cutting an pasting from examples)
  • A copy of the compiler output

We can hold one or more after school help sessions beforehand--please let me know what you need!

Formatting notes for the wiki version of your lab report...

1. Make sure you use distinct names for YOUR lab wiki pages
   1. bad choice = Student.Lab4-WimpMode
   2. good choice = Student.RhineLab4-WimpMode
2. Put the lab pages in a logical, easy-to-find place on your personal wiki page
3. Be sure to include your lab report, your code, and your flowchart (don't include HW questions). Format the text portion of your lab report using simple wiki text commands. My favorites:
   1. headings (! !! !!! etc.)
   2. bullets (* ** *** etc.)
   3. numbered lists (# ## ### etc.)
   4. indents (-> --> ---> etc.)
   5. bold, italics, etc.
   6. Colored text is useful
   7. etc.
4. Please Attach a text file with your "main.c" code rather than cuting an pasting directly into a wiki page
   1. Why? Because the wiki page doesn't use a non-proportional font and all white space and tabs at the beginning of each line are ignored by the wiki. All of your careful line spacing and indentation for your code will be lost, and someone trying to read your code will be cursing!!
   2. Example: Attach:RhineLab4Code.txt
   3. Be sure to include the .txt file extension at the end of the name!
   4. If you Be sure to include the .txt file extension at the end of the name!
5. You must attach your flow chart as well...
   1. Example: %newwin% [[Attach:RhineLab4Flow.xls]] will make a link to your excel spreadsheet, and it will open it in a new window!
   2. Only attach commonly used file types and be sure to include the file extension!:
      • Adobe PDF (.pdf)
      • Microsoft Word/Excel/Powerpoint (.doc, .xls, .ppt)
      • Pictures (.bmp, .jpg, .jpeg, .gif, .png, .tiff)
      • Audio/Video (.wav, .mp3, .avi, .mpg, .mpeg, etc.)