Do Mcode commands not use the queue?

Home › Forums › TinyG › TinyG Support › Do Mcode commands not use the queue?

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • August 1, 2016 at 3:26 pm #9859
    chorizo
    Member

    I’m trying to get my TinyG based pick and place machine to work with OpenPnP. All of the movement is working fine, but I run into trouble whenever I try to do something that uses Mcode. I have my vacuum (for picking and placing) connected to the spindle and coolant outputs of my TinyG board, and when I try to run a process that involves controlling the vacuum, the Mcode commands are sent all at once, before the machine gets a chance to move.

    OpenPnP has the option to set what response to wait for before sending a new command. I would normally set it to “qr:32”, but Mcode commands either don’t use the queue, or don’t prompt a queue report. OpenPnP suggests using the board’s “ok” response, but the TinyG sends “ok>” when it receives a command and when it finishes one, so that wouldn’t work.

    My question is: is there any response from the TinyG that indicates the completion of both Gcode and Mcode commands?

    August 2, 2016 at 7:21 am #9862
    cmcgrath5035
    Moderator

    I assume you are familiar with the tinyG wiki content, such as

    You might also want to browse about in the Chilipeppr forums. Chilipeppr has a command execution tracker, which I believe is tied to Gcode line (block ) numbers and status reports. Chilipeppr implements a dynamic tinyG buffer fill based flow control.

    You might want to repost this item over at

    It is closer to developers. I suggest you add some comments about your serial flow control strategy.

    Additionally, I assume you have tried a general search on the topic of PNP and tinyG. I have seen several folks discussing projects similar to yours, but I’m not sure how they might relate to use of OpenPNP.

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