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

2012-08-13 Thread Arnaud Quette
Hey Massimo and Greg,

2012/8/12 Massimo Gais massimo.g...@iki.fi

 On Sun, Aug 12, 2012 at 5:11 AM, Greg Vickers daehe...@iinet.net.auwrote:

  On 11/08/12 06:58, Arnaud Quette wrote:

 Hi Massimo and Greg,

 @Greg: if you yet returned your unit, you now have a solution ;)

 I have not yet gotten rid of it, so thank you very much!  It's a case of
 download, extract, apply patch, and compile on my RPi, correct?


 Hello Greg,
 yes you can compile it directly on the RPI. See anyway that if you have
 the old deb package installed and you want to replace only the recompiled
 driver, you may have some mismatch with the pidpath/statepath directories
 (/var/state/ups vs /var/run/nut). I tried to make a debian package on the
 RPi, but it was requiring to install all the documentation tools, and I did
 not have enough SD disk space for that.


use the following configuration line to get back inline with deb directives:

./configure --prefix= --includedir=/usr/include --mandir=/usr/share/man
--sysconfdir=/etc/nut --localstatedir=/var --without-ssl --with-cgi
--with-dev --enable-static --with-statepath=/var/run/nut
--with-altpidpath=/var/run/nut --with-drvpath=/lib/nut
--with-cgipath=/usr/lib/cgi-bin/nut --with-htmlpath=/usr/share/nut/www
--with-pidpath=/var/run/nut --datadir=/usr/share/nut
--with-pkgconfig-dir=/usr/lib/pkgconfig --with-user=nut --with-group=nut
--with-udev-dir=/lib/udev --without-doc

you may also want to disable a few more things, like CGI, by using
--without-cgi for example...
this will lower the dependencies barrier.

cheers,
Arnaud
-- 
Linux / Unix / Opensource Engineering Expert - Eaton -
http://opensource.eaton.com
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

Re: [Nut-upsuser] Mitsubishi 2033C via gamtronic (SEC)?

2012-08-13 Thread Arnaud Quette
2012/8/6 Mark Felder f...@feld.me

 Hi guys,


Hi Mark,

I have a couple Mitsubishi 2033C UPSes that I badly want data from. We used
 to have Mitsubishi Netcom devices which took the serial output and provided
 a web interface, SNMP, and email alerts. All of those devices died. They're
 really awful devices (they're clunky and have 386s in them) and not worth
 the pricetag for a replacement.

 The closest replacement I've seen so far is a device by Chipkin but it's
 not very clear if they're actually selling it -- http://www.chipkin.com/**
 products/cas-gateways/cas-**2700-21-mitsubishi-ups-**gateway/http://www.chipkin.com/products/cas-gateways/cas-2700-21-mitsubishi-ups-gateway/

 After reading about the Chipkin I realized the UPS I'm working with speaks
 the SEC protocol. This is supposed to be supported by the gamtronic driver.
 My next thought is getting something like a Soekris/Alix/RaspberryPi device
 nearby and reading the data with NUT. Has anyone tried this before? It
 seems nobody even talks about these Mitsubishi UPSes on the internet, so
 it's a little scary -- I've seen UPSes (namely APC) decide to shutdown if
 you plug in the wrong serial cable, so I'm worried about what could happen
 if something malformed comes over the wire.


 Thanks for any pointers you might have.


sadly for you:
- we don't have any Mitsubishi units supported,
- actual SEC support in the gamatronic driver probably requires the below
patch, that I've never integrated due to the lack of users/testers:
https://alioth.debian.org/tracker/index.php?func=detailaid=303719group_id=30602atid=411544

Note that this patch will probably not apply straight on a recent archive.

You may also be interested in looking at this tracker (preliminary effort,
before I asked Julius to merge this with gamatronic):
https://alioth.debian.org/tracker/index.php?func=detailaid=302733group_id=30602atid=411544

cheers,
Arnaud
-- 
Linux / Unix / Opensource Engineering Expert - Eaton -
http://opensource.eaton.com
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

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

2012-08-13 Thread Rojo Alvarez , Álex
Hi, this is the output of the command you asked for. THANKS

sweethome:~# lsusb -v -d0001:

Bus 002 Device 005: ID 0001: Fry's Electronics 
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize0 8
  idVendor   0x0001 Fry's Electronics
  idProduct  0x 
  bcdDevice0.00
  iManufacturer   1 ATCL FOR UPS
  iProduct1 ATCL FOR UPS
  iSerial 1 ATCL FOR UPS
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   41
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xe0
  Self Powered
  Remote Wakeup
MaxPower   98mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass 3 Human Interface Device
  bInterfaceSubClass  0 No Subclass
  bInterfaceProtocol  0 None
  iInterface  0 
HID Device Descriptor:
  bLength 9
  bDescriptorType33
  bcdHID   1.11
  bCountryCode0 Not supported
  bNumDescriptors 1
  bDescriptorType34 Report
  wDescriptorLength  32
  Report Descriptor: (length is 32)
Item(Global): Usage Page, data= [ 0xa0 0xff ] 65440
(null)
Item(Local ): Usage, data= [ 0x01 ] 1
(null)
Item(Main  ): Collection, data= [ 0x01 ] 1
Application
Item(Local ): Usage, data= [ 0x03 ] 3
(null)
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0x01 ] 1
Item(Global): Report Size, data= [ 0x08 ] 8
Item(Global): Report Count, data= [ 0x08 ] 8
Item(Main  ): Input, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile 
Bitfield
Item(Local ): Usage, data= [ 0x04 ] 4
(null)
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0x01 ] 1
Item(Global): Report Size, data= [ 0x08 ] 8
Item(Global): Report Count, data= [ 0x08 ] 8
Item(Main  ): Output, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile 
Bitfield
Item(Main  ): End Collection, data=none
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0008  1x 8 bytes
bInterval  10
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02  EP 2 OUT
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0008  1x 8 bytes
bInterval  10
Device Status: 0x
  (Bus Powered)




On 13/08/2012, at 15:00, Arnaud Quette wrote:

 lsusb -v -d0001:


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