Block Numbers

[BenK]

I would like to hear peoples thoughts an block numbers and how everyone uses them. I personally think they are a waste of memory and they make any program with goto statements much harder to work with.

[K2csq7]

Makes it easy to jump around in a program. We print out all programs so the operators can be spoon feed.

[robk]

The only places I use sequence #'s is at the beginning of every sequence (tool change) and not on every line. In my programs operators could use part counter to search for the sequence they need to go to (I provide that info in the tool list). I don't want the operators to start in the middle of the sequence so it works out great.

 

 

()

GOTO#3901 (USE PART COUNTER TO SEARCH FOR SEQUENCE NUMBERS)

G20 G69 G80 G40 G49 G17 G90 G94

G10.9 X0 (SET RAD. MODE)

G91 G28 Z0.

G28 X0. Y0.

G90

()

()

N1 T100 T69.1 M06

#3901 = #4114

G20 G69 G80 G40 G49 G17 G90 G94 G98

G10.9 X0 (SET RAD MODE)

G91 G28 Z0

G91 G28 X0 Y0

G90

()

()

/7G65 P9862 B1. T100 S3000

G4

#162000=0

G4

G65 P9862 B2. T2000 D2000 I[0.7500/2] E.005 S3000

G4

#162000=0

G4

G65 P9863 T100 H-.010 S3000

()

()

( Tool Name : T100_.750_ENDMILL)

()

(N1_REMOVE_LUGS)

()

()

G91 G28 Z0.0

()

(REMOVE LUGS)

()

M107 (B AXIS CLAMP)

M210 (C AXIS CLAMP)

M200 (C AXIS CONNECTION)

G90 G00 G53 B90.

G54.1 P23

C0.0

G90 G54.1 P23 X-7.269 Y-.9103 B90.

G97 S357 M3

G43 X-7.269 Y-.9103 Z 25.0 H100

G68 X0 Y0 Z0 I0 J1 K0 R90.

Z18.129

X-7.269 Y-.9103

M08

[spade117]

Standard for us is yes, but if a program is over the size limit to fit in the machine, I will remove them.

[Tony35]

yes but only on tool changes

[Pilot Plant Supervisor]

I use them. Sometimes I need to stop a program at quittin' time and re-start in the morning. Block #'s makes it much easier.

[rocheey1]

I would like to hear peoples thoughts an block numbers and how everyone uses them. I personally think they are a waist of memory and they make any program with goto statements much harder to work with.

 

How can you 'GOTO' anywehere without block numbers ?

 

Personally, I strip out all Block numbers, except I leave about 10 on, after each Operation ... Tool change or no.

[Bill Henderson]

We were just talking about this this morning here...

 

I always have left them in, but here for memory reasons they asked for them to be removed.

 

You see after they get the candles burning, squirrels turning the generators, and the woodstove to get the nip out of the shop I actually have to use those new fangled things called 1.44 diskettes to send my programs to the machine... and if I am lucky and they are not over 400k in most instances the machine can take it into memory.

 

Those are joyous times... when cutter comp can be anywhere in the program and its easy breazy to search and adjust.

[CADCAM3D5AXIS]

I only use them as a tool flag or sequence number in mill and lathe for search functions for ease of start restart of any sequences.

[Guyinthedesert]

yes but only on tool changes

 

+1

[MLS]

Yes, but only on tool changes/forced tool change sequences to check for cutter wear, etc.

[BenK]

How can you 'GOTO' anywehere without block numbers ?

 

I think they should only be used for goto's is what I was trying to say.

[Zoober]

Only on tool changes. Based on the tool number and how many tool changes for that tool

[Clarence L Cook]

For the lathe, at every tool change.

 

For the mill, at each change of work coordinate. I typically progressively move the part through the machine (ie. 4 ops, 4 pieces in machine, one part for each op). This has helped my operators quickly go to the correct operation as the parts finish through the machine. I start my sequence numbers at N2 and go up from there.

[BenK]

For those of you who have voted yes do you use them in every line?

[K2csq7]

I use them on every line.

For our lathes I have it set up so each cut gets an N number, cut 1 = N1, cut 2 = N2..... and so on.

All other lines in the lathe programs have normal N numbers (start at 200, increment by 2, it's rare we have a continuous program with more than 200 cuts.)

[Newbeeee™]

Yes on tool changes only. Our post calls N related to number of times the tool is used so:-

N0101 (is tool 1, 1st call)

N0103 (is tool 1, 3rd call)

N2004 (is tool 20, 4th call)

Easy to jump to and run a tool again.

[CADCAM3D5AXIS]

Same kind of format i follow for the lathes and also with multi offsets for tool control on close features. like T0101 T 0121

[35K chipper]

Yes on tool changes only. Our post calls N related to number of times the tool is used so:-

N0101 (is tool 1, 1st call)

N0103 (is tool 1, 3rd call)

N2004 (is tool 20, 4th call)

Easy to jump to and run a tool again.

 

Just like Newbeeee.

.

.

35k

[PeterM]

Ditto just like Newbee, line numbers are a waste of memory and a distraction when reading the program.

[Tim Johnson]

I use three sets of sequence numbers (that the post modifies).

 

1. tool changes

 

2 .correct pallet checks for starting in the middle of programs

 

3. toolpaths

[mayday]

no, only at toolchange

here's why, see the # of lines in this single sub program toolpath

[Tony35]

For those of you who have voted yes do you use them in every line?

 

no,

waste of memory

not needed

if the operator needs to pick up somewhere he will just add the N block

[gms1]

yes but only on tool changes

 

This is how I do it.

[Bruce Kanzelmeyer]

Thermwood controllers read label sets, gotos and calls: M80L1 (defines label 1) M81L1 (goto label 1) or M82L1 (calls label 1) M83 (return--jumps back to the line after a label call, ignored by goto) so line numbers unnecessary.