Commands
Design > Commands
Commands
Commands are the "methods" of the modules. Different versions of a module share, i.e. "inherit" the commands of earlier versions of the same module.
A module is a type of node. A module is the hardware analog of an object oriented software class. Multiple instances of a module may exist in a hardware implementation. Each of these instances would be a node running identical software even though they would operate uniquely because of their individual unique settings. All the "servo" nodes run similar firmware. The Robot DHQ design allows more than one version of the "servo" firmware but use of this provision should be more the exception than the norm. Servo module commands are HERE.
Another example of a module is the routing module. Again, multiple routing modules may exist in a given physical implementation. In the Robot DHQ design all routing nodes are instances of the routing module and all implement the same "methods". The routing methods are implemented as commands and the commands are documented HERE.
Many more modules may be suggested and incorporated in the Robot DHQ design. Here is a list of some possible future modules.
- Analysis module (to repetitively analyze multiple factors)
- Bounds module (to monitor and act on limits and bounds)
- Categorization module (to analyze combinations of factors into a class or category)
- Correlation module (to compare ordered sets of factors and characterize them for subsequent use)
- Notification module (to monitor sets of inputs for situations that call for a notification to be sent)
- Prioritization module (to rank proposed actions by priority or urgency)
- Synthesis module (to compare data from other modules to create a proposed action)
- etc.
Suggestions for additions and changes to this list are invited.