I'm using the Geetech Due with RAMPS-FD and current Reptier-Firmware without trouble.
If a filament stepper isn't moving, besides the obvious wiring problems, that can happen if the firmware is configured to not allow moving the filament when the thermistor reads below a certain temp (180 degreesC in my case).
If an X/Y/Z stepper isn't moving, besides the extensive wiring problems one can have (I had them all, it seems to me), you also need to ensure that the pin configuration in the firmware is right for your due board, and also that you either are configured to ignore endstops, or that your endstop direction (low or high) is right and not affected by pullups or pulldowns on the pins.
You may also need to check motor power to make sure the fuse isn't bad and that you get appropriate voltage at the stepper controller board.
Personally, I'd get the arduino toolchain in place to build repetier-firmware, and use that. I was able to make aprinter work, but had inconsistent luck with it.
The stepper controllers are easy to get in backwards or off by a pin or two. The power output pins on the stepper always go to the outside edge of the RAMPS-FD board (I don't know about 1.4).
An alternate route to begin debugging hardware would be to see if you can talk to the firmware at all via repetier host or pronterface, and do some simple things like read a thermistor value or an endstop and make sure you're getting some basic stuff working before trying to get the stepper to work.
Lastly, aprinter worked nicely on my teensy (AVR with USB), and I used that on a breadboard with a stepper controller to learn about setting up my first stepper.
If a filament stepper isn't moving, besides the obvious wiring problems, that can happen if the firmware is configured to not allow moving the filament when the thermistor reads below a certain temp (180 degreesC in my case).
If an X/Y/Z stepper isn't moving, besides the extensive wiring problems one can have (I had them all, it seems to me), you also need to ensure that the pin configuration in the firmware is right for your due board, and also that you either are configured to ignore endstops, or that your endstop direction (low or high) is right and not affected by pullups or pulldowns on the pins.
You may also need to check motor power to make sure the fuse isn't bad and that you get appropriate voltage at the stepper controller board.
Personally, I'd get the arduino toolchain in place to build repetier-firmware, and use that. I was able to make aprinter work, but had inconsistent luck with it.
The stepper controllers are easy to get in backwards or off by a pin or two. The power output pins on the stepper always go to the outside edge of the RAMPS-FD board (I don't know about 1.4).
An alternate route to begin debugging hardware would be to see if you can talk to the firmware at all via repetier host or pronterface, and do some simple things like read a thermistor value or an endstop and make sure you're getting some basic stuff working before trying to get the stepper to work.
Lastly, aprinter worked nicely on my teensy (AVR with USB), and I used that on a breadboard with a stepper controller to learn about setting up my first stepper.