I think you are suggesting that a TxVEC of 8.1dB would enable the link just to close. I would be surprised it that were true if the TXVEC were due to large
DCD with low RIN. What were the parameter(s) you adjusted to change the VEC?
Mike Dudek
QLogic Corporation
Director Signal Integrity
26650 Aliso Viejo Parkway
Aliso Viejo CA 92656
949 389 6269 - office.
Mike.Dudek@xxxxxxxxxx
From: John Petrilla [mailto:john.petrilla@xxxxxxxxxxxxx]
Sent: Thursday, June 26, 2014 5:23 PM
To: Jonathan King; STDS-802-3-100GNGOPTX@xxxxxxxxxxxxxxxxx; a_flatman@xxxxxxxxxxxxx; Abbott, John S Dr; Amezcua, A. (Adrian); Andy Moorwood; Anslow, Peter; Anthony Torza; Bernstein, Gary; Ephrem Wu; Gary Nicholl (gnicholl); Harry Fu; Jack Jewell; Jeffery
Maki; Keith Nellis; Kolesar, Paul; Lian Zhao; Martin Gilpatric; Phil.McClay@xxxxxx; Mike Peng Li; Mike Dudek; mnowell@xxxxxxxxx; Oren Sela; Patrick Decker; Rabinovich, Rick (Rick); Rick.Pimpinella@xxxxxxxxxxx; Robert Coenen; Ryan Latchman; Scott Kipp; Swanson,
Steven E; Tracy, Nathan L; Vipul Bhatt
Subject: RE: [802.3_100GNGOPTX] MMF ad hoc, Thursday 26th June, 2014, 9am to 10.30 am Pacific
Hello
Below is a chart that I didn’t have ready for my presentation today that may speak to the max value for TxVEC. It shows a correlation of a normalized TxVEC
margin to link model margin where TxVEC includes the effect of receiver noise as presented in my contribution today. Here link model margin ranges from 0 for the worst case Tx with the worst case input to ~5 dB for an idealized Tx and input signal. This
range is easily found with the link model. Those same Tx attributes yield a TxVEC range from ~ 8.1 (for worst case Tx) to ~1.1 (for ideal Tx). I normalized TxVEC margin by subtracting the TxVEC value for a given set of Tx attributes from 8.1 and dividing
the result by 1.44. You can see below how well the fit is for intermediate sets ofTx attributes.
An approach like this can normalize any metric that has a linear relationship with link margin – a one-to-one mapping doesn’t seem needed. The key is to normalize
the metric to match the range of link model margin.
By the way, Series 1 is the normalized TxVEC margin results for sets of Tx attributes that yield + link margin and Series 2 is a slope of 1.
Regards,
John
From: Jonathan King [mailto:jonathan.king@xxxxxxxxxxx]
Sent: Wednesday, June 25, 2014 3:43 PM
To: John Petrilla;
STDS-802-3-100GNGOPTX@xxxxxxxxxxxxxxxxx;
a_flatman@xxxxxxxxxxxxx; Abbott, John S Dr; Amezcua, A. (Adrian); Andy Moorwood; Anslow, Peter; Anthony Torza; Bernstein, Gary; Ephrem Wu; Gary Nicholl (gnicholl); Harry Fu; Jack Jewell; Jeffery Maki; Keith Nellis; Kolesar, Paul; Lian Zhao; Martin Gilpatric;
Phil.McClay@xxxxxx; Mike Peng Li;
mike.dudek@xxxxxxxxxx; mnowell@xxxxxxxxx; Oren Sela; Patrick Decker; Rabinovich, Rick (Rick);
Rick.Pimpinella@xxxxxxxxxxx; Robert Coenen; Ryan Latchman; Scott Kipp; Swanson, Steven E; Tracy, Nathan L; Vipul Bhatt
Subject: RE: [802.3_100GNGOPTX] MMF ad hoc, Thursday 26th June, 2014, 9am to 10.30 am Pacific
Thanks John, I’ll add your presentation to the agenda
From: John Petrilla [mailto:john.petrilla@xxxxxxxxxxxxx]
Sent: Wednesday, June 25, 2014 3:42 PM
To: Jonathan King;
STDS-802-3-100GNGOPTX@xxxxxxxxxxxxxxxxx;
a_flatman@xxxxxxxxxxxxx; Abbott, John S Dr; Amezcua, A. (Adrian); Andy Moorwood; Anslow, Peter; Anthony Torza; Bernstein, Gary; Ephrem Wu; Gary Nicholl (gnicholl); Harry Fu; Jack Jewell; Jeffery Maki; Keith Nellis; Kolesar, Paul; Lian Zhao; Martin Gilpatric;
Phil.McClay@xxxxxx; Mike Peng Li;
mike.dudek@xxxxxxxxxx; mnowell@xxxxxxxxx; Oren Sela; Patrick Decker; Rabinovich, Rick (Rick);
Rick.Pimpinella@xxxxxxxxxxx; Robert Coenen; Ryan Latchman; Scott Kipp; Swanson, Steven E; Tracy, Nathan L; Vipul Bhatt
Subject: RE: [802.3_100GNGOPTX] MMF ad hoc, Thursday 26th June, 2014, 9am to 10.30 am Pacific
Hello Jonathan
In case there’s time tomorrow,
attached please find some preliminary results for
including a 12.6 GHz filter in the TxVEC measurement and a review of what has turned out to be an unrealistically optimistic
assumption for
the
reference receiver sensitivity.
Regards,
John
<<...>>
-----Original Appointment-----
From: Jonathan King [mailto:jonathan.king@xxxxxxxxxxx]
Sent: Tuesday, June 24, 2014 6:28 PM
To: STDS-802-3-100GNGOPTX@xxxxxxxxxxxxxxxxx;
a_flatman@xxxxxxxxxxxxx; Abbott, John S Dr; Amezcua, A. (Adrian); Andy Moorwood; Anslow, Peter; Anthony Torza; Bernstein, Gary; Ephrem Wu; Gary Nicholl (gnicholl); Harry Fu; Jack Jewell; Jeffery Maki; John Petrilla;
Keith Nellis; Kolesar, Paul; Lian Zhao; Martin Gilpatric;
Phil.McClay@xxxxxx; Mike Peng Li; mike.dudek@xxxxxxxxxx;
mnowell@xxxxxxxxx; Oren Sela; Patrick Decker; Rabinovich, Rick (Rick);
Rick.Pimpinella@xxxxxxxxxxx; Robert Coenen; Ryan Latchman; Scott Kipp; Swanson, Steven E; Tracy, Nathan L; Vipul Bhatt
Subject: [802.3_100GNGOPTX] MMF ad hoc, Thursday 26th June, 2014, 9am to 10.30 am Pacific
When: Thursday, June 26, 2014 9:00 AM-10:30 AM (UTC-08:00) Pacific Time (US & Canada).
Where: Webex
Dear all,
As announced last week, here are call in details for the next MMF ad hoc which will be held on Thursday June 26th, 9 am to 10.30 am Pacific.
I’ll send out a provisional agenda on Wednesday.
Best wishes
jonathan
Jonathan King invites you to an online meeting using WebEx.
Meeting Number: 592 825 040
Meeting Password: IEEE
-------------------------------------------------------
To join this meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to
https://finisar.webex.com/finisar/j.php?MTID=m422b7bbe7c21eca0a1734c7b76bb463a
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: IEEE
4. Click "Join".
5. Follow the instructions that appear on your screen.
-------------------------------------------------------
Teleconference information
-------------------------------------------------------
Call-in toll-free number:1-866-668-0721
Conference Code: 1754333623
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically
consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of
litigation.