Instrustar ISDS205A USB Oscilloscope Linux Driver

• Instrustar ISDS205A USB Oscilloscope Linux Driver
  Posted by KSP on 26 Jan, 2022 16:00
• Hi All,
  
  I've got an IDS205A USB oscilloscope, and I've been playing with the Instrustar SDK at

  Code: [Select]

  https://github.com/instrustar-dev/SDK

  attempting to get their Linux example working. After raising a bug regarding their header file, they quickly updated the repo and I now have code which compiles and runs, but it does not see any devices attached.
  
  The scope is recognised by lsusb  and dmesg but the example program just can't find it. I've added udev rules, run as root but still no joy. The program initialises the library just fine, but as soon as it tries to make a function call to check if the device is available the program halts.
  
  The github repo states it was tested on Ubuntu, and I'm using Fedora 35, but other than that I've done everything as instructed.
  
  Anyone had any joy with this?
• #1 Reply
  Posted by paf on 26 Jan, 2022 19:41
• It does not work, and even if it worked, it would not be advisable.
  
  By their instructions:
  
  

  • you need to compile their version of libusb
  • you overwrite your Linux libraries with their versions
  • when the libraries have different names they have the name on file, instead of a symbolic link

  
  You can run it without messing with the libraries on your system like this:
  
  

  Code: [Select]

  LD_LIBRARY_PATH=../SharedLibrary/Linux/X64/Release/  ./DllTest 

  
  Running it this way (as root) it gives these messages:
  
  

  Code: [Select]

  Vdso Test...
  InitDll..............
  **********UsbDevAddRemoveCallBack DEVICE_NOTICE_ID=1**********
  **********CreateOscDevice 0**********
  **********SetDevNoticeCallBack**********
  **********SetDataReadyCallBack**********

  
  Then it does nothing.
  Removing the USB cable gives
  
  

  Code: [Select]

  **********UsbDevAddRemoveCallBack DEVICE_NOTICE_ID=2**********
  **********DestoryOscDevice Success**********
  **********DestoryDdsDevice**********
  **********DestoryIODevice**********
  DevNoticeRemoveCallBack
  **********DestoryOscDevice Success**********
  **********DestoryDdsDevice**********
  

  
  This was tested on a Debian (antiX) Linux machine.
  
  
   
• #2 Reply
  Posted by KSP on 26 Jan, 2022 19:51
• Quote from: paf on 26 Jan, 2022 19:41

  It does not work, and even if it worked, it would not be advisable.
  
  

  
  Thanks for your response, at least it’s not just me!
  
  I tried it with their libusb and my system’s libusb, got the same result with both. The output I get is the same as you’ve shown. I inserted some debug lines into the code to check device status etc., and it showed that the reason it pauses at that particular point is because it can’t talk to the device for whatever reason.
  
  It just seems so cumbersome to have an entire windows VM solely for my scope!
• #3 Reply
  Posted by simba15 on 26 Jan, 2022 21:14
• I think there was some requests to add the Iisds205a to Sigrok. ( it shows "in progress" currently).
  
  There were also a fair number of requests to add the device to OpenHantek ( from the user Gyro).
  
  It would be great to have some open source software for this device as its not bad for the price.
  
  Tristan.
• #4 Reply
  Posted by KSP on 27 Jan, 2022 07:47
• Quote from: simba15 on 26 Jan, 2022 21:14

  I think there was some requests to add the Iisds205a to Sigrok. ( it shows "in progress" currently).
  

  
  Yes I noticed that, it would be really handy if it was added to Sigrok. Though from what I can tell it has been 'in progress' for a couple years now, so no telling when it will actually be complete