Spindle fails to orient unless M5 commanded

[myhäje]

I removed M5 from Okuma's postprocessor before toolchange to shorten cycle time and now the spindle automatically stops (=orients) when moving to tool change position. Or at least, in 90% cases it does. Sometimes the spindle just keeps rotating and the orient led keeps flashing, recoverable only by reset. I'd hate to put the M5 back because it will add at least one second of cycle time.

Ideas?

Similar Threads:

• Need Help!- Stop machine if spindle motor fails.
• 2nd spindle orient
• Fanuc 6t, spindle runs in manual but not commanded.
• Need Help!- 197 C-AXIS COMMANDED IN SPINDLE MODE
• Need Help!- M19 Spindle Orient

[deadlykitten]

hy

M19 can/may not work if S<>0
S can/may work after M19 without M18

[konwey]

Mine has M19

[deadlykitten]

M19 may work if spindle is rotating but there is no S comand

this may happen, for example, after M109 + unbalanced fixture

S comand may behave the same

you may not get same behaviour on M110 / M147

.. those are machine state transition codes i experimented recently with such stuff ...

[myhäje]

Well the question is, why does it orient sometimes and sometimes it doesn't? A bug in the control (OSP-P200M)? An older machine with U10M always orients from spindle on state.

[deadlykitten]

hy myhaje ... somehow i thought that you maybe in a deeper problem ...

i dont know you dont have a constant behaviour ... all i can say is that confirmation from senzors may not always mean also a phisical state, but i dont know exactly how this happens

that thing happens always in same place ? thus you have a runing program, there are no interventions, and at same code line, sometimes it works, and sometimes not ? or are there different locations inside the code ? kindly !

[myhäje]

hy myhaje ... somehow i thought that you maybe in a deeper problem ...

i dont know you dont have a constant behaviour ... all i can say is that confirmation from senzors may not always mean also a phisical state, but i dont know exactly how this happens

that thing happens always in same place ? thus you have a runing program, there are no interventions, and at same code line, sometimes it works, and sometimes not ? or are there different locations inside the code ? kindly !

It is completely random. Could be a sensor issue, it is a 10 year old machine after all. Just wondering if anybody else has experienced this issue.

[deadlykitten]

i am not sure about what i am about to say : if you removed M5 from the code, so shorten whatever, than it may be a behaviour on the machine that is not constant

when it works, spindle is stopped, and M19 can occur ; otherwise you are in trouble

after testing CTR codes, i can tell that, even if more axis perform simulateously, they dont always behave the same : in other words syncro is always achieved, but start moments are not always the same

when machine reaches M19, is the spindle always stopped ? also, if the machine reaches M19 in the read ahead, and at that moment spindle is not stopped but meanwhile tool change occurs, than this may be your issue; maybe you need to delay the read ahead, to be sure that M19 is triggered when spindle is stopped

... i dont know just an opinion ... kindly !