UCCNC 1.1027 Works but 1.2113/6 don't

[ryana14]

So others can benefit I'm moving my report from e-mail.

1.1027 works perfectly for me, I can run G-code with no issues.
With 1.2113/6 I can jog the machine, I can home it. I can't run g-code though, not even one line, I immediately get ext. e-stop triggered. If I reset I can still jog and home the machine but even a one line X1 gcode will not work.
I have tried this on four computers. Three DELL laptops from 1 to 10 years old with built in gpu's and a 3 year old gaming PC with a Nvidia graphics card. I have installed the most appropriate graphics drivers on all. I have disabled all power savings and have set UCCNC to use 100% of resources.

I have two videos to show the issue:
1. 1.1027 jogging, homing and then running a simple few lines of Gcode. Works well.
https://photos.app.goo.gl/zKVe8QxvyiZJJFUc6

2. 1.2116 jogging, homing, then attempting to run the simple Gcode twice, then jogging and homing again (successfully) then trying just one line of Gcode. Any Gcode fails with ext. e-stop triggered. No Gcode works. The resource monitor does not show anything of note.
https://photos.app.goo.gl/DyfKhqEBQG958Dcj6

As I said I have tried this on four computers so I doubt it can be my computer set-up. Any help to resolve this would be appreciated. I would be happy to run a debug version of the code to try to help figure this out.

[cncdrive]

Try to disable the e-stop input and the limit inputs in the configuration to see if it resolves the issue.
If it does then your e-stop input or limit inputs getting noise spikes.
You can then try to add some debounce using the debounce filter setting in the UCCNC configuration, it filters/mutes the inputs for the set amount of milliseconds.

[ryana14]

Thanks for the reply. I have tried that. I disabled the e-stop pins as one test, I also disabled all limits as well. No change. I also tried hardwiring the e-stop so it was always on, also no change. What puzzles me is that 1.1027 works fine so that rules out noise.
As far as I know there is no debounce for the UC100. Sorry forgot to mention I was using UC100.

[ryana14]

I still can't get the later versions of UCCNC to work. I have the UC100 USB controller. I have tried on 4 windows 10 computers, between 6 and 1 year old. All have working graphics drivers and gpu's.

To summarise:
-- UCCNC 1.1027 works fine. Gcode runs, I can jog the machine.


-- UCCNC With 1.2116 I can jog the machine fine on any axis. But I can't even run 2 lines of gcode. eg. X1 Y1 will fail with ext. e-stop triggered. Sometimes one line will run but then the next will fail.

Clearly if 1.1027 works fine then my hardware set-up is fine, it's not bad pins or anything like that. All my PC's run graphics tests just fine. My only conclusion is that this is a UCCNC bug. Looking back through the forums many people have had this issue. Can someone please help. I'm happy to run any diagnostics provided.
Thanks

[cncdrive]

It is likely video card drivers problem.
UCCNC 1.0027 uses Flashplayer for the graphics and 1.1xx and 1.2xx uses OpenGL.
OpenGL uses graphics hardware acceleration, so it requires the graphics card drivers to be installed properly in order to run efficiently and properly.
It is a common problem that Windows installs an unoptimal graphics card drivers by default, but with that OpenGL is not working at all or working, but unefficiently.
By uneffitient I mean it overloads Windows or the memory which can lead to problems like lost connections when the software no more have enough CPU time or enough memory to work properly.

I would check the video card drivers, Windows usually always says that the video card drivers are up to date even if an unoptimal default drivers is installed, so the only good way is to check the video card manufacturer's website, download the latest drivers version and install it manually.

[ryana14]

Thanks for the reply, I have installed the proper Intel drivers on all four computers that I have tried. I have also run the Furmark test, it runs fine. See screenshot of Furmark graphics test which shows the driver details.


https://imgur.com/a/mv0oOU1

[cncdrive]

How does the Latency test looks like on the General settings/Statistics page?
Are there any spikes?

[ryana14]

Thanks for the suggestion.

Yes, latency spikes on one line of gcode, sometimes to 10ms then ext stop triggered, most often to almost 20ms then ext stop triggered. This was on 1.2116 UC100. Previously on 1.2113 I had similar behaviour.
See screenshot of the latency https://imgur.com/a/2cD726i
Jogging works fine though.


I then switched back to 1.027 and the same driver as 1.2116 and the gcode works fine, no issues. There is no latency checker there though.

Thanks

[cncdrive]

Open the Windows registry, type cmd and then type regedit.
In the registry modify the following key:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile

The NetworkThrottlingIndex key, modify it's value to 0xFFFFFFFF

Then restart Windows.

[ryana14]

I tried that on two PC's, one a Dell with Intel core i7 and a Nvidia GPU, and one an older Dell laptop.
I also disabled any power saving.

Unfortunately no change to the behaviour, when I enter a gcode line I either get ext e stop triggered, one line works, then next one does not, or nothing at all happens.

Thanks for helping with this.