Back
[08:32:13] <KGB-linuxcnc> 03Norbert Schechner 05master 5e077fb 06linuxcnc 10src/emc/usr_intf/gmoccapy/gmoccapy.py 10src/emc/usr_intf/gmoccapy/release_notes.txt gmoccapy_1_0_6_1 - error pin correction * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=5e077fb
[08:32:13] <KGB-linuxcnc> 03Norbert Schechner 05master 7424158 06linuxcnc Merge branch 'master' of ssh://norbert@git.linuxcnc.org/git/linuxcnc.git * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=7424158
[08:42:53] <KGB-linuxcnc> 03Norbert Schechner 05master e1d36aa 06linuxcnc 10src/emc/usr_intf/gmoccapy/gmoccapy.glade 10src/emc/usr_intf/gmoccapy/gmoccapy.py 10src/emc/usr_intf/gmoccapy/release_notes.txt gmoccapy_1_0_6_2 - changed standard settings ob box_custom_? * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=e1d36aa
[09:57:40] <linuxcnc-build> build #39 of 4017.deb-wheezy-armhf is complete: Failure [4failed apt-get-update shell_3] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/4017.deb-wheezy-armhf/builds/39 blamelist: Norbert Schechner <nieson@web.de>
[10:30:25] <norbert> Someone here to tell me how to add a message to linuxcnc.error_chanel with python code?
[11:39:19] <linuxcnc-build> build #40 of 4017.deb-wheezy-armhf is complete: Failure [4failed apt-get-update shell_3] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/4017.deb-wheezy-armhf/builds/40 blamelist: Norbert Schechner <nieson@web.de>
[11:41:49] <norbert> Not me again, please!
[11:45:58] <seb_kuzminsky> heh
[11:46:08] <seb_kuzminsky> not your fault this time ;-)
[11:46:25] <seb_kuzminsky> your branch is based on master, which doesn't build on armhf
[11:46:48] <seb_kuzminsky> the 'build rip and runtests' builder knows not to try, but the deb builder doesn't know not to try
[11:47:01] <seb_kuzminsky> notice that the name of the failed builder is deb-wheezy-armhf
[11:47:37] <norbert> OK but I do not like to get blamed ;-)
[11:50:56] <seb_kuzminsky> heh
[14:21:16] <jonasthomas> hello Is anyone here versed into running linux cnc beagle bone black. I trying to figure out how to get X-windows running on a remote desktop.
[14:21:48] <jonasthomas> mhaberler are you around?
[14:22:03] <mhaberler> yes
[14:22:45] <jonasthomas> ah.. I think was reading a blog that you've been playing around with the beaglebone and linux cnc... Is that correct?
[14:22:46] <mhaberler> did you try export DISPLAY=<ip of X server host>:0.0 - at least thats what I use
[14:22:58] <mhaberler> playing around... sort of correct
[14:23:55] <mhaberler> there are various other ways, like tunneling over ssh but that slows down quit a bit
[14:24:07] <jonasthomas> Oh boy this is really a dumb question... Ip of X server host is for the BBB?
[14:24:39] <mhaberler> it is the address of the X server, i.e. the machine running the display
[14:24:53] <jonasthomas> Ahhh...
[14:24:56] <mhaberler> you execute that on the BB before you start linuxcnc
[14:25:25] <mhaberler> whatever your host is - some people even use windows X servers, but on linux ifconfig will tell you the interface address
[14:25:30] <jonasthomas> So I could put that in the /home/.bashrc
[14:25:49] <mhaberler> that is what I do, but I do have a stable IP address setup
[14:26:25] <mhaberler> it might not be useful to save in .bashrc if you use DHCP and get different addresses all the time
[14:27:06] <jonasthomas> At the moment I have the usb cable from my laptop to the BBB
[14:27:12] <mhaberler> before this works you need to enable remote X access on the display
[14:27:20] <mhaberler> well thats just an IP link, right?
[14:27:39] <mhaberler> ethernet over usb I assume
[14:27:55] <mhaberler> so you have an ip address on the display host, I hope?
[14:28:26] <jonasthomas> ummm... hold on let me try a few things.
[14:31:31] <mhaberler> anyway, before firing off linuxcnc on the display host you execute something like 'xhost <ip address of beaglebone>'
[14:31:53] <mhaberler> which will allow bb X clients to connect to the X display server
[14:33:16] <jonasthomas> Oh boy I'm confused at the moment(which isn't too hard to do ;) )
[16:03:58] <jonasthomas> mhaberler are you still around?
[16:04:07] <mhaberler> yes
[16:05:32] <jonasthomas> I think I had everything setup ok... I had shh connection going to the bone and a regular terminal connection.. I had them ping each other..
[16:06:00] <jonasthomas> I open up a vnc to the bone had that working
[16:06:50] <jonasthomas> I did the DISPLAY = .... from the VNC and that seemed to work.
[16:07:18] <jonasthomas> did the xhost ... that worked...
[16:07:44] <jonasthomas> when I fired up linuxcnc &
[16:07:46] <jonasthomas> I got a unable to connect.
[16:08:19] <mhaberler> why vnc?
[16:08:47] <jonasthomas> I thought I needed that.
[16:09:02] <mhaberler> did you use any instructions from somewhere already, and if so, which ones - please point me to them?
[16:09:38] <jonasthomas> Not directly... I had someone who was doing stuff with RPI and I sort of adapted.
[16:09:54] <mhaberler> and where was that ?
[16:10:26] <jonasthomas> at the hacker space I belong to.. Not directly published.
[16:10:30] <mhaberler> aha
[16:10:54] <mhaberler> well I cant help you with that because I havent seen that, so hard to comment
[16:11:05] <mhaberler> I can tell you what I use
[16:11:31] <jonasthomas> I understand.
[16:11:32] <jonasthomas> I think the issue with the rpi was that you couldn't do it over usb... I wonder if the same applies to bbb
[16:11:33] <mhaberler> you seem to have some X server running on the BB?
[16:11:45] <jonasthomas> tinyvnc
[16:11:49] <mhaberler> aha
[16:12:31] <mhaberler> well vnc will have rather poor performance for the graphics remotely, which is why I use a direct X connection
[16:12:50] <jonasthomas> if you hook up a bbb to a laptop over ethernet do you need a crossover cable?
[16:13:27] <mhaberler> if you can ping vice versa, it should not matter - an IP connection is all that is needed, that has nothing to do which medium it goes over
[16:13:34] <mhaberler> I take that works?
[16:13:57] <mhaberler> as I understand from above
[16:14:45] <jonasthomas> I had a ethernet cable to router to BBB. bbb ->usb-> laptop that worked and I could update the bbb.
[16:15:16] <jonasthomas> bbb-> Ethernet-> laptop does not.
[16:15:31] <jonasthomas> hense the crossover question
[16:15:38] <mhaberler> and the laptop runs... what, linux, windows?
[16:15:40] <mhaberler> mac?
[16:15:53] <jonasthomas> 64 bit 12.04 ubuntu
[16:16:02] <mhaberler> aha
[16:16:47] <mhaberler> well likely that ethernet/laptop/bbb thing is merely a dhcp server is missing on the laptop, but it dont matter for now if you have IP connectivity one way or the other
[16:17:06] <jonasthomas> so your saying I can fire up linuxcnc without VNC..
[16:17:13] <mhaberler> yes
[16:17:27] <jonasthomas> ah.. my misunderstanding...
[16:17:48] <mhaberler> and it will perform better because VNC works at the copy-bitmap-over-tcp level which is a lot of traffic and cycles with fast updating grahics
[16:17:58] <jonasthomas> Ok.. let me do so rewiring... and try this again..
[16:18:17] <jonasthomas> Cool... so you do this over usb or over ethernet?
[16:18:22] <mhaberler> it is not important _how_ you get from a to be
[16:18:33] <mhaberler> if you can ping from either side you are fine
[16:18:48] <mhaberler> you can, I assume?
[16:19:19] <jonasthomas> ok.. let me try this again.. (I was till I started rewiring... back to where I was... Back in a few...
[16:19:38] <mhaberler> choose whatever works to ping from either side
[16:24:00] <jonasthomas> So this is coming to you from Laptop-> usb-> BBB-> to->ethernet -> router (I'm amazed that this works so easily)
[16:24:25] <mhaberler> I do not understand ?
[16:24:57] <mhaberler> probably the easiest thing is: plug both bb and laptop into router over ethernet
[16:25:44] <mhaberler> the router will give ip addresses to both; obviously the laptop wont give an ip address to a client like the bb because it is a dhcp client
[16:26:02] <mhaberler> (in case you connect them directly)
[16:26:29] <mhaberler> re crossover - these times are pretty much past, nowadays most ethernet plugs autodetect sex
[16:27:40] <mhaberler> (note this is neither a linuxcnc nor a development issue - it is basic networking so this is kind of the wrong forum)
[16:28:36] <jonasthomas> unfortunately I don't have the cabling and a wall wart with me at the moment
[16:29:08] <mhaberler> are you saying you power the bb over usb?
[16:29:20] <jonasthomas> yes
[16:29:37] <mhaberler> this is very likely to fail, because of power consumption
[16:30:04] <jonasthomas> at this point, its a bare bbb nothing hooked up... Just for play.
[16:30:38] <mhaberler> well yes, I assume you have the linuxcnc SD image on it, and hence the xenomai kernel
[16:30:41] <mhaberler> right?
[16:31:22] <jonasthomas> I got everything from
http://blog.machinekit.io/p/machinekit_16.html
[16:31:28] <mhaberler> ok
[16:32:03] <mhaberler> this means you run the xenomai kernel, which disables power saving to gain RT performance, and this is why USB power is likely to be insufficient
[16:32:54] <mhaberler> it might look it works, then keels over - I found this not to work reliably without a good external 5V supply (good = > 2amps)
[16:33:16] <mhaberler> a USB port can only feed up to 0.5amps
[16:33:25] <mhaberler> anyway this is an unrelated issue
[16:33:36] <jonasthomas> The lights all seem to be blinking but when I get a wall wart I'll get one.. good point..
[16:33:46] <mhaberler> see?
[16:34:02] <mhaberler> anyway, assume you have a good power supply
[16:34:17] <mhaberler> and an IP link, say through the router
[16:34:37] <mhaberler> you can log into the bb from the laptop, can you ? I assume you did so before?
[16:35:27] <jonasthomas> ok.. I have an ssh terminal session to the bone and a terminal session to the laptop... I'm able to ping between the two... So on to the next steps.
[16:35:37] <mhaberler> excellent
[16:36:03] <mhaberler> now record these steps:
[16:36:16] <mhaberler> record IP address of BB
[16:36:25] <mhaberler> record IP address of laptop
[16:36:31] <mhaberler> on laptop, do:
[16:36:45] <mhaberler> xhost <substitute ip address of bb>
[16:37:01] <mhaberler> on bb do this:
[16:37:15] <mhaberler> export DISPLAY=<laptop ip address>:0.0
[16:37:24] <mhaberler> then run linuxcnc
[16:37:57] <mhaberler> disable or remove that tinyvnc thing first
[16:38:02] <mhaberler> done
[16:38:04] <jonasthomas> I did that and got
[16:38:06] <jonasthomas> Application initialization failed: couldn't connect to display "192.168.7.1:0.1
[16:38:24] <mhaberler> that is not what I said if you compare to above line
[16:38:29] <mhaberler> I wrote:
[16:38:34] <mhaberler> export DISPLAY=<laptop ip address>:0.0
[16:38:42] <mhaberler> so the 0.1 comes from somewhere else
[16:39:07] <jonasthomas> hmm..
[16:39:29] <mhaberler> if you run a shell and do this:
[16:39:44] <mhaberler> $ export DISPLAY=1.2.1.4:0.0
[16:39:47] <mhaberler> then run
[16:39:50] <mhaberler> $ linuxcnc
[16:40:25] <mhaberler> it is impossible you get "couldn't connect to display "1.2.3.4:0.1"
[16:40:30] <mhaberler> note trailing '1'
[16:41:05] <mhaberler> the above commands (export, linuxcnc) must be run from the BB in the same shell
[16:42:06] <mhaberler> it looks like you still have this tinyvnc thing running - remove it
[16:42:25] <mhaberler> make sure there is no X server or Xvnc running on the BB
[16:42:55] <jonasthomas> At this point, I think I might need to redo the sd card and start from ground zero.. I think I did do much messing around to trust anything...
[16:43:38] <mhaberler> was there a tinyvnc on Charles' image? I dont think there i
[16:43:39] <mhaberler> s
[16:44:00] <jonasthomas> No I loaded that from debian
[16:44:10] <mhaberler> aha, then remove it
[16:44:28] <mhaberler> like 'apt-get remove <whatever that package name was>'
[16:44:38] <mhaberler> no need to restart a new image
[16:45:11] <jonasthomas> Ok..
[16:48:20] <jonasthomas> I'm being called to chores... ;( bbl.
[16:48:28] <mhaberler> ok
[17:17:03] <seb_kuzminsky> linuxcnc-build: force build --branch=unified-build-candidate-3 0000.checkin
[17:17:04] <linuxcnc-build> build forced [ETA 1h32m29s]
[17:17:04] <linuxcnc-build> I'll give a shout when the build finishes
[17:42:33] <linuxcnc-build> build #35 of 1401.rip-wheezy-amd64 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1401.rip-wheezy-amd64/builds/35
[17:44:08] <linuxcnc-build> build #35 of 1400.rip-wheezy-i386 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1400.rip-wheezy-i386/builds/35
[18:36:05] <linuxcnc-build> build #70 of 1403.rip-wheezy-armhf is complete: Failure [4failed apt-get-update compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1403.rip-wheezy-armhf/builds/70
[18:36:05] <linuxcnc-build> build #1887 of 0000.checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/1887
[18:50:20] <linuxcnc-build> build #36 of 1401.rip-wheezy-amd64 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1401.rip-wheezy-amd64/builds/36
[18:51:24] <linuxcnc-build> build #36 of 1400.rip-wheezy-i386 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1400.rip-wheezy-i386/builds/36
[19:41:25] <linuxcnc-build> build #37 of 1401.rip-wheezy-amd64 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1401.rip-wheezy-amd64/builds/37
[19:42:56] <linuxcnc-build> build #37 of 1400.rip-wheezy-i386 is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/1400.rip-wheezy-i386/builds/37
[19:43:04] <KGB-linuxcnc> 03Dewey Garrett 05dgarr/demo_apps f845366 06linuxcnc 03configs/apps/pyvcp/pyvcp.sh 10configs/apps/pyvcp/pyvcp_demo1.demo 03configs/apps/pyvcp/pyvcp_demo1.hal configs/apps/python_demo: pyvcp.sh script * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=f845366
[19:43:04] <KGB-linuxcnc> 03Dewey Garrett 05dgarr/demo_apps cd1f8a6 06linuxcnc 10configs/maintainer.txt configs/maintainer.txt: update for .demo files * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=cd1f8a6
[20:55:26] <linuxcnc-build> build #41 of 4017.deb-wheezy-armhf is complete: Failure [4failed apt-get-update shell_3] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/4017.deb-wheezy-armhf/builds/41 blamelist: Dewey Garrett <dgarrett@panix.com>
[22:29:14] <KGB-linuxcnc> 03Chris Morley 05pncconf_builder 2bbd3e6 06linuxcnc 10(32 files in 3 dirs) pncconf -GTK BUILDER refactor * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=2bbd3e6
[22:29:14] <KGB-linuxcnc> 03Chris S Morley 05pncconf_builder 1f3bc39 06linuxcnc 10src/emc/usr_intf/pncconf/dialogs.glade 10src/emc/usr_intf/pncconf/pages.py 10src/emc/usr_intf/pncconf/pncconf.py 10src/emc/usr_intf/pncconf/tests.py pncconf -fix live test bugs - openloop and stepper tune test * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=1f3bc39
[22:29:14] <KGB-linuxcnc> 03Chris Morley 05pncconf_builder a3879c1 06linuxcnc 10src/emc/usr_intf/pncconf/build_HAL.py 10src/emc/usr_intf/pncconf/pncconf.py 10src/emc/usr_intf/pncconf/tests.py pncconf -factor out mesa and parport loading wip * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=a3879c1
[22:29:17] <KGB-linuxcnc> 03Chris Morley 05pncconf_builder 5e82e9f 06linuxcnc 10src/emc/usr_intf/pncconf/pport2.glade pncconf -add pport test panel button * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=5e82e9f
[22:29:21] <KGB-linuxcnc> 03Chris Morley 05pncconf_builder 62b3a63 06linuxcnc 10src/emc/usr_intf/pncconf/pages.py pncconf -fix parport test for pport2 * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=62b3a63
[22:29:25] <KGB-linuxcnc> 03Chris Morley 05pncconf_builder 9770382 06linuxcnc 10src/emc/usr_intf/pncconf/pncconf.py 10src/emc/usr_intf/pncconf/tests.py pncconf -fix up tests to use common I/O loading code * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=9770382
[22:29:29] <KGB-linuxcnc> 03Chris S Morley 05pncconf_builder 92df8cf 06linuxcnc 10src/emc/usr_intf/pncconf/dialogs.glade 10src/emc/usr_intf/pncconf/pages.py 10src/emc/usr_intf/pncconf/pncconf.py 10src/emc/usr_intf/pncconf/tests.py pncconf -live test WIP * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=92df8cf
[22:29:34] <KGB-linuxcnc> 03Chris Morley 05pncconf_builder 7e1606f 06linuxcnc 10src/emc/usr_intf/pncconf/private_data.py pncconf -change share/ location definition code * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=7e1606f
[22:29:38] <KGB-linuxcnc> 03Chris Morley 05pncconf_builder 49f2948 06linuxcnc 10src/emc/usr_intf/pncconf/pages.py 10src/emc/usr_intf/pncconf/pncconf.py 10src/emc/usr_intf/pncconf/private_data.py 10src/emc/usr_intf/pncconf/tests.py pncconf -exculsive check fixed * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=49f2948
[22:29:43] <KGB-linuxcnc> 03Chris Morley 05pncconf_builder d4474b0 06linuxcnc 10src/emc/usr_intf/pncconf/pages.py 10src/emc/usr_intf/pncconf/pncconf.py 10src/emc/usr_intf/pncconf/screen.glade pncconf -wip * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=d4474b0
[22:29:47] <KGB-linuxcnc> 03Chris Morley 05pncconf_builder af0da01 06linuxcnc 10src/emc/usr_intf/pncconf/pncconf.py 10src/emc/usr_intf/pncconf/private_data.py pncconf -make the 5i25 default and use internal data * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=af0da01
[22:29:52] <KGB-linuxcnc> 03Chris Morley 05pncconf_builder 3f68bee 06linuxcnc 10src/emc/usr_intf/pncconf/pncconf.py 10src/emc/usr_intf/pncconf/tests.py pncconf -fixing tests wip * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=3f68bee
[22:29:56] <KGB-linuxcnc> 03Chris Morley 05pncconf_builder bb736f1 06linuxcnc 10src/emc/usr_intf/pncconf/build_HAL.py 10src/emc/usr_intf/pncconf/pncconf.py pncconf * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=bb736f1
[22:30:00] <KGB-linuxcnc> 03Chris Morley 05pncconf_builder cb38777 06linuxcnc 10lib/python/.gitignore 10share/linuxcnc/.gitignore pncconf -ignore generated files * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=cb38777
[22:30:04] <KGB-linuxcnc> 03Chris Morley 05pncconf_builder 87df8be 06linuxcnc 10src/emc/usr_intf/pncconf/build_HAL.py 10src/emc/usr_intf/pncconf/build_INI.py 10src/emc/usr_intf/pncconf/pages.py 10src/emc/usr_intf/pncconf/pncconf.py pncconf -PID stepper config wip * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=87df8be
[23:42:27] <linuxcnc-build> build #42 of 4017.deb-wheezy-armhf is complete: Failure [4failed apt-get-update shell_3] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/4017.deb-wheezy-armhf/builds/42 blamelist: dummy, Michael Haberler <git@mah.priv.at>, Jeff Epler <jepler@unpythonic.net>, Chris Radek <chris@timeguy.com>, Chris Morley
[23:42:27] <linuxcnc-build> <chrisinnanaimo@hotmail.com>, Chris S Morley <chrisinnanaimo@hotmail.com>, Norbert Schechner <nieson@web.de>, Sebastian Kuzminsky <seb@highlab.com>, ArcEye <arceye@mgware.co.uk>, Dewey Garrett <dgarrett@panix.com>
[23:59:33] <KGB-linuxcnc> 03Dewey Garrett 05dgarr/demo_apps e3b9136 06linuxcnc 10configs/apps/info.demo 10configs/apps/xhc-hb04/xhc-hb04.demo info.demo: updates for items and format * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=e3b9136