Re: [Nut-upsuser] Zigor Ebro 650 compatibility

2012-08-08 Thread Martyn Hill
Arnaud Quette aquette.dev at gmail.com writes:

 
 2012/6/3 Chris Rees crees at freebsd.org:
  Hi all,
 
 Hi Chris,
 
  After some research I've found that this device should run with the
  blazer_usb driver.
 
  Jun  3 16:15:38 pegasus kernel: ugen0.4: vendor 0x0001 at usbus0
  Jun  3 16:15:38 pegasus kernel: uhid0: vendor 0x0001 product 0x,
  class 0/0, rev 1.00/1.00, addr 4 on usbus0
 
  However, even after shoehorning it;
 
  [crees at pegasus]/usr/local/libexec/nut% sudo ./blazer_usb -a zigor
  -D -x vendorid=0x0001 -x productid=0x -x subdriver=krauler
  Password:
  Network UPS Tools - Megatec/Q1 protocol USB driver 0.04
  (2.6.3-Unversioned directory)
    0.00     send_to_all: SETINFO driver.parameter.vendorid 0x0001
    0.13     send_to_all: SETINFO driver.parameter.productid 0x
    0.18     send_to_all: SETINFO driver.parameter.subdriver krauler
    0.20     debug level is '9'
    0.000874     language ID workaround enabled (using '0x409')
    0.001019     No appropriate HID device found
    0.001025     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).
 
  This is on FreeBSD with NUT updated to 2.6.3 (I've modified the port).
 

Hi Chris

Any chance you could share the FreeBSD port? Using the version (2.6.1) 
currently available in the ports tree, I can get a step closer than your tests 
above, but without the enhanced blazer_usb driver (0.0.4) in nut 2.6.3, I 
don't think I can get any further.


  The UPS comes with UPSilon, but it's several years (!) old and I can't
  even get it to install, let alone work.
 
  Have I sent enough info?  I'm willing to have a go at hacking the
  driver, but having trouble getting started.
 
  Chris
 
  [crees at pegasus]/usr/local/libexec/nut% grep -v 
^# /usr/local/etc/nut/ups.conf
 
  [zigor]
         port = auto
         driver = blazer_usb
         langid_fix = 0x409
         desc = Zigor UPS
         vendorid = 0001
         productid = 
 
 it's quite probably due to a permission issue.
 See 4) Permissions on 
http://people.freebsd.org/~thierry/nut_FreeBSD_HowTo.txt
 
 cheers,
 Arnaud

I got a little further than the above by ensuring that the default 'uucp' user 
configured in the FreeBSD port had RW access to the appropriate usb node, as 
per the advice above (thanks for linking it, Arnaud).

Regards,
Martyn Hill
London.





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

[Nut-upsuser] bcmxcp_usb can not communicate with Eaton Powerware 5110

2012-08-08 Thread Massimo Gais

 I'm going to go with the last option I have, and will replace this UPS
 with one that works with this combination of architecture and OS! :)


 yup, still an option ;)

Hello,

I have the same issue with Raspberry Pi (running 'raspbian') and
Powerware 5110, and I'd like to help to solve it, as I don't have the
priviledge to replace UPS :-). I'm moving my nut server from an old
NSLU2 with debian squeeze (where it was working properly) to RPi as I
need a miniserver with more memory to run also other tasks.

So, is there any debug information that I can provide to help ?

# uname -a
Linux raspi0 3.1.9+ #272 PREEMPT Tue Aug 7 22:51:44 BST 2012 armv6l GNU/Linux

# ldd bcmxcp_usb
/usr/lib/arm-linux-gnueabihf/libcofi_rpi.so (0x40148000)
libusb-0.1.so.4 = /lib/arm-linux-gnueabihf/libusb-0.1.so.4 (0x40151000)
libpthread.so.0 = /lib/arm-linux-gnueabihf/libpthread.so.0 (0x40024000)
libc.so.6 = /lib/arm-linux-gnueabihf/libc.so.6 (0x4016)
/lib/arm-linux-gnueabihf/ld-linux.so.3 = /lib/ld-linux-armhf.so.3 
(0x4005)

# dpkg --list | grep -E 'nut-server|libc6|raspi-copies-and-fills'
ii  libc6:armhf   2.13-33
Embedded GNU C Library: Shared libraries
ii  libc6-dev:armhf   2.13-33
Embedded GNU C Library: Development Libraries and Header Files
ii  nut-server2.6.4-1
network UPS tools - core system
ii  raspi-copies-and-fills0.1
Optimised memcpy/memset implementation for ARM11 used in Raspberry Pi


Cheers,
Massimo

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


Re: [Nut-upsuser] bcmxcp_usb can not communicate with Eaton Powerware 5110

2012-08-08 Thread Greg Vickers

On 08/08/12 20:19, Massimo Gais wrote:

I have the same issue with Raspberry Pi (running 'raspbian') and
Powerware 5110, and I'd like to help to solve it, as I don't have the
priviledge to replace UPS :-). I'm moving my nut server from an old
NSLU2 with debian squeeze (where it was working properly) to RPi as I
need a miniserver with more memory to run also other tasks.

So, is there any debug information that I can provide to help ?

# uname -a
Linux raspi0 3.1.9+ #272 PREEMPT Tue Aug 7 22:51:44 BST 2012 armv6l GNU/Linux

# ldd bcmxcp_usb
/usr/lib/arm-linux-gnueabihf/libcofi_rpi.so (0x40148000)
libusb-0.1.so.4 = /lib/arm-linux-gnueabihf/libusb-0.1.so.4 (0x40151000)
libpthread.so.0 = /lib/arm-linux-gnueabihf/libpthread.so.0 (0x40024000)
libc.so.6 = /lib/arm-linux-gnueabihf/libc.so.6 (0x4016)
/lib/arm-linux-gnueabihf/ld-linux.so.3 = /lib/ld-linux-armhf.so.3 
(0x4005)

# dpkg --list | grep -E 'nut-server|libc6|raspi-copies-and-fills'
ii  libc6:armhf   2.13-33
Embedded GNU C Library: Shared libraries
ii  libc6-dev:armhf   2.13-33
Embedded GNU C Library: Development Libraries and Header Files
ii  nut-server2.6.4-1
network UPS tools - core system
ii  raspi-copies-and-fills0.1
Optimised memcpy/memset implementation for ARM11 used in Raspberry Pi

Fantastic Massimo, thank you!  I have yet to replace my 5110, so if 
there is anything I can contribute, I will do.


It looks like the only difference between our systems is the kernel 
version (I've put the latest rasbian image on, which has kernel 
3.2.0-3-rpi).


Cheers,
Greg

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


Re: [Nut-upsuser] Plexus 800VA UPS on ReadyNAS Duo

2012-08-08 Thread Rojo Alvarez , Álex
Hi,
i've got similar problem with an OVISLINK 1000VA UPS on Debian.

I've tried to connect with it using different drivers and this is what I get 
with each of them:


[UPS]
driver = blazer_usb
vendorid = 0001
productid = 
port = auto
subdriver = phoenix

sweethome:~# /lib/nut/blazer_usb -a UPS -u root -DDD
Network UPS Tools - Megatec/Q1 protocol USB driver 0.08 (2.6.4)
   0.00 debug level is '3'
   0.171290 Checking device (1D6B/0001) (005/001)
   0.171346 - VendorID: 1d6b
   0.171353 - ProductID: 0001
   0.171358 - Manufacturer: Linux 3.2.0-2-amd64 uhci_hcd
   0.171363 - Product: UHCI Host Controller
   0.171368 - Serial Number: :00:10.3
   0.171372 - Bus: 005
   0.171377 Trying to match device
   0.171390 Device does not match - skipping
   0.171400 Checking device (1D6B/0001) (004/001)
   0.171420 - VendorID: 1d6b
   0.171426 - ProductID: 0001
   0.171431 - Manufacturer: Linux 3.2.0-2-amd64 uhci_hcd
   0.171436 - Product: UHCI Host Controller
   0.171441 - Serial Number: :00:10.2
   0.171446 - Bus: 004
   0.171450 Trying to match device
   0.171456 Device does not match - skipping
   0.171463 Checking device (1D6B/0001) (003/001)
   0.171482 - VendorID: 1d6b
   0.171488 - ProductID: 0001
   0.171493 - Manufacturer: Linux 3.2.0-2-amd64 uhci_hcd
   0.171497 - Product: UHCI Host Controller
   0.171502 - Serial Number: :00:10.1
   0.171507 - Bus: 003
   0.171511 Trying to match device
   0.171517 Device does not match - skipping
   0.171524 Checking device (0001/) (002/005)
   0.209728 - VendorID: 0001
   0.209738 - ProductID: 
   0.209743 - Manufacturer: ATCL FOR UPS
   0.209747 - Product: ATCL FOR UPS
   0.209752 - Serial Number: ATCL FOR UPS
   0.209756 - Bus: 002
   0.209761 Trying to match device
   0.209802 Device matches
   0.218750 Trying megatec protocol...
   2.011770 flush: No error
   2.015287 send: Q1
   3.059778 read: No error
   3.059984 blazer_status: short reply
   3.060090 Status read 1 failed
   4.107789 flush: No error
   4.111775 send: Q1
   5.163801 read: No error
   5.164007 blazer_status: short reply
   5.164116 Status read 2 failed
   6.211812 flush: No error
   6.215799 send: Q1
   7.259823 read: No error
   7.260021 blazer_status: short reply
   7.260129 Status read 3 failed
   7.260224 Trying mustek protocol...
   8.307832 flush: No error
   8.311822 send: QS
   9.355847 read: No error
   9.356053 blazer_status: short reply
   9.356168 Status read 1 failed
  10.403860 flush: No error
  10.407846 send: QS
  11.451870 read: No error
  11.452069 blazer_status: short reply
  11.452177 Status read 2 failed
  12.499880 flush: No error
  12.503868 send: QS
  13.547892 read: No error
  13.548090 blazer_status: short reply
  13.548198 Status read 3 failed
  13.548295 Trying megatec/old protocol...
  14.595901 flush: No error
  14.599892 send: D
  15.651914 read: No error
  15.652110 blazer_status: short reply
  15.652219 Status read 1 failed
  16.699927 flush: No error
  16.703915 send: D
  17.747941 read: No error
  17.748138 blazer_status: short reply
  17.748252 Status read 2 failed
  18.795947 flush: No error
  18.799938 send: D
  19.843961 read: No error
  19.844147 blazer_status: short reply
  19.844255 Status read 3 failed
  19.844350 Trying zinto protocol...
  20.891970 flush: No error
  20.895962 send: Q1
  21.939989 read: No error
  21.940197 blazer_status: short reply
  21.940307 Status read 1 failed
  22.988001 flush: No error
  22.991986 send: Q1
  24.036013 read: No error
  24.036220 blazer_status: short reply
  24.036329 Status read 2 failed
  25.084022 flush: No error
  25.088009 send: Q1
  26.132034 read: No error
  26.132245 blazer_status: short reply
  26.132354 Status read 3 failed
  26.132451 No supported UPS detected

--

[UPS]
driver = blazer_usb
vendorid = 0001
productid = 
port = auto
subdriver = cypress 


sweethome:~# /lib/nut/blazer_usb -a UPS -u root -DDD
Network UPS Tools - Megatec/Q1 protocol USB driver 0.08 (2.6.4)
   0.00 debug level is '3'
   0.171948 Checking device (1D6B/0001) (005/001)
   0.171999 - VendorID: 1d6b
   0.172005 - ProductID: 0001
   0.172010 - Manufacturer: Linux 3.2.0-2-amd64 uhci_hcd
   0.172015 - Product: UHCI Host Controller
   0.172020 - Serial Number: :00:10.3
   0.172025 - Bus: 005
   0.172029 Trying to match device
   0.172044 Device does not match - 

Re: [Nut-upsuser] Windows NUT shutdown UPS?

2012-08-08 Thread FredericBohe


-

-

_
 From: nut-upsuser-bounces+fredericbohe=eaton@lists.alioth.debian.org 
 [nut-upsuser-bounces+fredericbohe=eaton@lists.alioth.debian.org] on 
 behalf of Kris Jordan [nut...@sagebrushnetworks.com]
 Sent: Friday, July 27, 2012 11:11 PM
 To: nut-upsuser@lists.alioth.debian.org
 Subject: Re: [Nut-upsuser] Windows NUT shutdown UPS?
 
 Kris Jordan wrote, On 7/27/2012 9:39 AM:
 
  fredericb...@eaton.com wrote, On 7/27/2012 12:15 AM:
  On Windows 7 x64 (I haven't tested XP), upsdrvctl shutdown doesn't
  appear to get called during automatic OS shutdown by NUT. I used upsmon
  -c fsd to test. upsdrvctrl shutdown works if I run it manually.
  Last time I tested this, upsdrvctl was correclty called at OS
  shutdown time. Maybe a regression or an issue with Win7. I will a
  have to investigate.
 
  Okay, that's good. That is what I was hoping it would at least do.
  I'll do some more tests to make sure I don't have something else going
  on.
 
 Not working in XP (as a VM) either. I might be doing something wrong.

This should be fixed in rev 3705

 upsdrvctl stop
 
 Network UPS Tools - UPS driver controller 2.6.4-3534:3579M
 Stopping UPS: ups
 Sending signal to C:\Program Files\NUT\bin\..\var\run/usbhid-ups-ups.pid
 Stopping C:\Program Files\NUT\bin\..\var\run/usbhid-ups-ups.pid
 failed: No error [The parameter is incorrect. ]
 
 I get the same message on Win7.
 
 If I run upsdrvctrl start myself, I can upsdrvctl stop then shutdown
 without issues.
 
 upsmon.pid doesn't get removed after stopping the nut service.
 upsd.exe.pid does get removed and it has 'exe' in its filename.

This should be fixed in 3709

Both fixes will be available in soon to be released NUT 2.6.5 Windows binaries.

Thanks for your feedback.

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

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

[Nut-upsuser] Network UPS Tools version 2.6.5 released

2012-08-08 Thread Arnaud Quette
Network UPS Tools version 2.6.5 has been released:
http://www.networkupstools.org/

Among the many improvements and bugfixes, this release fixes the upssched
regression, that rendered it unusable.
Update to 2.6.5 is thus highly recommended.

As noted in the news, website hosting is under migration.
While I don't expect any service disruption, please report any issue you
may face.

Direct access:
- Download: http://www.networkupstools.org/source/2.6/nut-2.6.5.tar.gz
- News: http://www.networkupstools.org/source/2.6/new-2.6.5.txt
- ChangeLog: http://www.networkupstools.org/source/2.6/ChangeLog


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