TinyG stops responding after (failed?) Home Z

Home › Forums › TinyG › TinyG Support › TinyG stops responding after (failed?) Home Z

Tagged: 

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • June 4, 2024 at 1:30 pm #12178
    jimtellier
    Member

    It *may* be coincidence, but I was (finally, after a long absence) getting back to testing my “Frankenstein” CNC router setup. Started up the TinyG, did a few trial X, Y and Z axis jogs, and after seeing signs of life, I tried to “home” each axis (X,Y then Z). I didn’t see a response from the Z operation, and subsequently No operations have any effect. Including “$$”, “sr”, “pos”, or any other G or M cmds. I’ve done a physical “reset” of the board (no effect), and cycled power and retried. The COM port status says it’s connected, and that changes appropriately with power cycling. Does anyone have any similar experiences or thoughts on how to proceed?
    Thanks very much!
    Jim

    June 4, 2024 at 1:41 pm #12179
    mristau
    Member

    What app are you using to send commands?

    I posted a question a week or so ago and got a response in a day or two. Patience I suppose.

    Have you tried contacting directly instead of posting to forum?

    • This reply was modified 5 months, 1 week ago by mristau.
    June 4, 2024 at 3:46 pm #12181
    jimtellier
    Member

    That’s a good idea; maybe they don’t troll the forum all that much?! Thanks! 🙂

    June 4, 2024 at 4:02 pm #12182
    mristau
    Member

    What app are you using to send commands?
    Are you using the same computer as you were previous use?

    June 5, 2024 at 8:50 am #12183
    cmcgrath5035
    Moderator

    jimtellier: You describe an odd (apparent) failure, indeed. Understanding your method of communications with TinyG might help. Could be a basic terminal window (putty, coolterm, etc) or a more complex interface such as chillipeppr. The serial interface on TinyG is a ftdi chip, it may be reporting ‘ok’ to your control computer without TingG FW actually running.
    When connected, a tinyG reboot (button press or power cycle) should yield the TinyG prompt in a command window when FW initializes.
    Homing Z axis was implemented by only a few users; do you actually have a limit switch installed at top of travel? Did Home to Z ever work? You might try disconnecting Z wires from TinyG to see if you can recover basic control
    I (am supposed to) get a message from this Forum when someone posts; this is the first I have seen in over a year. There is occasional activity at https://github.com/synthetos/TinyG/issues , but not much.

    June 5, 2024 at 8:51 am #12184
    cmcgrath5035
    Moderator

    added to set notification reminders

    June 5, 2024 at 9:40 am #12185
    jimtellier
    Member

    I think I mentioned on the post I put in the Wiki forum that I’m using custom software (that I wrote several years ago, which has been working fine). I do in fact have a Z limit switch implemented, and I’ve always homed all axes without issues.
    Now…. having said all that, I *think* my issue may have been resolved after doing a full PC reboot and a couple of TinyG power cycles. (I hate it when things just “go away”!). I’m just getting back to using my rig after a long time off, so I’ll be watching it closely! Thanks for the quick response!

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