Re: [Nut-upsuser] [Nut-upsdev] Bug/Patch for NUT 2.6.0 ; usbhid-ups (libhid.c)

2011-02-17 Thread Carsten Burkhardt
 Citeren Richard Gerth r.gerth@gmail.com:
 
 Thank you for looking into this.   And thank you (to you and the other
 developers) for NUT -- it's fantastic to have such a great open source
 UPS application.
 
 Would you be willing/able to test future releases of NUT? One thing that
 we're currently lacking is a group of people that can check upcoming
 releases. Most of NUT is generic and can be tested by the developers,
 but when it comes to testing drivers we need the actual hardware (UPS).
 Since you have a device that behaves differently than the ones the
 developers have access to, I think it would be a good idea if you could
 confirm the usbhid-ups driver still works if we plan on releasing a new
 stable version.
 
 Best regards, Arjen

Do you mean such unsuccessfully test with new hardware same like attached file 
explore.txt?

-- 
Mit freundlichen Grüßen

Carsten

Network UPS Tools - Generic HID driver 0.34 (2.4.3) 

 
USB communication driver 0.31

/lib/nut/usbhid-ups -a zinto -x vendorid=06da -DD -x explore  nut-explore.txt
   0.00 debug level is '2'
   0.000706 upsdrv_initups...
   0.121349 Checking device (1D6B/0001) (002/001)
   0.121378 - VendorID: 1d6b
   0.121389 - ProductID: 0001
   0.121399 - Manufacturer: unknown
   0.121408 - Product: unknown
   0.121417 - Serial Number: unknown
   0.121427 - Bus: 002
   0.121436 Trying to match device
   0.121452 Device does not match - skipping
   0.121474 Checking device (06DA/0601) (001/005)
   0.143508 - VendorID: 06da
   0.143530 - ProductID: 0601
   0.143550 - Manufacturer: ONLINE
   0.143560 - Product: ZINTO
   0.143569 - Serial Number: unknown
   0.143579 - Bus: 001
   0.143588 Trying to match device
   0.143611 Device matches
   0.149519 HID descriptor length 27
   0.158535 Report Descriptor size = 27
   0.158626 Using subdriver: EXPLORE HID 0.1
   0.161540 refresh_report_buffer: expected 2 bytes, but got 8 instead
   0.161568 Path: ffa4.ffa6, Type: Input, ReportID: 0x00, Offset: 
0, Size: 8, Value: 0.00
   0.161585 Path: ffa4.ffa7, Type: Output, ReportID: 0x00, Offset: 
0, Size: 8, Value: 0.00
   0.161677 Report descriptor retrieved (Reportlen = 27)
   0.161689 Found HID device
   0.161701 Detected a UPS: ONLINE/ZINTO
   0.161712 find_nut_info: unknown info type: load.off.delay
   0.161723 find_nut_info: unknown info type: load.on.delay
   0.161733 find_nut_info: unknown info type: load.off.delay
   0.161753 upsdrv_initinfo...
   0.161769 upsdrv_updateinfo...
   0.412579 libusb_get_interrupt: Connection timed out
   0.412614 Got 0 HID objects...
   0.412625 Quick update...
   0.412721 dstate_init: sock /var/run/nut/usbhid-ups-zinto open on fd 5
   0.412746 upsdrv_updateinfo...
   0.663875 libusb_get_interrupt: Connection timed out
   0.663909 Got 0 HID objects...
   0.663920 Quick update...
   2.415153 upsdrv_updateinfo...
   2.665335 libusb_get_interrupt: Connection timed out
   2.665367 Got 0 HID objects...
   2.665378 Quick update...
   4.416828 upsdrv_updateinfo...
   4.667774 libusb_get_interrupt: Connection timed out
   4.667808 Got 0 HID objects...
   4.667819 Quick update...
^C   6.293200   Signal 2: exiting
   6.293236 upsdrv_cleanup...attachment: carsten.vcf___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] [Nut-upsdev] Bug/Patch for NUT 2.6.0 ; usbhid-ups (libhid.c)

2011-02-17 Thread Arjen de Korte

Citeren Carsten Burkhardt c.burkha...@b-c-s.de:

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 support them.


Your UPS doesn't seem to match the 'known to be supported' condition.  
The VID:PID combination doesn't match any of the supported models. The  
USB interface has a VID of Phoenixtec Power Co, but other than telling  
us that it probably is some proprietary USB to serial converter,  
doesn't help us really much. If it is recognized by the kernels  
usbserial module, chances are that you can use one of the serial  
drivers with it.


Best regards, Arjen

PS  This is a subscription only mailing list.
--
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