I marked this with the prefix "Newbie" because I am new to UCCNC and the UC300ETH...
I received my UC300ETH a few days ago and first yesterday I had some time to test it a bit more seriously together with the UCCNC. I was very pleased with some functions, which I could not test with the demo version before, but what impressed me most is the huge speed I can get out of my CNC with this combo. Previously, the top speed for rapids was 5500mm/min, which I found very fast, so I never thought I could to that but never the less, I increased to see what happens, when will my motors start stalling. So I increased the speed first to 6000mm/min, then to 7000mm/min and played around for a while. Nothing bad happened, so I increased to 8000mm/min and... still nothing, no stalling. I just could help myself, played with the X and Y watching the whole table and the Z flying across at this, for me incredibly high speed. Not a single glitch or a sign of struggle... Didn't really reach top speed yet, no stalling, so I will continue playing tonight.
I changed nothing else except the motion controller and the software. Maybe the same speed would be possible with the same setting even with Mach3, but for now, there is no plugin for Mach3, so I can not test that. I can also not test how UCCNC with the UC300USB because my UCCNC license works only with the ETH, so I can't really compare apples with apples, but it certainly proves that my machine is not all that bad, it can run very fast without any additional hardware upgrades. Considering the fairly small table I have, 8000mm/min is pretty scary fast and before I keep this, or even higher speed, I need to test the reaction speed of hitting the limit switches. I don't want inertia to destroy those switches or smash the table or my Z into the sides, so that is definitely needed to be tested as well, especially at these speeds.
Another speedy reaction I noticed is at probing. Perhaps that is just my imagination, but I have a feeling that the UC300ETH and the UCCNC are much faster in detecting the probe contact and stopping than Mach3 was. I still need to get this tested out, but playing with it certainly gave me that impression, and if I can confirm this, it would be great. OK, maybe no surprise, since UCCNC is a much more modern software compared with Mach3, and is not written for parallel port at all, so it should be faster, but anyway, it is good to know.
Other things I like about probing is the possibility of probing with jog. It is a very simple, but genius idea because it makes probing so much easier in many situations. No need to type anything, just jog and the machine stops when the probe gets touched.
Things I don't like is the discovery that it does not support radius compensation. I initially thought that this is no big deal, I can wait until they fix it. Unfortunately, yesterday I thought I might as well start using the new setup for real, but I hit this problem immediately because the code I thought will be the first to use needs the radius compensation. This would have been fine, if that was the only file, but then I loaded another, and another and another... I guess you get the picture. Most of my files use it, and regenerating the code for all of those is not going to be easy, so I probably have to wait for the Mach3 plugin and continue using Mach3 until G40, G41 and G42 are implemented. I knew that this was not supported in UCCNC but never really realized how dependent on them I was.
Never the less, the UC300ETH with the UCCNC is a real speed monster, and I hope that it is also with the Mach3 and that the Mach3 plugin becomes available soon.