similar to: usb support

Dear Alexander Morozov, From the output of the command "ps -ef | grep wine", we can observe that the native Windows USB driver ICDUSB2.sys for the Sony IC Recorder gets loaded with winedevice.exe. enming 18814 18781 0 16:15 ? 00:00:00 C:\windows\system32\winedevice.exe ICDUSB2 However, Digital Voice Editor 3 (under Wine) simply would not detect the Sony IC Recorder. The

Dear Sirs, We appreciate your support and cooperation. Can you please kindly add our new USB-controller with productID 0X04 to NUT compatible list. Updated USB-controller compatible with previous version which is supported by your usbhid-ups driver. Detailed information regarding new POWERCOM communication protocol you could download via link

Hello All, Sorry for the long post, I'm just trying to give as much info as I have about the problem(s) ... Recently I've tried to port NUT to the hardware router Asus WL-500g Deluxe (http://wiki.openwrt.org/OpenWrtDocs/Hardware/Asus/WL500GD), that runs OpenWRT Linux distribution (http://www.openwrt.org) based on Linux 2.4.30 kernel, in order to support my Powerware 5110 UPS (through USB

Dear Sirs, First of all I would like to thank you for support PCM product in your project. Kindly please be informed that POWERCOM launch new USB-controller with productID 0X04. Updated USB-controller compatible with previous version which supported by your usbhid-ups driver. There is added some command and changed idProduct. Vendor ID stay the same 0X0d9f without changes. Detailed information

From https://github.com/networkupstools/nut/issues/26 : > Unfortunately I have only this UPS for testing purposes right now. It might makes sense to ask people on the nut mailinglist if they can send the result nut-scanner -qU if they have the same APC UPS. If you have a USB-based APC UPS, could you please send the list the output from "nut-scanner -qU"? You can remove the serial

Hi, I have an MGE Ellipse 1000 connected to a FreeBSD 7.1 system and it works well except that if I yank the cable it doesn't detect a problem.. It seems to quite merrily read the old data (upsc reports the same values). There is nothing logged by NUT to indicate comms is lost (usbhid-ups is still running). In the attached log I yanked the able at the 28 second mark and plugged it back

Hello, I have been trying to get a TrippLite Internet Office 750 UPS to talk to my Linux PBX for a couple of evenings now and I'm getting nowhere... I tried searching the list archives before posting here (I'm sure I'm not the first one to try to get this going) but they seem to be offline... The UPS is unfortunately USB based but I thought I'd give it a try anyway. Here is

On March 23, 2020 1:43:01 PM UTC, Tyler Montney <montneytyler at gmail.com> wrote: >Compiling against >http://www.networkupstools.org/source/2.7/nut-2.7.4.tar.gz. >I also have libusb-0.1-4 installed but no joy. > >On Mon, Mar 23, 2020 at 2:45 AM Jim Klimov <jimklimov at cos.ru> wrote: > >> On March 23, 2020 12:50:11 AM UTC, Tyler Montney ><montneytyler at

----- Forwarded Message ---- From: Terry Powling <terrypowling at yahoo.co.uk> To: nut-upsuser at lists.alioth.debian.org Sent: Sat, 27 February, 2010 22:30:05 Subject: trouble setting up kebo-1000d ups (usb) Trying to setup Kebo ups-1000D with usb port. lsusb Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 0925:1234 Lakeview Research Bus 002 Device

On March 23, 2020 12:50:11 AM UTC, Tyler Montney <montneytyler at gmail.com> wrote: >Came across this in the process of troubleshooting: >https://alioth-lists.debian.net/pipermail/nut-upsuser/2011-November/007249.html > >My whole reason for compiling from source is to add SSL support (as it >doesn't seem available through the package manager). Apt list shows >these

Sorry for such a noob question, but I'm having a problem with 2.7.4 ./configure . I down loaded the 2.7.4 tarball, unzipped. read the INSTALL and typed ./configure . The output of ./configure shows "build serial drivers: yes" and build everything else is "no". Looking at config.log, I see configure:8104: checking for libusb version via pkg-config configure:8111:

On 06/15/2017 04:32 PM, Arnaud Quette wrote: Hello > > .... still no reply from them ... > > is the guy you contacted Paul Henri? I wrote to a generic alias ( Ro-PQSupport ). Got a reply from a fellow Romanian who also CC:ed something looking like a list (List-EGPQCO-BUCRO-PQ ). I replied to both of them 5 days ago, received nothing since. > >>> Would you also

On Sep 12, 2014, at 5:15 PM, Stan Gammons <sg063015 at gmail.com> wrote: > On 09/11/14 22:34, Charles Lepple wrote: >> On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote: >> >>> I see a libusb_get_interrupt message in the log. Could that be the problem? >> Yes, it seems related. >> >> 1.126896 upsdrv_initinfo...

On 09/17/14 22:31, Charles Lepple wrote: > On Sep 12, 2014, at 5:15 PM, Stan Gammons <sg063015 at gmail.com> wrote: > >> On 09/11/14 22:34, Charles Lepple wrote: >>> On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote: >>> >>>> I see a libusb_get_interrupt message in the log. Could that be the problem? >>> Yes, it

On 06/13/2017 05:48 PM, Arnaud Quette wrote: > Hi Manuel Hi Arno > > 2017-06-07 14:40 GMT+02:00 Charles Lepple <clepple at gmail.com > <mailto:clepple at gmail.com>>: > > On Jun 7, 2017, at 5:47 AM, Manuel Wolfshant > <wolfy at nobugconsulting.ro <mailto:wolfy at nobugconsulting.ro>> wrote: > > > > If that matters, the

Hi Charles, > Sigh, I wish the vendors wouldn't change operation without changing identifiers. > > Do you have any recommendations on how the driver should decide whether it is an old 0x0004 or new 0x0004 device? No-no, there is no an old 0x0004 or new 0x0004 device, I guess that we have to handle general case for all 0d9f:0x0004 devices. From PCM_USB_LIST_device2014.pdf attached

I have just compiled and installed nut-2.4.1 and I get the following errors when I try it: There is no difference if I run it as root or normal user. Any help would be appreciated. # usbhid-ups -DDD -a SMART1000LCD Network UPS Tools - Generic HID driver 0.34 (2.4.1) USB communication driver 0.31 debug level is '3' upsdrv_initups... Checking device (1D6B/0002) (001/001) libusb

Dear Charles and Artem, I've recently bought a new PowerCom Imperial IMD825-AP LCD which identifies itself as 0x0d9f:0x0004. At first glance it seems that usbhid-ups driver works fine. But when I tried to shutdown UPS via DelayBeforeShutdown it started double beeping every couple seconds for indefinite time (the same problem described by Vincenzo Colonnella here:

Compiling against http://www.networkupstools.org/source/2.7/nut-2.7.4.tar.gz. I also have libusb-0.1-4 installed but no joy. On Mon, Mar 23, 2020 at 2:45 AM Jim Klimov <jimklimov at cos.ru> wrote: > On March 23, 2020 12:50:11 AM UTC, Tyler Montney <montneytyler at gmail.com> > wrote: > >Came across this in the process of troubleshooting: > > >

On 12/18/2015 10:01 PM, hyouko at gmail.com wrote: > 3 additional requests: > - can you plug the UPS to the serial port and test it with nutdrv_qx > (still with a debug level of 5)? > - can you test the UPS with blazer_usb and blazer_ser with a debug level of 3? > - which version of libusb/libusb-compat do you have? Exact versions: Information for package libusb-0_1-4: