Recent changes to feature-requests

ARM32: SDK3.1.102 & LibUsbDotNet

2020-07-03T05:04:12.032000Z

dotnet msbuild LibUsbDotNet.sln under ubuntu yields the following errors:

/home/ubuntu/dotnet/dotnet/sdk/3.1.102/Microsoft.Common.CurrentVersion.targets(1175,5): error MSB3644: The reference assemblies for .NETFramework,Version=v4.5 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework Developer Packs at https://aka.ms/msbuild/developerpacks [/home/ubuntu/LibUsbDotNet/src/Examples/Show.Info/Show.Info.csproj]
/home/ubuntu/dotnet/dotnet/sdk/3.1.102/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(234,5): error NETSDK1004: Assets file '/home/ubuntu/LibUsbDotNet/src/LibUsbDotNet.Generator/obj/project.assets.json' not found. Run a NuGet package restore to generate this file. [/home/ubuntu/LibUsbDotNet/src/LibUsbDotNet.Generator/LibUsbDotNet.Generator.csproj]

The hints point to v4.5 of .Net needed for LibUsbDotNet.

Do I need to find a version that is suited for sdk 3.1.102?

I am at an "M-pass".

Support for Xamarin/Android

2014-11-10T11:39:19.920000Z

LibUSB supports Android and it would be great if I could develop in C# based on Xamarin.
I successfully built LibUSB following these intructions: https://github.com/libusb/libusb/tree/master/android
I'm now looking into the LibUSB.NET code to find what's useful and what's not. It's hard to remove dependencies (like Windows Forms) without breaking everything.
Thanks!

Add (cross-platform) ability to open a device from a DeviceNotify event

2013-11-11T18:15:00.914000Z

I have found myself needing to adapt some code that communicates with USB devices under Win32 to work under OS X, and LibUsbDotNet seems like a godsend. There are a couple of problem points, however:

(1) Our software will need to control 8-16 identical devices. Furthermore, like many devices that originally used serial I/O, the manufacturer has neglected to populate the Serial Number field in the USB descriptor. This means the devices are nearly impossible to tell apart.

(2) Under Win32, opening the device is easy -- LibUsbDevice.Open will do the trick. However, there is no equivalent for MonoUsbDevice; furthermore, there is no information in the IUsbDeviceNotifyInfo interface that uniquely correlates it with a UsbRegistry object under OS X; the ill-defined SymbolicName property is blank.

I have created a patch that does the following:

(1) Adds an (abstract) DevicePath property to the UsbRegistry and UsbDevice classes.
(2) Adds an "Open" method to the IUsbDeviceNotifyInfo interface, to allow code using the DeviceNotify mechanism to directly access the device it received the notification about.

Add double buffering to endpoint reader

2011-03-28T21:36:28Z

It would be nice to add double-buffering to the endpoint reader so that data can continue to be collected while handling the DataReceived event.

Add double buffering to endpoint reader

2011-03-28T19:39:11Z

It would be nice to add double-buffering to the endpoint reader so that data can continue to be collected while handling the DataReceived event.

Add control endpoint transfer timeout option to calls

2011-03-26T23:53:36Z

It would be nice to add a timeout argument to the various implementations of the control endpoint read/write calls. That way the default value can be overridden. Please reference https://sourceforge.net/apps/phpbb/libusbdotnet/viewtopic.php?f=3&t=72.

Adding application config to libusbdotnet

2010-12-02T18:47:40Z

It would be nice if you could add an application config (called LibUsbDotNet.dll.config or just an example of that file) to the library with the following content:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<dllmap os="linux" dll="libusb-1.0.dll" target="libusb-1.0.so.0"/>
</configuration>

With that file it's no more required to add a symlink into the application directory to libusb-1.0.0 (ln -s /usr/lib/libusb-1.0.so.0 libusb-1.0.so)

Async control transfer support

2010-04-27T21:55:18Z

LibUsbDotNet doesn't directly support async control transfers. With v.2.2.5 the only way to achieve this is by using the low-level MonoLibUsb api directly (libusb-1.0)

Isochronous transfer support (libusb-win32)

2010-04-27T21:49:07Z

LibUsbDotNet doesn't implement the function need to support isochronous transfers when using it with libusb-win32.

InfoConfig.Extra

2008-08-19T12:00:08Z

Namespace: LibUsbDotNet.Usb.Info.InfoConfig
Property Name: Extra
Typ: byte[]

I expect the complete Configuration Descriptor (with other Descriptors inside) in this array.
At the moment I can not use it, because extra is always null. Will never been initialized.

I don't know where the Problem is.

best regards

Markus Schütterle