#linuxcnc-devel | Logs for 2016-01-17

[00:02:32] <KGB-linuxcnc> 03chris morley 05master 6edc3be 06linuxcnc Merge branch '2.7' * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=6edc3be
[00:56:00] <skunkworks> https://groups.yahoo.com/neo/groups/mach1mach2cnc/conversations/messages/149897
[07:38:46] <KGB-linuxcnc> 03John Thornton 052.7 5d21619 06linuxcnc 10docs/src/gui/ngcgui.txt Docs: add a bit more info to ngcgui * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=5d21619
[07:55:55] <skunkworks> lathe seems to run. needed a bunch of oil to get the carriage moving smoothly. (it had sat for a long time)
[07:56:21] <skunkworks> 400rpm with a 18 inch chuck is a bit scary
[08:05:59] <jthornton> I can't even imagine an 18" chuck
[10:56:03] <KGB-linuxcnc> 03Norbert Schechner 052.6 9cd3eba 06linuxcnc 10(9 files in 4 dirs) gmoccapy_1_5_6 - deleted alarm entry and added new settings for combi_dro * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=9cd3eba
[11:13:06] <maxcnc> hi Q someone knows the syntax of FEATURES = enable #<_hal[x]> read only variables: 8
[11:13:18] <maxcnc> im getting halpin not defined
[11:13:44] <maxcnc> is this the correct syntax
[11:14:54] <maxcnc> it is implemented interp_namedparams.cc
[11:15:07] <maxcnc> so why not using it but not well documented
[11:18:39] <maxcnc> i think it is good to add the "// current absolut position there
[11:19:48] <maxcnc> as init_readonly_param("_ax", NP_AX, PA_USE_LOOKUP);
[11:21:48] <maxcnc> and with NP_AX set to *value = _setup.current_ax;
[11:22:43] <maxcnc> so i need to know here _setup comes from
[11:26:49] <micges> maxcnc: you need to add [RS274NGC] FEATURES = 8 to ini file
[11:27:21] <micges> and then use it like this 'G4 P[#<_hal[gui.laser.off-delay]>]'
[11:28:55] <maxcnc> ok i try
[11:30:28] <maxcnc> micges: do i need the signal name or the halpin name
[11:30:31] <pcw_home> micges: Preempt-RT4.4-RT has at least 30% better latency than 4.1.5 on first 2 machines I tried it on
[11:31:25] <maxcnc> pcw_home: the coustemer called in today that the mesa5i25 did prevent the pc again from startup
[11:31:41] <pcw_home> what MB?
[11:32:18] <maxcnc> D2312-A2
[11:32:59] <maxcnc> the old versions 5i25 i got from 3years ago dont trouble at all
[11:33:16] <micges> maxcnc: I know it works for pins
[11:33:27] <maxcnc> the newer i got in 2015 from juli are the hell of miss troubling
[11:33:43] <micges> pcw_home: building now
[11:34:37] <pcw_home> I really dont think theres a difference in the 5I25s
[11:35:09] <maxcnc> micges: it works like a sharm
[11:35:54] <maxcnc> pcw_home: its the thing im dealing whith
[11:36:22] <maxcnc> i got near 25 pc from the same number
[11:36:43] <maxcnc> #<xabsolut>=#<_hal[axis.0.motor-pos-cmd]>
[11:38:18] <pcw_home> I woudl try a "bad" 5i25 on a new MB
[11:39:29] <maxcnc> ok but i gout realy good connections to get this pc for less then 20 bux
[11:39:50] <maxcnc> and there are 6000 less latency
[11:40:02] <maxcnc> realy good and stable
[11:40:20] <maxcnc> ok i need to go PIZZA
[11:41:12] <maxcnc> pcw_home: when i unplug and replug 2 times the 5i25s will run as long the power the pc is on 10hr's no problem
[11:41:21] <maxcnc> only the mis to get it started
[11:41:39] <pcw_home> probably BIOs related
[11:52:17] <seb_kuzminsky> http://www.smbc-comics.com/index.php?id=3990
[11:53:05] <pcw_home> :-)
[13:16:50] <maxcnc> Hi im back from launch ;-)
[13:17:20] <maxcnc> Question i now got finished implementation of the absulut named parameter for XYZ
[13:17:32] <maxcnc> as #<_ax> ...
[13:17:54] <maxcnc> but where do i fill this var in the cc hh files
[13:18:43] <maxcnc> interp_namedparams.cc ok and interp_internal.hhalso
[13:18:51] <maxcnc> recompile no error
[13:19:41] <maxcnc> i also candt find the numberd parameter file location in src
[13:20:00] <maxcnc> is thee a git search for #5420 for instance
[13:20:34] <maxcnc> i need only little help for basi understanding
[13:31:30] <maxcnc> micges: ?
[13:54:54] <maxcnc> all in holiday so tomorow is a new day for progging or when ever
[15:14:56] <jepler> maxcnc: suggest using git grep
[15:14:56] <jepler> ~/src/linuxcnc$ git grep 5420 src/emc/rs274ngc/
[23:18:56] <seb_kuzminsky> anyone else seeing a bug with the axis mdi history on jessie?
[23:19:34] <seb_kuzminsky> i hit up-arrow to select a command from the history and it populates the test-input field with that command, but then i can't use right-arrow or left-arrow to move around the command string to edit it
[23:20:09] <seb_kuzminsky> this is in master
[23:21:20] <seb_kuzminsky> and 2.7.3 behaves the same way
[23:21:38] <seb_kuzminsky> if i click in the test-input field i can edit it like normal
[23:21:44] <seb_kuzminsky> was it always this way and i just dont remember?
[23:46:45] <seb_kuzminsky> on lucid with 2.7 it works as expected: up-arrow/down-arrow select a line from history, then left-arrow/right-arrow let you edit that command
[23:49:21] <seb_kuzminsky> on wheezy with master it behaves the same correct way as on lucid/2.7
[23:49:41] <seb_kuzminsky> so it looks like some kind of jessie/tcl/tk/focus/hocus/pocus
[23:50:04] <seb_kuzminsky> gods i'm glad i'm not a gui guy
[23:59:48] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15SebKuzminsky opened issue #28: Axis GUI MDI history problem on Debian Jessie 02https://github.com/LinuxCNC/linuxcnc/issues/28