UCCNC IS SO DISSAPPOINTING.

[CNCChris]

Im probably gonna cop some slack for this post but here it goes.
Ive been trying to sort this problem out with support since February, Most of the time they dont bother to reply

Received an M6 macro for a tool change from uccnc support for a mnual tool change macro using an atc spindle. (macro attached)

First issue
If i setup a tool in the tool library with the correct offset. Let say tool 20
If i zero tool 20 to the top of the material
Press cycle start
Machine plunges straight down and crashes into the table.

If i set machine to tool 0
Set spindle nose to the top of material with no tool
machine moves to tool change position
insert new tool
gets offset
seems to work ok

why does it crash if I zero machine with the tool I want to use?.

I found this M35 macro for setting the Tools to the tool library, It does an intial probe from the spindle nose and writes it to the "spindlekey" where ever that is and then it works out tool offsets based off the difference, are these 2 macros conflicting?

Second issue
Pressed "Park 1"
Machine raised straight up and crashed right through the homing sensor destroying it.
I did not change the setting, its the standard setting, Why would software be setup to fail like this?

Beyond frustrated and really starting to hate UCCNC

[CNCChris]

Ok I've calmed down a bit and fixed up the machine

I edited the PARK macros and they work fine now

The problem seems to be with starting a file with the tool in the spindle
Let me explain



Select tool 20
Load file
zero tool 20 on top of material
Cycle start
CRASH!!!!

If your first tool in the gcode file starts with the tool thats already in the spindle and set to material top it will crash.

Chris

[Delco]

Does your gcode have a G43T20 call to get the measured tool height for tool 20 and is your tool table populated , if not then u need to use ref tool probe stategy in the probing section.

[Battwell]

It’s not disappointing
It’s not tolerant of Id. 10t errors.

If your not getting correct offset
Type in mdi g43 h tool number
This loads that tools length offset .

You can then set z zero with the loaded tool

[CNCChris]

Hi ID10T

I guess your calling support ID10T because they wrote the script.

The M6 tool script calls all that, no need to input in MDI.

Enter the number and click change tool and it grabs the tool offset, it's built into the script.

If you measure with the existing tool and then that is the first tool to start then it crashes

[CL_MotoTech]

I have done hundreds of thousands of tool changes, probably 10's of thousands of startups and touch offs, and the only time I get crashes is when I efff it up. I don't uses that macro, but mine isn't that different. It's for a carousel. Anyways, it sounds like your tool lengths aren't being referenced correctly. Try manual measurement and logging, get rid of the M35 for now, and see if you get better results.

[mr_guy99493]

Oh, good...
"Screen file not found" and the .pro file is full of zeros.

Luckily this is a known issue, and could have been averted had I thought to enable a plugin to perform the actions the software should perform automatically.

"Hey Ford, my car rolled away crashing into some old lady, even though the handbrake was on"
"Oh, yeah, the handbrake doesnt always work, we suggest leaving it in gear just in case"

Im sick of this.

[cncdrive]

You should not turn off the computer while UCCNC is saving the profile, because that will leave an empty or broken profile file.
You could use the AutoBackupProfile plugin to get backup copies of the profile file.
We just worked on optimising the Ini file reading/writting routines.
In the current UCCNC the keys are written one by one using the built in Windows API functions which we now implemented using standard file reading/writting functions instead of the Windows built in functions.
The difference will be that all keys will be written for one single writting cycle, so the file will be vurnelable only for sub milliseconds while now it is vurnelable for about a second or so.
This will make the writting safer, however ofcourse it is not possible to fully protect against a computer off while the UCCNC is saving to the profile, but with a sub milliseconds time interval writting cycle it will become very unlikely that the user switches the computer off in that exact short time interval.
The new ini file writting routine is already implemented in the new upcoming UCCNC release.