View Full Version : Offset problem
smittys800 06-15-2007, 09:24 PM Having some issues with setting offset's today. After homing the machine, I set the offsets for all axis, and X seems to be adding 20.0. If I set the machine right at 20.0 from the home spot, the offset will be 40.0.
Did not seem to have any problems last night cutting air and a few chips, but today, I cannot run anything. As you can tell, I'm the FNG here.
Thanks for any help,
Smitty
HuFlungDung 06-15-2007, 09:54 PM Do you have a setting in your G52 that is staying resident? I think it is possible to make some of those settings in the system settings persist even past a reboot.
smittys800 06-15-2007, 10:04 PM Not that I can see. I am using G54.
As of right now, machine position is at -20.000, but off set is at -57.000.
Even after I re-home the machine, and zero the x axis, and then again do the offset while at the home postion, offset reads -20.000?
Clueless, as the machine ran fine last night, so I am doing something wrong somewhere!!!
Smitty
HuFlungDung 06-15-2007, 11:25 PM What machine are you running?
smittys800 06-16-2007, 12:47 AM Sorry,
'03 TM-1
Now in my little pee brain mind here, looks as though things are backwards.
Meaning, when I home the machine, and then move the X axis towards the Spindle, would that not be a + move? Once there, machine position is -20.000?
What really bugs me, is that last night all was fine!!
Hmmm, steep learnin curve here!!
Thanks for the help,
Smitty
HuFlungDung 06-16-2007, 12:57 AM The spindle is always deemed to be 'in motion' even though the table is actually performing the move in X and Y. If the tool is making a cut from the right side of the part to the left, this is an X- motion command, but the table is indeed moving from left to right.
smittys800 06-16-2007, 01:18 AM Ok, that makes Sense,
But when I move my table, then set the offset, and decide to move the table again to another spot, same tool, the offset almost doubles. Make any sence to you?
Surfacefeet 06-16-2007, 03:53 AM Did you use a G13 in your last program and then stop it before the cycle was done?
Ok, that makes Sense,
But when I move my table, then set the offset, and decide to move the table again to another spot, same tool, the offset almost doubles. Make any sence to you?
Yes, I think.
When you use WRITE to enter anything it adds what you have typed to what is already there.
To enter the number you have typed you use F1, this overwrites whatever is there.
If you are entering offsets you should use the OFST MSR key. I think that is the name, it is located below the F4 key.
HAILINHAAS 06-16-2007, 08:35 AM G90 and G91 will make a difference too. Look in current commands page .. you will see what g codes are active. And as Geog said ... F1 will enter the exact number you have typed .. press write/enter you will add to whatever is set in that axis
Shotout 06-16-2007, 10:52 AM there.
If you are entering offsets you should use the OFST MSR key. I think that is the name, it is located below the F4 key.
Part Zero Set key on our TM-1s. This will set the current absolute position into whatever G5# offset row and column that is highlighted when in Offset/ Work Coord screen. It is a time saver over having to enter in and over write a 5 place decimal value and prevents miskeys.
Scott
smittys800 06-16-2007, 12:28 PM Thanks for all the help,
Don't really know what the deal was last night. Ran a few parts today, after machine home cycle. Newbie at it's best here.
THere was no G13 in the last program. What I did see, was if I hit the part zero button twice, it added what was already there again. Stupid mistakes, but ya gotta learn.
Smitty
Thanks for all the help,
Don't really know what the deal was last night. Ran a few parts today, after machine home cycle. Newbie at it's best here.
THere was no G13 in the last program. What I did see, was if I hit the part zero button twice, it added what was already there again. Stupid mistakes, but ya gotta learn.
Smitty
Are you writing your code by hand or using a CAM package?
I had a similar problem the other day... Mastercam outputted some optional delete blocks at the beginning of the program with a G92 in them. Didn't notice it until the program wouldn't run because of overtravel.
smittys800 06-17-2007, 01:08 AM I am using MC9, did not have any G92's in the program, but there was a G92 at the very last spot in the offset screen. Zero'd that one out and smooth from there. Spent all day tweekin the program, having a blast and actually made a few keepers.
Thanks to all, someday I hope to return the favor.
Smitty
|
|