Menu
▾
▴
libusb-win32-devel
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
(27) |
Dec
(9) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(2) |
Feb
(19) |
Mar
(13) |
Apr
(15) |
May
(11) |
Jun
(17) |
Jul
(31) |
Aug
(45) |
Sep
(10) |
Oct
(40) |
Nov
(39) |
Dec
(45) |
| 2005 |
Jan
(113) |
Feb
(45) |
Mar
(38) |
Apr
(53) |
May
(11) |
Jun
(42) |
Jul
(56) |
Aug
(50) |
Sep
(32) |
Oct
(32) |
Nov
(47) |
Dec
(22) |
| 2006 |
Jan
(19) |
Feb
(32) |
Mar
(40) |
Apr
(40) |
May
(41) |
Jun
(44) |
Jul
(37) |
Aug
(51) |
Sep
(30) |
Oct
(30) |
Nov
(51) |
Dec
(20) |
| 2007 |
Jan
(7) |
Feb
(20) |
Mar
(17) |
Apr
(67) |
May
(13) |
Jun
(73) |
Jul
(16) |
Aug
(58) |
Sep
(29) |
Oct
(5) |
Nov
(74) |
Dec
(9) |
| 2008 |
Jan
(17) |
Feb
(12) |
Mar
(65) |
Apr
(22) |
May
(40) |
Jun
(32) |
Jul
(11) |
Aug
(8) |
Sep
(3) |
Oct
(41) |
Nov
(34) |
Dec
(12) |
| 2009 |
Jan
(44) |
Feb
(33) |
Mar
(16) |
Apr
(109) |
May
(11) |
Jun
(22) |
Jul
(21) |
Aug
(37) |
Sep
(5) |
Oct
(23) |
Nov
(7) |
Dec
(7) |
| 2010 |
Jan
(36) |
Feb
(40) |
Mar
(35) |
Apr
(45) |
May
(42) |
Jun
(104) |
Jul
(135) |
Aug
(50) |
Sep
(65) |
Oct
(110) |
Nov
(129) |
Dec
(75) |
| 2011 |
Jan
(105) |
Feb
(48) |
Mar
(93) |
Apr
(166) |
May
(169) |
Jun
(188) |
Jul
(106) |
Aug
(33) |
Sep
(85) |
Oct
(46) |
Nov
(102) |
Dec
(105) |
| 2012 |
Jan
(81) |
Feb
(115) |
Mar
(56) |
Apr
(93) |
May
(56) |
Jun
(77) |
Jul
(88) |
Aug
(52) |
Sep
(72) |
Oct
(16) |
Nov
(70) |
Dec
(70) |
| 2013 |
Jan
(23) |
Feb
(85) |
Mar
(38) |
Apr
(48) |
May
(40) |
Jun
(49) |
Jul
(33) |
Aug
(28) |
Sep
(66) |
Oct
(28) |
Nov
(28) |
Dec
(16) |
| 2014 |
Jan
(33) |
Feb
(58) |
Mar
(17) |
Apr
(50) |
May
(16) |
Jun
(24) |
Jul
(19) |
Aug
(32) |
Sep
(10) |
Oct
(10) |
Nov
(4) |
Dec
(10) |
| 2015 |
Jan
(11) |
Feb
(2) |
Mar
(4) |
Apr
(14) |
May
(1) |
Jun
(6) |
Jul
(16) |
Aug
(29) |
Sep
(6) |
Oct
(26) |
Nov
(10) |
Dec
|
| 2016 |
Jan
|
Feb
(20) |
Mar
(6) |
Apr
|
May
(3) |
Jun
(3) |
Jul
|
Aug
(16) |
Sep
(6) |
Oct
|
Nov
(15) |
Dec
|
| 2017 |
Jan
(1) |
Feb
(2) |
Mar
(4) |
Apr
|
May
(1) |
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2018 |
Jan
|
Feb
(8) |
Mar
(10) |
Apr
(16) |
May
|
Jun
(15) |
Jul
|
Aug
(3) |
Sep
(19) |
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
(5) |
May
|
Jun
|
Jul
(7) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
(5) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(3) |
Aug
|
Sep
(6) |
Oct
(2) |
Nov
(4) |
Dec
|
| 2022 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
(5) |
Feb
(1) |
Mar
|
Apr
(3) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
(3) |
Mar
(1) |
Apr
(1) |
May
(11) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
(3) |
Dec
|
|
From: Pradeepa S. <pra...@gm...> - 2016-11-24 08:48:16
|
Hello All, I have been using libusbK with WinUSB for a long time now. Recently we found out a bug which had slipped away from us and has been in the source for 2 years. The issue is, when we call ReadPipe to read a bulk in endpoint sometimes we get a timeout. When we investigated more we found out that the issue comes only when our reply data amount is a multiple of 64 bytes. Nevertheless, when we get a timeout if I checked the transferred byte amount and the content, it has all the data the device had committed. I'm a bit perplexed at the moment due to this behavior. We have a STM32F4 IC in the device. It seems like it's committing all the data to the USB controller properly. Is there any one who had faced something similar? Or if this is a known issue can someone suggest a workaround? Thank you, Best Regards, Pradeepa Senanayake. |
|
From: Xiaofan C. <xia...@gm...> - 2016-11-19 02:23:06
|
On Fri, Nov 18, 2016 at 8:29 PM, armin davatgaran <arm...@gm...> wrote: > Hello > Is there any documentation for libusbk c# binding implementation? Unfortunately no. You can try to read the codes and examples. https://github.com/mcuee/usb-travis/tree/master/libusbK/bindings -- Xiaofan |
|
From: armin d. <arm...@gm...> - 2016-11-18 12:29:21
|
Hello Is there any documentation for libusbk c# binding implementation? |
|
From: Xiaofan C. <xia...@gm...> - 2016-11-18 11:49:59
|
On Fri, Nov 18, 2016 at 4:12 AM, Chris E <sp...@gm...> wrote: > Ahh. I had trouble even using the precompiled DLL at all in VS2015. Try > 2013. You might need to search a bit to find the installer. Microsoft > loves redirecting people to VS2015. > > I believe that the DLL was compiled with VS2008!!! The VS solution is of version VS2008. https://github.com/mcuee/usb-travis/blob/master/libusbK/libusbK.sln The binary package (including libusbk.sys, libusbk.dll, examples, installers, etc) is built with WDK 7600.16385.1 which has its own compiler. Ref: https://github.com/mcuee/usb-travis/blob/master/libusbK/make.cfg That WDK can be downloaded here. https://www.microsoft.com/en-us/download/details.aspx?id=11800 -- Xiaofan |
|
From: Chris E <sp...@gm...> - 2016-11-17 20:12:18
|
Ahh. I had trouble even using the precompiled DLL at all in VS2015. Try 2013. You might need to search a bit to find the installer. Microsoft loves redirecting people to VS2015. I believe that the DLL was compiled with VS2008!!! -Chris On Nov 18, 2016 12:04 AM, "armin davatgaran" <arm...@gm...> wrote: > I use vs2015. > > On Thu, Nov 17, 2016 at 3:38 PM, <libusb-win32-devel-request@li > sts.sourceforge.net> wrote: > >> Send Libusb-win32-devel mailing list submissions to >> lib...@li... >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel >> or, via email, send a message with subject or body 'help' to >> lib...@li... >> >> You can reach the person managing the list at >> lib...@li... >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Libusb-win32-devel digest..." >> >> >> Today's Topics: >> >> 1. libusbk 3.0.7 c example codes builing problem (armin davatgaran) >> 2. Re: libusbk 3.0.7 c example codes builing problem (Chris E) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Thu, 17 Nov 2016 13:29:09 +0330 >> From: armin davatgaran <arm...@gm...> >> Subject: [Libusb-win32-devel] libusbk 3.0.7 c example codes builing >> problem >> To: lib...@li... >> Message-ID: >> <CA+...@ma... >> ail.com> >> Content-Type: text/plain; charset="utf-8" >> >> Hello >> Libusbk examples in C:\libusbK-dev-kit\examples directory can't be build, >> there are total number of 814 errors like: link1120 unresolved externals. >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> >> ------------------------------ >> >> Message: 2 >> Date: Thu, 17 Nov 2016 21:50:56 +1100 >> From: Chris E <sp...@gm...> >> Subject: Re: [Libusb-win32-devel] libusbk 3.0.7 c example codes >> builing problem >> To: lib...@li... >> Message-ID: >> <CAL...@ma... >> ail.com> >> Content-Type: text/plain; charset="utf-8" >> >> What are you using to build them? I don't remember having any issues with >> Visual Studio 2013. >> >> On 17 November 2016 at 20:59, armin davatgaran <arm...@gm... >> > >> wrote: >> >> > Hello >> > Libusbk examples in C:\libusbK-dev-kit\examples directory can't be >> build, >> > there are total number of 814 errors like: link1120 unresolved >> externals. >> > >> > >> > ------------------------------------------------------------ >> > ------------------ >> > >> > _______________________________________________ >> > Libusb-win32-devel mailing list >> > Lib...@li... >> > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel >> > >> > >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> >> ------------------------------ >> >> ------------------------------------------------------------ >> ------------------ >> >> >> ------------------------------ >> >> _______________________________________________ >> Libusb-win32-devel mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel >> >> >> End of Libusb-win32-devel Digest, Vol 118, Issue 2 >> ************************************************** >> > > > ------------------------------------------------------------ > ------------------ > > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > > |
|
From: armin d. <arm...@gm...> - 2016-11-17 13:02:05
|
I use vs2015. On Thu, Nov 17, 2016 at 3:38 PM, < lib...@li...> wrote: > Send Libusb-win32-devel mailing list submissions to > lib...@li... > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > or, via email, send a message with subject or body 'help' to > lib...@li... > > You can reach the person managing the list at > lib...@li... > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Libusb-win32-devel digest..." > > > Today's Topics: > > 1. libusbk 3.0.7 c example codes builing problem (armin davatgaran) > 2. Re: libusbk 3.0.7 c example codes builing problem (Chris E) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 17 Nov 2016 13:29:09 +0330 > From: armin davatgaran <arm...@gm...> > Subject: [Libusb-win32-devel] libusbk 3.0.7 c example codes builing > problem > To: lib...@li... > Message-ID: > <CA+D-TNPHmWE2X6tX2GmCP_WufjQgBiLJxdMRbHjwp8i88Z1Qhg@ > mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hello > Libusbk examples in C:\libusbK-dev-kit\examples directory can't be build, > there are total number of 814 errors like: link1120 unresolved externals. > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > Message: 2 > Date: Thu, 17 Nov 2016 21:50:56 +1100 > From: Chris E <sp...@gm...> > Subject: Re: [Libusb-win32-devel] libusbk 3.0.7 c example codes > builing problem > To: lib...@li... > Message-ID: > <CALmGtgRPE2pHv0tFgty084A6hAfi4vDrNE+Vzp42oofBxnJwbw@mail. > gmail.com> > Content-Type: text/plain; charset="utf-8" > > What are you using to build them? I don't remember having any issues with > Visual Studio 2013. > > On 17 November 2016 at 20:59, armin davatgaran <arm...@gm...> > wrote: > > > Hello > > Libusbk examples in C:\libusbK-dev-kit\examples directory can't be build, > > there are total number of 814 errors like: link1120 unresolved externals. > > > > > > ------------------------------------------------------------ > > ------------------ > > > > _______________________________________________ > > Libusb-win32-devel mailing list > > Lib...@li... > > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > ------------------------------------------------------------ > ------------------ > > > ------------------------------ > > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > > > End of Libusb-win32-devel Digest, Vol 118, Issue 2 > ************************************************** > |
|
From: Chris E <sp...@gm...> - 2016-11-17 10:51:03
|
What are you using to build them? I don't remember having any issues with Visual Studio 2013. On 17 November 2016 at 20:59, armin davatgaran <arm...@gm...> wrote: > Hello > Libusbk examples in C:\libusbK-dev-kit\examples directory can't be build, > there are total number of 814 errors like: link1120 unresolved externals. > > > ------------------------------------------------------------ > ------------------ > > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > > |
|
From: armin d. <arm...@gm...> - 2016-11-17 09:59:16
|
Hello Libusbk examples in C:\libusbK-dev-kit\examples directory can't be build, there are total number of 814 errors like: link1120 unresolved externals. |
|
From: Xiaofan C. <xia...@gm...> - 2016-11-05 02:29:37
|
I closed libusb github ticket #224 since it is not really part of libusb project. On the other hand, maybe there are people who are interested in .Net Core wrapper for libusb. Ticket: https://github.com/libusb/libusb/issues/224 .Net Core https://www.microsoft.com/net/core -- Xiaofan |
|
From: Jeff B. <jef...@in...> - 2016-09-15 05:05:11
|
> I'm trying to get Network UPS Tools (NUT) working on my Hyper-V server and I'm running into libUSB problems. > > Specifically, when I run this command: > > usbhid-ups.exe -D -a ups > > I get the output shown below. > > 0.061189 libusb_get_report: libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning. > 0.061189 Can't retrieve Report 89: Input/output error [A device attached to the system is not functioning. ] > 0.061189 Path: UPS.ff8600fd, Type: Input, ReportID: 0x89, Offset: 0, Size: 8 > > 0.061189 libusb_get_report: libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning. > 0.061189 Can't retrieve Report 90: Input/output error [A device attached to the system is not functioning. ] > 0.061189 Path: UPS.ff8600fc, Type: Output, ReportID: 0x90, Offset: 0, Size: 8 It turns out that this is a vendor-specific issue, not a problem with libUSB. http://lists.alioth.debian.org/pipermail/nut-upsuser/2016-September/010296.html Thanks, Jeff Bowman Fairbanks, Alaska |
|
From: Jeff B. <jef...@in...> - 2016-09-14 15:08:23
|
> On the other hand, does it work under a real Windows machine, not a Hyper-V > virtual machine? I'm working directly on the Hyper-V host, not within a VM. CLI only, no Desktop GUI. |
|
From: Jeff B. <jef...@in...> - 2016-09-14 15:04:44
|
> I am not so sure why NUT still use libusb-win32 for HID device. > That is not recommended. They should use HIDAPI instead. Is there anything I can do about that, as only a user of the tool? I'm guessing not. |
|
From: Xiaofan C. <xia...@gm...> - 2016-09-14 12:57:06
|
On Wed, Sep 14, 2016 at 8:55 PM, Xiaofan Chen <xia...@gm...> wrote: > On Tue, Sep 13, 2016 at 7:46 PM, Jeff Bowman <jef...@in...> wrote: >> I'm trying to get Network UPS Tools (NUT) working on my >> Hyper-V server and I'm running into libUSB problems. >> >> Specifically, when I run this command: >> >> usbhid-ups.exe -D -a ups >> >> I get the output shown below. >> >> How can I got about troubleshooting this? The error message doesn't >> seem to provide much information. My UPS is detected, however, >> so there does appear to be basic communication occurring. > > I am not so sure why NUT still use libusb-win32 for HID device. > That is not recommended. They should use HIDAPI instead. On the other hand, does it work under a real Windows machine, not a Hyper-V virtual machine? -- Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2016-09-14 12:55:41
|
On Tue, Sep 13, 2016 at 7:46 PM, Jeff Bowman <jef...@in...> wrote: > I'm trying to get Network UPS Tools (NUT) working on my > Hyper-V server and I'm running into libUSB problems. > > Specifically, when I run this command: > > usbhid-ups.exe -D -a ups > > I get the output shown below. > > How can I got about troubleshooting this? The error message doesn't > seem to provide much information. My UPS is detected, however, > so there does appear to be basic communication occurring. I am not so sure why NUT still use libusb-win32 for HID device. That is not recommended. They should use HIDAPI instead. -- Xiaofan |
|
From: Jeff B. <jef...@in...> - 2016-09-13 15:21:36
|
I'm trying to get Network UPS Tools (NUT) working on my Hyper-V server and I'm running into libUSB problems. Specifically, when I run this command: usbhid-ups.exe -D -a ups I get the output shown below. How can I got about troubleshooting this? The error message doesn't seem to provide much information. My UPS is detected, however, so there does appear to be basic communication occurring. Thanks, Jeff Bowman Fairbanks, Alaska -- Output ------------------------------------------------------------ 0.000000 debug level is '1' 0.000000 upsdrv_initups... 0.000000 interrupt pipe disabled (add 'pollonly' flag to 'ups.conf' to get rid of this message) 0.061189 Using subdriver: APC HID 0.95 0.061189 Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 2 0.061189 Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID: 0x02, Offset: 0, Size: 8, Value: 3 0.061189 Path: UPS.PowerSummary.iManufacturer, Type: Feature, ReportID: 0x03, Offset: 0, Size: 8, Value: 1 0.061189 Path: UPS.PowerSummary.iOEMInformation, Type: Feature, ReportID: 0x04, Offset: 0, Size: 8, Value: 1 0.061189 Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, ReportID: 0x05, Offset: 0, Size: 8, Value: 4 0.061189 Path: UPS.PowerSummary.Rechargeable, Type: Feature, ReportID: 0x06, Offset: 0, Size: 8, Value: 1 0.061189 Path: UPS.PowerSummary.CapacityMode, Type: Feature, ReportID: 0x06, Offset: 8, Size: 8, Value: 2 0.061189 Path: UPS.PowerSummary.DesignCapacity, Type: Feature, ReportID: 0x0e, Offset: 0, Size: 8, Value: 100 0.061189 Path: UPS.PowerSummary.FullChargeCapacity, Type: Feature, ReportID: 0x0e, Offset: 8, Size: 8, Value: 100 0.061189 Path: UPS.PowerSummary.RemainingCapacity, Type: Input, ReportID: 0x0c, Offset: 0, Size: 8, Value: 100 0.061189 Path: UPS.PowerSummary.RemainingCapacity, Type: Feature, ReportID: 0x0c, Offset: 0, Size: 8, Value: 100 0.061189 Path: UPS.PowerSummary.CapacityGranularity1, Type: Feature, ReportID: 0x10, Offset: 0, Size: 8, Value: 1 0.061189 Path: UPS.PowerSummary.CapacityGranularity2, Type: Feature, ReportID: 0x10, Offset: 8, Size: 8, Value: 1 0.061189 Path: UPS.PowerSummary.WarningCapacityLimit, Type: Feature, ReportID: 0x0f, Offset: 0, Size: 8, Value: 50 0.061189 Path: UPS.PowerSummary.RemainingCapacityLimit, Type: Feature, ReportID: 0x11, Offset: 0, Size: 8, Value: 10 0.061189 Path: UPS.PowerSummary.ManufacturerDate, Type: Feature, ReportID: 0x09, Offset: 0, Size: 16, Value: 18094 0.061189 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, ReportID: 0x0d, Offset: 0, Size: 16, Value: 4200 0.061189 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, ReportID: 0x0d, Offset: 0, Size: 16, Value: 4200 0.061189 Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature, ReportID: 0x12, Offset: 0, Size: 16, Value: -1 0.061189 Path: UPS.PowerSummary.DelayBeforeReboot, Type: Feature, ReportID: 0x13, Offset: 0, Size: 24, Value: -1 0.061189 Path: UPS.PowerSummary.RemainingTimeLimit, Type: Input, ReportID: 0x08, Offset: 0, Size: 16, Value: 120 0.061189 Path: UPS.PowerSummary.RemainingTimeLimit, Type: Feature, ReportID: 0x08, Offset: 0, Size: 16, Value: 120 0.061189 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x0a, Offset: 0, Size: 16, Value: 24 0.061189 Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x0b, Offset: 0, Size: 16, Value: 27 0.061189 Path: UPS.PowerSummary.AudibleAlarmControl, Type: Input, ReportID: 0x14, Offset: 0, Size: 8, Value: 1 0.061189 Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature, ReportID: 0x14, Offset: 0, Size: 8, Value: 1 0.061189 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input, ReportID: 0x07, Offset: 0, Size: 1, Value: 0 0.061189 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature, ReportID: 0x07, Offset: 0, Size: 1, Value: 0 0.061189 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, ReportID: 0x07, Offset: 1, Size: 1, Value: 0 0.061189 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Feature, ReportID: 0x07, Offset: 1, Size: 1, Value: 0 0.061189 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x07, Offset: 2, Size: 1, Value: 1 0.061189 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x07, Offset: 2, Size: 1, Value: 1 0.061189 Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Input, ReportID: 0x07, Offset: 3, Size: 1, Value: 1 0.061189 Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Feature, ReportID: 0x07, Offset: 3, Size: 1, Value: 1 0.061189 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x07, Offset: 4, Size: 1, Value: 0 0.061189 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x07, Offset: 4, Size: 1, Value: 0 0.061189 Path: UPS.PowerSummary.PresentStatus.ShutdownRequested, Type: Input, ReportID: 0x07, Offset: 5, Size: 1, Value: 0 0.061189 Path: UPS.PowerSummary.PresentStatus.ShutdownRequested, Type: Feature, ReportID: 0x07, Offset: 5, Size: 1, Value: 0 0.061189 Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Input, ReportID: 0x07, Offset: 6, Size: 1, Value: 0 0.061189 Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Feature, ReportID: 0x07, Offset: 6, Size: 1, Value: 0 0.061189 Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Input, ReportID: 0x07, Offset: 7, Size: 1, Value: 0 0.061189 Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Feature, ReportID: 0x07, Offset: 7, Size: 1, Value: 0 0.061189 Path: UPS.PowerSummary.PresentStatus.CommunicationLost, Type: Input, ReportID: 0x07, Offset: 8, Size: 1, Value: 0 0.061189 Path: UPS.PowerSummary.PresentStatus.CommunicationLost, Type: Feature, ReportID: 0x07, Offset: 8, Size: 1, Value: 0 0.061189 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input, ReportID: 0x07, Offset: 9, Size: 1, Value: 0 0.061189 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Feature, ReportID: 0x07, Offset: 9, Size: 1, Value: 0 0.061189 Path: UPS.PowerSummary.PresentStatus.Overload, Type: Input, ReportID: 0x07, Offset: 10, Size: 1, Value: 0 0.061189 Path: UPS.PowerSummary.PresentStatus.Overload, Type: Feature, ReportID: 0x07, Offset: 10, Size: 1, Value: 0 0.061189 Path: UPS.PowerSummary.PresentStatus.VoltageNotRegulated, Type: Input, ReportID: 0x07, Offset: 11, Size: 1, Value: 0 0.061189 Path: UPS.PowerSummary.PresentStatus.VoltageNotRegulated, Type: Feature, ReportID: 0x07, Offset: 11, Size: 1, Value: 0 0.061189 Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Input, ReportID: 0x07, Offset: 12, Size: 1, Value: 0 0.061189 Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Feature, ReportID: 0x07, Offset: 12, Size: 1, Value: 0 0.061189 libusb_get_report: libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning. 0.061189 Can't retrieve Report 89: Input/output error [A device attached to the system is not functioning. ] 0.061189 Path: UPS.ff8600fd, Type: Input, ReportID: 0x89, Offset: 0, Size: 8 0.061189 libusb_get_report: libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning. 0.061189 Can't retrieve Report 90: Input/output error [A device attached to the system is not functioning. ] 0.061189 Path: UPS.ff8600fc, Type: Output, ReportID: 0x90, Offset: 0, Size: 8 0.061189 Path: UPS.ff8600f1, Type: Feature, ReportID: 0x96, Offset: 0, Size: 8, Value: 0 0.061189 Path: UPS.ff8600f7, Type: Feature, ReportID: 0x8d, Offset: 0, Size: 8, Value: 0 0.061189 Path: UPS.ff8600f6, Type: Feature, ReportID: 0x8e, Offset: 0, Size: 8, Value: 0 0.061189 Path: UPS.ff8600f3, Type: Feature, ReportID: 0x93, Offset: 0, Size: 8, Value: 1 0.061189 Path: UPS.ff8600f2, Type: Feature, ReportID: 0x94, Offset: 0, Size: 8, Value: 1 0.061189 Path: UPS.ff8600f4, Type: Feature, ReportID: 0x92, Offset: 0, Size: 8, Value: 3 0.061189 Detected a UPS: American Power Conversion /Smart-UPS C 1000 FW:UPS 10.0 / ID=1005 ---------------------------------------------------------------------- |
|
From: Xiaofan C. <xia...@gm...> - 2016-08-25 12:35:39
|
On Thu, Aug 25, 2016 at 9:45 AM, Chris E <sp...@gm...> wrote: > There's no error message, it just won't connect to the device > when debugging is enabled. I see. I remember people reporting similar problems for libusb Windows but I could not find the link. It may not be specific to VS2015 but other VS versions. You can try the debug version of the library and use DebugView to print the message generated by the library. > Do you have any tips for building from source? I tried this but it > complained about missing headers. Hmm, you should just build the dll and lib and not the driver. Does that work? I do not have VS2015 installed right now. For the driver building, you need to have WDK installed. And I think you can use older version of WDK. -- Xiaofan |
|
From: Chris E <sp...@gm...> - 2016-08-25 01:45:10
|
There's no error message, it just won't connect to the device when debugging is enabled. Do you have any tips for building from source? I tried this but it complained about missing headers. ~Chris On 25 August 2016 at 11:40, Xiaofan Chen <xia...@gm...> wrote: > On Mon, Aug 22, 2016 at 12:29 PM, Chris E <sp...@gm...> wrote: > > As the above states, I'm just wondering which versions of Visual Studio > > LibusbK works best with. > > > > I seem to get slight errors in VS2013 (I suspect it's just my code), but > it > > won't work at all in VS2015. > > I'm using the x64 .dll and .lib. > > > > What is the error message? > > Please try to build libusbk.dll and libusbk.lib from the source code to > see if that helps or not. > > > -- > Xiaofan > > ------------------------------------------------------------ > ------------------ > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > |
|
From: Xiaofan C. <xia...@gm...> - 2016-08-25 01:40:17
|
On Mon, Aug 22, 2016 at 12:29 PM, Chris E <sp...@gm...> wrote: > As the above states, I'm just wondering which versions of Visual Studio > LibusbK works best with. > > I seem to get slight errors in VS2013 (I suspect it's just my code), but it > won't work at all in VS2015. > I'm using the x64 .dll and .lib. > What is the error message? Please try to build libusbk.dll and libusbk.lib from the source code to see if that helps or not. -- Xiaofan |
|
From: Chris E <sp...@gm...> - 2016-08-22 04:29:36
|
As the above states, I'm just wondering which versions of Visual Studio LibusbK works best with. I seem to get slight errors in VS2013 (I suspect it's just my code), but it won't work at all in VS2015. I'm using the x64 .dll and .lib. Thanks, ~Chris |
|
From: Xiaofan C. <xia...@gm...> - 2016-08-18 12:25:06
|
On Thu, Aug 18, 2016 at 8:22 PM, Xiaofan Chen <xia...@gm...> wrote:
> On Thu, Aug 18, 2016 at 9:54 AM, popear <col...@16...> wrote:
>> Thanks for your reply.
>> I'll paste the error message directly:)
>>
>> I installed the WinUSB driver with Zadg, and xusb works well without any
>> error.
>> But I got my program crashed after the libusb_claim_interface(dev_handle, 2)
>> return -12, which is LIBUSB_ERROR_NOT_SUPPORTED.
>> My code is like this:
>> libusb_init(NULL);
>> libusb_get_device_list(NULL, devs);
>> while ((dev = devs[i++]) != NULL )
>> {
>> mydev = libusb_get_device_address(dev);//OK
>> if (XX != mydev)
>> {
>> continue;
>> }
>> dev_handle = libusb_open_device_with_vid_pid(NULL, myvid, mypid);//OK
>> libusb_get_configuration(dev_handle, &config);//OK
>> libusb_calim_interface(dev_handle, myinterface);//return -12 and
>> crashed.
>> }
>> ...
>>
>> It's the right interface which claimed while using libusb-compat-0.1.
>> Is there any error in my code? Thanks.
>
>
> Please post the descriptor of your device. How do you install
> WinUSB driver? This seems to be a problem with driver installation.
>
>
> BTW, I do not think you use libusb-compat-0.1, rather you
> were using libusb-win32, and how did you install the driver
> there? Are you using the filter driver mode or device driver mode?
Please also post the debug message output from your
libusb-1.0 API based program. You can set the environmental
variable LIBUSB_DEBUG to 4 to print out all the debug message.
--
Xiaofan
|
|
From: Xiaofan C. <xia...@gm...> - 2016-08-18 12:22:11
|
On Thu, Aug 18, 2016 at 9:54 AM, popear <col...@16...> wrote:
> Thanks for your reply.
> I'll paste the error message directly:)
>
> I installed the WinUSB driver with Zadg, and xusb works well without any
> error.
> But I got my program crashed after the libusb_claim_interface(dev_handle, 2)
> return -12, which is LIBUSB_ERROR_NOT_SUPPORTED.
> My code is like this:
> libusb_init(NULL);
> libusb_get_device_list(NULL, devs);
> while ((dev = devs[i++]) != NULL )
> {
> mydev = libusb_get_device_address(dev);//OK
> if (XX != mydev)
> {
> continue;
> }
> dev_handle = libusb_open_device_with_vid_pid(NULL, myvid, mypid);//OK
> libusb_get_configuration(dev_handle, &config);//OK
> libusb_calim_interface(dev_handle, myinterface);//return -12 and
> crashed.
> }
> ...
>
> It's the right interface which claimed while using libusb-compat-0.1.
> Is there any error in my code? Thanks.
Please post the descriptor of your device. How do you install
WinUSB driver? This seems to be a problem with driver installation.
BTW, I do not think you use libusb-compat-0.1, rather you
were using libusb-win32, and how did you install the driver
there? Are you using the filter driver mode or device driver mode?
--
Xiaofan
|
|
From: michel <dia...@ya...> - 2016-08-17 19:30:15
|
Of course 1.0 api work under window ;) like Xiaofan said you may have to install some backend driver like winusb or libusbk for your device get you claim interface to succeed. It is strange that with some old compat version you can claim interface just for curiosity why do you need libusb_get_port_number ? give a look at usb_get_port_numbers instead for my own purpose i use libusb_get_device_address and libusb_get_bus_number to build a kind of "id" unique for a device also note that none of this call require to open the device nor claim interface. -- View this message in context: http://libusb.6.n5.nabble.com/libusb-claim-interface-failed-on-Windows7-tp5715986p5715989.html Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com. |
|
From: Xiaofan C. <xia...@gm...> - 2016-08-17 14:19:59
|
On Wed, Aug 17, 2016 at 4:44 PM, popear <col...@16...> wrote: > I got a failed message when using `xusb.exe myvid:mypid`, and it failed when > claiming interface 2. > It shows like this: > > <http://libusb.6.n5.nabble.com/file/n5715986/failed.png> The image is not clear. Please do not use image. Just copy paste the error message. > And usb_claim_interface is OK while using the libusb-compat-0.1.4 library. > But libusb-compat-0.1 API does not meet my requirement, I need to use > libusb1.0 API(libusb_get_port_number). > So, is it possible to use libusb1.0 API on Windows? The example is not > working well. > Anyone help? Thanks! Yes libusb works well under Windows. You should use WinUSB driver. You can install WinUSB driver using Zadig. > Sorry, I mean usb_claim_interface is OK while using libusb-win32 library, > which is in libusb-win32-bin-1.2.6.0.zip. -- Xiaofan |
|
From: Chris E <sp...@gm...> - 2016-08-14 00:41:01
|
Hi Saeed. Libusb is a library for the USB protocol. If you have control over the USB hardware (ie can send control, iso, bulk, interrupt packets), then you will want libusb. You mentioned USB to UART, though. Maybe your chip doesn't give full USB control and instead connects as a COM port? If it connects as a COM port, do not use libusb. Instead, just use serial commands. If you have MATLAB, try the serial() command. For other languages you'll need a library. In short: - If your chip gives you a USB protocol, use libusb. - If your chip gives you a serial (COM port) protocol, use serial commands. On 14 August 2016 at 03:55, saeed nowrozi <sae...@gm...> wrote: > Hi all > I under design a printer that a fpga spartan6 is main board and for > connection to PC ,I use a usb to uart controller(CY7C64225).now I can use > libusb for driver connection between fpga and PC? > I read befor for driver fpga to PC need to kernel driver so my question is > libusb need a extra code for my board or no? > for connect between Qt(windows7) and board any one have a example code? > I use a board that have driver but a lot of files but when I download > libusb have not is files.of course some files is special for any Ic ,now I > need special files .inf , .sys for my app? > sorry for poor English and a lot of question. > > ------------------------------------------------------------ > ------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > patterns at an interface-level. Reveals which users, apps, and protocols > are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning reports. http://sdm.link/zohodev2dev > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > > |
|
From: saeed n. <sae...@gm...> - 2016-08-13 17:55:11
|
Hi all I under design a printer that a fpga spartan6 is main board and for connection to PC ,I use a usb to uart controller(CY7C64225).now I can use libusb for driver connection between fpga and PC? I read befor for driver fpga to PC need to kernel driver so my question is libusb need a extra code for my board or no? for connect between Qt(windows7) and board any one have a example code? I use a board that have driver but a lot of files but when I download libusb have not is files.of course some files is special for any Ic ,now I need special files .inf , .sys for my app? sorry for poor English and a lot of question. |
50 messages has been excluded from this view by a project administrator.
