Back
[09:15:11] <jepler> seb_kuzminsky: you should probably say words to niemand sonst / gmoccapy on the mailing list, he is asking there about merging an entirely new feature to 2.7
[10:12:01] <seb_kuzminsky> jepler: i don't see him talking about 2.7 - the branch he linked to is based on master, no?
[10:13:29] <archivist> it is in the message title
[10:43:31] <seb_kuzminsky> oh! heh yep
[12:05:17] <skunkworks> where is the deb for rt_preemt for linuxcnc on wheezy?
[12:05:23] <skunkworks> *jessie?
[12:05:41] <skunkworks> can I add an apt-get source and pull it that way?
[12:05:58] <skunkworks> (I remember seb saying it was on the site)
[12:56:47] <skunkworks> zlog
[13:06:10] <skunkworks> what is the difference between 2.7-rt-preempt sources and the 2.7-uspace?
[13:23:27] <jepler> skunkworks: different words for the same thing
[13:29:53] <skunkworks> ok
[13:29:54] <skunkworks> thanks
[13:40:05] <skunkworks> would this be the latest? inux-image-4.1.0-1-amd64_4.1.18-1linuxcnc_amd64.deb
[13:40:19] <skunkworks> from
http://highlab.com/~seb/linuxcnc/dists/jessie/main/binary-amd64/?C=M;O=A
[13:40:51] <skunkworks> what is the difference between dbg and non dbg?
[13:53:34] <skunkworks> zlog
[14:42:32] <kwallace2> Hello. I'm trying to modify G76 to use a stationary safe x. The safe x part worked okay but I also noticed that the In move for an entry taper should not be synchronized. The beginning of the taper and the threading move should be, as well as an exit taper if needed. I moved the In move code to just before the synch is invoked which can be seen here:
http://wallacecompany.com/tmp/Screenshot-g76_sync_prob-2a.png
[14:43:48] <kwallace2> The plot comes up okay but the run trace doesn't as seen here:
http://wallacecompany.com/tmp/Screenshot-g76_sync_prob-1a.png
[14:44:42] <kwallace2> If I make the In move a rapid it works the way I think it should.
[15:15:42] <kwallace2> Oops, this is with 2.8.0~pre1
[15:46:49] <pcw_home> Can hal files include other hal files?
[16:01:54] <seb_kuzminsky> skunkworks: the apt sources are listed in a bunch of big tables on the buildbot front page
[16:02:47] <seb_kuzminsky> the kernel you named, linux-image-4.1.0-1-amd64_4.1.18-1linuxcnc_amd64.deb, is a regular vanilla kernel i compiled as part of building the new experimental rtai kernel
[16:03:18] <seb_kuzminsky> linux-image-*-dbg contains just the debug symbols for the matching non-dbg linux-image
[16:03:39] <seb_kuzminsky> install linux-image if you want to run that kernel, and install linux-image-dbg if you want to debug a crash dump from that kernel
[16:04:42] <seb_kuzminsky> pcw_home: the halcmd manpage says yes:
[16:04:45] <seb_kuzminsky> source filename.hal
[16:04:45] <seb_kuzminsky> Execute the commands from filename.hal.
[16:12:04] <pcw_home> Just wondering how practical it would be to make hardware independent hal files (mainly structural parts like PID connections)
[16:12:06] <pcw_home> and just have hardware specific include files that link the hardware pins/parameters to generic signals
[16:32:18] <jepler> pcw_home: man halcmd says there's "source"
[16:32:31] <jepler> pcw_home: in a pinch you could also loadusr another halcmd process but eew
[16:32:51] <pcw_home> I'll have to give this a try
[16:33:00] <jepler> argh I failed to see seb answer already
[16:33:24] <jepler> blind spot
[16:33:43] <pcw_home> separating the structure from the names seem like a win
[16:34:05] <jepler> if you want a programming language, you can also use .tcl files
[16:34:08] <jepler> configs/sim/axis/axis_9axis.ini:HALFILE = LIB:basic_sim.tcl
[16:34:50] <jepler> I think the modest library of .tcl files is dewey's doing
[16:35:59] <pcw_home> Yeah I looked at that before
[17:35:07] <kwallace2> The above ^^^ doesn't work in 2.6.12 either.
[18:15:22] <Roguish> hey all. is it possible to modify the primary Touchy gui screen? I would like to remove some tabs and alter others. like a large DRO
[18:16:37] <Roguish> I see a touchy glade file, but do not see how the some of the tabs screens connect to linuxcnc
[18:39:09] <skunkworks> then what is the latest rt_preempt?
[18:42:41] <kwallace2> Crud, or yay, I figured out why one of the threading legs was being by-passed. I copied a portion of a g-code file to get my sample threading file. It turns out I didn't have an F value so the G76 canned cycle just by-passed the normal feed bits. It seems to me G76 should probably check for a missing F? Anyway, I added F 5 to the g-code and my edits work fine.
[19:00:22] <pcw_home> 4.6.7-rt11 :-)
[21:52:36] <skunkworks> zlog
[21:52:48] <skunkworks> heh - I didn't want to have to build one ;)
