Direct answer
A 1×N switch selects a path between a common port and multiple ports. An M×N matrix provides multiple inputs and outputs, but port count alone does not establish concurrency. List simultaneous connections, blocking rules, path specifications and control sequences. A fixed Optical Shuffle does not perform dynamic switching.
Select the architecture from the test task
EXFO describes non-blocking M×N matrices and blocking 1×N arrays for the MXS-9200, including centralized-instrument sharing and automated testing of multiple devices. Its architecture descriptions show why port count is an incomplete selection field. EXFO architecture
Use this guide for laboratory fixtures and monitoring access. An optical-path switch is not a packet-forwarding Ethernet switch. The example identifies an equipment category, not ARRANEX supply.
| Test requirement | Candidate structure | Confirm |
|---|---|---|
| One instrument visits several devices sequentially | 1×N or suitable array | Common port, outputs and sequence |
| Several instruments access several devices | M×N or a combined design | Simultaneous connections and conflicts |
| Independent groups of common-port polling | Multiple 1×N groups | Independence and port allocation |
| Fixed fiber rearrangement | Passive Optical Shuffle | Approved map, without dynamic control |
Provide a simultaneous-connection list
M×N identifies input/output scale. Supported concurrent combinations depend on the actual architecture and supplier definition. List which instruments need which device ports at the same time, then request confirmation. This guide prescribes no default concurrency count.
| State field | Record | Purpose |
|---|---|---|
| State ID | Unique test-state identifier | Associate results |
| Requested paths | Input/output pairing set | Express concurrency needs |
| Conflict rules | Occupied ports and prohibited combinations | Avoid resource contention |
| Start conditions | Completion, settling and acquisition criteria | Avoid premature measurement |
| Exit state | Normal, fault and power-loss requirements | Support recovery and protection |
Separate loss, stability and repeatability
EXFO's detailed specifications define stability and repeatability separately and identify wavelength and connector-boundary conditions. EXFO specification notes
Associate each optical result with its path and state. Initial insertion loss, variation while dwelling on one connection, and results after returning repeatedly to that path answer different questions. An average loss cannot replace those records or cover unmeasured paths.
Switching time alone is not a complete test-cycle duration. Record command issuance, state confirmation, agreed settling and acquisition separately. Validate timing through the actual test program rather than assuming a universal delay.
Define external test cords separately
Switch specifications do not automatically include external reference cords, branches, mating connections or the DUT. Assign cable IDs and align port diagrams, measurement boundaries and reference setup. Review a changed path after repatching. Use the existing Shuffle guide for fixed routing without treating that assembly as a programmable switch.
Procurement FAQ
- Does a 1×N switch split power to every output? Path selection and PLC splitting are different functions.
- Does M×N guarantee every simultaneous combination? Obtain explicit connectivity and blocking rules.
- Does one loss pass establish repeatability? Request evidence under repeated switching conditions.
- Is switching time the test-cycle time? Control, settling and acquisition also contribute.
- What starts the RFQ? Instruments, DUTs, simultaneous pairing sets, wavelengths and test objectives.
Related guides and configurations
Fixed fiber mapping · Splitting and fiber fan-out · Reference validity · Test reference cord configuration · Fixed Shuffle configuration
Contact an engineer. Share actual part references, drawings and test or acceptance needs for configuration review. Related links do not establish unverified supply, performance or qualification.
Sources and review date
Sources reviewed on 2026-10-12. Manufacturer examples apply only to the cited configurations, and calculations depend on stated assumptions. Procurement tables do not replace full specifications or establish unverified ARRANEX performance or qualification.
Sources checked: 2026-10-12