Small picture, I've run x11VNC on my BBB briefly, but I find ssh -X actually works better, I picked this tip up from one of the Machinekit youTube videos.
I might change my tune if my host had to be Windows, I'm currently helping a friend get going so I'm in the process of installing cygwin on my only Windows machine to find out. Here are my notes from when I set up x11VNC on one of the Machinekit images: -----------------------------------------------------VNC Set Up----------------------------------------------------------------- // Set up running machinekit using VNC // probably best to do this to use the USB Ethernet gadget as WiFi and wired Ethernet will be slower than the maximum USB2 speed. // Download a VNC viewer, this one is popular on Windows: http://www.uvnc.com/docs/uvnc-viewer.html // lots of info about running it: http://www.uvnc.com/docs/uvnc-viewer.html // login to the BBB ssh 192.168.7.2 using putty, and do all this as normal user (default: machinekit) // install X11 VNC server: sudo apt-get install x11vnc // start the server: x11vnc -bg -o %HOME/.x11vnc.log.%VNCDISPLAY -auth /var/run/lightdm/root/:0 -forever // note the assigned port, usually 5900 //Start your VNC viewer and connect by putting 192.168.7.2:5900 (or whatever port the server started on) // The AUTO mode is the best starting point. // I did it on Linux using a different viewer client and performance seemed better than with the local HDMI display and keyboard/mouse. // This is probably the way to go forward. (I used Gnome Remote Desktop Viewer) // to start the server automatically after bootup: // create a shell script to start the server, Don't do this as root! use the normal user login (default: machinekit) nano startVNCserver.sh // paste in these lines: #!/bin/bash /bin/sleep 30 /usr/bin/x11vnc -bg -o %HOME/.x11vnc.log.%VNCDISPLAY -auth /var/run/lightdm/root/:0 -forever // exit nano and make the script executable with: chmod a+x startVNCserver.sh // start the server on bootup crontab -e // and add the following at the end of the file: @reboot /home/machinekit/startVNCserver.sh // exit nano and save the normal way This was with a Machinekit image form something like 2015-04 so I apologize in advance if things have changed that make this totally wrong. I'm not sure how robust my script to start it from a crontab is, the sleep 30 is adhoc, as the @reboot seems to run before all the needed system pieces have finished their startup, but it seemed to work for me before I decided ssh -X was a better way to go. On Tuesday, December 15, 2015 at 10:05:23 PM UTC-6, Bill Dussault wrote: > > I am trying (Big picture here) to run Machinekit on the beaglebone for my > CNC router. I am trying to use VNC to be able to run the machine with the > computer out of the room to prevent everything from getting dusty. I have > x11vnc installed on the bone but cannot connect to it over the ethernet. I > have been chipping away all week and started over, this time without a > static IP address and finally got ssh over ethernet to work. I am using > tightvnc on my laptop to try and communicate with it. > > > Thanks > > Bill > > On Sunday, December 6, 2015 at 7:29:06 PM UTC-6, Bill Dussault wrote: >> >> Greetings, >> >> I am trying to install X11VNC and log into it via my laptop and I am >> having some tough luck >> >> Here is what I have done.......... >> >> I have changed my IP address to a 192.168.1.XX >> My router for some reason still thinks it is the old IP address even when >> I refresh it. >> >> I have turned on VNC on the firewall on my 2wire router >> >> Next I installed VNC: >> >> - Debian: sudo apt-get install x11vnc >> >> 3. Enter the below command >> >> >> >> -Debian: >> >> x11vnc -bg -o %HOME/.x11vnc.log.%VNCDISPLAY -auth >> /var/run/lightdm/root/:0 -forever >> >> >> (I'm not sure if I turned it on) >> >> >> I can ping the beaglebone from my computer >> >> >> C:\Users\William>ping 192.168.1.XX >> >> >> Pinging 192.168.1.XX with 32 bytes of data: >> >> Reply from 192.168.1.XX: bytes=32 time=3ms TTL=64 >> >> Reply from 192.168.1.XX: bytes=32 time=3ms TTL=64 >> >> Reply from 192.168.1.XX: bytes=32 time=5ms TTL=64 >> >> Reply from 192.168.1.XX: bytes=32 time=3ms TTL=64 >> >> >> Ping statistics for 192.168.1.XX: >> >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), >> >> Approximate round trip times in milli-seconds: >> >> Minimum = 3ms, Maximum = 5ms, Average = 3ms >> >> >> So I can See it. >> >> >> I start tightVNC on my laptop >> >> >> 192.168.1.XX:5901 >> >> >> I get connection has been gracefully closed. Or Connection >> was actively Refused... >> >> >> X11VNC has a few configurations when opened on the desktop I am >> unfamiliar with. No passwords in use as of yet (I was warned when I started) >> >> >> Does anyone see anything out of whack? >> >> >> Thanks! >> >> >> Bill >> >> >> -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
