Learn how to make a Tachometer for your machine

Ғылым және технология

In this video, Chris explains how he made a tachometer for his precision drill press. The spindle on this machine runs at 11,000 and this tachometer can easily handle that speed. Utilizing a 3D printer, the housing can be made quickly and easily. The tachometer is run on a PICO, and uses the Waveshare 1.28" round display and an RPR-220 photoreflective sensor.
There are several other associated videos with the project:
Video detailing the RPR-220 photo sensor
• How to Use the RPR-220...
Video on getting started with the Waveshare Round 1.28" LCD Module
• Getting Started with t...
Video on creating the '7 segment' font for the Waveshare Round 1.28" LCD Module
• Creating a 7 Segment F...
The schematics, source code, and 3D files can be downloaded from the companion website
www.MakingStuffWithChrisDeHut.com

Пікірлер: 6

  • @bobweiram6321
    @bobweiram63218 ай бұрын

    A mix of woodworking, machining and electronics. This is my kinda channel. I made a tach using parts from a broken optical mouse. It was a bit overkill though.

  • @MakingStuffwithChrisDeHut

    @MakingStuffwithChrisDeHut

    8 ай бұрын

    Hi Bob, An optical mouse, that should have been fun. How fast of speed were you monitoring? Cheers! Chris

  • @donepearce
    @donepearce8 ай бұрын

    I like this. A lot. The display looks really good - but obviously I'm going to chime in with some ideas. First would be to use the 10msec wait to do multiple reads and average them - that might stabilise the flickery pointer a bit. Next is a big one - use this reader to feed back to the controller so you can set the speed accurately. Good luck with coding that!

  • @MakingStuffwithChrisDeHut

    @MakingStuffwithChrisDeHut

    8 ай бұрын

    Hi Don, Thanks for the feedback. I tried the averaging as you suggested and it provided little change. As for the controller, it is unlikely to work with feedback. It is a VERY inexpensive driver and truthfully I am surprised it works! Cheers! Chris

  • @jyvben1520
    @jyvben15208 ай бұрын

    18:32 line 50 "Cycle_time = Temp_ST - ST", could be a problem, see time.ticks_diff() which would always give a correct/expected answer. was thinking why RPM and not RPS, tradition ? 213 RPS would be easier to read than 12780 RPM, personal preference i guess.

  • @MakingStuffwithChrisDeHut

    @MakingStuffwithChrisDeHut

    8 ай бұрын

    Hi Ben, RPS??? Seriously? I am guessing you perhaps work with a lot of very high speed things? In the industrial work of machine tools and cars and motor cycles it is always RPM. That isn't just a USA thing either, machine tools from all over the world use RPM. As for, time.ticks_diff(), I recall that not providing any change in accuracy for this project. I have used it on a couple other projects where the device being monitored was more stable and recall seeing benefits there though. Perhaps I should have utilized even with this machine as it would have been better for others using this on more precise spindle systems. Hmmm, I have to watch out for that more, thanks! Chris

Келесі