Solved Robo beta doesnot connect

It is a new COM port now that you have replaced the electronics. Windows auto-assigns COM ports to devices to avoid conflicts.
You need to figure out (Device Manager will show you) which is the new COM port

 

Easy way to get to Command prompt in Windows 10 is to right-click on the start button, this will bring up a menu which includes "Command Prompt (Admin)" among other useful items. Click on that and you command window will appear and you will have run CMD in Administrator mode. Faster than typing cmd.exe and then right-clicking to select Run as Administrator.

 

You do have only one thing connected right?
You can't have (for example) the Arrduino compiler and MatterControl connected to the printer at the same time.

Reboot and try to connect only one thing (like MatterControl).

Completely power-down the printer as well (turn off the switch AND unplug the USB cable). Then power it back up.

 

Well, it is showing a RAMPS for COM 3 which, while odd, at least confirms that is where it is,
(It is Odd because normally it will show a type of Arduino since that is what the computer is connecting to)

 

It is possible that you have bad Arduino board.
They are cheap, but I would try to rule out everything else first.

If you do have a spare just swap it in a load the firmware.

 

That looks better. That is what I usually get for mine.
Can you get to the COM port?

 

Ah, the problem is that you are using the current version of the Arduino compiler with an old version of Marlin,
Things have changed and there are going to be minor code fixes that need to be made for the old code to compile.

Which version of the Arduino compiler are you using?


Welcome to the world of embedded programming... and Marlin doesn't make it easy

 

OK, I just downloaded and compiled Marlin_6_10 with the Arduino compiler 1.6.9
It compiled fine when targeted to an Arduino Mega 2560

You must have changed something in CONFIGURATION.H that it is unhappy with.

 

Actually reading it further... most of these can be ignored they are warnings:
warning: "X_MAX_PIN" redefined

 

The problem is that the COM port is generating an error talking to the Arduino.
This is why you are getting the "The handle is invalid" errors when using the COM port.
This is the actual problem.

Looking at the arduino forums I see this:

https://forum.arduino.cc/index.php?topic=358363.0

which leads to this:

http://forum.arduino.cc/index.php?topic=144470.0

and all of this points to an error with the driver on 64-bit Windows, There are some alternative drivers uploaded into that second thread. Try those and see if you can get it working.

(this thread already gets the nomination for most technically involved of 2016)

You should have already tried a different USB cable was well although a poor quality cable usually generates different errors I would still suggest you try another.