help - infinite recursion! I want to make some little parts with a tapped hole - I should get rigid tapping working - I need to mount this encoder - I need to turn an adapter on the lathe - I should get touchy working on the lathe - I need to rearrange stuff so there is a place to set the touchscreen - I should go chat on irc!
come on over cradek I'll help you out
the only thing that would "help" more is some beer or something
at least it's a weekend!
yep I agree it is a glass of dry red for me
* jt-plasma wished he had left 6" more inches between the CHNC and the plasma table :/
jt-plasma: Hey stooopid, remember.... Cut twice, measure once!
I ain't cut it yet
GIT ER DUN!
well it don't take the siemens long to lose it's mind when you take the battery out with the power off
still trying to get that thing to work?
come over to the light side, luke errr john
jt-plasma: "I am your Father"
<evil laugh goes here>
not much more I think
I can get everything to work except the controller
* jt-plasma listens to Eric Johnson Cliffs of Dover .... ahh Bach
EMC: 03cradek 07master * r199f26e6f049 10/src/emc/usr_intf/touchy/emc_interface.py: fix minor visual problem in lathe mode: dro columns not lining up
Is this possible?
A custom stepgen for simple sinking EDM:
I have made some progress in using hal for EDM.
I can move an 'axis' with an analog gap signal, using a velocity mode stepgen.
The tool moves forward and backward between a beginning position and an end position according to a gap error signal (a signed velocity).
But, EMC uses position mode stepgens.
Would it be possible to modify a custom stepgen to allow the mode (position vs velocity) to be selected by a pin?
Would other components of emc care?
I'd like to enter 'velocity mode' or 'position mode' at will.
Velocity mode would be for sink edm, Position mode would be for 'poses'.
Programs would basicly be 'pose', 'edm' 'pose', 'edm' ... ( never both at once )
I'd be willing to invest time if it wasnt impossible.
Please comment about the possibilty.
seems like the problem would be with switching from velocity mode back into position mode. since the position is different from when you switched out of position mode, the position control (emc) sees a jump in the feedback
and if i insured the posn was the same?
(start here end here)
I don't see any problem then
thx :) will try to do it
I bet you can do it without any modifications
run two stepgens, one in each mode
use muxes to switch the ins/outs between them
2 stepgens for 1 axis?
sure why not?
oh, duh... yes why not :)
not sure about homing - you'll have to play with it
if you cause a position jump, emc will just give you an ferror and disable the amps...
but if you are careful about that I bet you can wire it up in hal and go
EMC: 03micges 07tlo_all_axes * r63426a55566a 10/lib/python/rs274/glcanon.py: Fix Axis to load programs with G43 and G43.1
EMC: 03micges 07tlo_all_axes * r7fad832d4d06 10/lib/python/rs274/glcanon.py: oops this line was added by accident
EMC: 03micges 07tlo_all_axes * r7287daaff59a 10/src/emc/rs274ngc/interp_internal.cc: Changing G43.1 to use axis words caused sometimes to be interpreted like motion gcode, this patch fix this