lucazulian / gyuvl53l0x

GYUVL53L0X - VL53L0X a Time-of-Flight I2C laser-ranging module

gyuvl53l0x

no_std driver for VL53L0X (Time-of-Flight I2C laser-ranging module)

Basic usage

Include this library as a dependency in your Cargo.toml:

[dependencies.gyuvl53l0x]
version = "<version>"

Use embedded-hal implementation to get I2C handle and then create vl53l0x handle.

Single read:

extern crate gyuvl53l0x;

match gyuvl53l0x::VL53L0X::default(i2c) {
    Ok(mut u) => {
        // set a new device address
        u.set_device_address(0x39).unwrap();
        // set the measurement timing budget in microseconds
        u.set_measurement_timing_budget(20_000).unwrap();
        loop {
            match u.read_range_single_millimeters_blocking() {
                Ok(val) => {
                    println!("{:#?}", val).unwrap();
                }
                _ => {
                    println!("Not ready").unwrap();
                }
            }
        }
    }
    Err(gyuvl53l0x::VL53L0X::Error::BusError(error)) => {
        println!("{:#?}", error).unwrap();
        panic!();
    }
    _ => {
        panic!();
    }
};

Continuos read:

extern crate gyuvl53l0x;

match gyuvl53l0x::VL53L0X::default(i2c) {
    Ok(mut u) => {
        u.start_continuous(20_000).unwrap();
        loop {
            match u.read_range_continuous_millimeters_blocking() {
                Ok(val) => {
                    println!("{:#?}", val).unwrap();
                }
                _ => {
                    println!("Not ready").unwrap();
                }
            }
        }
    }
    Err(gyuvl53l0x::VL53L0X::Error::BusError(error)) => {
        println!("{:#?}", error).unwrap();
        panic!();
    }
    _ => {
        panic!();
    }
};

License

MIT license

gyuvl53l0x's Issues

Address shifting

First, thank you for this awesome crate, which usually works great!

I was only a bit surprised about the address shifting:

gyuvl53l0x/src/lib.rs

Line 75 in 9174435

address: address << 1,

What is the reason for this?
In my case, this was not necessary. Due to the structure of the library, it is also not possible for a user to bypass this, or am I wrong?

If the assumption is true, what do you think about removing the shift and leaving it up to the caller to decide if this is necessary or not?

Add minimum viable implementation as example

Add dependabot

Add github workflows