Search the Community
Showing results for tags 'buffer'.
Found 4 results
-
Hi guys, We are using a 4 digit tool number in our tool library that works great for the Makino mills we have. We are trying to standardize this process over to some Hurcos. The Makinos use H1 D1 for offsets because we use the tool management. The limitation on the Hurcos is that they only have 199 registers for diameter offsets, and apparently the restisters cannot be re-numbered. So regardless of the tool number, the diameter offset needs to use 1-199. I have a buffer that extracts tool numbers from the pwrtt$ postblock. This is what the tool table looks like at the beginning of the program: ( T3293 ( GARR VRX - 27763 0.5 Bull-Nosed Endmill )) ( T3299 ( GARR VRX - 61374 0.5 Flat Endmill )) ( T5200 ( HARVEY - 68062-C3 0.0625 Roundover Tool )) ( T5415 ( INTERNAL TOOL - 64-2880-C 0.375 Chamfer Mill )) ( T5806 ( HARVEY - 43362-C3 0.375 Slotting Tool or Saw )) Here is a sample array: 0. 3293. 1. 0. 3299. 2. 0. 5200. 3. 0. 5415. 4. 0. 5806. 5. The second column represents the tool number, the third represents the initial order in which the tools run. The problem is that sometimes tools repeat after others have already run. How can I look up the second column and match it to the third so that any time T5200 comes up in the program, it will always use offset 3? Thanks in advance
-
Helloo, I'm new to this forum, but i have got alot of good info from here so thank you all! Now i'm facing a problem that our Okuma M560 with OSP-P300 and it's .LIB file... I wanted to add G116 logic to our machine that controls the toolchange that we dont have to manually enter M64 each time wrong tool is prepared and we want to start a program. We are getting the 5223 error that says buffer overflow... We are using .lib file that allready has tool measurement macros in it and if i increase the size of the file by adding just a coupe of lines, then we get this error... So my question is. Is there a way to increase buffer size (at the moment its only 5Kb?) or can i rewrite the .lib file that it is selecting automatically a smaller program that contains CALL or GOTO-s to another program in MD1 directory? Thanks for your help!
-
I currently have all my vertical mill posts (Mazak, Haas, Fanuc) setup to post sequence numbers only at "operation comments" using the pcomment2 block pcomment2 #Output Comment from manual entry scomm$ = ucase (scomm$) if gcode$ = 1005, sopen_prn, scomm$, sclose_prn, e$ #Manual entry - as comment if gcode$ = 1006, scomm$, e$ #Manual entry - as code if gcode$ = 1007, sopen_prn, scomm$, sclose_prn #Manual entry - as comment with move NO e$ if gcode$ = 1026, scomm$ #Manual entry - as code with move NO e$ if gcode$ = 1008, n$, sopen_prn, no_spc$, scomm$, no_spc$, sclose_prn, e$ #Operation comment if gcode$ = 1051, sopen_prn, scomm$, sclose_prn, e$ #Machine name if gcode$ = 1052, sopen_prn, scomm$, sclose_prn, e$ #Group comment if gcode$ = 1053, sopen_prn, scomm$, sclose_prn, e$ #Group name if gcode$ = 1054, sopen_prn, scomm$, sclose_prn, e$ #File Descriptor this is the only place that sequence numbers are in my programs ex: N10 (SKIM FACE OF STOCK, +.002 FOR FLY CUTTER) T01 M06 (1.5 FACE MILL | H01) G00 G90 G56 X16.025 Y-2.1249 S3500 M03 Z2. T6 I always put comments on every single operation, this way the operators not only know whats going on in every section of the program, but can quickly search and start at the relevant section. however, i would like to create, if possible, a buffer which sends all of these comments with their sequence numbers to a .txt file that i can print out as a reference with the job setup paperwork. Is this going to be more complicated than its worth?
-
Good Afternoon folks, I am so close I can taste victory, but my last tools buffer information is coming out twice. (PROGRAMMER: G) (WORK OFFSET) G10 L2 P1 X0.0 Z3.6 (TOOL LIST) (TOOL - 1 OFFSET - 1 TOOL = OD ROUGH RIGHT - 80 DEG.) (TOOL - 12 OFFSET - 12 TOOL = OD 55 DEG RIGHT ) (TOOL OFFSETS) DEBUG*******START OF OUTPUT*******DEBUG rc5 1. size5 9. G10 L10 P1 R2.591 G10 L12 P1 R1.367 DEBUG*******END OF OUTPUT*******DEBUG rc5 4. size5 9. DEBUG*******START OF OUTPUT*******DEBUG rc5 4. size5 9. G10 L10 P12 R3.587 G10 L12 P12 R3.249 DEBUG*******END OF OUTPUT*******DEBUG rc5 7. size5 9. DEBUG*******START OF OUTPUT*******DEBUG rc5 7. size5 9. G10 L10 P12 R3.587 G10 L12 P12 R3.249 DEBUG*******END OF OUTPUT*******DEBUG rc5 10. size5 9. M00 Here is my Buffer that I created: # -------------------------------------------------------------------------- #Buffer 5, testing to store misc real values wc5 : 1 #Initial count for write buffer 5 rc5 : 1 #Initial count for read buffer 5 size5 : 0 #Buffer 5 size g10z : 1 #Saved mr9$ value g10x : 1 #Saved mr10$ value gten_tool : 1 #Tool number capture fbuf 5 0 3 0 0 # -------------------------------------------------------------------------- Here is my pwrtt post block with my added code see (#STEVE ADDED): pwrtt$ #Buffer toolchange information, tooltable = 3 calls on 1003 if gcode$ = 1001, psetup pcut_cctyp if opcode$=104 | opcode$=105 | opcode$=three | opcode$=16, cc_pos$ = zero if gcode$ <> 1001, plast_recd pcur_recd if gcode$ <> 1003, cc_pos$ = zero !opcode$, !tool_op$ if gcode$ = 1003, [ size1 = rbuf (one, zero) rc1 = one if rc1 < size1, preadcur_nxt if cc_1013$ = zero, cc_pos$ = zero ] mr9$ = wbuf(5,wc5) #STEVE ADDED mr10$ = wbuf(5,wc5) #STEVE ADDED t$ = wbuf(5,wc5) #STEVE ADDED #if you want repetitive tool output, keep the abs( ) in ptooltable and remove the >= t$ from the pwrtt call to this block if (tool_info = 2 | tool_info = 3) & gcode$ <> 1003 & op_id$ <> last_op_id & t$ >= 0, ptooltable last_op_id = op_id$ Here is my output postblock that is called from LSOF in this case: ptooloffsets # Output of Tool Offsets for G10 rc5 = 1 size5 = rbuf(5,0) " ", e$ "(TOOL OFFSETS)", e$ while rc5 <= size5, [ "DEBUG*******START OF OUTPUT*******DEBUG", *rc5, *size5, e$ #used for debugging g10z = rbuf(5,rc5) g10x = rbuf(5,rc5) gten_tool = rbuf(5,rc5) "G10 L10", *gten_tool, *g10z, e$ "G10 L12", *gten_tool, *g10x, e$ "DEBUG*******END OF OUTPUT*******DEBUG", *rc5, *size5, e$ #used for debugging ] " ", e$ What kind of trap do I need to build to keep the (in this case) second tools information from coming out a second time?
