Hi Arjen, I tried your sugestion, changing the protocol to megatec and putting the port with /dev/ttyUSB0.
This didn't work, the output is as follows: r...@comserver:/lib/nut# ./megatec -a sms -DDDDDD Network UPS Tools 2.2.1- - Megatec protocol driver 1.5.13 [megatec] Carlos Rodrigues (c) 2003-2007 debug level is '6' Starting UPS detection process... Asking for UPS status [Q1]... Q1 => FAILED [timeout] Asking for UPS status [Q1]... Q1 => FAILED [timeout] Asking for UPS status [Q1]... Q1 => FAILED [timeout] Asking for UPS status [Q1]... Q1 => FAILED [timeout] Asking for UPS status [Q1]... Q1 => FAILED [timeout] 5 out of 5 detection attempts failed (minimum failures: 2). Megatec protocol UPS not detected. I think that maybe, this version doesn't use the megatec protocol, maybe some variation. Could you or somebody help me to find wich protocol this nobreak uses? I have another server running the windows version of the manuftaturer software, maybe I could sniff or find something. The old version of this manufturer with serial interface uses megatec. Thanks in advance, Gabriel. On Thu, Mar 5, 2009 at 8:21 AM, Gabriel Hahmann <gabriel.hahm...@gmail.com>wrote: > Hi Arjen, > > Thanks for your answer, I'll try this as soon as possible, and if I have > any luck I'll post here. > > Sorry for posting in the dev list too, but after sending to the user list I > found some topics concerning the megatec_usb and new devices vendorid and > productid in the developer list. > > Sorry for posting in both lists. > > Thanks in advance, > Gabriel.- Show quoted text - > > > On Thu, Mar 5, 2009 at 11:42 AM, Arjen de Korte > <nut+us...@de-korte.org<nut%2bus...@de-korte.org> > > wrote: > >> Citeren Gabriel Hahmann <gabriel.hahm...@gmail.com>: >> >> [...] >> >> > My device is connected in the bus 001, device 004, and when i do a lsusb >> -s >> > 001:004 -vvv the result is as follows: >> > >> > Bus 001 Device 004: ID 04b4:5500 Cypress Semiconductor Corp. HID->COM >> RS232 >> > Adapter >> > Device Descriptor: >> > bLength 18 >> > bDescriptorType 1 >> > bcdUSB 1.00 >> > bDeviceClass 0 (Defined at Interface level) >> > bDeviceSubClass 0 >> > bDeviceProtocol 0 >> > bMaxPacketSize0 8 >> > idVendor 0x04b4 Cypress Semiconductor Corp. >> > idProduct 0x5500 HID->COM RS232 Adapter >> > bcdDevice 0.00 >> > iManufacturer 1 Cypress Semiconductor >> > iProduct 2 USB to Serial >> > iSerial 0 >> > bNumConfigurations 1 >> > Configuration Descriptor: >> > bLength 9 >> > bDescriptorType 2 >> > wTotalLength 41 >> > bNumInterfaces 1 >> > bConfigurationValue 1 >> > iConfiguration 4 Sample HID >> > bmAttributes 0x80 >> > (Bus Powered) >> > MaxPower 100mA >> > Interface Descriptor: >> > bLength 9 >> > bDescriptorType 4 >> > bInterfaceNumber 0 >> > bAlternateSetting 0 >> > bNumEndpoints 2 >> > bInterfaceClass 3 Human Interface Device >> > bInterfaceSubClass 0 No Subclass >> > bInterfaceProtocol 0 None >> > iInterface 0 >> > HID Device Descriptor: >> > bLength 9 >> > bDescriptorType 33 >> > bcdHID 1.00 >> > bCountryCode 0 Not supported >> > bNumDescriptors 1 >> > bDescriptorType 34 Report >> > wDescriptorLength 37 >> > 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 1 >> > Endpoint Descriptor: >> > bLength 7 >> > bDescriptorType 5 >> > bEndpointAddress 0x02 EP 2 OUT >> > bmAttributes 3 >> > Transfer Type Interrupt >> > Synch Type None >> > Usage Type Data >> > wMaxPacketSize 0x0008 1x 8 bytes >> > bInterval 1 >> > Device Status: 0x0000 >> > (Bus Powered) >> > >> > Anybody knows how to handle this? >> >> This device should be recognized by the kernel as a generic USB to >> serial converter. Usually this means that it will create a >> /dev/ttyUSBx port for you when you connect it. You can use the megatec >> driver to connect to this port. >> >> Best regards, Arjen >> >> PS Don't cross-post to the development mailing list if you don't get >> an answer immediately. This list is mostly run by volunteers, so give >> us a little time to answer. >> -- >> Please keep list traffic on the list >> >> >> _______________________________________________ >> Nut-upsuser mailing list >> Nut-upsuser@lists.alioth.debian.org >> http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser >> > >
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser