|
|
|
![]() |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#8
|
||||
|
||||
|
Re: Alpha Weekend #2, 2015 Control System
Forgive me if this is on a website, or already posted, but I have a few questions about the new control system.
1. How are the times to deploy code, reimage, reboot, or connect? 2. What is the overall quality of the board and its software? 3. Are there any tools to monitor the CPU/RAM usage of the system? If so, what is the typical usage? 4. Have you confirmed the brownout voltage, or seen any part of the system drop out? 5. How well does CAN work? Are there still issues with floods of errors? 6. I2C/SPI/Serial timing? Does it work? 7. Encoders-how fast with 4x sampling, can it still do averaging? Does it have issues with getRate? 8. How much of the linux operating system is exposed? Have you used any linux features yet? 9. We're one of those teams that just wants a single solenoid for shifting so we don't want the fancy pneumatics bumper, but we use more than 4 relays on most robots. How much current can the DIO source? Enough for a relay? Can the super expansion port do it? 10. Most importantly, what are the plans for the cRIOs? Can we use them on a practice bot next year? When LV/windriver licenses run out, do we end up with really expensive paperweights? That would really suck. A lot. 11. How robust is communication? How often is there an issue between any parts communicating with each other? 12. How easy is it to troubleshoot these issues? Thanks! |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|