SWPadnos__ is now known as SWPadnos
darn, got the tach back together, it has a cleaner signal now, but still the same oscillation
I'm starting to feel out of my league. every time I think I have it, I don't
amp swap time?
can you swap individual boards, or only amp assembiles?
the amp is pretty atomic
so long as I leave everything that is referenced by the g code quick reference in the gcode/main.lyx file I should be safe in splitting out some of the other chapters into their own files...
to do a little changing in the order of subjects...
Sure. You just have to put the references in the order you want.
Lyx takes care of details like numbering and references and such
yea, I just didn't want to break any links in the g code quick reference :)
Um. Those might break.
I'm thinking the g code best practices would be best before the g codes and the canned cycles best after the g codes
If I leave the g m o codes in the main.lyx they should be ok ???
It looks like the references in quick are to specific tags setup in the html.
those tags in the generated html should stay the same if I don't remove any of those sections I think :)
Hey BigJohnT. It looks to me like we need a chapter on the nature of NML and overview of how it is setup in EMC2.
Then we need to rework much of the stuff in libnml and NML notes.
* rayh is looking at the doc produced from trunk today.
rayh: I was out in the shop
in the How EMC2 Works section of the Integrators manual?
rayh: who did the g code quick reference?
we did that for last year's CNC workshop
SWPadnos: If I remove some sections from gcode/main.lyx and split them into new files as long as I leave the g,m and o stuff nothing should break right?
I have no idea ;)
as far as the links in g code quick reference
I was more in charge of getting them printed and laminated (plus some conceptual stuff) - I really don't know how things will react to lyx changes
Let me look at that in a bit.
I do know that there wasn't a lot of space - we had to reduce the point size quite a bit to get them to fit on those half-pages
I was talking about the html one from the menu
oh. damfino then :)
hmmm, I didn't get a printed one with my download :)
rayh: just searching through the Integrators manual I only find things that mention NML but not what is and how it is used.
be back in a bit off to the shop
BigJohnT: that was jepler
I'm wondering about the code in emc-environment that says "you only have to run this once", and exits
will running it more than once do harm?
prohibiting it from running more than once prevents someone from running-in-place in one checkout, then cd'ing to another and running in place there, since the env vars will still be pointing at the first checkout
if there is a good reason for the run once restriction, I'll add a note to the wiki page saying "start a new shell if you want to run a different tree", otherwise I'd like to remove the restriction
jmkasunich: running it to completion multiple times will add more entries to environment variables like PATH each time.
ok, I was thinking it might be something like that
I put words in the wiki advising a new shell when you change checkouts or switch from sim to RT
well phooey, I broke the flex coupling
for the tach?
or between the servo and the leadscrew?
between the leadscrew and resolver/tach
so it gave me a nice runaway - but I was by the button.
ouch. Don't know if I have any of those bellows out there.
was it the tach?
Last time I got one it was about $80
BigJohnT, docs/src/code/Code_Notes.lyx need a big rewrite. I'd like to start by breaking it up into chapters.
ok sounds good to me
mcmaster has them for $25. I ordered two :-)
Does anyone know if the motion section in there is current at all?
I know that the IO sections are not.
I found one reason for oscillation - the pulley on the motor was just a tiny bit loose. after I fixed that, it worked for a couple rapids and then started with a much faster oscillation.
I am narrowing it down [slowly].
rayh: did you get a chance to look at the NML messages section?
Yes and right now I think it is great.
cradek those motors are quite responsive. any little play will be magnified a lot.
I'd like to break down the gcode/main.lyx into chapters as well but I don't want to break the g code quick reference links
the last thing I did was try to remove any slop from the tach mounting. I must have gotten it a tad too tight and broke the coupling.
I'm thinking if I leave all the g,m and o stuff in main.lyx no links will break
getting ppmc amps and mounting encoders is sounding better and better
Does that feedback package use a split gear with springs for the center drive?
but I'll work on this a while longer.
no, the center gear is solid
split would be smarter - less finicky
So the tach and resolver have an eccentric where they hook in.
yes they are mounted eccentric so you rotate them to adjust the engagement
You're getting there. Just takes time to figure it all out.
and breaking things sometimes...
BigJohnT, I'd say hack up a revised gcode section and see what breaks.
ok will do
I'll do the same here for code notes after a bit.
I ended up writing a python scrip to put the info from Alex's spreadsheet into a lyx format...
rayh: do you know if the Z ballscrew has an adjustable nut?
* BigJohnT hears the dinner bell, can't be late for that