hangs due to attempted use of touch plate during program

Home › Forums › TinyG › TinyG Support › hangs due to attempted use of touch plate during program

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • September 8, 2016 at 11:09 pm #9904
    ehrichweiss
    Member

    This has been driving me nuts the past few days. I thought the problem was stemming from my tool change macro but when I finally reduced it back down to just an M6, I realized it was happening due to the TinyG.

    I just made myself a touch plate and it works fine if I start from a complete reboot of TinyG, json server, and ChiliPeppr but if I try to do a M6 tool change in a program and then attempt to use G38.2 Z-20 F25(what ChiliPeppr sends for the touch plate), the system seems to hang and I get no response from the TinyG(I’m fairly certain the lights stop blinking at all). If I try to do a TinyG reset from the ChiliPeppr interface, no lights blink and no response. If I then try resetting the json server(thinking that it might be the problem) sometimes it will work just fine but most of the time that’s not the case. I have tried resetting the json server first and same thing. The only thing that consistently gets everything working again is a hardware reset of the TinyG, but like I said, sometimes it will take a software reset of either the TinyG or json server to do the trick.

    Now, a fine point to put on it. When I soft reset TinyG and restart, connect, select the TinyG, etc. with the json server, the server seems to detect and connect to the TinyG just fine even though there doesn’t seem to be any form of response on the software level from the TinyG. I guess that could be something cached but felt that it might help you work out the issue.

    My json server is v1.92 and the results from $$ on my TinyG are below. I’ll answer any questions as best I can.

    http://pastebin.com/Mtka3DU0

    • This topic was modified 8 years, 2 months ago by ehrichweiss.
    September 9, 2016 at 10:52 am #9906
    ehrichweiss
    Member

    Oh, I should also emphasize that this all happens in the middle of a program. If I do it before a program or after it, there aren’t any problems that I’m aware of. Also, jogging, and the like work just fine when I hit an M6. It’s just the touch off command, or that’s what it seems to be.

    September 10, 2016 at 7:16 am #9907
    cmcgrath5035
    Moderator

    I am a little confused as to what is actually being sent to tinyG.
    Per tinyG Wiki

    The M6 Gcode command is “no operation at this time”, which to me translates to Not supported , but I have never tried it.
    If you are sending M6, what internal state tinyG ends up in might be indeterminate.

    Perhaps it would be helpful to post (Pastebin worked just fine) a short Gcode file that exhibits the issue.

    You might also want to review this (somewhat dated) thread

    September 10, 2016 at 12:39 pm #9908
    ehrichweiss
    Member

    I have ran other programs with M6 in them(actually they also had a G43 in the tool macro as well even though I didn’t use it). ChiliPeppr pauses, I do my tool change and jog everything manually where it needed to be, then hit pause and it ran fine. It didn’t seem to be affected by the M6 at all in that regard. It’s only when I try to use the touch plate that everything locks up. I just looked again and I think I may have seen “G28.2” and written “G38.2” because I don’t see G38 now at all but that’s beside the point I think.

    I read that thread and I was wondering if I wouldn’t be forced to run each part of the program separately. If it would be possible to make it so that the touch plate sequence can run in the middle of a program after some form of pause, that would be great. Otherwise I guess I’ll just do separate programs for each tool for now.

    September 11, 2016 at 6:35 am #9909
    cmcgrath5035
    Moderator

    The way I read my previous references(wiki, issues), M6 is not ‘rejected’ by tinyG, rather some code runs but apparently, as you are finding, not completely or correctly.
    I would suggest you open a new issue at

    requesting status update on M6 Gcode command support, referencing Issue 75 this thread and any others you have over at Chilipeppr that make clear what you are trying to do.

    The gitHub/Issues are managed by the developers directly.

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