#linuxcnc-devel | Logs for 2018-11-09
Back
[01:03:45] -!- jthornton has quit [Read error: Connection reset by peer]
[01:04:11] -!- jthornton has joined #linuxcnc-devel
[01:05:28] -!- c-log has quit [Ping timeout: 245 seconds]
[01:06:04] -!- JT-Fshop- has quit [Ping timeout: 250 seconds]
[01:07:06] -!- c-log has joined #linuxcnc-devel
[01:31:09] -!- c-log has quit [Ping timeout: 252 seconds]
[01:33:20] -!- c-log has joined #linuxcnc-devel
[01:37:30] -!- c-log has quit [Ping timeout: 252 seconds]
[01:38:58] -!- c-log has joined #linuxcnc-devel
[02:11:57] -!- c-log has quit [Ping timeout: 252 seconds]
[02:14:02] -!- c-log has joined #linuxcnc-devel
[03:03:11] -!- JT-Fshop- has joined #linuxcnc-devel
[06:17:24] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15andypugh commented on issue #525: On Fri, 9 Nov 2018 at 04:01, John Morris <notifications@github.com> wrote:
[08:58:29] -!- mozmck has quit [Quit: Leaving.]
[08:59:58] -!- mozmck has joined #linuxcnc-devel
[09:04:42] <mozmck> I'm getting this error trying to compile linuxcnc and can't figure out why: hal/user_comps/xhc-hb04.cc:31:20: fatal error: libusb.h: No such file or directory
[09:06:28] <mozmck> Oh, I might have figured it out now - always happens as soon as you ask someone!
[11:00:21] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15zultron commented on issue #525: > 2.8 provides as opportunity to move things around in the INI file. We are already introducing significant INI file layout changes for JA, and there is a script to handle the reformatting. I think that it an INI file entry should move, this is the time to do it.... 02 https://github.com/LinuxCNC/linuxcnc/pull/525#issuecomment-437404923
[14:07:06] <mozmck> can hal signals be connected together?
[14:08:24] <mozmck> net signal1 pin1 pin2 net signal2 pin3 pin4 and then net sig signal1 signal2
[14:13:12] <andypugh> Np
[14:13:15] <andypugh> No, I mean
[14:13:20] <mozmck> Looks like not
[14:13:29] <mozmck> That would be handy though.
[14:13:30] <andypugh> But you might be able to alias sig1 to sig2
[14:14:03] <mozmck> Hmm, I need to read on aliases
[14:14:28] <mozmck> andypugh: did you see the multispindle branch dgarr made with some fixes?
[14:26:52] <andypugh> Not yet, I have been busy making things
[14:27:29] <andypugh> I don’t even really know what version my “production” machines are running.
[14:27:51] <andypugh> Though I should put them both on Master as that now has everything that I use that wasn’t in before.
[14:39:06] <mozmck> I should do so myself. I'm still running emc2 2.3 on my router table in the shop - it works - why break it!
[14:40:18] <andypugh> Err, possibly you have less reason to say that than most.
[14:40:59] <mozmck> less reason to say why break it? I'm sure you're right.
[14:42:12] <mozmck> That is a more major upgrade though and would probably need some hardware upgraded and the OS as well.
[14:43:01] <Tom_L> configs would be slightly different
[14:44:13] <mozmck> Yeah - I have easier things to upgrade than that for now.
[15:00:21] -!- ve7it has joined #linuxcnc-devel
[16:24:34] <rene_dev_> andypugh do you know why external offsets uses scale and counts instead of float? that doesnt make any sense to me
[16:24:58] <rene_dev_> its annoying for stuff like thc
[16:25:33] <rene_dev_> I would prefer machine units
[16:28:24] <pcw_mesa> I think it was originally conceived for things like jogging while paused
[16:29:11] <pcw_mesa> but yeah, machine units would be cleaner for general use
[16:47:08] <pcw_mesa> add a mode bit for integer (easy jog implementation in hal) or floating point (real time motion tweaking)?
[16:49:52] <rene_dev_> jog while paused should really not be done in hal
[16:50:24] <rene_dev_> why is integer easier in hal?
[16:54:01] <rene_dev_> andypugh does touchy use the same mdi as gmoccypy?
[16:56:43] <rene_dev_> doesnt look like it... what else uses hal_mdihistory.py?
[16:59:17] <andypugh> Touchy has no MDI history. Which is actually it’s only real problem as I use it
[17:00:07] <andypugh> rene_dev_: Yes, JWP in HAL is a kludge. There is a better version in Machinekit, I think.
[17:00:41] <rene_dev_> better jwp or better external offsets?
[17:01:07] <rene_dev_> I would prefer floats, makes it easier for thc pid, or wobbly turning
[17:01:16] <rene_dev_> and I think now is the time to change it...
[17:01:30] <rene_dev_> ah, Im fixing the mdi in gmoccapy.
[17:01:57] <rene_dev_> the fact hat it doesnt have a history that can be operated by the keyboard annoys me
[17:03:20] <rene_dev_> andypugh do you maintain touchy? it doesnt start if the gcode folder does not exists
[17:03:32] <rene_dev_> OSError: [Errno 2] No such file or directory: '/home/rene/linuxcnc/nc_files'
[17:04:34] <rene_dev_> what tooledit does touchy use? cant find it...
[17:24:37] <pcw_mesa> motions jog inputs expect "counts" which I think is why the EO branch used integers
[17:26:25] <pcw_mesa> so just by wiring the jog count source to EO you get jog while paused
[18:06:29] <andypugh> rene_dev_: Touchy was written by cradek
[18:06:54] <andypugh> I use it, but don’t consider it mine
[18:07:59] <andypugh> rene_dev_: I think it just expects you to edit the MDI code that “touch-off” brings up to change the tool table.
[18:09:01] <andypugh> Yes, I am not 100% happy with EO using ints, but my impression is that it made it more flexible.
[18:39:21] <rene_dev_> I don’t agree
[18:44:58] <rene_dev_> you can just convert what you have to float
[19:49:06] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15rene-dev pushed 1 new commit to 06master: 02 https://github.com/LinuxCNC/linuxcnc/commit/f36ddbe0e0cc43adf379aa430114f67ee26efa30
[19:49:06] -linuxcnc-github:#linuxcnc-devel- 13linuxcnc/06master 14f36ddbe 15Rene Hopf: Add spindle.N.amp-fault-in pins to motion, to report spindle amplifer faults...
[20:13:15] <andypugh> Cool
[20:13:25] -!- andypugh has quit [Quit: andypugh]
[20:48:31] -!- mozmck_lp has joined #linuxcnc-devel
[20:55:51] -!- mozmck_lp has quit [Quit: Leaving.]
[20:56:14] -!- mozmck_lp has joined #linuxcnc-devel
[21:30:58] -!- dgarr has joined #linuxcnc-devel
[21:32:14] <dgarr> > do you know why external offsets uses scale and counts instead of float? that doesnt make any sense to me
[21:32:36] <dgarr> Using machine_units for external offsets could lead to hazards particularly if a machine is turned off and then on with an offset value active on a machine_units pin.
[21:33:04] <dgarr> Suppose you have set a machine_units offset to 10mm, then turn machine off (either on purpose or by other perhaps unexpected means like an estop), then turn on with the offset value unchanged at 10mm.
[21:33:18] <dgarr> Do you want the machine to jump at the restart to its current position plus another 10mm? If not, when do you move the 10mm as specifed by a machine_units pin? It is a safety issue avoided by the counts/scale interface.
[21:33:35] <dgarr> As documented, using scale and counts: "The accumulation register is RESET to ZERO at each machine-on." Changes in counts are honored (just like jog wheels etc.) There is no jump at machine-on.
[21:33:54] <dgarr> And: "... external offsets are DEFINED as ZERO at each startup (machine-on) regardless of the value of the axis.L.eoffset-counts pins. To avoid confusion, it is recommended that all axis.L.eoffset-counts pins are set to zero when the machine is off."
[21:34:13] <dgarr> NOTE: if the user application does not follow this recommendation, there will still be no jump -- not as easily done if you specify offset as a floating point machine_units value.
[21:34:34] <dgarr> I wouldn't want to explain to an injured user that they should have followed the recommended procedure and returned all machine_unit offsets to zero before turning the machine on
[21:34:46] <dgarr> The scale/counts interface supports: 1) scalable, jog-like movements, 2) fixed (floating point) scaling so movement amount is determined by the product of count*scale, or 3) complex movements resulting if both scale and counts are changed dynamically.
[21:34:54] <dgarr> Ref: http://linuxcnc.org
[21:35:54] <mozmck_lp> dgarr: makes sense
[21:36:28] <dgarr> this interface was not designed casually -- i would caution about unexpected consequences of changing it
[21:58:44] <dgarr> minor s/product of count*scale/accumulated product of count*scale/
[22:15:33] <dgarr> or better: accumulated product of delta_counts*scale
[22:15:45] -!- dgarr has quit [Quit: Leaving.]
[22:47:36] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15rene-dev commented on issue #414: looks like it is fixed. 02 https://github.com/LinuxCNC/linuxcnc/issues/414#issuecomment-437555707
[22:54:20] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15rene-dev closed issue #384: sim/axis/vismach/puma does not home 02 https://github.com/LinuxCNC/linuxcnc/issues/384
[22:59:15] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15rene-dev commented on issue #213: you can have a pll that syncs the thread to some external clock.... 02 https://github.com/LinuxCNC/linuxcnc/issues/213#issuecomment-437556180
[23:03:19] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15rene-dev commented on issue #134: any update? There is still interest. 02 https://github.com/LinuxCNC/linuxcnc/issues/134#issuecomment-437556353
[23:08:26] <linuxcnc-build> build #3519 of 1401.rip-wheezy-rtai-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
[23:20:31] -!- mozmck_lp has quit [Quit: Leaving.]
[23:32:04] <linuxcnc-build> build #5710 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
[23:33:09] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15c-morley commented on issue #525: I can help with Gmoccapy and Gscreen GUI changes - but I'm fairly busy for the next month.... 02 https://github.com/LinuxCNC/linuxcnc/pull/525#issuecomment-437557542