-
Notifications
You must be signed in to change notification settings - Fork 145
TX/RX frequency range documentation #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This is just a RF matching question. It may be tuned to lower frequencies using different components. |
I guess the point is, is it a question of poor performance, or is it "you must modify the networks yourself to use the board at 100kHz"? |
The RF matching components are size 0402. Some stuff based on reading the schematics and googling: TCM1-63AX+ balun transformer is used in the 2-2.6 GHz branches for both TX and RX. The coupling caps in the 30 MHz-1.9 GHz branch are 100nF, which should be usable on HF, but might be too little at LF. |
Thanks for the analysis! Better info than I'd have come up with. Unrelated to the RF side of things, if you ever find yourself having to do a rework on components like that at your bench at home with a pretty-good-but-not-pro soldering station, get some ChipQuick. The stuff is seriously magical. |
Are there any real tests at very low frequencies so we can check it? |
LimeSDR USB,What is the name of the transmitting antenna? |
This isn't necessarily an issue, but for lack of a better place to discuss, I'll ask here: the LimeSDR is advertised with a working frequency range from 100kHz to 3.8GHz, but the schematic notes on the RF matching networks don't match this. I'm assuming (speaking of RX) that "RXRF2_L" is "low frequency", "_H" is "high frequency," and "_W" is "wideband." I suppose the overlap is to allow for mechanical design flexibility (using a single connection and antenna for full coverage) at the price of receive signal strength? Beyond that, both L+H and W seem to cover only 700MHz to 2.6GHz. Given my poor RF design skills, I don't know just looking at the matching networks if that's shorthand, or if those matching networks actually roll off sharply at those bounds and I'm missing something else. So I guess, what's the deal?
The text was updated successfully, but these errors were encountered: