Displaying 20 results from an estimated 20 matches for "5e1500i".
2017 Jun 07
0
Unable to use nut-2.7.4 with Eaton 5E1500I USB
On Jun 7, 2017, at 5:47 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote:
>
> If that matters, the OS is a fully updated CentOS 6.9 and this (latest stable ) version of nut was packaged by me. The problem appears on any of the USB ports ( well, I tried the 2 in front and one in the back of the server ).
>
> lsusb -v reports:
...
> wDescriptorLength
2017 Jun 19
0
Unable to use nut-2.7.4 with Eaton 5E1500I USB
On Jun 19, 2017, at 4:27 AM, Manuel Wolfshant wrote:
>
> 1.014501 [D2] Unable to get HID descriptor (Pipe error)
> 1.014511 [D3] HID descriptor length (method 1) -1
So at this point in the logs, the kernel USB HID driver is detached from the UPS HID interface (until the UPS USB cable is unplugged and reattached). If you run "lsusb -vvv -d 0463:ffff", does it print
2017 Jun 19
0
Unable to use nut-2.7.4 with Eaton 5E1500I USB
On Jun 19, 2017, at 10:45 AM, Manuel Wolfshant wrote:
>
> #lsusb -vvv -d 0463:ffff
>
> Bus 002 Device 012: ID 0463:ffff MGE UPS Systems UPS
...
> HID Device Descriptor:
> bLength 9
> bDescriptorType 33
> bcdHID 1.10
> bCountryCode 33 US
> bNumDescriptors 1
>
2017 Jun 20
0
Unable to use nut-2.7.4 with Eaton 5E1500I USB
On Jun 19, 2017, at 7:56 PM, Manuel Wolfshant wrote:
>
> On 06/20/2017 02:27 AM, Charles Lepple wrote:
>> On Jun 19, 2017, at 10:45 AM, Manuel Wolfshant wrote:
>>
>>> #lsusb -vvv -d 0463:ffff
>>>
>>> Bus 002 Device 012: ID 0463:ffff MGE UPS Systems UPS
>>>
>> ...
>>
>>> HID Device Descriptor:
>>>
2017 Jun 13
0
Unable to use nut-2.7.4 with Eaton 5E1500I USB
On 06/13/2017 05:48 PM, Arnaud Quette wrote:
> Hi Manuel
Hi Arno
>
> 2017-06-07 14:40 GMT+02:00 Charles Lepple <clepple at gmail.com
> <mailto:clepple at gmail.com>>:
>
> On Jun 7, 2017, at 5:47 AM, Manuel Wolfshant
> <wolfy at nobugconsulting.ro <mailto:wolfy at nobugconsulting.ro>> wrote:
> >
> > If that matters, the
2017 Jun 20
1
Unable to use nut-2.7.4 with Eaton 5E1500I USB
On 06/20/2017 04:08 AM, Charles Lepple wrote:
> [...]
> It does not get a length for method 1, so it moves on to method 2, which gets a length, but fails to get the rest of the descriptor. This is what is happening to lsusb, too (tries to fetch 549 bytes, gets only 9).
and is there anything I can do to fix, short of hoping to receive an
updated unbroken firmware for the UPS from a support
2017 Jun 07
2
Unable to use nut-2.7.4 with Eaton 5E1500I USB
Hello
I have a remote Dell R310 to which I connected via USB a new UPS,
model Eaton 5E1500I USB. Assuming I interpreted correctly the docs, it
should normally work using the usbhid-ups driver. However, no matter
what I tried, I get an error which you can also is included in the below
paste:
#usbhid-ups -DDDD -u root -x explore -x vendorid="0463" -a eaton
Network UPS Tool...
2017 Jun 19
1
Unable to use nut-2.7.4 with Eaton 5E1500I USB
On Jun 19, 2017, at 4:02 AM, Manuel Wolfshant wrote:
> On 06/18/2017 05:42 PM, Charles Lepple wrote:
>> On Jun 16, 2017, at 6:12 AM, Manuel Wolfshant wrote:
>>>
>>> running autogen.sh was triggered automatically. but even if I do it explicitly, I still get:
>>> + autoreconf -i
2017 Jun 19
0
Unable to use nut-2.7.4 with Eaton 5E1500I USB
On 06/18/2017 05:42 PM, Charles Lepple wrote:
> On Jun 16, 2017, at 6:12 AM, Manuel Wolfshant
> <wolfy at nobugconsulting.ro <mailto:wolfy at nobugconsulting.ro>> wrote:
>>
>> running autogen.sh was triggered automatically. but even if I do it
>> explicitly, I still get:
>> + autoreconf -i
>> configure.ac:887: warning: AC_LANG_CONFTEST: no
2017 Jun 14
0
Unable to use nut-2.7.4 with Eaton 5E1500I USB
Hello
On 06/14/2017 03:32 PM, Arnaud Quette wrote:
>
>
> On Jun 7, 2017, at 5:47 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro
> <mailto:wolfy at nobugconsulting.ro>> wrote:
>
>> >
>> > If that matters, the OS is a fully updated CentOS 6.9
>> and this (latest stable ) version of nut was packaged by me.
>>
2017 Jun 19
2
Unable to use nut-2.7.4 with Eaton 5E1500I USB
On 06/19/2017 11:02 AM, Manuel Wolfshant wrote:
> Thank a lot !
> Now, conclusions after attempting builds ( with no docs included since
> attempting to enable them triggers the errors related to missing or
> too old tools mentioned by me in an earlier message )
> - building against libsub 1.0 triggers the following 2 errors :
> nutdrv_qx-nutdrv_qx.o: In function
2017 Jun 19
2
Unable to use nut-2.7.4 with Eaton 5E1500I USB
On 06/19/2017 05:33 PM, Charles Lepple wrote:
> On Jun 19, 2017, at 4:27 AM, Manuel Wolfshant wrote:
>> 1.014501 [D2] Unable to get HID descriptor (Pipe error)
>> 1.014511 [D3] HID descriptor length (method 1) -1
> So at this point in the logs, the kernel USB HID driver is detached from the UPS HID interface (until the UPS USB cable is unplugged and reattached). If
2017 Jun 16
0
Unable to use nut-2.7.4 with Eaton 5E1500I USB
On 06/15/2017 04:32 PM, Arnaud Quette wrote:
Hello
>
> .... still no reply from them ...
>
> is the guy you contacted Paul Henri?
I wrote to a generic alias ( Ro-PQSupport ). Got a reply from a fellow
Romanian who also CC:ed something looking like a list
(List-EGPQCO-BUCRO-PQ ). I replied to both of them 5 days ago, received
nothing since.
>
>>> Would you also
2017 Jun 19
2
Unable to use nut-2.7.4 with Eaton 5E1500I USB
On 06/20/2017 02:27 AM, Charles Lepple wrote:
> On Jun 19, 2017, at 10:45 AM, Manuel Wolfshant wrote:
>> #lsusb -vvv -d 0463:ffff
>>
>> Bus 002 Device 012: ID 0463:ffff MGE UPS Systems UPS
> ...
>> HID Device Descriptor:
>> bLength 9
>> bDescriptorType 33
>> bcdHID 1.10
2017 Jun 13
2
Unable to use nut-2.7.4 with Eaton 5E1500I USB
Hi Manuel
2017-06-07 14:40 GMT+02:00 Charles Lepple <clepple at gmail.com>:
> On Jun 7, 2017, at 5:47 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro>
> wrote:
> >
> > If that matters, the OS is a fully updated CentOS 6.9 and this
> (latest stable ) version of nut was packaged by me. The problem appears on
> any of the USB ports ( well, I tried the 2 in
2020 Jan 07
2
unexpected UPS status
...I though it was supposed
to wait for a higher charge?
Nevertheless, the UPS reported a charge of 58% when the machine restarted, I expected about 20%. Free energy?
Q1) Does this last exercise indicate a bad battery that woke up on the second restart?
Or a failed UPS?
The UPS is a Eaton 5E1500i. It is only 6m old and within the warranty period.
Q2) What is the parameter I need to set on the UPS for a minimum charge before restarting power?
$ upsc eaton
Init SSL without certificate database
battery.charge: 68
battery.runtime: 1290
battery.type: PbAc
device.mfr: EATON
device.model: 5E 150...
2017 Jun 18
3
Unable to use nut-2.7.4 with Eaton 5E1500I USB
On Jun 16, 2017, at 6:12 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote:
>
> running autogen.sh was triggered automatically. but even if I do it explicitly, I still get:
> + autoreconf -i
> configure.ac:887: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body
2017 Jun 14
2
Unable to use nut-2.7.4 with Eaton 5E1500I USB
2017-06-13 17:49 GMT+02:00 Manuel Wolfshant <wolfy at nobugconsulting.ro>:
> On 06/13/2017 05:48 PM, Arnaud Quette wrote:
>
> Hi Manuel
>
>
> Hi Arno
>
>
Hi Manuel
>
>
> 2017-06-07 14:40 GMT+02:00 Charles Lepple <clepple at gmail.com>:
>
>> On Jun 7, 2017, at 5:47 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro>
>> wrote:
2017 Jun 15
2
Unable to use nut-2.7.4 with Eaton 5E1500I USB
Hi Manuel,
2017-06-14 15:16 GMT+02:00 Manuel Wolfshant <wolfy at nobugconsulting.ro>:
> Hello
>
>
>
> On 06/14/2017 03:32 PM, Arnaud Quette wrote:
>
>
>
> On Jun 7, 2017, at 5:47 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro>
> wrote:
>
>> >
>>> > If that matters, the OS is a fully updated CentOS 6.9 and this
>>>
2020 Jan 07
0
unexpected UPS status
....start" report?
> Nevertheless, the UPS reported a charge of 58% when the machine restarted, I
> expected about 20%. Free energy?
>
> Q1) Does this last exercise indicate a bad battery that woke up on the second
> restart?
> Or a failed UPS?
> The UPS is a Eaton 5E1500i. It is only 6m old and within the warranty
> period.
>
> Q2) What is the parameter I need to set on the UPS for a minimum charge
> before restarting power?
What does command "upsrw <ups>" report?
Roger