Arjen de Korte de-korte.org> writes:
>
> Citeren Arnaud Quette gmail.com>:
>
> > can you please send us an upsc output?
>
> Not really needed. The richcomm_usb driver supports only 'ups.status'
> since the UPS is essentially a glorified contact closure device.
>
> > Have you also tested fo
Citeren Arnaud Quette :
can you please send us an upsc output?
Not really needed. The richcomm_usb driver supports only 'ups.status'
since the UPS is essentially a glorified contact closure device.
Have you also tested for shutdown, and upsrw / upscmd supported data?
Testing the shutdow
Hi Sergey,
2011/3/21 Sergey Talchuk
> Arjen de Korte de-korte.org> writes:
>
> >
> > Citeren Sergey Talchuk gmail.com>:
> >
> > > 2. lsusb output
> > > Bus 002 Device 001: ID :
> > > Bus 002 Device 002: ID 0925:1234 Lakeview Research
> >
> > Your UPS might be supported by the 'richcomm
Arjen de Korte de-korte.org> writes:
>
> Citeren Sergey Talchuk gmail.com>:
>
> > 2. lsusb output
> > Bus 002 Device 001: ID :
> > Bus 002 Device 002: ID 0925:1234 Lakeview Research
>
> Your UPS might be supported by the 'richcomm_usb' driver. It is most
> certainly not supported by
Citeren Sergey Talchuk :
2. lsusb output
Bus 002 Device 001: ID :
Bus 002 Device 002: ID 0925:1234 Lakeview Research
Your UPS might be supported by the 'richcomm_usb' driver. It is most
certainly not supported by the 'blazer_usb' driver.
Best regards, Arjen
--
Please keep list traf
Hello guys,
Please help me to resolve the issue.
I bought 'SVEN Power Pro+ 500 USB' UPS few days ago and tried to setup
NUT 2.6.0 to work with it.
blazer_ups driver doesn't recognize the UPS :(
The Manufacturer provides 'PowerD' software for linux with
installation instractions on a CD (see exampl
6 matches
Mail list logo
