1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
//! A safe, high-level interface to LinuxCNC's HAL (Hardware Abstraction Layer) module.
//!
//! For lower level, unsafe use, see the
//! [`linuxcnc-hal-sys`](https://crates.io/crates/linuxcnc-hal-sys) crate.
//!
//! # Development setup
//!
//! [`bindgen`](https://github.com/rust-lang/rust-bindgen) must be set up correctly. Follow the
//! [requirements section of its docs](https://rust-lang.github.io/rust-bindgen/requirements.html).
//!
//! To run and debug any HAL components, the LinuxCNC simulator can be set up. There's a guide
//! [here](https://wapl.es/cnc/2020/01/25/linuxcnc-simulator-build-linux-mint.html) for Linux Mint
//! (and other Debian derivatives).
//!
//! # Project setup
//!
//! This crate depends on the `linuxcnc-hal-sys` crate which requires the `LINUXCNC_SRC` environment
//! variable to be set to correctly generate the C bindings. The value must be the absolute path to
//! the root of the LinuxCNC source code.
//!
//! **The version of the LinuxCNC sources must match the LinuxCNC version used in the machine
//! control.**
//!
//! ```bash
//! # Clone LinuxCNC source code into linuxcnc/
//! git clone https://github.com/LinuxCNC/linuxcnc.git
//!
//! # Check out a specific version tag. This may also be a commit, but must match the version in use by the machine control.
//! cd linuxcnc && git checkout v2.8.0 && cd ..
//!
//! # Create your component lib
//! cargo new --lib my_comp
//!
//! cd my_comp
//!
//! # Add LinuxCNC HAL bindings as a Cargo dependency with cargo-edit
//! cargo add linuxcnc-hal
//!
//! LINUXCNC_SRC=/path/to/linuxcnc/source/code cargo build
//! ```
//!
//! If LinuxCNC is configured to run in place, `liblinuxcnchal.so.0` may not be found on startup. To
//! fix, try setting the library path with e.g. `export LD_LIBRARY_PATH=~/Repositories/linuxcnc/lib`
//!
//! # Examples
//!
//! ## Create a component with input and output
//!
//! This example creates a component called `"pins"` with a single input (`"input-1"`) and output
//! pin (`"output-1"`). It enters an infinite loop which updates the value of `output-1` every
//! second. LinuxCNC convention dictates that component and pin names should be `dash-cased`.
//!
//! This example can be loaded into LinuxCNC with a `.hal` file that looks similar to this:
//!
//! ```hal
//! loadusr -W /path/to/your/component/target/debug/comp_bin_name
//! net input-1 spindle.0.speed-out pins.input-1
//! net output-1 pins.output-1
//! ```
//!
//! Pins and other resources are registered using the [`Resources`] trait. This example creates a
//! `Pins` struct which holds the two pins. [`HalComponent::new`] handles component creation,
//! resources (pin, signal, etc) initialisation and UNIX signal handler registration.
//!
//! ```rust,no_run
//! use linuxcnc_hal::{
//! error::PinRegisterError,
//! hal_pin::{InputPin, OutputPin},
//! prelude::*,
//! HalComponent, RegisterResources, Resources,
//! };
//! use std::{
//! error::Error,
//! thread,
//! time::{Duration, Instant},
//! };
//!
//! struct Pins {
//! input_1: InputPin<f64>,
//! output_1: OutputPin<f64>,
//! }
//!
//! impl Resources for Pins {
//! type RegisterError = PinRegisterError;
//!
//! fn register_resources(comp: &RegisterResources) -> Result<Self, Self::RegisterError> {
//! Ok(Pins {
//! input_1: comp.register_pin::<InputPin<f64>>("input-1")?,
//! output_1: comp.register_pin::<OutputPin<f64>>("output-1")?,
//! })
//! }
//! }
//!
//! fn main() -> Result<(), Box<dyn Error>> {
//! rtapi_logger::init();
//!
//! // Create a new HAL component called `rust-comp`
//! let comp: HalComponent<Pins> = HalComponent::new("rust-comp")?;
//!
//! // Get a reference to the `Pins` struct
//! let pins = comp.resources();
//!
//! let start = Instant::now();
//!
//! // Main control loop
//! while !comp.should_exit() {
//! let time = start.elapsed().as_secs() as i32;
//!
//! // Set output pin to elapsed seconds since component started
//! pins.output_1.set_value(time.into())?;
//!
//! // Print the current value of the input pin
//! println!("Input: {:?}", pins.input_1.value());
//!
//! // Sleep for 1000ms. This should be a lower time if the component needs to update more
//! // frequently.
//! thread::sleep(Duration::from_millis(1000));
//! }
//!
//! // The custom implementation of `Drop` for `HalComponent` ensures that `hal_exit()` is called
//! // at this point. Registered signal handlers are also deregistered.
//!
//! Ok(())
//! }
//! ```
extern crate log;
use ParameterPermissions;
pub use crateHalComponent;
pub use crateParameter;
use crate::;
/// Resources for a component
/// Component metadata used when registering resources