Troubleshooting Overview - stodev-com-br/Universal-G-Code-Sender GitHub Wiki

Is the problem UGS, the controller, or CAM?

Many issues and requests for help are not actually specific to UGS, some of these are related to connecting to the controller, while others are CAM related.

UGS has three simple primary missions:

  1. Take G-code from your computer and send it to your controller.
  2. Send signals to your controller for setting up jobs. Examples: Homing, Jogging and setting Work Coordinate System (WCS) manually.
  3. Displaying and changing controller status. Examples: seeing alarm statuses and clearing them, toggling coolant, or adjusting speed+feed overrides, or pausing the program.

UGS does have additional secondary missions through plugins. Some of these are:

  1. Dowel pin creation.
  2. Probe wizard to automatically set WCS.
  3. Workflow manager to help with tool changes between separate programs.

If your problem doesn't fit into the above, it may be that the problem is actually outside of UGS. The following table can help you figure out where to look:

Description Likely Components
Strange motion Controller
Work Coordinate System changes between restarts of controller Controller
Work Coordinate System changes between programs CAM or Controller
Unable to connect to controller Controller

UGS is not starting properly

Recent Upgrade - Reset Preferences

If you have recently upgraded UGS and it has been a long time since the previous upgrade, sometimes the preference files need to be reset. Preferences are kept in a user directory called .ugsplatform for v2.0 and .ugs for v1.0, and deleting (or renaming) this directory will reset UGS back to the defaults.

The exact path varies between the major operating systems because of where they keep user data. Check out these pages for where the settings are located:

Java Version

Currently UGS Platform requires Java 8. More recent versions of Java may or may not work. Ticket #1151 shows how to change Java versions for several operating systems.

Antivirus software

There has been cases where the antivirus software caused a problem with a popup that wasn't able to close. The issue was resolved by disabling the antivirus software: https://github.com/winder/Universal-G-Code-Sender/issues/1237

Errors have been reported with Antivirus softwares:

  • Comodo
  • Trend Micro

Error message "Assistive Technology not found"

On KDE Neon 5.16 with OpenJDK 1.8.0_212 a user got the follwing error message (https://github.com/winder/Universal-G-Code-Sender/issues/1267):

./start.sh 
Exception in thread "main" java.awt.AWTError: Assistive Technology not found: org.GNOME.Accessibility.AtkWrapper
        at java.awt.Toolkit.loadAssistiveTechnologies(Toolkit.java:807)
        at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:886)
        at sun.swing.SwingUtilities2.getSystemMnemonicKeyMask(SwingUtilities2.java:2020)
        at javax.swing.plaf.basic.BasicLookAndFeel.initComponentDefaults(BasicLookAndFeel.java:1158)
        at javax.swing.plaf.metal.MetalLookAndFeel.initComponentDefaults(MetalLookAndFeel.java:431)
        at javax.swing.plaf.basic.BasicLookAndFeel.getDefaults(BasicLookAndFeel.java:148)
        at javax.swing.plaf.metal.MetalLookAndFeel.getDefaults(MetalLookAndFeel.java:1577)
        at javax.swing.UIManager.setLookAndFeel(UIManager.java:539)
        at javax.swing.UIManager.setLookAndFeel(UIManager.java:579)
        at javax.swing.UIManager.initializeDefaultLAF(UIManager.java:1349)
        at javax.swing.UIManager.initialize(UIManager.java:1459)
        at javax.swing.UIManager.maybeInitialize(UIManager.java:1426)
        at javax.swing.UIManager.getInstalledLookAndFeels(UIManager.java:419)
        at com.willwinder.universalgcodesender.MainWindow.main(MainWindow.java:180)

To solve this, edit the accessibility.properties file for OpenJDK:

sudo vim /etc/java-8-openjdk/accessibility.properties

Comment out the following line:

assistive_technologies=org.GNOME.Accessibility.AtkWrapper

Other problems

If UGS is still not starting properly, we encourage gathering and looking through the messages.log file for clues, then asking for help on the Google Group, attaching the most recent log / post them to somewhere like Pastebin or create a Github Gist. messages.log can be found at these locations depending on your OS.

"Grbl has not finished booting."

This happens when UGS connects to a serial port and does not receive the GRBL startup string. Typically this is caused by a configuration problem and can be solved by one of the following:

  • Check the baud rate is 115200, or 9600 for very old versions of grbl.
  • Make sure you are connecting to the correct port.
  • Make sure you have installed any drivers required for your controller.
  • Make sure GRBL is properly flashed on your controller.

Program Slows Down and Send Freezes

If you notice slowness while running your program, it may mean UGS is running out of available memory. There are a couple things to try:

  • Check the controller settings, and make sure "Arc Expander" is not enabled. This can take a small program and turn it into a very large one by converting arcs into many small movements.
  • Increase the memory allocated to UGS by navigating the the installation directory. There is a folder named etc containing ugsplatform.conf, open this file with a simple text editor and modify the value of Xms to something like -J-Xms256m, or larger. Additional details can be found here

Open Issues

Found a problem? Check the list of open issues and see if someone is already working on it.