Possibly burned out Y axis

Home Forums gShield grblShield Support Possibly burned out Y axis

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #5778
    pyrohmstr
    Member

    I have a gShield V5 with an arduino Uno. I flashed grbl to the arduino no problem and everything ran perfectly for about an hour. The pots are set correctly and all of the lights were good.

    At one point I powered everything down, soldered a header to the D8 block (no bridges or anything), plugged in a Y axis hard limit switch, changed the settings, and everything worked once. The hard limit tripped the alarm, which I could clear and continue using. I tried issuing the home command and the motors wouldn’t turn. After that, the Y axis totally stopped responding. No movement, no flashing green light. I changed the settings back to their defaults and it sill won’t work. X still works.

    I reflashed grbl to the arduino (using atmel studio 6 and grbl_v0_8c_atmega328p_16mhz_9600.hex), unplugged my switches, and set it up the same as the last known-working setup. No luck, still no green light or movement on Y.

    I tried the motor on the X and Z axis, the motor works fine then. Other motors that work on X don’t work on Y.

    My PSU is good. 12V 3A for a .6A and 1.2A motor.

    The pot isn’t broken and measuring the voltage on it seems correct.

    I’ve checked all the pins and everything looks physically good.

    grbl itself seems to be working just fine, all settings are default. I’m using Universal Gcode sender but it shows the same behavior with gcodesender and sublime text 2 (through the serial control)

    So, is there a way to determine if the controller itself went bad? I had the pots set at half and the thing has worked less than one day.

    If the controller is bad, is there anything I can do? Can I replace the chip or should I look into returning it? I don’t know if adding the header would void any warranty on the board.

    Thanks in advance for any insight y’all can give.

Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.