How to reset TinyG?

Home Forums TinyG TinyG Support How to reset TinyG?

Tagged: 

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #5084
    tomking505
    Member

    I was working most of the weekend with my TinyG. Sometimes fristrating, often a lot of fun. Until my TinyG stopped talking to me.

    I was getting ready to rehome after my spindle hit a hold down. First I moved the spindle to Y=0, and it did that. But when I issued x=0, nothing happened. Then I noticed that TinyG stopped talking on CoolTerm.

    I power cycled the 24V supply for the TinyG. I restarted my laptop. My card is in a metal case, with a big fan on it. Nothing has moved or changed about my power supply or electronics.

    The PWM red LED is on solid, and so is the blue power LED. The RX light blinks when I hit return, sometimes he TX. No response on CoolTerm.

    How do I reset the board? How do I test to figure out the problem?

    Cheers!

    #5085
    alden
    Member

    Sounds like yolu have done most of the right things. Most likely the USB connection between the board and the host is at fault. You can try the following steps – in roughly this order. Once we found a bad USB cable. Wasted quite a few minutes on that one. Are you on Mac, PC or Linux?

    – Power cycle the TinyG board. Let the power LED stay off for a few seconds before turning it back on
    – Physically disconnect the USB and replug
    – Disconnect coolterm session, rescan ports, and reconnect
    – Kill coolterm terminal and generate a new one. Saved settings is helpful.
    – Kill coolterm and restart
    – Reboot your host.

    • This reply was modified 10 years, 11 months ago by alden.
    #5087
    JuKu
    Member

    Also worth checking: USB devices dometimes renumber themselves. In other words, check that serial port number is still correct.

    #5088
    tomking505
    Member

    You were right.

    It sounded crazy, because I did I did everything you said except for disconnecting the cable. But I followed your instructions. After reconnecting the USB cord, everything worked correctly.

    No idea what could go wrong with the cable between issuing a Y command and issuing a X command. But everything is working again.

    Thanks for your help, Alden.

    Tom

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