Exactly. These videos have been a big help in my classes and I'm still tinkering with my Pi and the Tiny2040 (little cousin to the Pico).

😮😮

Hi Perry, there is a lot of potential in this tiny and low-cost little Pi.

There so cheap and affordable which makes them very worthy too

I think Pi Picos are kind of an addiction!

I've got 7 so far! Plus a couple of Pimoroni Tiny 2040. Along with loads of Arduino Unos, Nanos, Megas and Pro Minis, and a few ESP32s, ESP8266s and Seeeduino Xaios. Buying one microcontroller is the start of a very slippery slope!!!!

Chris only has 3/4 of a million subs, his channel is basically the best kept secret on the interwebs.

Ooooh. I like that idea!!

I wondered if you did some rounding on the pot results say nearest 10 would take out the dithering but without loosing any accuracy

simple_smoothed_value = simple_smoothed_value * 0.9 + lastest_value * 0.1

I would try to divide it by 100 and truncate the result.

@@marksterling8286 losing.......loosing...........we know by now how autocorrect sometimes makes our text somewhat inaccurate, so it is worth checking before posting. You may be very experienced in giving commands to computers , so will appreciate accuracy in coding.

You should always place a small (10nF) capacitor on ADC inputs to micros to give something to charge up and dominate the internal sample and hold circuit capacitance. What you get is the result seen here if you don't.

Those PLCs were a bit of a rip off. They were just 8 bit micro controllers with some inputs and outputs and a simplified programming language. Late '80's through the '90's we would do the same thing with a Z80 and some code written in C. The advantage of a PLC was the electrician could program it.

@@wayland7150 - Ladder Logic was cryptic as heck. PLCs were a rip off but well worth it to the companies who needed such a thing.

More to come!

They are doing OK -- and will return! :)

Hi Steve. :)

Like de-bouncing a push button. That can be done either with the capacitor as you mentioned, or in the coding.

A capacitor correcting the problem points to jittering voltage from the potentiometer, not the ADC.

@@dang48 If the capacitor solves the problem then it's less work for the software.

@@onjofilms It's the nature of the real world, there is noise. The only reason there is not noise inside computers is the efforts taken to design it out or at least design out the effects.

@@wayland7150 That is true. The reason for debouncing in the coding would be to save physical space on your circuit board. Both methods have their advantages and disadvantages.

Thanks for your support, most appreciated.

Thanks, and welcome aboard!

Sounds like you have some experimenting to do! :) Good luck with it.

@@ExplainingComputers Definitely! Thanks!

:)

Many thanks!

:)

ExplainingComputers is Concise and Clear as always! :) The servo jitter can indeed be reduced as Roger Froud pointed out using a capacitor to dampen the noise. Probably the best way. Yet, while the best software is hardware, I would still add a software value damper to the while loop which averages out the values as a fail safe.

@@TriAngles3D Exactly. My professor was teaching us these concepts but with push buttons. Called 'Debouncing', he showed us both the hardware and software way. He insisted that we use the software way though. :-)

It would be a very short playlist unless you started getting into more complex servos like ones with higher accuracy, force feedback etc.

I have a project on the go to connect multiple Picos using the RFM69HCW radios (not the LoRa variants). The libraries for these radios are only available in C (they be available in CircuitPython but I believe CP doesn't support interupts, which my project needs), so I went down the C++ route a couple of months ago using the Pico SDK and Visual Studio Code. It was an absolute nightmare to setup and get working on W10 (KZfaq was my friend here), and is pretty cumbersome to use. In the last month or so RP2040 support became available on the Arduino IDE which I have briefly used just to test that it works. If the radio libraries were available to Micro Python I'd use that in a heartbeat. So much easier to use, and TBH I wouldn't miss the greater (much greater) efficiency of C++ on this project.

@@skf957 The advantage of C is speed of execution. C is *compiled* whereas Python is *interpreted.

@@lesliedeana5142 Yes, thanks. And I like what I’ve seen of C++. Its relative inaccessibility (on the Pico at least) appeals to my inner geek/snob, it seems to be extremely feature-rich, and as you say, is fast in execution. But, and I am no expert here, Python and Micro Python, far from being the modern day equivalent of BASIC (and that wasn’t THAT bad), are also feature-rich and really nice languages to use.

Thanks 👍

Thanks for watching! :)

Thanks for this. I have a video on using servos with a standard Pi here: kzfaq.info/get/bejne/rq50h5d03NC5gXk.html I also did two videos on a weather station using a Pi earlier this year, first one here: kzfaq.info/get/bejne/ec6Bo6djzNmnYmQ.html -- and second (where I build an anemometer) here: kzfaq.info/get/bejne/Z7KAeLOLlZiRpGw.html But there will be more projects . . .

So for some that has used both, what's the speed difference?

Bad typing - "some" was supposed to be "someone".