At the 6th of March 2017 Mozilla released a new version of their Firefox Browser, which drops Java support. So Firefox 52 can no longer be used for programming Universal Transceivers.
Author Archives: matthias.steines
We've designed an additional model of our FLEXBOX series, now supporting our Universal CFP, CFP2 and CFP4 optics in addition to our already established form factors SFP, SFP+, SFP28, XFP, QSFP+ and QSFP28.Get your CFP capable FLEXBOX now
Self-configure option for CFPs in our store
Once you own a FLEXBOX supporting CFPs you
- get your usual discount by configuring CFPs yourself - just select the "self-configure" option
- can decide later in which vendor platform you want to use your optics
We can provide configurations for the following Universal Transceivers
- C.161HG.10 - 100G CFP, 10km, LC-Duplex, LR4
- C.161HG.20 - 100G CFP, 20km, LC-Duplex, LR4
- C.1640G.10 - 40G CFP, 10km, LC-Duplex, LR4
- C.851HG.02.M - 100G CFP, Multimode, MPO/MTP, SR10
- C2.161HG.10 - 100G CFP2, 10km, LC-Duplex, LR4
- C4.161HG.104 - 100G CFP4, 10km, LC-Duplex, LR
Optimized Reconfiguration for all FLEXBOXes
Also, since nothing sucks more than waiting unnecessarily long for a reconfiguration to complete, we've optimized our reconfiguration process, to be significantly faster, especially for our more exotic products.
This enhancement applies to all currently available models of the FLEXBOX series.
We send out sweets all the time and - lucky you - we seldomly need to use the birch. However - now that end of the year is getting closer, we get most charming questions regarding the FLEXBOX reconfiguration Flatrate.
So ... please check your FLEXBOX application ... by now you should see a notification for unlimited reconfiguration for your FLEXOPTIX transceivers in 2017.
All the best, the FLEXOPTIX Nikolaus.
OSNR Characteristics with External CDR for for FLEXOPTIX tunable DWDM P.1696.23.xT (*)
at different datarates, Bit-Error-Rates, Rx Input Power Ranges, and dispersion levels.
Data Rate (gbps) BER Dispersion (ps/nm) Rx Power Range (dBm) OSNR (dB) 10.709 1E-4 0 -7 to -18 16 10.709 1E-4 -400 to +1450 -7 to -18 19 11.1 1E-4 0 -7 to -18 17 11.1 1E-4 -400 to +1450 -7 to -18 20 9.95
1E-12 0 -7 to -24 30 9.95
1E-12 0 -7 to -19 25 9.95
1E-12 -400 to +1450 -7 to -19 26
(*) For all technology loving people: There is a balance or better a direct relation between Data Rate, BER (Bit-Error-Rate), Chromatic Dispersion (CD), Rx Power Range and OSNR (Optical-Signal-to-Noise-Ratio). A high gap between Signal-Level and Noise-Level results in a low BER. To achieve this big gap the input power needs to be higher than with lower BER and same OSNR. If you consider the Cromatic Disperion, too you need to have around 3-4dB more input power than without Chromatic Dispersion. This 3-4dB are known as Dispersion Penalty which has to be considered when CD is in given range. This is almost the same for all data-rates around 10G. (here 10.709-11.1 gbps) If you for example compare this with a 1G signal the OSNR can be much lower because of higher signal spacing.
While tunable XFP started already in 2010 it took a couple of years to introduce this tuning capability to a SFP+. The main barrier was cutting down the power consumption of the tunable SFP+ to fit in the SFP+ MSA.
There are two Power Levels defined:
- Power Level I modules - up to 1.0 W
- Power Level II modules - up to 1.5W
P.1696.23.xT fits in Power Level II which guarantees that this device will work in all switches which are working with Power Levels defined in MSA.
Very low power consumption compared to XFP MSA which has defined Power Levels up to Level 4 with greater than 3.5 W. Resultant from this low power consumption there is one main difference between tunable XFP and tunable SFP+:
CDR functionality. (Clock-Data-Recovery)
XFP is born with CDR (defined in MSA) while SFP+ is without. Sure there are some SFP+ on the market with CDR but these are already working at Power Level II so that there is no space for tuning capability.
Usually the host borad for xWDM applications have a CDR chipset or the transceiver is working with a FEC (Foward-Error-Correction) mechanism.