@DougJoseph Thank you for the design. I’ve printed a pair of enclosures and was plodding along slowly planning to build them up. I had snagged two of the M5Dials from the DigiKey link I had posted above.
I’ve decided to get the pair ready to take to RMRRF as was being discussed in a thread shown below.
A question- this pendant enclosure is awesome, but would be even more so if instead of a cable clamp there was a keystone opening so that a standard keystone ethernet jack could be used as the basis of the wiring. Any chance of a collaboration to make that happen?
A further side question- did you ever find a project to lay out a simple PCB? A carrier that had provisions to complete a turnkey pendant would be pretty simple- and pretty useful.
This is definitely doable, and I’d be happy to help. All I would need is clear specs / shape / dimensions of the “jack” thing needing accomodated!
No ,not yet.
Yes, it’s a great idea. However, Mitch from the FluidNC / FluidDial dev team said on the dev Discord channel that he had already created something, and even indicated a willingness to share one with me, as he had several prototypes ordered. I’d hate to horn in on that now that he’s already tackling it.
There’s a “negative” shape here: (I haven’t tried that- but I would print and test fit an enclosure right away if one exists)
Note there’s some discussion of how to use the shape in the makes section on printables.
April 7, 2024 — added a new version of the base that has a keystone jack socket for use of a standard keystone ethernet jack for wiring connection to the pendant, as proposed by V1E forum member @MakerJim in this thread, and for which I used some geometry from this listing by @frfrh_161863.
and thank you again for your support. In order to get my problem with the UART connection under control, I connected a USB/serial converter (3.3V) directly to the FluidNC and M5Dial and looked at the data with HyperTerm.
This is how I noticed that the M5 dial connectors that I got for ports A & B had no contact on the pins. Stupid mistake if you rely on the plugs…
But HUHU the connection works and FluidNC reacts.
BUT unfortunately the touchscreen doesn’t respond for me
Do you have a few helpful ideas about this?
Maybe you could try to test the touchscreen with a factory reset and using the built-in power-on interface from the factory just as a process of elimination to see if you have a bad dial versus a connection problem
Sometimes I’m so silly… went to test fit the lid, then realized half the clamp is on the lid in the original, then realized you’d already uploaded a no-clamp version of the top lid. So that’s printing now, but I expect it’ll work out great.
Yes, and you could 3D print the “stand offs” to be like “spacers” and you would only need the wood to be 1.7 mm or so. You could even “shave” a piece of wood down to “thick veneer” thickness using either a table saw or band saw, and then just 2D cut the profile. It would not even need to be 2.5D.
Thanks,
I just found a program to reset to delivery status directly on the manufacturer’s website.
Works without problems. This is how my touchscreen works. I’ll re-install the M5Stack later and try to figure out the error.
have you updated to latest fluid NC firmware to install latest build with macros on the dial pendan?
or do the latest changes still work on 3.7.12?
The latest fluid firmware is now 3.7.16
Just build pendant and everything was going great - to easy I thought. Sure enough pendant will not connect. Wiring checked many times and all the latest software/firmware loaded. Found your reply about changing to brand rate. This fixed my connect issue. Thanks!
Tested all functions and they work. My only issue is the main screen graphics do not show up but work. Britt you note “Be sure and upload the new graphics to the dial too:” I build and uploaded the latest (as of 4/12/24) from the GitHub. This was the first and only load of software on the M5. I assume the graphics would upload with all the files and since it is the latest should be no issue. Am I missing something?
You have to build and upload the filesystem as well as the code. These were two separate actions for me, and after uploading the filesystem everything works as expected.
