Hi Arjen,<br><br>I tried your sugestion, changing the protocol to megatec and putting the port with /dev/ttyUSB0.<br><br>This didn't work, the output is as follows:<br><br>root@comserver:/lib/nut# ./megatec -a sms -DDDDDD<br>
Network UPS Tools 2.2.1- - Megatec protocol driver 1.5.13 [megatec]<br>Carlos Rodrigues (c) 2003-2007<br><br>debug level is '6'<br>Starting UPS detection process...<br>Asking for UPS status [Q1]...<br>Q1 => FAILED [timeout]<br>
Asking for UPS status [Q1]...<br>Q1 => FAILED [timeout]<br>Asking for UPS status [Q1]...<br>Q1 => FAILED [timeout]<br>Asking for UPS status [Q1]...<br>Q1 => FAILED [timeout]<br>Asking for UPS status [Q1]...<br>Q1 => FAILED [timeout]<br>
5 out of 5 detection attempts failed (minimum failures: 2).<br>Megatec protocol UPS not detected.<br><br>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.<br>
<br>Thanks in advance,<br>Gabriel.<br><br><div class="gmail_quote">On Thu, Mar 5, 2009 at 8:21 AM, Gabriel Hahmann <span dir="ltr"><<a href="mailto:gabriel.hahmann@gmail.com">gabriel.hahmann@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Arjen,<br><br>Thanks for your answer, I'll try this as soon as possible, and if I have any luck I'll post here.<br>
<br>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.<br>
<br>Sorry for posting in both lists.<br><br>Thanks in advance,<br><font color="#888888">Gabriel.</font><div><div><span id="q_11fd67015e3f9c55_2" class="h4">- Show quoted text -</span></div><div class="h5"><br><br><div class="gmail_quote">
On Thu, Mar 5, 2009 at 11:42 AM, Arjen de Korte <span dir="ltr"><<a href="mailto:nut%2Busers@de-korte.org" target="_blank">nut+users@de-korte.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Citeren Gabriel Hahmann <<a href="mailto:gabriel.hahmann@gmail.com" target="_blank">gabriel.hahmann@gmail.com</a>>:<br>
<br>
[...]<br>
<div><div></div><div><br>
> My device is connected in the bus 001, device 004, and when i do a lsusb -s<br>
> 001:004 -vvv the result is as follows:<br>
><br>
> Bus 001 Device 004: ID 04b4:5500 Cypress Semiconductor Corp. HID->COM RS232<br>
> Adapter<br>
> Device Descriptor:<br>
> bLength 18<br>
> bDescriptorType 1<br>
> bcdUSB 1.00<br>
> bDeviceClass 0 (Defined at Interface level)<br>
> bDeviceSubClass 0<br>
> bDeviceProtocol 0<br>
> bMaxPacketSize0 8<br>
> idVendor 0x04b4 Cypress Semiconductor Corp.<br>
> idProduct 0x5500 HID->COM RS232 Adapter<br>
> bcdDevice 0.00<br>
> iManufacturer 1 Cypress Semiconductor<br>
> iProduct 2 USB to Serial<br>
> iSerial 0<br>
> bNumConfigurations 1<br>
> Configuration Descriptor:<br>
> bLength 9<br>
> bDescriptorType 2<br>
> wTotalLength 41<br>
> bNumInterfaces 1<br>
> bConfigurationValue 1<br>
> iConfiguration 4 Sample HID<br>
> bmAttributes 0x80<br>
> (Bus Powered)<br>
> MaxPower 100mA<br>
> Interface Descriptor:<br>
> bLength 9<br>
> bDescriptorType 4<br>
> bInterfaceNumber 0<br>
> bAlternateSetting 0<br>
> bNumEndpoints 2<br>
> bInterfaceClass 3 Human Interface Device<br>
> bInterfaceSubClass 0 No Subclass<br>
> bInterfaceProtocol 0 None<br>
> iInterface 0<br>
> HID Device Descriptor:<br>
> bLength 9<br>
> bDescriptorType 33<br>
> bcdHID 1.00<br>
> bCountryCode 0 Not supported<br>
> bNumDescriptors 1<br>
> bDescriptorType 34 Report<br>
> wDescriptorLength 37<br>
> Report Descriptors:<br>
> ** UNAVAILABLE **<br>
> Endpoint Descriptor:<br>
> bLength 7<br>
> bDescriptorType 5<br>
> bEndpointAddress 0x81 EP 1 IN<br>
> bmAttributes 3<br>
> Transfer Type Interrupt<br>
> Synch Type None<br>
> Usage Type Data<br>
> wMaxPacketSize 0x0008 1x 8 bytes<br>
> bInterval 1<br>
> Endpoint Descriptor:<br>
> bLength 7<br>
> bDescriptorType 5<br>
> bEndpointAddress 0x02 EP 2 OUT<br>
> bmAttributes 3<br>
> Transfer Type Interrupt<br>
> Synch Type None<br>
> Usage Type Data<br>
> wMaxPacketSize 0x0008 1x 8 bytes<br>
> bInterval 1<br>
> Device Status: 0x0000<br>
> (Bus Powered)<br>
><br>
> Anybody knows how to handle this?<br>
<br>
</div></div>This device should be recognized by the kernel as a generic USB to<br>
serial converter. Usually this means that it will create a<br>
/dev/ttyUSBx port for you when you connect it. You can use the megatec<br>
driver to connect to this port.<br>
<br>
Best regards, Arjen<br>
<br>
PS Don't cross-post to the development mailing list if you don't get<br>
an answer immediately. This list is mostly run by volunteers, so give<br>
us a little time to answer.<br>
--<br>
Please keep list traffic on the list<br>
<br>
<br>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<div><a href="mailto:Nut-upsuser@lists.alioth.debian.org" target="_blank">Nut-upsuser@lists.alioth.debian.org</a><br>
</div><a href="http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser" target="_blank">http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser</a><br>
</blockquote></div><br>
</div></div></blockquote></div><br>