The Walsin antenna frequency range column cannot be joined to Walsin’s RF frequency columns as text. We compared all 44 antenna cells with 587 RF cells and exactly 1 matches. Convert GHz to MHz and strip the spaces and 22 of 44 join. The other 22 hold DC ranges, spot values, wildcards and a tolerance.
Venatech Limited, an authorised Walsin distributor in Hong Kong, holds the Working Frequency Range column of the antenna export from Walsin Technology (Walsin) and the frequency columns of all seven RF function files. This post is written from those cells, read as raw strings, and nothing else. We hold no datasheet for any antenna or RF part, so no band below is checked against a PDF. Every part number is real and sits in Walsin’s own export. The question is the one a front-end designer asks the day an antenna and a filter must share a band: can the two files be joined?
How many ways does Walsin write an antenna’s frequency range?
Twenty-two, for 44 parts. We parsed all 44 cells in Walsin_Antenna_ALL.xlsx and found 22 distinct strings, 21 once whitespace is collapsed, and 17 distinct shapes once every number is replaced by a placeholder. Three units appear: GHz on 34 cells, MHz on 9, KHz on 1. Each cell carries one unit, never two, but the unit sits after the last number, after every number, or attached to the digit with no space, depending on the row.
| Kind of cell | Cells | Example string | A real part carrying it | Match / mismatch against a parser built for low ~ high unit |
|---|---|---|---|---|
| Single range, GHz | 16 | 2.4~2.5 GHz and 2.4 ~ 2.5 GHz |
RFANT3216120A1T |
Match after trimming spaces |
| Single range, MHz | 5 | 863~928 MHz |
RFMTA010504NNRB002 |
Match on shape, mismatch on unit |
| Two-band range | 6 | 2.4 ~ 2.5 / 5.15 ~ 5.85 GHz |
RFDPA151414IMLB902 |
Mismatch — one cell, two bands |
| Spot value | 6 | 433MHz, 13.56 MHz, 100 KHz, 1.575 GHz, 2.4 GHz |
RFDPA131000SBUB802 |
Mismatch — no low and high |
| DC to 6 GHz | 6 | DC ~ 6GHz |
RFCBA000014NN6B301 |
Mismatch — DC is not a number |
| Wildcard | 3 | 5.x GHz |
RFDPA151415IM5B901 |
Mismatch — a letter inside the number |
| Centre plus or minus | 1 | 700±50 MHz |
RFDPA660900SMTB801 |
Mismatch — centre and spread, not edges |
| List of spot frequencies | 1 | 850/1900/2100 MHz |
RFDPA131012IMTB301 |
Mismatch — three points, one unit |
Add the rows: 16 + 5 + 6 + 6 + 6 + 3 + 1 + 1 is 44. A parser built for the commonest shape reads 21 of 44 cells cleanly. We have not seen this counted anywhere.
Does the antenna column use the same unit as the RF columns?
No. The RF side uses one unit and the antenna side uses three. We read every non-empty frequency cell in the seven RF function files that hold parts: 587 cells, 160 distinct strings, MHz on all 587 and GHz on none. The files are Walsin_Filter.xlsx, Walsin_Balun.xlsx, Walsin_Coupler.xlsx, Walsin_Multiplexer.xlsx, Walsin_SAW_Filter.xlsx, Walsin_BAW_Filter.xlsx and Walsin_Antenna_Switch.xlsx; the three hyphen placeholders in the SAW Frequency 2 column are not counted. The antenna column writes GHz on 34 of 44 cells. Joining the two on the text therefore fails by construction, and it fails in a quiet way: no error, just no rows.
We ran the join anyway. One antenna string out of 44 equals an RF string character for character: 880~960 MHz, on the metal antenna RFMTA060206NNBB002 and on the balun RFBLN20120G9D4T. Everything else, including the 15 single-band antennas at 2.4 to 2.5 GHz, returns nothing against 2400~2500 MHz.
After conversion the picture changes. We converted every antenna cell to MHz, split two-band cells into their bands, and asked whether each band equals an interval that appears in an RF file.
| Antenna part | Antenna cell | Converted to MHz | RF part with the identical interval | Match / mismatch |
|---|---|---|---|---|
RFANT3216120A1T |
2.4~2.5 GHz |
2400 to 2500 | RBBPF1005040A1T |
Match on band, mismatch on function — a chip antenna and a band pass filter |
RFMTA060206NNBB002 |
880~960 MHz |
880 to 960 | RFBLN20120G9D4T |
Match as text and as number |
RFDPA141300SBLB801 |
2.4~2.5GHz / 5.15~5.85GHz |
2400 to 2500 and 5150 to 5850 | each band exists in RF files | Match on both bands after splitting |
RFFPA401410IMGB301 |
1559 ~ 1609MHz |
1559 to 1609 | none | Mismatch — the nearest RF band is 1558 to 1606 on RFBPF1411070E0T |
RGFRA9937380A3T |
2.4~2.55 GHz |
2400 to 2550 | none | Mismatch — every RF band here stops at 2500 |
22 of the 44 antenna cells join exactly once units are converted. That is 16 single ranges and all 6 two-band cells. The other 22 cannot, and the next section lists them.
Which antenna cells can no frequency parser read?
Twenty-two, in six groups. We counted them against the converted join above, and each group fails for a different reason. Six cells read DC ~ 6GHz and belong to the three cable assemblies and three connectors that share the antenna file. Six are spot values. Three carry a lowercase x inside the number. One is a centre and spread. One is a list. Five are ordinary ranges that simply have no identical twin in the RF files.
| Group | Cells | Part carrying it | What a numeric parser does | Match / mismatch |
|---|---|---|---|---|
DC ~ 6GHz |
6 | RFCBA000014NN6B301 |
Rejects DC or reads 6 GHz alone |
Mismatch — and these are not antennas |
| Spot values | 6 | RFNFC355500NNNB001 at 13.56 MHz |
Reads one number, no band | Mismatch — nothing to test containment against |
Wildcard 5.x |
3 | RFPCA201018IM5B301 is 5.x GHz only |
Fails on the letter | Mismatch — we will not expand it to a band for you |
| Centre plus or minus | 1 | RFDPA660900SMTB801 |
Reads 700 and 50 as two numbers | Mismatch — means 650 to 750 MHz |
| Spot list | 1 | RFDPA131012IMTB301 |
Reads 850, 1900, 2100 as one cell | Mismatch — three bands |
| Range without an RF twin | 5 | RFMTA010504NNRB002 at 863 to 928 MHz |
Parses fine | Match on parse, mismatch on every RF edge |
The wildcard deserves a plain statement. 5.x GHz is on RFDPA151415IM5B901, on RFPCA201018IM5B301, and as the second half of 2.4 / 5.x GHz on RFDPA131012IMLB301. Walsin does not say what the x stands for in this export, and we hold no datasheet that would. We read it as “a 5 GHz band”, and no more than that.
How are two-band antennas written, and which notation silently drops a band?
Three notations for six cells, and the padded one drops a band without warning. We counted the characters between the two bands on RFANT6050110L0T and RFANT6050110L1T: 27 whitespace characters on the first, 29 on the second, and no slash. A splitter that breaks on / returns one band for those rows and discards 4.9 to 5.9 GHz.
| Notation | Cells | Example | Part | Match / mismatch against a splitter on / |
|---|---|---|---|---|
| Bands separated by a run of spaces | 2 | 2.4~2.5 GHz then 27 spaces then 4.9~5.9 GHz |
RFANT6050110L0T |
Mismatch — second band lost |
| Unit repeated after each band | 1 | 2.4~2.5GHz / 5.15~5.85GHz |
RFDPA141300SBLB801 |
Match — splits cleanly |
| Unit written once at the end | 3 | 2.4 ~ 2.5 / 5.15 ~ 5.85 GHz |
RFDPA151414IMLB902 |
Match on split, mismatch on unit — the first half has none |
Note the units in the third row. After a split, the first half reads 2.4 ~ 2.5 with no unit at all. A parser that looks for the unit inside each half and defaults to MHz would read 2.4 MHz. The same second band is also written 4.9 to 5.9 GHz on the padded rows and 5.15 to 5.85 GHz on the rest, so two different second bands share one column. For which bands hold a single orderable part, see chip antenna selection: 14 of Walsin’s 19 antenna bands hold exactly one part.
What should you normalise before filtering antenna and RF bands together?
Four things, in this order, and each one is a count above. First, split every cell on the slash and on any run of three or more spaces. Second, read the unit once per cell and apply it to every number in that cell. Third, convert to MHz, so 13.56 MHz stays 13.56 and 100 KHz becomes 0.1. Fourth, set aside the DC, x and spot cells and handle them by hand.
Do that and the first-pass join returns 22 of 44 antenna cells. It does not make the other 22 safe to skip. Six of them are cables and connectors, so exclude those rows by Series before you filter. For the fields that sit beside the band, see Walsin antenna specification fields: 4 of 10 are filled on all 44 parts.
Our free cross-reference tool states differences from your original rather than hiding them behind a tick. We checked the 1,125 part numbers in the ready-stock snapshot dated 23 September 2026 against all 501 antenna and RF part numbers: none appears, so these lines are enquiry items, and the snapshot is not a live feed. See ready stock for what is there, and the antenna range for the full 44 parts.
We hold 28 Walsin datasheets, 451 pages, and none covers antennas or RF. Frequency, gain and VSWR figures must be confirmed against Walsin’s own site, and qualification stays with you.
The short version
Walsin writes the antenna frequency range 22 ways across 44 cells, in three units, where the RF files use one. Compared as text, 1 antenna cell equals an RF cell. Converted to MHz and split into bands, 22 of 44 join exactly. The other 22 are 6 DC ~ 6GHz cells on cables and connectors, 6 spot values, 3 5.x wildcards, 1 700±50 MHz, 1 list and 5 ordinary ranges with no RF twin. Two chip antennas separate their bands with 27 and 29 spaces and lose one in a slash splitter. We will not tell you a band matches. We will show you the string the file holds. Confirm against both datasheets and qualify in your own circuit.
Send us the antenna and the filter you plan to pair and we will show you both cells as the file holds them. And a question back: when your join returned one row out of 44, did you decide the catalogue had nothing, or the text had not been read?
Frequently asked questions
How many different frequency strings are in the Walsin antenna export?
There are 22 distinct strings across 44 parts, 21 once whitespace is collapsed. They fall into 17 shapes when every number is replaced by a placeholder. Three units appear: gigahertz on 34 cells, megahertz on 9 and kilohertz on 1. No cell mixes two units.
Why does my join of Walsin antenna bands to RF filter bands return nothing?
Because the antenna column writes gigahertz on 34 of 44 cells and the RF columns write megahertz on all 587 of theirs. Compared as text, only 1 antenna string, 880 to 960 megahertz, equals an RF string. Converted to megahertz and split into bands, 22 of 44 cells join exactly.
Which antenna frequency cells cannot be parsed as a low and high pair?
Twenty-two cells fail the join. Six read DC to 6 gigahertz and belong to cable assemblies and connectors. Six are spot values, three contain a lowercase x in a 5 gigahertz entry, one is a centre with a plus or minus spread, one is a list of three spot frequencies, and five are ordinary ranges with no identical RF band.
What does 5.x GHz mean in the Walsin antenna export?
The export does not say. The string appears on 3 cells, on 2 parts alone and on one part beside 2.4 gigahertz. We hold no antenna datasheet, so we read it only as a 5 gigahertz band and have not expanded it to numbers. Confirm the exact edges against Walsin’s current specification.
Which Walsin antennas write two bands in one cell?
Six cells hold two bands, in three notations. Two chip antennas, RFANT6050110L0T and RFANT6050110L1T, separate 2.4 to 2.5 gigahertz and 4.9 to 5.9 gigahertz with 27 and 29 spaces and no slash. One part repeats the unit after each band, and three write the unit once at the end.
Are there Walsin antenna or RF parts in the ready-stock list?
Not as at 23 September 2026. We checked all 501 antenna and RF part numbers against the 1,125 part numbers in the snapshot and none appears. These lines are available on enquiry, and the snapshot is a dated list, not a live feed. Send the part numbers and we will tell you what we can supply.