Back
[00:00:13] <Skunkemc> *it displays the program but doesn't allow you to navigate through it. (leaves you at the end)
[01:10:02] <cradek> I would have never thought to try clicking a different program while one is running - I bet it does a wrong thing
[01:10:08] <cradek> does it show an error at the bottom?
[01:11:47] <cradek> there may be many ways it doesn't yet protect you from doing wrong things
[01:21:09] <Skunkemc> can't do that (EMC_TASK_PLAN_OPEN) in auto mode with the interpreter waiting
[01:21:32] <cradek> ok, so it fails, but touchy incorrectly reads in the new program anyway
[01:23:41] <Skunkemc> oops
[01:24:00] <cradek> whee, jr is running a linuxcnc branch again (random_toolchange)
[01:24:10] <Skunkemc> It is very clean and self explanatory
[01:25:37] <cradek> did you hook up buttons or wheel?
[01:26:19] <Skunkemc> only thing I can think of is it might be nice to have a list of active g-codes. and velocity - I see it in preferences but it looks like it is in units/second.
[01:26:23] <Skunkemc> NO
[01:27:51] <Skunkemc> No
[01:28:04] <cradek> yeah I should scale the velocity in status
[01:28:17] <cradek> I could sure put active gcodes on the status screen
[01:45:05] <Skunkemc> oh - and run from line (You probably don't use it) is probably impossible in long programs (you can only move down one line at a time)
[01:45:28] <cradek> it jumps to lines with N in them
[01:45:40] <cradek> the idea is that you can mark places that make sense to restart, that way
[01:45:46] <Skunkemc> ah - ok
[01:45:52] <cradek> like tool changes, maybe rapids above the work
[01:47:42] <Skunkemc> that is why I couldn't seem to move down in some programs.. No n numbers :)\
[01:48:42] <cradek> right. [needs documentation doesn't it]
[01:49:01] <cradek> on the boss I started putting an N by each T. you can jump to the N words.
[01:50:50] <Skunkemc> neat
[01:52:43] <Skunkemc> it is really neat how everything scales as you change fonts. :)
[01:53:20] <cradek> yeah I think you can use it on any screen size, I tried down to 800x600
[01:53:29] <cradek> touch screens can be pretty low res by today's standards
[01:54:25] <Skunkemc> heh
[01:57:13] <Skunkemc> oh - time for bed. Again - very cool.
[02:44:32] <CIA-82> EMC: 03cradek 07master * re6545d865042 10/src/emc/usr_intf/touchy/emc_interface.py: sam suggests velocity in /min, not /sec
[02:44:33] <CIA-82> EMC: 03cradek 07master * r580aa690d155 10/src/emc/usr_intf/touchy/ (emc_interface.py touchy.glade touchy.py): sam suggests adding active gcode readout
[02:46:09] <CIA-82> EMC: 03cradek 07random_toolchange * rc83c69c6c4ab 10/src/emc/usr_intf/touchy/ (emc_interface.py touchy.glade touchy.py): Merge branch 'master' into random_toolchange
[02:50:51] <cradek> git doesn't get in my way anymore. it just does the right things.
[02:51:03] <cradek> I'm sure glad we switched
[06:50:38] <alex_joni> morning micges_work
[06:54:57] <micges_work> hi alex_joni
[07:08:17] <alex_joni> what's up?
[07:10:33] <micges_work> not much
[07:12:22] <micges_work> database programming (bleh)
[07:12:25] <alex_joni> tried touchy ?
[07:13:05] <micges_work> nope
[07:18:44] <alex_joni> I was planning to do that now.. but having trouble pulling from git
[07:19:05] <alex_joni> ! [rejected ] joints_axes3 -> joints_axes3 (non fast forward)
[07:19:44] <micges_work> switch to ja3 and try again
[07:20:00] <micges_work> I run it now, very cool
[07:20:58] <micges_work> try git pull --rebase
[07:21:12] <alex_joni> --rebase didn't work
[07:21:14] <alex_joni> but --force did
[07:23:24] <micges_work> emc has touchy config in sim
[07:27:54] <micges_work> alex_joni: do you know how to run pygtk program in windows?
[07:29:16] <alex_joni> hmm.. never tried
[07:29:49] <alex_joni> cradek: touchy fails because I don't have ~/emc2/nc_files
[07:32:28] <alex_joni> cradek: if the folder is empty, and one clicks the loaded file area, then I get a traceback:
http://pastebin.ca/1636763
[07:35:19] <micges_work> touchy don't start if you don't have ~/emc2 dir
[07:36:17] <alex_joni> hmm.. wonder how you set parameters for g-codes in MDI
[07:37:06] <alex_joni> ah, it works for some codes (G1, etc) but doesn't for M66 for example
[07:43:01] <alex_joni> cradek: minor nag: select for handwheel jogging: then Y, and another increment, switching to FO and back to jogging resets the selected axis and increment
[12:27:41] <CIA-82> EMC: 03jepler 07v2_3_branch * r0dade5e2f37e 10/configs/hm2-servo/hm2-servo.hal: use the proper .ini variable for the pid maxoutput
[12:27:42] <CIA-82> EMC: 03jepler 07v2_3_branch * r6d913485b606 10/configs/hm2-servo/hm2-servo.hal: disable driver debug output by default
[12:27:43] <CIA-82> EMC: 03jepler 07v2_3_branch * r592b46cc068a 10/configs/hm2-servo/ (9 files): Fix homing in the hm2-servo config.
[12:27:45] <CIA-82> EMC: 03jepler 07v2_3_branch * rdb186f578a73 10/configs/hm2-servo/ (10 files): better description of this config, and better comments inside
[12:27:48] <CIA-82> EMC: 03jepler 07v2_3_branch * rf5504e2f8e1e 10/debian/changelog: note new fixes
[12:50:10] <skunkworks_> logger_dev: bookmark
[12:50:10] <skunkworks_> Just this once .. here's the log:
http://www.linuxcnc.org/irc/irc.freenode.net:6667/emcdevel/2009-10-22.txt
[13:03:33] <cradek> alex_joni: I can't reproduce the problem where switching to FO then back to jogging resets the scale
[13:04:25] <cradek> M66 is not handled in MDI because it's not on the gcode quickref which is what I used as reference
[13:08:30] <alex_joni> heh, ok..
[13:08:39] <alex_joni> anything I can do to help debug 1?
[13:09:02] <cradek> yes, troubleshoot and report back :-)
[13:10:28] <alex_joni> I would have thought you're going to say: troubleshoot and commit a fix :D
[13:11:14] <CIA-82> EMC: 03cradek 07master * r37104b94d0c5 10/src/emc/usr_intf/touchy/mdi.py: alex says add M66, M100..M199
[13:11:24] <cradek> that's another valid approach you might take
[13:11:47] <cradek> but seriously, I've been using it for a while and have never seen that, and when I try it here (different computer, using mouse) it also works fine (remembers the axis and increment)
[13:12:00] <cradek> btw, do you mean the hal outputs are wrong, or the buttons on screen change?
[13:12:23] <cradek> brb
[13:24:41] <alex_joni> buttons on the screen change
[13:24:55] <alex_joni> not sure about the hal outputs, didn't look at those
[13:24:56] <alex_joni> bbl
[13:36:37] <cradek> that's bizarre then
[13:38:15] <cradek> g'morning matt
[13:38:15] <CIA-82> EMC: 03cradek 07master * r5aa17a7d7210 10/src/emc/usr_intf/touchy/mdi.py: too early for comments to become stale already
[13:39:20] <mshaver> Hey Chris!
[13:42:02] <CIA-82> EMC: 03cradek 07master * r40a6dbecb50c 10/src/emc/usr_intf/touchy/mdi.py: fix stupid breakage of g/m codes with . in them
[13:42:03] <cradek> jeez, it's too learly for programming
[13:42:08] <cradek> and too early
[13:46:28] <skunkworks_> it keeps the axis and increment here also.
[13:47:01] <cradek> huh
[13:47:34] <skunkworks_> (does what it should)
[13:48:08] <cradek> skunkworks_: I made the changes you suggested last night
[13:48:28] <skunkworks_> oh - cool. I will re-git it.
[13:54:33] <cradek> hm, touchy and axis both show an extra and wrong G0 in active gcodes
[13:55:34] <JT-Work> do you load touchy with an entry in the ini file like axis?
[13:55:54] <cradek> yes, also there's a sim/touchy config in git
[13:56:13] <JT-Work> ok thanks
[13:56:35] <cradek> if you change an existing config to use touchy, you will need to write touchy.hal which hooks up the controls it needs
[13:57:02] <JT-Work> ok
[13:57:23] <jepler> cradek: that's a hardcoded name for a hal file that is executed after touchy creates its hal pins?
[13:57:24] <cradek> some instructions:
http://git.linuxcnc.org/gitweb?p=emc2.git;a=blob;f=src/emc/usr_intf/touchy/design.notes;hb=HEAD
[13:57:30] <cradek> jepler: yes
[14:00:37] <cradek> someone sure crapped up Interp::write_g_codes
[14:00:51] <cradek> in particular, the comment is baffling
[14:01:06] <cradek> it never writes to gez[12], which causes that extra G0
[14:02:03] <Dave911> What do you guys use as a reference for creating Python scripts? For instance a book? A website?
[14:02:25] <jepler> docs.python.org is a very thorough reference for the Python standard library
[14:02:59] <Dave911> Cool, thanks, I knew I was missing something ....
[14:10:54] <CIA-82> EMC: 03mshaver 07master * r2e5e97f6ae26 10/configs/smithy/ (622.hal 622_4axis.hal 924.hal):
[14:10:54] <CIA-82> EMC: Add options to Sieg HAL files to allow for different spindle drive firmware
[14:10:54] <CIA-82> EMC: versions. Early drive firmware required a low pass filter on the velocity
[14:10:54] <CIA-82> EMC: command signal to prevent drive faults during acceleration. Later drives
[14:10:54] <CIA-82> EMC: implement this filtering internally, so the HAL lowpass filter gain must be set
[14:10:54] <CIA-82> EMC: to 1.0 to avoid sluggish spindle response.
[14:13:31] <cradek> hm I bet it was taken out when we switched to the big swirl of override overrides
[14:13:42] <cradek> http://www.linuxcnc.org/docs/devel/html/gcode_main.html#sec:Overrides
[14:13:51] <cradek> not sure how to show the state of all this mess
[14:16:49] <mshaver> On this last commit I got, "! [rejected] v2_3_branch -> v2_3_branch (non-fast forward)". I'd like my changes to go into both master and v2_3_branch. Do I have to switch branches, copy the files and commit in 2_3 also, or can I somehow turn on "fast forward"?
[14:17:27] <cradek> use checkout to get v2_3_branch. do a pull to update it. use git cherry-pick to apply your change to that branch too. then push.
[14:18:50] <mshaver> Thanks!
[14:19:47] <CIA-82> EMC: 03cradek 07v2_3_branch * rbede96fc9a94 10/src/emc/rs274ngc/interp_write.cc: fix bogus extra G0 in the active gcode readouts
[14:20:25] <CIA-82> EMC: 03cradek 07master * rf898a4ba557b 10/src/emc/rs274ngc/interp_write.cc: fix bogus extra G0 in the active gcode readouts
[14:20:26] <CIA-82> EMC: 03cradek 07master * r4ef0554d517f 10/configs/smithy/ (622.hal 622_4axis.hal 924.hal): Merge branch 'master' of ssh://
[email protected]/git/emc2
[14:51:19] <CIA-82> EMC: 03mshaver 07master * r877407641575 10/configs/smithy/924eztrol.hal: Fix whitespace error.
[14:51:20] <CIA-82> EMC: 03mshaver 07master * r56c3b59d536a 10/configs/smithy/924eztrol.hal: Start adding lathe support for Smithy's eztrol program with this postgui halfile.
[15:01:34] <CIA-82> EMC: 03mshaver 07v2_3_branch * r97ffa00b8793 10/configs/smithy/ (622.hal 622_4axis.hal 924.hal):
[15:01:34] <CIA-82> EMC: Add options to Sieg HAL files to allow for different spindle drive firmware
[15:01:34] <CIA-82> EMC: versions. Early drive firmware required a low pass filter on the velocity
[15:01:34] <CIA-82> EMC: command signal to prevent drive faults during acceleration. Later drives
[15:01:35] <CIA-82> EMC: implement this filtering internally, so the HAL lowpass filter gain must be set
[15:01:37] <CIA-82> EMC: to 1.0 to avoid sluggish spindle response.
[15:01:39] <CIA-82> EMC: 03mshaver 07v2_3_branch * r7377aa62665e 10/configs/smithy/924eztrol.hal: Fix whitespace error.
[15:01:42] <CIA-82> EMC: 03mshaver 07v2_3_branch * r983169271771 10/configs/smithy/924eztrol.hal: Start adding lathe support for Smithy's eztrol program with this postgui halfile.
[15:01:52] <skunkworks_> cradek: works great! :)
[15:02:51] <mshaver> I'm slowly "gitting" the hang of this...
[15:06:44] <cradek> takes a while...
[15:07:28] <cradek> +net Xmax eztrol.x-negative-limit
[15:07:33] <cradek> why this?
[15:11:20] <cradek> well I guess there are two questions
[15:12:03] <cradek> 1- why use hal instead of getting that from the stat buffer? 2- why does the pos limit switch go to eztrol.neg-limit etc? they all look backward
[15:41:51] <cradek> oh hmm, maybe in stat you can't tell which limit it's on
[15:42:08] <cradek> (not that it should be hard to figure out when looking at the machine...)
[15:45:04] <cradek> skunkworks_: are you running something with it or just playing?
[15:45:19] <skunkworks_> just playing... Sorry
[15:45:25] <cradek> I'm wondering if anyone will really use it. You pretty much have to build a panel based on it.
[15:45:39] <skunkworks_> but not much to build..
[15:46:13] <cradek> my kick-ass panel:
http://timeguy.com/cradek-files/emc/jr.jpg
[15:46:38] <cradek> I should probably put labels on stuff...
[15:46:39] <skunkworks_> very clean
[15:46:52] <skunkworks_> what is the meter for? spindle load?
[15:46:56] <cradek> yes
[15:47:01] <skunkworks_> neat
[15:48:04] <skunkworks_> have you made the meter move yet?
[15:48:25] <cradek> it's not wired to the vfd yet - but the vfd does support it I'm pretty sure
[15:49:02] <cradek> it takes 6 or so amps just to turn the spindle with no load - not sure how much use the meter will be
[15:49:12] <cradek> the vfd doesn't have a "load" output, only current
[15:50:47] <cradek> I've drilled some big holes in steel to see if it still has any power down at 500 rpm - yes it does
[15:53:22] <skunkworks_> :)
[15:59:14] <skunkworks_> people have been asking about a touch screen able emc gui.. Also this looks more 'industrial control'.
[15:59:19] <skunkworks_> (to me)
[16:00:37] <cradek> yeah I wrote it because none of our guis worked well on a touch screen, and they really all needed keyboards (and even mice), which is bad for an industrial setup
[16:01:01] <cradek> there are compromises everywhere, but I think it's ok
[16:02:01] <cradek> you cannot MDI g0 x[#123*atan[#234]/[456]]
[16:02:18] <cradek> (or however you spell it) but who cares
[16:03:22] <cradek> I have done some work at the panel - MDI for drilling, continuous jog at slow speed for milling some slots, etc. it works comfortably.
[16:04:21] <cradek> if you enable jogging then switch to MV, the wheel changes the continuous jog speed but the continuous jog switches still work
[16:04:45] <cradek> (continuous jogs are at MV speed)
[16:05:47] <cradek> hm, I could have it send a new jog command if MV changes while jogging - then you could change speed without stopping by just turning the wheel while holding the switch
[16:06:14] <cradek> that is a lot like how BOSS worked (the FO pot was the only way to control continuous jog speed)
[16:10:50] <cradek> hm, if I send an mdi command while the previous one is still running, it doesn't queue it and wait
[16:10:57] <cradek> I'm pretty sure in AXIS you can type ahead
[16:11:01] <cradek> wonder how that works
[16:14:24] <cradek> ah I see it, touchy is sending a mode set, which nukes the running command
[16:23:28] <CIA-82> EMC: 03cradek 07master * r54bd64cc81e2 10/src/emc/usr_intf/touchy/mdi.py: mdi commands should politely queue up, not interrupt each other
[17:16:13] <jepler> hm, I have motion getting a latched position from software encoder, but something between there and task is putting the wrong (feedback?) number in
[17:16:58] <jepler> or maybe I'm misinterpreting things
[17:16:59] <cradek> I don't follow
[17:17:10] <cradek> what do you mean latched?
[17:17:15] <cradek> oh the probe thing?
[17:17:30] <jepler> yeah
[17:17:47] <cradek> what are you seeing?
[17:18:24] <jepler> well, I've put debugging statements at each level and I'm also watching the position-latched in halmeter
[17:18:55] <jepler> position-latched is always the value I expect (Z = 1 count less than zero) but the values ultimately printed in the logfile are different
[17:19:25] <cradek> the probe result interp variables are wrong?
[17:19:56] <jepler> well, somewhere between hal and there it gets wrong
[17:20:00] <jepler> I must just have overlooked something
[17:20:15] <cradek> emcmotStatus->probedPos = emcmotStatus->carte_pos_fb;
[17:20:21] <cradek> you changed this in control.c?
[17:21:12] <jepler> yes
[17:21:30] <jepler> it's supposed to get the latched joint position and call kinematicsInverse
[17:21:44] <cradek> is it right so far then?
[17:25:10] <jepler> no, it seems like the joint position is already wrong in process_probe_inputs
[17:25:28] <jepler> + joint->motor_pos_latch = *(joint_data->motor_pos_latch);
[17:25:31] <jepler> + joint->pos_latch = joint->motor_pos_latch -
[17:25:31] <jepler> +(joint->backlash_filt + joint->motor_offset);
[17:25:38] <jepler> +*(joint_data->joint_pos_latch) = joint->pos_latch;
[17:26:13] <jepler> 32770 float OUT 0.8331667 axis.2.joint-pos-latch
[17:26:15] <cradek> eww, backlash
[17:26:21] <jepler> probe Z=0.83150
[17:26:45] <cradek> hm
[17:27:05] <jepler> (yeah, though that's a sideline -- what my code above is intended to do is assume that the backlash/screw comp value of the feedback position and latched position are "the same enough")
[17:27:29] <cradek> I bet that's a perfectly fine assumption
[17:28:34] <jepler> 32770 float OUT 0.8331667 axis.2.joint-pos-latch
[17:28:34] <jepler> 32770 float IN 0.8333333 axis.2.motor-pos-latch <== lz
[17:28:35] <jepler> hmm
[17:28:39] <jepler> does servo-sim have backlash or screw comp?
[17:28:56] <jepler> or motor offset..
[17:29:19] <cradek> it has X screw comp
[17:59:15] <jepler> oh, am I calling the opposite kinematics function from what I want?
[18:03:18] <jepler> durrrr that was exactly it
[18:04:47] <jepler> Z-0.167000 probed with F5.000000
[18:04:49] <jepler> Z-0.167000 probed with F100.000000
[18:04:54] <jepler> I believe that's it!
[18:05:09] <cradek> wooo!
[18:06:24] <cradek> dang, I wish I would have noticed that for you, sorry
[18:06:35] <jepler> np
[18:10:15] <jepler> hm, smartprobe ends up looking a bit odd with high feedrates
[18:10:32] <cradek> too much extra travel?
[18:10:37] <jepler> yeah, basically
[18:23:19] <jepler> the downside to what I've written is it breaks all existing probing configs
[18:24:38] <cradek> just need a new hal connection?
[18:24:58] <jepler> yeah -- just hook the same old feedback to the new pins as well
[18:25:05] <cradek> meh
[18:25:11] <jepler> probably I should call this something besides "latch" in hal
[18:25:15] <jepler> -probed ?
[18:25:24] <jepler> axis.2.{joint,motor}-pos-probed
[18:25:40] <cradek> sure that sounds descriptive
[18:25:48] <jepler> for the encoder I think it makes sense to call it "latch"; you might use the latch for other purposes that I haven't imagined yet
[18:26:21] <cradek> ok
[18:35:06] <CIA-82> EMC: 03mshaver 07master * r279170f412bd 10/configs/smithy/ (1240eztrol.hal 622eztrol.hal 924eztrol.hal eztrol.hal): Fix reversed connection of limit switch signals to eztrol hal pins as observed by cradek on irc.
[18:35:17] <cradek> heh
[18:35:27] <mshaver> though you'd like that
[18:35:32] <cradek> :-)
[18:35:33] <mshaver> thought
[18:35:45] <cradek> so the eztrol world is not as crazy as I feared!
[18:36:00] <mshaver> btw is status doesn't have pos & neg limits, it should
[18:36:50] <mshaver> no, it's not. but due to the way it works (now) the only thing to be done is to "override limits", log off & go on, so noone whould really have noticed this.
[18:36:55] <cradek> motion knows, because it limits jogs to the correct direction when you override limits.
[18:37:12] <cradek> it's probably not in the stat buffer because jmk and I were too tired to change all the guis
[18:37:30] <cradek> (seriously, I think we did the directional jogs after everyone else went to bed one night at workshop)
[18:37:43] <mshaver> if you put it in stat, we can remove these hal pins!
[18:38:13] <mshaver> actually, i don't know that eztrol even indicates the limit polarity...
[18:38:22] <cradek> then it can use stat!
[18:38:32] <jepler> status.motion.axis[i].minHardLimit status.motion.axis[i].maxHardLimit
[18:38:35] <mshaver> yes, exactly!
[18:38:37] <cradek> (you'd have to be quite without clue to not know which limit switch you were on)
[18:39:03] <jepler> (or did I miss the point again)
[18:39:07] <mshaver> jepler: so it is in stat?
[18:39:26] <cradek> I admit I didn't even look
[18:39:41] <mshaver> if so, I'll tell Wally to use the status, rather than this hal stuff!
[18:39:48] <jepler> that's what axis uses to display the on-limit symbol
[18:40:03] <jepler> though inexplicably the C++ code encodes it in a bitfield before sending it to Python!
[18:40:12] <jepler> if(s->status.motion.axis[i].maxHardLimit) v |= 2;
[18:40:29] <mshaver> jepler: but the arrow always faces left, doesn't it (towards the digits)
[18:40:48] <jepler> mshaver: yes, there's only one symbol
[18:41:46] <mshaver> and the standard message only says ~ "axis 0 on a limt"
[18:42:03] <mshaver> not, "axis 0 on pos limit"
[19:07:35] <CIA-82> EMC: 03jepler 07master * r09ea88a507c8 10/tests/counter-encoder.0/test.hal: prefer net to linkxx
[19:07:36] <CIA-82> EMC: 03jepler 07master * r5a39e13fc0c4 10/docs/man/man9/encoder.9: fix redundant markup
[19:07:37] <CIA-82> EMC: 03jepler 07master * r0626c8f85eed 10/src/hal/components/encoder.c: style: convert encoder to use _newf-family functions
[19:07:39] <CIA-82> EMC: 03jepler 07master * rb039b2ddf1cf 10/configs/sim/servo_sim.hal: correct thread order: produce count then count it, not the other way around
[19:07:41] <CIA-82> EMC: 03jepler 07master * r76fbfaa3a2ba 10/src/hal/hal_lib.c: debugging tool
[19:25:22] <CIA-82> EMC: 03jepler 07master * r1f501fb253e5 10/src/hal/components/encoder.c: Provide a position latch in the software encoder
[19:25:27] <CIA-82> EMC: 03jepler 07master * r4b1601727a6f 10/src/hal/components/sphereprobe.comp: new component to ease testing of high-resolution probing
[19:25:30] <CIA-82> EMC: 03jepler 07master * r3817ad5b39f1 10/configs/sim/servo_sim.hal: make it possible to look at how encoder latch is working
[19:25:33] <CIA-82> EMC: 03jepler 07master * r709520da77d7 10/configs/sim/servo_sim.hal: hook up high-resolution probe signals
[19:25:36] <CIA-82> EMC: 03jepler 07master * r799409d259e2 10/src/emc/motion/ (control.c mot_priv.h motion.c motion.h): Use a high-resolution probe result
[19:25:41] <CIA-82> EMC: 03jepler 07master * rd6d41e6eda8f 10/docs/man/man9/ (encoder.9 motion.9): document new functionality
[19:26:25] <cradek> that is super slick, I can't wait
[19:26:37] <jepler> it still needs the hm2-specific part written..
[19:26:42] <jepler> I'll start looking at that
[19:27:41] <cradek> want to come over and play tonight?
[19:28:10] <jepler> yeah, I think I might
[19:35:43] <jepler> want to do dinner too? I think I'm abandoned.
[19:36:36] <cradek> jepler: I'll never eat again
[19:36:54] <alex_joni> heh
[19:37:13] <alex_joni> if you care, I'll fedex you a bottle :P
[19:37:23] <alex_joni> make that a bottle each
[19:44:18] <cradek> oh my, you even wrote docs
[19:50:36] <jepler> oh my, hostmot2 counter wrapping
[19:50:42] <jepler> * jepler 's head explodes
[19:51:09] <cradek> eek, how to test that
[19:55:38] <jepler> jepler@install2:~/emc2-dev$ git pull india:emc2-dev master
[19:55:40] <jepler> that's cool
[19:56:02] <jepler> I realized my WIP hostmot2 driver was on a sim-only system, so I can't even see if it compiles
[19:56:20] <jepler> but I could pull it from that machine to one with a realtime kernel without going through any intermediate steps
[19:56:46] <cradek> host:path uses ssh?
[19:56:49] <jepler> yeah
[19:58:22] <cradek> that is cool
[19:59:55] <jepler> and paths can be relative to ~ which also makes for nice shorthand
[20:03:10] <jepler> now it compiles; it must be right
[20:05:59] <cradek> the hm2 part already?
[20:06:25] <jepler> yeah
[20:06:28] <cradek> wow
[20:06:35] <cradek> going to stick it in linuxcnc git somewhere?
[20:06:38] <jepler> perhaps you didn't hear the sarcasm in my voice
[20:06:45] <cradek> wellll
