TinyG initialization commands

Home › Forums › TinyG › TinyG Support › TinyG initialization commands

Tagged: 

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • April 21, 2015 at 9:57 pm #7649
    SecondSource
    Member

    Hi

    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.

    April 22, 2015 at 12:09 pm #7650
    cmcgrath5035
    Moderator

    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

    How does LabView do flow control?
    tinyG supports Xon/Xoff and RTS/CTS.
    Chilipeppr (SPJS actually) does it’s own flow and buffer management.

  • Author
    Posts
Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.