jepler/linuxcnc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
linuxcnc/tests/t0
History
Sebastian Kuzminsky d3e45d954f t0 tests: let introspection complete before continuing the test 
The t0 tests have failed intermittently since they were written in 2012.
The failures has always involved missing lines of output, corresponding
to the MDI of user-defined m-codes that did not complete.  The fix is
to wait for introspection to complete before moving on to the next part
of the test.

Signed-off-by: Sebastian Kuzminsky <seb@highlab.com>
2017-05-31 21:13:32 +00:00
..
nonrandom tests: avoid mdi queueing after gcodes that can fail 2015-08-09 12:53:54 -05:00
random-with-t0 tests: avoid mdi queueing after gcodes that can fail 2015-08-09 12:53:54 -05:00
random-without-t0 tests: avoid mdi queueing after gcodes that can fail 2015-08-09 12:53:54 -05:00
subs add tests for t0 handling 2013-02-08 09:05:10 -07:00
.gitignore add tests for t0 handling 2013-02-08 09:05:10 -07:00
core_sim.hal add tests for t0 handling 2013-02-08 09:05:10 -07:00
README add tests for t0 handling 2013-02-08 09:05:10 -07:00
shared-checkresult add tests for t0 handling 2013-02-08 09:05:10 -07:00
shared-test.sh t0 tests: let introspection complete before continuing the test 2017-05-31 21:13:32 +00:00

README 

nonrandom toolchanger:

    T0 is special and means "no tool".  T0 should not appear in the tool
    table, if T0 is defined there is ignored.


random toolchanger:

    T0 is a normal tool like any other, totally devoid of special meaning.
    In practice T0 is usually(?) used to track an empty pocket in the
    tool changer hardware.

    Tool number -1 is used to indicate "unknown tool".