Platform UGS properties are stored in your home directory: ClassicĬlassic UGS properties are stored in your home directory, which changes based on the operating system being used:įiles include UniversalGcodeSender.json which contain different settings, and a firmware_config directory which contains several configurations for different firmwares and testing profiles. Occasionally it is useful to attach some of these property files to bug reports to help with reproducing a problem. This can be fixed by clearing out the user cache directory which can be found on the UGS "About" screen seen in the image below.
The user cache is initialized but some objects become corrupt and initialization fails in the future even after upgrading Java. This usually happens if you try running the platform without the required version of Java. Platform Specific Issues Toolbars or Windows don't appear. > UGS > Controller Options.įor both, you need to uncheck or remove the invalid settings in the bottom list: In UGS Platform the option is under Preferences. In UGS Classic the option is in Settings > Gcode Processor Configuration. Those rules should be removed from the gcode processor by going into the controller options. Skipping good commands may lead to broken gcode. Sometimes GRBL will get into an ALARM state and there will be lots of these popups which should not be skipped in the future. The UGS Parser has a configurable list of rules to skip certain patterns, these rules are typically added by a Yes/No dialog asking if you would like to skip the erroneous commands in the future.
#Grbl controller not moving axis drivers
Make sure you have installed any drivers required for your controller.Make sure you are connecting to the correct port.
#Grbl controller not moving axis serial
This happens when UGS connects to a serial port and does not receive the GRBL startup string. Common Problems "Grbl has not finished booting."
0 kommentar(er)
