Hello Kjell, Thank you very much for helping me, it's very kind.
When I try to set "generic" in my ups.conf file for newhidups driver, I got an error message so I decided to use the SVN repository to compile the latest source code 2.1.0. Now, all is fine and the newhidups driver returns those debug info: /usr/local/ups/bin# ./newhidups -DDDD -u root -a blazer2000usb Network UPS Tools: New USB/HID UPS driver 0.28 (2.1.0) debug level is '4' ... Checking device (0665/5161) (003/004) - VendorID: 0665 - ProductID: 5161 - Manufacturer: Cypress Semiconductor - Product: USB to Serial - Serial Number: unknown - Bus: 003 Trying to match device Device matches HID descriptor retrieved (Reportlen = 27) Report descriptor retrieved (Reportlen = 27) Found HID device Report Descriptor size = 27 Report Descriptor: (200 bytes) => 06 00 FF 09 01 A1 01 09 02 15 00 26 FF 00 75 08 Detected a UPS: Cypress Semiconductor/USB to Serial Using subdriver: GENERIC HID 0.1 Looking up ff000001 Looking up ff000002 entering string_to_path() parsing ff000001 Looking up ff000001 parsing ff000002 Looking up ff000002 Path depth = 2 0: UPage(ff00), Usage(1) 1: UPage(ff00), Usage(2) Can't find object ff000001.ff000002 Path: ff000001.ff000002, Type: Input Looking up ff000001 Looking up 00000000 Looking up ff000001 Looking up 00000000 Looking up ff000001 Looking up 00000000 Looking up ff000001 Looking up 00000000 Looking up ff000001 Looking up 00000000 Looking up ff000001 Looking up 00000000 Looking up ff000001 Looking up 00000000 Looking up ff000001 Looking up ff000002 entering string_to_path() parsing ff000001 Looking up ff000001 parsing ff000002 Looking up ff000002 Path depth = 2 0: UPage(ff00), Usage(1) 1: UPage(ff00), Usage(2) Can't find object ff000001.ff000002 Path: ff000001.ff000002, Type: Output Looking up ff000001 Looking up 00000000 Looking up ff000001 Looking up 00000000 Looking up ff000001 Looking up 00000000 Looking up ff000001 Looking up 00000000 Looking up ff000001 Looking up 00000000 Looking up ff000001 Looking up 00000000 Looking up ff000001 Looking up 00000000 entering identify_ups(0x0665, 0x5161) upsdrv_updateinfo... dstate_init: sock /var/state/ups/blazer2000usb open on fd 5 upsdrv_updateinfo... Waiting for notifications... upsdrv_updateinfo... Waiting for notifications... The link between the UPS and the driver seem to work when the driver is started as root user. Centralion manufacturer reply to me this mail when I ask them if they will write a driver for Linux: ... Moreover, the USB protocol is same as the RS232 protocol. We only use the USB port to be the interface for the communication between the UPS and the computer. So for, the USB communication is functional for Windows family and Mac with the WinPower program. But O/S could detect the USB port as HID device without any driver. The USB for Linux is still under developing but it is not released in formal at this moment. ... This answer is from : Andy Deputy Manager, Customer Service Dept. Centralion Industrial Inc. Andy (at) centralion.com.tw +886-2-8692-6288 Ext. 6728 Maybe he could help you if needed? Regards, Guillaume JAOUEN. -----Message d'origine----- De : Kjell Claesson [mailto:[EMAIL PROTECTED] Envoyé : vendredi 14 avril 2006 20:41 À : Guillaume JAOUEN Cc : [email protected] Objet : RE: [Nut-upsuser] SOS : Help needed for UPS CentralionBlazer2000VAUSB Hi Guillaume, I think you got a 'hid' ups. It shows all the right descriptors to comply with the ups hid document. http://www.usb.org/developers/devclass_docs/pdcv10.pdf Look at Device descriptor on page 46. The 'USB to Serial' is reported from lsusb as it is in the list. Like if cypress and product 2 then it is a usb to serial. So what you have to do is to trick the newhidups driver to find the ups. You can set ------------------- generic vendorid=0665 ------------------ In the define tag of your ups in 'ups.conf' (Check the man page for newhidups) Now you have to run it with debug ./newhidups -DDDD -u root -a blazer2000usb As it don't do much when generic is defined. If this seems to give something back, put it on the mail list and we go from there. If it was a serial with some 'proprietary' protocol it should say class = ff on the interface, and not 03 that say it is a hid device. Regards Kjell fre 2006-04-14 klockan 18:17 +0200 skrev Guillaume JAOUEN: > Hello, > > If it could help this is the lsusb -v outpout of the blazer usb UPS : > > Bus 003 Device 002: ID 0665:5161 > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 0 (Defined at Interface level) > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x0665 > idProduct 0x5161 > bcdDevice 0.02 > iManufacturer 1 Cypress Semiconductor > iProduct 2 USB to Serial > iSerial 0 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 34 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 3 > bmAttributes 0x80 > MaxPower 100mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 3 Human Interface Devices > bInterfaceSubClass 0 No Subclass > bInterfaceProtocol 0 None > iInterface 4 Sample HID > HID Device Descriptor: > bLength 9 > bDescriptorType 33 > bcdHID 1.00 > bCountryCode 0 Not supported > bNumDescriptors 1 > bDescriptorType 34 Report > wDescriptorLength 27 > Report Descriptors: > ** UNAVAILABLE ** > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0008 1x 8 bytes > bInterval 32 > > -----Message d'origine----- > De : [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] De la part de Kjell > Claesson > Envoyé : mercredi 12 avril 2006 23:15 > À : Arnaud Quette; Carlos Rodrigues > Cc : [email protected] > Objet : Re: [Nut-upsuser] SOS : Help needed for UPS Centralion > Blazer2000VAUSB > > Hi, > > There is a slight difference between the bcmxcp_usb driver and this > ups. > If you look at the descriptor it tell you that the protocol is reported on > the interface level. The interface level say HID device. > If you look at the bcmxcp_usb driver it say vendor protocol on > the interface level. > > So this should follow the usb hid device rules on the interface. > > Regards > Kjell > > ----- Original Message ----- > From: "Arnaud Quette" <[EMAIL PROTECTED]> > To: "Carlos Rodrigues" <[EMAIL PROTECTED]> > Cc: <[email protected]> > Sent: Wednesday, April 12, 2006 7:48 PM > Subject: Re: [Nut-upsuser] SOS : Help needed for UPS Centralion Blazer > 2000VAUSB > > > Hi Carlos, > > 2006/4/12, Carlos Rodrigues <[EMAIL PROTECTED]>: > > That hardware doesn't have a serial port right? > > > > I think that UPS could be supported if only one could configure a > > "ttyUSB" with that serial-usb converter. > > > > I (temporarily) have a model with an USB port here, and I would like > > to see if I could get it to work with "megatec"/"powermust" without > > resorting to some HID/USB magic... > > > > The protocol used seems to be the same, so the only thing needed is to > > configure a emulated serial port. Anyone has any ideas? > > isn't bcmxcp_usb built on the same idea? > iirc, they were just encaps'ing the serial protocol over usb (not sure > about hid). Another example of "strange hid approach" is energizerups, > but it's hiddev only. Anyway, all this might give you some ideas ;-) > > Arnaud > > _______________________________________________ > Nut-upsuser mailing list > [email protected] > http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser > > _______________________________________________ > Nut-upsuser mailing list > [email protected] > http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser > > _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
