RHD:Features: Difference between revisions
From Rsewiki
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
* Hard real-time operation possible | * Hard real-time operation possible | ||
* Linux or RTAI scheduling support | ** Linux or RTAI scheduling support | ||
* 32-bit signed database variables | ** Fixed and accurate timebase | ||
* Two-way variable database | |||
** 32-bit signed database variables | |||
** Timestamps for all variable updated | |||
* TCP / IP Socket interface | * TCP / IP Socket interface | ||
* Only one write-client accepted (first in, first access) | ** Only one write-client accepted (first in, first access) | ||
* Theoretically up to 256 read-clients | ** Theoretically up to 256 read-clients | ||
* Low communication overhead in protocol | ** Low communication overhead in protocol | ||
* Plug-in interface with a range of plugins avalible (see [[RHD:Plug-ins]]) | * Plug-in interface with a range of plugins avalible (see [[RHD:Plug-ins]]) | ||
** Easy plug-in updates using shared libraries | |||
Revision as of 10:37, 6 August 2008
RHD is developed as a flexible hardware abstraction layer framework, that could be used in any application where interaction between a high-level control program and hardware devices are needed in real-time.
The main philosophy of RHD is the idea of a distributed variable database, making all communication variable oriented. A plug-in structure makes it simple to write interfaces to new hardware.
Feature list
- Hard real-time operation possible
- Linux or RTAI scheduling support
- Fixed and accurate timebase
- Two-way variable database
- 32-bit signed database variables
- Timestamps for all variable updated
- TCP / IP Socket interface
- Only one write-client accepted (first in, first access)
- Theoretically up to 256 read-clients
- Low communication overhead in protocol
- Plug-in interface with a range of plugins avalible (see RHD:Plug-ins)
- Easy plug-in updates using shared libraries
