cmcgrath5035

tinyG does have limitations on some G2 and G3 moves.
It has implemented rather strict check for arc start and end points based on gCode specifications.
Is this manually generated gCode, or output from a CAD to gCode translator?
Are you in inch mode or mm mode? MM frequently works better. All tinyG internals are in mm, inch commands and data are converted first into mm, with some inevitable loss of precision(its 8 bit math).

the CP display on screen is essentially a gCode plotting package and does not include the rules checking that goes on within tinG

That of course depends on your definition of ‘control’ and the desired sophistication of your work flow.

A quick short list would include:
CoolTerm – Terminal emulator for CLI level control and a basic file sender
UGS (Universal gCode Sender) –
CNC.js –
Goko –

You’ll have to dig in to their on-line documentation to see if they fit your needs.

Hmm, no OSX experience here, but in Linux land I would suggest opening a command console and running DMESG right after removing, then reinserting the USB into the MAC. There you would see OS messaging as the hardware was initialized.
I assume MAC has something similar.
From what you have reported so far, it does sound like a driver or perhaps a USB cable issue. Fact is, as long as the Blue led is lit on V8, the FTDI UASB to Serial device is powered and the connection should appear on the MAC side, whether or not tinyG firmware is actually booted.
Does tinyG boot up? That would be flashing SPN/DIR for a few seconds, then a quick flash from the tx/rx leds.

we went into alarm and the spindle stopped travelling in mid cut

What do you mean by “went into alarm” ?
Sounds like it shut down as if a limit switch was hit?
That would cause tinyG to reset and the current coordinate would become the new (zero, zero) after a reset.

I would doubt this is CP/internet related. First reaction would be noise induced false limit switch indication.

I think you are on the right track.
It is unclear to me if the DUE has USB Host capability, which is likely required for the controller DUE.

Many in this space use RaspPi or BeagkleBoards for the controller side.
Folks have actually ported the entire Chilipeppr environment to a RPi3.

Good Luck with your hunt

When you built 101.03, did you build for DUE-gShield?
BTW, there as a pre-built version here https://github.com/synthetos/g2/releases/download/101.03/g2core-gShield-101.03.bin

Check that the Motors are enabled, I believe that they are disabled by the default settings.h.

This does sort of sound like a config issue

Not much traffic here at this level of detail.
I’d suggest a question be posted at https://github.com/synthetos/TinyG/issues.
The developers hang out there.
If you are using G2core, then https://github.com/synthetos/g2/issues