#linuxcnc-devel Logs

Jun 14 2017

12:57 AM KGB-linuxcnc: 03Sebastian Kuzminsky 05hy-gt-vfd-3 80b33c6 06linuxcnc 10src/hal/user_comps/Submakefile build system: rename the GS2 VFD Makefile variables for clarity * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=80b33c6
12:58 AM KGB-linuxcnc: 03Sebastian Kuzminsky 05hy-gt-vfd-3 40629a0 06linuxcnc 10docs/man/.gitignore 03docs/src/man/man1/hy_gt_vfd.1.txt 10src/hal/user_comps/Submakefile 03src/hal/user_comps/hy_gt_vfd.c add a driver for the Huanyang GT series VFD * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=40629a0
08:36 AM skunkworks: How do you connect to ethercat with linuxcnc? Is it as easy as plugging into the network or do you need some sort of interface between the ethercat devices and the pc?
08:39 AM skunkworks: having a hard time finding info on that.
08:40 AM skunkworks: ah - you need a EK1100 or the like
08:41 AM skunkworks: or not
08:43 AM pcw_home: To use Ethercat slave devices like drives all that is built in, you just need ethernet on the host
08:43 AM skunkworks: cool
08:43 AM skunkworks: (not something I am interested in - just trying to get some facts)
08:43 AM skunkworks: interested in using..
08:44 AM skunkworks: pcw_home, still hectic?
08:44 AM pcw_home: Still looking for things in boxes...
08:45 AM skunkworks: heh
08:48 AM skunkworks: http://www.machsupport.com/forum/index.php/topic,35057.10.html
08:53 AM cradek: I would not recommend linuxcnc+ethercat to anyone because of the problems with license compatibility, the details of which I've heard about several times but again forgotten
08:53 AM cradek: I believe it's ok to use, but the ethercat support can never be put into mainline linuxcnc and distributed like normal
08:54 AM cradek: so you'll always be building your own versions and doing your own maintenance if you choose to use this hardware
08:55 AM pcw_home: Though the driver interface is not something that's likely to change too quickly
08:56 AM cradek: yeah, I'd have to study it to guess how much extra work it would be, and I haven't
08:56 AM pcw_home: I guess with Mach you need PC --> RTBOX --> Ethercat slaves
08:57 AM skunkworks: cradek, I vaguely remember that too
08:57 AM skunkworks: I guess galil has some sort of ethercat motion card
08:58 AM pcw_home: (Galil would be the RTBOX)
08:58 AM skunkworks: right
08:59 AM pcw_home: still seem like an awkward architecture compared to PC (or Arm Host) --> EthercatSLaves
09:00 AM pcw_home: seems
09:00 AM skunkworks: you always need that extra layer
09:00 AM pcw_home: that's proprietary and often has limited resources
09:03 AM pcw_home: It does seem that a lot of this is driven by the desire to run Windows
09:07 AM skunkworks: right
09:09 AM pcw_home: we once worked with some people using windows with a real time extension, it was terrible
09:09 AM pcw_home: expensive and very poor latency
09:13 AM pcw_home: It did not (maybe deliberately) have working tools to measure latency, so we instrumented our I/O FPGA card
09:13 AM pcw_home: so we could timestamp the scheduled accesses, and the Windows RTOS had multi-ms gaps
09:19 AM skunkworks: yeck
09:19 AM skunkworks: I am really happy with the direction linux has gone with rt_preempt.
09:20 AM skunkworks: so far ;)
09:24 AM pcw_home: Its nice that its so easy with Preempt-RT to get a working modern RT kernel
09:33 AM pcw_home: I now have at least a couple machine years of uptime with Preempt-RT/Ethernet hardware
09:33 AM pcw_home: Some running on my normal desktop, very stable, only thing that causes trouble is OS updates
09:33 AM pcw_home: (they sometimes restart the Ethernet driver...)
10:35 AM KGB-linuxcnc: 03Sebastian Kuzminsky 052.7 40629a0 06linuxcnc fast forward * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=40629a0
10:35 AM KGB-linuxcnc: 05hy-gt-vfd-3 40629a0 06linuxcnc 04. branch deleted * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=40629a0
10:36 AM KGB-linuxcnc: 03Sebastian Kuzminsky 05master c799f62 06linuxcnc 10docs/man/.gitignore 10src/hal/user_comps/Submakefile Merge remote-tracking branch 'origin/2.7' * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=c799f62
10:37 AM seb_kuzminsky: i just merged a driver for an inexpensive chinese vdf called "Huanyang GT-series". It's the newer version of the crazy old "Huanyang" (non-GT-series) VFD. We're using it at the Boulder Hackspace, it seems to work so far.
10:38 AM cradek: sweet
10:41 AM TurBoss: seb_kuzminsky: ok nothing happends, will wait 30 min or so the I close the issue
10:41 AM TurBoss: :D
10:41 AM TurBoss: Thanks
10:41 AM TurBoss: *then
10:42 AM seb_kuzminsky: ok, glad to hear it
10:42 AM seb_kuzminsky: the issue will close automatically when github realizes i've pushed the fix to the master branch
10:42 AM TurBoss: so I leave it open?
10:42 AM TurBoss: ok
10:42 AM seb_kuzminsky: if you get phantom movement again, or you notice anything else wrong, please open a new issue
10:43 AM TurBoss: fine
10:43 AM seb_kuzminsky: yeah, feel free to ignore the issue unless something's broken
12:30 PM linuxcnc-build: build #4967 of 1300.rip-precise-i386 is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1300.rip-precise-i386/builds/4967 blamelist: Sebastian Kuzminsky <seb@highlab.com>
12:30 PM seb_kuzminsky: boo
12:32 PM seb_kuzminsky: hmm, that test doesn't usually fail
12:45 PM seb_kuzminsky: yuck
02:02 PM linuxcnc-build: build #4985 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4985 blamelist: Sebastian Kuzminsky <seb@highlab.com>
05:08 PM linuxcnc-build: build #3138 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/3138 blamelist: Sebastian Kuzminsky <seb@highlab.com>
05:09 PM seb_kuzminsky: ugh, random segfault while building docs on wheezy-armhf
05:27 PM linuxcnc-build: build #4986 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4986 blamelist: Sebastian Kuzminsky <seb@highlab.com>
06:28 PM jepler: seb_kuzminsky: it's the same old song eh
06:28 PM seb_kuzminsky: summertime is segfaulttime apparently
06:29 PM jepler: put the builder in an ice bath maybe
06:29 PM seb_kuzminsky: i took your advise and limited the max cpu freq to 1.2 ghz, and i limited the buildbot to 3 parallel jobs on those slaves (the default is one job per cpu, so 4 on the u3)
06:29 PM seb_kuzminsky: the cpu temp tops out in the mid 40's C, and it seems generally more stable, but not enough maybe
06:30 PM seb_kuzminsky: i also have high quality fans pointing at the heat sinks on those boards now
06:30 PM seb_kuzminsky: i'll check when i get home if the fan stopped, i think it did not because the temp goes quickly back down to 30-ish when the build job finishes
09:23 PM jepler: seb_kuzminsky: just ran across this http://sjoerd.luon.net/posts/2017/07/debian-armhf-vm-on-arm64/