Pinout – Due w/ external drivers (Gshield.bin)

Home Forums TinyG TinyG Support Pinout – Due w/ external drivers (Gshield.bin)

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #9751
    MaxFrenzy
    Member

    I programmed a Due via Chilipeppr over native USB with the latest gshield.bin. The plan is to use external drivers, but use the gshield pinout to make things a bit more organized (which might not actually be the case), but at least its a common binary file. After I flashed the due, I realized that I didn’t know what pins a gshield occupied on the due. Since the only “official” .bin compiled for the due is for a gshield, I figured I should use the DUE pinout diagram from the G2 wiki. (Note: I know the motate pinout explains everything I need to know. I’m still a bit confused by parts of it.

    Either way, the plan is to use the DUE with Gecko 251x drivers. I want to see if I have the pinout numbers and which ones to use correct:

    Gecko 251X has a 12 pin terminal block with the following pins:
    1. Power Ground
    2. Power (+) 15-50 VDC
    3. Current Set (resister)
    4. Current set (resister)
    5-8. A+, A-, B+, B- (stepper motor)
    9. Direction
    10. Step
    11. Disable – This terminal will force the winding currents to zero when shorted to ground (TERMINAL 12).
    12. Common – Connect this to your logic (controller) ground.

    So really, we’re only concerned with pins 9, 10, 11, 12 (dir, step, disable, common) as it relates to connecting to the DUE

    For Motors 1-4 (x,y,z,a) as referenced from the wiki due diagram, using the pin numbers actually labeled on the DUE itself (link to diagram):
    Direction – Due pins: 5 (m1dir), 6 (m2dir), 7 (m3dir), 32 (m4dir)

    Step – Due pins: 2 (m1step), 3 (m2step), 4 (m3step), 31 (m4step)

    Disable (would these go to enable pins or perhaps vref pins?) – Due pins: 22 (m1enab), 25 (m2enab), 28 (m3enab), 33 (m4enab) || (or) 34 (m1vref), A8 (m2vref), A9 (m3vref), A10 (m4vref)

    Common – Any Due ground pin? Isolate each driver to a separate ground pin?

    Regarding power management, the hope is still to be able to use it to turn off the motors after $MT timeout. If the enable pins are brought low (0v) after timeout, then it seems like it might work? I’m not sure if that’s actually the case. Any advice is appreciated.

    Thanks
    Matt

    #9776
    cmcgrath5035
    Moderator

    m_vref pins are analog outputs for setting motor power level.
    Could be made to work with your Gecko’s, but non-trivial.

    Have a look at this post:

    Might help understand pin configuration.

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