'?' to Cyton COM port gets: "'Failure: Communications timeout - Device failed to poll host"
I plugged in the USB-dongle. Sending a question-mark (or any other
string) to the COM port of the dongle results in 'Failure:
Communications timeout - Device failed to poll host$$$' and depending on
the exact USB port either the LED D5 or both the LED D4 and D5 are
flashing.
I didn't verify my VPC-driver installation. I didn't get
an error during the installation, but I don't know how to verify that
they are working properly.
Thank you in advance for suggestions!
Comments
http://openbci.com/community/openbci-radio-configuration-utility/
If it's still worth to try out that util tool, can you recommend me a simple, lightweight program to launch it? I only worked with c-like files for arduino projects in the past (and even that were more proof of concept like projects), while this looks like a java-like file.
https://github.com/OpenBCI/OpenBCI_Processing
Mentioning Colin @cfausn who is the author of the config tool.
I'm suggesting running the radio config tool, because it sounds like your dongle and mainboard may be on different channels. Not sure why your channel keeps changing.
Colin have you seen that dongle channel randomization behavior yourself?
I ran some tests to clarify my statement from before: The dongle doesn't appear to change the channel while plugged in. If I just request to get the channel, unplug and replug the channel appears to be stable. If I sent signals (directly to the port (for instance the '?' I mentioned earlier) or via set channel in the GUI) the channel first appears to stay at the same channel, but may switch around after replugging. The destination seems uncorrelated to the actual channel I've selected in the GUI. The channels I've seen so far are 1, 2, 5 and 25 (is there anything special about any of these except being the last and the first one?).
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 '?' supposed to return relevant firmware information instead of 'Failure: Communications timeout - Device failed to poll host$$$'? What is even regarded as "host" in that manner?
Thank you for the clarification.
I'll post later (tomorrow?) how it went with the radio-util.
I know the following is a completely different kind of error - feel free to direct me to open a new discussion if that's more appropriate for the forums structure.
When I try to stream data over my connection I receive instead of actual data the error:
"OpenBCI_ADS1299: interpretBinaryStream: expecteding end-of-packet byte is missing. Discarding packet. (___)
OpenBCI_ADS1299: interpretBinaryStream: Actbyte = -63"
while the brackets (___) contain the corresponding package count. I have no idea where to start.
Edit: I forgot to mention that the led D4 starts to burn permanently when I try to get a stream.
Thank you very much for your guidance and help!
complete newb to all of this), but I seem to be stuck on the same issue
as the OP. I tried installing the Radio Config utility, but it gives me
the same error: "Communications timeout -- Device failed to poll
Host$$$" and then adds "Could not connect, is your board powered on?" As
far as I can tell the leds are on on both the board and my USB dongle (the latter is, in fact, blinking quite furiously. If it is relevant, the Gpio2 is on, blue, the other two leds blink continuously -- the TXD red and the RXD green).
Oddly, when I press "Autoscan" on the RCU it cycles through "Success:
System is Up$$$/Failure: System is Down$$$" and the communication error
above.
Not sure what to do -- any input (beyond, as I said, trying the RCU)?
Also,
I should say, I didn't know of the existence of Processing before this,
so please speak slowly and do not assume ANYTHING on my part in terms
of background knowledge!!!
thank you for any help
openBCI: openNewLogFile: opened ODF output file: SavedData\OpenBCI-RAW-2017-05-25_17-13-29.txt
WOOHOO!!!
OpenBCI_GUI: initSystem: -- Init 4 -- 158483
OpenBCI_ADS1299: systemUpdate: [0] Sending 'v' to OpenBCI to reset hardware in case of 32bit board...
Failure: Communications timeout - Device failed to poll Host$$$openBCI_GUI: haltSystem: Halting system for reconfiguration of settings...
OpenBCI_GUI: stopRunning: stop running...
OpenBCI_ADS1299: startDataTransfer(): writing 's' to the serial port...
Closing any open SD file. Writing 'j' to OpenBCI.
OpenBCI_ADS1299: closeSerialPort: closed
The GUI suggests powering down/up USB dongle and OBCI, but it doesn't seem to help.
I've also tried the openVibe, but essentially same thing, the dongle and board just don't seem able to talk. Help!
I've tried it on both a desktop (Dell XPS Win 10) and a laptop (ASUS Win 10). It is a brand new OBCI system, so I have just downloaded the FTDI drivers on both computers following the tutorial. And yes, I have followed the tutorial step by step -- in fact, that might be what broke it: when I first clicked "status" (as per the tutorial) it said the system was up, then I followed the tutorial through the 'change channel' example, and after that it never came back. Perhaps unsurprisingly, when I launch the GUI from Processing, as it opens it gives me the following error: OpenBCI_GUI.pde: could not open /dev/tty.usbmodem1411
On both computers it shows up as a COM (COM3 in one and COM4 on the other). I've tried to look if there is any problem detecting the ports, but I can see them from both the device manager as well as get it listed through the shell (the windows powershell).
One small advance, I could type 'v' and get the data visualization part of the GUI to show, but of course no data streaming.
I've tried to connect to the COM port using putty as you suggested, but it gives me the exact same error "Communications timeout - Device failed to poll Host$$$"
More suggestions?
I've made a post as you suggested: https://github.com/OpenBCI/OpenBCI_GUI/issues/155
I tried to include all that I could recall, feel free to ping me if I omitted anything that can be of help!
thank you
martin