Arduino IO Expansion

Fuck there goes my new year's resolution, getting caught up in stuff like this.

Cant do this anymore bye all wrote:

When setting the baud rate (divisor) on a 8250 or the later variants it will always be tied directly to the time allowed for each bit.
 

Lol yeah, that's how all asyncronous serial works. What do you think you are setting when you set "115200" on a COM port? Divide that baud rate into 1 and get the "time allowed for each bit". It's just easier to ask people to set the baud rate on the COM port than it is to say "gimme the period of time in us/ms". Anything that happens a specific number of times within a second is a period, you just forgot to do the division.

Yeah sure there are serial protocols the will define a zero has being so many us and one has being another value, which no one has yet to mention, but each period for either 1 or 0 will be an absolute value. 

Like what? What protocol is that? That would literally be something that has no predefined data rate because the rate you can transfer data specifically relies on the difference between how many 1s are in that package vs how many 0s are in that package.

Morse code is not a serial protocol, it's a method of spelling the alphabet by using human understandable events, like flashes of light or sound. There is no precise timing involved, just perception. You can't perceive the difference between 1us and 1ms and a machine would have a hard time trying to figure out what the hell some outrageously long and inconsistent "dot" is.
 

This one is close to 30 years old, I wrote a win95 device driver in assembly many many moons ago, ones & zeros of different length. I also manged to squueze a basic master station into a 16f84 all done in assembly.
www.nmra.org/sites/default/files/standar...C/S/s-92-2004-07.pdf


www.testandmeasurementtips.com/morse-cod...munication-protocol/

Then there's "Manchester encoding" used by ethernet.

We can also encode 1 & 0 as a certain frequency or shifting the phase.

The PCIe bus transfers data serially, at far greater rates than the parallel ISA & PCI buses could.

PS/2 is another way of sending data serially.

SPI is somewhat different in that the transfer of data is controlled by a clock are controlled by a clock. Bits can be shifted in & out depending on the clock polarity, of course you wanna define this beforehand.

Human generated speech is serial in nature, supposedly Tibetan throat singers can generate more than one sound at a time. Then again sound is serial in nature, as is light.

Even the written word is serial in nature, unless of course you are some rare type that can ingest a whole page of words at once. I don't know if this is even possible.

Even the parallel port could be considered serial in nature, talking to printer requires sending the data at one byte at a time, even 32 bit transfers end up being broken into 8 bit chunks.

PAL, SECAM and NTSC sent data in a serial fashion.

This is kind of going off the rails now. I quite happy to not totally agree with you but also not think you are a fascist.

Wow, off the rails is definately where that went.....fascist? Where on earth did that come from? We're talking about serial protocols....I don't think I tried to suppress your freedom from my keyboard.

Point was you theres some kind of misunderstanding about how asyncronous serial works, even though that post was edited out of existance now. I have no idea what this last post has to do with anything. All I said was in service to Baudrate != Bitrate. Though it's generally OK to colloquially just say it like it does.

Thank you for confirming that as soon as you say you will not think someone of being something they deny it.

I think maybe you need to take some time off and work some things out. That's beyond bizarre.