Getting GRBLshield to work with a 168

Home › Forums › gShield › grblShield Support › Getting GRBLshield to work with a 168

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • August 7, 2011 at 5:56 am #1638
    alistairallan
    Member

    I just started trying to get my grblshield to work yesterday but with no luck using 0.6b 168 .HEX from github (I’m not using a 328p board, but have just ordered one).

    Using G-Ctrl I can send commands and they are acknowledged but I get no movement from the motor (only x attached at this point).

    To test the shield I created a little sketch to test, by simply attaching stepper to X connector and sending pulses to pin 2 (X step) and also testing direction (pin 5).

    That seemed to work fine, I could drive the motor in both directions with the shield.

    There are two things which would be helpful for newbies on the wiki
    -Pin-outs for the shield would be helpful
    -A list of what’s in the Patched version of GRBL

    Should the standard 0.6b 168 .HEX from github work with the GRBLSHIELD?

    Thanks

    August 8, 2011 at 8:50 pm #1639
    alden
    Member

    I don’t know the status of the grblshield changes in the v0_6b 168 package. Here’s the background.

    We submitted a pull request to the grbl project on March 1, 2011 that was incorporated into the edge branch sometime later. You can find the details by looking at the closed pull requests in the edge branch on the grbl github. The changes were:

    – Changed the default invert mask in settings.c to 0x1C to support active LO stepper drivers

    – Changed stepper enable to be active LO in steppers.c/.h
    This is the most crucial change. If you look for occurrences of STEPPERS_DISABLE_BIT in steppers.c in the edge branch you will see what grbl changed that to. (It’s different than what we had in the pull request, but gets the job done… so no matter)

    – We also did some things with the serial read to make it work in an WinAVR/AVRStudio environment.

    We have not made a 168 version of the patched grblshield code and to my knowledge the grblshield patches have not been incorporated into the grbl master branch or the v0_51 branch. AFAIK the v0_51 is the only one that supports the 168 – which is now considered legacy by grbl.

    If you wanted to hack the v0_51 branch for the grblshield patch you should look at the above changes applied to the edge branch and make at least the first 2 to the v0_51 branch

    Or just wait for your 368 to arrive. 🙂

    Hope this helps

    Alden

    August 9, 2011 at 6:25 pm #1640
    alistairallan
    Member

    Thanks for this Alden, I’ll have a bash at getting the 168 arduino to work with 0.6b. failing that I suppose I’ll use the 328.

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