Need Help!- Problem with move.

[alejoresmo]

Dear sir's.
In this moments, I'm installing the MC 4VA okuma with OSP 5020 Control, when I move the machine in manual mode, the machine move Ok in all axes, but when I program the machine in mode MDI the machine don't move, and I search the program in mode EDIT change to mode AUTO, I push cycle start but the machine don't move, in move MDI I can turn on the spindle, but I can't change the tool, the unique way for change tool I have to go the axes Z to the point of change and change the tool manually, but if I move the "Z" axes the ATC don't work, I program the machine in mode MDI, the next way.

G00 X100.;
I push WR
and push Cycle Start " Machine Don't move"

I program the tool change in mode MDI, the next way.

M6 T01;
I push WR
and push Cycle Start
- is the machine is in tool position the atc work, but if the position if axes "Z" is in other point the ATC don't work.

Please help me

[Frazprg]

Im not familiar with that model but Ill asume its a mill. On the okumas I normaly call a tool then specify an index. This is because when i call a tool in a program i prep the next tool then index when i need the next tool

so t01 write m06 write then start

I dont know if your familiar with okuma controls but normaly calling m06 will move to atc automaticly so make shure you move your tools away from work to a safe travel possition before calling it. Its also common on the machines i use that common variables like absolute or increment speeds and limits are defined in the current or last known loaded program so you dont have to redefine these when you want to mdi. Ive never cleared the memory to scratch before trying to manually imput data. I would suggest writing a simple default program with a simple layout defining max rpms (g50 s500) and possibly possitioning limits like the chuck barrier calls on the lathes.

I must admit i hardly ever think of these things because we have defaults programs made out that we imput data into to write our programs.

[alejoresmo]

dear franz,

thank for your information, but the problem is that the machine don't move the axes in the mode MDI and AUTO, because, I call the program in mode EDIT, I change the mode to AUTO, I push Cycle start and the machine turn on the spindle but when have to read the block to move the program stop. and I don't know, I have a question, can I program a move in mode MDI, for example G00 X100. Y100: and later push cycle start and the machine go to this point..

Thanks. for all and I'm sorry for me english.

[Superman]

make sure all your switches are turned off

"Dry Run" could be ON with the over-ride knob turned down to zero
"STM lock" is OFF ( because you can start your spindle )

Dry run I suspect is the problem, when running a line of code, check "Actual Position" , do any axes move slowly as the over-ride knob cannot go to zero, scale is 1~4000mm/min (0.04~160"/min)

[Frazprg]

Wow I recently had this problem (a few days ago) on a osp 5000L.
The problem I had was on the hardware side with the relays. The machine in question had a bad relay on CRSPC. The machine could move manually and start the spindle but when you ran code to move the turret it wouldnt move unless you went back and flicked the relay. Replaced with an omiron relay and all is well. Maybe similar to your issue.

Dont ask what the make on the relay is I had a case of em stashed away.

[Algirdas]

any error message?
did You checked condition of ATC?

[Mohawk72]

Did the problem go away?

One thing I was going to mention is the Controls of that era.

OSP 5020 and later had a control Machine lock.

if the bulb behind this button is out you will never know you are locked, as the control is working right and no alarm will show up.

If I remember right you had to push the Inter lock soft key hold it and then push machine lock. and repeat to unlock machine.

Then you were able to run the program to prove code without ANY axis moving.

The later controls have this feature too. Both Mills and Lathes.

Good Luck

Mohawk

[Algirdas]

yes, of course - OSP shows "work" on the screen, but no movement of mechanical parts while machine locked.
But in this case is easy to see coordinates runing on the screen, response to speed override ...