Drivers Tektronix USB Devices



I am trying to get a RSA306B spectrum analyzer to be recognized by NI MAX.The RSA306B is connected to the computer through USB 3.0 -The device shows up in device manager under USB controllers -I have downloaded the drivers provided by Tektronix for the RSA306B -I'm running Windows 7 With the RSA306B plugged in while Tektronix SignalVu-PC is running or not, the device does not show up in NI. All my USB ports are labeled with the USB 3.0 logo, one also has a lightning bolt next to it. If I plug into the lightning bolt port, the light on the RSA goes green, but the RSA doesn't show up in Device manager. If I plug into any of the other 3 ports, the RSA shows up in Device Manager, but the LED never goes green.

  • USBSSP-TX, USB-TX, BSAUSB31, BSXUSB31N DPOJET Analysis plots displaying eye mask hits, bath tub curve, and SSC profile The Tektronix USBSSP-TX and USB-TX Automated Transmitter solutions provide an easy way to validate and characterize emerging USB 3.2 Type-C host controllers, hubs and devices with Tektronix MSO/DPO/70000DX/ SX series oscilloscopes.
  • Quick Tips The USB 3.0 super-speed (SS) device port is the correct USB port for computer connectivity. Use the rear- and front-panel USB 2.0 or 3.0 host ports to connect your oscilloscope to USBflash drives, hard drives, keyboards or mice. Use the USB Device port to connect your oscilloscope to a PC.
Devices-->

This article helps to fix an issue in which Windows 10 doesn't install specific drivers for USB audio devices on the first connection.

Drivers Tektronix Usb Devices Pc Camera

Original product version: Windows 10, version 1703
Original KB number: 4021854

Symptom

When you connect a USB audio device to a Windows 10 Version 1703-based computer the first time, the operating system detects the device but loads the standard USB audio 2.0 driver (usbaudio2.sys) instead of the specific device driver.

Cause

This issue occurs because the USB audio 2.0 driver (usbaudio2.sys) isn't classified as a generic driver in Windows 10 Version 1703. Therefore, the system assumes that a compatible, nongeneric driver is installed for the device even though the driver is generic.

This issue also causes Windows 10 Version 1703 to postpone the search for other compatible drivers through Windows Update that typically occurs immediately after you install a new device.

Resolution

To fix this issue, use one of the following methods.

Method 1

To resolve this issue, install update 4022716.

Method 2

If the device-specific driver is distributed through Windows Update, you can manually update the driver by using Device Manager. For more information about how to do this, see update drivers in Windows 10.

Method 3

If the device is not yet connected, first install the device-specific driver, such as by using the appropriate installer. After the device-specific driver is installed, Windows 10 will select that driver instead of the standard USB audio 2.0 driver when you first connect the device.

Note

See the device manufacturer's user guide for specific instructions about how to install the driver.

Method 4

If the driver isn't distributed through Windows Update, you can manually reinstall the driver. To do this, follow these steps:

  1. Install the device-specific driver (see Method 2).
  2. Open Device Manager.
  3. Right-click (or tap and hold) the name of the device, and then select Uninstall.
  4. Restart the computer.

When it restarts, Windows will try to reinstall the device by using the device-specific driver.

Table of Contents

  • PyVISA and the NI-VISA Library on Windows
  • Python and Libusb with Linux

Finding USB Busses and Devices

  • For Linux, use lsusb to list usb busses and devices connected to them. The command, lsusb -v will provide much information. Then use lsmod to list the kernel modules loaded. Note that LinuxCommand.Org explains shell commands.

Instrument USB Interfaces

  • The USB test and measurement specifications provide the information necessary to communicate with compliant instruments. The GPIB over USB specifications are commonly used. Perusing these documents, one can readily understand why a dynamic library between Python and libusb or a substantial Python module would be so useful. Once you understand how to achieve communication over USB, then you can send commands and receive data according to the syntax for a particular instrument. An oscilloscope might conform to the Interchangeable Virtual Instruments - Scope Class specifications or the Standard Commands for Programmable Instruments (SCPI).

USB Linux Kernel Drivers

  • To understand device drivers in Linux, buy or download for free the Linux Device Driver book. The USB chapter.
  • Writing a Simple USB Driver by Greg Kroah-Hartman is illuminating.
  • The USBTMC kernel driver is a character device driver for USBTMC compliant instruments and can be downloaded here. This is an attractive solution for low speed communication, but since there is no Python module you will have to use ctypes and read and write to the /dev/usbtmcX files directly.

Drivers Tektronix Usb Devices Adapters

PyVISA and the NI-VISA Library on Windows

  • PyVisa can be used with XP to communicate with this oscilloscope via USB. As the documentation shows, this is accomplished using a LabView Visa compatible DLL.

    • Tektronix TDS1012B Digital Oscilloscope

    • This Python program acquires a waveform and performs an FFT using the FFT function in the SciPy or numpy packages. The crude tds1012b.py module provides a few functions and classes for the scope. The programming manual for the tds1000/2000 series explains the command sequences.
DriversDrivers Tektronix USB devices

PyVISA and the NI-VISA Library on Linux

  • As this informative forum exchange shows, this approach can be problematic, at least for Tektronix oscilloscopes.

PySerial

  • The PySerial module provide a simple means to achieve low speed communication using the serial.Serial class with /dev/tty0usb. As an example, channels.py and prologix_usb2gpib.py modules can be used to create a prologix usb to gpib converter object based on the serial.Serial communication channel object. The Prologix USB to GPIB converter uses the FTDI FT232BL USB-Serial (UART) IC to mimic a serial port connection to the GPIB bus, thus requiring the use of the pyserial module. Upon enumeration, the FT232 usb device is claimed by the kernel modules ftdi_sio and usbserial. You can see if these are loaded by running the lsmod command

Python and Libusb with Linux

  • Libusb provides user-space access to usb devices, and the PyUSB module provides access through Python. The libusb api can be used in lieu of PyUSB documentation. PyLibUSB seems to be similar but uses ctypes. Together with the libusb api, this is an attractive choice.

    • Examples

    • PyUSB can be used to communicate with the prologix device as well, although you have to know much about how the microcontroller uses the IO stream from the FTDI USB chip. The program prologix_pyusb.py finds and claims interface 0 of configuration 1. Note that interface needs to be released from the kernel module that initially claimed the device upon enumeration, presumably ftdi_sio. Also, create or modify /etc/udev/rules.d/11-prologix.rules with GROUP='users' and MODE='0666' so that all users can open the device.

Other Dynamic Libraries, Libusb and Python

  • Libftdi uses libusb to talk to FTDI FT232BM/245BM, FT2232C/D and FT232/245R controllers. This is the open-source version of FTDIs libftd2xx. There is said to be a Python module.
  • The LabJack family of USB analog and digital IO devices uses a custom dynamic library to communicate through libusb. Make sure the file /etc/udev/rules.d/10-labjack.rules has GROUP='users' and MODE='0666' so that all users can open the device. With the LabJack disconnected, reload the udev rules using 'udevadm control --reload-rules'. Also, download the source code for exodriver from labjack.com/support and follow the simple installation instructions. Under Linux, the library liblabjack.so (actually a link to the real library liblabjack.so.2.0.1) is in /usr/local/lib, an unusual location. If the 'import LabJackPython' line in a program results in the error 'could not load LabJackUSB driver', do the following. In /etc/ld.so.conf.d create the file labjack.conf. This file has only one line: /usr/local/lib . Then as root, run ldconfig. If in doubt, run 'ldconfig -v | grep labjack', and you should see a statement about liblabjack.so.

Other Dynamic Libraries And Libusb But No Python

  • The I2C Tiny USB Project provides a USB interface to an I2C port using the Atmel attiny45.
  • The USB Tiny ISP project provides a USB interface to an SPI port using the Atmel ATTINY2313-20PU.