2560x1440@60Hz has a pixel clock of 241.5 MHz, TMDS clock of 2.415 GHz, and suddenly your Raspberry Pi 4 can't use 2.4GHz WiFi and 1440p at the same time, because EMI is hard. I guess the RPi foundation *still* can't design hardware. https://www.enricozini.org/blog/2019/himblick/raspberry-pi-4-loses-wifi-at-2560x1440-screen-resolution/ …
-
I'm not entirely sure but I don't think you can equate the average power drawn on the supply to the RMS pulse power of an non CW RF emitter As an optical alegory I have driven a 1W LED to full brightness with a 110mW supply by using a 1:9 mark-space ratio of pulses
Full throttle WiFi (e.g. local file transfer) is basically CW. You can expect ~50% duty cycles, due to various inefficiencies, but then again the transmitter also isn't 100% efficient. Not sure what you mean with the LED. You can't drive a 1W LED to full brightness with <1W.
-
-
I *think* what you meant is that you can drive 1W of power into an LED with a 10W supply at 10% duty cycle (this is e.g. common in IR LEDs which are separately specced for pulse and average power since they are always modulated).
-
At least that Twitter feud give me a lot to rtfm and learn thank both of you :P
End of conversation
New conversation -
-
-
Not near my reference stuff so cannot comment on wifi, but as for LEDs, oh yes you can because the human eye sees the peak brightness & POV handles the gaps so can totally make an LED appear as bright as it would be using 1W on DC while only dissipating a 10th of that.
-
OK, I believe the issue is that you are talking RMS average consumption but the ism spec is for peak power
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.