#linuxcnc-devel Logs

Mar 15 2021

02:00 AM -!- #linuxcnc-devel mode set to +v by ChanServ
02:05 AM -!- #linuxcnc-devel mode set to +v by ChanServ
03:32 AM -!- #linuxcnc-devel mode set to +v by ChanServ
03:32 AM -!- #linuxcnc-devel mode set to +v by ChanServ
04:05 AM mrec: Hi, is there any plan about multiple motion probe inputs?
04:06 AM mrec: I'd need one for a tool setter and another one for a touch off probe
04:06 AM mrec: I saw some people are doing a xor on the inputs
07:11 AM htasta: mrec what's wrong with using an xor?
07:33 AM mrec: well I have different operations behind that
07:34 AM mrec: maybe I just need to change my thinking and give it a try
07:36 AM mrec: since I didn't get an answer in another channel did anyone test the probe screen v2?
07:36 AM mrec: seems like the corner operations aren't working properly
07:55 AM mrec: ok well I'll dig into it.
08:28 AM htasta: unless you are using 2 probes simultaneously you don't need 2 dedicated signals. you can handle it all in your gcode macros. so if you do touch off you move until probe signal (which is either touch or setter), same if you do tool setting you move until probe signal (which is either touch or setter)
08:52 AM mrec: I will work that out thanks.
08:52 AM mrec: I'm currently pulling glade to modify the probe screen v2
08:52 AM mrec: or is there any other "standard" for touch off / tool setter available with linuxcnc?
08:52 AM mrec: I'm not satisfied with the tool setter support, I have done my own setter support where I can dynamically set the setter position on the milling table
08:20 PM -!- #linuxcnc-devel mode set to +v by ChanServ