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/ …
-
Sorry, licensed bands come with their own restrictions but mostly not the hard EI tolerance/emission ones that restrict WiFi to an EIRP of +35dbm (4 watts) which means a 6dbi dipole is limited to 1W & an 18dbi dipole to 63mW Many unintentional emitters can easily overpower that
You wouldn't want to be pumping out more power anyway. The RPi barely gets 10W to run the whole thing, best case. Never mind battery-powered devices!
-
-
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.
- Show replies
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.