No one is having troubles with the latest fluidnc? I am having all sorts of troubles.
I just issued g28 z-70 and it moved like 20 down then, back up, right away. (just after homing).
Probing has not been successful, this is not working for me.
g28 x0 y0 worked though
shouldn’t that be G38.2??
What are you trying to do??
G0 Z-70
G1 Z-70
g28 is different for marlin and fluid, I would not use it.
True
G0/1 is move to
G38.2 is probe
This is my CAM Probe on program start with the mini touch plate from V1
G38.2 Z-80 F100 P0.5 ( probe down set thickness )
What is the best option for polling now, auto 1 second?
Personally, I use auto polling, and then have a fall back manual poll once per minute or something like that in WebUI3.
I haven’t had any problem with Autoreport, but I have seen Mitch say that it causes problems if your WiFi connection is shaky…
I use 1 second.
Okay so polling 1 second. I knew I had see those exact comments, I just could not remember where.
So that means instead of the webui asking for location, the esp32 “knows” to send it back as close to every second it can? That makes sense half the traffic even
Any other v2 preferences you can think of?
polling every second, enable probe tab, change travel speeds.
o…k. my bad on the g28, but I used the probe function in Fluidnc, I was not trying to command line that LOL, but i was trying to move with g28, ugh!!!
and the probe was not working when I used it in my gcode, neither. It seemed delayed. I don’t know, I am giving up for tonight. code and frustrated.
I was just trying to move closer to use Jaimes surfacing program. i wanted it at x0 y0 (after i homed) then move to z0 and let his (g92 I think it is) work. I was just trying to not to have to spam z 7 times is all.
And very ODDLY g28 x0 y0 moved to zero for me, but Z did not like it, now I know why, LOL
I have no idea what that is in fluidnc.
G92 sets the location, seems like that is what you actually wanted.
If you want to start a thread we can walk you through it. I can update the docs if needed. Jamie’s tool does not require you to move at all. it is all built in.
Makes me think the probe tab is best left off.
In this mode FluidNC sends the status to the WebUI. It sends updates whenever status changes and at regular intervals during moves. This mode can make the status display appear to be more responsive.
The interval here should be the minimum amount of time between updates. So you can read it as "Send me an update no sooner than < n > ms after the last update. But it will not send it, unless something has changed and it is necessary to send.
In this mode, the WebUI will send a ‘?’ and a status response is returned. This mode introduces more traffic since
However, polling does have the benefit of the failure mode affecting the web, instead of FluidNC, as stated above.
I’ve only tried auto reporting with some of the websocket stuff I’ve been playing with (same functionality). It’s really nice that it doesn’t spam the terminal when it’s not moving. Note that the WebUI tablet page/extension sets the auto-reporting to 300 ms.
Edit:
Oh, dots are connecting in my head. Auto 1000 is $Report/Interval=1000 while the tablet UI is doing $Report/Interval=300. I’m not sure what it means if you had it set for polling but then the tablet UI set it to auto 300 ms. If it was doing both, is that dumb? Or a good backup in case something happens?
Okay I think v2 configs and stuff are all updated, going to merge it now. v3 stuff is going to wait a little bit. I want to give 3.9.1 and v2 a good test before I even think about V3 again.
