How to manually jump around in a running program

[laka]

Most machines i've ran will let you manually move around to different lines in a program once the previous line has been completed with Single Block on. Can't seem to figure this out on our Haas.

[Geof]

Never heard of it and I have had lots of Haas machines for many years.

I must say it sounds like a strange requirement. You mean you can jump ahead or back in a running program? What happens about all the operations in the blocks you have jumped past?

[HuFlungDung]

Setting 36 'Program restart' affects the way the control restarts a program. When ON, the entire program is re-read up to the point where you choose to begin. This simply ensures that all necessary positioning moves and miscellaneous functions have been properly executed.

Now, if you like to live in the danger zone, turn that setting OFF and be wary of what happens if the current tool begins to cut, perhaps not knowing what work offset should be used, what the tool diameter is (if comp was used), what the tool length is (if it was altered). Personally, I'd always begin from a tool change if I had this setting off, because I don't assume too much modality from one operation to the next. But there may be circumstances where you could use direct execution to your advantage. But I'd suggest that setting 36 should be turned back ON for day to day use, especially if more than one guy is running the machine, because we all carry around our assumptions

[laka]

Perfect, thanks!


Geof: This is actually very handy for many reasons. Say you bust a tool mid cycle and have to load a new one, you wouldn't necessarily want to re-run the whole program cutting air to get to where you had left of.

I used to use it many times when running a long cycle and stopping the machine at end of the day and starting back at the line number I left at. On our Yasnac machine, I would run the tool change line all the way up to the G43 line, and just page down through the program to where I wanted to start. You definately need to be careful, but it is a handy feature.

[Geof]

You phrased your question poorly, you don't want to move around you want to move down to a start point somewhere in the program. As HFD describes,yes, Haas does that. The one time Program Restart can give problems is when you are using G101 to mirror axes. Starting immediately below the G101 line can cause bad things to happen.

[double a-ron]

I leave 36 off and start from a tool change. Unless I need to start in the middle of a series of g83 holes.

[Black08Chally]

I'll put a GOTO666 in after all the start up lines, then an N666 where I want to pick up.....Make sure your initial Z is high enough to clear any XY repositions as it goes from the 'GOTO' to line 666. You probably will have to put a feed rate in on your first linear move after the 666 as well as sometimes it alarms out if you are relying on the first one after the startup lines.

[WallyL7]

Originally Posted by Black08Chally I'll put a GOTO666 in after all the start up lines, then an N666 where I want to pick up.....Make sure your initial Z is high enough to clear any XY repositions as it goes from the 'GOTO' to line 666. You probably will have to put a feed rate in on your first linear move after the 666 as well as sometimes it alarms out if you are relying on the first one after the startup lines.

That sounds pretty sketchy. So, you just add in a N666 if you need to start on a specific line? then you erase it when your done? Setting 36 takes care of all of your adding GOTO stuff to every single program since it reads the program from the beginning...Interesting you chose the number of the beast though!!lol!


however, I'm with Double A-ron on this. I only turn it "on" if I have a legitimate reason to start in the middle of a tool. Otherwise, I start at the tool call, and all the modals are there with feedrates, etc...Leaving it on makes me crazy with all the extra time waiting for it to read the program, go to the previous position, or even load the last tool in

[Black08Chally]

Originally Posted by WallyL7 That sounds pretty sketchy. So, you just add in a N666 if you need to start on a specific line? then you erase it when your done? Setting 36 takes care of all of your adding GOTO stuff to every single program since it reads the program from the beginning...Interesting you chose the number of the beast though!!lol! however, I'm with Double A-ron on this. I only turn it "on" if I have a legitimate reason to start in the middle of a tool. Otherwise, I start at the tool call, and all the modals are there with feedrates, etc...Leaving it on makes me crazy with all the extra time waiting for it to read the program, go to the previous position, or even load the last tool in

I always use 666 since I can easily type 'N666' in edit mode, then hit arrow down and find if it is in the program. If I get a not found then I know if I forget to remove the 'GOTO666' line it will alarm out with 'GOTO P OR N LINE NOT FOUND' or something like that. It allows me to choose exactly where to run up to, skip ahead to and and remove when I'm done. Since 666 means evil, I don't let it exist in a program, and if I do find it, I investigate why it was put there.

[Geof]

Originally Posted by WallyL7 That sounds pretty sketchy. ...

Could be less sketchy than simply turning 36 off because you don't want to wait for the machine to scan the program.

If you are reading in offsets and tool dias from G10 lines at the head of the program and 36 if off they will not be picked up if you scroll down and start anywhere below the G10 lines.

If you put the GOTO below the G10 lines they will be picked up before the jump.

Yes, No? Do I have it right or wrong?

I keep 36 ON, I am a patient and cautious guy.

[WallyL7]

Originally Posted by Geof Could be less sketchy than simply turning 36 off because you don't want to wait for the machine to scan the program. If you are reading in offsets and tool dias from G10 lines at the head of the program and 36 if off they will not be picked up if you scroll down and start anywhere below the G10 lines. If you put the GOTO below the G10 lines they will be picked up before the jump. Yes, No? Do I have it right or wrong? I keep 36 ON, I am a patient and cautious guy.

How is that method less sketchy than setting 36? It certainly is faster to turn it on and start from mid cycle when you need to than to ALWAYS add GOTO lines. Personally, it is a rare thing for me to have to mid cycle start, so for me to add it to every program would just add a lot of extra time...and to add it to even one program would take more time than turning on 36 and waiting for the machine to read through the program...just sayin.


Don't misunderstand, I get that we all have our little nuances and tastes regarding how we do things. I think if this works great for him, then he should run with it, but, I think the majority of users are better off with setting 36.



There is less room for error with 36. It always homes the -Z- axis first (which he even said you need to make sure with his method that you have enough -Z- clearance first - potential disaster if you don't)...So, being patient and cautious is only more necessary with that system.

I understand you are a patient and cautious guy, Geof, but don't mistake my - - - not ALWAYS wanting to wait for the control to read through the program when I am simply running each tool one at a time - - - for not being cautious.


You remember I ran your program on my machine a while back

[Geof]

I think the meaning I intended didn't come through in what I wrote so I will do it differently.

In declining order of safety (the way I rate them):

Setting 36 ON is safest and slowest; painfully slow if you have a load of 38 parts and want to restart the last tool on the last part.

Putting in a line number and a GOTO, with the GOTO after any essential commands that have to be read at the top of the program such as G10 commands. I would intermediate in safety and slowness because you have to do some editing and then remove it.

Setting 36 OFF is the fastest and riskiest if you forget you have stuff that must be read ahead of your start point. Also risky to have the machine in regular use with Setting 36 OF,F just in case you where looking at something down in the body of the program and then forget to hit Reset before Cycle Start.

Incidentally has anyone found that sometimes in a Restart on a program with subroutines the machine will hang up on a subroutine call.?