Andy, This is the output, and while there is no guarantee and apparently no documentation :-(, this leads me to believe the active g-codes are ordered: … (0, 800, -1, 180, 400, 200, 900, 940, 540, 490, 990, 640, -1, 970, 911, 80) (0, 800, -1, 180, 400, 200, 900, 940, 540, 490, 990, 640, -1, 970, 911, 80) (0, 800, -1, 180, 400, 200, 900, 940, 540, 490, 990, 640, -1, 970, 911, 80) (0, 800, -1, 180, 400, 200, 900, 940, 540, 490, 990, 640, -1, 970, 911, 80) (0, 800, -1, 180, 400, 200, 900, 940, 540, 490, 990, 640, -1, 970, 911, 80) (0, 800, -1, 180, 400, 200, 900, 940, 540, 490, 990, 640, -1, 970, 911, 80) (0, 800, -1, 180, 400, 200, 900, 940, 540, 490, 990, 640, -1, 970, 911, 80) …
-Tom > On Sep 14, 2015, at 4:30 AM, andy pugh <bodge...@gmail.com> wrote: > I don't know for sure, but I suspect that the stat attribute returns > an unordered list of active G-codes. I wouldn't rely on looking in a > particular position, you probably need to look at all the values to > see if any are "80". I imagine that this is only a single expression > in Python. > <Google> > if 70 in s.gcodes: ------------------------------------------------------------------------------ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
