-
Notifications
You must be signed in to change notification settings - Fork 66
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
Library doesn't work with new Seead Ultrasonic Distance Ranger V2 #69
Comments
Ths is the Library the unit uses: https://github.com/Seeed-Studio/Seeed_Arduino_UltrasonicRanger |
Hello, @benpaddlejones! Thank you very much for sharing this issue. Could you give me a link to the sensor you are using? If that's what I'm thinking, unfortunately I don't have any here with me to test. However, Seed itself provides a library for ultrasound that uses a strategy to measure distance very similar to this one. Thank you very much! |
Hi Erick Yes it works perfectly with the Seead library (same link you shared) and sample code provided in the documentation. Happy to help with any testing my end. Be great if you can solve as I would rather just use one library for both our schools Seead Grove ultrasonic senors and generic 4 pin ultrasonic senors. Ben |
Great, Ben! This week I'm going to see if I can get one of these sensors in the lab where I work, but I already bought one of these and now I'm going to wait for it to arrive to do the necessary tests and adjustments (it may take a while due to the delivery time here to Brazil). As soon as I update it, I'll let you know here. Thanks! |
@benpaddlejones, would you be able to test version 2.1.0 of the library? I think the addition of a |
Hi Erick |
Hi Erick |
Describe the bug
Code loads, Serial monitor prints line statements but measurement value is always 0
Code to reproduce
Wiring
Connected to a Seead Senor Shield
Expected behavior
As Sensor is moved distance value should show distance to object
Error message
none
Context (please complete the following information):
The text was updated successfully, but these errors were encountered: