I think Luc would likely add it back if it was reported.
He was on vacation for a bit, but I wanted to verify it was properly in WebUI v2 and wasn’t something Mitch added before I bothered him with it
Hmm, well Mitch is already working on the v2 fix. I actually like the flexibility of the V3 configuration options so I’m not sure having an explicit retract distance there is necessary. But then again, I don’t use this. I just put it in my gcode.
1 Like
Well, flexibility is good, but I think ease of use is more important.
Adding retraction doesn’t prevent someone from setting it to 0, and still customizing it yourself if you want.
But the retraction box makes it more accessible for people using the probing panel to not have to worry about the separate settings tab to use/change it
I can understand that perspective. Either way, what Mitch is updating is independent of what would need to be changed for WebUI v3.
I dont remember actually what version in using but with the v2 ui it lost the second probing touch. (It retracts but only touches the probe one time
Mitch put out a new WebUI v2 build with the fix to use the specified retract distance. I confirmed it will now retract based on that value.
It will still only touch once. It would be easy to make a macro to do whatever you want, but I think a generic probe panel is always going to have limits. When running a job, I’ve never cared. I know that it can make sense for the first probe to be at a higher speed, then again at a slow speed. But, I just jog Z to a reasonable distance and do a slow probe.
Thats the way i do it too, but was just saying the probe code was changed.
I hope fluid solves the bugs with the latest versions and the new interface (im not a fan but would like to try them more than a couple of minutes)
What bugs? I mean it’s software so there will always be bugs, but I’m not aware of anything impacting as of 3.9.1. The main thing in the next release that I want is Mike’s fix to not display that basic screen if you load the UI during a hold.
I would be curious on your opinions surrounding this. There are a bunch of options to customize the interface to your liking. I know for me, by default it displayed a bunch of panels I didn’t care about, which I hid. The jog panel in v2 drove me to v3 more than anything else which I think is better, but then I made my own panel. There are a lot of varying preferences around user interfaces.
1 Like
As my machines are always cutting, routing non stop (and thanks god because thats good Business ) i havent had much time to update the software and try new things. Will take the time with one of the lr4 builds to do so. Then i would have to train the guys who attends the machines into it. They are like machines programed to v2 from factory lol
1 Like
There’s really not much to gain from upgrading to V3 if V2 is working for you, and you aren’t interested in themes or extensions.
The interaction in either is minimal for me.
I just happen to like the Status panel and the Jog panel a lot better in V3.
I felt like I had connection issues in V2, but that was at a time where FluidNC had more crashing/memory issues.
V3 has the same controls as V2. You don’t gain extra functionality by upgrading. It just looks different
1 Like
We never have seen a crash using the machines the way we do. Its just a matter of presenting the ui to the guys and see if they would like it. As i said earlier we dont get the bug for refreshing the ui ( there’s no f5 button)
5 second fix, probe retraction
2 Likes
You could just do it as a single grbl jog command:
$J=G91 G21 Z10 F1000
This way that G91 only applies to this specific line. Either works.
1 Like
The probe for WebUI-v3 will be fixed in the next build, in a day or two.
For any new installs it will work, but if you already have a V3 preferences.json, you will need to update the Probe panel settings to include the retract in the finalize commands.
from
G10 L20 P1 #selected_axis##probe_thickness##
to
G10 L20 P1 #selected_axis##probe_thickness#;$J=G91 G21 F1000 Z#probe_retract#
That P1 likely should preferably be P0. Will feed that back to Luc as well
4 Likes
Is this a general place for all questions about FluidNC? Please forgive me if it’s not. If I should be posting in a dedicated thread, let me know and I’ll redo it.
Why do FluidNC installs from a zip downloaded from the GitHub repo, and built and uploaded via VSCode, show no version number, saying instead something like “No Git”? I’ve noticed this issue every time I build from a download.
I was on FluidNC v3.7.18 - and this version just got me with the issue of “pausing the job causes the steppers to disengage and the router bit crashes into material.”
So, I downloaded " v3.9.2-pre1" and built and installed it, and now I don’t get a version number even when I run $ss in the console.
Am I doing the build wrong?
In a related matter, I tried to punt and install the main v3.9.1 using the web installer, and it thinks there is no version of FluindNC on the Jackpot, and offers me to either wipe everything and install, losing all files I have on the Jackpot, or “update” existing without wiping, but when I tried the latter, I got "Was not able to flash device: Error: Timeout" (also happens when I do the “Boot” button) — So, I’m thinking about doing the wipe.
Update: I also tried the erase all option, and also got “Was not able to flash device: Error: Timeout”
Hmm.
Still pecking away at it.
no, not really. We really don’t want mega thread, question dumping grounds
Because it’s not officially connected to github. The build process using the context of the local git repo to figure out the version number. When you download a zip file of source code, it is completely detached from git.
I would have thought you should still get a version number, just no commit string.
This is something you may need to ask Mitch. Sounds like a bug in the build script. It’s been a while, but I’ve always had version numbers in my self-built firmware.
I’ve had this happen where it thinks the firmware isn’t there. I usually just disconnect and connect again, and it usually fixes itself. Once I had to wipe the whole thing to fix it.
I’m not familiar with that error. Maybe try a different cable, different USB port, etc. and see if anything changes.
1 Like
3 Likes
whoa, this is your own release, outside of Barts?
ohhh, i see, this is only webui. The version confused me, i thought this was full fluidnc.
I tag it FluidNC just to differentiate it from the official repository, which doesn’t support FluidNC
1 Like