There are two UART serial ports on the PIC, Serial0 and Serial1. 0 is used for the link between the PIC and onboard RFduino (called the 'device', dongle RFduino is 'host). 1 is free for other uses. Yo

OK, here is the thread mentioning the V3 mods to allow data stream output to serial1 port. serial0 is the port used to talk with the RFduino. This mod is not in V2, only V3 and above.

***************Can the GUI be used to change the rate at which the Ganglion's A/D delivers data on its SPI channel? ("Serial1"?)

Snoop on the "Serial1" SPI lines (SCK, MOSI, MISO, maybe more), which I'll optically couple to ensure proper patient isolation.  Upon reset/powerup, a PC could, thru bluetooth, configure Gan

Another idea that I had was to use an HC05 module with the serial1 port: do you think that that would be a better approach?

Next concept: using Serial1 with an optoisolator hardwired tp your laptop will support a higher sample rate. This can lead to shock if you hooked up wires incorrectly so no one recommends this. Thats

docs. I spent some time looking at using the Serial1 for the Wifi shield but unfortunately, it was ultimately too slow because it could never break 480200 baud which as you can do the math is only 50

The external D1 LED will NOT work once the pins are remapped and you activate Serial1 because Serial1 then uses the same digital I/O as the LED. So you are farther away from bricked and closer to what

activate Serial0 for data to be streamed through Serial1 is also a bit strange.

Hmm, interesting. I guess I was mistaken about the defs file being fixed in V2. I still don't understand why using Serial1 requires extra work. Seems like it should be enabled by default so any OpenBC

With the wired usb mods for V1, the PIC sends the EEG data stream on Serial1, which has RX TX wired over to the FTDI breakout board. Serial0 is reserved for the link between the PIC and the RFduino. W

I tried swapping out references to Serial0 and Serial1 in the code, while setting _SER1_TX_PIN and _SER1_RX_PIN to Pins 11/12 (similar approach that Winslow takes). However, it appears that so far al

For example to send out the serial data on Serial1 vs. Serial0. You'll have to check the v2 documentation.

Sounds like Winslow_Strong @Winslow_Strong was not able to get output from the serial1 port above 460800 baud? As I read his repo and such. 

The blue is from data streaming over wifi. I have the Serial1 baud at 230400 feeding to a ESP8266 running a UDP server and the blue are seeing is a Node.js program running on my computer. Gonna see if

Hey has anyone been able to activate the Serial1 after it was mapped at output after startup? Like activate the serial port on the fly?

Another curiousity is that changing the baud rate within the COM settings of Windows Device manager seems to have no effect whatsoever.  All that matters is the baud as set in putty and in Serial1.beg

I've been careful to match the port baud rates in Windows Device Manager, the Serial1.begin(baud) initializations, and the terminal connection (putty in my case).  So all 3 of those were changed to ma

I mentioned a couple posts back. Find all the Serial1() output calls and instead call your own Serial1buffered() routine. This checks the status of the RTS pin. If the 1K ring buffer is full (RTS==1)

The OBCI board writes data to Serial1 in a stream.  I.e. there’s no buffering/packeting going on, but every 1s / sampleRate, the current channel data is written to Serial1.  This passes over the jumpe