rotation detect

[Mark C]

Hello all,

Is it possible to scan the file when post processing and detect if a axis rotations are used and if so trigger an event?

What I have in mind is outputting a note after the tooltable to check a axis rotation direction and invert it if not correct. We have several verticals and some go one way and others the other. I don't know which when posting. We have a fairly new operator who didn't know to check and scrapped a part. I nornally add this note myself but have been swamped and forgot to this time.

I like to make things as automatic as possible.

I'm using a post based on the MPMaster V8.1.1 but will be upgrading to V9 as soon as I get a chance

 

Thanks in advance

 

[ 01-20-2003, 09:02 PM: Message edited by: Mark C ]

[Surface]

Why not change the rotation of the spindle so that all the machines turn in the same direction. On 3 phase motors it is as simple as switching two legs. Anyone with the smallest electrical knowlage could do it in one minute.

[Mark C]

It's not the rotation of the spindle. I should have been a little more clear. It's the A axis. And believe me I would rather have them all consistent. It's kind of a sore subject with me. it was to have been taken care of a while ago, but it never happened. Now they just rely on the operators to check for proper rotation

[Allan Brown]

Sure - what you looking for should be possible. To implement it, we would need specifics. Put your logic into plain English, and someone can suggest the post logic.

[Mark C]

basically, something simple.

like:

if (rotations are used),

n, "(CHECK ROTATIONS BEFORE RUNNING AND INVERT A AXIS IF NECESSARY)",e

 

thanks for your help

[Jeremiah]

Mark- I think what Surface was refering to was the spindle of the "A" axis. This would be a logical thing to do.

[Allan Brown]

In mpmaster, there is already some logic in the pwrtt section to omit output of Z depth limits if rotary or 5-Axis moves are found in the file. You would need to apply a check for toolplane positioning, set a flag, and output a string at the top of your file based on that flag.

 

e.g.

 

initialize amsg_flg

 

amsg_flg : 0

 

in pwrtt:

 

code:

---

  if rotaxis > 0 | rotary_type > 0 | mill5 <> 0 | tlplnno > 1,

[

rot_on_x = sav_rot_on_x #exiting logic

output_z = no #exiting logic

amsg_flg = 1

]

---

in pheader:

 

code:

---

  if amsg_flg = 1, "YOUR MESSAGE HERE!"

---

 

[ 01-21-2003, 11:31 AM: Message edited by: Dave Thomson ]

[steve f]

Mark,

 

Along with a comment your post could be edited to output macro programs when rotary axis was enabled if your controls support macro. With a M00 at program start the operator would have to specify at the beginning of a program which machine the part was being run on by means of a variable value in the macro program (1 = machine 1 rotation type, 2 = machine 2 rotation type, etc.) and the program would compensate as required. This would eliminate having to generate different programs for different machines as well as eliminate alot of operator error.

 

Steve

[Mark C]

thanks everyone for your thoughts. I agree that getting all the machines to work consistently would be the obvious answer, but we're stuck with things the way they are. Nobody wants to be bothered but it becomes my problem when something goes wrong. But, such is the life of the programmer. I will try your suggestion, Dave

 

Thanks again