@PBarrows, no, the Wifi Shield is no longer supported. The larger capacitor was 'thought' to be a temporary workaround for this Cyton-Shield issue. But in fact the root cause is in the variant of the

The emulation you are proposing would be very difficult. As it involves multiple levels of firmware (Cyton PIC32 mainboard and Shield ESP8266) and GUI coordination. The Wifi Shield (hardware, software

The reason these Chinese units do not work, is that they depend upon the "Wifi Shield" board. That board was removed from the Shop pending re-engineering. It never worked reliably with Cyton

Multiple clone board users have reported unsolvable issues with the operation of their boards. There also appear to be more than one manufacturer of the clones. So issues likely differ between manufac

firmware is stressing the Wifi hardware module (ESP8266), and causing the strongly increased current demand. So in other words, it cannot be fixed by 'band-aid' solutions involving extra power supply

That would require complete reorganization of the firmware. It is currently setup to use either the RFduino's (default), or the ESP8266 on the Wifi Shield. Wifi Shield has been deprecated, and is no l

You are going to just have to look over the various examples and tutorials. Surely it is possible for Python to interact with the ESP8266 / NodeMCU. I would start with the link I gave:

https://stackoverflow.com/questions/50728522/how-to-send-data-over-tcp-to-esp8266-with-python

per second throughput) of the Bluetooth or Wifi (ESP8266) channel and constraints. You are limited in the amount of data you can push through the 'pipe', by the speed of the stream through the pipe (

https://openbci.com/forum/index.php?p=/discussion/2507/wifi-connection-with-different-esp8266-resolved

Would the NodeMCU V3 work as a replacement to the Wi-Fi shield(on the Cyton)? Both use the ESP8266 chip, and the NodeMCU can communicate with the PIC32 using SPI as the Wi-Fi shield does, so this seem

Cyton's default sample rate is 250 Hz. This is a limitation imposed by the RFduino Bluetooth radio link. Using a Wifi Shield with Cyton will allow faster rates. But the Shield is currently on hold for

In January last year I did some Arduino ESP8266 development and I remember I had to do something to get the usbserial to work. Do I think I would have removed it completely when I had to get the ESP8

developing my own hardware using esp32 instead of esp8266, I am having issues in sending the EEG signal data to openBCI GUI through wifi. Can anyone please let me know the data format of http response

* Used a FTDI adapter (baud rate: 115,200 b/s) to program the WiFi Shield "BoardWithWifi" firmware onto the ESP8266 with Terminal via esptool.

regulation than with 6V (4 AAs) alone. The ESP8266 makes excessive power demand spikes, that are somehow worse with Cyton than with Ganglion. On the official OpenBCI Wifi Shield board, there are furt

The ESP8266 regulation issue, has to do with peak power demands it creates when doing certain radio transmissions / packet sending. Other thread on the forum has links showing how this impact packet l

The point I am making with the Ganglion, is that Cyton+Shield can probably work just as reliably provided: (1) you have the correct Chinese manufacturer for your ESP8266 or adapt another ESP model. (2

So far, WiFi Shield works but it is quite erratic. The hardware involved, ESP8266 is sensible to its manufacturing origin. Some of them works better, some of them are horrible. In summary: not reliabl

Curious, how is this related to your other thread posts regarding DIY Cyton's using ESP8266 chips? Do you have RFduino based Cytons?