jmkasunich: life was calling me too
jmkasunich: perhaps I'll be here when you get back
can I stay in here so as to avoid any breast-udder correlations that might be lurking on that other channel?
jmk-vm03: did you figure out your shlib problem?
no, I just got back
and the vm's are clamoring about an update - thats annoying, so I'm dealing with it
damn thats slow
click on the "I wanna update" icon and it takes literally 30-60 seconds for the first sign of any activity
no compiles are going on, CPU load is low, no swapping
it's probably doing apt-get update
no, it does that after asking for the password
it was just very slow
now its fine (once the password dialog came up and I answered it)
maybe it wasn't seeing my mouse click
who knows... VMs are mysterious sometimes
ok, that rot is finished
how does one check on shared libs?
where did it put it?
find is also slow on a VM
"sudo ldconfig /usr/local/lib/" seems to have fixed it
but I wonder how it got broke
what exactly does ldconfig do?
sets up symlinks it seems (according to the manpage)
I wonder why they went away
I know it was working a while ago
ld.so (the dynamic loader) also caches those paths
well, I think its all fixed
just gotta have somebody break a compile to be sure
hey - I can probably do that :)
so - I was thinking of maybe ordering some of the motor connectors that fit the 7i30, plus the 4-pin connectors that several of the boards use for power (the ones that look like floppy power connectors)
"look like", or "are" floppy power connectors?
they aren't the same, though the pin spacing is the same (and the locking tab)
I saw you mention the motor connectors yesterday? and tried to tell you I wanted some, dunno if you saw that
I have the cables from a couple of PC power supplies, I thought I was all set
I saw, but wasn't sure of the right part numbers (and the ones I think were appropriate were out of stocK)
you can use them, but you have to remove the +12V wire and shave off the key on the top
I thought about that - a PC power supply give s you +- 12V for op-amp circuits, lots of +5V, and lots of +12 for switches / relays etc.
I thought Mesa had specifically designed them to use PC connectors, including making the 12V pin a no-connect
nope = +5 G G +5
the PC's -12 would be inconvenient to access, but +12 would be nice to have
if the current is low enough, converting +12 to -12 on the expansion boards can be pretty cheap too
just get an ATX -> AT adapter and cut off one connector
that gives all the voltages
or ATX24 -> ATX20 (or the other way)
well, the main power supply connector is plugged into the mobo
I'd want to use a drive connector
no - a separate supply
(or extra somewhere ... )
why use a separate one?
its not like the grounds are isolated from each other or anything
I like the idea that a wiring problem won't crash the computer
it's one reason I don't like the idea of pulling power from USB connectors
(though those are "protected" by the USB chip)
what I had in mind was power for the interface board, not power that would leave the interface board
right. I was thinking more of "power for eveything else in the cabinet"
12V relays, analog amp boards, contactors ...
limit / other switches
for contactor coils and limit switches I like 24V
and I also like it isolated if possible
that's a good point
my tentative plan is to use the PC supply for non-isolated power
that eliminates any issues of sequencing - which supply do I turn on first, off last, etc
the thing to do is probably to get several HD -> 2x floppy Y cables, snip the 12V cable at the HD end, and shave off the key on the floppy ends
that leaves the PS pristine (and lets you replace it if needed)
if you're sneaky, you can also attach the 12V wire to the 5V line at the HD end
I can't imagine any of the interface boards actually needing two pins worth of 5V current
I haven't checked to see that both pins are connected - one sec
ok. they are (as I hoped)
and also connected to the +5V from the ribbon cable (makes sense, since the external supply is optional)
how is the 7i33 (+/-10V outputs) powered?
there's a big 6-pin component by Vitek - there may be a booster on board
any xfmrs or inductors?
well, there has to be, since there's only 5V from the PC or external power conector
yes, there's a SMT inductor next to the Vitek thing (Which may itself be a power inductor)
ok - it's a triple coil power inductor, probably 2:1:2, fed from a 5V square wave to the center coil
what feeds it?
just logic and discretes
that part number isn't in the datasheet, so it may be a custom 1:3:3 or something
[04:48:51] <SWPadnos> http://www.viteccorp.com/data/g303.pdf
the part number I have is 16Z5777 though
time for sleep
lerneaen_hydra is now known as hydra_away
hmmm.. I think there are still 2 languages left from which to control emc2
prolog and fortran?
haskell? scheme? forth? brainfuck?
you just made that up
hmm.. but some lisp bindings
no, I didn't make those language names up. http://www.muppetlabs.com/~breadbox/bf/
jepler: ok, just read about it :P
[15:04:09] <alex_joni> http://www.rpi.edu/~hughes/boof/
jepler: you looked a bit at homing, is it possible to set it up so that 2 axes don't get homed at once ?
* alex_joni wonders if the driver can request that
alex_joni: that's not currently possible. A user can issue NML home messages for as many axes as he likes, and there's no code to prevent them all trying to happen at the same time.
alex_joni: but in 2.1 and newer you can set a "homing sequence" and define shared home switches, so that the "home all" button will always do the right thing.
ok, I am just wondering..
see HOME_IS_SHARED and HOME_SEQUENCE in http://linuxcnc.org/docs/2.1/html/config/ini_homing/index.html
the STG board (yuck) needs to select a pair of axes to watch for index pulse, then it outputs 2 bits (odd/even)) when that index has arrived
so you first select axis 1&2 or 3&4 or 5&6 or 7&8
wonder what they were smoking
sounds like you have to just declare the board broken, and support index pulse on half the axes
e.g., only on 1,3,5,7
you can select 1&2 to check for index
then you get 2 bits (even if axis 2 has hit an index or odd for axis 1)
sounds like you have to just declare the board broken, and support index pulse only on two of the axes
so you can only home max. 2 axes at once
I think it can work for all, just only one at a time
can the software driver request the bits for axis 1 and 2 in one polling cycle, and so on -- getting all the index pulse information in 4 servo periods?
hmm.. don't think so
unless the index pulses come at the right time
it works like this: you request axis 1&2 then wait for indexes to arrive
then you can select 3&4 and wait for that
sounds like you have to just declare the board broken, and place it in the trash bin
well, it kinda reminded me why I didn't do this part the first time
alex_joni: how did it work in emc1? I think it did
cradek: one at a time
but probably without any error checking
you can home all axes together in emc1 too
bet no-one used that with the stg
yes I'm sure they do, I've heard les say so
of course this is STG1
STG2 is completely different
yes, maybe his is STG2
you don't have to inhibit homing, you only have to inhibit the last move that searches for index
just use the emc2.1 homing sequence and always "home all"
the integrator must make sure two axes have a different HOME_SEQUENCE unless they're on the same stg axis pair
jepler: right, that's what I was thinking
and the operator must always use the homing sequence when homing more than one axis
is there a way that he doesn't ?
afaik only axis sends the "homing sequence" nml message, which is "home axis -1". but in all the guis, you can also home one axis at a time
one at a time is no issue
unless the user pushes home on all the axes rapidly
I guess I don't really mean "one at a time"
in all the guis, you can send homing messages for the axes individually
guess he could go to axis 1 push home, then 2 push home, while 1 didn't finish
seems STG2 does it a bit better
8 different bits for index pulses
alex_joni: do you have a link to the stg1 documentation? I can't quite understand it by reading emc1 code
does reading this latch reset it? otherwise I don't see the harm in reading more data than you need
you need to read some other registers to reset the latches
but the minute you select another pair of axes the latched values are of no use any more
[15:43:44] <alex_joni> http://www.servotogo.com/hardman.zip
that's for stg1
[15:44:18] <alex_joni> http://www.servotogo.com/hardman2.pdf
HARDMAN1.DOC: Microsoft Office Document
OO opens it though
I see these latches but I don't understand what the index actually does - how do you know the count when the index happened?
it latches the count
ok (I should read more)
so if you have an index latched, you only red from the output register
if not, then you need to make it copy from the counters to the OR then read it
wonder which stg people are mostly using
I'll try implement both of them
I don't understand how homing on stg1 works - it must not actually work (sometimes) in emc1.
homing one axis at a time can work, right?
the axis go marching 2 by 2
hydra_away is now known as lerneaen_hydra