controlling lots of servos with a Raspberry Pi Pico

[@TheEmbeddedHobbyist]

Nice to see an example to show there is life outside libraries, this helps the beginner's understanding of how the hardware actually works. This could lead to them thinking I could increase the pwm frequency add an RC low pass filter and now I've got an analogue output. Nice video

[@fredflintstone1]

Meow!!!!!!!!!!!!!!!!!!!!!!

[@andymouse]

@@fredflintstone1 Squeak !

[@andymouse]

good idea !

[@fredflintstone1]

@@andymouse Cheese!!!!!!!!!!!!!!!!!!!!!!!

[@RandomBitzzz]

Great example of how to do this. Nuggets like this are great as starting points for bigger, more complex projects.

[@jimlynch9390]

Thank you. I really enjoy watching these types of videos.

[@retireeelectronics2649]

That was good for a chuckle, 15 servos and a pico, very nice.

[@oracid]

Thank you very much !

[@Videogame9559]

Thanks for this your only one explained you don't need servo driver board it's usually one servo running. I've got skulls jaw moving up and down on poreject skull.

[@andymouse]

Nice and to the point !

[@fredflintstone1]

What a fun video and informative great🙂

[@shroomy7199]

I like this

[@Bob_Burton]

08:20 I was surprised to see a value of 9000 microseconds used as the top value in the for loop because I am under the impression that the top value for a servo should be 2000 microseconds

[@conorstewart2214]

That value is not microseconds, it is the number that the hardware pwm module counts to. The hardware PWM here is using a 16 bit counter and has a frequency of 50 Hz that means that 50 times per second that counter counts up to 65535 (there are 65535 counts per 20 ms), so then you can divide the period of 50 Hz (1/50) with the value it counts to (65535), which gives you that every count equals 305 ns, now if you multiply that by 9000 counts you get 2747 microseconds. It could be done better to get you exactly what you need like 2500 microseconds would be 8192 counts, here they probably just chose a round value like 9000 and went out of range of the servos, which isnt recommended.

[@conorstewart2214]

Also different servos sometimes use different min and max values, sometimes they can get better resolution if they go from like 0.5 ms to 2.5 ms or something like that, rather than the standard range of 1 ms to 2 ms, by going to 0.5 - 2.5 ms they get double the resolution.

[@kyleallred984]

With the holidays approaching any projects planned for decor?

[@pileofstuff]

Wait... People think I actually plan ahead? 😉

[@kyleallred984]

@@pileofstuff well, more specifically has the wife asked for anything to be made😁

[@jyvben1520]

great demo, adding the power board was essential, the base for an 8 legged (16 feet) insect or a snake ... could be remote controlled when used with a Pi Pico Wireless ... 5 volts wasn't needed for the pico, does the servo need it ? a 1650 + stepdown convertor to 3.3V is probably enough to make it mobile.

[@wrxs1781]

If you delve into the realm of new model airplane controls running on 2.4 ghz, you can remote control up to a mile away, line of sight.

[@Videogame9559]

That great news I only need 3 servo to work and. Could not get PAC9685 servo control board to work. I'll give it a go thanks great video

[@dtec30]

hmm wonder if you could make a servo analogue clock

[@pileofstuff]

As long as you spread the numbers around 180 degrees on the display (or add some gearing) it should be possible. Though the hands wound need to "rewind" to the start each day.

[@frankowalker4662]

Cool. Nice rats nest. :)

[@aqib2000]

This is a good beginning but I was hoping for 2 simultaneously operation not just one after the other

[@pileofstuff]

That's not much different. Just send the same value to multiple servos at the same time.

[@aqib2000]

@@pileofstuff that’s not what I meant

[@kndskjnjdsksns]

is it ok with 360 degrees?

[@pileofstuff]

I would assume so - I don't have any 360 degree servos to experiment with.

[@brettb.345]

My brain was in fact screaming “no, use an array with loops.” 😊

[@pileofstuff]

I know, I know... ;-)

[@tinygriffy]

a robot playing some sort of string instrument perhaps ?

[@pileofstuff]

Or waving 16 surrender flags after trying for too long...

[@user.A9]

Micropython or circuitpython?

[@pileofstuff]

In this case, I was using micropython.

[@nidzdotnet76]

or just get a PCA9685 that has header pins for the servo plugs and use that to plug all the servos in and then interface it with the PICO.

[@pileofstuff]

There's plenty of valid ways to get to the same place.

[@ArjanvanVught]

Although I am not in favor of the Pico, I do still like the video :-)

[@ericblenner-hassett3945]

defining individually or a loop setting an array is ineficient compared to HEX data.. and way beyond most ' beginner ' videos and totally take away from 16 servos on one Pi PICO being adressed individually.

[@whodatdere1]

1337 Great time

[@jyvben1520]

13:37 is the end of the video

[@whodatdere1]

@@jyvben1520 Look up 1337 meaning. You'll understand what I mean :)

[@ZenHulk]

Why don't you all stop believing that a 9gram servo is a servo its nothing can do nothing works for nothing, most of them don't work out of the box.... LETS PUT 10 25kg or 40kg servos on the raspberry pi and watch it explode. i am so tired of 9gram servos being the test for everyone who thinks they're making a good video.

[@pileofstuff]

The 9 gram ones are really cheap, which makes them approachable for beginners. The better ones can become prohibitively expensive if your project needs more than couple. Regardless, the control method is the same, so this demonstration is still valid no matter which servomotors you prefer to use.