search

winder / Universal-G-Code-Sender

A cross-platform G-Code sender for GRBL, Smoothieware, TinyG and G2core.
http://winder.github.io/ugs_website/
GNU General Public License v3.0
1.91k stars 768 forks source link

raspberry pi visualization while using VNC #1247

Open khturnings opened 5 years ago

khturnings commented 5 years ago

Problem description

Installed UGS Platform on a Pi and visualization does not work or it might but unable to test due to needing to use VNCServer which uses data in /opt/vc

Expected Behavior

When I try to open a Gcode file it should be shown in the visualizer.

Actual Behavior

Not able to use VNCServer and UGS together.

Steps to Reproduce the Problem

  1. Install as per https://github.com/winder/Universal-G-Code-Sender/wiki/Raspberry-Pi
  2. Reboot machine - VNCServer fails to start
  3. Revert /opt/vc.old back to /opt/vc
  4. Restart Pi and start UGS.
  5. VNCserver is running but UGS Visualizer does not work.

    Specifications

    Version

    Product Version: Universal Gcode Platform 20190423 Java: 1.8.0_212; OpenJDK Client VM 25.212-b01 Runtime: OpenJDK Runtime Environment 1.8.0_212-8u212-b01-1+rpi1-b01 System: Linux version 4.19.50-v7+ running on arm; UTF-8; en_US (ugsplatform) User directory: /home/pi/.ugsplatform/2.0-SNAPSHOT/dev Cache directory: /home/pi/.ugsplatform/2.0-SNAPSHOT/dev/var/cache

Operating system

Raspbian Buster on a Pi3

Platform

GRBL 1.1f

khturnings commented 5 years ago

Anyone have a solution for this, is it an issue with the new Raspbian Buster or another issue? thanks

winder commented 5 years ago

@khturnings you could give this a shot: https://github.com/winder/Universal-G-Code-Sender/wiki/Raspberry-Pi#activate-opengl-driver

khturnings commented 5 years ago

@winder I used these instructions on a clean buster build - I'm using a headless setup via VNC. To use VNC it requires the /opt/vc and I guess without removing this directory the opengl driver does not get fully enabled. Not sure what the solution would be?

winder commented 5 years ago

Ah, sorry about not reading your entire bug report. This is a long time issue and I assumed this was the version that we've seen on the issue board many times before.

I don't know a lot about this, but it looks like you need to install videocore6. After you reboot, does it re-create the /opt/vc directory?

I did find an interesting comment while running a quick keyword search on this issue... on this page:

On the Pi 4, a newer and faster version called VideoCore6 (VC6) is used.

Seems like the Pi 4 should work out of the box!

khturnings commented 5 years ago

@winder Interesting - The /opt/vc directory is not re-created when rebooted. Shame I am using a Pi 3 - someone else suggested reverting back to a Raspbian Stretch and then following your instructions. I will give it a try and update this thread.

BusbyGT commented 5 years ago

I came across this issue and tested this on a Raspberry Pi 4 running Raspbian buster.

1) Running headless and renaming the vc folder caused the VNC issue described here 2) Visualizer on platform 4/23/19 doesn't work 3) Changing GL driver in raspi-config doesn't fix the Visualizer (i'm using the new v3d by default anyways). vc4 driver is still being used as well. vc6 is the chip itself from what I've researched. 4) Java 1.8 and OpenJDK v11 both had same results 5) Verified other GL programs work

I might be able to try it on a display when my new case arrives.

khturnings commented 5 years ago

Hi All A friend of mine has a pi4 and I got him to test UGS and following the instructions on wiki he too confirmed that the visualizer did not work.

BUT all is not lost, he came up with a partial solution for running UGS as in headless mode.

  1. Follow the Wiki but do not rename the /opt/vc directory to /opt/vc.old
  2. Open a VNC session - this will now work ok.
  3. Now rename /opt/vc to /opt/vc.old
  4. Start UGS by running ugsplatform in normal way.

Now UGS works as does the Visualizer. If running with a screen this is not required I believe.

If I get time I might write a small script to automate the process above and then rename /opt/vc.old back to /opt/vc when UGS closes. If you don't then you will not be able to VNC into the machine a second time and will need to ssh into machine to rename the directory.

Hope this helps

khturnings commented 5 years ago

Upon unloading UGS I saw a number of these messages - i'm not sure if these will be an issue. I have not run it while linked up to my CNC.

MESA-LOADER: failed to retrieve device information libGL error: MESA-LOADER: failed to retrieve device information

khturnings commented 5 years ago

Above error is still not tested but I did write this simple script to automate

Hi All A friend of mine has a pi4 and I got him to test UGS and following the instructions on wiki he too confirmed that the visualizer did not work.

BUT all is not lost, he came up with a partial solution for running UGS as in headless mode.

  1. Follow the Wiki but do not rename the /opt/vc directory to /opt/vc.old
  2. Open a VNC session - this will now work ok.
  3. Now rename /opt/vc to /opt/vc.old
  4. Start UGS by running ugsplatform in normal way.

Now UGS works as does the Visualizer. If running with a screen this is not required I believe.

If I get time I might write a small script to automate the process above and then rename /opt/vc.old back to /opt/vc when UGS closes. If you don't then you will not be able to VNC into the machine a second time and will need to ssh into machine to rename the directory.

Hope this helps

Here is the script I wrote to automate this -

!/bin/sh

sudo mv /opt/vc /opt/vc.old sudo /home/pi/ugsplatform/bin/ugsplatform sudo mv /opt/vc.old /opt/vc echo "Finished"

TheNetStriker commented 4 years ago

@khturnings I found out that the vc file only has to be renamed as long as the application is starting up. After that it can be renamed back and everything seems to work. I've added some lines to you script to automate this:

!/bin/sh

sudo mv /opt/vc /opt/vc.old sudo /home/pi/ugsplatform/bin/ugsplatform & sleep 30 sudo mv /opt/vc.old /opt/vc

If the application needs more than 30 seconds to start up just increase the sleep timeout.

sepiroth887 commented 2 years ago

pretty old thread, but i stumbled here after trying without luck to get the visualizer working on pi 4 bullseye amd64 install with 2.0.12.

Turns out the switch to new openGL handler since this commit d432d5e made everything work :)

khturnings commented 2 years ago

pretty old thread, but i stumbled here after trying without luck to get the visualizer working on pi 4 bullseye amd64 install with 2.0.12.

Turns out the switch to new openGL handler since this commit d432d5e made everything work :)

Thanks for letting us know - I will give the new build on a Pi3 as that's what I have.