move point error

[djone368]

We have dmis 3.5 at our shop
when writing a program and at the end of the day we save and log off
next day when opening all the move points have changed by about 2000mm
does anyone know why

[Wes Cisco]

rerun alignment

We have dmis 3.5 at our shop
when writing a program and at the end of the day we save and log off
next day when opening all the move points have changed by about 2000mm
does anyone know why

Well, if you do not recall a saved external alignment at the begining of the program and you do not rerun the alignment, I am not surprised at all. Once you have done either one of those two things you should be spot on. HTH

[bw_bob]

I run 3.5 mr2.....Does anyone have access to the machine @ night. A new one for me.

[djone368]

Wes

I write and save the alignment as a seperate program
then recall it in the main program
the fixture hasnt moved either
maybe I am missing something
I am realatively new at this
any other suggestions
thanks

Dave

[Underspec]

Do you loop any features your programs? Move points will change if you loop features. Atleast for me. 3.7MR1.

[Mike N.]

I'm not sure what version you are working. I have found in a few versions that when writing or editing prog's the cursor postion doesn't update the machine xyz position. If your not careful you could add incorrect move points when using the print key on pendant and not watching the screen coordinates.

Is it possible that you didn't execute your prog or edits made until the next day? then the previous info could be the cause.

just a possibility and a warning to watch the xyz status bar when editing or creating prog's

[Tested]

I have 3.5 and find this happens to me any time I tell DMIS NOT to update alignments. There might be something in that for you but I'm just guessing.

[djone368]

I will try to keep that in mind