Likely noob problem related to TP Set Z0

[christopera]

Chris, FYI, I'm in Europe this week and probably can't reply in detail until next week.
Dave


Sent from my SM-G900V using Tapatalk

No problem, Dave. I find myself traveling a good bit in the summer and my ability to respond to work requests via computer often slows down dramatically. So I can appreciate what it's like to travel and manage this forum.

A little update here. I think I finally got everything to work! I was able to set tool length, set Z0 via WC page, and when I enter a Z coordinate it went there. I set a telescoping gage to 3" via a micrometer and was able to consistently get a bit of friction on it at Z3 measured from the table for every tool in small tool library.

It took some work though, let me elaborate a bit. I turned on MTM then attempted to reset TCP TP MCZ. I wanted to use the bottom of the spindle to do this so that I could enter 0 PTL (reduction of a variable). Of course in MTM it made me use a true tool number, #0 doesn't suffice. So i decided to setup tool 100 with 0 PTL, 0 Offest, RH (Skip RH on). The TCP TP MCz operation then ran. But after running the TCP TP MCz operation a few times the machine would probe until it actived the TP, then instead of reversing it would then lower some more. Luckily I set my limit switch to active just before the TP is fully compressed (a stroke of practicality I'm glad I had). This happened at least three times. I restarted the software, re-referenced, and it happened again. I repeated, the issue went away. No idea what was going on. After this successful try I was then able to log tools and get consistent results. Victory!

Now I am going to do a bunch of calibration work, mainly get my TP fully squared up, get a more accurate measurement on it's uncompressed height, reset TP MCz, and relog my tools. But I am confident after I do this that I will get consistent and usable tool library as intended in MTM. After playing in MTM for just 15 minutes I am already excited for my next machine operation.

[DaveCVI]

A little update here. I think I finally got everything to work! I was able to set tool length, set Z0 via WC page, and when I enter a Z coordinate it went there. I set a telescoping gage to 3" via a micrometer and was able to consistently get a bit of friction on it at Z3 measured from the table for every tool in small tool library.

Good News.

Now I am going to do a bunch of calibration work, mainly get my TP fully squared up, get a more accurate measurement on it's uncompressed height, reset TP MCz, and relog my tools. But I am confident after I do this that I will get consistent and usable tool library as intended in MTM. After playing in MTM for just 15 minutes I am already excited for my next machine operation.

[/quote]
Uh, in case you have not read this thread, please give it consideration:
http://www.calypsoventures.com/forums/v ... ?f=6&t=177

Dave

[christopera]

Thanks for the link. Seems like maybe it would be simpler (and more reliable) to set my combo probe/touch plate up as a permanent probe and get a static touch plate.

[christopera]

Hi Dave,

As I slowly progress towards full functionality and continually fine tune my machine (hardware and software) I do have one more question for you. And this may be obvious but nevertheless it's something I don't understand and feel that doing so would improve my own setup performance. It appears to me that when MTM Mode is off that I can set X0, Y0, and if I load the G-Code those WC offsets stay the same. Though if I set Z0 before loading that coordinate changes once the code is loaded. Why is this?

[DaveCVI]

Hi,
I can't say for sure - as the action depends on what the gcode contains.

Background: There are multiple work coordinate systems (sets of axis offsets) that can be used: these are designated in gode by G54, G55, etc.
To set the stage, remember that gcode is really old in computer terms - 1960's vintage - and that gcode is inherently stateful.
One of the WC systems is always "active" - i.e. there is no such state as "no WC system is active". The default WC system offsets are used if no WC system is explicitly called for by gcode. The default is G54. Once to set a WC, say for example G57, that will be the active WC until it is changed.

Many gode files reset the CNC control state to a default set of states early in the gocde - typically G54.

Also, Mach may or may not remember WC offsets between mach sessions - that depends on some mach option settings.

Many people never use anything other than the default G54 WC - and thus they never see the EC offsets change unless they change where the WC zero is.
There are also various ways to set WC offsets via gcode (besides G54).

So my first thought is that if the WC offsets are changing when you load a gcode file, I'd suggest first looking at look a the gcode file to see what it is telling the CNC control (mach) to do.

Dave

[christopera]

Once again, thanks for the thorough reply, Dave! I am learning day in and day out. Right now, the probing operations are changing my world as far as setup and set down times. Additionally, I've purchased another tool height touch off plate and will install it using the timing input. After that's done I anticipate the machine will run like a freight train for just about every job I foresee doing. There has been a big learning curve, know all the buttons, operations, the order by which all of it gets done, but I am getting there.