1G–400G · SFP · SFP+ · SFP28 · QSFP · QSFP-DD
Coded Optical Transceivers for Named Network Platforms
A configurable optical transceiver range supplied against a recorded host, software release, port mode and approved coding profile—not a vague “compatible with everything” claim.
PRODUCT SCOPE
Choose the physical optic first; then approve its host identity
MingApex coordinates coded optical transceivers across common SFP, SFP+, SFP28, QSFP+, QSFP28, QSFP56 and QSFP-DD families. Every order begins with the real optical requirement: line rate, form factor, reach, wavelength, fibre, connector, temperature class, lane architecture and FEC. Coding is applied only after that physical baseline is clear.
The supplied identity can include agreed vendor, part-number, revision, serial, date-code, capability, checksum and DOM/DDM fields where the relevant memory map and hardware permit. The exact writable and protected regions vary by module architecture; a visible vendor name is not the complete coding profile.
Coding can support recognition and inventory presentation. It cannot turn an SR optic into LR, correct the wrong wavelength pair, add missing FEC support or guarantee operation on an unnamed host.
AVAILABLE FAMILIES
One controlled coding workflow across the product range
SFP / SFP+
1G and 10G identity, checksum and DOM/DDM profiles for access, enterprise and metro links.
SFP28
25G profiles with host port mode, required FEC and diagnostic behavior recorded together.
QSFP+ / QSFP28
40G and 100G multi-lane identity, breakout, lane and telemetry controls.
QSFP56 / QSFP-DD
200G and 400G application, firmware/profile revision, power class and CMIS-aware validation scope.
ORDER DEFINITION
Required data for a coded-transceiver quotation
| Buyer input | What MingApex freezes | Release evidence |
|---|---|---|
| Host model, chassis/card and port | The exact hardware tuple that reads the module | Inventory and diagnostic output from the named host |
| Software or firmware release | Allow-list, warning policy, port mode and known constraints | Recorded software baseline and test result |
| Optical specification | Rate, reach, wavelength, fibre, connector, lanes, FEC and temperature | Approved product specification and sample identity |
| Reference identity | Vendor/PN/revision/OUI policy, serial format and applicable checksums | Pre/post programming readback and controlled profile version |
| Quantity and repeat-order plan | Sample count, lot scope, labels, packaging and change notification | Serialized sample approval and production-lot comparison |
VALIDATION
Sample-first release workflow
1. Freeze
Record the host tuple, optic specification, coding target and acceptance limits before programming.
2. Program and read back
Apply the controlled profile, validate required fields and preserve the serialized identity record.
3. Prove and release
Check recognition, link, DOM, alarms, counters, FEC and traffic; bridge the approved sample to the production lot.
COMMERCIAL CONTROL
What the written quotation will confirm
- Exact product line: form factor, optical standard, reach, wavelength, connector and temperature class.
- Coding scope: named host/software target, identity fields, DOM profile and any protected-field limitation.
- Sample plan: quantity, lead time, test location, evidence format and approval boundary.
- Production control: profile version, serial rule, label/packaging reference, sampling and change notification.
- Commercial terms: unit price, MOQ, production lead time, Incoterm, payment, warranty and RMA boundary.
CONNECTED EVIDENCE