Re: [Nut-upsuser] driver looking for MAXIM MXE II

2012-11-26 Thread Walter O. Dari

El 24/11/12 12:49, Arnaud Quette escribió:

You will need at least 2.6.4 for this unit, but it's really blazer_usb.


Ok, I'll try ...


Thanks,
Walter





Cheers,
Arnaud
(sent from my S3... please excuse my brevity)

Le 23 nov. 2012 09:40, "Walter O. Dari" mailto:wlin...@gmail.com>> a écrit :

Results:

wodari@svrsw2:/usr/local/__MonitorSoftware$ lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 06da:0201 Phoenixtec Power Co., Ltd
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


1
--__--__
ups.conf

[maxim]
    driver = blazer_usb
    port = auto
    desc = "SW servers"


wodari@svrsw2:~$ /sbin/upsdrvctl start
Network UPS Tools - UPS driver controller 2.4.3
Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.4.3)
No supported devices found. Please check your device availability
with 'lsusb'
and make sure you have an up-to-date version of NUT. If this does
not help,
try running the driver with at least 'subdriver', 'vendorid' and
'productid'
options specified. Please refer to the man page for details about
these options
(man 8 blazer).

Driver failed to start (exit status=1)
--__--__

2
--__--__
ups.conf

[maxim]
    driver = megatec_usb
    port = auto
    desc = "SW servers"


wodari@svrsw2:~$ /sbin/upsdrvctl start
Network UPS Tools - UPS driver controller 2.4.3
Network UPS Tools - Megatec protocol driver 1.6 (2.4.3)
Serial-over-USB transport layer 0.10
No supported devices found. Please check your device availability
with 'lsusb'
and make sure you have an up-to-date version of NUT. If this does
not help,
try running the driver with at least 'vendorid' and 'subdriver' options
specified. Please refer to the man page for details about these options
(man 8 megatec_usb).
Please report your results to the NUT user's mailing list
mailto:nut-upsuser@lists.alioth.debian.org>>.

Driver failed to start (exit status=1)
--__--__

3
--__--__
ups.conf

[maxim]
    driver = bcmxcp_usb
    port = auto
    desc = "SW servers"


wodari@svrsw2:~$ /sbin/upsdrvctl start
Network UPS Tools - UPS driver controller 2.4.3
Network UPS Tools - BCMXCP UPS driver 0.23 (2.4.3)
USB communication subdriver 0.18
Can't open POWERWARE USB device, retrying ...
Can't open POWERWARE USB device, retrying ...
Can't open POWERWARE USB device, retrying ...
--__--__

4
--__--__
ups.conf

[maxim]
    driver = tripplite_usb
    port = auto
    desc = "SW servers"


wodari@svrsw2:~$ /sbin/upsdrvctl start
Network UPS Tools - UPS driver controller 2.4.3
Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.4.3)
Warning: This is an experimental driver.
Some features may not function correctly.

No matching USB/HID UPS found
Driver failed to start (exit status=1)
--__--__


More info...

I'm use Debian Squeeze

wodari@svrsw2:~$ uname -a
Linux svrsw2 2.6.32-5-amd64 #1 SMP Sun Sep 23 10:07:46 UTC 2012
x86_64 GNU/Linux

wodari@svrsw2:~$ upsrw maxim
Can't connect: Connection failure: Connection refused

wodari@svrsw2:~$ upscmd -l maxim
Error: Connection failure: Connection refused



Walter




El 23/11/12 04:18, Arnaud Quette escribió:

HolÃ

Try blazer_usb. Please report back if everything is working as per
http://www.networkupstools.__org/stable-hcl.html#footnotes


Cheers
Arnaud
(sent from my S3... please excuse my brevity)

Le 21 nov. 2012 23:13, "Walter O. Dari" mailto:wlin...@gmail.com>
>> a
écrit :

    Hello:

    I have a UPS model MXE II MAXIM brand online, 3500VA 2100W.
    Connects to the PC by a USB 2.0 port.
    I wanted to use nut, but this brand is not on the list of
nut drivers.

    lsusb returns:

 

Re: [Nut-upsuser] APC UPS: replacement battery always triggers shutdown

2012-11-26 Thread JS


I forgot to mention that I was not able to test
the procedure in #1 below successfully because my 
UPS never shows more than 65% battery charge anymore. This may be the result of 
a
failed calibration run.

Jack




 From: JS 
To: Arnaud Quette ; Kastus Shchuka ; 
Michal Soltys  
Cc: "nut-upsuser@lists.alioth.debian.org"  
Sent: Monday, November 26, 2012 9:38 PM
Subject: Re: [Nut-upsuser] APC UPS: replacement battery always triggers shutdown
 

 Arnaud,


I haven't been able to test Kastus' suggestion because my UPS (APC Back-UPS ES 
750) doesn't appear on the list

and I didn't want to take take the risk of disabling it by mistake.


However, I did make a bit of progress on this:


1. There is a more detailed procedure than the one in NUT FAQ #37 in: 
http://excessups.com/blog/manual-runtime-calibration-apc-ups/ 

     which is summarized as:


    Follow these steps to do a proper manual calibration on your APC UPS:

    1. Battery must be at 100% capacity when the Runtime Calibration is 
initiated/started. (charge the UPS for 24hours prior)
    2. The UPS must have 30-34% load on it during the calibration (Constant 
load, try: lamps, computers, monitors. Measure load % by PowerChute)
    3. Disconnect the serial/USB comm cable from the UPS (you don’t want 
PowerChute to shut down equipment)
    4. The battery must be discharged completely  (unplug UPS from wall outlet, 
let the UPS to shut off completely due to a discharged battery).
 
   5. Remove the attached load (ie – lights, computers)
    6. Let the UPS charge for 8 hours while OFF (plug back into utility power, 
press OFF button when UPS turns ON)
    7. Turn on UPS (run time should now be accurate)

 

2. the man page for the  usbhid-ups has an alternative, based on the battery 
charge instead of the estimated runtime:

      "New" units have battery.runtime.low, but depending on battery 
quality, firmware version, calibration and UPS load - this variable can be 
underestimated quite
      a bit - especially right after going into OB state. This in turn can 
cause LB to be asserted, which under normal conditions will cause NUT to 
initiate the
      shutdown. You might want to disable this condition entirely, when 
relying on ignorelb option (this was actually the main
 motivation behind introduction of
      such feature).

      Simple example:

      [apc]
      ignorelb
      override.battery.charge.low = 15
      override.battery.runtime.low = -1



I've been using this config and it works fine, allowing my system to keep 
running during the occasional 30-60 second AC power losses we see:
           [apc]
            driver = usbhid-ups
             port = auto
            desc = "APC Back-UPS ES 750"
            ignorelb
            override.battery.charge.low = 20
     
       override.battery.runtime.low = -1


My system is running debian (testing distribution) and unfortunately the 
apcupsd package with apcsmart conflicts with nut-client. I tried installing it
but could not get it configured properly for the Back-UPS ES 750 (which has 
only a USB cable with a db-9 connector for access).

thanks,
--jack



 From: Arnaud Quette 
To: JS ; Kastus Shchuka ; Michal Soltys 
 
Cc: nut-upsuser@lists.alioth.debian.org 
Sent: Monday, November 26, 2012 2:42 PM
Subject: Re: [Nut-upsuser] APC UPS: replacement battery always triggers shutdown
 

Michal, Kastus, Jack,

I have a similar request sitting in the Features requests for years:
https://alioth.debian.org/tracker/index.php?func=detail&aid=304645&group_id=30602&atid=411545
http://lists.alioth.debian.org/pipermail/nut-upsdev/2006-June/000938.html

would you please unite your efforts and bring a patch for NUT FAQ (or the 
driver(s))?

thanks a lot!
Arnaud
-- 
NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org/
Free Software Developer - http://arnaud.quette.fr/


2012/11/11 Kastus Shchuka 

On Sun, Nov 11, 2012 at 07:21:35AM -0800, JS wrote:
>> I followed this procedure (charging the battery fully, letting it drain off 
>> a token load while UPS is grounded on a surge protector) but it did not help.
>>
>> Perhaps I missed something running this procedure; if anyone has suggestions 
>> for solving this they'd be greatly appreciated.
>
>I've been in the same situation after replacing the battery in SC620I model.
>
>Then I found http://old.nabble.com/SmartUPS-and-new-battery-td20678966.html
>and followed the procedure:
>
>1. Shutdown the apcupsd daemon.
>2. Run apctest
>3. Choose option 6 to enter terminal mode
>4. Enter Y (UPS should respond SM)
>5. Enter 1 (one, not el; wait 4 seconds)
>6. Enter 1 (one, not el; UPS should respond PROG)
>7. Enter 0 (zero, not oh; UPS should respond with current constant)
>8. Enter + (plus) or - (minus) to increment/decrement the va

Re: [Nut-upsuser] APC UPS: replacement battery always triggers shutdown

2012-11-26 Thread JS
 Arnaud,


I haven't been able to test Kastus' suggestion because my UPS (APC Back-UPS ES 
750) doesn't appear on the list

and I didn't want to take take the risk of disabling it by mistake.


However, I did make a bit of progress on this:


1. There is a more detailed procedure than the one in NUT FAQ #37 in: 
http://excessups.com/blog/manual-runtime-calibration-apc-ups/ 

     which is summarized as:


    Follow these steps to do a proper manual calibration on your APC UPS:

    1. Battery must be at 100% capacity when the Runtime Calibration is 
initiated/started. (charge the UPS for 24hours prior)
    2. The UPS must have 30-34% load on it during the calibration (Constant 
load, try: lamps, computers, monitors. Measure load % by PowerChute)
    3. Disconnect the serial/USB comm cable from the UPS (you don’t want 
PowerChute to shut down equipment)
    4. The battery must be discharged completely  (unplug UPS from wall outlet, 
let the UPS to shut off completely due to a discharged battery).
    5. Remove the attached load (ie – lights, computers)
    6. Let the UPS charge for 8 hours while OFF (plug back into utility power, 
press OFF button when UPS turns ON)
    7. Turn on UPS (run time should now be accurate)

 

2. the man page for the  usbhid-ups has an alternative, based on the battery 
charge instead of the estimated runtime:

      "New" units have battery.runtime.low, but depending on battery 
quality, firmware version, calibration and UPS load - this variable can be 
underestimated quite
      a bit - especially right after going into OB state. This in turn can 
cause LB to be asserted, which under normal conditions will cause NUT to 
initiate the
      shutdown. You might want to disable this condition entirely, when 
relying on ignorelb option (this was actually the main motivation behind 
introduction of
      such feature).

      Simple example:

      [apc]
      ignorelb
      override.battery.charge.low = 15
      override.battery.runtime.low = -1



I've been using this config and it works fine, allowing my system to keep 
running during the occasional 30-60 second AC power losses we see:
           [apc]
            driver = usbhid-ups
             port = auto
            desc = "APC Back-UPS ES 750"
            ignorelb
            override.battery.charge.low = 20
            override.battery.runtime.low = -1


My system is running debian (testing distribution) and unfortunately the 
apcupsd package with apcsmart conflicts with nut-client. I tried installing it
but could not get it configured properly for the Back-UPS ES 750 (which has 
only a USB cable with a db-9 connector for access).

thanks,
--jack



 From: Arnaud Quette 
To: JS ; Kastus Shchuka ; Michal Soltys 
 
Cc: nut-upsuser@lists.alioth.debian.org 
Sent: Monday, November 26, 2012 2:42 PM
Subject: Re: [Nut-upsuser] APC UPS: replacement battery always triggers shutdown
 

Michal, Kastus, Jack,

I have a similar request sitting in the Features requests for years:
https://alioth.debian.org/tracker/index.php?func=detail&aid=304645&group_id=30602&atid=411545
http://lists.alioth.debian.org/pipermail/nut-upsdev/2006-June/000938.html

would you please unite your efforts and bring a patch for NUT FAQ (or the 
driver(s))?

thanks a lot!
Arnaud
-- 
NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr


2012/11/11 Kastus Shchuka 

On Sun, Nov 11, 2012 at 07:21:35AM -0800, JS wrote:
>> I followed this procedure (charging the battery fully, letting it drain off 
>> a token load while UPS is grounded on a surge protector) but it did not help.
>>
>> Perhaps I missed something running this procedure; if anyone has suggestions 
>> for solving this they'd be greatly appreciated.
>
>I've been in the same situation after replacing the battery in SC620I model.
>
>Then I found http://old.nabble.com/SmartUPS-and-new-battery-td20678966.html
>and followed the procedure:
>
>1. Shutdown the apcupsd daemon.
>2. Run apctest
>3. Choose option 6 to enter terminal mode
>4. Enter Y (UPS should respond SM)
>5. Enter 1 (one, not el; wait 4 seconds)
>6. Enter 1 (one, not el; UPS should respond PROG)
>7. Enter 0 (zero, not oh; UPS should respond with current constant)
>8. Enter + (plus) or - (minus) to increment/decrement the value
>9. Enter R to reprogram constant value (UPS should respond Bye)
>10. Enter Y (UPS should respond SM)
>11. Enter 0 (zero, not oh; UPS should respond with the new constant)
>12. Enter Esc to exit terminal mode
>13. Choose option 7 to exit apctest.
>
>The value to store in the register 0 differs by the model. There is a table
>posted in the middle of the thread. I hope your model is listed there.
>If you cannot find your model, you may want to try experimenting with different
>valu

Re: [Nut-upsuser] CyberPower DX600E won't switch up after power

2012-11-26 Thread Arnaud Quette
2012/11/26 Franck 

> On 2012-11-26 19:34, Arnaud Quette wrote:
>
>> 2012/11/26 Franck 
>>
>>  On 2012-11-26 18:39, Arnaud Quette wrote:
>>>
>>>  Hi Franck

 2012/11/23 Franck 

  Subject: [Nut-upsuser] CyberPower DX600E wont switch up after
>>
>> power
>> is back
>> Message-ID: 
>> <3c530815d1ea602efdfec0d67eb1e**0...@secretfatty.net<3c530815d1ea602efdfec0d67eb1e...@secretfatty.net>
>> [1]
>> [1]>
>>
>> Content-Type: text/plain; charset=UTF-8; format=flowed
>>
>> Hello
>> I have an issue with an CyberPower DX600E,
>> it doesnt switch up when the power is back; after it has been
>>
>> unloaded;
>> is it because of one of those variables ?
>> regards
>> Franck
>>
>> #upsc myups
>> battery.charge: 100
>> battery.charge.low: 10
>> battery.charge.warning: 20
>> battery.mfr.date: CPS
>> battery.runtime: 1380
>> battery.runtime.low: 300
>> battery.type: PbAcid
>> battery.voltage: 4.7
>> battery.voltage.nominal: 12
>> device.mfr: CPS
>> device.model: DX600E
>> device.type: ups
>> driver.name [2] [2]: usbhid-ups
>>
>>
>> driver.parameter.pollfreq: 30
>> driver.parameter.pollinterval: 2
>> driver.parameter.port: auto
>> driver.version: 2.4.3
>> driver.version.data: CyberPower HID 0.3
>> driver.version.internal: 0.34
>> input.transfer.high: 0
>> input.transfer.low: 0
>> input.voltage: 230.0
>> input.voltage.nominal: 230
>> output.voltage: 238.0
>> ups.beeper.status: enabled
>> ups.delay.shutdown: 20
>> ups.delay.start: 30
>> ups.load: 31
>> ups.mfr: CPS
>> ups.model: DX600E
>> ups.productid: 0501
>> ups.realpower.nominal: 360
>> ups.status: OL
>> ups.timer.shutdown: -60
>> ups.timer.start: 0
>> ups.vendorid: 0764
>>
>
> Am i suppose to run a "shutdown.return" command ?
>
> Does it make sense to do it in the script triggering (for
> example
> when receiving "low battery" ?
>

 depending on your exact OS / distros, this should be handled by
 NUT
 initscripts and probably the halt one.
  what is yours?

>>>
>>> Thanks for your reply Arnaud;
>>> I have a debian squeeze.
>>>
>>
>> looking again at your upsc output, I suspect more an issue with the
>> UPS than with Squeeze.
>>
>> a good test would be to:
>> - remove your PC from the UPS,
>>
>
> Just to check I understood well:
> You mean I would plug the PC directly to the power source, and connect the
> UPS with the PC only using the USB ?


right. we need to monitor the UPS while it's shutting down...


>  - stop NUT after the reboot,
>> - restart the driver in debug more (/lib/nut/usbhid-ups -D myups)
>> and upsd (simply type "upsd") in another term
>>  - then execute "upscmd -u ... -p ... myups shutdown.return"
>> - leave it half a minute, then Ctrl+C in the driver term.
>> and send back the driver output, in compressed form.
>> you can then restart everything as usual...
>>
>> Id like to see how the data behind "ups.timer.shutdown" and
>> "ups.timer.start" behave.
>>
>>
>
-- Arno
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CyberPower DX600E won't switch up after power

2012-11-26 Thread Franck

On 2012-11-26 19:34, Arnaud Quette wrote:

2012/11/26 Franck 


On 2012-11-26 18:39, Arnaud Quette wrote:


Hi Franck

2012/11/23 Franck 


Subject: [Nut-upsuser] CyberPower DX600E wont switch up after

power
        is back
Message-ID: <3c530815d1ea602efdfec0d67eb1e...@secretfatty.net
[1]
[1]>

Content-Type: text/plain; charset=UTF-8; format=flowed

Hello
I have an issue with an CyberPower DX600E,
it doesnt switch up when the power is back; after it has been

unloaded;
is it because of one of those variables ?
regards
Franck

#upsc myups
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 20
battery.mfr.date: CPS
battery.runtime: 1380
battery.runtime.low: 300
battery.type: PbAcid
battery.voltage: 4.7
battery.voltage.nominal: 12
device.mfr: CPS
device.model: DX600E
device.type: ups
driver.name [2] [2]: usbhid-ups

driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.version: 2.4.3
driver.version.data: CyberPower HID 0.3
driver.version.internal: 0.34
input.transfer.high: 0
input.transfer.low: 0
input.voltage: 230.0
input.voltage.nominal: 230
output.voltage: 238.0
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.load: 31
ups.mfr: CPS
ups.model: DX600E
ups.productid: 0501
ups.realpower.nominal: 360
ups.status: OL
ups.timer.shutdown: -60
ups.timer.start: 0
ups.vendorid: 0764


Am i suppose to run a "shutdown.return" command ?

Does it make sense to do it in the script triggering (for
example
when receiving "low battery" ?


depending on your exact OS / distros, this should be handled by
NUT
initscripts and probably the halt one.
 what is yours?


Thanks for your reply Arnaud;
I have a debian squeeze.


looking again at your upsc output, I suspect more an issue with the
UPS than with Squeeze.

a good test would be to:
- remove your PC from the UPS,


Just to check I understood well:
You mean I would plug the PC directly to the power source, and connect 
the UPS with the PC only using the USB ?



- stop NUT after the reboot,
- restart the driver in debug more (/lib/nut/usbhid-ups -D myups)
and upsd (simply type "upsd") in another term
 - then execute "upscmd -u ... -p ... myups shutdown.return"
- leave it half a minute, then Ctrl+C in the driver term.
and send back the driver output, in compressed form.
you can then restart everything as usual...

Id like to see how the data behind "ups.timer.shutdown" and
"ups.timer.start" behave.




---
http://secretfatty.net

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] APC UPS: replacement battery always triggers shutdown

2012-11-26 Thread Arnaud Quette
Michal, Kastus, Jack,

I have a similar request sitting in the Features requests for years:
https://alioth.debian.org/tracker/index.php?func=detail&aid=304645&group_id=30602&atid=411545
http://lists.alioth.debian.org/pipermail/nut-upsdev/2006-June/000938.html

would you please unite your efforts and bring a patch for NUT FAQ (or the
driver(s))?

thanks a lot!
Arnaud
-- 
NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr

2012/11/11 Kastus Shchuka 

> On Sun, Nov 11, 2012 at 07:21:35AM -0800, JS wrote:
> > I followed this procedure (charging the battery fully, letting it drain
> off a token load while UPS is grounded on a surge protector) but it did not
> help.
> >
> > Perhaps I missed something running this procedure; if anyone has
> suggestions for solving this they'd be greatly appreciated.
>
> I've been in the same situation after replacing the battery in SC620I
> model.
>
> Then I found
> http://old.nabble.com/SmartUPS-and-new-battery-td20678966.html
> and followed the procedure:
>
> 1. Shutdown the apcupsd daemon.
> 2. Run apctest
> 3. Choose option 6 to enter terminal mode
> 4. Enter Y (UPS should respond SM)
> 5. Enter 1 (one, not el; wait 4 seconds)
> 6. Enter 1 (one, not el; UPS should respond PROG)
> 7. Enter 0 (zero, not oh; UPS should respond with current constant)
> 8. Enter + (plus) or - (minus) to increment/decrement the value
> 9. Enter R to reprogram constant value (UPS should respond Bye)
> 10. Enter Y (UPS should respond SM)
> 11. Enter 0 (zero, not oh; UPS should respond with the new constant)
> 12. Enter Esc to exit terminal mode
> 13. Choose option 7 to exit apctest.
>
> The value to store in the register 0 differs by the model. There is a table
> posted in the middle of the thread. I hope your model is listed there.
> If you cannot find your model, you may want to try experimenting with
> different
> values.
>
> In my case, after updating register 0, my UPS is back to 42 min runtime.
>
> Hope this helps.
>
> Kastus
>
>
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CyberPower DX600E won't switch up after power

2012-11-26 Thread Arnaud Quette
2012/11/26 Franck 

> On 2012-11-26 18:39, Arnaud Quette wrote:
>
>> Hi Franck
>>
>> 2012/11/23 Franck 
>>
>>  Subject: [Nut-upsuser] CyberPower DX600E wont switch up after

 power
 is back
 Message-ID: 
 <3c530815d1ea602efdfec0d67eb1e**0...@secretfatty.net<3c530815d1ea602efdfec0d67eb1e...@secretfatty.net>
 [1]>

 Content-Type: text/plain; charset=UTF-8; format=flowed

 Hello
 I have an issue with an CyberPower DX600E,
 it doesnt switch up when the power is back; after it has been

 unloaded;
 is it because of one of those variables ?
 regards
 Franck

 #upsc myups
 battery.charge: 100
 battery.charge.low: 10
 battery.charge.warning: 20
 battery.mfr.date: CPS
 battery.runtime: 1380
 battery.runtime.low: 300
 battery.type: PbAcid
 battery.voltage: 4.7
 battery.voltage.nominal: 12
 device.mfr: CPS
 device.model: DX600E
 device.type: ups
 driver.name [2]: usbhid-ups

 driver.parameter.pollfreq: 30
 driver.parameter.pollinterval: 2
 driver.parameter.port: auto
 driver.version: 2.4.3
 driver.version.data: CyberPower HID 0.3
 driver.version.internal: 0.34
 input.transfer.high: 0
 input.transfer.low: 0
 input.voltage: 230.0
 input.voltage.nominal: 230
 output.voltage: 238.0
 ups.beeper.status: enabled
 ups.delay.shutdown: 20
 ups.delay.start: 30
 ups.load: 31
 ups.mfr: CPS
 ups.model: DX600E
 ups.productid: 0501
 ups.realpower.nominal: 360
 ups.status: OL
 ups.timer.shutdown: -60
 ups.timer.start: 0
 ups.vendorid: 0764

>>>
>>> Am i suppose to run a "shutdown.return" command ?
>>>
>>> Does it make sense to do it in the script triggering (for example
>>> when receiving "low battery" ?
>>>
>>
>> depending on your exact OS / distros, this should be handled by NUT
>> initscripts and probably the halt one.
>>  what is yours?
>>
>>
> Thanks for your reply Arnaud;
> I have a debian squeeze.
>

looking again at your upsc output, I suspect more an issue with the UPS
than with Squeeze.

a good test would be to:
- remove your PC from the UPS,
- stop NUT after the reboot,
- restart the driver in debug more (/lib/nut/usbhid-ups -D myups) and
upsd (simply type "upsd") in another term
- then execute "upscmd -u ... -p ... myups shutdown.return"
- leave it half a minute, then Ctrl+C in the driver term.
and send back the driver output, in compressed form.
you can then restart everything as usual...

I'd like to see how the data behind "ups.timer.shutdown" and
"ups.timer.start" behave.

cheers,
Arnaud
-- 
NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] MEC0003 protocol support

2012-11-26 Thread Arnaud Quette
2012/11/21 Walshe, John (DCOR) 

> Hi Folks,
>
> I’m trying to use a ZIGOR Danubio 2000 ups with NUT on Debian squeeze
> (AMD64).
>
> OS/NUT are all the latest official release (as of last week) with NUT
> installed from packages.
>
> ** **
>
> As the usb descriptor presents MEC (and the Fry’s electronics) I chose to
> use the blazer_usb driver.
>
> ** **
>
> All appears to work well excepting that the UPS does not appear to accept
> the shutdown instcmd to turn off the ups outputs at the end of the shutdown
> process. The UPS remains on until the batteries completely drain and it has
> to turn off to protect itself.
>
> Apart from that, reporting, messaging, shutdown process etc  all works
> well.
>
> ** **
>
> ** **
>
> On shutdown I can see 
>
> instcmd: command [shutdown.stop] handled
>
> instcmd: command [shutdown.return] handled
>
> Shutting down in 30 seconds
>
> Waiting for UPS to cut power.
>
> Will now halt.
>
> ** **
>
> The PC turns off put UPS stays running until batteries run out.
>
> ** **
>
> So I can see that the driver issues the command and thinks that it is
> “handled”. Looking at it with higher debug level I can see that the driver
> reports a “USB no ACK” to these instcmds. Checking the USB with wireshark
> shows that this text string originated in the UPS, ie it is a text string
> returned in response to the instcmds.
>
> ** **
>
> Looking closer at the USB descriptor it presents MEC0003 rather than the
> MEC0002 that I see all over the fora.
>
> ** **
>
> So it would appear that there is a new variety of MEC protocol. 
>
> Has anyone else seen this?
>
> Is there any work ongoing with this MEC0003 protocol?
>
> What can I do to help this cause? (bear in mind I’m a Linux newbie – but
> with good backup J )
>

could you please send back a driver output, debug level 5 (i.e -D),
including a shutdown.return command sent from upscmd.
note that, for this test, you should remove your system from the UPS, or
send directly a shutdown.stop afterward.

I'm also interested in the wireshark snoop.

cheers,
Arnaud
-- 
NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CyberPower DX600E won't switch up after power

2012-11-26 Thread Franck

On 2012-11-26 18:39, Arnaud Quette wrote:

Hi Franck

2012/11/23 Franck 


Subject: [Nut-upsuser] CyberPower DX600E wont switch up after
power
        is back
Message-ID: <3c530815d1ea602efdfec0d67eb1e...@secretfatty.net
[1]>
Content-Type: text/plain; charset=UTF-8; format=flowed

Hello
I have an issue with an CyberPower DX600E,
it doesnt switch up when the power is back; after it has been
unloaded;
is it because of one of those variables ?
regards
Franck

#upsc myups
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 20
battery.mfr.date: CPS
battery.runtime: 1380
battery.runtime.low: 300
battery.type: PbAcid
battery.voltage: 4.7
battery.voltage.nominal: 12
device.mfr: CPS
device.model: DX600E
device.type: ups
driver.name [2]: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.version: 2.4.3
driver.version.data: CyberPower HID 0.3
driver.version.internal: 0.34
input.transfer.high: 0
input.transfer.low: 0
input.voltage: 230.0
input.voltage.nominal: 230
output.voltage: 238.0
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.load: 31
ups.mfr: CPS
ups.model: DX600E
ups.productid: 0501
ups.realpower.nominal: 360
ups.status: OL
ups.timer.shutdown: -60
ups.timer.start: 0
ups.vendorid: 0764


Am i suppose to run a "shutdown.return" command ?

Does it make sense to do it in the script triggering (for example
when receiving "low battery" ?


depending on your exact OS / distros, this should be handled by NUT
initscripts and probably the halt one.
 what is yours?



Thanks for your reply Arnaud;
I have a debian squeeze.


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CyberPower DX600E won't switch up after power

2012-11-26 Thread Arnaud Quette
Hi Franck

2012/11/23 Franck 

> Subject: [Nut-upsuser] CyberPower DX600E won't switch up after power
>> is back
>> Message-ID: 
>> <3c530815d1ea602efdfec0d67eb1e**0...@secretfatty.net<3c530815d1ea602efdfec0d67eb1e...@secretfatty.net>
>> >
>> Content-Type: text/plain; charset=UTF-8; format=flowed
>>
>> Hello
>> I have an issue with an CyberPower DX600E,
>> it doesn't switch up when the power is back; after it has been
>> unloaded;
>> is it because of one of those variables ?
>> regards
>> Franck
>>
>> #upsc myups
>> battery.charge: 100
>> battery.charge.low: 10
>> battery.charge.warning: 20
>> battery.mfr.date: CPS
>> battery.runtime: 1380
>> battery.runtime.low: 300
>> battery.type: PbAcid
>> battery.voltage: 4.7
>> battery.voltage.nominal: 12
>> device.mfr: CPS
>> device.model: DX600E
>> device.type: ups
>> driver.name: usbhid-ups
>> driver.parameter.pollfreq: 30
>> driver.parameter.pollinterval: 2
>> driver.parameter.port: auto
>> driver.version: 2.4.3
>> driver.version.data: CyberPower HID 0.3
>> driver.version.internal: 0.34
>> input.transfer.high: 0
>> input.transfer.low: 0
>> input.voltage: 230.0
>> input.voltage.nominal: 230
>> output.voltage: 238.0
>> ups.beeper.status: enabled
>> ups.delay.shutdown: 20
>> ups.delay.start: 30
>> ups.load: 31
>> ups.mfr: CPS
>> ups.model: DX600E
>> ups.productid: 0501
>> ups.realpower.nominal: 360
>> ups.status: OL
>> ups.timer.shutdown: -60
>> ups.timer.start: 0
>> ups.vendorid: 0764
>>
>>
>>
> Am i suppose to run a "shutdown.return" command ?
>
> Does it make sense to do it in the script triggering (for example when
> receiving "low battery" ?
>

depending on your exact OS / distros, this should be handled by NUT
initscripts and probably the halt one.
what is yours?

some generic info on how shutdown works with NUT:
http://www.networkupstools.org/docs/user-manual.chunked/ar01s06.html#Shutdown_design

cheers,
Arnaud
-- 
NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] cheap UPS for NUT?

2012-11-26 Thread Arnaud Quette
2012/11/23 Periko Support 

>  Hi guys.
>

Hi

 My first post, I had see the list of compatible UPS devices, I have
> use APC BackupUPS 550, 450, but does cost +55 bucks, exist other model
> or brand usb/serial that someone have working and a little cheaper
> that APC?
>
> Thanks!!!
>

the cheapest units supported by NUT are the ones supported by
blazer_{ser,usb} drivers, and sold by more than 75 manufacturers (this is
only the number of brands supported by NUT though!):
http://www.networkupstools.org/stable-hcl.html

cheers,
Arnaud
-- 
NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Unable to disable beeper on Powercom Imperial IMP-525AP [SOLVED]

2012-11-26 Thread Arnaud Quette
2012/11/23 Sergey Talchuk 

> Hi Arnaud,
>

Hi Sergey,

I received several replies from technical support.
> It turned out that according to the UPS serial number it had been
> manufactured in 2012. So, the device should support the ability to disable
> the beeper.
> But still I can not disable the beeper using the latest version of UPSMON
> Plus in Windows:
> http://www.pcm.ru/data/download/public/soft/setup_upsmon_v2.9.rar (don't
> know why; the device was tested on XP/Win7 with different USB cables)
> [WORKAROUND]
> However, beeper can be disabled with the button on the UPS (except when
> the device starts and the battery capacity is 0 the beeper should/will work)
> NUT gets the correct value now:
>
> $ upsc powercom ups.beeper.status
> disabled
>
> Thank you,
> Sergey
>

thanks for this info, it will probably be useful to other NUT Powercom
users.

cheers,
Arnaud
-- 
NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr

On Thu, Nov 1, 2012 at 3:07 PM, Arnaud Quette  wrote:
>
>>
>> 2012/10/31 Sergey Talchuk 
>>
>>> Hi Arnaud,
>>>
>>
>> Hi Sergey,
>>
>> Unfortunately, I did not get an answer from the manufacturer's support.
>>> However, in the forum I got to know that the ability to disable the
>>> beeper had been added in 2010 only.
>>> http://forum.pcm.ru/viewtopic.php?f=4&t=12642
>>> http://forum.pcm.ru/viewtopic.php?f=10&t=10376
>>>
>>> So UPS devices which where built after 2010 should support this option.
>>>
>>
>> thanks for sharing this info with us.
>> I assume yours was built before 2010.
>>
>> cheers,
>> Arnaud
>> --
>> Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org
>> Debian Developer - http://www.debian.org
>> Free Software Developer - http://arnaud.quette.fr
>>
>>
>
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

[Nut-upsuser] New intermediate Windows binaries release - 2.6.5-4

2012-11-26 Thread FredericBohe
Hello,

There is a new intermediate Windows binaries release available at :

http://www.networkupstools.org/package/windows/NUT-Installer-2.6.5-4.msi

This is based on SVN trunk revision 3774.

This release include the porting of NSS. It uses NSS for SSL connections now, 
rather than OpenSSL previously.
This release also fix a crash at exit time.

Feedback is highly appreciated.

Regards,
Fred


--
Eaton Opensource Team - http://opensource.eaton.com


-

-


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser