Hello, That is a good point, but I am trying to avoid stopping and restarting the spindle and such. My spindle motor is a permanent magnet motor, and the controller does not support a flying start, so the spindle would have to stop and start for each part set. My spindle is also very high inertia, so stopping the spindle 2 times a minute would waste a few dozen KW of power each day (this machine has a 24 KW spindle motor). While I could write a specific HAL file to fix this, I really don't think that a modification to the HAL file should really be part of running an NC file. I can run a program with an infinite loop on my Fagor controller, and it works fine out of the box, so why do we need to mess with HAL to accomplish what other controllers do? I realize that my Fagor controller does not backplot, and there is a price there, but are we thinking clearly when we limit what NC code can run for this? The program is about 2500 lines with a loop around it, it runs in about 35 seconds. If I make enough iterations (2471) that the machine can run one day, Gremlin dies... -Neil Whelchel-
On Thu, Jun 23, 2016 at 6:23 PM, Dave Cole <[email protected]> wrote: > You can get around that by not doing infinite loops! ;-) > > Seriously, if you have something like Classic Ladder initiate the > program you can run as many parts as you want > and still have the Gcode terminate. That avoid the infinite loop > issue. The needed bits to trigger and monitor the program are all in Hal. > > I have a machine that has a PYVCP panel that is tied to Classic > Ladder. You enter the number of parts you want to run and push the go > button, > the the machine indexes sheets into the machine, cuts them, and indexes > the cut sheet out the other side. The operator loads sheets onto a > conveyor which feeds the machine. > > Dave > > > > On 6/23/2016 5:03 PM, Neil Whelchel wrote: > > Hello, > > When I do large production runs especially with multiple fixtures that > are > > used alternately, it is quite handy to put the work in an infinite loop. > > Gremlin on the other hand has an issue with this as it attempts to > backplot > > infinity. A comment can be added to the code to make Gremlin ignore it, > but > > it still throws non fatal Python errors. It would be really handy to have > > some sort of checking built into Gremlin to have it not crash when it > > encounters an infinite loop. Something as a simple loop counter that > breaks > > out of the loop after one iteration if all parameters are the same > between > > any previous pass? Or how about a comment in the NC code that tells > gremlin > > that a loop is infinite and to only parse it once or N number of times? > > Any thoughts or reasons as to why this might be a bad idea, either from > the > > standpoint of patching Gremlin or writing NC files with infinite loops... > > -Neil Whelchel- > > > ------------------------------------------------------------------------------ > > Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San > > Francisco, CA to explore cutting-edge tech and listen to tech luminaries > > present their vision of the future. This family event has something for > > everyone, including kids. Get more information and register today. > > http://sdm.link/attshape > > _______________________________________________ > > Emc-developers mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/emc-developers > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > > > > ------------------------------------------------------------------------------ > Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San > Francisco, CA to explore cutting-edge tech and listen to tech luminaries > present their vision of the future. This family event has something for > everyone, including kids. Get more information and register today. > http://sdm.link/attshape > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers > ------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
