On 1/27/19 9:49 PM, Charles Lepple wrote: > You might be lucky with this particular model, but definitely beware of the > USB issues I mentioned in another thread: > > https://github.com/networkupstools/nut/issues?q=is%3Aissue+is%3Aopen+label%3A%22CyberPower+%28CPS%29%22 > > The output of upsc is sorted alphabetically by key, so it isn't immediately > obvious which values come from earlier in the report descriptor. However, > after the values for input.transfer.low and input.transfer.high, the other > values might end up being scaled to the transfer voltage range. Hence, I > would treat a lot of the values from usbhid-ups on CyberPower hardware > (including writable thresholds) as suspect. The USB HID report descriptors > are hierarchical, which enables cascading errors like these. We do have a > debug procedure that can get to the bottom of that if something comes up. >
Thanks, useful to know. I'll have to keep a note of that in case anything starts looking weird. I'm not 100% certain I'm tracking what you mean by 'scaled to the transfer voltage range' though. Could you clarify? -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 _______________________________________________ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
