A Teensy -> Python Interface Manualmatic MPG/pendant

smc.collins wrote:

I would be interested in casting these cases for this pendant design, in fiber reinforced epoxy resin, stuff is strong like bull, could make buttons in silicone rubber etc, are the CAD files around ?
 

 
Hi Sean - I like the idea but the case is specifically designed for 3D printing so would require significant modification for casting (drafting, skrinkage, tolerances etc). I'm not planning to release the current CAD files as they're extremely 'fragile' - as in they're created using a weekly release of FreeCAD from a while back and don't render/play nicely in other versions. STLs are available here: github.com/Stutchbury/Manualmatic-Pendan...n/Hardware/case/v1.1
My focus (which, for reasons, has slipped a little lately) is currently on the software side - primarily to make it easier to add functionality. If you know how to code compile time 'plugins' in C++ advice would be appreciated.
For what it's worth my case, printed in PETG, has been well and truly abused (eg stepped on, dropped and generally mistreated) - it appears to be tough in all the right places. There are different filaments ([carbon] fibre reinforced) that would probably make it even more robust.

 

As I had to delve into the python code this week (should now work with v2.9 and v2.10 - thanks TadyTheFish for reporting it and @andypugh for pointing me in the right direction) I thought I'd post a quick video demonstrating the 'manual' bit of the Manualmatic - a facing operation:

www.youtube.com/shorts/LUMRR05cWKM
 

Can I use esp32 s3? Teensy is too expensive

onceloved wrote:

Can I use esp32 s3? Teensy is too expensive
 

My apologies @onceloved, I missed this post. The board is designed around the Teensy 4.1 partial because it has enough GPIO pins (although that could be worked around with a MUX) but primarily because of the optimised encoder library from Paul Stroffregen which pretty much guarantees lossless use of the MPG - you can spin it as fast as humanly possible and it won't lose steps.

If ever I moved to a wireless re-design, it would likely be a choice between the ESP32 and a Pico W, but that is a far off project!

As for cost, the Teensy makes up only a small(ish) part of BOM so this is not a cheap pendant (there may well be cheaper COTS ones out there) but is is the best

Philip

just found this manual matic pendant, but teensy 4.1 is too expensive ower price board, can i use teensy 2.0 this ? lot lot cheapen, and what need dong encoder or other library, ?not understand english good, need change arduino ide encoder library to new and were have ? i come old teensy 2.0 USB pendant all time only errorrs whit encoder.h
no declare scope etc. i not know what this all mean. not need diplay , only encoder and rotary SW change acis and scale. can move XYZ remote controll. were i found code teensy 2.0 can use. this.

masawee wrote:

just found this manual matic pendant, but teensy 4.1 is too expensive ower price board, can i use teensy 2.0 this ? lot lot cheapen, and what need dong encoder or other library, ?not understand english good, need change arduino ide encoder library to new and were have ? i come old teensy 2.0 USB pendant all time only errorrs whit encoder.h
no declare scope etc. i not know what this all mean. not need diplay , only encoder and rotary SW change acis and scale. can move XYZ remote controll. were i found code teensy 2.0 can use. this.
 

Hi - the project is based around the Teensy 4.1 to ensure responsiveness from both inputs and the display. Technically you could use a Teensy 4.0 on the PCB (ir I created a common footprint) but I have not tested this and you would not be able to use the 5 physical buttons below the display.
If you don't need the display, this is probably not the right hardware to base your project off but the Manualmatic Python Component and pendant code is all open source so should help point you in the right direction. A Teensy 2.0 would no doubt be more than enough to run an MPG and an encoder button or two.
The Encoder (`encoder.h`) library is designed/written by PJRC for the Teensy range and is extremely reliable, so not sure why you are getting errors. You could use my InputEvents library (in Arduino IDE  and PlatformoIO library managers) to make it easier to use the base Encoder library.
HTH