search for: devclass_docs

...31 seconds in 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

...tery low. > 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 t...

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

...54 (repeated at #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 t...

...ly. Here are 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...

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

On Mar 7, 2014, at 11:24 AM, Rob Groner wrote: > Charles, > > Thank you so much for the information. I'm trying to digest it along with the other docs I have, the example code from Microchip, and a USB HID tutorial I found online. I realize that some of the descriptions can be a bit vague, so if you want to post a link to the HID tutorial, I can try to describe what is going on

On 11/23/2016 2:24 PM, Leon Fauster wrote: > DIY based onhttp://www.pcengines.ch/ hardware ... the APU2, which is their current generation board suitable for a router like this, requires 12VDC up to 1 amp, so tis not suitable for USB power (5V, up to 2.5 amp) unless you rig up a USB to 12V DC-DC converter. I do wonder how the OP plans on connecting his phone and/or tablet via ethernet to

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

...0000 0009 9 < 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...

Charles, Thank you so much for the information. I'm trying to digest it along with the other docs I have, the example code from Microchip, and a USB HID tutorial I found online. So, if I understand correctly.... When the device first connects, it sends a huge dump of data (which the usbhid driver shows when you use the debug option) which fully describes the data it is capable of sending.

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?

Hi Peter, I've forwarded your mail to upsdev as it will be of interest for several people that are working on it. As I'm also on vacation (again) for a week and 1/2 as of this evening, I don't think I'll have the time for it before I get back.... I've not yet audited the patches, but these are queued on the Alioth tracker: