#emc-devel | Logs for 2008-07-27

[00:57:54] <SWPadnos__> SWPadnos__ is now known as SWPadnos
[03:03:03] <cradek> darn, got the tach back together, it has a cleaner signal now, but still the same oscillation
[03:05:19] <cradek> I'm starting to feel out of my league. every time I think I have it, I don't
[03:06:14] <jmkasunich> amp swap time?
[03:06:34] <jmkasunich> can you swap individual boards, or only amp assembiles?
[03:06:50] <cradek> the amp is pretty atomic
[14:57:58] <BigJohnT> 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...
[14:58:31] <BigJohnT> to do a little changing in the order of subjects...
[14:59:56] <rayh> Sure. You just have to put the references in the order you want.
[15:00:18] <rayh> Lyx takes care of details like numbering and references and such
[15:00:41] <BigJohnT> yea, I just didn't want to break any links in the g code quick reference :)
[15:01:12] <rayh> Um. Those might break.
[15:01:19] <BigJohnT> I'm thinking the g code best practices would be best before the g codes and the canned cycles best after the g codes
[15:01:52] <BigJohnT> If I leave the g m o codes in the main.lyx they should be ok ???
[15:05:26] <rayh> It looks like the references in quick are to specific tags setup in the html.
[15:10:43] <BigJohnT> those tags in the generated html should stay the same if I don't remove any of those sections I think :)
[15:42:45] <rayh> 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.
[15:43:17] <rayh> Then we need to rework much of the stuff in libnml and NML notes.
[15:43:46] <rayh> * rayh is looking at the doc produced from trunk today.
[15:50:22] <BigJohnT> rayh: I was out in the shop
[15:52:41] <BigJohnT> in the How EMC2 Works section of the Integrators manual?
[15:54:21] <BigJohnT> rayh: who did the g code quick reference?
[15:54:52] <SWPadnos> we did that for last year's CNC workshop
[15:55:53] <BigJohnT> 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?
[15:56:04] <SWPadnos> I have no idea ;)
[15:56:18] <BigJohnT> as far as the links in g code quick reference
[15:56:54] <SWPadnos> 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
[15:56:58] <rayh> Let me look at that in a bit.
[15:57:09] <BigJohnT> ok
[15:57:26] <SWPadnos> 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
[15:58:04] <BigJohnT> I was talking about the html one from the menu
[15:58:13] <SWPadnos> oh. damfino then :)
[15:59:41] <BigJohnT> hmmm, I didn't get a printed one with my download :)
[16:03:12] <BigJohnT> rayh: just searching through the Integrators manual I only find things that mention NML but not what is and how it is used.
[16:05:38] <BigJohnT> be back in a bit off to the shop
[17:44:53] <alex_joni> BigJohnT: that was jepler
[17:45:04] <alex_joni> bbl
[17:57:02] <jmkasunich> jepler: around?
[17:58:07] <jmkasunich> I'm wondering about the code in emc-environment that says "you only have to run this once", and exits
[17:58:19] <jmkasunich> will running it more than once do harm?
[17:59:24] <jmkasunich> 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
[18:00:06] <jmkasunich> 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
[18:09:21] <jepler> jmkasunich: running it to completion multiple times will add more entries to environment variables like PATH each time.
[18:09:40] <jmkasunich> ok, I was thinking it might be something like that
[18:10:06] <jmkasunich> I put words in the wiki advising a new shell when you change checkouts or switch from sim to RT
[19:20:49] <BigJohnT> jepler: around?
[22:40:32] <cradek> well phooey, I broke the flex coupling
[22:45:36] <skunkworks> for the tach?
[22:45:48] <skunkworks> or between the servo and the leadscrew?
[22:46:07] <cradek> between the leadscrew and resolver/tach
[22:53:20] <cradek> so it gave me a nice runaway - but I was by the button.
[22:56:27] <rayh> ouch. Don't know if I have any of those bellows out there.
[22:58:58] <skunkworks> was it the tach?
[23:00:17] <rayh> Last time I got one it was about $80
[23:03:01] <rayh> BigJohnT, docs/src/code/Code_Notes.lyx need a big rewrite. I'd like to start by breaking it up into chapters.
[23:03:34] <BigJohnT> ok sounds good to me
[23:03:58] <cradek> mcmaster has them for $25. I ordered two :-)
[23:04:09] <rayh> Great.
[23:04:30] <rayh> Does anyone know if the motion section in there is current at all?
[23:04:49] <rayh> I know that the IO sections are not.
[23:04:55] <cradek> 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.
[23:05:17] <cradek> I am narrowing it down [slowly].
[23:05:22] <BigJohnT> rayh: did you get a chance to look at the NML messages section?
[23:05:44] <rayh> Yes and right now I think it is great.
[23:05:57] <BigJohnT> ok :)
[23:06:33] <rayh> cradek those motors are quite responsive. any little play will be magnified a lot.
[23:07:11] <BigJohnT> 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
[23:07:19] <cradek> 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.
[23:07:55] <BigJohnT> I'm thinking if I leave all the g,m and o stuff in main.lyx no links will break
[23:08:15] <cradek> getting ppmc amps and mounting encoders is sounding better and better
[23:08:20] <rayh> Does that feedback package use a split gear with springs for the center drive?
[23:08:23] <cradek> but I'll work on this a while longer.
[23:08:37] <cradek> no, the center gear is solid
[23:08:55] <cradek> split would be smarter - less finicky
[23:09:09] <rayh> So the tach and resolver have an eccentric where they hook in.
[23:09:25] <cradek> yes they are mounted eccentric so you rotate them to adjust the engagement
[23:10:37] <rayh> You're getting there. Just takes time to figure it all out.
[23:10:48] <cradek> yes
[23:11:16] <cradek> and breaking things sometimes...
[23:11:23] <rayh> BigJohnT, I'd say hack up a revised gcode section and see what breaks.
[23:11:46] <BigJohnT> ok will do
[23:12:07] <rayh> I'll do the same here for code notes after a bit.
[23:12:17] <BigJohnT> cool :)
[23:13:16] <BigJohnT> I ended up writing a python scrip to put the info from Alex's spreadsheet into a lyx format...
[23:13:17] <cradek> rayh: do you know if the Z ballscrew has an adjustable nut?
[23:16:02] <BigJohnT> * BigJohnT hears the dinner bell, can't be late for that
[23:16:08] <BigJohnT> ttul