5 notes on lfps signals – Teledyne LeCroy USB Protocol Suite User Manual (Voyager_Advisor T3_Mercury) User Manual
Page 38

Teledyne LeCroy Corporation
USBTracer/Trainer, USB Advisor, USBMobile HS and USBMobile T2
38
USB Protocol Suite User Manual
Test scripts can customize ReadyLink Emulation Mode to include error scenarios, such as:
Header LBADs
Invalid link commands
8B10B / CRC Error
Running Disparity Error
Corrupt Link Commands
Corrupt Flow Control (Wrong L_CRD_x, Wrong L_GOOD_n, Drop L_Good_n)
Corrupt Header Packet acknowledgement (Send LBAD, LRTY)
Corrupt Packet Framing (SHP, SDP, END)
At the packet level, you can send customized data payloads anywhere within the stream
to insert logic errors, perform corner‐case, or do stress testing. Commands, such as the
Set ErrWrongLCRD command, allow link‐layer error injection anywhere within the script.
1.5.5
Notes on LFPS Signals
Voyager Exerciser requires received “Ping” LFPS signals to be a minimum of
150 nanoseconds to be reliably recognized.
Voyager Analyzer can recognize “Ping” LFPS signals above 60 nanoseconds and report
their durations to ±15 nanoseconds of accuracy.
1.6
USBTracer/Trainer, USB Advisor, USBMobile HS and USBMobile
T2
These CATC analyzers are no longer explicitly supported beginning in version 4.70.
No further validation testing will be done with this equipment, which have been deemed
End‐Of‐Life (EOL) by Teledyne LeCroy. Nothing will be done to remove support of these
older devices from the software, but the user should be cautioned that no new bug fixes
will be implemented for these analyzers. If problems occur on these EOL'd analyzers in
future releases, you will have to uninstall the newer software and install an older release
(4.60 or earlier) which will be available on the Teledyne LeCroy Web Site.
Earlier versions of the software include the documentation related to these units in their
respective User Manual versions.