Sorry for opening this can 'o worms…
Beats me. It’s not like they were out of numbers or anything. Probably though it was parallel development, where GRBL went one way for things they wanted (workspace coordinates) and Marlin didn’t think they needed that (3D printers don’t typically want/need an offset from the machine coordinates.) So they used the code for something they could use…
Agree, 
but… personally like my phone’s 5"-6" LCD, and, Chrome/Edge/Opera Web Browser JavaScript can send/recv commands via COM/USB connected device.
Never tried USB connecting Android Mobile to ESP32 and seeing what happens…
If that works then ESP32 USB cable wired to a cell phone in bad wifi situation could be neat back up. Could be useful for places like RMRRF 2024.
Web Joystick UI’s functionality/usability could be improved, maybe that’d be enough to reduce the friction that pushes people to invest in dedicated pendant for functional reasons. That said, Pendant is on my to-do list, but not because I need one.
I just now verified that the offset I set in the video (x=20mm, y=30mm) is retained after powering down the Jackpot board, and then powering up again, and remains in place even after homing after a reboot. Homing to machine 0,0 gets reflected as -20, -30. I like this.
Also, I am currently setting up my probing values and testing that process.
That also means you now need to make sure to Zero Everytime unless you are using the exact same starting place. If you forget to Zero it will move.
The old way, home is always home. This way means your last zero is now home. Be careful.
It has benefits, but is also now adds a step.
Is it different? After I run a job with G92 in the start, if I say go to (0,0), isn’t it going to go back to whatever arbitrary place I started it?
Couple more tidbits:
The setting of zero for Z on the dial pendant seems to be remembered past a reboot of the Jackpot as well.
However, the manual adjustment of probe values, does not survive a reboot. I’m on the hunt for where those values can be changed in a lasting way.
Quite so. And I understand fully here, both the potential risk and benefit.
G10…If you use my code you are using G92 to do the probe offset.
I mean after a reboot.
So I just checked my gcode snippets for FluidNC-based probing, which were based on older snippets used for Marlin-based probing, and the snippets are all G92 actions for setting the new Z position to the thickness of the touchplate.
My config.yaml file has only one mention of “probe” and no mentions of “probing”:
probe:
pin: gpio.36:low
toolsetter_pin: NO_PIN
check_mode_start: true
I just now located the dial pendant’s probing values, hardcoded in the source file named “main.cpp” —
Ideally, these should not only be “savable” in the pendant’s live operating system, but also defaulted to values that are editable outside of uncompiled firmware, since any “saved” changes don’t survive a reboot.
I need to ask the Fluid NC team if… Are there values that could be inputted into config.yaml or some similar config file that can be read by the pendant?
I would give them more time. They are both working on this faster than anything I have seen. They do not seem to be ready yet. I would save it until you see them stop messing with it for a couple of days.
Lower part of case (case bottom) is 7mm deeper than the original, to give more room for getting power to the M5 Stack dial. Also the screw wells on the bottom of the lower case are slightly larger, as I found they weren’t quite large enough on the original. Upper part of case (case top) is altered to allow printed logo medallions to be inserted/glued in. The printed logo medallions are included. Both the original case parts (top and bottom) are included as well, for mere convenience, and the graphics for printing a paper graphic top to glue onto the original lid is also included. I’m also throwing in Fusion 360 solid bodies of the original case bottom, and the modified case top, as well as SketchUp file (remixed mesh) of the case bottom with the added depth.
NOTE: the pendant is still under development, so unless you want to be on the bleeding edge, consider waiting a bit before diving in.
See my full build log of this, on the V1 Engineering Forum here: Fluid Dial (Fluid NC dial pendant by Bart Dring, using M5 Stack's M5 Dial)
A huge “shout out” and thank you to Bart Dring, Mitch Bradley, and Michael Melancon of the Fluid NC dev team, and also to Ryan Zeller, @vicious1 over at V1 Engineering Inc, and all the helpful crew at the V1E forum! If you benefit from their amazing work, consider joining me in donating to help them continue their work.
The project’s wiki is at: M5Dial Pendant | Wiki.js
The original case (and firmware and other resources) can be accessed in the project’s Github repo, at: https://github.com/bdring/PendantsForFluidNC/tree/Files/M5Dial_Pendant
Watch these videos to see the CNC pendant in action:
What’s changed in my remix?
What’s available in this listing?
The original is released under the GNU GENERAL PUBLIC LICENSE, and accordingly, so is this listing.
My PayPal tip jar: https://paypal.me/design8studio
Various LowRider 3 CNC remixes:
View all my models and remixes on Printables:
*Product links may be affiliate links, which add nothing to your price, but may benefit me by a small percent.
I’d really love to build it. Would be great for a machine at school.
I just wanted to chime in a thank everyone that contributed to this thread. I am adding a removable fence to my spoil board, which I did want to set up with a coordinate system. I wish there was a graceful way to handle this in Estlcam 11 (or12?). I’m absolutely sure I’ll screw up the preamble text and send it to the wrong coordinate system semi-regularly. I guess I’ll have some commented lines that I’ll need to switch based on my current project.
I expect that fenced projects will far exceed the number of times I remove it and cut the full capabilities of the machine (since I don’t have a full sheet.). I also built a drop table in to one end, for fixtures and whatnot. I suppose that might be another coordinate system.
Currently, I just use a macro to home and move to the correct location, then reset 0,0. But now I’m realizing I’m doing it wrong.
Anyway - I also appreciate all the work on the pendant. In my small garage shop, wall space is at a premium. So I put the machine with the short side on a wall, “sticking out” into the center of the space. However, the computer is mounted on the front of an adjacent shelf unit (because I didn’t want to take additional space for another stand.) This means I move from the front of the machine to the computer about 4-5 times to start a job. It’s particularly noticeable when I’m trying to line something up precisely. I’m really just looking for the ability to jog a bit while I’m watching closely, and resume after the programmed holds without “getting my steps in” moving back and forth. I can do it from my phone, but weirdly, the WebUI on the phone doesn’t click with my brain as well (and the touch targets seem small for my fat fingers.)
I’m up to experiment with the dial pendant, if it’s not for me, I’ll figure out something else to do with it. But it strikes me that Ryan must get a lot of requests to support machines despite “community mods.” I think these mods are a great part of the community, but would never expect Ryan to support them. (I super appreciate that he is so generous with his information.) I wonder if there’s a way to classify community mods (with some level of development and adoption) with a disclaimer that any problems with modded machines must be repeatable with a stock configuration before contacting support?
Try zooming in. I use mine in two modes. Zoomed in for positioning, then zoomed out for monitoring. I like the pendant, I will not be using it other than for testing but I know some will prefer being tethered again. The cost is also the same as a tablet so I think the money is better spent that way if it came down to it. In the end more options are great!
Well currently I just refer everyone to the forums. I support everything I can but give preferential support to stock machines that are bought from me, even though I rarely ask to find out if that is the case.
@vicious1 Here’s a handy little thing while you’re learning about all of these workspaces…
Interesting, 28, 30 and 92 are listed. Hmmm.
Either Bart or one of the other FluidNC devs mentioned to me in the Discord that G92, in and of itself, would not / should not prevent the soft limits and hard limits from working. The implication was that was not their reason for discouraging use of 392, and they still encouraged avoiding use of it, unless it is well understood.
I’m still delving into why Bart Dring and FluidNC wiki, etc, discourage use of G92. See more on this in my “Getting started with Jackpot on LR3” thread.
