Discussion:
Polling gcodes does not return active gcodes
(too old to reply)
Kurt Jacobson
2017-03-27 21:21:57 UTC
Permalink
Raw Message
Good evening all,

I am trying to get a list of the currently active gcodes using the Python
Interface in LCNC 2.7.8. As long as the interpreter is not executing,
stat.gcodes appears to return the active gcode values as expected. Ex: when
I issue a command via MDI the active gcodes update immediately. However, if
I try runing a program the gcodes update initially but then stop updating
until the program finishes. Ex: G0 and G91 are active. I start a program
and the gcodes initially update to G1 and G90, but will not update for the
remainder of the program, even though the program includes many switches
between G0 / G1 and G90 /G91. None of the other gcodes change either.

Is this expected behavior of stat.gcodes or is this a bug in the Python
Interface, or elsewhere?

I think this might be related to Norbert's issue here:
https://github.com/LinuxCNC/linuxcnc/issues/200

Thanks,
Kurt Jacobson
Chris Radek
2017-03-27 23:59:34 UTC
Permalink
Raw Message
Post by Kurt Jacobson
Is this expected behavior of stat.gcodes or is this a bug in the Python
Interface, or elsewhere?
This is expected, but is fixed in a branch that will be merged in
the future, called statetags.

That branch is really close to being mergeable after a lot of work
at fest last Oct/Nov, but it's still waiting on a few things. I
think it's mostly documented here:

https://github.com/LinuxCNC/linuxcnc/issues/134

You might want to try that branch if you're interested in helping
test or fix the remaining problems.

Chris
Kurt Jacobson
2017-03-28 00:34:18 UTC
Permalink
Raw Message
Post by Chris Radek
This is expected, but is fixed in a branch that will be merged in
the future, called statetags.
Excellent, just what I wanted to hear.
Post by Chris Radek
https://github.com/LinuxCNC/linuxcnc/issues/134
Good info there.

You might want to try that branch if you're interested in helping
Post by Chris Radek
test or fix the remaining problems.
I think I'll give it a try.

Chris
Thanks Chris!
Post by Chris Radek
Post by Kurt Jacobson
Is this expected behavior of stat.gcodes or is this a bug in the Python
Interface, or elsewhere?
This is expected, but is fixed in a branch that will be merged in
the future, called statetags.
That branch is really close to being mergeable after a lot of work
at fest last Oct/Nov, but it's still waiting on a few things. I
https://github.com/LinuxCNC/linuxcnc/issues/134
You might want to try that branch if you're interested in helping
test or fix the remaining problems.
Chris
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Emc-developers mailing list
https://lists.sourceforge.net/lists/listinfo/emc-developers
Loading...