Thanks Kirk - I really appreciate the help. I've put my .hal file here: http://pastebin.com/Zx7x0h6F
<http://pastebin.com/Zx7x0h6F>According to the line numbering in pastebin, I commented out lines 27, 28 and 35, and added the line you suggested in at line 36/37 (the gap). That didn't change anything, I also tried changing line 28 from xenable to zenable and 35 from xenable to yenable, but no dice there either. Two things occur to me: 1) Is there a section of the manual on this manual tweaking that I should have read? I'm quite happy to RTFM if I should have done.. 2) When I load the modified profile into stepconf, it tells me that it's been modified outside of stepconf, and that any changes will be overwritten if I save. Does this mean that (a) it doesn't use the modified settings during stepconf or (b) it will use the modifications during stepconf but not save them? Cheers, KEv. On 29 April 2011 17:02, Kirk Wallace <kwall...@wallacecompany.com> wrote: > On Fri, 2011-04-29 at 16:02 +0100, Kev James wrote: > ... snip > > Pin 4 is X-axis enable > > Pin 5 is Z-axis enable > > Pin 17 is Y-axis enable > > > > I have assigned Amplifier enable to all three pins. I discovered that > when > > the "test this axis" button is clicked (and the axes are enabled), I get > a > > voltage on pin 4 but not 5 and 17. If I set pin 4 to "unused" and try > again > > I get a voltage on 5 but not on 17. If I set 5 to "unused" as well, I get > a > > voltage on 17. This enables the Y-axis so I can run the motor. > > > > My understanding (following on from Chris' reply at the start of this > > thread) is that I can assign this signal to multiple pins and it will > pull > > them all high when the signal is "on". However, it seems that it is only > > pulling the lowest numbered assigned pin high. > ... snip > > It sounds to me like the enable signal assignments are made in a way > that creates them as three different calls to create the same signal. > The first invocation sticks but the next ones error out. In your .hal > file, try assigning the axes enable with something similar to: > ~~~~~~~~~~~ > > +--make up a unique signal name > | +--Master, whatever you use for an enable input > | | +--Slaves, list of parport output > pins > | | | > V V V > net AxesEnable axis.N.amp-enable-out parport.0.pin-04-out > parport.0.pin-05-out parport.0.pin-17-out > > ~~~~~~~~~~~ > > Then comment out the other net commands that used to create the axes > enable outputs. > > Posting your .hal file might help too. > > -- > Kirk Wallace > http://www.wallacecompany.com/machine_shop/ > http://www.wallacecompany.com/E45/index.html > California, USA > > > > ------------------------------------------------------------------------------ > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
