Chris, I agree that your observation has a lot of truth in it. One of the reasons behind it is that with electrical signaling, almost all of our noise sources are eventually deterministic, the noise contributors tend to have truncated distributions, so apart of a very narrow active region, the BER slope is like a flip-flop; either works or doesnt work. The truly Gaussian white noise is surely there, but our signal levels are so much above this noise floor that most of the failures are traceable to deterministic events in the system. The distributions of our disturbances are mostly truncated, we just often times tend to extrapolate to more sigmas down the curve. And if we dont extrapolate, but take the time to collect the number of samples to get the BER, we may not be sure that our 'noise' contributors stayed stationary during the data collection window. To answer the original question, yes, I have seen several systems to fail with frequent enough bit errors so that it was obviously worse than 1E-12, but not so bad that the system would stop working. In these systems, with some digging, usually one can pinpoint a set of circumstances and/or data patterns that eventually will force the system fail repetitively. But in a complex system, where 'noise' contributions may also come from remote sub systems, it is close to impossible to catch those same exact circumstances AND data patterns just by excercising the high-speed serial link with any practical length of pseudorandom data. The conclusion to me is: the forgiving coded differential signaling does not substitute for a proper worst-case design check of the link. Regards, Istvan Novak SUN Microsystems Chris Cheng wrote: >I've been shipping Gb/s serial products for a while and have my share of >fail parts. However, I have yet to see a physical channel that is not either >working like a charm or just fall on its face and barfing errors like crazy. >Sure, chips or disk can fail and generates errors but no flaky channels that >spits an error every other hour or days. To me, the channel is either have a >BER that is near 1 (barfing errors like crazy) or near 0 (never fail, or at >least approaching the life of the product it is attached to). >Are we just kidding ourselves with these fancy BER analyzers or jitter >instruments ? Do you really let a machine runs at say BER 10e-12 and say "ah >ha, it only fails once a day and let's ship it" ? Is BER really meant for >IEEE spec committees and not for real engineers who actually have to ship a >product ? >------------------------------------------------------------------ >To unsubscribe from si-list: >si-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field > >or to administer your membership from a web page, go to: >//www.freelists.org/webpage/si-list > >For help: >si-list-request@xxxxxxxxxxxxx with 'help' in the Subject field > >List FAQ wiki page is located at: > http://si-list.org/wiki/wiki.pl?Si-List_FAQ > >List technical documents are available at: > http://www.si-list.org > >List archives are viewable at: > //www.freelists.org/archives/si-list >or at our remote archives: > http://groups.yahoo.com/group/si-list/messages >Old (prior to June 6, 2001) list archives are viewable at: > http://www.qsl.net/wb6tpu > > > > > ------------------------------------------------------------------ To unsubscribe from si-list: si-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field or to administer your membership from a web page, go to: //www.freelists.org/webpage/si-list For help: si-list-request@xxxxxxxxxxxxx with 'help' in the Subject field List FAQ wiki page is located at: http://si-list.org/wiki/wiki.pl?Si-List_FAQ List technical documents are available at: http://www.si-list.org List archives are viewable at: //www.freelists.org/archives/si-list or at our remote archives: http://groups.yahoo.com/group/si-list/messages Old (prior to June 6, 2001) list archives are viewable at: http://www.qsl.net/wb6tpu