Skip to content
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

Update VL53 driver for production OW memory content #202

Closed
ataffanel opened this issue Feb 23, 2017 · 2 comments
Closed

Update VL53 driver for production OW memory content #202

ataffanel opened this issue Feb 23, 2017 · 2 comments
Milestone

Comments

@ataffanel
Copy link
Member

The final production OW memory content has been decided for the VL53 board, now called Z-Ranger: https://wiki.bitcraze.io/projects:crazyflie2:expansionboards:index#deck_info. The driver needs to be updated accordingly.

@stephanbro You are using the VL53 driver for ranging in another direction. What about setting the memory VID/PID to 0xBC:0x09 but with a different name (called ID in the wiki). This way the driver will be initialized, test what board is attached, and can take decision as if the values needs to be pushed in the EKF or not (for example).

@stephanbro
Copy link
Contributor

Since the application I'm using the VL53 for has a fairly custom deck different from the Z-Ranger you guys are working on, I don't have any issues manually setting the VID/PID on my board now that the ranging application has varied pretty decently. Thanks for the consideration though!

Also unless any objects, I don't have any issue with you guys modifying the code to make the Z-Ranger the normal operation of that deck (instead of forward ranging).

@ataffanel
Copy link
Member Author

Ok, we keep it as it is then. Thanks.

ataffanel added a commit that referenced this issue Mar 3, 2017
@ataffanel ataffanel added this to the Next version milestone Apr 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants