-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rangefinder Sensor (VL53L1X) not working an Speedybee F7V3 #9188
Comments
@DzikuVx @druckgott fix is not working |
Can be closed, fixed an tested with @maxledfreak |
I've had issues making the VL53L1X (bought on aliexpress) work with INAV (version 5.1.0.) #define USE_RANGEFINDER (your FC might be using BUS_I2C2 if it has one, check where is the magnetometer configured, that's where most likely will the rangefinder work) I also had to check the sensors address (all the aliexpress VL53L0X and VL53L1X sensors seems to have 0x29 address).
Then the sensor, after connecting to 5V,GND,SCL and SDA pins (SDA->SDA, SCL->SCL)* on your FC should work. |
@mxchinist This issue includes 2 PR's. Second one works. That means rangefinder works. Default I2C adress is the correct one. Only matching of rangefinder I2C bus was missing. @mmosca @DzikuVx is it possible that you build a .hex for me with stable 6.0 version + this PR for this board for testing? We tried it like described above, but we noticed a strange behaviour related to the GPS. Maybe we did anything wrong in building SW correct. rangefinder works as expected. We tried same rangefinder sensor on Speedybee F4 Wing and can not notice this strange behaviour. Thanks! |
Current Behavior
Sensor VL53L1X on i2C is not detected. Measurement with logic analyzer shows no request to sensor. To validate this behaviour the following procedure were done:Measurement:
![image](https://private-user-images.githubusercontent.com/35899208/255329998-96dddc26-8a04-42d7-8182-a2904826d735.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk2ODUyOTksIm5iZiI6MTczOTY4NDk5OSwicGF0aCI6Ii8zNTg5OTIwOC8yNTUzMjk5OTgtOTZkZGRjMjYtOGEwNC00MmQ3LTgxODItYTI5MDQ4MjZkNzM1LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE2VDA1NDk1OVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWJjNjg5ZjkzOTAxMmY3MmUyNDFiZDBjMGY4Mjg3MTU0MjEwZjcyZjEzNzQ4ZTZmY2Y3NGEzODdjOTk0ODJhMjUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.X2xM1uHRr-1YxTOIPN7azBj9C08wKd2tTkz_9hn9N2k)
Measurement:
Steps to Reproduce
1.Reboot FC
Expected behavior
Sensor is deteced with address 0x76 (7 bit address)Suggested solution(s)
Maybe mapping to all ragefinder sensors is connected to internal bus like Acc., Baro etc.Additional context
# version
INAV/SPEEDYBEEF7V3 6.0.0 Mar 22 2023 / 11:23:04 (084101a)
GCC-10.2.1 20201103 (release)
The text was updated successfully, but these errors were encountered: