search for: pdcv10

...the pcap file, the payload is 0x03, then it changes to 0x01 , and then it changes again to 0x02 at packet #3975/2081 seconds. It seems like: 0x01 = AC failed 0x02 = Battery low. 0x03 = AC is ok It looks simillar to the UPS implementation example from http://www.usb.org/developers/devclass_docs/pdcv10.pdf

...the details: On the page: https://networkupstools.org/ups-protocols.html Under the heading: Standard protocols USB/HID Power Devices Class USB Usage Tables for HID Power Devices (offsite PDF, 351K) This the bad link: -> http://www.usb.org/developers/devclass_docs/pdcv10.pdf ( which goes to "Developers / Page Not Found" at usb.org ) The link should probably be changed to -> https://www.usb.org/document-library/power-device-class-document-10 ( as the referral page on www.usb.org for the document ) The link to actual document is...

...0x03 = AC is ok Also, there is an Interrupt Out transfer at #4115/2154 (repeated at #4117) that sends a 0x01 down to the UPS. I assume it turns off at that point, or shortly thereafter? > It looks simillar to the UPS implementation example from > http://www.usb.org/developers/devclass_docs/pdcv10.pdf Well... the first few pages of Appendix A are boilerplate USB descriptors. The report descriptor (A.6) is where things start to differ. Your UPS doesn't have Usage Page 0x84, 0x85 or 0x86 in its report descriptor - it only has 0xFFA0, which is in the vendor-specific range, and the two Usag...

On 20/12/13 21:22, Charles Lepple wrote: > > Maybe Dan, the maintainer of the nutdrv_qx driver, has better insight on this, but my uneducated guess is that I don't think it is Megatec/Qx. The logs don't show any commands going down to the UPS, just Interrupt Read requests to EP1IN. > > It definitely won't be covered by stock usbhid-ups either, although it does implement the

...t #4117) that sends a 0x01 down to the UPS. I assume it turns off at that point, or shortly thereafter? Sorry for the the delay, If I remember correctly, that's what happened. >> It looks simillar to the UPS implementation example from >> http://www.usb.org/developers/devclass_docs/pdcv10.pdf > Well... the first few pages of Appendix A are boilerplate USB descriptors. The report descriptor (A.6) is where things start to differ. Your UPS doesn't have Usage Page 0x84, 0x85 or 0x86 in its report descriptor - it only has 0xFFA0, which is in the vendor-specific range, and the two...

...ffset: 8, Size: 8, > Value: 2 > Path: UPS.PowerSummary.*DesignCapacity*, ReportID: 0x0c, Offset: 16, > Size: 8, Value: 100 > Path: UPS.PowerSummary.FullChargeCapacity, ReportID: 0x0c, Offset: 24, > Size: 8, Value: 100 > > (These are both 'Type: Feature'.) > > From pdcv10.pdf, UPS.BatterySystem.Battery.DesignCapacity should be in > CapacityMode units, and CapacityMode==2 is %. But since CapacityMode is in > UPS.PowerSummary, maybe it refers to UPS.PowerSummary.DesignCapacity instead. > The 18000 might be mAh or mWh. > > It is also possible that one of...

Hello Charles, Am 2008-03-13 19:27:27, schrieb Charles Lepple: > Another advantage of going the HID PDC route (regardless of whether > NUT is involved) is that the device is essentially self-describing. If > the first version does not have a shutdown flag, but later versions > do, then very little driver code needs to change - just device > firmware. > > Also, I believe that

Any news? Send dubug with explore one more time in attach 19.12.2014 15:39, Charles Lepple ?????: > On Dec 19, 2014, at 5:16 AM, ??????? ??????? <freemgm at gmail.com> wrote: > >> # /usr/local/libexec/nut/usbhid-ups -DD -a eaton9sx -u root -x explore -x vendorid=0x0463 2>&1 | tee /tmp/eaton9sx-explore.log > Ah, I forgot about the vendorid. The string is a regex which

Things are going along well, but there is one remaining area of confusion...."units". I understand exponents now...it's basically how you pass decimal values. That's easy enough. But "units"....in other words, I have a voltage I want to put in a report. If I include in the report descriptor the fact that it is actually a voltage, with units of "volts",

Hello, since I had delayed the programming of the UPS Device part, now it is time to continue... My Device is "24 V DC modular ATX PSU" which replace the standard ATX Power Supply in PCs and use 15-43 V Input Voltage. The microcontroller is a TI LM3S5T36 Cortex M3 and I get the "UPS" infos using up to 4 Maxim DS1780 and some I?C current sensors. The ATX PSU has 4

Dear ladies and gentlemen, we are developer and producer of UPS devices. Now we would like to integrate a small UPS via USB connection to NAS systems. We heart from third party that we need a special driver for NAS systems to work fine and to display also the company name and UPS device name in the web page / software of NAS. Currently we have a UPS with USB and our own VID (0x2B2D) and PID

...lt; 265b7600 0.724412 C Ci:6:002:0 0 9 = 09210001 00012278 02 265b7600 0.724428 S Ci:6:002:0 s 81 06 2200 0000 0278 632 < 265b7600 0.806424 C Ci:6:002:0 0 632 = 05860904 a1010584 091ea100 8501091f 65007504 95011500 250f6500 b1027504 I've looked at http://www.usb.org/developers/devclass_docs/pdcv10.pdf (linked from http://www.networkupstools.org/protocols/) and deciphered the "** UNRECOGNIZED: ?09 21 00 01 00 01 22 78 02" line from lsusb, but I don't know how to get it to spew out the 0x7802 bytes of reports the document describes. I suppose that I can install Windows in a virt...

Dear Nut-UPSdev Team, First of all I would like to appreciate the great job you are doing. Your work is very important and helpful for all UPS users. I found that you show compatibility with blazer_ser and blazer_usb for six of our models. Please inform me how we can make it happen that all our models become compatible? Who from your team added the compatibility with PowerWalker VI 850 LCD?