On Friday, June 08, 2012 10:21:38 PM Brian May did opine:

> I am having trouble setting up threading on my lathe.  At this point I
> am thinking my spindle encoder is bad.  I have the following setup in
> my HAL File:
> 
> net spindle-revs hm2_[HOSTMOT2](BOARD).0.encoder.01.position
> motion.spindle-revs
> net spindle-vel-fb scale.0.in motion.spindle-speed-in
> hm2_[HOSTMOT2](BOARD).0.encoder.01.velocity
> net spindle-index-enable hm2_[HOSTMOT2](BOARD).0.encoder.01.index-enable
> motion.spindle-index-enable
> 
> My Parameters are set as follows:
> 
> setp    hm2_[HOSTMOT2](BOARD).0.encoder.01.counter-mode 1
> setp    hm2_[HOSTMOT2](BOARD).0.encoder.01.filter 0
> setp    hm2_[HOSTMOT2](BOARD).0.encoder.01.index-invert 0
> setp    hm2_[HOSTMOT2](BOARD).0.encoder.01.index-mask 0
> setp    hm2_[HOSTMOT2](BOARD).0.encoder.01.index-mask-invert 0
> setp    hm2_[HOSTMOT2](BOARD).0.encoder.01.scale  1024
> 
> For everything else, the spindle has been working fine.  I have been
> running in G96 spindle speed mode, the RPM that the encoder reads is
> perfect.  However, when I try and do a thread, the process never starts.
> The machine goes to the start point and just sits there and waits.  I am
> assuming it is waiting for an index pulse and never receives it.  From
> what I have read in the manuals - when the index pulse is found, the
> motion.spindle-revs goes to zero during a threading cycle.  On my
> machine this never happens.  It just continues to count.
> 
> I ran my G-code in the lathe sim and it seems to work fine.  I am using
> a mesa 5i20 and a 7i33 daughter board.  The encoder is connected to the
> 7i33 board.  The encoder is an automation direct TRD-N1024-RZVWD.
> 
> Am I missing something simple?

Possibly.  The interface should have an index pulse on it, could be labeled 
encoder.N.Z where N is the encoder enumerator if you are using more than 1.

Use the halscope to search for it.  If it is feeding one of the mesa 
boards, there should be an index pulse there, but I am not familiar enough 
with the 7i33 to know which pin, or even if it sends it on to someplace hal 
can access.  To work, I would think it would have to.

Have you tried to contact Peter (mesa) about this?  He'll be far more 
knowledgeable than I can ever be.

Cheers, Gene
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: <http://coyoteden.dyndns-free.com:85/gene>
love, v.:
        I'll let you play with my life if you'll let me play with yours.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to