extruder/pin 0 conflict

I'm running the 5D G-Code on my sanguino, and I have a DC powered extruder (the maker bot model), with the reprap host.

The current setup[1] has extruder_0 as a stepper based 'struder, and extruder_1 as a DC. Why is extruder_1 using pin 0 as DirA?? I believe pin0 is used during serial communication, and plugging the DC board into that pin makes the extruder go back and forth as the sanguino gets new instructions.

I've tried changing pin 0 to pin 10 in pins.h but that causes the host to freeze. And the DC board doesn't work when addressed as extruder_1.

What else needs to redefine the pins, or is there some other workaround?

L

[1] [dev.www.reprap.org]
[I do believe the Sanguino and RepRap Host are talking to each other fine -- I'm getting a temperature reading via the thermister and heating via the PWM card.]

The Sanguino hardware page shows pins 8 and 9 as connected to the USB2TTL header, which I assume means these two pins are used for communication to the host.

Pin 0 is connected to the debug LED, but I don't think that would cause much of a problem. You should be able to verify that the dir signal is correct by watching the debug LED.

Also, look at this thread for a bug with the DC extruder on the 5D firmware. [forums.reprap.org]

---

---

Darwin clone, Gen 2 electronics, Arduino Duemilanove w/ AtMega328, 5D Firmware, Pinchwheel extruder
[www.codeerrors.com]

Using pin 0 for direction step makes sense as the boot strap firmware blinks the led when the processor is reset or during power up.

So since the firmware is also not exercising the step line no physical movements take place, essentially a functional no operation.