Connecting to g2core

To connect to g2core you must have the correct USB drivers on your host computer. We use the g2core-api NodeJS module or Coolterm v1.4.3 for testing g2core. Chilipeppr is a good option for a CNC controller. Other options are Universal G-code Sender, Goko or cncjs

See the g2core Communications page if you need details of the communications protocol. If you are using one of the above communications tools you do not need the page.

Drivers for g2core

OSX

OSX you have everything you need. The drivers will install automatically.

Windows

Windows users need download an INF file in order to use g2core. Use this G2 Windows Driver to download the inf file. Besure to "right click save as when downloading. Note that the g2core USB registration makes it show up in the device list as TinyG v2.

Here is a video tutorial explaining how to install the g2core drivers on windows 7.
www.youtube.com/watch?v=UCF4FoVghsI

Windows 10 does not need this procedure and should work out-of-the-box.

Connecting

Option 1: Choose a G-Code Sender

Several G-Code Senders support g2core. You only need one, so feel free to experiment and choose whichever appeals to you the most:

• CNCjs - Fully featured, and suitable for remote usage.
  • eg set it up on a Raspberry Pi 3, control your CNC, 3D printer, (etc) from that
• Universal G-Code Sender - Desktop/laptop application.
  • Support for g2core is in the nightly builds. Choose "UGS Platform" from the downloads.
• Goko - Desktop/laptop application.
  • Not much development activity recently, but should still work ok.
• Chilipeppr - Requires an online internet connection, and uses Google provided services.
  • Doesn't load if you use an ad blocker.

Option 2: Coolterm 1.4.3

For OSX you can also use Coolterm version 1.4.3. There is a bug in the latest version and 1.4.3 is the latest we have tested that works well. (A bug has been opened with the author who has supported us extremely well throughout this project). Look on this page for this file: CoolTermMac143

• In Coolterm the usb will show up as 2 devices labeled something like:
  • usbmodem14311
  • usbmodem14313

These are the 2 endpoints for the dual endpoint USB connection. You can connect to either and it will work. For most purposes that's all you need.

If you want to run dual port mode, the first port opened will become a control and data port. If you open the second port it will become a data port, and the first will become control-only. Send Gcode to the data port, and everything else to the control port. All responses, status reports and exception reports will be returned to the control port - no text will be sent to the data port. This way you can queue a lengthy gcode file to the data port, while still having access to controls.