Re: [Emc-developers] strange interpreter results - was [iocontrol.0.tool-prepare]
Hi Stuart, thank you for your attention! On Dienstag, 19. Mai 2020, 17:42:39 CEST Stuart Stevenson wrote: > The stop spindle command on line 20 seems correct to me as stopping and > starting the spindle should be part of the total tool change routine and > come between the start change and end change commands. Ok, that makes sense. > As for the 21 and 5 commands I can only guess. It is possible the 21 and 5 > are pocket numbers to handle a random tool change sequence. Hm, that can't be true. As far as I understand random tool changers, random toolchanging only works with a gripper, that can hold two tools at the same time. Result is then, that the tool from spindle goes into the slot of the tool, that now goes into the spindle. That means, that only one pocket is used on toolchange. Well, a well designed toolchanger software would reserve two slots for the gripper, so that each tool has a pocket at any time and can't get lost in case of hardware or user failure. But those gripper-slots should be different from the slots that hold tools. When I start linuxcnc, axis says: no tool loaded. So no pocket to occupy on tool change. ... and from tool table: tool 21 is in slot 5 and tool 30 is in slot 21. Neither tool 21 nor tool 31 are mentioned in gcode file, so a random toolchanger can't use these slots for whatever reason. > Shrugs shoulders So we are two :) Thanks for your reply. cheers Reinhard ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
[Emc-developers] Actually i use 2.9 ... problem at launch with estop activated ...
First time to see these issue when launch my machine with axis gui on rip-install with estop activated, axis gui freeze. I'm on ubuntu 18.04 rip-install. I see these issue on 2.9, 2,8 version but no issue using 2.7. I use a mesa board 7i77. Where file can search for find and try to solve these problem? regards bkt ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Re: [Emc-developers] strange interpreter results - was [iocontrol.0.tool-prepare]
The stop spindle command on line 20 seems correct to me as stopping and starting the spindle should be part of the total tool change routine and come between the start change and end change commands. As for the 21 and 5 commands I can only guess. It is possible the 21 and 5 are pocket numbers to handle a random tool change sequence. Shrugs shoulders Stuart On Tue, May 19, 2020, 8:54 AM Reinhard wrote: > Hi, > > I digged a bit deeper to understand what happens, but result is, the > deeper I > dig, the less I understand. > > I added N-words to each line to be able to link (in my mind) interpreter > output to each gcode-line. > > Sample is now like this (obvious motion lines ommited): > N005 G17 G21 G64 > ( Tasche1 ) > ( T4 : 12.0 HPC ) > N010 G40 G80 > N015 T4 > N020 M6 > N025 G0 G90 G54 X50 Y70 S4750 M3 T23 > N030 G43 H4 Z2 M8 > N035 G1 Z-9 F300 > ... > N090 G1 X38.523 Y55.077 > N095 G1 X50 Y70 > N100 G0 Z150 M5 > N105 M9 > N110 M6 > > corresponding tool.tbl is this: > T4 P4 Z56.4 D12 ;12,0mm hpc 4-schneider > T23 P7 Z50D10 ;10,00mm 4 schneiden fräser > T24 P8 Z50D12 ;12,00mm 4 schneiden fräser > > ... there exists no tool entry with number 5 ! > > ... and here's the output from interpreter, started standalone with > gcode-file > as commandline-parameter. First executed option 3 - read tool file, then > start > interpreting. > >10 N005 SELECT_PLANE(CANON_PLANE_XY) >11 N005 USE_LENGTH_UNITS(CANON_UNITS_MM) >12 N005 SET_MOTION_CONTROL_MODE(CANON_CONTINUOUS, 0.00) >13 N005 SET_NAIVECAM_TOLERANCE(0.) >14 N. COMMENT("Tasche1 ") >15 N. COMMENT("T4 : 12.0 HPC ") >16 N010 COMMENT("interpreter: cutter radius compensation off") >17 N010 COMMENT("interpreter: motion mode set to none") >18 N015 SELECT_TOOL(4) >19 N020 START_CHANGE() >20 N020 STOP_SPINDLE_TURNING(0) >21 N020 CHANGE_TOOL(21) >22 N025 SET_SPINDLE_SPEED(0, 4750.) >23 N025 SELECT_TOOL(23) >24 N025 START_SPINDLE_CLOCKWISE(0) >25 N025 COMMENT("interpreter: continuing to use same coordinate > system") >26 N025 STRAIGHT_TRAVERSE(50., 70., 0., 0., 0., > 0.) >27 N030 FLOOD_ON() >28 N030 USE_TOOL_LENGTH_OFFSET(0. 0. 1432.5600, 0. 0. > 0., 0. 0. 0.) >29 N030 STRAIGHT_TRAVERSE(50., 70., 2., 0., 0., > 0.) >30 N035 SET_FEED_RATE(300.) >44 N095 STRAIGHT_FEED(50., 70., -9., 0., 0., > 0.) >45 N100 STOP_SPINDLE_TURNING(0) >46 N100 STRAIGHT_TRAVERSE(50., 70., 150., 0., 0., > 0.) >47 N105 MIST_OFF() >48 N105 FLOOD_OFF() >49 N110 START_CHANGE() >50 N110 STOP_SPINDLE_TURNING(0) >51 N110 CHANGE_TOOL(5) > > I guess, that the first number of each line is the sequence of command > execution. > Line 18 is as expected, but line 20 should go before line 19 ... > Don't know, but from my point of view the spindle should stop, before > initiating any tool-change process. > > Line 21 looks strange to me. Where does the 21 come from? > In the whole file no tool #21 is mentioned. > > Line 23 shows, that the tool selection has been recognized. But is not > sent to > atc-pin (yes, I broke the cut-loop). > > Line 25 shows the tip is at Z0. > Line 28 applies the tool length offset - but not the offset from tool.tbl > - no > idea, where that numbers come from. In my understanding, G43 H4 means, > that > the tool-length from tool #4 should be taken. That length is 56.4 (with > dot, > not with comma). So if the tip was at Z0, it should be at ±56.4 - as G21 > has > been commanded. > > Then at line 51 a tool #5 will be changed. I don't have a tool #5 in > tool.tbl > and no T5 in the whole gcode file. > > Please gimme a hand to understand the whole story. > > cheers Reinhard > > > > > > ___ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Re: [Emc-developers] strange interpreter results - was [iocontrol.0.tool-prepare]
Hi, I digged a bit deeper to understand what happens, but result is, the deeper I dig, the less I understand. I added N-words to each line to be able to link (in my mind) interpreter output to each gcode-line. Sample is now like this (obvious motion lines ommited): N005 G17 G21 G64 ( Tasche1 ) ( T4 : 12.0 HPC ) N010 G40 G80 N015 T4 N020 M6 N025 G0 G90 G54 X50 Y70 S4750 M3 T23 N030 G43 H4 Z2 M8 N035 G1 Z-9 F300 ... N090 G1 X38.523 Y55.077 N095 G1 X50 Y70 N100 G0 Z150 M5 N105 M9 N110 M6 corresponding tool.tbl is this: T4 P4 Z56.4 D12 ;12,0mm hpc 4-schneider T23 P7 Z50D10 ;10,00mm 4 schneiden fräser T24 P8 Z50D12 ;12,00mm 4 schneiden fräser ... there exists no tool entry with number 5 ! ... and here's the output from interpreter, started standalone with gcode-file as commandline-parameter. First executed option 3 - read tool file, then start interpreting. 10 N005 SELECT_PLANE(CANON_PLANE_XY) 11 N005 USE_LENGTH_UNITS(CANON_UNITS_MM) 12 N005 SET_MOTION_CONTROL_MODE(CANON_CONTINUOUS, 0.00) 13 N005 SET_NAIVECAM_TOLERANCE(0.) 14 N. COMMENT("Tasche1 ") 15 N. COMMENT("T4 : 12.0 HPC ") 16 N010 COMMENT("interpreter: cutter radius compensation off") 17 N010 COMMENT("interpreter: motion mode set to none") 18 N015 SELECT_TOOL(4) 19 N020 START_CHANGE() 20 N020 STOP_SPINDLE_TURNING(0) 21 N020 CHANGE_TOOL(21) 22 N025 SET_SPINDLE_SPEED(0, 4750.) 23 N025 SELECT_TOOL(23) 24 N025 START_SPINDLE_CLOCKWISE(0) 25 N025 COMMENT("interpreter: continuing to use same coordinate system") 26 N025 STRAIGHT_TRAVERSE(50., 70., 0., 0., 0., 0.) 27 N030 FLOOD_ON() 28 N030 USE_TOOL_LENGTH_OFFSET(0. 0. 1432.5600, 0. 0. 0., 0. 0. 0.) 29 N030 STRAIGHT_TRAVERSE(50., 70., 2., 0., 0., 0.) 30 N035 SET_FEED_RATE(300.) 44 N095 STRAIGHT_FEED(50., 70., -9., 0., 0., 0.) 45 N100 STOP_SPINDLE_TURNING(0) 46 N100 STRAIGHT_TRAVERSE(50., 70., 150., 0., 0., 0.) 47 N105 MIST_OFF() 48 N105 FLOOD_OFF() 49 N110 START_CHANGE() 50 N110 STOP_SPINDLE_TURNING(0) 51 N110 CHANGE_TOOL(5) I guess, that the first number of each line is the sequence of command execution. Line 18 is as expected, but line 20 should go before line 19 ... Don't know, but from my point of view the spindle should stop, before initiating any tool-change process. Line 21 looks strange to me. Where does the 21 come from? In the whole file no tool #21 is mentioned. Line 23 shows, that the tool selection has been recognized. But is not sent to atc-pin (yes, I broke the cut-loop). Line 25 shows the tip is at Z0. Line 28 applies the tool length offset - but not the offset from tool.tbl - no idea, where that numbers come from. In my understanding, G43 H4 means, that the tool-length from tool #4 should be taken. That length is 56.4 (with dot, not with comma). So if the tip was at Z0, it should be at ±56.4 - as G21 has been commanded. Then at line 51 a tool #5 will be changed. I don't have a tool #5 in tool.tbl and no T5 in the whole gcode file. Please gimme a hand to understand the whole story. cheers Reinhard ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers