In this post, cmcgrath5035 mentioned “When CP starts up, it sends a sequence of initialization commands to tinyG, to ensure that both ends are ‘in sync’.”
I am writing code in Labview to drive a Shapeoko 2 / Arduino Due, bashing gcode commands through the serial port, and it does not seem to connect as reliably as Chillipeppr.
Do you have any idea what the initialization command sequence for the tinyg consists of? Thanks for any advice.
Easiest way is to start up CP/tinyG, clear the Serial Port Console scroll area, then connect to tinyG.
You will see the sequence of commands, and responses, scroll thru the console.
These are tinyG commands, not GCode.
If you continue to have issues, report the FW build of G2 you are using.
Some versions had issues with some of the commands.
Also, have you seen/reviewed
.
