A userspace component begins by creating its pins and parameters, then enters a loop which will periodically drive all the outputs from the inputs. The following component copies the value seen on its input pin (passthrough.in) to its output pin (passthrough.out) approximately once per second.
#!/usr/bin/python
import hal, time
h = hal.component("passthrough")
h.newpin("in", hal.HAL_FLOAT, hal.HAL_IN)
h.newpin("out", hal.HAL_FLOAT, hal.HAL_OUT)
h.ready()
try:
while 1:
time.sleep(1)
h['out'] = h['in']
except KeyboardInterrupt:
raise SystemExit
Copy the above listing into a file named “passthrough”, make it executable (chmod +x), and place it on your $PATH. Then try it out:
$ halrun
halcmd: loadusr passthrough
halcmd: show pin
Component Pins:
Owner Type Dir Value Name
03 float IN 0 passthrough.in
03 float OUT 0 passthrough.out
halcmd: setp passthrough.in 3.14
halcmd: show pin
Component Pins:
Owner Type Dir Value Name
03 float IN 3.14 passthrough.in
03 float OUT 3.14 passthrough.out
If you typed “show pin” quickly, you may see that passthrough.out still had its old value of 0. This is because of the call to 'time.sleep(1)', which makes the assignment to the output pin occur at most once per second. Because this is a userspace component, the actual delay between assignments can be much longer--for instance, if the memory used by the passthrough component is swapped to disk, the assignment could be delayed until that memory is swapped back in.
Thus, userspace components are suitable for user-interactive elements such as control panels (delays in the range of milliseconds are not noticed, and longer delays are acceptable), but not for sending step pulses to a stepper driver board (delays must always be in the range of microseconds, no matter what).
h = hal.component("passthrough")
The component itself is created by a call to the constructor 'hal.component'. The arguments are the HAL component name and (optionally) the prefix used for pin and parameter names. If the prefix is not specified, the component name is used.
h.newpin("in", hal.HAL_FLOAT, hal.HAL_IN)
Then pins are created by calls to methods on the component object. The arguments are: pin name suffix, pin type, and pin direction. For parameters, the arguments are: parameter name suffix, parameter type, and parameter direction.
| Pin and Parameter Types: | HAL_BIT | HAL_FLOAT | HAL_S32 | HAL_U32 |
| Pin Directions: | HAL_IN | HAL_OUT | HAL_IO | |
| Parameter Directions: | HAL_RO | HAL_RW |
The full pin or parameter name is formed by joining the prefix and the suffix with a “.”, so in the example the pin created is called passthrough.in.
h.ready()
Once all the pins and parameters have been created, call the .ready() method.
The prefix can be changed by calling the .setprefix() method. The current prefix can be retrieved by calling the .getprefix() method.
For pins and parameters which are also proper Python identifiers, the value may be accessed or set using the attribute syntax:
h.out = h.in
For all pins, whether or not they are also proper Python identifiers, the value may be accessed or set using the subscript syntax:
h['out'] = h['in']
Periodically, usually in response to a timer, all HAL_OUT pins should be “driven” by assigning them a new value. This should be done whether or not the value is different than the last one assigned. When a pin is connected to a signal, its old output value is not copied into the signal, so the proper value will only appear on the signal once the component assigns a new value.
The above rule does not apply to bidirectional pins. Instead, a bidirectional pin should only be driven by the component when the component wishes to change the value. For instance, in the canonical encoder interface, the encoder component only sets the index-enable pin to FALSE (when an index pulse is seen and the old value is TRUE), but never sets it to TRUE. Repeatedly driving the pin FALSE might cause the other connected component to act as though another index pulse had been seen.
A “halcmd unload” request for the component is delivered as a KeyboardInterrupt exception. When an unload request arrives, the process should either exit in a short time, or call the .exit() method on the component if substantial work (such as reading or writing files) must be done to complete the shutdown process.