forum.cncdrive.com

Hi guys, any eta on 1.2118? And if it's not imminent, is 1.2117 safe to use, without any machine breaking bugs? Last time I installed a test version it destroyed a custom pressure switch, so, a little wary of jumping in early again.

It would be nice to have a post up when the development version is released in its own thread and all known bugs to be reported on that page and all confirmed bugs in a sticky.

I have been frustrated again using 1.2115 as I have 2 different version BUT they have the same version number on has a major probing bug and the other doesnt - spent a good few hours troubleshooting what I thought was a setup/noise issue on probing but turned out I had installed the dud version

Hah, yes, probing bug in 1.2116 is what caught me last time, undocumented as far as I can see, and cost me a days work to figure out and fix the damage. A sticky post with known bugs would have been great. Reported in June and was told the next version was coming "soon", so I held off on modding my screenset and have been waiting since. Though I see sadly Dezsoe passed away recently, I dont know if he was responsible on the software side, but it's understandable that progress has been stalled.

We still working on version 1.2118, but it will be out soon.
And yes, unfortunately the death of Dezsoe slowed down our progress, he was a talented guy, but we did not stop developing.

What are the known issues in v1.2117 please ?

we did not make a list yet.
How it works is when somebody reports an issue and we test it and find that it is a real bug/issue then we correcting it and creating a new copy of the whole UCCNC source code adding a text file with the bug description and fix description in that copy.

When making a new release then we collecting all these files one by one and creating a list of bugs and using this list as the release notes.
We did not create this list yet.

Very sorry to hear of the loss of Dezsoe...
While I am here, I just discovered a bug, or at least it looks like a bug to me. If there is a comment with a second pair of brackets inside, then UCCNC reads anything in the first brackets. For instance:
(go y3)
is ignored of course, but if you do
(()g0 y3)
then it will run the g0. This is an issue for Fusion, since when you duplicate toolpaths, the name is modified so that for instance "toolpathx2" becomes "toolpathx2(2)" and then x2 is run as a command.
Anyway! Here's hoping "soon" is weeks not months this time . I appreciate the work you are doing.

No reply, so I guess you think this is a more of a problem for the post. Went looking for solutions, and eventually found that latest version of UCCNC fusion post already corrects the issue of nested brackets. So, never mind!

I came from Linuxcnc (free) and uccnc is a paid software... but Linuxcnc is better.. and better support.

I've tried LinuxCNC a few times, found it completely impenetrable, literally nothing was easy - maybe if you're used to it, and have put in the hours. But even the linux environment itself was a nightmare, I hated it. I couldnt speak to support... UCCNC does everything I need, is easy to use, easy to modify and the macros are great. So I'm generally happy. I occasionally check in on Duet boards, wondering an CNC usage in the future, but I think they have a long way to go.