#linuxcnc-devel Logs

May 07 2023

12:33 AM linuxcnc-build2: Build [#770](http://buildbot2.highlab.com/buildbot/#builders/8/builds/770) of `30-dsc-uspace.debian-12-bookworm` 4failed.
03:31 AM linuxcnc-build2: Build [#840](http://buildbot2.highlab.com/buildbot/#builders/7/builds/840) of `10-rip.debian-11-bullseye-rtpreempt-amd64` 4failed.
03:33 AM linuxcnc-build2: Build [#840](http://buildbot2.highlab.com/buildbot/#builders/14/builds/840) of `10-rip.debian-10-buster-rtpreempt-amd64` 4failed.
03:56 AM -!- #linuxcnc-devel mode set to +v by ChanServ
03:59 AM linuxcnc-build2: Build [#841](http://buildbot2.highlab.com/buildbot/#builders/14/builds/841) of `10-rip.debian-10-buster-rtpreempt-amd64` 8completed with warnings.
04:47 AM linuxcnc-build2: Build [#842](http://buildbot2.highlab.com/buildbot/#builders/7/builds/842) of `10-rip.debian-11-bullseye-rtpreempt-amd64` 8completed with warnings.
05:13 AM linuxcnc-build2: Build [#771](http://buildbot2.highlab.com/buildbot/#builders/8/builds/771) of `30-dsc-uspace.debian-12-bookworm` 8completed with warnings.
05:20 AM linuxcnc-build2: Build [#898](http://buildbot2.highlab.com/buildbot/#builders/13/builds/898) of `00-checkin` 3completed successfully.
10:02 AM linuxcnc-build: build #2742 of 4041.deb-buster-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4041.deb-buster-rtpreempt-amd64/builds/2742 blamelist: ALatSMT <63883285+ALatSMT@users.noreply.github.com>, Rene Hopf <renehopf@mac.com>, Steffen Moeller <moeller@debian.org>, Hans Unzner
10:02 AM linuxcnc-build: <hansunzner@gmail.com>
11:38 AM linuxcnc-build: build #3512 of 1640.rip-buster-rtpreempt-amd64 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1640.rip-buster-rtpreempt-amd64/builds/3512 blamelist: CMorley <chrisinnanaimo@hotmail.com>
11:38 AM linuxcnc-build: build #9926 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/9926 blamelist: CMorley <chrisinnanaimo@hotmail.com>
11:38 AM linuxcnc-build: build #9927 of 0000.checkin is complete: Failure [4failed fetch branch to local git repo] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/9927 blamelist: Sebastian Kuzminsky <seb@highlab.com>
11:46 AM linuxcnc-build2: Build [#774](http://buildbot2.highlab.com/buildbot/#builders/8/builds/774) of `30-dsc-uspace.debian-12-bookworm` 4failed.
11:53 AM linuxcnc-build2: Build [#901](http://buildbot2.highlab.com/buildbot/#builders/13/builds/901) of `00-checkin` 4failed.
01:01 PM linuxcnc-build: build #2888 of 3304.dsc-buster-rtpreempt is complete: Failure [4failed shell] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/3304.dsc-buster-rtpreempt/builds/2888 blamelist: andypugh <andy@bodgesoc.org>
01:22 PM roguish[m]: just out............... https://docs.python.org/3.12/whatsnew/3.12.html
02:31 PM linuxcnc-build: build #9928 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/9928 blamelist: andypugh <andy@bodgesoc.org>
03:16 PM linuxcnc-build2: Build [#847](http://buildbot2.highlab.com/buildbot/#builders/7/builds/847) of `10-rip.debian-11-bullseye-rtpreempt-amd64` 4failed.
03:17 PM linuxcnc-build2: Build [#847](http://buildbot2.highlab.com/buildbot/#builders/14/builds/847) of `10-rip.debian-10-buster-rtpreempt-amd64` 4failed.
03:29 PM andypugh: So, how can G-code determine if the machine uits are mm or in?
03:29 PM andypugh: I think that it is tricky.
03:43 PM linuxcnc-build2: Build [#848](http://buildbot2.highlab.com/buildbot/#builders/14/builds/848) of `10-rip.debian-10-buster-rtpreempt-amd64` 8completed with warnings.
03:45 PM linuxcnc-build2: Build [#848](http://buildbot2.highlab.com/buildbot/#builders/7/builds/848) of `10-rip.debian-11-bullseye-rtpreempt-amd64` 8completed with warnings.
03:47 PM seb_kuzminsky: andypugh: you could look at #<_metric> and #<_imperial>, http://linuxcnc.org/docs/2.9/html/gcode/overview.html#gcode:predefined-named-parameters
03:48 PM andypugh: Those tell you if G20 or G21 are active?
03:48 PM andypugh: So don’t really answer the question (ie, of what units the probe-screen or tool table numbers are in)
03:52 PM linuxcnc-build2: Build [#776](http://buildbot2.highlab.com/buildbot/#builders/8/builds/776) of `30-dsc-uspace.debian-12-bookworm` 8completed with warnings.
03:59 PM andypugh: pere: I bought the tickets
03:59 PM linuxcnc-build2: Build [#904](http://buildbot2.highlab.com/buildbot/#builders/13/builds/904) of `00-checkin` 3completed successfully.
04:01 PM -!- #linuxcnc-devel mode set to +v by ChanServ
04:25 PM seb_kuzminsky: andypugh: ah, right
04:26 PM rene-dev5: andypugh what are you trying to do?
04:26 PM andypugh: Figure out that not-really-linuxcnc probe screen problem.
04:27 PM rene-dev5: I have crashed a very expensive probe once, due to some default being in inches.
05:10 PM roguish[m]: andypugh: what problem exactly is that? reference?
05:10 PM roguish[m]: which gui?
05:10 PM andypugh: https://github.com/LinuxCNC/linuxcnc/issues/2329
05:12 PM roguish[m]: thanks. shooo, I don't really know much of PSNG. I used ProbeScreen v1 and v2 for years. now using qtdragon, and having issues with some of the probing.... going around with cmorley to fix 'em.
05:13 PM roguish[m]: rodw is helping out too
05:40 PM rmu: i recently had a look at probing routines in the "probe basic" GUIs. wouldn't recommend switching units and using those routines either. aborting a probe operation also leaks state
05:55 PM pere: andypugh: great to hear. feel free to add arrival and departure time to <URL: https://pad.efn.no/p/linuxcnc-2023-norway > so we know when to pick you up. Do you use signal.org?
05:55 PM rmu: i wonder if it would make sense with mesa hardware to latch probe position directly in FPGA firmware, similar to home to index. should improve speed/accuracy of probing.
05:56 PM andypugh: rene-dev5: Have you decided if you are attending?
05:56 PM andypugh: rmu: I think that’s a thing.
06:05 PM seb_kuzminsky: rmu: hm2_????.0.encoder.??.probe-enable
06:08 PM rmu: interesting. thanks.
06:09 PM rene-dev5: pere Im going as well
06:09 PM rene-dev5: rmu nice idea, but probably makes no sense.
06:11 PM rene-dev5: you just do a really fast probe, and then another close one very slowly.
06:15 PM rmu: it seems hostmot encoders and stepgens support latching coordinates into a probe register upon probe signal. but i'm not sure how to connect an actual probe.
06:26 PM pere: rene-dev5: cool. please update the pad with your details.
06:32 PM rmu: i guess mesa firmware with QCountProbePin on some input is needed for that to work
06:34 PM rene-dev5: Rmu how far does the machine move in 1 servo cycle with probing speed
06:35 PM rene-dev5: pere will do, once I booked the hotel.
06:40 PM rmu: rene-dev5: that depends i guess, about 1µ with my presets ;)
06:42 PM rene-dev5: Then it probably makes no sense :D
07:37 PM -!- #linuxcnc-devel mode set to +v by ChanServ
09:12 PM -!- #linuxcnc-devel mode set to +v by ChanServ
10:54 PM fdarling: rmu: I was also wondering how to actually hook up a probe with Mesa hardware, like what input is required? Any pin in GPIO mode? A specific one?
11:06 PM linuxcnc-build: build #2744 of 4041.deb-buster-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4041.deb-buster-rtpreempt-amd64/builds/2744 blamelist: Sebastian Kuzminsky <seb@highlab.com>, CMorley <chrisinnanaimo@hotmail.com>, andypugh <andy@bodgesoc.org>
11:39 PM -!- #linuxcnc-devel mode set to +v by ChanServ