3 ms·
I think I understand this like I'm five...or there about...let me know if this sounds correct. Let's say the clock ticks at 100 Mhz. So every second, the clock
by deaps 8y ago
I think I understand this like I'm five...or there about...let me know if this sounds correct.
Let's say the clock ticks at 100 Mhz.
So every second, the clock ticks 100,000,000 times.
Let's say the wifi broadcasts at 200 Mhz.
So every 200,000,000 (100,000,000 x 2) clock ticks, it sends something out into the airwaves - regardless of how much time actually passed in those 200,000,000 clock ticks.
Now let's slow the system clock down by half. It's now ticking 50,000,000 times per second - but still, every 200,000,000 ticks, it's going to send that signal out into the air.
Obviously those actual number are grossly misrepresented (because it's not sending something every 200,000,000 clock ticks, it's more likely sending something PER clock tick (or more accurately performing some function per available clock tick and sending it out at some predetermined number of clock ticks) - but this is just for visualization purposes)...and I could be way off - because maybe it's not the actual signal that is being slowed down, but the data inside of that signal - if that were the case, it just wouldn't be 2.4Ghz anymore. Either way, that sounds like a pretty basic why to me - Yes, this is explained below because the system uses two different phase lock loops...so it is not the signal itself, but the data in that signal that is slowed.
- deleted 8y ago[deleted]
- dkersten 8y agoSo, if you visualise a wave, by reducing the frequency, the wave stays the same except it gets stretched. So if you send the same signal each tick but the time between ticks is increased, the signal is stretched. I guess the data signal is stretched and this gets modulated into a 2.4 GHz carrier signal? I don’t know how WiFi works ;)