wevets
28-10-2011, 00:16
Does anyone know where I can find an end-to-end description of the FRC control system? It would need to show:
1. End-to-end from (joy stick movement) to (driver interface), (across the wireless link to the cRIO) to (digital sidecar) to (victor or other controller) to (motor)
2. End-to-end from, say a sensor or cRIO (i.e. battery voltage) back to operator display.
3. What the signals look like (i.e. if digital, what format, if PWM, pulse descriptions, if motor drive from controller, what that looks like) at each point.
4. IP addresses (or IP addess templates) of each device
5. Differences in signal paths at competition and during development.
6. At a low enough level to be independent of programming system (Java, LabView, etc.), but high enough level to understand how messages get across the system.
7. Any other info that would help with giving a quick leg-up on how the control system works.
If all this already exists in some document, would you point me to it?
I'd like my team to have more than a cook-book understanding of how the control system goes together, and I think other teams might benefit from this, too.
Thanks.
wevets
1. End-to-end from (joy stick movement) to (driver interface), (across the wireless link to the cRIO) to (digital sidecar) to (victor or other controller) to (motor)
2. End-to-end from, say a sensor or cRIO (i.e. battery voltage) back to operator display.
3. What the signals look like (i.e. if digital, what format, if PWM, pulse descriptions, if motor drive from controller, what that looks like) at each point.
4. IP addresses (or IP addess templates) of each device
5. Differences in signal paths at competition and during development.
6. At a low enough level to be independent of programming system (Java, LabView, etc.), but high enough level to understand how messages get across the system.
7. Any other info that would help with giving a quick leg-up on how the control system works.
If all this already exists in some document, would you point me to it?
I'd like my team to have more than a cook-book understanding of how the control system goes together, and I think other teams might benefit from this, too.
Thanks.
wevets