Citeren Vlad :
I'll try to install dev version and see whether it works.
What kind of diagnostic info would you need?
USB ID of my device is :.
Could you also try the blazer_usb driver from nut-2.4.3 (the same
version as the megatec_usb driver that worked for you)?
/path/to/bla
Citeren Martin Ivanov :
root@alhana:/etc/nut# /etc/rc.d/rc.ups start
Network UPS Tools - UPS driver controller 2.6.0
Network UPS Tools - Generic contact-closure UPS driver 1.36 (2.6.0)
UPS type: Repoteck RPT-800A, RPT-162A
tcgetattr: Inappropriate ioctl for device
Driver failed to start (exit st
Citeren Vlad :
I downgraded back to 2.4.3, configured nut to use megatec_usb again,
and it started working again.
However, it seems strange that I cannot use the latest version.
This is not strange at all. We have reworked this driver core and
could not find people with access to these dev
Citeren Martin Ewing :
This seems very similar to the trouble I have with a Belkin UPS (USB) with
Natty (64 bit).
Not at all. You seem to be suffering from a permissions problem, where
Vlad is not (most likely, there is a problem in the protocol
handling). These are totally unrelated issue
Citeren Raphaël :
Testing PID before launching a new instance of driver is a good
solution but need to be implemented in /etc/init.d/nut
So, what's the big deal here? This is just a script on most (if not
all systems) that can be modified easily. On the other had, changing
the binaries is
Citeren Raphaël :
When reading /etc/init.d/nut, i see that when restarting nut, script
stop nut and start it again.
When starting again the driver is one more time started without any
verification that its already launched.
Stopping a driver is an asynchronous process. So you either have to
Citeren James Smith :
So how do I make sure it never sees the LB event (or ignores it)?
By wiring you sensor so that it either sets OB or LB and hard wiring
the other to the inactive state.
[...]
The point about the short is a valid one, but I don't think it will
be an issue (if it ever
Citeren James Smith :
I now have everything in place and I get an email when the temp sensor opens
Question - what do I set so the system doesn't shut down when the
sensor stays open?
The system will only shutdown if you have an OB+LB event at the same
time. As long as you make sure the s
Citeren Martin Ivanov :
Browsing the compatibility list of nut has revealed that there are
NUT drivers for the RPT-162A (genericups upstype=13) and RPT-800A
and RPF525/625/800/1000 modes (safenet). Is it possible that any of
these drivers work, and if yes, which one?
As far as I can tell,
Citeren Manzoor e Elahi :
Here's something more I've found using the new soft. Please take a look.
If you have such a table available, you can figure out quite easily
which upstype is applicable here:
cable power = DTR
online = CTS off
low battery = CD on
This looks like
Citeren Jose Álvarez :
When I turn on my pc everything works fine, but if I restart fails
(I'm not sure if this is true at 100%) (then, i can do 'sudo
/etc/init.d/nut restart' and it works)
This usually means that you're attempting to use the USB bus before it
has initialized.
But what
Citeren Manzoor e Elahi :
Thanks for your instruction. I tried the portman under XP. The log file is
attached with the mail. Please check that out and let me know what you think
or any further instruction. Thanks for your time.
This is almost certainly supported by one of the genericups models
Citeren Dushan Tcholich :
[...]
/lib64/nut/blazer_ser -D -a munja -i 10
Network UPS Tools - Megatec/Q1 protocol serial driver 1.51 (2.6.0)
0.00 send_to_all: SETINFO driver.parameter.port "/dev/ttyS0"
Looks fine.
[...]
upsmon -D
Network UPS Tools upsmon 2.6.0
0.00
Citeren Arnaud Quette :
I've not gone through this thread, but is there any reason not to commit
this patch (ie issues with phoenix that need more work)?
I'm good with it and just committed the patch. This will not affect
existing supported devices, so there is no reason not to commit it.
Citeren Rupert Hair :
I'm running Solaris 11 Express (snv_151a X86) with NUT 2.6.0 compliled
from the source tarball and a Powerware 5115. I was seeing the driver
hang,
What makes you think the driver 'hangs'?
so gave it some '-D's (23 apparently ;-) and found that it seems
to be getting in
Citeren Manzoor e Elahi :
Thanks for your replay. Actually my UPS uses a lite version of that software
and only reports mains on/off, ups on/off and ups connected/disconnected
status. I also think the genericups driver should work and tried all the
driver types without any luck. Unfortunately I
Citeren Manzoor e Elahi :
I'm trying to configure my ups with nut which is a locally made one. It
uses a rs232 port to talk to the computer and comes with a software called
"Powermanager Lite" which is provided by Richcomm and supports Windows,
Linux and UNIX. According to the manual it uses
Citeren Pavel Selivanov :
I've being using nut 2.2.2 (Debian Lenny) via megatec_usb driver for
IPPON Back UPS 600.
Then I upgraded to nut 2.4.3 (Debian Squeeze) with broken megatec_usb.
I moved to blazer_usb, it connected IPPON.
[myups]
driver = blazer_usb
port = /dev/usb/hiddev0
Citeren Josu Lazkano :
Hello list, I am trying to configure Belkin F6C550-AVR UPS on a
Squeeze server.
I try with "usbhid-ups" but I get "(driver(s) failed)" message on
service start.
[...]
This is my lsusb output:
$ lsusb
Bus 001 Device 004: ID 0665:5161 Cypress Semiconductor USB to S
Citeren "GATINEAU, ANTOINE (ANTOINE)" :
I got it working. Aparently, the script is launched as the specified
user but without the environment variables.
To make it work, i have defined NOTIFYCMD as following :
NOTIFYCMD "/bin/bah -c 'source /etc/profile ; /path/to/script/scriptname"
Is there
Citeren Francesco Talamona :
I was simply trying to gather more information because the running
setup, the one with liebert driver and nut user, wasn't able to run
anymore with the upgrade. Sorry I didn't make it clear in the first
instance.
I made too many tests and more than one driver get lo
Citeren Danilo Godec :
I just got two new UPS's - GE EP6000R. These have both RS232 and USB
connection.
As far as I could detect these are not supported by NUT. However, they
provide some Linux software and as long as these UPS's are not in
production (another week or so) I could 'play' with th
Citeren Justin Ellison :
Attached is a -DDD log of the driver.
Did you look at it before sending it? If not, look now... :-)
We need the output of both stdout and stderr:
/path/to/usbhid-ups -DDD -a upsname > CyberPower_CP850.log 2>&1
The first 30 seconds worth of output should be enoug
Citeren Francesco Talamona :
I have a 64 bit Gentoo, with a Liebert UPS. The last NUT working version
was sys-power/nut-2.4.1-r1 (I also tried sys-power/nut-2.4.3-r2 but
downgraded, don't remember the reason).
[...]
I don't know what else I can try, I simply don't understand what's going
on.
Citeren Márk Csaba :
[eaton_1]
driver = blazer_usb
port = "002"
desc = "Eaton NV 2000H"
vendorid = 0665
productid = 5161
bus= "003"
[eaton_2]
driver = blazer_usb
port = "002"
desc = "Eaton NV 2000H"
vendo
Citeren Arun :
Yeap. IMO an even better option (if technically feasible) would be
for the driver to try and reconnect to the UPS every few seconds. It
seems to do this well if it loses connectivity after having
established the initial connection, but not at all at startup.
This is intenti
Citeren Justin Ellison :
When I tested it out tonight, I made a point to watch the LED on the
unit in comparison to the battery.charge indicator from nut. Almost
instant I unplugged it, battery.charge went from 120 to 91, and
immediately fell in sync with what the LED was showing.
In that cas
Citeren Charles Lepple :
in the current version of cps-hid.c, it looks like
FullChargeCapacity, DesignCapacity and CapacityMode are unmapped.
This is intentional. The capacity mode determines the units in which
FullChargeCapacity and DesignCapacity will be reported. Generally,
this will b
Citeren Justin Ellison :
I have a CyberPower Systems CP850PFCLCD that I'm hooking up to NUT 2.4.3
from apt running under Ubuntu 10.04. Using the usbhid-ups driver, things
*seem* to work at first glance, but there are some odd issues. The most
notable issue is that the battery.charge indicator
Citeren Garðar Arnarsson :
Just wondering what information is required for adding a ups to the
compatability list...
Is upsc output enough?
No, we also need to know if the UPS supports shuts down automatically,
both when on mains and on battery. To check this, issue the
upsmon -c fsd
Citeren Andrea :
* Service upsdrv starting
Network UPS Tools - UPS driver controller 2.6.0
Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.6.0)
Can't claim USB device [:]: could not detach kernel driver
from interface 0: Operation not permitted
Driver failed to start (exit st
Citeren Andrea :
Exactly what benefit can i have using the new driver with this hack?
If nothing changes i can wait for nut 2.6.1 ;-)
It would help to confirm that this is indeed the problem so that
nut-2.6.1 will work out-of-the box for you (and all others using this
model). Other than th
Citeren Andrea :
0.257887 Trying megatec protocol...
0.257901 send: Q1
0.506931 blazer_status: short reply
0.506950 Status read 1 failed
Sadly there is a small flaw in the krauler subdriver here and it
doesn't output the data it has read from the UPS. But since it
Citeren Andrea :
Some output with blazer_usb:
* Service upsdrv starting
Network UPS Tools - UPS driver controller 2.6.0
Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.6.0)
No supported UPS detected
Driver failed to start (exit status=1)
Failed to start UPS drivers!
Citeren Espen Berg :
I have just installed nut_2.6.0 from Debian testing, do anyone know
the correct driver for this ups? The blazer_usb don't report
battery-charge, the bundled software report charge and runtime.
The UPS doesn't report battery charge and/or runtime. See the
paragraph BA
Citeren John Bayly :
Thanks for pointing that out. Just did some timing and found that
with and without the "pollonly" flag set, the ups.load value was
changing when applying and removing additional load. I did however
notice that the time taken to register the load change could be
betwee
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
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
Citeren Charles Lepple :
If I run it under strace, the ioctls on the /dev/bus/usb file descriptor
preceeding each "operation not permitted" error return 0, not an
error code
such as EPERM.
That seems strange. Would you please compress and send the strace output
(without "-u root")?
Attach
Citeren Charles Lepple :
Arjen: do we actually have any cases of reports larger than 8 bytes?
Yes. At least the MGE Evolution series uses reports that are larger
than 8 bytes.
If so, should we mark this as a quirk for CyberPower devices?
Well, I still don't understand why we can't read
Citeren Brian Read :
Am Trying to use nut (2.2.0 - on an SMEServer V8 aka Centos 5.5) on
the above UPS, I've tried the megatec driver in serial and USB mode
(the device has both types of connection), but no success.
The version of NUT you're using is almost four years old and well past
i
Citeren Armin Barth :
Hallo,
I'm loocking for a driver to connect a AEG UPS Protection A 1500 mit
nut.
The Error-massage is this:
Network UPS Tools - UPS driver controller 2.6.0
Network UPS Tools - Generic HID driver 0.35 (2.6.0)
USB communication driver 0.31
This Liebert device (06da:0003) is n
Citeren James :
$ sudo /usr/sbin/upsd -
Network UPS Tools upsd 2.4.3
0.00 listen_add: added ::1:3493
0.84 listen_add: added 127.0.0.1:3493
0.000102 setuptcp: try to bind to 127.0.0.1 port 3493
0.000185 listening on 127.0.0.1 port 3493
0.000204 setup
Citeren Lukas Haase :
I somehow tried both but it does somehow not work as expected.
When I add
ups : ALL
upsd : ALL
to hosts.deny, then no communication should be possible. However, I
can access the statistics from another host running upsstats.cgi!
I also tested with "upsc denchi@localh
Citeren Garðar Arnarsson :
Only if the UPS finds that the battery needs to be replaced it will report
the 'RB' status (replace battery). If it doesn't, all is well. The Q1
protocol that is used by your UPS doesn't support more verbose messages
(and neither does it report runtime or charge capaci
Citeren Garðar Arnarsson :
Thanks a bunch, that worked like a charm :)
Glad to hear that.
But now I've got another question... After I run commands (tests) with
upscmd, where do I see the results?
You don't.
Ran a battery test check and it did not give any output.
Only if the UPS finds
Citeren Garðar Arnarsson :
I have defined the user in the /etc/ups/upsd.users
74 [gardar]
75 password = hidden
76 allowfrom = local
77 actions = SET
78 instcmds = ALL
79 [local_mon]
80 password = hidden
81 allowfrom = localhost
82
Citeren James Cameron :
# upscmd myups load.on
Username (root):
Password:
#
It didn't turn on. What's this username and password?
How should I know? (man 5 upsd.users)
Best regards, Arjen
--
Please keep list traffic on the list (off-list replies will be rejected)
_
Citeren James Cameron :
# lsusb
Bus 001 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial
Try the blazer_usb driver instead. Make sure that any remaining NUT
drivers that may be running in the background are terminated. Chances
are that multiple drivers are now fighting for cont
Citeren Frederic Praca :
I wondered how the USB UPS are detected and if my UPS is described in
the source code. Any idea of where I should take a look ?
We search for a VendorID / ProductID combination. The one you posted earlier
idVendor = 0x0463
idProduct = 0x
is one of the combina
Citeren frederic.pr...@free.fr:
I have to manage an Eaton Ellipse ASR 750 VA UPS under a FreeBSD 8.2 server.
I used nut from ports collection but I'm unable to detect the UPS by
USB cable.
[...]
Any idea of how to make it works ?
Did you follow the FreeBSD installation HOWTO that's menti
Citeren Erik Hjertén :
I'm quite stuck now so any pointers on how to troubleshoot is most
appreciated.
The first thing to check is whether or not the UPS receives the
shutdown command. Power your system from an alternative source (this
is important!) and run the command
/path/to/usb
Citeren Carsten Burkhardt :
Do you mean such unsuccessfully test with new hardware same like
attached file explore.txt?
No. We're specifically looking for people that have access to UPS
systems that are known to be supported by existing versions of NUT, to
verify that new releases still s
Thank you for support, the problem is solved. Wrong cable.
Now it's working with megatec driver and settings:
[IPPON]
driver = megatec
port = /dev/ttyd0
desc = "IPPON Smart Winner 1500VA"
battvolts = 53:39
mfr = "Ippon"
model = "Smart Winner"
You'll probably want to try the blazer_ser driver to
Citeren Zach La Celle :
On the Dell server, the MpMemory testing all passed. It doesn't
seem to be a physical problem with the memory on the machine. I
also ran some other basic diagnostics on the disk drives, cache, and
the rest of the system, and it all passed as well.
Any further ide
Citeren Zach La Celle :
You can see where the problem happens in parseconf.c, on line 125
with the code:
/* resize the lists */
ctx->arglist = realloc(ctx->arglist,
sizeof(char *) * ctx->numargs);
With the given arguments, this boils down to
ctx->argli
Citeren Brian Daniels :
upshid-ups is unable to communicate with the UPS, giving 'Protocol
error'. I've also tried the snapshot and 2.7 svn release with the
same results. Debug output is below, any ideas appreciated.
Could you try if the attached patch makes any difference? We've seen
o
Citeren Ernest Sales :
N.B.: the blazer_usb driver recognized the device, but logs showed
connection loss about every minute, so I didn't do further
trying.
This is a known problem in nut-2.4.3 and should be solved in
nut-2.6.0. We have also dropped the megatec and megatec_usb drivers,
s
Citeren Kevin :
For info, I added this line:
{ "shutdown.stop", 0, 0,
"UPS.APCGeneralCollection.APCDelayBeforeShutdown", NULL, "-1",
HU_TYPE_CMD, NULL },
{ "shutdown.reboot", 0, 0,
"UPS.APCGeneralCollection.APCDelayBeforeReboot", NULL, "10",
HU_TYPE_CMD, NULL },
* { "shutdown.retur
Citeren Mike Barber :
Installed 2.4.1 using apt and installed in place of initial version
Found various web documents detailing that blazer_usb would probably be the
driver to use.
using usb.conf :
[UPS]
driver = blazer_usb
port = auto
and running the driver in debug mode gives the following
Citeren Kevin :
On power:
Switches immediately to battery
Waits 60 seconds
Sleeps for 2 seconds, switches output power off
Restarts
Although it is a bit weird that the device switches to battery, this
doesn't really harm. We know such behavior from older devices with
'dumb' contact closur
Citeren Kevin :
Yes, that does the trick!
# clients/upscmd -u apcmon -p pass123 apc1500 shutdown.return
has the desired effect.
Good. I assume you tried this on the CS-500, right? Do you have any
idea how long the delay is before the device actually shuts down?
Would you like me to prov
Citeren Kevin :
You are quite right! I now have this line in apc-hid.c:
{ "shutdown.return", 0, 0,
"UPS.APCGeneralCollection.APCDelayBeforeReboot", NULL, "1",
HU_TYPE_CMD, NULL },
and get this result:
# clients/upscmd -u apcmon -p pass123 apc1500 shutdown.return
Unexpected response from
Citeren Ernest Sales :
I would like to report a working device to add to the hardware
compatibility list, but cannot find a way on the website. Would this
list be OK for that purpose?
Sure. Please list the output of 'upsc' as well as whether or not you
tested the shutdown function of the
Citeren Kevin :
Exactly. I am beginning to see a 'broken firmware' pattern here.
The above is the only reason why we need multiple HID subdrivers in
usbhid-ups. If every UPS vendor would care to implement (and properly
test!) their firmware, we would need exactly one subdriver that would
Citeren Kevin :
You could have perhaps made a point of the sudden change to a
different command. Others also missed this subtlety.
I posted the 'old' and 'new' lines. You might have missed this on the
first look, buy after I told you the difference, you could have looked
again at the orig
Citeren Pier Paolo Glave :
Yes!
The results are quite different now :)
That's good to know.
This is the result of "upsc" now, when AC power is plugged in:
battery.charge: 100
battery.type: PbAc
battery.voltage: 28
battery.voltage.nominal: 2
device.mfr: Emerson Network Power
device.model: Lie
Citeren Kevin :
There is no call for language like that. I've spent a huge amount of
time in the last six weeks trying to sort this problem with your code.
This is not *my* code. I'm just trying to help here. I would be more
than happy to ditch the APC support from NUT entirely, but due to
Citeren Kevin :
Ok. Thanks. The order of the code is now:
{ "shutdown.reboot", 0, 0,
"UPS.APCGeneralCollection.APCDelayBeforeReboot", NULL, "1",
HU_TYPE_CMD, NULL },
{ "shutdown.reboot", 0, 0, "UPS.PowerSummary.DelayBeforeReboot",
NULL, "10", HU_TYPE_CMD, NULL },
{ "shutdown.reboot"
Citeren Pier Paolo Glave :
Please find attached the log of "/lib/nut/usbhid-ups -D -a liebert",
produced with the 2.6 driver.
From this it is quite clear what is happening. The UPS *is* reporting
the values needed, but the people that wrote the firmware of this
device apparently got so
Citeren Kevin :
On 06/02/2011 21:42, Kevin wrote:
Ok, I've tried that. The result of "clientcmd -u apcmon -p pass123
-a apc1500 shutdown.reboot" is nothing. Nothing that I can see
changes at all.
Of course. Do as I asked you and it *will* make a difference.
I did this with the old workin
Citeren Pier Paolo Glave :
Everything seems to be fine, except that, when I run "upsc
liebert@localhostups.status", it retuns "OB", even if the UPS is
currently online.
Looking at the rejected earlier message, I'd say you have a Belkin OEM
device that has a very broken report descriptor. You
Citeren Kevin :
Seems to have gone a bit quiet. Are we at a dead end now?
No, I just don't have a lot of spare time on my hand lately. You could
try if changing
{ "shutdown.reboot", 0, 0,
"UPS.APCGeneralCollection.APCDelayBeforeReboot", NULL, "10",
HU_TYPE_CMD, NULL },
to
{
Citeren Mehmet Giritli :
Here you go. Thanks!
This looks like a different model than the existing ones. Sadly, it
seems to be just as broken as previous models... :-(
One more thing. Does this ups support reporting temperature? Can you
tell this by looking at the log file I sent? Current
Citeren Mehmet Giritli :
I managed to install 2.6.0 on a Gentoo system and almost everything is
functioning properly with the usbhid-ups driver. I had to add "productid
= 0004" into my ups.conf. For monitoring and administration, I use the
cgi interface.
We've never seen this productid in for
Citeren Kevin :
Happy to dig as deep as you would like me to. (I would like to get
the CS 500 sorted out too though)
I think the only solution I can come up with to support (?) all known
APC models, is to not map the HID paths to 'load.on.delay' and to rely
on the UPS to provide a grace p
Citeren Kevin :
Sorry about that, the report descriptor is only reported at debug
level 3 (or higher). So I need the output of the below command
instead:
/path/to/usbhid-ups -DDD -a apc1500 > APC_Smart-UPS_1000.log 2>&1
Here it is.
Much better, thanks! Could you do the same for the CS
Citeren Jonathan Cunliffe :
[...]
Anyone any ideas...?
Someone posted a reply to your first message. Instead of reposting the
same message, you might try if following that reply might get you
further. Reading the manuals might also help.
Best regards, Arjen
--
Please keep list traffic o
Citeren Kevin :
./clients/upsrw -s ups.delay.shutdown=30 -u apcmon -p pass123 apc1500
OK
# ./clients/upsc apc1500
[...]
ups.delay.shutdown: 30
ups.delay.start: 250
..and apparently can be written as well.
Yes, but this value could also be changed before the patches. (See
previous post
Citeren Kevin :
Different
# ./clients/upsc apc1500
[...]
ups.delay.shutdown: 90
ups.delay.start: 250
This is what I expected to happen. The value of ups.delay.shutdown is
now read from the UPS...
./clients/upsrw -s ups.delay.shutdown=30 -u apcmon -p pass123 apc1500
OK
# ./client
Citeren Kevin :
#define APC_HID_VERSION "APC HID 0.95-patch2"
[...]
{ "ups.delay.shutdown", ST_FLAG_RW | ST_FLAG_STRING, 10,
"UPS.Output.APCShutdownAfterDelay", NULL, "%.0f",
HU_FLAG_QUICK_POLL, NULL },
I see my error now. The above line should be moved up to before the
first occure
Citeren Kevin :
[...]
but doesn't affect the initial value of ups.timer.shutdown (90)
after the shutdown.return command:
# ./clients/upscmd -u apcmon -p pass123 apc1500 shutdown.return
OK
# ./clients/upsc apc1500
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.
Citeren Kevin :
I'm posting the debug file again in case it gives any more clues. I
modified the version number to make sure I was actually using the
patched driver. I don't know, but these lines may be significant:
# grep "Value: 90" APC-1000.patched.txt
1.397898 Path: UPS.Output.AP
Citeren "Mike." :
Trying to build nut 2.6.0 on OpenBSD 4.8, I get a compiler error.
[...]
Making all in drivers
gmake[1]: Entering directory `/home/downloads/nut/nut-2.6.0/drivers'
gcc -DHAVE_CONFIG_H -I. -I../include-I../include -DSHUT_MODE
-g -O2 -Wall -Wsign-compare -MT newmge_sh
Citeren tubbi...@math.arizona.edu:
Debian Server (Lenny) running a Linux 2.6.26-2-686 SMP kernel.
NUT version 2.2.2-6.5 (Latest Lenny Stable)
[...]
Any insights?
Upgrade. We no longer support this version of NUT. Since nut-2.2.2 was
released, a lot of changes were made to the usbhid-ups
Citeren Kevin :
[apc1500]
driver=usbhid-ups
port=auto
ondelay=200
offdelay=1
Yes.
After restarting the driver, and running shutdown.return, the timers
are set to
90 and 200. (the values of ups.delay.shutdown and ups.delay.start)
REBOOT:-1 SHUT:-1 START:-1
R
Citeren Kevin :
On the Smart-UPS 1000, all the instant commands do more or less what
you would
expect. Looking at the timers using "upsc apc1500" I now see that:
shutdown.
load.off/load.off.delay both set the shutdown timer to 90, shuts down
after 90 seconds
It looks like this is t
Citeren Kevin Myers :
As far as I can tell from your previous message, it works (with
nut-2.6.0) for the Smart-UPS 1000, right?
No, although it does go into sleep mode if the power is off at the
right time, it doesn't cycle the power otherwise so the load will
not reboot after the shutdown.
Citeren Kevin :
It's a shame that I can't seem to get the up to date releases
working properly
on both of these UPS models, specially after seeing that it can be done,
apparently fairly simply, by sending the 0xff86007c code in both cases.
As far as I can tell from your previous message, it
Citeren Kevin :
0.686325 Initiating UPS shutdown
0.686340 upsdrv_shutdown...
0.686365 instcmd(shutdown.return, [NULL])
0.686382 find_nut_info: unknown info type: shutdown.return
This is normal. Some UPS'es (models that have a HID layer around an
essential serial i
Citeren Kevin :
Have you tried the latest version (nut-2.6.0) that was released only a
couple of days ago? Chances are that it might just work, since we have
seen reports about people running the CS 500 in recent years.
Yes, I have now had a chance to try this version and can confirm that it do
Citeren Kevin :
I have been using usb APC units (CS 500 and SmartUPS 1000) with nut
for some 6
years. I got this to work after extensive trawling of the net and found a fix
involving changing the source and recompiling usbhid-ups (or hidups
as it used
to be).
It's sad that you never submi
Citeren Mick :
While nut is running, my logs fill up with:
Jan 10 22:50:06 compaq usbhid-ups[5083]: libusb_get_report: No error
Jan 10 22:50:08 compaq usbhid-ups[5083]: libusb_get_report: No error
Jan 10 22:50:10 compaq usbhid-ups[5083]: libusb_get_report: No error
Jan 10 22:50:12 compaq usbhid
Citeren Mick :
[ snip ]
0.171361 refresh_report_buffer: expected 4 bytes, but got 8 instead
0.171403 Path: UPS.PowerSummary.DelayBeforeStartup, Type:
Feature, ReportID: 0x11, Offset: 0, Size: 24, Value: 0.00
0.171446 Report descriptor retrieved (Reportlen = 412)
0.17
Citeren Charles Lepple :
Technically, HID only needs to be specified on the interface class
(device class can be 0), so this descriptor is correct in that regard.
If the device is auto detected by Windows and Apple, it is quite
possible that this is indeed a HID PDC device.
Not sure why i
Citeren Kjell Claesson :
So start to send the output of:
lsusb -v
Cut out the part about the ups, and we have a look on it.
Make that
lsusb -v -d 075d:0300
to save yourself the trouble of weeding out the interesting stuff from
the other USB devices (we already know the VID:PID combin
Citeren Zach La Celle :
After setting the variable, the only further information I have is this:
upsd: free(): invalid pointer: 0x01d20f30 ***
Segmentation fault
Try again with debug level set to -DDD. This might provide a little
more context of where this occurs.
Best regards, Arj
Citeren Alexander Todorov :
You'll see in the above output that your UPS doesn't report battery
charge. The
blazer_usb driver can attempt to guestimate the charge remaining (see 'man 8
blazer'), but since the UPS doesn't report the load either, this will not be
nearly good enough to base a dec
Citeren Alexander Todorov :
# upsc powerwalker
battery.voltage: 24.60
battery.voltage.nominal: 24.0
beeper.status: enabled
device.type: ups
driver.name: blazer_usb
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.vendorid: 0665
driver.version: 2.4.3
driver.version.in
It's attached to this message. My apologies...
Best regards, Arjen
--
Please keep list traffic on the list (off-list replies will be rejected)
Desc: Using suspend to disk
File: suspend-to-disk.txt
Date: 29 December 2008
Auth: Arjen de Korte
Support for suspend to RAM and suspend to dis
1 - 100 of 1026 matches
Mail list logo
