Move/point Unexpectant

[VONDY]

Does Anyone Know How A Move/point Can Be Inserted Into A Program Other Than Typing It In, Ctrl+m, Or The Print Button? We Have Had Quit A Few Instances Lately Were Our Operators Have Had The Cmm's Crash After The Program Has Finished Running Because Of A Move/point Being Inserted At The End Of The Program.
They Have All Insisted That They Haven't Hit The "print" Button On The Jog Box, This To Me Was The Logical Conclusion, But It Has Been Happening More And More Lately And I Am Starting To Wonder If There May Be Something Else That Could Cause This Or If Anyone Else Has Encountered This? One Operator Said He Never Used The Jog Box Until The Program Was Executed From The Pc, After A Program Is Executed, Is There A Way To Insert A Move/point? Is There A Possibility That A Program Was Exited And Then The Print Button Was Pushed And It Was Placed In Memory And Then When A New Program Was Opened, Could It Insert It At That Time?

The Operators Cursor Is Usually At The End Of The Program And That Is Were The Move/points Have Been Being Inserted At And Most Of Them Open There Programs In The Command Mode. This Has Been Happening On Our Machines That Are Using 3.5mr2.

[#2#]

Almost certainly operator error! That is why I make all our programs read-only. Then this can not happen.

[T Miller]

I don't know of anyway it can. But if your jog box is like mine the print and the done button are right next to each other. Sorry no help

[Matthew D. Hoedeman]

I think, that depending on the controller, a PRINT will store until it can go to the PC (ie a program). Also, if the program is open and you lose or shut off the air, the 'locking' of the z axis (machine dependant) will send a 'move point' to the program (I have seen this happen). Also, if more than one program is open, ANY PRINT move point will ALWAYS go to the ONLINE program.

[Peter DeGroot]

We only let the non-programmer / operators operate the CMM in "operator mode" - Execute only - unable to edit the program.

[rebeldude]

On mine, I move it to wanted move point position, then I have to wait about 2 minutes before I can insert it... The position takes that long to read

[VONDY]

Who can tell me where to go to check/un-check the mark that allows the "PRINT" button on the jog box to insert a move\point? Its been so long since I have programmed on-line but can someone also comment on how to enter a move\point while on-line if I remove this mark? My operators may already know this, but if not, I will want to be able to tell them what to do to insert one.
Sharpe 32 controller

[Bill **********]

CNTRL-M Inserts a move point from the key board.

[#2#]

Who can tell me where to go to check/un-check the mark that allows the "PRINT" button on the jog box to insert a move\point? Its been so long since I have programmed on-line but can someone also comment on how to enter a move\point while on-line if I remove this mark? My operators may already know this, but if not, I will want to be able to tell them what to do to insert one.
Sharpe 32 controller

edit-preferences-machine interface setup-on the sharpe 32 tab you can select "move point" or "delete hit".

I think that is it - not at my machine but I will double check when I get it started up.

EDIT - OK, I looked and that is the correct path to take. Looks like you can also have it as "done"

[VONDY]

edit-preferences-machine interface setup-on the sharpe 32 tab you can select "move point" or "delete hit".

I think that is it - not at my machine but I will double check when I get it started up.

EDIT - OK, I looked and that is the correct path to take. Looks like you can also have it as "done"

Will this override all operators preferences or will all operators need to log in and change this setting? Is there a 'write protect' that I can do that will set this and not allow it to be changed? If this is done, will it lock the operators out of setting up there own preferences for there other 'edit-preferences'?

[#2#]

Will this override all operators preferences or will all operators need to log in and change this setting? Is there a 'write protect' that I can do that will set this and not allow it to be changed? If this is done, will it lock the operators out of setting up there own preferences for there other 'edit-preferences'?

I believe this will change the button's function for all operators (log on names). I do not think there is a way to lock them out of changing the "edit-preferences" Of course, I would highly advise that you train your operators to not mess around with anything in any of the menus. I know that may not be realistic but...

[Underspec]

setup should cover everything. Parameters change settings just for that program.

One reason your move points could possibly be moving to different locations is that your datums could be mis-hitting thus changing the origin, then the move point would change also of course. Have an operator setup a program or install a NETCAM and watch from home secretly

[#2#]

I just thought of another possibility. Underspec may have a good point if you measure a cylinder and then align to it and then the move point is the only move after the alignment. I am sure we all know that PC-DMIS can get a cylinder's orientation messed up if it is approx. the same length as diameter and you take only two rows of hits.

[VONDY]

These are programs we run every other shift or so, so they get ran allot and when you only have an instance once every month or two and not on the same parts ( well one program it did happen to it twice) or even in the same plants, I will have to say I think the move point is being inserted accidentally some how, I'm trying to find the source and eliminate it. I have had it happen to operators running these machines for a long time without any instances of this happening before, it just seems to have started, well since we went from 3.2 to 3.5mr2 is when more odd things started happening(?). You can see the move point in the program and when they exit out of it and load it back up, it will not be there, they do not have the rights to write to the programs but it will allow them to add move points to there opened program, they just can't write over the original.

[Underspec]

I've had issues with operators crashing probes due to these "weird" occurances. I am 99% sure that it's half the operator's fault and half the machines fault. I found that these seem to occur when programs get errors (PCDLRN demon) and/or machine errors. Some operators don't close out or exit PCDMIS and just go right into executing it again.