Geeetech

I just got Geetech aluminum Prusa I3 printer and while assembling ran into few problems. One of those problems is I'm failing to connect End stops to the control board. My first idea was to connect "C" and "NC" on end stop to "Sig" and "Gnd" on the board. That does nothing. What am I doing wrong? Also I'd like to know how can I tell if end stops work? Thus far I have been using "auto home" and clicking the end stop.

Connect the endstop to the sig and GND , and the wirings to the NC and C . Did you get the building instructions of this printer? It includes all the wirings you want. you can download it here:
http://www.geeetech.com/geeetech-alumin ... p-944.html
And the endstops, you can check the endstop status with the M119 command.When the endstop is released, send command M119 from the repetier host it will report "open", and when it is pressed it will report "triggered".

Okay. I actually used videos to learn how to assemble it. The wiring part was missing. I have one more question - why do motors drive in wrong direction and how do I fix it.

check out this link:
http://www.geeetech.com/forum/viewtopic ... 17&t=17037

I have a major problem here.
I downloaded Arduino 1.0.1 and also "Plusa I3 A sanguinololu" firmware as well as aditional boards for Arduino (Sanguino does not come with stock version of Arduino 1.0.1) and was about to upload firmware to the printer but then this happen: Arduino does not see COM of the printer. I tried to test Arduino UNO board to make sure FTDI trivers work properly. It sees UNO but not the printer. What does that mean?
One more question - does your company sell parts for your products?

An update: I have removed FTDI drivers I had and instead installed drivers from this page: http://www.geeetech.com/wiki/index.php/ ... he_drivers

In both cases, with old drivers and with the new ones, I have the same problem - device manager shows printer under COM5 but has a exclamation mark next to it and if I look up under Device status it says there the following:
"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"

how about check out this link here to update the driver:
http://www.geeetech.com/forum/viewtopic ... 18&t=17041

Updating USB driver helped.
Just as a precaution I have deleted files associated with FTDI drivers I already had on my system. I was able to compile and upload a sketch with following set up:
#define INVERT_X_DIR true
#define INVERT_Y_DIR true
#define INVERT_Z_DIR false
And motors finally moved in the right direction.