Jump to content

Search the Community

Showing results for tags 'ubuntu'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Test and Measurement
    • Measurement Computing (MCC)
    • Add-on Boards
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • LabVIEW
    • FRC
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions
    • Archived

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 3 results

  1. Hello, i have a MiniLab-1008 but i get the error: Error: No DAQ devices found when i execute lsusb i get: Bus 001 Device 006: ID 09db:0075 Measurement Computing Corp. MiniLab 1008 but when i execute this in python3.8 from uldaq import (get_daq_device_inventory, DaqDevice, InterfaceType, AiInputMode, Range, AInFlag) get_daq_device_inventory(InterfaceType.USB) i get->[] so uldaq seems to be unable to find the device, but the computer finds the usb device i am using ubuntu 20.04, libuldaq-1.2.1 from https://github.com/mccdaq/uldaq/ uldaq 1.2.3 from https://pypi.org/project/uldaq/ python3.8 the MiniLab-1008 should be supported https://www.mccdaq.com/PDFs/Manuals/Linux-hw.pdf please help me regards Tristan
  2. Hi all! I'm running Ubuntu 20.04.1 LTS on ryzen 1700 with B350 chipset. When running waveforms (3.14.3, adept 2.20.2) after selecting device in Device Manager the application hangs for a while and show error box The LED on AD2 doesn't start blinking. However if I use "Force programming" from context menu (whatever it does) the error message is the same, but LED starts blinking. My Analog Discovery 2 is working perfectly fine on the same PC under Windows and on other computers under Windows (I don't heave another Linux machine available). It also was working some time ago, probably before updating from Ubuntu 19 or something like that (I'm not sure now - it was a few months ago). I did try different USB cables, different ports (different USB controllers too) and using external power supply for AD2, though I really don't think it's hardware issue as it works on the same machine on Windows. There are no errors in dmesg: [ 4535.196219] usb 1-2: USB disconnect, device number 27 [ 4537.393789] usb 1-2: new high-speed USB device number 28 using xhci_hcd [ 4537.564412] usb 1-2: New USB device found, idVendor=0403, idProduct=6014, bcdDevice= 9.00 [ 4537.564417] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4537.564420] usb 1-2: Product: Digilent USB Device [ 4537.564422] usb 1-2: Manufacturer: Digilent [ 4537.564424] usb 1-2: SerialNumber: 210321AD5BE1 [ 4537.576482] ftdi_sio 1-2:1.0: FTDI USB Serial Device converter detected [ 4537.576527] usb 1-2: Detected FT232H [ 4537.587553] usb 1-2: FTDI USB Serial Device converter now attached to ttyUSB0 [ 4537.604594] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [ 4537.604617] ftdi_sio 1-2:1.0: device disconnected Disconnect, I suspect, is because of dftdrvdtch which probably reconfigures the FTDI device thus disabling virtual serial port. Any ideas what might be the problem here?
  3. I have generated the bit file from Vivado 18.2 which is installed in windows PC. Now I am trying to generate the SD card image boot file (.bin and .ub files) from petalinux 18.2 installed in a seperate linux PC. I have gone through the ug1144, but I am not able to figure out how to generate. Please share the point wise steps. its very urgent. Thanks in advance.
  • Create New...