Back
[00:06:38] <KimK> linuxcnc-build_: force build --branch=aux_gladevcp_apps 0000.checkin
[00:06:39] <linuxcnc-build_> build forced [ETA 2h45m38s]
[00:06:40] <linuxcnc-build_> I'll give a shout when the build finishes
[00:09:57] <KimK> I noticed that dgarr correctly added a trailing underscore to the buildbot's nick, but then typoed --branch= to --branch- so I thought I'd give it a try. It seems to be working, good luck Dewey, I hope you get what you wanted.
[01:25:32] <linuxcnc-build_> Hey! build 0000.checkin #4713 is complete: Success [3build successful]
[01:25:32] <linuxcnc-build_> Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4713
[07:57:48] <dgarr> KimK: thanks for your help
[08:55:58] <JT-Shop> pcw_home: can you connect a 7i78 to a 26 pin header on the 7i76e?
[12:01:20] <pcw_home> JT-Shop: sure, with the right firmware, in fact you can connect two 25 pin daughtercards of any type to a 7I76E
[12:32:28] <JT-Shop> the sserial firmware is part of hm2? ie you specify it in the hal loadrt hm2_??
[12:34:10] <JT-Shop> ah I found the example loadrt setsserial cmd="flash hm2_7i76e.0.7i76.0.0 hm2/sserial/7I76R14.BIN"
[13:59:24] <stustev> Just reading the section 3.3.2.0 Tool Radius Offset in the V2.8.0-pre1 Documentation and saw this statement "This means you can program a cutter to pass down a path that is narrower than the cutter without any errors." I don't understand this statement. Would someone be able to explain it to me?
[14:00:31] <seb_kuzminsky> it means linuxcnc will accept that gcode without error, even though it gouges the part and produces a faulty geometry
[14:01:26] <seb_kuzminsky> linuxcnc doesn't look ahead more than one move (and doesnt look into the past at all) when it comes to trying to avoid gouging
[14:23:06] <KimK_laptop> Hi Seb. I could create a new branch to make proposed document text changes in, but is there a way to put out pdf pages of just the changed pages, with the changes in red? Or do you have to git/gitk your way through the asciidoc diffs to evaluate the proposed changes?
[14:23:46] <KimK_laptop> I'm just wondering what is the best way to give folks information without making life more difficult for them.
[14:27:48] <KimK_laptop> OK, I guess worst case I could extract a few finished pdf pages, and put them together in one new pdf. Is there a way to change text color, or yellow-highlight a pdf? BRB, let me look...
[14:38:08] <KimK_laptop> It looks like LibreOffice might be able to do it (edit pdfs to add some kind of highlighting), I'll try it this weekend and see what it can do.
[14:41:09] <KimK_laptop> If it could add "hover labels" with the git commit short (or long) hash number, that might help too, I'll keep a lookout.
[14:42:38] <stustev> My 5 axis cutter diameter routine is currently pointed at my Cincinnati 5 axis profilers where the rotary axes are A and B with B carrying A. I need to know the current XYZ position, the next XYZAB position and the next XYZ postion for a total of three tool points. Is there one best place to insert this into LinuxCNC to allow tool path modification?
[15:43:38] <seb_kuzminsky> KimK_laptop: you could make your proposed changes on a branch, then use diffpdf (from the debian package of the same name) to compare your new pdfs to the ones you branched from
[15:44:05] <seb_kuzminsky> though one of the great things about asciidoc is that the changes are understandable even without looking at the rendered output, generally
[15:45:04] <seb_kuzminsky> stustev: i'm not sure... we have some of that info on motion pins in HAL, and some in the status structure
[21:19:08] <KGB-linuxcnc> 03Dewey Garrett 05master eda5d16 06linuxcnc 10src/emc/usr_intf/axis/scripts/axis.py axis.py: identity kins: no teleop until homed #224 * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=eda5d16
[21:19:08] <KGB-linuxcnc> 03Dewey Garrett 05master 2b22052 06linuxcnc 10docs/src/getting-started/updating-linuxcnc.txt 10src/emc/motion/control.c 10src/emc/motion/mot_priv.h 10src/emc/motion/motion.c motion: motion.servo.last-period: parameter to pin * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=2b22052
[21:19:08] <KGB-linuxcnc> 03Dewey Garrett 05master 721e430 06linuxcnc 10(5 files in 4 dirs) corexy kinematics (+man page update +sim config) * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=721e430
[23:51:39] <KGB-linuxcnc> 03Chris Morley 05qtvcp-2.7 b8d05fd 06linuxcnc 10lib/python/qtvcp_widget_plugins/lcnc_widgetplugin.py 03lib/python/qtvcp_widgets/gcode_widget.py qtvcp -add a gcode display / edit widget * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=b8d05fd
[23:51:40] <KGB-linuxcnc> 03Chris Morley 05qtvcp-2.7 43751d6 06linuxcnc 10share/qtscreen/skins/qt_cnc/qt_cnc.ui 10share/qtscreen/skins/qt_cnc/qt_cnc_handler.py qtscreen -update test screen for gcode display widget * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=43751d6