- Posts: 6803
- Thank you received: 0
qt_dragon_hd - manual tool change and remap
3 years 5 months ago #272067
by cmorley
Replied by cmorley on topic qt_dragon_hd - manual tool change and remap
Also if you could post your config files...
Please Log in to join the conversation.
3 years 5 months ago #272071
by grey_goat
Replied by grey_goat on topic qt_dragon_hd - manual tool change and remap
I'm using a switch type toolsetter.
I switched the polarity of the wiring from the diagram that came with the toolsetter, and now my halmeter for the pin sits at true, turning to false when I press the button. This is progress, it used to do nothing but stay false. It was contributing to my confusion with the halmeter as that was the first time I'd used it and nothing was happening when I pressed the toolsetter.
I think this has resolved my current issue. Stay tuned for tomorrow, when there's something else I can't figure out how to do.
I switched the polarity of the wiring from the diagram that came with the toolsetter, and now my halmeter for the pin sits at true, turning to false when I press the button. This is progress, it used to do nothing but stay false. It was contributing to my confusion with the halmeter as that was the first time I'd used it and nothing was happening when I pressed the toolsetter.
I think this has resolved my current issue. Stay tuned for tomorrow, when there's something else I can't figure out how to do.
Please Log in to join the conversation.
3 years 5 months ago #272072
by cmorley
Replied by cmorley on topic qt_dragon_hd - manual tool change and remap
you will need to invert the signal now.
probe-input must be normally false - true when tripped.
probe-input must be normally false - true when tripped.
Please Log in to join the conversation.
3 years 5 months ago #272130
by grey_goat
Replied by grey_goat on topic qt_dragon_hd - manual tool change and remap
I inverted the signal. Now when I trigger the toolsetter after completing a tool change I immediately get. "Probe is already tripped when starting G38.2 or G38.3 move"
Please Log in to join the conversation.
3 years 5 months ago #272135
by cmorley
Replied by cmorley on topic qt_dragon_hd - manual tool change and remap
hmm can you confirm again that motion.probe-in is false when the probe is not tripped?
Please Log in to join the conversation.
3 years 5 months ago #272137
by grey_goat
Replied by grey_goat on topic qt_dragon_hd - manual tool change and remap
Can confirm.
My understanding is that the tool was supposed to touch the tool setter, back up, and then touch it again slowly. At the moment a single touch triggers, "the probe is already tripped," when pressed for the first time.
My understanding is that the tool was supposed to touch the tool setter, back up, and then touch it again slowly. At the moment a single touch triggers, "the probe is already tripped," when pressed for the first time.
Please Log in to join the conversation.
3 years 5 months ago #272147
by cmorley
Replied by cmorley on topic qt_dragon_hd - manual tool change and remap
What speeds to you have set for searching/probing?
Please Log in to join the conversation.
3 years 5 months ago #272177
by grey_goat
Replied by grey_goat on topic qt_dragon_hd - manual tool change and remap
Search velocity is 40mm/min and probe velocity is 10mm/min
Please Log in to join the conversation.
3 years 5 months ago #272181
by cmorley
Replied by cmorley on topic qt_dragon_hd - manual tool change and remap
Sounds very slow.
On my little test mill I search at 10 ipm and probe at 5 ipm.
That's about 250 and 125 mm/m
I would try bumping up the search speed - try double and see if that has an effect.
On my little test mill I search at 10 ipm and probe at 5 ipm.
That's about 250 and 125 mm/m
I would try bumping up the search speed - try double and see if that has an effect.
Please Log in to join the conversation.
3 years 5 months ago #272182
by grey_goat
Replied by grey_goat on topic qt_dragon_hd - manual tool change and remap
I went up to 250 and 100. I had slowed it down from 300 and 10 initially.
Now the error is, "probe tripped in non-probe move."
Now the error is, "probe tripped in non-probe move."
Please Log in to join the conversation.
Time to create page: 0.064 seconds
