On Sunday 15 October 2017 09:18:36 Gene Heskett wrote:
> On Sunday 15 October 2017 04:56:09 andy pugh wrote:
> > On 15 October 2017 at 02:10, Gene Heskett <[email protected]> wrote:
> > > In the Ducumentation.pdf, there is a remark in the g33 command
> > > description about needing to hookup both the spindle-at-speed and
> > > the encoder.n.Z (index) to something. I seem to have lost one or
> > > the other in this little puff of smoke from the ptc on a 5i25.
>
> The point I was making was that the Doc said see the other integrators
> manual for more details. It doesn't exist in that doc, so I go to the
> wiki, and all the links to other wiki pages from spindle-synched
> motion are broken.
>
> > I don't think that either of those is true.
> > Spindle-at-speed is (or ought to be) ignored during a
> > spindle-synchronised move.
>
> True, for after the move has begun, but it needs a true to allow it to
> start.
>
> > encoder.Z is not typically a HAL connection (except when using
> > parport and software encoder counters).
> > Furthermore, without an index connected the spindle-synch move won't
> > even start.
>
> I found that info in man 9 motion, an hour ago. And I've been pouring
> over my hal file since. I think its all hooked up but isn't working.
> The joint following error is exerted (I found this by slowing the
> spindle to about 40 rpms) at the initiation of the reverse move back
> up. But I'm not awake yet either. Coffee is perking, and I'll probably
> go back to bed after I've coffee'd and fed the missus. Up and down on
> an 18" stool quite a few times yesterday, cause all this is on a shelf
> close to 6 feet off the floor, and leg cramps screwed up what should
> have been plenty of sleep time. Still in pain.
>
> I don't recommend old age, its not at all what its cracked up to be.
>
> So first I have to reinstall the P3 cable after I'd trimmed the end of
> the ribbon and gave it a coat of superglue gel, which may have been
> the short that blew the 5i25's ptc to bits, leaveing a charred
> depression in the pcb where it was. Then I can check the near.speed
> output, and take another look at motion.spindle-index-enable. The 5i25
> is a fresh one.
>
> Back with more details after I've put it back together and up to
> normal on my coffee levels.
>
> Cheers, Gene Heskett
>From man 9 motion:
motion.spindle-at-speed IN BIT
Motion will pause until this pin is TRUE, under the following
conditions: before the first feed move after each spindle
start or speed change; before the start of every chain of
spindle-synchronized moves; and if in CSS mode,
at every rapid->feed transition.
Should be satisfied by:
net spindle-vel-cmd-rps <= motion.spindle-speed-out-rps near.speed.in1
net spindle-vel-fb-rps => motion.spindle-speed-in near.speed.in2
setp near.speed.difference 3
net is-spindle-at-speed <= near.speed.out => motion.spindle-at-speed
And its true 99% of the time. Encoder output is noisy as can be.
and
motion.spindle-index-enable I/O BIT
For correct operation of spindle synchronized moves, this signal
must be hooked to the index-enable pin of the spindle encoder.
should be satisfied by:
net spindle-index-enable <=> motion.spindle-index-enable
net spindle-index-enable <=> hm2_5i25.0.encoder.00.index-enable
I see false on a halmeter above. I can see the index at the bob's encoder.Z
input
and
motion.spindle-revs IN FLOAT
For correct operation of spindle synchronized moves, this signal
must be hooked to the position pin of the spindle encoder.
should be satisfied by:
net spindle-vel-fb-rps <= hm2_5i25.0.encoder.00.velocity
net spindle-vel-fb-rps => scaleX60.in abs.encdir.in enc0.in0
comp.filter.in0 motion.spindle-revs
But the 5i25's builtin encoder does not have a "position". Would count do?
4 more hours later, I've rung the 5i25 p3 to bob cable twice, it has no
shorts, and 2 ohms or less for every conductor. Its around 4 feet long.
Then I notice the z motor is running rough, which it wasn't yesterday.
But put my scope of pin 6 (stepgen-2-step.out)
and the 2nd channel on pin 7 (stepgen-2-dir.out)
Everything is quiet, pin 6 sitting at vcc, pin 7 on ground, until I hit
the keyboard page-up/down key, either one. Sliders set for less than an
inch a minute. Step goes active, issuing step pulses of the set width,
but has randomly timed extra pulses thrown into the stream, all the same
4us width. The dro's last two digits are random but close, and these
steps that continue after my finger has left the button, stopping the
dro advance, but it continues pumping out the steps until it throws the
joint 2 error, sometimes as following, but not always.
Direction line, pin 7, stays low regardless of key.
3 more 5i25 cards, can readhmid of a prob_rfx2 program just as if thats
all they knew how to do. I reburn them anyway. And all 4 behave exactly
the same when installed in this dual core box.
Next idea? I'm fresh out, and at about round 6 or 7, losing this fight
on points alone.
Thanks everybody.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
