On 03/08/2012 02:37 PM, Arnaud Quette wrote:
2012/3/7 Zach La Celle lace...@roboticresearch.com:
On 3/7/2012 11:53 AM, Arnaud Quette wrote:
2012/3/5 Zach La Cellelace...@roboticresearch.com:
Still getting the usbhid-ups Report 89 / Report 90 issues...output below.
hem, there was a bug in
2012/3/7 Zach La Celle lace...@roboticresearch.com:
On 3/7/2012 11:53 AM, Arnaud Quette wrote:
2012/3/5 Zach La Cellelace...@roboticresearch.com:
Still getting the usbhid-ups Report 89 / Report 90 issues...output below.
hem, there was a bug in the developer, mixing hexa and decimal :-/
the
2012/3/5 Zach La Celle lace...@roboticresearch.com:
Still getting the usbhid-ups Report 89 / Report 90 issues...output below.
hem, there was a bug in the developer, mixing hexa and decimal :-/
the reportIDs are really hexa!
a better patch is attached, same data needed than before please.
On 3/7/2012 11:53 AM, Arnaud Quette wrote:
2012/3/5 Zach La Cellelace...@roboticresearch.com:
Still getting the usbhid-ups Report 89 / Report 90 issues...output below.
hem, there was a bug in the developer, mixing hexa and decimal :-/
the reportIDs are really hexa!
a better patch is attached,
Hi Zach,
2012/2/29 Zach La Celle lace...@roboticresearch.com:
On 02/27/2012 06:38 AM, Arnaud Quette wrote:
2012/2/21 Zach La Celle lace...@roboticresearch.com:
I figured out the cause of this problem: incorrect permissions on the
USB device. At least, this seemed to fix the problem I had
Yes, I can test on trunk or on a patched version, but I cannot shut down
or restart this particular UPS during the day. Hopefully we won't need
to do that to figure out the Report 89 / Report 90 stuff.
Would you like me to run off of stable or devel? Also, can I check out
stable with
2012/3/5 Zach La Celle lace...@roboticresearch.com:
Yes, I can test on trunk or on a patched version, but I cannot shut down
or restart this particular UPS during the day. Hopefully we won't need
to do that to figure out the Report 89 / Report 90 stuff.
perfect.
indeed, I just need a driver
Still getting the usbhid-ups Report 89 / Report 90 issues...output below.
Thanks,
-Zach
upsc output:
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.runtime: 4860
battery.runtime.low: 120
battery.type: PbAc
battery.voltage: 54.8
battery.voltage.nominal: 24.0
On 02/27/2012 06:38 AM, Arnaud Quette wrote:
2012/2/21 Zach La Celle lace...@roboticresearch.com:
I figured out the cause of this problem: incorrect permissions on the
USB device. At least, this seemed to fix the problem I had when I
manually tried to run upsdrvctl and got a permission
On 02/13/2012 11:41 AM, Arnaud Quette wrote:
2012/2/13 Zach La Celle lace...@roboticresearch.com:
On 02/07/2012 10:58 AM, Zach La Celle wrote:
On 02/07/2012 10:41 AM, Arnaud Quette wrote:
that's what I was suspecting.
I've never seen that one before, though!
a driver debug output, Ie:
$
On 02/07/2012 10:58 AM, Zach La Celle wrote:
On 02/07/2012 10:41 AM, Arnaud Quette wrote:
that's what I was suspecting.
I've never seen that one before, though!
a driver debug output, Ie:
$ /lib/nut/usbhid-ups -D -a rack1ups
please, compress the result or sent in a reference to the
2012/2/13 Zach La Celle lace...@roboticresearch.com:
On 02/07/2012 10:58 AM, Zach La Celle wrote:
On 02/07/2012 10:41 AM, Arnaud Quette wrote:
that's what I was suspecting.
I've never seen that one before, though!
a driver debug output, Ie:
$ /lib/nut/usbhid-ups -D -a rack1ups
2012/2/6 Zach La Celle lace...@roboticresearch.com:
On 02/03/2012 08:51 PM, Charles Lepple wrote:
On Feb 3, 2012, at 3:10 PM, Arnaud Quette wrote:
On the USB side of things, something seems fishy with the APC usb
connection: it's been incrementing the Device ID, up to 124 from 004.
this is
On 02/07/2012 10:41 AM, Arnaud Quette wrote:
2012/2/6 Zach La Celle lace...@roboticresearch.com:
On 02/03/2012 08:51 PM, Charles Lepple wrote:
On Feb 3, 2012, at 3:10 PM, Arnaud Quette wrote:
On the USB side of things, something seems fishy with the APC usb
connection: it's been incrementing
On 02/03/2012 08:51 PM, Charles Lepple wrote:
On Feb 3, 2012, at 3:10 PM, Arnaud Quette wrote:
On the USB side of things, something seems fishy with the APC usb
connection: it's been incrementing the Device ID, up to 124 from 004.
this is not a big issue, and probably due to the 2.4.3
We recently had to replace an old APC SmartUPS 3000 with a newer 3000VA
(the 2U one). It has both serial and USB in the back (with an RJ-45 on
the end of the serial cable).
I can't get the apcsmart driver to connect. I figured it should work
the exact same as the old UPS, with /dev/ttyS0
Zach,
2012/2/3 Zach La Celle lace...@roboticresearch.com:
We recently had to replace an old APC SmartUPS 3000 with a newer 3000VA (the
2U one). It has both serial and USB in the back (with an RJ-45 on the end
of the serial cable).
I can't get the apcsmart driver to connect. I figured it
Thank you guys for your responses.
- The Nut version I have installed (from the Ubuntu repositories) is
2.4.3-1ubuntu3.1.
- The OS is Ubuntu server 10.04 LTS x64 with the 2.6.35-std210-amd64 kernel.
- Driver output:
root@www:/etc/nut# /lib/nut/apcsmart -D -a rack1ups
Network UPS Tools - APC
Updates on the USB side (sorry, I should have done these before sending
the last list email)...
lsusb:
root@www:/etc/nut# lsusb
Bus 005 Device 004: ID 051d:0003 American Power Conversion UPS
Bus 005 Device 002: ID 0624:0248 Avocent Corp.
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1
2012/2/3 Zach La Celle lace...@roboticresearch.com:
Thank you guys for your responses.
- The Nut version I have installed (from the Ubuntu repositories) is
2.4.3-1ubuntu3.1.
- The OS is Ubuntu server 10.04 LTS x64 with the 2.6.35-std210-amd64 kernel.
- Driver output:
root@www:/etc/nut#
2012/2/3 Zach La Celle lace...@roboticresearch.com:
I upgraded manually to the new Nut, but still receive the same error:
I should have added: supported by the usbhid-ups driver (so USB only).
root@www:/etc/nut# /lib/nut/apcsmart -D -a rack1ups
Network UPS Tools - APC Smart protocol
On Feb 3, 2012, at 3:10 PM, Arnaud Quette wrote:
On the USB side of things, something seems fishy with the APC usb
connection: it's been incrementing the Device ID, up to 124 from 004.
this is not a big issue, and probably due to the 2.4.3 driver.
I tend not to agree - the device ID should
We recently had to replace an old APC SmartUPS 3000 with a newer 3000VA
(the 2U one). It has both serial and USB in the back (with an RJ-45 on
the end of the serial cable).
I can't get the apcsmart driver to connect. I figured it should work
the exact same as the old UPS, with /dev/ttyS0 as
23 matches
Mail list logo
