I've run a few tests playing around with byte count and delays.
The MCU was sending only zeroes.
If byte count is set to 1 and there's no delay almost every byte becomes corrupted.
If byte count is set to 100,and there's no delay, bytes get corrupted at the same locations. I included screenshots of the locations where errors occur.
If byte count is set to 100 and the MCU is transmitting with a 100 ms delay none of the bytes become corrupted.
If byte count is equal to the bytes at port and the MCU is transmitting with a 100 ms delay bytes get corrupted quite often. Increasing the delay decreases the occurance of corrupted bytes.
Similar behavior was observed when I sent data other than zeroes and actual signals.
Byte count set to 100 and delay set 100 ms produced the best results but it's way too slow for me because I'd like to display FFT results in real time.
