Re: [Nut-upsuser] Unitek UPS 1250xD - megatec_usb driver

2008-02-18 Thread Matt Brown
Hi Alexander, Please update to revision 1308. Does it work better? I have checked out revision 1308 and when trying to do a autoreconf I get the following.. [EMAIL PROTECTED]:/usr/local/src/trunk# autoreconf configure.in:69: error: possibly undefined macro: AC_PROG_LIBTOOL If this

Re: [Nut-upsuser] Unitek UPS 1250xD - megatec_usb driver

2008-02-18 Thread Alexander I. Gordeev
On Mon, 18 Feb 2008 14:42:40 +0300, Matt Brown [EMAIL PROTECTED] wrote: Hi Alexander, Please update to revision 1308. Does it work better? I have checked out revision 1308 and when trying to do a autoreconf I get the following.. [EMAIL PROTECTED]:/usr/local/src/trunk# autoreconf

Re: [Nut-upsuser] Unitek UPS 1250xD - megatec_usb driver

2008-02-18 Thread Alexander I. Gordeev
On Mon, 18 Feb 2008 15:59:51 +0300, Matt Brown [EMAIL PROTECTED] wrote: Hi Alexander, Hm... compiling under root... You should install package 'libtool'. Ok, exited out of sudo bash ;-) Installed libtool and compiled... Clean compile, and install. Running the megatec_usb -D -a

Re: [Nut-upsuser] Unitek UPS 1250xD - megatec_usb driver

2008-02-17 Thread Alexander I. Gordeev
On Sat, 16 Feb 2008 23:23:39 +0300, Matt Brown [EMAIL PROTECTED] wrote: Hi Alexander, Thanks for that, I am seeing one issue tho which is: Feb 16 20:09:37 pegasus upsmon[32005]: Communications with UPS [EMAIL PROTECTED] established Feb 16 20:10:58 pegasus upsd[28437]: Data for UPS [Unitek]

Re: [Nut-upsuser] Unitek UPS 1250xD - megatec_usb driver

2008-02-17 Thread Arjen de Korte
[...] Asking for UPS status [Q1]... get_data_krauler: index [03], prefix [(] - String: UPS No Ack (len = 10/128) get_data_krauler: retry [UPS No Ack] - String: UPS No Ack (len = 10/128) get_data_krauler: retry [UPS No Ack] - Unable to fetch string 3 get_data_krauler: connection failure

Re: [Nut-upsuser] Unitek UPS 1250xD - megatec_usb driver

2008-02-17 Thread Carlos Rodrigues
On Feb 17, 2008 7:56 PM, Alexander I. Gordeev [EMAIL PROTECTED] wrote: The best solution would probably to ignore the first couple of failures in the 'megatec.c' driver, before declaring data stale. Generally speaking, one should be careful to declare data stale and only do so after a couple

Re: [Nut-upsuser] Unitek UPS 1250xD - megatec_usb driver

2008-02-17 Thread Arjen de Korte
Carlos Rodrigues wrote: If the driver fails to get any data in the current polling cycle, it declares the data as stale until the next cycle. It tried to read the data, it got nothing, ergo the current data is stale. That's a bit too harsh. Even serial communication is sometimes plagued by

Re: [Nut-upsuser] Unitek UPS 1250xD - megatec_usb driver

2008-02-17 Thread Carlos Rodrigues
On Feb 17, 2008 9:16 PM, Alexander I. Gordeev [EMAIL PROTECTED] wrote: Still I concern about the added latency. I can retry after timeout but it means that ser_send_pace will not return for seconds. I'd rather add a variable in megatec.c to make user decide the number of retries before driver

Re: [Nut-upsuser] Unitek UPS 1250xD - megatec_usb driver

2008-02-16 Thread Alexander I. Gordeev
On Sat, 16 Feb 2008 20:50:13 +0300, Matt Brown [EMAIL PROTECTED] wrote: Hi All, I am a newcomer to Nut, so firstly hello :-) Hello :) I am keen to implement Nut and have been digging around most of the day to see how to get my two Unitek 1250xD UPS devices working. I have now managed to