#linuxcnc-devel Logs

Oct 11 2019

02:26 AM linuxcnc-build: build #3349 of 1903.clang-wheezy-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1903.clang-wheezy-amd64/builds/3349 blamelist: Dewey Garrett <dgarrett@panix.com>
02:33 AM linuxcnc-build: build #6199 of 1306.rip-precise-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1306.rip-precise-amd64/builds/6199 blamelist: Dewey Garrett <dgarrett@panix.com>
02:35 AM linuxcnc-build: build #3348 of 1902.clang-wheezy-rtai-i386 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1902.clang-wheezy-rtai-i386/builds/3348 blamelist: Dewey Garrett <dgarrett@panix.com>
02:42 AM linuxcnc-build: build #3874 of 1402.rip-wheezy-rtpreempt-i386 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1402.rip-wheezy-rtpreempt-i386/builds/3874 blamelist: Dewey Garrett <dgarrett@panix.com>
02:44 AM linuxcnc-build: build #5415 of 1301.rip-precise-rtai-i386 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1301.rip-precise-rtai-i386/builds/5415 blamelist: Dewey Garrett <dgarrett@panix.com>
02:46 AM linuxcnc-build: build #6196 of 1300.rip-precise-i386 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1300.rip-precise-i386/builds/6196 blamelist: Dewey Garrett <dgarrett@panix.com>
02:47 AM linuxcnc-build: build #4358 of 1403.rip-wheezy-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1403.rip-wheezy-amd64/builds/4358 blamelist: Dewey Garrett <dgarrett@panix.com>
03:10 AM linuxcnc-build: build #2826 of 1530.rip-jessie-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1530.rip-jessie-rtpreempt-amd64/builds/2826 blamelist: Dewey Garrett <dgarrett@panix.com>
03:13 AM linuxcnc-build: build #2824 of 1500.rip-jessie-i386 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1500.rip-jessie-i386/builds/2824 blamelist: Dewey Garrett <dgarrett@panix.com>
03:16 AM linuxcnc-build: build #4561 of 1404.rip-wheezy-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1404.rip-wheezy-rtpreempt-amd64/builds/4561 blamelist: Dewey Garrett <dgarrett@panix.com>
03:19 AM linuxcnc-build: build #1214 of 1630.rip-stretch-rtpreempt-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1630.rip-stretch-rtpreempt-amd64/builds/1214 blamelist: Dewey Garrett <dgarrett@panix.com>
03:20 AM linuxcnc-build: build #2824 of 1510.rip-jessie-rtpreempt-i386 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1510.rip-jessie-rtpreempt-i386/builds/2824 blamelist: Dewey Garrett <dgarrett@panix.com>
03:20 AM linuxcnc-build: build #4028 of 1401.rip-wheezy-rtai-i386 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1401.rip-wheezy-rtai-i386/builds/4028 blamelist: Dewey Garrett <dgarrett@panix.com>
03:21 AM linuxcnc-build: build #2826 of 1520.rip-jessie-amd64 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1520.rip-jessie-amd64/builds/2826 blamelist: Dewey Garrett <dgarrett@panix.com>
03:22 AM linuxcnc-build: build #1214 of 1610.rip-stretch-rtpreempt-i386 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1610.rip-stretch-rtpreempt-i386/builds/1214 blamelist: Dewey Garrett <dgarrett@panix.com>
03:22 AM linuxcnc-build: build #6213 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/6213 blamelist: Dewey Garrett <dgarrett@panix.com>
07:29 PM jthornton: how difficult would it be to create a new G code based off of G0? G0.1 rapid but stop if probe trips and G1.1 feed but stop if probe trips
07:30 PM jthornton: for complex probe routines there may be rapid or fast feed moves and if the wrong parameters are used for stock size the probe could contact the part but now it does not stop just breaks the probe
07:32 PM pcw_mesa: I thought a unexpected probe hit always stopped
07:32 PM jthornton: not while running a program, only while jogging or a mdi move
07:33 PM jthornton: 2.7 - 2.9 have the same behavior
07:33 PM jthornton: also it will stop if using the keyboard to jog
07:35 PM pcw_mesa: seems like it should be always be a fault and stop motion
07:36 PM pcw_mesa: (if unexpected)
07:36 PM jthornton: I think it was nixed because of nuisance trips of machines with a probe in the tool changer and stuff like that
07:37 PM pcw_mesa: so you are thinking of gcode specifically for probing routines
07:37 PM jthornton: yea
07:37 PM jthornton: makes sense for some machines
07:37 PM pcw_mesa: you could mask the fault in hal
07:38 PM pcw_mesa: so you could probably cobble together the desired behaviour without a new code
07:39 PM jthornton: hmm, what are you thinking of?
07:40 PM pcw_mesa: probe causes a fault, and this is enabled by a digital out bit
07:41 PM jthornton: like a drive fault or something?
07:42 PM pcw_mesa: Not sure what the best way to stop is, maybe feedrate forced to 0?
07:42 PM jthornton: it would need to not interfere with the normal G38 probes
07:44 PM pcw_mesa: Right and be synchronized with each gcode line (but I think the digital out can do that)
07:45 PM pcw_mesa: Just thinking of a hack that simpler than a gcode change
07:46 PM jthornton: so a digital out to "arm" the error detection when not doing probe moves and then turn it off for a probe move?
07:47 PM jthornton: I'll have to cobble up something in the morning to test with, thanks for the idea
07:48 PM jthornton: went to the new Chinese restaurant and everything was so good I ate too much...
07:52 PM pcw_mesa: Yes arm for non-probe moves in the probe subroutine
07:52 PM pcw_mesa: (sorry my IRC client crashed) bbl
07:52 PM jthornton: ok
07:53 PM jthornton: I've about had it for the day
09:11 PM hazzy-m: for a while stop when probe tripped during jog was not working in master, I fixed it, so it can't have been very difficult
09:12 PM hazzy-m: will have to see if I can find the commit
10:28 PM cradek: Previously it would stop in those cases. But I found on a real machine with a real probe, no real program would actually run, there were false edges all the time, like bounce when rapiding off a probe touch. So I made the protection just be for jogging/homing when the danger is the highest.
10:28 PM cradek: you can try changing it back, but I bet it will be an unwanted change for most real machines.
10:30 PM cradek: 5c61bfe2d5aa
10:30 PM cradek: (sigh) 12 years ago
10:49 PM pcw_home: Maybe a motion pin to turn the option to stop on probe hits on or off?