- Posts: 20
- Thank you received: 0
Brother TC-225 / TC-229 adventure!
Please Log in to join the conversation.
- ihavenofish
- Topic Author
- Offline
- Platinum Member
-
- Posts: 1029
- Thank you received: 0
Please Log in to join the conversation.
ihavenofish wrote: this is from another thread
.ini:
[AXIS_2]
MAX_LIMIT = 0
MAX_LIMIT_TOOLCHANGE = 200
postgui.hal:
loadrt mux2
addf mux2.0 servo-thread
setp mux2.0.in0 #<_ini[AXIS_2]MAX_LIMIT>
setp mux2.0.in1 #<_ini[AXIS_2]MAX_LIMIT_TOOLCHANGE>
net extend_z_max motion.digital-out-10 => mux2.0.sel
net z-max-limit mux2.0.out => ini.2.max_limit
change.ngc:
M64 P#10 ; enable off-limit movement
G53 G0 Z[#<_ini[CHANGE_POSITION]Z>]
...
G53 G0 Z[#<_ini[AXIS_2]MAX_LIMIT>]
M65 P#10 ; restore z max limit
thanks!
You said you still haven't figured out a way to swap limits for the ATC. Did you have problems with muxing the limits as above? To me that looks like the most elegant solution. Much less configuration than a virtual W-axis.
Please Log in to join the conversation.
- ihavenofish
- Topic Author
- Offline
- Platinum Member
-
- Posts: 1029
- Thank you received: 0
im gonna upload my hal/ini files tonight, and the toolchange.ngc. we'll see if we can finally manage to get this going correctly.
Please Log in to join the conversation.
Looking forward to your config files!
Please Log in to join the conversation.
- ihavenofish
- Topic Author
- Offline
- Platinum Member
-
- Posts: 1029
- Thank you received: 0
noise on the line, and missed encoder pulses due to noise is definitely a possibility.
from memory, if i push the table by hand, the encoder feedback seems to be not as smooth as it should. its been a while though so i dont remember anymore.
Please Log in to join the conversation.
- ihavenofish
- Topic Author
- Offline
- Platinum Member
-
- Posts: 1029
- Thank you received: 0
Please Log in to join the conversation.
- Todd Zuercher
- Offline
- Platinum Member
-
- Posts: 4739
- Thank you received: 2
I would set up the soft limits for the full travel including tool change length. Then for the regular travel length I would set up something using the near component to trigger a user message and machine pause for the 17" travel. Then during a tool change it wouldn't be too difficult to disable the user limit you just created.
Please Log in to join the conversation.
Please Log in to join the conversation.
- ihavenofish
- Topic Author
- Offline
- Platinum Member
-
- Posts: 1029
- Thank you received: 0
im 99% sure what you posted will do it, but i will need to see how to implement.
inside the toolchange.ngc you would need to trigger the z upper limit change. i have to get back into this on the weekend, and try to remember where i left off
but, we still need to tune the drives first, or this is all for nothing.
Please Log in to join the conversation.
