-
Notifications
You must be signed in to change notification settings - Fork 296
Getting Started with g2core
G2core is an Open Source CNC, 3D Printer, and general stepper-motor-based motion control firmware that runs on the next generation of g2core hardware as well as the Arduino Due.
You will need whatever machine you are trying to control, such as a CNC machine, 3D printer, laser cutter, etc., along with the general knowledge of how to use that machine safely.
You will also need software to generate GCode.
The following is a list of the minimum you will need strictly for g2core, regardless of what project you'll be using it for.
Compatible Target Board - Arduino Due (~$50) (Digi-Key, Newark, Sparkfun, Maker Shed)
- Currently the only publicly-available board g2core works on is the Arduino Due.
- We plan to release the gQuadratic and gQuintic boards in fall 2016 that will also run g2core.
Adapter Cabling/Shield
If you're only going to use 3 axes (XYZ), the most popular shield is the gShield ($50) (Synthetos Store, Adafruit, Inventables), or roll-your-own cabling.
- The gShield provides three stepper drivers and pinouts for spindle controls and limit switches.
- Depending on the project and your level of expertise, you may be able to wire stepper drivers you already have (as long as they have STEP/DIRECTION/ENABLE pinouts) to the Due or roll your own shield.
For using more axes (eg 4th, 5th, or 6th axes), the most popular options are the DJuke shields. There are two to choose from, depending on your needs:
- g2core shield (onboard drivers) - Choose this one if you're using smaller stepper motor drivers. eg Pololu
- g2core shield (external drivers) - Choose this one if your using external stepper motor drivers. eg DM542
For doing development of g2core itself, you'll need a hardware debugger. People just wanting to use g2core and not do development can completely skip this bit. 😄
Debugger/Programmer - Atmel-ICE debugger on Mouser and Digikey.
- You can program the Due and the TinyG v9 boards without a debugger, but to do realtime debugging you need an ICE of some sort.
- Note that the Atmel-ICE is not the Atmel SAM-ICE or the Atmel JTAG-ICE. The Atmel SAM-ICE will work as well, but is older and more expensive. All the examples on this site use the Atmel-ICE.
If you are not planning on compiling the firmware yourself, then all you need is the Arduino 1.5+ IDE installed on your machine (for the bossac
binary). You can then program any provided hex directly onto the Due or TinyG v9.
Getting Started Pages
- Home
- What is g2core?
- Who uses g2core?
- Jerk-Controlled Motion
- Getting Started with g2core
- Connecting to g2core
- Configuring g2core
- Flashing g2core
- Troubleshooting
Reference Pages
- Gcodes
- Mcodes
- Text Mode
- JSON Communications
- GPIO Digital IO
- Alarms & Exceptions
- Power Management
- Coordinate Systems
- Status Reports
- Status Codes
- G2 Communications
- Tool Offsets and Selection
- Probing
- Feedhold, Resume, Job Kill
- Marlin Compatibility
- 9 Axis UVW Operation
- gQuintic Specs
Discussion Topics
- Roadmap
- GPIO for 1.X Releases
- Toolheads
- Raster Streaming Prototol
- g2core REST Interface
- Gcode Parsing
- G2 3DP Dialect
- Consensus Gcode
- Digital DRO
- Overview of Motion Processing
Developer Pages
- Development & Contribution
- Branching and Release - DRAFT
- Getting Started with g2core Development
- Project Structure & Motate
- Compiling G2
- OSX w/Xcode
- OSX/Linux Command Line
- Windows10 w/AtmelStudio7
- Debugging G2 on OSX
- Board and Machine Profiles
- Arduino Due Pinout
- Arduino DUE External Interfaces
- Diagnostics
- Debugging w/Motate Pins
- Development Troubleshooting
- g2core Communications
- Git Procedures
- Windows 10 / VMware 8 Issues
- Dual Endpoint USB Internals
- G2core License
- VSCode Setup
- Compatibility Axioms
- Wiki History