michaelrommel

Wow, Zootalaws, those are very thorough instructions – I highly appreciate that! I am waiting for my Due to arrive and also for the breakout shield, that I ordered from Djuke in the Netherlands.

I am building the CNC frame and the base that it sits upon right now. It will be a couple of weeks, until all is ready. I tend to look ahead quite a bit, since many times, the ordering and shipment process takes quite long, especially if you order some parts from China, as most of us hobby CNC users do.

The big decision I had to make – and the reason for this post and asking for advice – was whether it is a reasonable and „future-proof“ path to switch from an integrated solution (Arduino+grbl+board-with-4-drivers) to a modular solution (due+tinyg2core plus external drivers) which in the end would allow me to drive my 2 Y Axis and an additional A axis so I would end up with 5 drivers.

It seems this is the way to go, as there IS development and community around g2core! I am very happy and am looking forward to being part of this community and endeavour!

Thanks for all the help!!

Michael.

Hello all,

thank you for your comments, it is good to see that there seems to be some activities out there, that I didn‘t find.

I am considering to switch from a grbl based system with integrated motor drivers to a Arduino Due with Tiny G2core firmware, because I can then use external drivers (read: closed loop).

Now in researching github and the forums, it seems, that there is very little development going on and there is not a synthetos‘ own board available that lets you use external drivers which would make it easier to get support officially from synthetos.

You mentioned an Ox Forum – where there are people using g2core and can report on functionality or stability? Where is that forum? When I go the the OpenBuilds forum and search for TinyG, G2 or g2core, nothing comes up!

I have read every single page in the g2 wiki, but they still leave some questions open, e.g. it is mentioned that the Due/the processor has no eepro storage there is no persistence of settings, so, how does everybody store the machine setting? Do they always re-compile the firmware and flash it, once they have the need to change a setting?

There is no problem in compiling the stuff (I‘m on Mac OS but also have some Linux machines around (ia64 based and arm based).

I am also looking around, what may be the best way to send gcode to such a setup (chilipeppr is one option I know) – a simple minimal GUI with a few buttons like performing jogging, homing and loading/sending a gcode file would be sufficient.

If there is anyone around here, that can provide some tipps or a link to the above mentioned forum – many thanks!

Michael.