The Walsin Multiplexer Export Is Offset by One Column

Walsin’s 116-row multiplexer export shifts one column to the left from Pin Description onward. Pin Description holds an impedance value, Pin Description.1 holds the construction category LTCC, and Category itself is empty on all 116 rows. Reading the file uncorrected gives a naive average pin count of 50 — impossible for an LTCC multiplexer. Corrected, the real average is 6.1 pins.

---

Venatech Limited, an authorised Walsin distributor in Hong Kong, holds the Walsin Technology (Walsin) multiplexer parametric export, 116 rows across two multiplexer types. This post publishes a data defect we found in Walsin’s own export and the exact correction we apply before using the file. Nothing here implies Walsin’s parts are wrong — only that nine of the twenty columns in this one export are shifted.

What is wrong with Walsin’s multiplexer export?

Every column from Pin Description onward holds the value that belongs one header to its right. The export has 20 columns. The last nine are Pin Description, Impedance for Frequency 1, Impedance for Frequency 2, Impedance for Frequency 3, Attenuation for Frequency 1, Attenuation for Frequency 2, Attenuation for Frequency 3, Pin Description.1, and Category. On all 116 rows, the data in each of those cells belongs to the header immediately to the right of its own:

Header as labelled	What it actually contains	Verified on
Pin Description	The real Impedance for Frequency 1 (always 50Ω)	116 of 116 rows
Impedance for Frequency 1	The real Impedance for Frequency 2 (always 50Ω)	116 of 116 rows
Impedance for Frequency 2	The real Impedance for Frequency 3 (50Ω or blank)	116 of 116 rows
Impedance for Frequency 3	The real Attenuation for Frequency 1 (a dB table)	116 of 116 rows
Attenuation for Frequency 1	The real Attenuation for Frequency 2 (a dB table)	116 of 116 rows
Attenuation for Frequency 2	The real Attenuation for Frequency 3, where it exists	13 of 116 rows
Attenuation for Frequency 3	The real Pin Description (pin count)	116 of 116 rows
Pin Description.1	The real Category (LTCC)	116 of 116 rows
Category	Nothing — there is no 21st column to supply it	0 of 116 rows

This matches what we found for the RF chip filter export, where Filter Type carries a double-space spelling defect, and it is a different kind of problem from that one: here the values themselves are correct, they are simply filed under the wrong header. A script that trusts the header names without checking will read every one of these nine fields wrong.

What does a naive read of the Pin Description column return?

50.0, on every one of the 116 rows, as an average. We parsed the labelled Pin Description column as a number across the full file: all 116 values resolve to 50, because that column actually holds the real-impedance figure, not a pin count. A naive script computing “average pin count” from the field Walsin’s own header calls Pin Description returns 50 pins on an LTCC multiplexer the size of a single surface-mount passive. That number should be the first signal that the column is wrong — no part in this catalogue is anywhere near a 50-pin package.

What does the corrected read return?

6.1 pins on average, and five real values: 4, 6, 8, 6-LGA and 9-LGA.

Pin count (corrected)	Parts	Share of 116
6	84	72.4%
8	15	12.9%
4	9	7.8%
6-LGA	7	6.0%
9-LGA	1	0.9%

What a naive script reads	What a corrected read returns	Match / mismatch
Average “pin count” = 50.0	Average pin count = 6.1	Mismatch — naive figure is not a pin count at all
“Pin Description” field holds an impedance	Real Pin Description holds 4, 6, 8, 6-LGA or 9-LGA	Mismatch — field contents and header name do not agree
“Category” is blank on 116 of 116 rows	Real category is LTCC on 116 of 116 rows	Mismatch — the part is fully specified, the column is not

The correction is one column shift, applied once: read each of the nine affected columns as the value that belongs to the header one position to its right, and drop the final Category column, which has nothing left to receive.

Does the shift also hide the construction category?

Yes, completely. The labelled Category column is empty on all 116 rows — read naively, it looks as though Walsin publishes no construction category for any multiplexer in the file. The real figure is one column to the left, in Pin Description.1, where it reads LTCC on all 116 rows without exception. Every multiplexer in this export is LTCC construction; the export simply never says so under the header that claims to say it.

How do I tell a diplexer from a triplexer once the columns are corrected?

By the real Impedance for Frequency 3 field and by how many frequency bands are populated. 105 of the 116 rows are labelled Diplexer and 11 Triplexer. Once impedance is read from the corrected position, a third 50Ω figure appears on exactly 13 rows — the 11 triplexers plus two rows still labelled Diplexer that in fact carry three populated frequency bands each (AMDIP1606L96A8Q1C and AMDIP1606L96B8Q1C, both spanning 2400–2500 MHz, 4900–5100 MHz and 5150–5950 MHz). Those two carry a triplexer’s frequency structure under a diplexer label — a second, smaller inconsistency layered on top of the column shift, and one to flag separately rather than fold into the main correction.

Part number	Labelled type	Populated frequency bands	Match / mismatch
RFTIP2109ATM0T63	Triplexer	3	Match — label agrees with structure
AMDIP2004L157B1U	Diplexer	2	Match — label agrees with structure
AMDIP1606L96A8Q1C	Diplexer	3	Mismatch — structure reads as a triplexer
AMDIP1606L96B8Q1C	Diplexer	3	Mismatch — structure reads as a triplexer

Can I trust any other field in this file without checking it?

The first eleven columns are unaffected. Part Number, Series, Multiplexer Type, Size, Application, Frequency 1 through Frequency 3, and Insertion Loss for each frequency read correctly and need no correction. The shift begins exactly at Pin Description, the twelfth column, and runs through to the end of the row. Any script built against this file should apply the one-column correction from that point on and treat the final Category field as structurally unfillable, not as a missing-data gap to chase down.

Do you hold a Walsin multiplexer datasheet?

No. Venatech holds no datasheet and no public datasheet URL for Walsin’s multiplexer line. This post, and the correction in it, are built entirely from the parametric export. Confirm every frequency, insertion loss and attenuation figure above against Walsin’s own documentation before a design is frozen on it.

For the rest of the RF front end, see The Walsin RF front end: switches, BAW, SAW and multiplexers and Walsin RF baluns: how to pick one. The full range is on the Walsin RF products page.

The short version

Walsin’s multiplexer export is internally consistent once you know the rule: everything from Pin Description onward belongs one column to the right of its header, and Category is left with nothing to hold. A naive script averaging the labelled pin-count field gets 50.0, which is not a real pin count on any part in the file. The corrected figure is 6.1, with real values of 4, 6, 8, 6-LGA and 9-LGA, and every one of the 116 parts is LTCC construction.

Send us your multiplexer requirement and Venatech Limited, an authorised Walsin distributor in Hong Kong, will read the corrected fields back to you — pin count, impedance and attenuation, not the header a naive script would trust.

Check it against the catalogue yourself. Cross-reference accepts one part number or a whole BOM column and prints the mismatches as plainly as the matches — qualification stays with you, which is the honest division of labour. Ready stock covers the RF part lines held in Hong Kong.

---

Frequently asked questions

<!– wp:rank-math/faq-block {"questions":[{"id":"faq-question-01","title":"Why is Walsin's multiplexer export offset by one column?","content":"The last nine of its 20 columns — from Pin Description onward — each hold the value that belongs under the header one position to the right. Pin Description holds an impedance figure, Pin Description.1 holds the construction category LTCC, and Category is left empty because there is no 21st column to supply it. Venatech found and corrected this across all 116 rows.”,”visible”:true},{“id”:”faq-question-02″,”title”:”What happens if I read the Pin Description column without correcting it?”,”content”:”You get an impedance value, not a pin count. Parsed as a number across all 116 rows, the labelled Pin Description field averages 50.0 — the standard RF impedance figure, not a realistic pin count for any LTCC multiplexer in Walsin’s range.”,”visible”:true},{“id”:”faq-question-03″,”title”:”What is the real pin count once the shift is corrected?”,”content”:”An average of 6.1, from real values of 4 pins (9 parts), 6 pins (84 parts), 8 pins (15 parts), and two LGA variants, 6-LGA (7 parts) and 9-LGA (1 part). No part in the 116-row extract carries anywhere near 50 pins.”,”visible”:true},{“id”:”faq-question-04″,”title”:”Does the empty Category column mean Walsin does not publish a construction type?”,”content”:”No. The real value is one column to the left, in Pin Description.1, where it reads LTCC on all 116 rows. Every multiplexer in this export is LTCC construction; the shift just moved the answer out of the column that claims to hold it.”,”visible”:true},{“id”:”faq-question-05″,”title”:”How many Walsin multiplexers are diplexers versus triplexers?”,”content”:”105 are labelled Diplexer and 11 Triplexer. Two of the diplexer-labelled rows, AMDIP1606L96A8Q1C and AMDIP1606L96B8Q1C, carry three populated frequency bands each — the structure of a triplexer under a diplexer label — which is a separate inconsistency from the column shift.”,”visible”:true},{“id”:”faq-question-06″,”title”:”Are any other columns in the multiplexer export affected?”,”content”:”No. The first eleven columns — part number, series, multiplexer type, size, application, the three frequency bands and their insertion loss figures — read correctly as labelled. The shift begins at Pin Description, the twelfth column, and runs to the end of the row.”,”visible”:true},{“id”:”faq-question-07″,”title”:”Does Walsin publish a multiplexer datasheet Venatech can link to?”,”content”:”No. Venatech holds no datasheet and no public datasheet URL for this line. Every figure in this post comes from the parametric export, corrected for the column shift, and should be confirmed against Walsin directly before a design review.”,”visible”:true},{“id”:”faq-question-08″,”title”:”Does this column shift affect part ordering or the part numbers themselves?”,”content”:”No. Part Number, Series, Multiplexer Type, Size, Application and the three frequency columns are unaffected. The shift is confined to pin description, impedance, attenuation and category — specification fields, not the ordering code.”,”visible”:true}],”listStyle”:””,”titleWrapper”:”h3″,”titleCssClasses”:””,”contentCssClasses”:””,”sizeSlug”:””} –>

---