Appendix A Legacy Script Decoding - LeCroy Advisor User Manual

USBAdvisor User Manual
Appendix A: Legacy Script Decoding
Earlier LeCroy USB Analyzers used .REQ and .DSC script files to decode class and
vendor requests.
This method uses fixed definitional structures.
For legacy script decoding, LeCroy provides .req files for the following requests and
classes:
Note:
If you must add your own .req file for a Class or Vendor Request, do the following:
Step 1 Use the Notepad application to create and edit your own Request Definition file
Note:
Step 2 Add the name of your Request file to the request.lst file.
Step 3 Click Setup. The decoding menu in the Class/Vendor List appears.
LeCroy Corporation
• .REQ stands for Requests.
• .DSC stands for Descriptors.
• Standard Requests (standard.req)
• Hub Class (hub.req)
• HID Class (hid.req)
• Printer Class (printer.req)
• Communications Class (communication.req)
• Audio Class (audio.req)
• Bluetooth USB HCI commands and events (bluetooth.req)
• Vendor Request definition file (vendor.req)
.req files are no longer used in LeCroy USB Analyzers.
In addition, .req files are not compatible with the UWBTracer
application.
The new script decoding for LeCroy USB Analyzers uses
Script Decoder version .dec files.
.dec files are compatible with the UWBTracer application.
It is highly recommended that you use the new Script Decoder
mechanism.
For information about .dec files and the new script decoding, see
"Class and Vendor Definition Files" on page 85.
(for example, my_vendor_commands.req).
To learn to write such a file, review the Request (.req) files provided by
LeCroy.
Appendix A: Legacy Script Decoding
147