1 / 67

Motors and Sound Troubleshooting Tips

Motors and Sound Troubleshooting Tips. Problem 1. Why can’t I download my program to the RCX?. Solution 1. The RCX was facing the wrong direction. (Don’t forget to turn it on too!). InfraRed receiver must face IR Tower. Problem 2. Why won’t the motor work?. Solution 2.

urbano
Download Presentation

Motors and Sound Troubleshooting Tips

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Motors and SoundTroubleshooting Tips

  2. Problem 1 Why can’t I download my program to the RCX?

  3. Solution 1 The RCX was facing the wrong direction. (Don’t forget to turn it on too!) InfraRed receiver must face IR Tower

  4. Problem 2 Why won’t the motor work?

  5. Solution 2 It was connected to a sensor port. Motor ports are A, B, and C. Sensor ports Motor ports

  6. Problem 3 What is wrong with this program?

  7. Solution 3 Bad wiring. Always check for bad wires. Missing wire Bad wire

  8. Problem 4 This program is supposed to turn on Motor A for 4 seconds, then turn off the motor. What’s wrong?

  9. Solution 4 There was no “Stop Motor” icon.

  10. Wiring Tips andTroubleshooting

  11. Many of the problems associated with programming in Robolab have to do with mistakes in wiring the Icons or Modifiers.

  12. Problem 5 This Program looks good at first glance, but notice the broken black arrow on the upper left hand corner of the screen. If you click on the arrow, you will see the list of errors

  13. Solution 5 The List of Errors shows that neither the input nor the output of the ‘Wait For 4 Seconds’ Icon are wired. It looks like the programmer just laid the icon over the wire. If you grab the icon and drag it down, you can see this clearly.

  14. Problem 6 This Program looks just like the previous one, and again notice the broken black arrow on the upper left hand corner of the screen. If you click on the arrow, you will see a different list of errors.

  15. Solution 6 This time, there’s only one error listed. It says that the end of the ‘Stop All Outputs’ Icon isn’t wired. If you’re in the ‘Select’ mode of the tools palette (that’s the arrow) and highlight the wire connected to the Red Light, you’ll see a ghost image of the wire connected from the input of the Stop Sign to the input of the red light.

  16. Problem 7

  17. The List of Errors tells us that the ‘Motor C Forward’ Icon isn’t wired. But when we click on one of the errors, neither corner of the ‘Motor C Forward’ Icon flash. And, when we look at the icon, we can see that it is correctly wired……hmm!

  18. Solution 7 What happened here is that our programmer took the icon off the palette by mistake and rather than delete it, he tried to put it back on the palette. In trying this, all he did was hide the icon under the palette. Delete this icon and the arrow will turn white.

  19. Problem 8 The robot is supposed to go forward for 4 second but it stops after only 1. What could be wrong?

  20. Problem 8 Someone forgot to wire the modifier to the ‘Wait for Time’ Icon. Every icon that can have a modifier has a “Default Value.” The default value for the ‘Wait for Time’ icon is 1 second.

  21. Modifiers, Loops and JumpsTroubleshooting Tips

  22. Problem 9 Write a program that plays a beep three times in a row. This plays sound #3, NOT 3 sounds.

  23. Solution(s) 9 Use 3 Play Sound icons, or use a loop that loops 3 times.

  24. Problem 10 Turn on motor A at power level 1. This is a numeric constant modifier NOT a power level modifier. (Strangely enough, it does not show a bad wire. Hmmmm…..)

  25. Solution 10 Use a Power Level 1 modifier.

  26. Problem 11 Write a program that beeps forever. What’s wrong? But this is a red land This is a yellow jump

  27. Solution 11 Make sure jump and land pairs are the same color.

  28. Problem 12 Write a program that beeps forever. What’s wrong now? Land here End Start Jump to green land Oops!

  29. Solution 12 Be careful not to mix up the order of your jumps and lands!

  30. Sensor Wait-for’sTroubleshooting Tips

  31. Problem 13 Why won’t the light sensor work? This is a motor port.

  32. Solution 13 Sensors need to be connected to sensor ports 1, 2 or 3. Sensor ports

  33. Problem 14 The touch sensor is connected to port 1. What’s wrong with this set up? But the software says the touch sensor is on port 3.

  34. Solution 14 Connect the touch sensor to port 3. Or, change the port number in the software.

  35. Problem 15 Why won’t the touch sensor work?

  36. Solution 15 Make sure the cable is connected to the front of the touch sensor. WRONG RIGHT

  37. Problem 16 What isn’t too great about the way the light sensor is mounted?

  38. Solution 16 If the light sensor is too high, it has a harder time distinguishing between dark and light. Mounting it lower to the ground will help.

  39. Problem 17 What’s wrong with this program? What is the default port? What is the default port?

  40. Solution 17 Remember: Different sensors MUST be on different ports in the software. If a port is not specified, it assumes Port 1.

  41. Problem 18 This program should turn on motor A until the rotational sensor has turned 2 revolutions, then turn off the motor. Why doesn’t it work? Hint: What is the default number of ticks in a Wait-for Rotation icon?

  42. Solution 18 The default number of ticks is 16, or 1 revolution. For 2 revolutions, you must specify the number of ticks with a numeric constant modifier. 32 ticks = 2 revolutions

  43. Conditional StatementsTroubleshooting Tips

  44. Problem 19 What’s wrong with this program?

  45. Solution 19 Remember: All forks need a fork merge.

  46. Problem 20 This program is supposed to turn on motor A if the touch sensor is pressed, otherwise turn on motor C. What’s wrong?

  47. Solution 20 The branches of the fork are mixed up. This is a common mistake.

  48. Problem 21 In this program, if the light sensor reads a value above 80, it should turn on motor B. Otherwise, it should beep. Why doesn’t it work? Hint: What is the default light level value?

More Related