Good day,
I use my platform with arduino due ..
pins assignment is different
Driver Allegro A3977:
Pin 13 Sleep Stepper X and Y
Pin 12 Reset Stepper X and Y
Pin 11 Stepper Y Low Current
Pin 10 Stepper Y Step
Pin 9 Stepper Y you
Pin 8 Stepper Y Enable
Pin 7 Stepper X Low Current
Pin 6 Stepper X Step
Pin 5 Stepper X you
Pin 4 Stepper X Enable
What can I change to TinyG2
I ask for help
Thank you
the 3 allegro Drivers are already installed in my developed board.
the A3977 interface with 3.3V logic.
pins are connected so physically:
Pin 13 Sleep Stepper X and Y
Pin 12 Reset Stepper X and Y
Pin 11 Stepper Y Low Current
Pin 10 Stepper Y Step
Pin 9 Stepper Y Dir
Pin 8 Stepper Y Enable
Pin 7 Stepper X Low Current
Pin 6 Stepper X Step
Pin 5 Stepper X Dir
Pin 4 Stepper X Enable
I can move the motors with arduino code.
to wake the driver, i must set the Two Pins (Sleep and Reset) High.
The Problem:
I would like to work with TinyG2 Version 0.98.
under the folder: TinyG2\platform\atmel_sam\board\due are the 3 files:
where you will get a general idea of how the Motate layer works.
Then compare your develope pinouts to Gshield, and hack away at a My_development_board.h following the example you see.
then recompile.
Or, perhaps better yet, remap the pin assignments on your developer board to match Gshield.
FYI, I don't know what your development board looks like, but my initial suspicion would be limited thermal conductivity. Your drivers, like the TI drivers used on Gshield, are in special heat slug packages.
Don't drive the proto very hard, and don't expect to do much real 'work' without a good thermal solution.
Is there a particular reason you are using these drivers?
I just needed more power and Flexibility.
The pins of arduino due are physically lashed to the Pins Of Driver.
I can not change anything.
I can not remap the pin assignments on my developer board to match Gshield.
for example:
Step/dir Pins X-Motor on Gshield are (2 / 5) On my Board are (6 / 5)
Step/dir Pins Y-Motor on Gshield are (3 / 6) On my Board are (10 / 9)
I am frankly not sure in what Pin numbering space your developed board is described. I am assuming it is physically compatible/mates directly to the DUE?
I have the software adapted to my Shield.
if my Shield energized, the motors are enabled.
but if I give a command for example: G0 X10 Y10 then the two motors will be disable.
Have you perhaps a idea? why the motors do not move.
I might guess you have the enable lead inverted - tinyG2 Enable(inverted) [enable bar] - a zerologic state when enable is on.
What are your drivers looking for?
My suggestion would be to make the logic inversion with a logic gate or just a small fet and appropriate pullup.
It might be possible to to invert the I/O logic in the firmware, but not necessarily simple.
I can only guess a bit at what you call 'motor tremble' - is it a buzz but no movement?
That could just be the energized motor holding current position.
Have you compared all specs for your drivers to comparable TI specs, for example step pulse width?
Hallo..
Thank you cmcgrath5035 it work now thank you...
now i need your Help for Homing and switch.
i have 2 sensors and i wanted to use it as a switches.
-- Sensor X for minX
-- Sensor Y for minY
i don't need MaxX/MaxY