Primarily useful for teams already using a Raspberry Pi as a coprocessor. Supports 1-4 color sensors, sends data to the roboRIO via NetworkTables. The Pi Pico is low cost (less than $10) and readily available. Supports up to 2 REV color sensors, sends data to the roboRIO via serial. A similar approach could be used for other I2C sensors. Several alternatives exist for accessing the REV color sensor without using the roboRIO I2C port. So it waits for whatever the program was meant to do to be done then messes up. As soon as the triangle is made it stops responding. One part is making a program where the user clicks 3 points in the window, then it makes a triangle from connecting the points. If you can access your roboRIO via any of these methods, you are experiencing a different issue. Basically when I start a program it immediately doesn't respond. This lockup is a CPU/kernel hang, the roboRIO will completely stop responding and will not be accessible via the DS, webpage or SSH. This lockup can not be definitively identified on the field and a field fault will not be called for a match where this behavior is believed to occur. Acessing the device less frequently and/or using a different roboRIO may significantly reduce the likelihood/frequency of lockups, it will be up to each team to assess their tolerance of the risk of lockup. Workaround: The only surefire mitigation is to use the MXP I2C port or another device to read the I2C data. different roboRIOs will behave differently) as well as how the bus is being used. The frequency of these lockups appears to be dependent on the specific hardware (i.e. Issue: Use of the onboard I2C port, in any language, can result in system lockups.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |