Advanced Search

My tool setter in NC , probe is NO.
So I'm using the remora.input11.not to invert the pin. But that dosnt seem to work with or 2.0.
When I use the normal remora.input.11 pin the prob works as it should triggering the motion.probe signal. Tool setter when pressed triggers only the or2 in. 

Addf or2.0 servo-thread
Net toolsetter remora.input.11.not or2.0.in0
Net Probe_tool remora.input.12 
or2.0.in1
Net probes or 2.0.out motion.probe-input

Is there a way to get this to work other than a relay

^^^^ I got this to work with classic ladder

Hey all, 

I've got a Bridgeport BTC-1 milling machine, controlled by an old Dell Optiplex 755 and a Mesa 5125 card. The 5125 card connects to a Mesa 7177 card with a parallel port cable. It is in a barn without AC, and it seems the Dell is the weakpoint. It often breaks, probably due to the heat and humidity. I can get new ones for about $80 on Ebay, but would prefer to have a more permanent solution.

Can anyone recommend a good computer for this application that wont' break the bank?

Thanks, 
-Hunter Long

I don't know, with the latest Windows 11 update screwing up SSD's and such " Artificial Incompetence " may
be Windows epitaph.

Ok thanks for the tip. I tried to setup the spindle via pncconf but it didn't run. I have a screenshot below of what I tried. In the TB1/TB2 tab I selected spindle PWM as you can see. Is this the wrong place to setup the spindle?

Thanks for the reply PCW. I was going through pncconfs and I couldn't find anything like discovery(Im new to LinuxCNC). While going through pncconfs I was a little confused because I flashed the 7i96s_5abobd.bin file but I couldn't find this as an option in pncconf as you can see in the image below. Anyways, I tried all three of the options that were there and none of them gave me the option of adding the BoB. Thank you for your help

Hi,

I'm trying to get my toolsetter to work, but i'm running into "Probe tripped during non-probe move" just as the probe is tripped. I've been though a lot of the usual stuff i found on the forum, like electrical noise, debouncing and so on....I'm fairly new to gcode, macros and stuff, so bear with me on this...

I'm using all the standard stuff that comes with Probe Basic, but looking at the "default" tool-touch-off macro here: 
github.com/kcjengr/probe_basic/blob/0490...ol_touch_off.ngc#L59
(And again later in line 69 with the slow probe retract)

I think that this G1-move might be the one causing my issue? I'm trying to understand why this isn't a G38.5 move instead? Then it would be a probe-movement which allows the probe to be triggered while moving...at least as far as i've understod...or maybe a combination of a G38.5 first and then a G1 move, since G38.5 stops after untripping the probe per the documentation...am i completely off here?

I've been really hesitant to post this, because a lot of people use this macro(i guess?) and i assume it work for all of these people, so chances are very high that I'm mistaken and something else is going on...

Any input will be highly appreciated! Thanks!

/Thomas