On the first glace _ I didn't analyze this in detail yet - it did look to me like a GL timeout thing. Since the initial GUI initialization is pretty slow on pretty much every machine I've tried so far

I neither not convinced that it is a channel issue nor that it is even a failure in the dongle itself. I still can imagine that the problem comes from the communication over the port. Isn't '?' suppos

Communications timeout - Device failed to poll host$$$' and depending on

               scaled_output=True, daisy=False, log=True, timeout=None):

connect to the Ganglion but then throws an init timeout error.'

anymore, i.e. we always got the error 'init timeout' in the GUI. Because it could connect before the firmware update, we tried to downgrade to firmware v1, which did not work. Now we wanted to redo t

Your problem sounds like a radio channel number mismatch is the print out from the HOST "Failure: Communications timeout - Device failed to poll Host $$$" when there is no polling DEVICE. 

I checked the com port on cmd using command netstat -a -n. It showed that the port was active.But when I used hyperterminal to check, it stated "Failure: Communications timeout - Device failed t

         Timeout                       : 200

Hi again, and thanks for the answer William. We have not tried the new GUI, but we think that the problem lies with the RFduino flashing, since we don't get any communication between device and host.

It seems okay to open openBCI GUI. I am sure there is no problem with connection dongle and openBCI ( No error message about COM or timeout)

with serial.Serial('COM4', 115200, timeout = 1,parity=serial.PARITY_NONE, stopbits=serial.STOPBITS_ONE) as ser:

On my 32bit v3, I often get the init timeout error when selecting the "write to sd" option.  I have to repeat the initialization several times to get it to work.  This never happens when I a

http://openbci.com/forum/index.php?p=/discussion/350/init-timeout-retry-initialization-reload-firmware

have it installed and been testing but constant timeout it just becomes unresponsive and I stop it and reconnect but need to then powerdown, unplug and replug the dongle then power up again, 10 or 15

http://openbci.com/forum/index.php?p=/search&Search=timeout

"Init timeout Verify your Serial/COM Port Power DOWN/UP your OpenBCI & USB Dongle Then retry Initialization"

Some other related threads about the timeout message here,

'Init Timeout Verify your Serial/COM Port Power UP/DOWN your OpenBCI & USB Dongle Then retry initialization'

The thread link above for reloading the firmware further links to an 8-bit firmware, but since you have the 32 bit board, use the instructions here for reflashing,