search for: vgd

...y 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 by Alexey Morozov: "(VGD, VRT, RPT, .. and new UPS etc.) - 0X04.". According to this doc we can expect that all new PowerCOM devices will be shipped with ID 0X0d9f:0X04. For example, my Imperial IMD-825AP LCD has 0x0004, but an old examples of this model have 0Xa2. Also, lets take a look inside PCM_USB_protocol_20...

On Nov 11, 2014, at 3:30 PM, Maksym Bodaniuk <max.bodaniuk at gmail.com> wrote: > 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

...on on that one. There was another thread about this, where it seems there are other mismatches between the report descriptor sizes, and what the UPS expects: http://article.gmane.org/gmane.comp.monitoring.nut.user/7662 > From PCM_USB_LIST_device2014.pdf attached by Alexey Morozov: > "(VGD, VRT, RPT, .. and new UPS etc.) - 0X04.". According to this doc we can expect that all new PowerCOM devices will be shipped with ID 0X0d9f:0X04. For example, my Imperial IMD-825AP LCD has 0x0004, but an old examples of this model have 0Xa2. > > Also, lets take a look inside PCM_USB_prot...

Hi Have been trying to get nut and Powercom Vanguard 2000 ups communicating ? in the /lib/udev/rules.d/52-nut-usbups.rules file we have this entry #? PowerCOM VGD - Vanguard? - usbhid-ups ATTR{idVendor}=="0d9f", ATTR{idProduct}=="0004", MODE="664", GROUP="nut" ? In the /etc/ups/ups.conf [UPS] ??????? driver = usbhid-ups ??????? port = /var/lib/ups/hiddev0 ??????? productid = 0004 When running the command upsdrvctl...

resending to the list - got an error the first time. From: Charles Lepple <clepple at gmail.com> Subject: Re: [Nut-upsuser] Re Powercom Vanguard driver for nut Date: July 21, 2012 1:21:22 PM EDT To: Gordon Longland <gordon at compsos.com.au> Cc: nut-upsuser at lists.alioth.debian.org <nut-upsuser at lists.alioth.debian.org> On Jul 21, 2012, at 7:52 AM, Gordon Longland wrote:

...1 BILN NO OABS INST IDC NO DCNO 0 * NDNO 0 DEXT NO ANTK SIGO STD ICIS YES TIMR ICF 512 OGF 512 EOD 13952 NRD 10112 DDL 70 ODT 4096 RGV 640 GRD 896 SFB 3 NBS 2048 NBL 4096 IENB 5 TFD 0 VSS 0 VGD 6 DRNG NO CDR NO VRAT NO MUS NO FRL 0 0 FRL 1 0 FRL 2 0 FRL 3 0 FRL 4 0 FRL 5 0 FRL 6 0 FRL 7 0 OHQ NO OHQT 00 CBQ NO AUTH NO TDET NO TTBL 0 ATAN NO PLEV 2 ALRM NO ART 0 SGRP 0 AACR NO DES VERSA TN 101 01 TYPE TIE CDEN SD CUST 0 TRK PRI P...

We've been trying unsuccessfully to connect our Meridian Option 81C to a TE110P via PRI. We've followed the directions in asterisk-meridian-a1.pdf (link on http://www.voip-info.org/wiki/view/Asterisk+legacy+integration), but it doesn't seem to work on our 81C (even though many, many users report it works very well on Option 11's). Has anyone had any success in getting the above

Hello all, long time away from this list, glad to be around again! I have this Powercom Vanguard VGN VGD-20K31. Some details of this model: * 3-phase input, single phase output * Model has 240V / 12V9AH x 20 x 2SET, plus another set of 20 batteries. All in all, 3 sets * Serial connection to Windows 2k3 server with UPSMon Now I was strongly considering replacing the bundled no-good upsmoon crap, wi...