'Also, since your ♜ is probably not having one of any considerable size, except maybe a few Bytes in UART. I was desparate and grabbed the only time delay I could think of. I'm aware of sleep, but at 70 years old, I have trouble keeping all this at the top of my mind. MrSwiss ' This is the WORST method ever (to implement a delay), simply forget it!' I can set in device manager to 300, 4 bits/word and pc still receives data sent at 9600, 8bits/word. 'Do you set the right params in the device manager also?'ĭoesn't seem to matter. The pc reads data that the 8051 never sent, and returns zeros. But when I install the Win 10 hdd into my laptop, using all the same programs and hardware, it doesn't work.

If the pc asked for more data than what the 8051 sent, the pc hangs, as I expected, I assume waiting for the next start bit, and none comes. I did write a bit-banging 8051 program to create 9600 baud, and it simulated ok, ie, 104 microseonds per bit. When I go back to the Win 7 machine and send only 5 bytes, the pc stops after receiving the five bytes and then patiently waits for the next byte, just as I expected.ĭ.J.Peters 'Do you measure the 2400 baud rate from your MC with an oscilloscope?' If the 8051 is sending as fast as it can and if the pc is hobbled by that time delay, how does it still work? I want to try a faster BAUD but don't have a proper crystal (without manual bit banging). Both sender and receiver are set to 2400, 8 data bits, no parity, 2 stop bits.

I set the transmit and receive buffers to 1 in device manager. The 8051 asks the pc 'are you ready?' over and over and when the pc finally responds 'yes', the 8051 sends data as fast as it can with no sense (that I'm aware of) that the pc is successfully receiving the data. If I make the delay two orders of magnitude shorter then the problem persists, all of which only adds to my confusion. Inside the FB loop that receives the data I placed a time delay I did come up with a not so pretty solution.

Windows 10 serial console