devducks/asi-rs

ZWO ASI drivers written in Rust

asi-rs's Issues

refactor exposure cycle

An exposure cycle is usually following this flow:

1. a client request the camera to expose for X seconds
2. the driver call into the library function to do the exposure
3. when done, the client gets the BLOB with the exposure data

right now, to have a semi-functional driver that can be tested the driver converts binary data into FITS and dumps the picture to the disk.

The exposure cycle should be refactored such that:

1. clients request an exposure
2. the driver prepare the properties to signal an exposure is ongoing
3. when the exposure is done the driver should dump the exposure data into a buffer
4. the client gets the raw data and does whatever it wants with it

open questions about this API remain:

• what is the best way to notify the client the exposure is ready to be downloaded? Callback into the client? Client polling a driver property until it is ready?
• should the buffer be dynamically allocated to store more exposures or should the driver block until the latest exposure is downloaded?

Can't compile

If I git clone the repo ant then cargo build it always fails. I get giant list of C errors of missing functions and at the end

= help: some 'extern' functions couldn't be found; some native libraries may need to be installed or have their path specified = note: use the '-l' flag to specify native libraries to link = note: use the 'cargo:rustc-link-lib' directive to specify the native libraries to link with Cargo (see https://doc.rust-lang.org/cargo/reference/build-scripts.html#cargorustc-link-libkindname)

document OS dependencies

libusb
cmake
libclang