Major issues exist with the constructor and destructor

[ger21]

I'd love to agree, except my destructor is dead simple and just grabbing values from fields and writing them to the profile.

As I said before, this is done automatically by UCCNC. What are you doing that you need to do this yourself?

It works 9/10 times.

For EVERYONE else, it woks 100% of the time.

Yes, I'm running Windows 11. The PC is a home built 10 core i5 in an MSI MAG B660M Mortar motherboard with 32 GB of ram.

[cncdrive]

Yes, many customers are running Windows 11 without problem.

[Battwell]

the only thing the constructor macro cannot do (in pre 115 versions) is set something that cannot be set until the control is out of reset.
(like set current tool) or anything with exec.
deszoe wrote a nice fire once macroloop to overcome this.
my systems still use this feature. everything re populates on first reset after software start.

[Battwell]

https://youtu.be/zFRpZK72R7M

Load everything on first reset

[Parkgrr]

@CNCDrive, glad to see you responding, though not addressing the actual issue. Care to respond to the other threads?

@Battwell, not a fix-all, but in what is seemingly like a lifetime of UCCNC clean-up I will implement this. Do you have a link or code snippet?

I switched to W11, did a clean install of the OS and software, did some experimenting without any custom macros on the dead stock program and am still having problems. Random axis movements from CNCDrive's cursed UCR201, a new freeze up commonly happening, crashes, UC300ETH hardware disconnections, profile not saving, frustrated out of my mind at everyone saying it's my fault for some mysterious reason when it's happening even I'm using this sht BONE STOCK and have checked everything everyone has told me to check many times, ethernet everything, voltages correct, no RF interference anywhere, power saving off, sacrificed the best lamb, blah blah blah. Haven't been able to work for 2 months because I'm shellshocked from the past 2 years of trying to get UCCNC to work properly and can't even walk in my shop door. May be liquidating my shop and quitting. Not trying to be a baby, just not sure I can take much more and can't bear another conversion. The cost-reward just doesn't make sense when the cost of operating the machine is so high due to UCCNC-caused crashes and lost time due to nuisances and lost years due to stress on extremely high dollar projects. I wince every time I do *anything* in UCCNC inc just powering up. Super disappointed that I chose UCCNC. There's a chorus of ~4-5 ppl on these forums that say it's god's gift to machinists and that the support is so good, I must live in a different dimension.

[ger21]

Unfortunately, I don't have an answer for any of your questions.
You're experience seems to be unique among UCCNC users.
I have a friend that's used UCCNC in a production environment for 5+ years, and has not experienced any of the issues you are seeing. I've personally never experienced any of the issues your seeing.

[cncdrive]

We have lots of UCCNC users and with the latest update basically nobody experience any issues with the UCR201 except the OP.
Also it is interesting that the OP experiences all type of different issues.
I think his only intention is to ruin our reputation, he is probably a destructive narcissist enjoying posting crap on forums.

[cncdrive]

And in case you really have that much problems then we are happy to buy the devices back from you for a full refund and then you can buy something which works for you.