![]() ![]() ![]() View this article for more information about using the Print Console in VEXcode 123. Blocks from the 'Looks' category of the Toolbox are used to print to the Print Console in VEXcode 123. In the image shown here, data about the robot's heading at various times while the project is run is being printed. This can help make the visual connection between the project and the actions of the 123 Robot easier to see. Printing to the Print Console in VEXcode 123 be used to display information as a project is running, to help provide visual cues to help see what is happening in a VEXcode 123 project at a specific moment in a project. You can also view sensor data as a project is running to learn more about what the sensor is reporting. You can learn about the blocks or commands in the Toolbox individually by using the Help. There are also tools and strategies that you can use to help you as you learn more about coding your sensor in VEXcode 123. You may also want to try to create your own simplified project to apply what you have learned from the example project to your task. You may want to run the example project multiple times to help with this. Then look at the project to see how the sensor data is being used in order to cause the observed behaviors. Run the example project and observe the robot behavior. In the example project shown here, the note indicates that the Eye Sensor is being used to detect an object so that the robot can stop driving and turn when an obstacle is detected. Once open, read the Note to determine if the functionality in the example project aligns with what you are trying to do with the sensor. If you apply any of these strategies to your project, test your project again to see if this resolved the issue. The following strategies can help you with coding your sensor. Iterating on a project can help you to ensure that the data from the sensor is being used effectively in your project. ![]() Once you have identified that the sensor is not blocked and is reporting data successfully, you can look to your Coder or VEXcode 123 project next. If your 123 Robot or Coder cards did not change, move onto the next step to continue the troubleshooting process. If you changed something to unblock the sensor or adjust a Coder card, test your project again to see if this resolved the issue. You can also try swapping out the 123 Robot you are using with another to see if that resolves your issue. To learn more about the device info shown in the VEX Classroom App view this article. This can help you validate that the sensor is working. Once you have selected the 123 Robot you are troubleshooting, select 'Show Device Info' to view the data for sensors connected to that Brain. Test the sensor’s functionality by looking at the data reported in the VEX Classroom App. Each of the following hardware considerations could be affecting the functionality of your sensor. The second step is to check the hardware on the robot to be sure that the sensor can function as intended. Once you have identified which sensor is causing the unintended behavior, you can move forward in the process. Coding the 123 Eye Sensor with VEXcode 123.Coding the 123 Eye Sensor using the Coder.Is the problematic behavior caused by a sensor? If you need more information to determine if a sensor may be the problem, read the article(s) below related to the sensors on your robot. Compare the observed robot behavior with the intended robot behavior. The first step to troubleshooting your sensor is to identify if the sensor is causing the problem. This article will explain the steps in a troubleshooting process, and provide tips for how to use these steps. When your robot is not behaving as intended while using sensor feedback, you can follow a step-by-step troubleshooting procedure to find and fix your issues. This article's translation was completed by machine translation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |