Back
[06:55:53] <jsskangas_> jepler: updating to 2.7.xx helped litle, but I isolated problem to halui.feed-override.counts
[06:57:11] <jsskangas_> if i connect my analog value to control this it will some how create lagness to jog signals
[06:57:48] <jsskangas_> are there possible to that tryes to write same pin?
[06:57:55] <jsskangas_> or somethig?
[07:02:24] <jsskangas_> I mean that axis and halui are trying to use same pin or similar?
[08:40:19] <jthornton> is there a command line way to see if linuxcnc-uspace is installed vs the rtai version?
[08:45:14] <jepler> jt: python -c 'import hal; print hal.is_userspace'
[08:47:01] <jthornton> thanks
[08:50:47] <jepler> jsskangas_: is the input to halui feed-override stable in all bits, or is it changing even when you're not adjusting the trimpot or whatever? if the input is changing all the time, halui is issuing a storm of NML feed override messages. messages are processed in the order they're received, and there may be a limit on how frequently task processes a message too
[08:51:14] <jepler> there are debug flags you can turn on in the inifile that will show you all nml messages being sent. if they are constantly being sent even while you're not touching your user interface elements, this could be the problem.
[08:51:24] <jepler> or maybe there's simply a bug in halui's feed-override function and somebody needs to debug it.
[08:52:13] <jthornton> cool, found that and more in halmodule.cc
[08:53:42] <jepler> man rtapi_is for information about one important limitation of is_realtime: if it's a RIP where you haven't "sudo make setuid", is_realtime will still say 1 / true
[10:32:23] <jsskangas_> jepler: ok its not totally stable, but nether is jog feed witch is connected
[10:32:26] <jsskangas_> as well
[10:32:36] <jsskangas_> and spindle override
[10:33:29] <jsskangas_> with all other connected it works fine, but even connecting only feed over ride make it lagging
[12:14:17] <jepler> I wonder how much longer humans would win at games like chess or go if their computerized components are also limited to ~100W.
[12:20:46] <jepler> s/components/opponents/
[12:59:27] <archivist> humans should be able to team up in opposition
[13:00:01] <archivist> unfair to use multiple processors against the single human
[13:39:28] <KGB-linuxcnc> 03Dewey Garrett 05joints_axes12 067a046 06linuxcnc 10src/emc/motion/control.c 10src/emc/usr_intf/axis/scripts/axis.py motion/control.c update teleop_tp.curr_pos * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=067a046
[13:39:28] <KGB-linuxcnc> 03Dewey Garrett 05joints_axes12 0f0e97c 06linuxcnc 10configs/sim/axis/ldelta.ini 10configs/sim/axis/ldelta_demo.ini ldelta demos: revise world limits * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=0f0e97c
[14:09:58] <linuxcnc-build> build #2153 of 1405.rip-wheezy-armhf is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1405.rip-wheezy-armhf/builds/2153 blamelist: Dewey Garrett <dgarrett@panix.com>
[14:09:59] <linuxcnc-build> build #3974 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/3974 blamelist: Dewey Garrett <dgarrett@panix.com>
[14:26:52] <seb_kuzminsky> Segmentation fault
[14:26:52] <seb_kuzminsky> make: *** [.html-images-stamp] Error 139
[14:27:31] <seb_kuzminsky> i think my odroid may be failing
[14:27:35] <seb_kuzminsky> the fan has stopped :-/
[14:27:40] <jepler> seb_kuzminsky: yuck
[14:33:22] <seb_kuzminsky> 13:07:44 up 113 days, 18:29, 1 user, load average: 0.00, 0.05, 1.08
[14:34:36] <jepler> the fanless heatsink works much better than a stopped fan, if you still have the heatsink somewhere at the bottom of a pile.
[14:42:06] <seb_kuzminsky> god idea
[14:42:10] <seb_kuzminsky> *good
[14:42:16] <seb_kuzminsky> i know where the old heat sink is
[14:57:22] <seb_kuzminsky> the old heatsink is on and the buildslave is back
[14:58:54] <seb_kuzminsky> we'll see how it goes
[17:31:03] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15yaqwsx opened pull request #46: Add support for 5i24 in PnCConf (06master...06pncconf_5i24) 02
https://github.com/LinuxCNC/linuxcnc/pull/46
[17:57:18] <jepler> cmorley: can you evaluate whether this patch is right? it seems too simple in a way.
https://github.com/LinuxCNC/linuxcnc/pull/46
[17:57:54] <jepler> cmorley: (remember not to close a pull request using the github button, because that will get undone the next time git.linuxcnc.org is mirrored to github)
[18:23:16] <cmorley> well amazingly it may be just that simple - I see in the forum he used pncconf to configure for the 6i24 - bit embarrassing for me :) But I don't have a card to actually test with. - i will look into it more later if i can.
[18:30:39] <jepler> cmorley: if you decide it's OK but don't know the git incantation to merge it manually let me know and I'll do it for you.
[18:30:58] <jepler> cmorley: the github pull request is for master branch, but I could make it against 2.7 if that makes sense.
[18:31:22] <cmorley> yes 2.7 would be where i would put it.
[18:32:16] <cmorley> I'll message you when I am happy it's ok. Thanks!
[18:34:35] <jepler> thank you for taking the time to look at it!
[21:19:14] <pcw_home> minor spell-o in gantry comp: with no limit on accleration.
[21:25:11] <witnit> do we care about typos on the main page?
http://linuxcnc.org/docs/2.7/html/getting-started/getting-linuxcnc.html
[21:26:34] <witnit> section 5 next to the warning line "promped" should be "prompted"
[21:30:58] <KGB-linuxcnc> 03Jeff Epler 052.7 9301dcc 06linuxcnc 10docs/src/getting-started/getting-linuxcnc.txt docs: fix typo in getting started guide * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=9301dcc
[21:30:58] <KGB-linuxcnc> 03Jeff Epler 052.7 0639b2b 06linuxcnc 10src/hal/components/gantry.comp gantry: fix typo in docs * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=0639b2b
[21:32:33] <jepler> thanks, I think I fixed both of those
[22:22:27] <seb_kuzminsky> wow, game 3 wasnt even close