The practical limit is going to depend on the design of your system. In general, the method of addressing multiples of those sensors is the same as for the VL53L0X. You might look at this thread on our forum and continue the discussion there or post a new topic with more details about your system if you have further questions:
The amount of time the sensor takes to return a distance measurements depends on a number of factors. I recommend looking at the "Range Timing" section starting on page 26 of the VL6180X Datasheet for more information about the time required for ranging and then comparing that to the length of time the target will be in the sensor's field of vision.
The 10k pull-up resistors on each of the signal lines on each channel consume current when the channel is in a logic low state. It is possible to calculate a current from your HV and LV supplies using Ohm's law.
Yes! You can find that software on the "Resources" tab of the Tic's product page, and you can see a really brief example of it in action in our Tic introduction video. We are also working on a longer, more detailed video to help show you how to get started with the Tic, and that should be done early next week (we'll announce it on this blog when it's up).
The DRV8825 driver IC on that board has fixed 30kHz PWM routine to control the current through the coils. That is above the audible range and cannot be changed. If you are having problems with your stepper motor making noise, you might try adjusting the decay mode and current limit in the Tic software. Also, the step rate is often audible, so if you are stepping near the frequency of the noise, that could be creating the issue. If you post more details about your system to our forum like a datasheet for your stepper motor, what kind of power supply you are using, and the settings you are using for your Tic, we can help you troubleshoot more there.
We have some basic example code for doing things like controlling the motors and other onboard peripherals like the buzzer in our A-Star 32U4 Arduino library, which is linked to on the "Resources" tab of the product page for the A-Star 32U4 Robot Controller:
We do not know of any code for using the other sensors in this configuration or a schematic of how they are connected, but you might post on the forum (linked to above) to see if the original poster is interested in making those available.
Sorry, I guess I didn't explain that very well. I want to set up a Sharp distance sensor pointing off to the side of the robot and, when I'm tuning it, I can place objects to the side of the line following course so the sensor can detect them as it passes. That would allow lap times can be more precisely calculated to get a more accurate idea of how changing settings affects the lap time. I still haven't gotten around to doing this yet.
It might be possible, but there are a few things that might limit the practicality of stacking two of this particular shield. If you are using the hardware included with the board, the screw terminals are a little bit too tall to fit underneath another board, so you would probably need another way of making those connections like soldering your motor and power supply leads directly to the board. Also, if you want independent control of the 4 channels, you would need to remap the connections (which we discuss in the user's guide for the board).
Depending on your application, you might be able to limit the current to 500mA using the current feedback feature of the driver, though you should be aware that the feedback is not very precise and might require calibration.
Nathan's line following robot: Suckbot
- 16 April 2024Hello.
Thanks. Unfortunately, I don't remember exactly where I got it. Sorry about that.
-Nathan
Now available: VL53L1X library for Arduino
- 9 April 2019Hi, Rajesh T.
The practical limit is going to depend on the design of your system. In general, the method of addressing multiples of those sensors is the same as for the VL53L0X. You might look at this thread on our forum and continue the discussion there or post a new topic with more details about your system if you have further questions:
https://forum.pololu.com/t/vl53l0x-maximum-sensors-on-i2c-arduino-bus/10845/
-Nathan
New product: VL6180X Time-of-Flight Distance Sensor Carrier
- 14 May 2018Hello, Yuri.
The amount of time the sensor takes to return a distance measurements depends on a number of factors. I recommend looking at the "Range Timing" section starting on page 26 of the VL6180X Datasheet for more information about the time required for ranging and then comparing that to the length of time the target will be in the sensor's field of vision.
-Nathan
New product: Logic Level Shifter, 4-Channel, Bidirectional
- 26 March 2018Hello, Supreeth.
The 10k pull-up resistors on each of the signal lines on each channel consume current when the channel is in a logic low state. It is possible to calculate a current from your HV and LV supplies using Ohm's law.
-Nathan
New product: Tic T500 USB Multi-Interface Stepper Motor Controller
- 16 March 2018Hello, Gilbert.
Yes! You can find that software on the "Resources" tab of the Tic's product page, and you can see a really brief example of it in action in our Tic introduction video. We are also working on a longer, more detailed video to help show you how to get started with the Tic, and that should be done early next week (we'll announce it on this blog when it's up).
-Nathan
Introducing the Tic T825 USB Multi-Interface Stepper Motor Controller
- 1 March 2018Hello, Sarah.
The DRV8825 driver IC on that board has fixed 30kHz PWM routine to control the current through the coils. That is above the audible range and cannot be changed. If you are having problems with your stepper motor making noise, you might try adjusting the decay mode and current limit in the Tic software. Also, the step rate is often audible, so if you are stepping near the frequency of the noise, that could be creating the issue. If you post more details about your system to our forum like a datasheet for your stepper motor, what kind of power supply you are using, and the settings you are using for your Tic, we can help you troubleshoot more there.
-Nathan
How to make a Balboa robot balance, part 4: a balancing algorithm
- 30 January 2018Hello, Stefan.
We posted a response to your questions here on our forum.
Please continue the discussion there if you have further questions.
-Nathan
Custom Mini Sumo robot
- 27 November 2017Hello.
We have some basic example code for doing things like controlling the motors and other onboard peripherals like the buzzer in our A-Star 32U4 Arduino library, which is linked to on the "Resources" tab of the product page for the A-Star 32U4 Robot Controller:
https://www.pololu.com/product/3116/resources
We do not know of any code for using the other sensors in this configuration or a schematic of how they are connected, but you might post on the forum (linked to above) to see if the original poster is interested in making those available.
-Nathan
Nathan's line following robot: Suckbot
- 10 November 2017Hello.
Sorry, I guess I didn't explain that very well. I want to set up a Sharp distance sensor pointing off to the side of the robot and, when I'm tuning it, I can place objects to the side of the line following course so the sensor can detect them as it passes. That would allow lap times can be more precisely calculated to get a more accurate idea of how changing settings affects the lap time. I still haven't gotten around to doing this yet.
-Nathan
New product: Pololu Dual MC33926 Motor Driver for Raspberry Pi
- 28 August 2017Hello, Sid.
It might be possible, but there are a few things that might limit the practicality of stacking two of this particular shield. If you are using the hardware included with the board, the screw terminals are a little bit too tall to fit underneath another board, so you would probably need another way of making those connections like soldering your motor and power supply leads directly to the board. Also, if you want independent control of the 4 channels, you would need to remap the connections (which we discuss in the user's guide for the board).
Depending on your application, you might be able to limit the current to 500mA using the current feedback feature of the driver, though you should be aware that the feedback is not very precise and might require calibration.
-Nathan