Brainstorming user interface suggestions

I made a list of things that have come to mind. I’m an outsider to CNC stuff so it may be a newbie perspective. Also there is overlap here between web controls and the backend code, but I’ll put all my thoughts here.

Zero belts independently:

Edit: This is nonsense since the bolts would be in the way anyway. Leaving it here anyway.

Can we have an option to zero each belt one at a time? My biggest problem right now if anything happens (breaker trip), or I get confused and screw something up and have to re-zero I have to undo my bolts then bolt everything again. Yes it would be slower to do it this way, but maybe others have had this problem and it could help them. Of course ideally we just retract them all at once which is why I’ll be modifying my anchor bolts.

I’m on a horizontal platform. This method may be problematic a vertical platform, but I think it could work on a horizontal one.

Alarm / Idle change:
The button saying Alarm is confusing. Perhaps Engaged / Disengaged, or Armed / Disarmed would be better. Really not sure myself. If that language is perhaps standard in other CNC systems maybe a some kind of hover text could add context for new users.

Control Lock Overrides:
I would love to have a button that overrides not allowing you to control the belts and stuff like that. I got a jam on my belt and the only option was to zero belts. Not ideal
Something to control individual belts yourself manually. I don’t know, just a thought.

Pause and Stop:
Not sure what is limiting this as an option. I know we will always need an E-Stop, but I have multiple times wished I could pause or stopped my calibration or other tasks and been unable to without a hard stop. I realize that it’s going to complete whichever step in the g-code first.

Warnings before start:
For Calibration or running a job can users enable a caution confirmation message allowing user to abort the action. This way you don’t accidentally hit your touch screen or whatever.
I had someone helping me who thought my commenting about calibration meant we should hit the calibration button. Had to E-Stop then of course undo all the @#$% bolts to zero them again.

Button colors:
I think sometimes the gray buttons give the idea that they are disabled when they aren’t. Honestly I’ve been having a hard time when I’m setting things up and get confused between things and perhaps I am wrong about this. Things have been starting to make more sense.

Checklist Toggle Buttons:
I was thinking of making myself a physical device for Maslow Launch Controls with actual switches. It may be better in the user interface. Check off each step before starting your job. Bit inserted, Remove Button Pusher , Home z Axis, Set x/y home, Turn on router, Turn on dust control…

Just some toggle buttons that otherwise don’t do anything. Just there to help you keep track of doing all the steps.

Figured I’d share these thoughts as I procrastinate un-jamming my belt and hacking off the ends of my bolts.

Handy_Owl wrote:

I made a list of things that have come to mind. I’m an outsider to CNC stuff so it may be a newbie perspective. Also there is overlap here between web controls and the backend code, but I’ll put all my thoughts here.

Zero belts independently:
Can we have an option to zero each belt one at a time? My biggest problem right now if anything happens (breaker trip), or I get confused and screw something up and have to re-zero I have to undo my bolts then bolt everything again. Yes it would be slower to do it this way, but maybe others have had this problem and it could help them. Of course ideally we just retract them all at once which is why I’ll be modifying my anchor bolts.

I agree

I’m on a horizontal platform. This method may be problematic a vertical platform, but I think it could work on a horizontal one.

even on a vertical machine, you could do this easily with the lower belts, and
if you have a way to hold the machine up, you could do it with the upper belts.

Alarm / Idle change:
The button saying Alarm is confusing. Perhaps Engaged / Disengaged, or Armed / Disarmed would be better. Really not sure myself. If that language is perhaps standard in other CNC systems maybe a some kind of hover text could add context for new users.

Alarm means that something went wrong and the machine doesn’t know that it’s
safe to move. I agree with the mouseover text to explain this.

Control Lock Overrides:

I would love to have a button that overrides not allowing you to control the
belts and stuff like that. I got a jam on my belt and the only option was to
zero belts. Not ideal
Something to control individual belts yourself manually. I don’t know, just a
thought.

the code to support this is in the firmware, I think it would be gret to have an
‘advanced’ tab/popup that exposed these things to the user

Pause and Stop:

Not sure what is limiting this as an option.

the attempt to implement it didn’t work, and Bar has been tied up in
troubleshooting and then the 4.1 upgrades as a result of the findings from the
troubleshooting.

This needs someone to dig into the fluidnc code and how the maslow interfaces
with it to figure out what’s going wrong.

Warnings before start:

For Calibration or running a job can users enable a caution confirmation
message allowing user to abort the action. This way you don’t accidentally hit
your touch screen or whatever.

as a config option. for some people it will just be an annoyance of an extra
step.

Button colors:

I think sometimes the gray buttons give the idea that they are disabled when
they aren’t. Honestly I’ve been having a hard time when I’m setting things up
and get confused between things and perhaps I am wrong about this. Things have
been starting to make more sense.

good point

Checklist Toggle Buttons:

I was thinking of making myself a physical device for Maslow Launch Controls
with actual switches. It may be better in the user interface. Check off each
step before starting your job. Bit inserted, Remove Button Pusher , Home z
Axis, Set x/y home, Turn on router, Turn on dust control…

as an optional feature, this is a good idea, I would do it as a popup table that
you work your way down (or go back up) with a checkbox to say you have done that
step that prevents you from doing the next step

(at power on) belt length unknown, disconnect belts → retract belts all the way
→ extend belts → connect belts → apply tension

Z position unknown or Z skewed, remove bit → lower router all the way until
both motors bottom out → set z Stop → raise router → insert bit → lower to
touch → set z Zero

not calibrated (once belt lengths are known), remove bit → lower router all the
way → set calibration size → calibrate

David Lang

I have seen this as a pilots aid when doing prechecks for takeoff etc. I series of switches which have to be activated in order to get a green go light. Good idea.

1 Like

After some thought you really can’t do a retraction with the dang anchors in the way. Unless you hold your maslow upside down or something crazy like that. Thankfully I’ve modified my anchors already so I’m not going to have to unscrew them each time.

Also good too hear that Bar is aware of the pause / stop. That’ll be nice when it can get sorted out.

1 Like

On the user interface, a few ideas:

Change the access point and password descriptions to something that make -sense-. They are totally cryptic right now!

Add some checks before the “calibrate” button actually works. Right now if you don’t do the whole dance (retract, extend, tension) you are going to get into stuck Maslow mode… and no way to stop things.

Would it be possible/valuable to put a little box at the top of the button panel for setup that shows the current state of the machine? IE: retract, extend, tension, release, etc.

A button that gives you a “stop whatever the heck you are doing ESP32” function feels useful. It may just be my newbieness talking :wink:

Rod wrote:

Change the access point and password descriptions to something that make -sense-. They are totally cryptic right now!

what do you suggest?

Add some checks before the “calibrate” button actually works. Right now if you don’t do the whole dance (retract, extend, tension) you are going to get into stuck Maslow mode… and no way to stop things.

Would it be possible/valuable to put a little box at the top of the button panel for setup that shows the current state of the machine? IE: retract, extend, tension, release, etc.

very good idea

A button that gives you a “stop whatever the heck you are doing ESP32” function feels useful. It may just be my newbieness talking :wink:

it’s being worked on

David Lang

I will need to take a bunch of screen shots to support this…
Here’s the one I actually have with annotation! This is SUPER confusing and has terrible english.
BTW, a different bar or double bar where I added the blue line would help clarify that the upper stuff and lower stuff are -different- things.

1 Like

While getting up and running yesterday, I took a bunch of screenshots. It really looks like the wifi menu is the most confusing one!

1 Like

One other item: could we make “fitness” something more meaningful? Maybe 100% = perfect? I still can’t decide if low is good or high is good :wink:

1 Like

Higher is better :grinning_face:

These are great suggestions! I 100% agree that the wifi menu is confusing, I still consult the user guide every time I need to set it up, and it could absolutely be simpler.

Ultimately I think that we need to push the FluidNC UI stuff further back and expose just the settings that folks actually want to see.

Rod wrote:

One other item: could we make “fitness” something more meaningful? Maybe
100% = perfect? I still can’t decide if low is good or high is good :wink:

higher is better

the problem is that we don’t know what ‘perfect’ is.

currently we take what we think is the anchor locations, then look at all the
points measured during calibration, and find the average error between what the
belt lengths for that point were measured at vs what would work with the
calculated anchor points.

then fitness = 1/error so a higher score is better.

David Lang