im trying to connect my gaups board to my arduino due with tinyg2 firmware from edge-feature-076 branch, i have dual y with each one separate drivers, my second Y (4th motor) is not workink so a compare the pinout from Gaups board and TinyG2 firmware and i have every thing ok for x (1),y (2) and z(3) but not for my motor (4) my second y.
I check the pinout of tinyg2 and pinout of gaups, x,y,z are the same,for second y it´s different, in tinyg 2 i have:
In Gaups, im using dual y each one with a separate driver, so its connected to PIN D13 and D12, i can change the pinout in the gShield-pinout.h and compile, i know for kSocket4_DirPinNumber will be 13 and kSocket4_StepPinNumber will be 12, i also know for kSocket4_InterruptPinNumber, kSocket4_Microstep_2PinNumber and kSocket4_VrefPinNumber because it´s the same from the others motors but i don´t know if i have to change kSocket4_SPISlaveSelectPinNumber, kSocket4_EnablePinNumber, kSocket4_Microstep_0PinNumber and kSocket4_Microstep_1PinNumber because it´s diff between all motors. I think i only have to change dir and step because the other pins are unused by gaups because they are at the top of the board.
Just some comments and questions, this will likely need to be looked at by the developers. A quick look on my part.
1. Rather than posting items like the schematic , I would suggest you post a link to a copy in a Dropbox or similar account. The Schematic is somewhat difficult to read within this forum tool. See
4. Are you sure the specified drivers are compatible with 3.3v input?
5. It would appear that in the upper right of your schematic, there is a way to derive the Amotor step and dir from the Y leads, making Gaups pin compatible with Gshield. Is there a reason why you don't want to use that feature? Just curious.
6. I would carefully review the pullup to +5 (I think) on Gaups pin D8. That might kill your DUE (3.3v logic)
7. Perhaps post (a link) your proposed modifications to gShield-pinout.h, as a commented copy from git-hub, as that will be speaking the developers language most clearly. Make your proposed modifications clear and search-able, something like //Gaups_mod ........
8. For safety sake, include info on the OS you are using for G2 builds. There are some issues at the moment with the Linux cross compiler that is pulled in by the Makefile.
one issue resolved, i have an unscrew in the pulley of my motor 4 (second Y) so all my motors lock, now i understand what do you tell me in point 6, i will change that to ioref, thanks to the maker of Gaups shield:).
im compiling with the new pinout, i change also the spindle enable because he have the same pin number 12
Frankly, G2 has many new details, so we are trying to figure out what to ask for.
Item 6 is a 10K pull up to VDD on the GAUPS, feeding both the 8825 drivers and DUE port D8. Vdd=5v, correct? I am not sure DUE port D8 will like that. A pullup to 3.3V would be safer.
Item 8 you answer is unclear, have you loaded your binary to the DUE yet? What does it reports as $fb (firmware build)? I was just on another forum where the member reported building 75.02 less than 12hours ago. But yes, this is a fast moving world.
Pololu DRV8825 should be great - I have been looking at them as well. The GAUPS reference had a pointer to older drivers which were not familiar.
I'll reinforce my Item 6 concern - Gaups uses Vdd=+5V to power all 4 drivers. I am probably being a bit paranoid, but if +5v should get back to the Due from any leads on the 8825 that might have an active or passive pullup, it could degrade or kill your DUE. I have been slowly thinking thru a custom shield similar to what you are doing and how to power these functions is still on my to-do list.
im sorry for lack of information, im using now the edge branch, i made a git clone to edge branch and compiled with new pinout, i change also the spindle pin because is the same of motor 4. its version 75.02. everything is working great, i was able to move each y motor at a time to test it and its working!
you are right for vdd=5v, im talking with the maker of gaups to fix that, maybe asking him if i can cut the pin connected in pin 5v and make a connection with a wire to ioref in arduino due.
By the way, look up at my item 5 again
It may be moot now that you have figured out all the re-compiles.
That block on the schematic would allow you to drive two 8825 drivers from the same logic thread called motor"y". Each motor would have it's own driver. You would reverse the direction on one motor by wiring it 'reversed'.
You gain nothing, in reality, by maintaing four motor calculations doing only 3 functions, X,Y and Z.
Unless Gaups becomes uber popular, I would doubt Synthetos will add a Platform=Gaups build option, so you will always be recompiling standard builds wilth unique .h files.
The good news is, you have the flexibility, the bad news is, you have to remember to do it and do it. All builds will be named the same (e.g. 75.02)
I will check that tomorrow, i don´t understand that when i configure the gaups board for the first time, thanks to open my mind for this option:)the first time i configure that i was thinking in this jumper like y with one stepper or y with two stepper like i have, i have to check again the gaups wiki.
There is never a 'clean' answer to this question.
In tinyG space, lets call it G1, 'Master' has become very out of date and I would recommend 'Edge'. Having said that, I do know that a new 'Master' will be posted soon after some cleanups to the current 'Edge'.
In G2 space, the current Master is a relatively new build, 72.01 I believe. Currently Edge is building 75.02.
G2 is still under heavy development. Master and Edge are changing more frequently. Master will always be a bit more mature than Edge.
All that said, as best I can see more folks are using the Edge of the day, perhaps because they are in experimental mode as well designing new machines around the capabilities of the DUE and full 6 axis control.
I guess the good news is that the BOSSA loader works well, so switching is not a huge hassle once you have your build (compile) environment tweaked for your system.
Do be aware that custom settings files may not port directly to new builds, Edge added some additional parameters recently that affected my builds.
Best solution: Unless you want the most stable environment, I would build a Master that you test and verify it works, then put it in a safe place should you need it. Then build an Edge, if it seems to work for you stick with it, you can ride the crest of the wave.
Also, monitor the chatter here:
it´s look like your are right again about the point 5:) i don´t need to change the pins, i think it´s the problem with my pulley that induce me in error.
I have already change my Gaups board Pin Vdd to IOREF in Due instead of 5V.
im still testing tinyg2, i have both version compiled running in chilipeppr/tinyg but i have some problems with edge branch:
In Edge branch i cannot run helloWorld in chilipeppr but i can Jog and put some gcode manually but with master branch i can do the helloworld...i have to run more test to find the problem, i use always the same setting file.
I'll hazard a guess that the Gaups folks will realize quickly that they are uniquely positioned to serve the 4 motor DUE users and make the 5V to 3.3V transition easier in the near future.
Enjoy your machine and please feedback bugs and issues.
Nothing improves a product faster than good user experience.
This topic is from the original forum (February 2015). Your reply starts a new discussion linked to it.
