USB Connection: Error Device Not Responding about mw-wingui

[GoogleCodeExporter]

After power up the first connect will reset the board. If your board does not 
complete the reset within 2 second (it depends on your config) then you got 
this error. Did you tried connect again after this error ?

Original comment by [email protected] on 12 Apr 2013 at 9:49

[GoogleCodeExporter]

Yes a few times and left it connected for a while. Since posting a minute ago, 
I've noticed that if I open hyperterminal and connect to the board and close 
it. The GUI will then connect fine. If it helps the red light on the FTDI stays 
on solid when the error occurs and initially the blue led on the board flashes.

Original comment by [email protected] on 12 Apr 2013 at 9:55

[GoogleCodeExporter]

I can confirm this behavior on a Crius AIOP V2. The red light(A) stays on solid 
as well and the GUI does not connect. However, when I try to connect with the 
MultiWiiConf that comes with MultiWii 2.2 it works fine and thereafter the 
WinGUI works fine as well. It indeed looks like something needs to initialize 
the COM port first before WinGUI is able to connect.

Original comment by [email protected] on 26 Apr 2013 at 3:48

[GoogleCodeExporter]

Hi it looks like issue 29 is the same as the one i raised here except using 
bluetooth rather the a lead  i get the same issue over bluetooth and its 
because of com port initilisation.

Original comment by [email protected] on 4 May 2013 at 5:48

[GoogleCodeExporter]

Original comment by [email protected] on 8 Dec 2013 at 8:00

• Changed state: Fixed