Hi Donald, I don't want it to seem like I'm saying RTFM, but if you are using a kritzler circuit, but the kritzler software is not working with it - it makes me think the circuit is not correct - or it is not what you think it is. The solution is, as I've covered in your other thread (http://www.polargraph.co.uk/forum/polargraphs-group2/code-software-forum2/der-kritzler-using-polargraph-software-thread291) to get der kritzler working, THEN at least you know it works.

I'll repeat it here though - the kritzler software is set up to use the kritzlershield, which has the motor driver control pins on 6, 7, 8 and 9. In the photograph of the circuit, it looks like the driver control pins are actually physically connected on pins 9, 10, 11 & 12. I think this is the early version of the circuit that Alex used, before he made the shield.

Now, I just noticed that the photograph is actually of Alex (tinkerlog)'s own circuit from his site - I had previously assumed it was a photo of your circuit (why didn't I spot the wrong kind of arduino! duh!). So it is possible that there are other physical differences in your circuit that are not present in his. How can I possibly troubleshoot something without knowing anything about it?

Lanthan's pioneering polargraph code is discussed here (http://www.polargraph.co.uk/forum/polargraphs-group2/code-software-forum2/new-build-and-attempted-firmware-for-stepdir-drivers-thread21/). The Polarshield was a formalisation of this method of control, and polargraph_server_polarshield supports it. Just change the pin assignments (covered in http://www.polargraph.co.uk/forum/polargraphs-group2/building-hardware-forum3/arduino-mega-2560r3-with-ramps-1-4-thread286.0/) to match your physical circuit.

good luck
sn