1.5.0 Released https://github.com/duembeg/gsat/tree/v1.5.0 Changes in 1.5.0: * Added support for .

General CNC CNC Routers
,
1

1.5.0 #gsat Released

Changes in 1.5.0:

  • Added support for #TinyG2.
  • Added support for Mac OS X Mavericks with working OpenCV.
  • Added run time dialog at end of program run (configurable option).
  • Added PAUSE state, tool-bar button and menu item, in pause state run time continues.
  • Added machine setting for grbl, tinyg, or #TinyG2.
  • Added machine setting for initialization script, useful to send setup commands after device connect detect.
  • Added machine run time status.
  • Added machine Auto Status request setting (mainly for Grbl not needed with TinyG(2)).
  • Consolidated Link and Machine setting panels (require a one time reconfiguration of port and baud when upgrading from old version).
  • Added jog settings to auto update from machine status.
  • Added jog settings to auto request update from machine after jog set operation that don’t normally generate verbose information, like set to zero or set to job values.
  • Added jog custom button support for scripts.
  • Removed second set of XYZ coordinates and enlarge the reminding for ease of view at a distance.
  • Updated G-Code message dialog, it is now treated as entering * PAUSE state (run time continues).
  • Fixed bug with missing variable “serialBaud” not found when changing settings while serial port was open.
  • Fixed bug with File->Open being enabled while RUN state was active.
  • Fixed multiple UI issues with Mac OS X
  • Moved decode of status string processing to program exec thread, this will help UI from becoming temporarily unresponsive.

1680×1023 480 KB

2

What is the main differentiator for Gsat? Is it just an alternative Gcode sender? Or are there specific use cases you are solving that other Gcode senders don’t solve? I think the webcam view is cool.

3

I made gsat while back, the big idea is to treat Gcode as any other code. For example if debugging C code on a PC or an embedded device one can put breakpoints analyze what is going on with the machine registers, memory, program counter (PC) and many other aspects of a machine and also to modify them at will… gsat allows one to treat Gcode and the device Grbl, TinyG, or TinyG2 in a similar manner. Being able to set breakpoints and change/align, or modify the state of the machine and or execute only parts of the code. For example execute a second time but only for the last pass for a pocket operation. Also to modify the Gcode itself.

The camera view is for alignment; with a camera properly mounted and calibrate to a known offset of the tool. With this setup one can actually target say a drill hole with the camera and then just move the known distance to the tool (have to know your machine backlash), reset the machine coordinates to those coordinates and continue with a drill program. All of these allows one to change tools or even remove the workpiece come back and verify aliment before continuing the program or move to another program.

Other features like init script after device detect useful for devices like TinyG2 (Arduino DUE) which currently requires recompile of the code to have new settings saved, with the init script, these can be setup upon connect. But you can get a fuller picture at the github readme file.