Difference between revisions of "Talk:Low-cost Robotics"
From AIRWiki
(→Goals) |
(→Communication Middleware) |
||
Line 15: | Line 15: | ||
* Requirements | * Requirements | ||
− | - Low hardware requirements to run on 8-bit microcontrollers | + | - Low hardware requirements to run on 8-bit microcontrollers<br /> |
− | - Some way to sync all processes (distributed clock) | + | - Some way to sync all processes (distributed clock)<br /> |
− | - Lowest possible latency for real time control | + | - Lowest possible latency for real time control<br /> |
− | - Possibility to run on different hardware links (low cost as CAN, high bandwidth as Ethernet, wireless like Zigbee) | + | - Possibility to run on different hardware links (low cost as CAN, high bandwidth as Ethernet, wireless like Zigbee)<br /> |
*Candidates (hardware link) | *Candidates (hardware link) | ||
− | - CAN | + | - CAN<br /> |
− | - Ethernet | + | - Ethernet<br /> |
− | - 802.15.4 - >Zigbee | + | - 802.15.4 - >Zigbee<br /> |
* Candidates (communication protocol) | * Candidates (communication protocol) |
Revision as of 15:06, 23 August 2010
Goals
- September 2010
Written state-of-the art in the area, including a reasoned and commented collection of relevant sites
- September 2010
Selection of an appropriate tool to support plug-and-play interaction among HW/SW modules, on widely used standards (e.g., CAN bus). A candidate is CAN Festival. Test of the tool on ST-based boards (and Microchip as well)
Notes
Communication Middleware
- Requirements
- Low hardware requirements to run on 8-bit microcontrollers
- Some way to sync all processes (distributed clock)
- Lowest possible latency for real time control
- Possibility to run on different hardware links (low cost as CAN, high bandwidth as Ethernet, wireless like Zigbee)
- Candidates (hardware link)
- CAN
- Ethernet
- 802.15.4 - >Zigbee
- Candidates (communication protocol)
- CANopen - TTP/A - UDP - (Ethercat)
- Candidates (communication framework)
- Candidates (middleware)
- Candidates (distributed objects)