search

Foamflyinfool / mw-wingui

MULTIWII GUI CODE
3 stars 0 forks source link

USB Connection: Error Device Not Responding #28

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Flash the multiwii board (MultiWii SE 2.0 Board)
2. Fly the copter
3. Leave overnight
4. Connect FTDI and USB and GUI won't communicate, BUT the arduino IDE can 
connect and upload fine and you can fly the copter as normal.

When you try to connect you get the error in the image. When you open arduino 
IDE and re-flash it then works fine again. Tried different FTDI and leads etc, 
but like I said any other serial comm program can communicate with board.

What version of the product are you using? On what operating system?
Version 2.1 and 2.2 both same on Win XP Pro

Please provide any additional information below.

Original issue reported on code.google.com by jblackm...@bournes.biz on 12 Apr 2013 at 9:22

Attachments:

GoogleCodeExporter commented 9 years ago 
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 eosba...@gmail.com on 12 Apr 2013 at 9:49

GoogleCodeExporter commented 9 years ago 
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 jblackm...@bournes.biz on 12 Apr 2013 at 9:55

GoogleCodeExporter commented 9 years ago 
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 kevin.ho...@gmail.com on 26 Apr 2013 at 3:48

GoogleCodeExporter commented 9 years ago 
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 julianBl...@gmail.com on 4 May 2013 at 5:48

GoogleCodeExporter commented 9 years ago

Original comment by eosba...@gmail.com on 8 Dec 2013 at 8:00