WebUI v3 improvements

Software / Firmware
1

I’m in a spot now where I have a little bit of time to finally make some improvements to the WebUI, and feel ok about doing so now that the development on the original project has slowed down.

I detailed a few changes I made over in the other thread FluidNC 3.9.9

  • Restored coloring to the Terminal
  • Added setting for max Terminal messages to keep
  • Improved Terminal performance, especially when at max messages
  • Some rendering efficiency improvements

I’ve also made some changes to the Jog Panel that have been on my list for a while:

Go To Position

Position indicators now have button overlays for “Go To Position”

image
image393×161 3.34 KB

image
image647×228 7.36 KB

Separate Jog settings for Z

This one has been discussed here since WebUI v3 was a thing. I believe @azab2c even made a similar PR to the original repo that was denied.

image
image400×469 10.9 KB

For anyone who wants to test any of these changes, you can download a PRE-RELEASE version at my github

index.html.gz.zip

This will download a zip file, and you’ll need to extract the index.html.gz file from inside to upload to the FLASH

If you have some time to test it, please let me know how it goes.

11 Likes
2

Oh buddy, this is needed so bad when manually jogging.

When this gets implemented I will add some stick on tape measures to my table so I can make some better educated guesses as to the location I want to be. This is slick to get you further faster.

You and Jason have really moved the needle on the webUI. I am really excited about the changes.

9 Likes
3

It’s there already in that latest build link…

Just need some testers :slight_smile:

3 Likes
4

I will try to get out to the shop and test it out this afternoon

2 Likes
5

Nice work @Michael_Melancon !

I ran out of patience for that pull request… Implement optional XY/Z Max Jog distance setting by aaronse · Pull Request #292 · luc-github/ESP3D-WEBUI · GitHub it’s been nice to use personally, sorry I wasn’t able to share broadly. Wider than average button makes it a bit easier to touch.

image
image1920×1032 79.1 KB

Here’s another minor pull request that’s a no brainer quality of life improvement imo Implement really really basic autocorrect by aaronse · Pull Request #287 · luc-github/ESP3D-WEBUI · GitHub

1 Like
6

The jog panel supports configuration adding axes A, B, and C. What step values are those axes using? I assume the XY values?

1 Like
7

Yep, they still use the XY

2 Likes
8

For now, the only thing I’m doing with the extra axes is making sure they are still supported.

I’ve never used a 4+ axis machine, and am not sure if I’ve seen many/any in the forum.

So I’m just going to keep them functioning as they are until some actual users have complaints/suggestions enough that warrant dealing with them :grin:

3 Likes
9

Color is awesome, separate Z jog is awesome. I forgot to check the " go to". I will hit that shortly.

It was very nice to move XY at 500mm and the Z at 10 back and forth quickly. I was seeing if I had clearance under a shelf in the new table home, and I moved it all around. SO AWESOME.

Not sure if you want to look at other things at the moment. If not disregard this.

Screenshot_20251104-123519
Screenshot_20251104-1235191080×2424 246 KB

Screenshot_20251104-123527
Screenshot_20251104-1235271080×2424 245 KB

We have a firmware version with no output, maybe those are just links to use when in STA mode?
At the bottom we do get a FW version with enough info to figure out which it is, name instead of number.

I also agree, I see nothing special on the information tab that is not on the status module.

2 Likes
10

Goto didn’t work.

Screenshot_20251104-151030
Screenshot_20251104-1510301080×2424 219 KB

1 Like
11

Looks like it’s relying on a feed speed that’s not yet set. Does it work if you select a different jog speed for XY first?

1 Like
12

As soon as I can get it to compile again, I’ll look at it :sweat_smile:

3 Likes
13

What does your jog panel look like? Does the normal jog work when the “go to” doesn’t?

It should be using the same feed rates as the jog button

1 Like
14

Odd, I can check again but yes I jogged and homed it.

1 Like
15

ok @vicious1 … I think that’s fixed now.

index.html.gz.zip

It was working for me because I had additional axes configured where I was running, so it was falling back to the extra axis feedrate.

His logic there wasn’t great.

The real problem is that the comparisons are case-sensitive, and the axis was coming in as ‘y’ instead of ‘Y’…

2 Likes
16

Just glad I was not crazy.

2 Likes
17

Even if you had been, you wouldn’t be alone-so the fix helps all of the rest of us in the asylum.

4 Likes
18

Hey I just had an idea.

Is it possible to display the line number, or line of gcode it is paused/stopped on? Even if it is buffered. I left a clamp on one of my cuts and had to pause it to home and reset. It took me a bit to figure out where to edit my gcode to start from. Something that initiates an immediate stop/pause, then displays the line number or line of code we can search, then pauses again. That would be great to add an external “oh crap” input button to.

edit - maybe even an “alarm” or custom macro?

2 Likes
19

This would be awesome!

1 Like
20

To do this you need to enable line numbers in FluidNC and include them in your gcode.

1 Like