Chris Barker wrote:
Is it possible to edit the conf file manually?
YES, very much so.
EMC has _always_ been configured by editing ini and hal files. Stepconf
is brand new in version 2.2, and is a "wizard" intended to make setting
up simple stepper machines easier for beginners. It is NOT the only way
or the best way to do things, just one way, for one class of machines.
Editing the files requires a somewhat deeper understanding of what you
are trying to do than using a wizard like Stepconf, but it also gives
you MUCH more control over your configuration.
Can EMC handle sharing the home and min. limit switch on each axis > individually?
Yes. You can share limits and use individual homes, or vice versa.
Of course, I would like to avoid rewiring.
Thanks,
Chris
Dean Hedin wrote:
Chris make sure you are up to version 2.2.2
There are some bugs in the wizard regarding home/limit switch setup.
The bugs are only in the Stepconf wizard, not in EMC itself. (Stepconf
is new in version 2.2)
You may find it easier to just rewire the switches.
Everyone is entitles to his own opinion, but I can't imagine rewiring a
perfectly usable machine just because it exceeds the capability of the
"simple stepper machine" configuration wizard. Configure the machine
the "old fashioned" way using the ini and hal files. That gives you
complete control.
The "most simple" configuration is to put all the homes on one pin and
all the limits on another pin. Have a pull up resistor on each pin and any
on of the switches can pull
the line to ground.
If you have enough physical input pins to use one for each home switch,
why would you want to lump multiple switches on one pin? Permanently
handicapping your machine to avoid some temporary inconvenience during
configuration doesn't seem like a good tradeoff to me.
In the original mail Chris Barker wrote:
> Each axis has it's own home switch. The home switch also acts as
> a minimum limit when home isn't being used.
> 3 input pins are used. Active low.
>
> Maximum travel limits are combined on all axes in a serial conection.
> Active low.
> Only 1 pin is used on the par. port.
I don't know your actual pinout, but lets assume it is like this:
Parport pin 10 = X axis home (and min limit)
Parport pin 11 = Y axis home (and min limit)
Parport pin 12 = Z axis home (and min limit)
Parport pin 13 = combined X,Y,Z max limit
All inputs are active low (low when on the switch)
Then the limit section of your hal file should look something like this:
# connect pin 10 to X home and min limit
net X-home parport.0.pin-10-in-not => axis.0.home-sw-in axis.0.neg-lim-sw-in
# connect pin 11 to Y home and min limit
net Y-home parport.0.pin-11-in-not => axis.1.home-sw-in axis.1.neg-lim-sw-in
# connect pin 12 to Z home and min limit
net Z-home parport.0.pin-12-in-not => axis.2.home-sw-in axis.2.neg-lim-sw-in
# connect pin 13 to all three max limits
net XYZ-max-lim parport.0.pin-13-in-not => axis.0.pos-lim-sw-in
axis.1.pos-lim-sw-in axis.2.pos-lim-sw-in
Notes:
Lines beginning with # are comments, you can put whatever you want
there. Write something that will make sense to you when you are
troubleshooting five years from now.
Lines beginning with "net" create a HAL signal that connects things
together. In this case, it connects a parport pin to EMC. Everything
after "net" is on one line (my mail client is wrapping the long lines,
and yours might too). "X-home", "Y-home", "Z-home", and "XYZ-max-lim"
are signal names, and can be whatever makes sense to you. The remaining
names on each line are the pins that the signal connects, and must be
names that already exist in the system. The "=>" arrows are optional,
and are used to show a human reading the file which way the signal is
flowing.
Regards,
John Kasunich
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
