- Posts: 30
- Thank you received: 0
Checking if Z axis is homed
7 years 9 months ago #123584
by eriksalo
Checking if Z axis is homed was created by eriksalo
Hi All;
I finally got my 20 position tool changer working. N=17 inputs and N=13 outputs. Used the vismach tool changer sample config as a guide.
I'm stuck on a finish question, how do I verify that the Z axis has been homed before starting the tool change procedure.
Tried mapping a "motion.digital-in-XX" pin to "halui.joint.2.is-homed" but got an error.
What's the right way to do this?
Thanks;
Erik
I finally got my 20 position tool changer working. N=17 inputs and N=13 outputs. Used the vismach tool changer sample config as a guide.
I'm stuck on a finish question, how do I verify that the Z axis has been homed before starting the tool change procedure.
Tried mapping a "motion.digital-in-XX" pin to "halui.joint.2.is-homed" but got an error.
What's the right way to do this?
Thanks;
Erik
Please Log in to join the conversation.
7 years 9 months ago #123585
by cmorley
Replied by cmorley on topic Checking if Z axis is homed
What was the error?
Please Log in to join the conversation.
7 years 9 months ago #123636
by andypugh
I think that is the right way to do it. As Chris asked, what was the error?
Replied by andypugh on topic Checking if Z axis is homed
eriksalo wrote: Tried mapping a "motion.digital-in-XX" pin to "halui.joint.2.is-homed" but got an error.
What's the right way to do this?
I think that is the right way to do it. As Chris asked, what was the error?
Please Log in to join the conversation.
7 years 9 months ago #123663
by eriksalo
Replied by eriksalo on topic Checking if Z axis is homed
Hi Guys;
The error was a failure on loading LinuxCNC. The debug log mentioned halui.joint.2.is-homed as the offending line, I think the error was "not recognized." I solved the problem.... It looks like I had commented out the .ini file line:
HALUI = halui
I was trying to get my tool changer remap to work and the .ngc file wasn't getting called. I didn't know why so for debug I commented out everything I didn't for sure know what it did in the .ini file including HALUI=halui.
The root cause of my original problem was that I didn't have tool-prep-loop command in my .hal file. After getting my .ngc program running, I un-commented all the .ini file stuff, and the halui.joint.2.is-homed loaded without error and works just fine!
Really happy to have gotten the tool changer finished. It was much more difficult than the milling machine itself. Now that I've done the tool changer, I will add a an M3 remap for my two speed gearbox!
The error was a failure on loading LinuxCNC. The debug log mentioned halui.joint.2.is-homed as the offending line, I think the error was "not recognized." I solved the problem.... It looks like I had commented out the .ini file line:
HALUI = halui
I was trying to get my tool changer remap to work and the .ngc file wasn't getting called. I didn't know why so for debug I commented out everything I didn't for sure know what it did in the .ini file including HALUI=halui.
The root cause of my original problem was that I didn't have tool-prep-loop command in my .hal file. After getting my .ngc program running, I un-commented all the .ini file stuff, and the halui.joint.2.is-homed loaded without error and works just fine!
Really happy to have gotten the tool changer finished. It was much more difficult than the milling machine itself. Now that I've done the tool changer, I will add a an M3 remap for my two speed gearbox!
Please Log in to join the conversation.
7 years 9 months ago #123682
by andypugh
This is often the case. All milling machines are controlled in much the same way, but the same is not true of toolchangers.
Replied by andypugh on topic Checking if Z axis is homed
eriksalo wrote: Really happy to have gotten the tool changer finished. It was much more difficult than the milling machine itself.
This is often the case. All milling machines are controlled in much the same way, but the same is not true of toolchangers.
Please Log in to join the conversation.
Time to create page: 0.108 seconds
