#linuxcnc-devel | Logs for 2015-02-14

Back
[00:06:26] <tjtr33> wiki page edited, review please
[00:06:40] <tjtr33> thx seb, thx dgarr, thx pcw
[00:06:43] <tjtr33> gnite
[00:10:04] <seb_kuzminsky> looks good tjtr33, thanks
[10:27:45] <seb_kuzminsky> zlog: link
[11:18:06] <KGB-linuxcnc> 03Sebastian Kuzminsky 05feature/spiral-arc-handling-2.7 485966a 06linuxcnc 10src/emc/rs274ngc/interp_internal.hh tp: restore arc radius relative error threshold to 0.1% * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=485966a
[11:18:06] <KGB-linuxcnc> 03Sebastian Kuzminsky 05feature/spiral-arc-handling-2.7 95873cd 06linuxcnc 10(7 files) tests: more complete tests of bad arcs * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=95873cd
[11:48:50] <KGB-linuxcnc> 03Sebastian Kuzminsky 05feature/spiral-arc-handling-2.7 9dc0208 06linuxcnc 10tests/interp/bad/bad-arc.small.imperial.center-format.ngc 10tests/interp/bad/bad-arc.small.metric.center-format.ngc tests: specify small bad arc errors more clearly * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=9dc0208
[11:54:18] <KGB-linuxcnc> 03Sebastian Kuzminsky 05feature/spiral-arc-handling-2.7 82b9fc6 06linuxcnc 10(12 files) tests: update good-arc tests with new tolerances * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=82b9fc6
[11:54:54] <seb_kuzminsky> i think the spiral-arc branch is in good shape now
[11:55:16] <seb_kuzminsky> i'm taking a vacation with my family for the weekend, i'll be back on sunday night or monday
[11:55:31] <seb_kuzminsky> if no one's found any problems with the branch by then i'll merge it into 2.7
[11:56:53] <kwallace2> seb_kuzminsky, I hope you have a good vacation.
[11:57:25] <seb_kuzminsky> thanks :-)
[11:57:53] <seb_kuzminsky> or if someone else wants to merge it while i'm gone that's fine too, i'm happy with it now
[12:59:20] <dgarr> tjtr33 , seb_kuzminsky revised per seb's suggestion; http://www.panix.com/~dgarrett/stuff/v2-hal_lib-change-.time-item-from-parameter-to-pin.patch
[13:05:47] <dgarr> pcw_home: this commit (2.7) provides a halfile that will show common errors, omissions: 1) functions with no addfs, 2) signals with no inputs, 3) signals with no outputs
[13:06:17] <dgarr> http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=commitdiff;h=a8bef4174584c11ea4b7fe824a0f68cb13c9d46d
[13:32:40] <pcw_home> Thats great, especially for halfiles that have stuff scattered about
[14:22:50] <skunkworks> can I tell what version a git directory has been 'maked'
[14:23:17] <skunkworks> I can do a git describe - but I don't know if it was compiled to that version
[14:23:26] <skunkworks> if that makes sensel
[14:23:28] <skunkworks> sense
[14:25:16] <micges> version will be compiled in so it will show in terminal after ./linuxcnc
[14:26:36] <micges> if that's what you asking
[14:27:05] <skunkworks> I see that - but that give the LINUXCNC - 2.7.0~pre2
[14:27:09] <skunkworks> I would like to know
[14:27:33] <skunkworks> v2.7.0-pre2-398-gc6b7502
[14:28:26] <micges> I think that magic is in mk
[14:29:25] <skunkworks> ah
[14:29:38] <skunkworks> I guess I just make clean and make ;)
[14:30:06] <micges> if it's not atom then yeah
[14:30:40] <micges> make -j2 if you have multicore cpu
[14:32:06] <micges> skunkworks: http://ibin.co/1reBDsCXvDgH
[14:32:31] <skunkworks> cool
[14:32:38] <skunkworks> how is it going?
[14:33:10] <micges> no spikes at all and blending is working
[14:33:27] <skunkworks> wow!
[14:34:23] <micges> working on correction position undershoot when have deriative of high acc/vel values
[14:34:34] <micges> and feed override during move
[14:36:42] <kwallace2> skunkworks, how is your healing going?
[14:37:06] <skunkworks> good - 4 more weeks of no lifting. Pretty sore at the end of the day still though
[14:38:56] <kwallace2> I suppose, if you are feeling better each day, that's good.
[14:41:06] <skunkworks> right
[14:44:11] <kwallace2> I saw your comments on the CNCZone/Tormach forum. Are you going to buy one? :)
[14:46:26] <skunkworks> kwallace2: heh - no. I did get to go down to tormach (it is relatively close to me). Cool machines.
[14:46:49] <skunkworks> they had a machinekit get-togather a year or 2 ago
[14:47:19] <skunkworks> My work should buy one of the lathes
[14:49:07] <skunkworks> They are very impressed with your wizard writing ability :)
[14:50:55] <kwallace2> I keep wondering why they have anything to do with me, but I'm not going to ask.
[14:51:53] <skunkworks> heh
[14:52:43] <skunkworks> I suppose it wouldn't be easy for them to make a rigid tapping kit - They probably don't have enough inputs in one printer port.
[14:54:44] <kwallace2> They are using only one port on a 5i25, so there is another port free.
[14:57:27] <skunkworks> sure - But most people currently with the mills have printer ports.
[14:57:50] <skunkworks> I love that they are using mesa
[15:06:06] <kwallace2> I didn't consider that older Tormachs might be parallel port only.
[15:43:13] <kwallace2> The PP might me fast enough for rigid tapping but just barely. The spare 5i25 port would do just fine. I have an upgrade in mind that uses an embedded toothed steel ring in the spindle pulley. The sensors are Allegro tooth sensors. The next problem is in casting the sensor and PCB in a package that can bolt under the pulley.
[15:55:36] <skunkworks> the 5i25 will defiantly help but people have tapped with just the printer port
[16:02:57] <kwallace2> The only problem I have with the PP is that some users will expect the encoder to function in the full RPM range, which is about 100 RPM (easy peasey) to 5140 RPM (not even close). My guess is the the PP will peter-out at about 500 RPM ( maybe a little more), which is probably fine for most tapping, but the UI will need to manage expectations.
[16:03:25] <pcw_home> You dont need a terribly high resolution encoder for rigid tapping especially you do position interpolation
[16:03:36] <pcw_home> if you do
[16:04:29] <pcw_home> One advantage of 5I25 is that you dont need a base thread, or even very good latency
[16:05:40] <kwallace2> I rather fancy an encoder with 50 or 100 pulses per rev.
[16:07:50] <kwallace2> Plus, a 5i25 could be part of the upgrade.
[16:10:54] <pcw_home> skunkworks: I got my laptop to test hm2_eth
[16:10:55] <pcw_home> it should be a good test since it has dreadful latency :-)
[17:16:07] <KGB-linuxcnc> 03Dewey Garrett 052.7 01f42b9 06linuxcnc 03docs/src/hal/images/sim_pin.png 03docs/src/hal/images/simulate_probe.png 10docs/src/hal/tools.txt 10scripts/simulate_probe tools.txt: provide some command line help info * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=01f42b9
[19:54:56] <KGB-linuxcnc> 03Dewey Garrett 052.7 ffd212c 06linuxcnc 10(5 files in 4 dirs) Latency_Test.txt: describe other latency utils * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=ffd212c
[19:54:56] <KGB-linuxcnc> 03Dewey Garrett 052.7 7109b12 06linuxcnc 10docs/src/hal/parallel_port.txt 10docs/src/install/Latency_Test.txt hal/parallel_port.txt restore text for Port Address' * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=7109b12
[22:45:42] <KGB-linuxcnc> 03Dewey Garrett 052.7 e4fa85c 06linuxcnc 10docs/src/config/images/latency-histogram.png latency-histogram.png: scale to 800px wide * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=e4fa85c