Make sure that the baud rate passed to beginSerial() in your Arduino code matches the baud rate in the serproxy.cfg file. Also be sure that nothing else is trying to use COM10 at the same time as the serproxy.
Does the serial monitor in the Arduino IDE show you
data coming from the board on COM10? (Again, make sure that the baud rate in the "Tools | Serial Monitor Baud Rate" matches the argument to beginSerial().)
Just had this same problem, but had no option to work on COM port less than 10 on Windows.. And it seems that is the problem:
The designers of Microsoft Windows could not conceive of machines with more than 9 serial ports. As a consequence, you cannot use conventional port names beyond COM9:
To deal with this oversight, newer versions of windows require the following notation for port numbers beyond 9:
\.\COM10
\.\COM11
\.\COM12
Was anyone ever able to patch and recompile the code as described in this thread ? I was able to retrieve the source code and make the change but got a bunch of errors upon compilation in Visual C++ 2008.
If anybody could tell me which compiler I should be using to compile this code or any pointers at all that would be great. I am in an environment (college classroom) where I cannot reinstall the Arduino FTDI drivers. Fixing this problem is my only solution right now.
I realize this post started back in 2006 but it is the only information I was able to find regarding this problem. Any help would be greatly appreciated.
There may be another way to solve this problem. FTDI has a procedure to assign virtual COM ports by location id instead of by the device's serial number (which is the default).
Go to you Hardware Manager (Windows Control Panel), and chage the COM10 to anoher below COM10.
I changed my COM11 to COM3 or COM1 and it starts working.