Questions about FluidNC

Software / Firmware Jackpot Board / FluidNC
1

My FluidNC has been a little quirky so today I upgraded to v3.9.1. The install went well, but I have one new problem and some old. The new issue is with the Z probe. This worked with my old version of the firmware v3.7.16. Now the router will move down and touch the touch plate but does not retract. The signal light comes on and it does stop moving down but does not retract. I have the config set to retract 5mm. Am I missing something in the preferences or config?

My second issue is with the display of the machine and work coordinates. Pressing the 0xyz button (or the 0x, 0y, or 0z) most times (in both the old version and the new 3.9.1) does not change the displayed values of the work coordinates. Any suggestions to fix this?

2

Roll back to 3.7.17 for now. It’s the last known good version. Not perfect- but best available at the moment for production use (in my opinion.)

3.9.2-pre1 may turn out good, but there has been a lot of development swirl lately.

3

If you are using the probe button that is expected. If you use the milling basics probe start gcode it works as you want. I do not use the probe button so I never knew to test it. In the future I think we can get the button sorted but using the starting gcode is prefered.

Work coordinates are based off the end stops, the others are based off the current coordinate system you are in, again, this is as expected.

4

Just to clarify, pressing the 0xyz or 0x or 0y or 0z buttons does nothing to the coordinates displayed.

5

Does g92 x0 y0 z0 work?

I don’t use the buttons I use gcode from milling basics.

We can get the buttons sorted out if they don’t work, I just don’t think many people really use them.

6

Oh, and there is a lag, the update is not instant. I think by default it is 3 seconds between every refresh.

1 Like
7

If the buttons are there the buttons should work. Everything else is just confusing. I had the same problem with the probe button (or rather a different one, but it didn’t work).

8

Absolutely right, thats why mine works with an really old stable version. Zero’s button should work. In mine i use them all the time

9

I agree fully, I just don’t think many people actually use them so they don’t get tested. This is the first I have heard about the Zero buttons so I will go check. We know about and have reported the probe not retracting.

Buttons make for a lot more work compared to gcode, so it is good practice to build it into your job.

10

I have experienced these issues in both 3.8.17 and 3.9.1 and agree that if the buttons are there they should work. I would like to add that when the probe button is activated it does not correctly set the z offset……ie, if my probe height is 4 mm, it will set it to something less than this. Usually about 0.05 mm or more.

1 Like
11

I used briefly the new interface before i ran into hardware issues, and then broke down the machine for the rebuild to v4, noticed the same thing. It’s been a few months so going from memory.

Using the probe button works but the actual code is missing the retract command. It doesn’t matter what you have it set to, it ignores it. In one of the settings page you can manually add in the z move, save it, and the probe button will work correctly.

I finally got my machine powered up yesterday with a new esp and it is running the old interface so i can’t give you a step by step at the moment.

1 Like
12

Yup, i have my fluidnc boards running an old version with the trusted v2 interface until they sort out the shenanigans.

13

I looked at this a bit. It appears to be a problem in WebUI v2. I see zero code that actually uses the retract value.

It sounds like this broke between 3.7.16 and 3.7.17? Is that correct? While I don’t think this has anything to do with FluidNC itself, it provides some context for which WebUI build goes with it. I’m just trying to track down the commit that broke it.

14

grbl.js line 500

function grblGetProbeResult(response) {
    var tab1 = response.split(":");
    if (tab1.length > 2) {
        var status = tab1[2].replace("]", "");
        if (parseInt(status.trim()) == 1) {
            if (probe_progress_status != 0) {
                var cmd = "$J=G90 G21 F1000 Z" + (parseFloat(getValue('probetouchplatethickness')) + parseFloat(getValue('proberetract')));
                SendPrinterCommand(cmd, true, null, null, 0, 1);
                finalize_probing();
            }
        } else {
            probe_failed_notification();
        }
    }
}
15

I was looking in the revamp branch of Mitch’s fork, which is what I thought was currently being used. There is no grbl.js file anymore since it looks like that was split out into different files.

ESP3D-WEBUI/www/js at revamp · MitchBradley/ESP3D-WEBUI

16

Hmm. I thought I was on the revamp branch?

I left home so I can’t look again.

It’s possible I might not have pulled recently.

But that’s the area to look for changes then.

There should be a handler for a PRB: message coming back somewhere. That’s what previously triggered the retract code.

1 Like
17

Ohh, I didn’t see it because grbl.js is in the tablet submodule. That is confusing.

Now that code is this, so it indeed is not retracting. Since the tablet code is common between WebUI v2 and v3, need to be careful a change doesn’t break WebUI v3.

const grblGetProbeResult = (response) => {
    const tab1 = response.split(":");
    if (tab1.length > 2) {
        const status = tab1[2].replace("]", "");
        if (is_probing) {
            finalize_probing();
        }
        if (parseInt(status.trim()) != 1) {
            probe_failed_notification(probe_fail_reason == '' ? 'Probe Failed' : probe_fail_reason);
        }
    }
}
1 Like
18

I went ahead and posted this on Discord. We’ll see where it goes.

19

I know i talked about it when i was having hardware problems, i might have done a video showing where to add it. If it’s easilt done in the interface.

20

This issue is specific to the WebUI v2 probing. It allows you to specific a “Retract distance” but it doesn’t do anything with it.

image

For WebUI v3, it might make sense to update the default preferences.json file so that it does a retraction. That probe panel doesn’t allow for specifying a retract distance.

image
image357Ă—556 12.8 KB

But you could easily add that in with a gcode command under the settings for the “Finalizing probing commands”.

image
image358Ă—559 13.8 KB

1 Like