Topic: TinyG2 pinout diagram questions

Tagged: Tinyg2 pinout diagram arduino Due gshield

This topic has 16 replies, 5 voices, and was last updated 4 years, 9 months ago by therobotguyllc.

Viewing 15 posts - 1 through 15 (of 17 total)

1 2 →

Author

Posts
December 13, 2016 at 4:50 am #10075

SecondSource
Member

Hi I was happy to find a TinyG2 pinout diagram at:
https://github.com/synthetos/g2/wiki/Arduino-DUE-Pinout-for-g2core

But after looking it over I started to wonder what some of the pin definitions mean, and I cannot find any reference to them. For example:
Pin 36 is labelled m4ms1
Pin 26 is labelled m2ms0
Pin 34 is labelled m1vref

I think the ‘m4’ part refers to motor 4 but what do ms0, ms1 and vref refer to with respect to each of the motors? Is there some place I can look these definitions up?

One other thing, is this pinout likely to be consistent with the latest build of g2core? Or have pins changed over time?

Thanks for any advice.

December 13, 2016 at 5:57 am #10076

Zootalaws
Member

M1vref is motor 1 voltage reference, used for tuning your motor power,

M2ms0’is motor 2 microstepping pin 0
M4ms1 is motor 4 microstepping pin 1

microstepping is set in binary, so pin 0 + pin1:

00 – 0
01 – 1
10 – 2
11 – 3

December 13, 2016 at 8:12 am #10077

SecondSource
Member

Excellent thanks a lot for the speedy reply!
That clears it up. Much appreciated.

December 13, 2016 at 8:17 am #10078

SecondSource
Member

Oh the other thing was re. the TinyG2 pinout diagram at:
https://github.com/synthetos/g2/wiki/Arduino-DUE-Pinout-for-g2core

Is this pinout likely to be consistent with the latest build of g2core? Or have pins changed over time?

Thx

December 13, 2016 at 9:44 pm #10081

cmcgrath5035
Moderator

I have not looked at recent G2 Core builds, but doubt that the default pin assignments have changed.

The Motate pin reassignment layer in G2 is very powerful but comes with side effects. As you can imagine, folks seeking help here in the forum might forget to mention that they a recompiled with different I/O and it could take a lot of cycles to figure that out!

I believe it safe to assume that mainstream G2 builds remain targeted to DUE with a Gshield as an introductory test platform. But a lot of folks are using G2 in various applications, so you may find custom builds with very different characteristics.

December 14, 2016 at 4:33 am #10082

SecondSource
Member

Great thanks for the information cmcgrath5035.
All the best.

May 13, 2018 at 1:23 pm #10982
typ1804
Member
Evening,
im currently at the state to directly connect a DRV8825-driver to an arduino due board. This is my current state:

https://www.dropbox.com/s/588t5ciklh0mb4c/g2core_drv8825.pdf?dl=0

based on

https://github.com/synthetos/g2/wiki/Arduino-DUE-Pinout-for-g2core

But i cant get a grasp on the microstepping connections. m1ms0 and m1ms1 are clear but whats with m1ms2. where is it comming from?
Basend on the information from https://www.pololu.com/product/2133 i assume ms2 needs to be connected separately. Is that correct?

Furtermore is my understanding that the output for m1vref is only for measurements and must not be connected. Is that correct?

Hints are appreciated
- This reply was modified 6 years, 4 months ago by typ1804. Reason: forget something
May 13, 2018 at 2:24 pm #10984

cmcgrath5035
Moderator

It has been a long time since I created that pin-out diagram, had to stare at it a while to refresh what is going on.

I believe the following to still be correct:
Microstepping – the pinout for all 6 motors only supports microstepping for 1,2,4 and 8 microsteps per step; 4 states, needs 2 bits.
The Due pinout was created with Gshield in mind, whose drivers only do up to 8 microstepping.
There are not enough pins on a DUE to support ALL G2core functionality; this default pinout supports 6 motors with partial functionality. If you want to control more detailed microstepping individually, you will have to sacrifice some other pinned out functionality to gain access to M1MS2(etc.)

m1vref is an analog output (D/A) meant to control 8825 Power between 0 and 100%. The Pololu headers do not support the feature read up on the 8825 driver device to see how stepper current is made adjustable.
The default pin-out for the DUE has m[1-6]vref outputs.
See https://github.com/synthetos/g2/wiki/Configuring-0.99-Motors#1pl-power-level

If you do not want software based power control, you could map the vref pins to something else, such as m[1-6]ms2. Read up on Motate

May 13, 2018 at 3:00 pm #10985

typ1804
Member

Thank you very much for this fast and detailed answer. i have not chosen what i will do but youre answer is very helpfull

May 15, 2018 at 1:40 pm #10988

typ1804
Member

i´ve recently seen the update to 9 axis (https://github.com/synthetos/g2/wiki/9-Axis-UVW-Operation) but i can´t find any information how to connect 3 new motors to the board…will there be any updates to the pinout?

May 19, 2018 at 3:38 pm #10989

cmcgrath5035
Moderator

Thanks for the heads up about 101.02 release, I missed that.

There is no DUE/gShield build yet either, not sure why.
As we already know, the current list of assigned pins does not leave much room, so I feel safe in saying that the answer will be decide what you don’t need with the current mapping and use Motate to create your own.

Keep your eyes out for an update, I have asked the devs for some guidance.

May 20, 2018 at 11:58 am #10990

cmcgrath5035
Moderator

OK, A G2core build for DUE/gShield is now available here: https://github.com/synthetos/g2/releases

As best I can tell, pinouts have not changed but you could rebuild a custom.
As I understand the notes, you could now map ases W,U and V to existing pinouts if you had Gcode file that needed it.

Also note that X,Y,Z and W,U,V are linear axes, ABC are still rotational be design.
Review the wiki for early comments on motion coupling among the various axes

December 9, 2019 at 10:52 am #11714

therobotguyllc
Member

Greetings,

I am trying to convert my old Uno/GRBL system to a tinyg2/Due system and I think I have the software working but I had a few questions about the board setup. I apologize if these questions are noob but I did not want to mess my board up.

Q1. I was planning on using the Due outputs to control some TB6600 type stepper drives which have an input range from 2-5.5V so I should be able to use this Due without adding any gShield, right?

Q2. For inputs like the microstep pins and the limit switches, am I connecting them to 0v or to 3.3v to activate?

Q3. Pin #8 is labeled gblenab, but I was not able to figure out what that meant. Can someone translate that for me?

Q4. What are the motor voltage reference pins used for?

Thanks a ton. The software looks to be a great solution for my CNC upgrade. Hoping to get it working and back cutting parts!

Cheers!

December 10, 2019 at 2:58 pm #11717

cmcgrath5035
Moderator

Q1 – Yes, the DUE should be able to interface to the 2 – 5v logic directly. Beware that G2Core is Enable active low (a.k.a. enable-bar). Not sure that is directly applicable with TB6600

Q2 – the micostep outputs are binary programming for the the driver device, does the TB6600 support that input?
Limit switch inputs are for a NO or NC switch . You need to provide some lead filtering similar to what is provided on tinyG or Gshield (R-C lpf)

Q3 – That lead is GrblEnable, name of the Gshield pin when Gshield is used on a UNO with Grbl.

Q4 – G2Core provides a o-100% Motor power control, similar to the pot ON tingG. See PL parameter at https://github.com/synthetos/g2/wiki/Configuring-0.99-Motors#summary
TB6600 may not support that

December 11, 2019 at 11:50 am #11721

therobotguyllc
Member

That helped a lot! Thanks.

Although I am still not sure if the switch inputs are looking for a high or a low signal…. By high or low I am referring to the input voltage, not the state of the switches.

I am assuming it’s looking for 3V but I wanted to make sure. I’ve seen a number of arduino setups that have internal pullup resistors on and are looking for the input to be pulled low to activate.
Author

Posts