[Nut-upsuser] Feedback for Powercom IMD1000 AP with 2.6.0

2011-01-31 Thread Mehmet Giritli
Hi,

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.

I have problems with the instant commands tough: The commands seem to
have no effect most of the times (except see next paragraph), despite
the response is always OK after issuing the commands.

One effect the commands have is to confuse the ups in such a way that it
beeps twice every second or so and it is not possible to stop this
behaviour until turning the whole thing off and then back on. 

Other than the commands, everything seems fine.


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


Re: [Nut-upsuser] Feedback for Powercom IMD1000 AP with 2.6.0

2011-01-31 Thread Mehmet Giritli
Here you go. Thanks!

One more thing. Does this ups support reporting temperature? Can you
tell this by looking at the log file I sent? Current NUT driver does not
seem to find this data.

I am not an expert on this, but it seems there is some data for
temperature.

Best.

On Mon, 2011-01-31 at 12:22 +0100, Arjen de Korte wrote:
 Citeren Mehmet Giritli mgiri...@giritli.eu:
 
  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 PowerCOM so far. Could you post  
 the output of
 
  /path/to/usbhid-ups -DDD -a upsname  PowerCOM.log 21
 
 here (preferablly gzip'ed to reduce the size) so that we can get an  
 idea of the variables the UPS might support?
 
  I have problems with the instant commands tough: The commands seem to
  have no effect most of the times (except see next paragraph), despite
  the response is always OK after issuing the commands.
 
 See above. The existing powercom HID subdriver was written for a  
 series of devices that don't have native HID PDC support in them  
 (essentially these were serial devices with a USB HID PDC layer tacked  
 on). I'm not too surprised that you're seeing odd behavior, since this  
 the UPS firmware contains some gross hacks (which we reported back to  
 PowerCOM to result in compatibility issues with native HID devices  
 later on).
 
  One effect the commands have is to confuse the ups in such a way that it
  beeps twice every second or so and it is not possible to stop this
  behaviour until turning the whole thing off and then back on.
 
 Please provide us with the output of above command.
 
  Other than the commands, everything seems fine.
 
 I fear there may be some pitfalls along the way.
 
 Best regards, Arjen




PowerCOM.log.gz
Description: GNU Zip compressed data
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Feedback for Powercom IMD1000 AP with 2.6.0

2011-01-31 Thread Arjen de Korte

Citeren Mehmet Giritli mgiri...@giritli.eu:


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 NUT driver does not
seem to find this data.


Yes and no. Although the UPS lists this in the report descriptor (the  
list of supported variables), it miserably fails when we try to read it:


   0.219124	libusb_get_report: error sending control message:  
Operation not permitted

   0.219149 Can't retrieve Report 2c: Operation not permitted
   0.219165	Path: UPS.PowerSummary.Temperature, Type: Feature,  
ReportID: 0x2c, Offset: 0, Size: 8



I am not an expert on this, but it seems there is some data for
temperature.


All lines where you see 'Operation not permitted' are variables that  
are supposed to be readable from the UPS, but when we do so, fail to  
return an answer. There is nothing we can do about this. The firmware  
in the UPS is broken, so we can't read these values.


Best regards, Arjen
--
Please keep list traffic on the list (off-list replies will be rejected)


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