On Thursday, April 12, 2012 11:00:51 AM Erik Friesen did opine:

> Where can I find a cut and pastable pin list?

I am not sure this is the correct question for me to try to answer because 
I am not using a 5i25, I have had good results so far with cnc4pc's C1G 
interface card.  It may not be capable of as many pre-programmed functions 
as the 5i25 as it is "programmed" with jumper clips.  Very limited, but 
versatile too, just not in the sense that the 5i25 is.

When using something along its (C1G) lines, the choice of pin numbers vs 
function assignments is purely at your convenience given the limits of the 
std parport as some pins in the normally initiated condition are input 
only, and more are output only.  With then 5i25, those limits disappear 
from what I can read.  That can be quite an advantage but also appears to 
require programming firmware to be loaded.

I am fond of wiring things up with a 4 wire cable per device controlled, 
with the stepper motor drivers outputs and encoder signals in a shielded 
"Star-Quad" style microphone cable.  The version I get from Clark Wire & 
Cable in the Chicago area has what seems to be an oil immune outer jacket 
(in your choice of several colors) where the shield is NOT connected at the 
machine end to prevent the noise injecting formation of "ground loops" and 
is actually pretty flexible, or for outputs such as the spindle controls I 
like to use a 4 wire flat ribbon cable the shack sells on spools, 50 foot 
IIRC.  But its a solid conductor & I wouldn't call in flexible in the same 
sense.

The stepper driver signals, all in the same box with this interface card, 
are all controlled by short pieces of that flat ribbon cable as I've found 
the best way to handle the dirty environment is to put all that in one box 
I've made from heavy, 1/4" and 1/8" thick alu plate, with individual fans 
on each motors driver, and all the I/O I need brought out to a long nylon 
terminal strip via a notch in the cover that passes several pieces of this 
4 wire ribbon, all 'gooped' in place so the cover being swung on two of its 
retainer screws isn't likely to guillotine the wires. This box, when 
completed, will be well sealed against swarf, and if it gets too warm, a 
std 120 volt rotron fan does a great job of cooling the whole box.

This particular interface has all I/O tallied by super bright LED's which 
can serve as a troubleshooting tool while wiring things up.  In fact, I cut 
a recess above where it is mounted to the lid panel of this box, and have 
fitted a lexan cover that will be, when everything is finally wired up, 
gooped in at about 4 places so the LED's will be visible in normal 
operation.

What you wire to where is entirely up to you within the constraints of the 
ability of that particular pin, if you are outputting a signal then 
obviously your hal file needs to steer that signal to an output pin, 
conversely if this signal is an input, then a pin capable of input needs to 
be wired to this signal both in the external wiring you connect to and in 
the internal .hal files "wiring".

However, I agree 200% with the relative lack of doc's for the hal stuff.  
The loadrt command is simple enough,  and so is the setp, meaning set a 
parameter for that named function to work with when it is executed.  The 
net command appears to be how one does the internal 'wiring', at least that 
is what I have deduced from the few examples.

But really, the explanations as to how an individual module of code that is 
loaded by the loadrt command, have been so emasculated as to be less than 
useful to those of us, who are functioning as the 'system integrator' in 
our own home shops, where each new function needed is so poorly described 
in the hal manual that we have to come to this list and ask if anyone else 
has managed to 'figure it out'.

There are, I think, advantages for the developers who then hear who is 
having what sort of trouble, but then its quite often only the developer 
that wrote that code who can begin to tell us frogs how to use it 
correctly.

His having to repeatedly teach us frogs I am sure wastes more of his time 
than he might have used to fill out to at least half a page, each modules 
description of what it can do, and at least another paragraph on the 
effects of each parameter that code module needs.

But maybe that is just me getting stupid in my dotage too.  I'll let others 
be the judge of that.  I do get 'told off' occasionally. ;-)

> On Thu, Apr 12, 2012 at 10:11 AM, Viesturs Lؤپcis
> 
> <viesturs.la...@gmail.com>wrote:
> > 2012/4/12 Erik Friesen <e...@aercon.net>:
> > > I don't mind writing my own, its just that details are so sketchy
> > > and I don't know where to get information.  I am blindly kludging
> > > around trying to get a grasp on basics here.
> > 
> > Any specific questions?
> > 
> > Viesturs
> > 
> > 
> > ----------------------------------------------------------------------
> > -------- For Developers, A Lot Can Happen In A Second.
> > Boundary is the first to Know...and Tell You.
> > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> > http://p.sf.net/sfu/Boundary-d2dvs2
> > _______________________________________________
> > Emc-users mailing list
> > Emc-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/emc-users
> 
> ------------------------------------------------------------------------
> ------ For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users


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>
The only "intuitive" interface is the nipple. After that, it's all learned.
(Bruce Ediger, bedi...@teal.csn.org, in comp.os.linux.misc, on X 
interfaces.)

------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to