Skip to main content
FADOS MUX 100-Channel multiplexer connected to a test fixture for production PCB testing

FADOS MUX in Production: Setting Up 100-Channel Automated Board Testing

GSAS Engineering · · 8 min read

From Bench Diagnostic to Production Test Station

The FADOS MUX transforms the FADOS VI curve tracer from a manual bench tool into an automated production test system. Where a technician manually probing a board might test 30–50 points in 20 minutes, the MUX scans up to 100 test points in under 60 seconds, comparing every point against a golden reference and generating a pass/fail report without human interpretation.

For Indian EMS (Electronics Manufacturing Services) facilities handling incoming inspection, end-of-line testing, or depot-level repair verification, this automation directly addresses two persistent challenges: testing throughput and operator skill dependency.

System Architecture

A complete FADOS MUX test station consists of:

  • FADOS 9F1 or 7F1: the VI curve tracing engine (FADOS 9F1 or FADOS 7F1)
  • FADOS MUX module: 100-Channel relay multiplexer with multi-way connector interface
  • Test fixture: custom bed-of-nails or pogo-pin fixture matched to the board under test
  • FADOS software: controls the MUX, stores golden references, runs automated comparison, generates reports

The MUX connects to the FADOS unit via a standard interface cable and to the test fixture via a 96-pin connector. The FADOS software treats the MUX as a channel expander, each of the 100 channels is sequentially connected to the VI curve tracing circuit, measured, and compared against the stored reference.

Phase 1: Fixture Design

The test fixture is the mechanical interface between the MUX and the board under test. Each pogo pin or test probe in the fixture maps to one of the MUX’s 100 channels.

Selecting Test Points

Not every component on the board needs a dedicated test point. Prioritize:

  • Power rails: VCC, GND, and intermediate voltage rails at multiple locations
  • High-value components: processors, FPGAs, memory ICs, power regulators
  • Known failure points: components with historically higher failure rates
  • Connector pins: interface connectors where assembly defects are common
  • Decoupling capacitors: these fail frequently and are easy to test via VI signature

For a typical automotive ECU with 400–600 components, 60–80 strategically placed test points provide coverage sufficient to catch the majority of manufacturing defects.

Fixture Construction

Most production fixtures use spring-loaded pogo pins mounted in a machined alignment plate. The board sits on registration pins that ensure repeatable positioning. Vacuum hold-down or mechanical clamps keep the board stable during testing.

For lower-volume applications, hand-wired fixtures with individual probes can be built faster and at lower cost, though they sacrifice the repeatability and speed of a precision-machined fixture.

Phase 2: Golden Board Learning

The golden board learning process creates the reference database against which all subsequent boards are compared.

Procedure

  1. Select a known-good board: ideally from a production batch that has passed functional testing
  2. Mount the board in the fixture: verify all pogo pins make clean contact
  3. Run the learning sequence: the FADOS software cycles through all 100 channels, recording the VI curve signature at each point
  4. Repeat with 3–5 additional known-good boards: multiple samples establish the normal variation range for each test point
  5. Set tolerance bands: the software calculates mean signatures and allows the operator to define acceptable deviation thresholds per channel

Tolerance Tuning

Tolerance settings require engineering judgment. Passive components (resistors, capacitors) typically show tight VI signature clustering across boards and can use narrow tolerance bands. Semiconductor junctions (transistors, diodes, ICs) may show wider variation and need broader tolerance bands to avoid false failures.

The FADOS software provides per-channel tolerance adjustment, so the operator can tighten tolerances on critical test points while relaxing them on components with inherent variation.

Phase 3: Production Testing

With the fixture built and golden reference established, production testing follows a repeatable cycle:

  1. Operator loads board into fixture (5–10 seconds)
  2. Operator presses “Test” in FADOS software (1 second)
  3. MUX scans all 100 channels (30–60 seconds depending on configuration)
  4. Software generates pass/fail report (instant)
  5. Operator removes board and sorts pass/fail (5–10 seconds)

Total cycle time per board: approximately 45–90 seconds. Compare this to 20–40 minutes for manual VI probing of equivalent coverage.

Report Output

The FADOS software generates a test report for each board containing:

  • Pass/fail status per channel
  • VI curve overlay (measured vs. reference) for each failed channel
  • Deviation magnitude for each failure
  • Timestamp and operator ID

These reports provide traceability documentation for ISO 9001 quality systems and can be exported for integration with MES (Manufacturing Execution System) databases.

Phase 4: Ongoing Maintenance

Fixture Maintenance

Pogo pins wear over time. Plan for pin replacement based on test volume, typical spring-loaded pogo pins are rated for 100,000–500,000 cycles. Monitor first-pass yield trends; a gradual increase in false failures often indicates worn or contaminated probe tips.

Reference Updates

When the board design changes (ECO revisions), the golden reference must be re-learned. Maintain revision-controlled reference files so the correct reference loads automatically based on board revision markings.

Why Buy FADOS MUX from GSAS

GSAS Micro Systems is an authorized ProT Ar-Ge partner and ODM assembler. Our team in Bengaluru supports fixture design consultation, golden board learning assistance, and tolerance optimization for production deployments.

We support FADOS MUX installations across India, Bengaluru, Hyderabad, Chennai, Pune, Mumbai, Delhi NCR, and Visakhapatnam: with on-site commissioning, operator training, and ongoing service.

  • INR invoicing with GST-compliant documentation
  • Fixture design guidance based on board complexity and test coverage targets
  • Training for operators and quality engineers

Request a FADOS MUX quote → · Book a demo →

Interested in ProT Ar-Ge tools?

Talk to our application engineers for personalized tool recommendations.

Stay in the Loop

Get monthly compliance updates, product insights, and engineering best practices delivered to your inbox.

Related Articles

Embedded engineering workstation in India, illustrating the debug, analysis and design steps where AI now runs inside the process, supported by GSAS
Industry Insights

AI Inside the Engineering Process: What Is Worth Automating, and What Still Needs an Engineer

Arm, SEGGER, Perforce and Siemens EDA have each put AI inside a step of the engineering process rather than on top of it: debug, remediation, design entry, inference on the part. GSAS sets out the position behind our coverage of each: which steps are now worth automating, and which keep a human because the cost of being wrong is a recall.

21 Sept 2026 · 11 min read
Master and slave roles on a 100BASE-T1 link: the master PHY times its transmitter from a local clock, the slave recovers the clock from the received signal, with the both-master and both-slave misconfigurations that leave the link down, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

100BASE-T1 Link Won't Come Up: A Vendor-Neutral Checklist

A 100BASE-T1 link that will not come up is almost never a mystery, but the answers on the web are written per silicon vendor and do not transfer. This is the ordered bring-up checklist that holds regardless of which PHY, switch or SoC you have: physical layer first, then the PHY over MDIO, then the master and slave pairing, then the causes of a link that comes up and drops. The standards and tooling claims trace to IEEE 802.3 task force records, the Linux ethtool and kernel documentation or published test material. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 14 min read
Horizontal stacked bar showing where an ADAS test vehicle's bandwidth budget is spent, split into cameras, lidar, radar and bus traffic, with the logger uplink limit drawn as a vertical rule crossing the bar, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

ADAS Sensor Data Logging: Bandwidth Budgets That Add Up

Every page that tells you an ADAS test vehicle produces terabytes a day states the headline and skips the arithmetic, so you cannot redo it for your own sensor set. This article publishes the arithmetic instead: one formula, every table row derived on the page, a worked eight-hour drive that chains those rows into a sustained write rate, a media count and an offload window, and the five places bandwidth budgets go wrong. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 15 min read