If so, you obviously know more of where the tool's going and have confidence in the tools you've set? Out of interest, do most of you who go for it 1st time write your own progs and set your own tools?
However, it's interesting as to the different ways of proving out. The original post was just an easy way to raise the Z as a global. This is starting to divert a little but it's quite interesting. This is a global shift, which 'lifts' your datum up by the value you input.ĭoing it this way, allows you to run all tools etc, without altering any of your true datum values (which can be dangerous when putting them back after dry running, especially if your'e dyslexic!!!) We then enter a positive Z figure (say 50mm) into the Top left work coordinate screen. So, for program proving, we set up with everything as it should be (datums/tool lengths etc). This will write to the Bottom left work coordinate screen, No 01 (G54), once read. We type our datum info into a G10 line at the start of the program, such as (metric figures)
In the work coordinates screen, there are 4 numbers. Just posted this as a reply to another thread, but thought it may be of benefit to someone as a post on it's own.įor proving a program in dry run, we lift the Z like you but a different way.
0 kommentar(er)
