- Posts: 41
- Thank you received: 12
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Rory wrote: Make sure your "probe pin" is set to the pin you have connected the probe to. Should be pin 10. Go to the diagnostic screen and check that pin 10 is changing state as you press the probe pin. This ensures the signal is getting to the correct pin and you then assign the probe setting to this pin (pin 10 port 1).
Then you need to make sure you understand what the macro is doing.
Then copy the atached file to C:\UCCNC\Profiles\Macro_YOUR_PROFILE
file needs to be just M31.txt so remove the date from the file (forum adds these)
And the probe should work like this
- newZ = 33
This should be changed to whatever height your probe device is, isn't it? I
suppose 33 is your probe button device I see in the video. I would change that
variable name to ProbeHeight for example.
- while(exec.IsMoving()){}
Wouldn't it be better to add another line like this to the macro start, so if
the machine is moving and you hit the probe button by error, it won't stop
until finished?
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
jvalencia wrote:
Rory wrote: Make sure your "probe pin" is set to the pin you have connected the probe to. Should be pin 10. Go to the diagnostic screen and check that pin 10 is changing state as you press the probe pin. This ensures the signal is getting to the correct pin and you then assign the probe setting to this pin (pin 10 port 1).
Then you need to make sure you understand what the macro is doing.
Then copy the atached file to C:\UCCNC\Profiles\Macro_YOUR_PROFILE
file needs to be just M31.txt so remove the date from the file (forum adds these)
And the probe should work like this
Hi Rory, I've seen the macro and saw 2 things:
- newZ = 33 This should be changed to whatever height your probe device is, isn't it? I suppose 33 is your probe button device I see in the video. I would change that variable name to ProbeHeight for example. - while(exec.IsMoving()){} Wouldn't it be better to add another line like this to the macro start, so if the machine is moving and you hit the probe button by error, it won't stop until finished?
I modified it a bit and attached it here, but it's not tested since I don't own a probe right now (I'll have to make one myself). If you test it let us know
Please Log in or Create an account to join the conversation.
We use cookies on our website. Some of them are essential for the operation of the site, while others help us to improve this site and the user experience (tracking cookies). You can decide for yourself whether you want to allow cookies or not. Please note that if you reject them, you may not be able to use all the functionalities of the site.