t;
Yes indeed it should be reported as negative value. I will check in
firmware and make the according changes.
Thanks for noticing.
Regards,
Nicu Pavel
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
Hi,
On Wed, Nov 28, 2012 at 11:46 PM, Arnaud Quette wrote:
>
>
> 2012/11/28 Nicu Pavel
>
>> Hi,
>
>
> Hi
>
> thanks for your patches.
> though I've started to process your 1rst patch 6 days ago, my current
> latency should push me in acknowledging
Hi,
A small update to the patch with correct names for upower-hid.rules and a
running dump for openups.
Thanks,
Nicu
On Tue, Nov 20, 2012 at 11:37 AM, Nicu Pavel wrote:
> Hi all,
>
> I attached a driver for MiniBox openUPS device (
> http://www.mini-box.com/OpenUPS) and a dum
ort[get]: (5 bytes) => 20 99 01 1a 03
Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x20,
Offset: 0, Size: 16, Value: 153
Report[buf]: (5 bytes) => 20 99 01 1a 03
Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x20, Offset: 16,
Size: 16, Value: 7.94
Thanks,
N
kupstools.org/projects/nut/changeset/3770
>
In the mean time I got the firmware source and tried to clean/add some
missing entries but there are still issues. I have a partially working
driver that I'll post in a few days for comments.
Thanks,
Nicu Pavel
Hi,
I'm trying to generate a skeleton driver with usbhid-ups and
gen-usbhid-subdriver but the output seems to be incorrect. Same
behavior with stable 2.6.5, so I guess there is something wrong with
data coming out of device.
I attached the output of usbhid-ups and gen-usbhid-subdriver from the com
