I have a small shapeoko2 machine and I have recently upgraded to a gshield with a due clone running tinyg2 after running with GRBL uno for a couple years.
My primary problem is that my Z axis does not respond. The X and Y move appropriately, but the Z stepper powers up and does not step in either direction. I used chillipeppr to flash the latest version of tinyg2 onto my device, and can jog in X-Y, but when I jog Z, the Z led briefly blinks and shuts off and no motion occurs, yet tinyg reports to chillipeppr that the motion was successful.
I have confirmed it is not an issue with the gshield by reconnecting the uno, and it functions as expected in all 3 axes.
Is my problem likely the due clone or the version of chillipeppr I flashed? I have 2 dues and tried both, but the problem persists across controllers.
My minor issue is that I have a difficult time connecting to tinyg in windows7, often requiring manual resets of the controller to move from ‘Bossa Programming port’ to ‘tinyG v2 data and control’. Once connected in chillipeppr, I will often have to cycle ‘feedhold’ for tinyg to respond.
Continuing previous comment:
The parameter is $1ma ($2ma for 2nd stepper motor, $3ma for 3rd and so on). I have 3 stepper motors, one per axis instralled in my machine, so my setup is:
$1ma = 0 -> X axis
$2ma = 1 -> Y axis
$3ma = 2 -> Z axis
If you have 2 motors installed on the same axis (which I guess is Shapeoko case for Y axis) then you need to assign appropriate motors to this axis ($2ma = 1 and $3ma = 1), and use $4ma = 2 for Z axis. Make sure you check motors polarity ($2po and $3po for motors 2 and 3 in this example, so they run the same linear direction). If you other motors moving wrong direction e.g. Z moving up for negative values, reverse polarity, as well.
There were some problems reported while using autolevel, be careful with that and do not break too many bits. If you wish to use NC limit switches configuration, you will need to adapt settings.h and re-complie firmware.