search for: m_msg

.../ (V_interval[1] - V_interval[0]))); + dstate_setinfo("battery.charge", "%3d", bp); + } + /* - * - * - * - * - * - * - * - * - * - * - * - * - * - * - */ ret = send_cmd(m_msg, sizeof(m_msg), m_value, sizeof(m_value)); ------ end patch ------ This is against NUT 2.7.1 and so will probably not apply cleanly on the current latest and greatest. I would not apply it as is anyway since it is quick and dirty and I am sure that it may be simplified (the conditional in particu...

.../ (V_interval[1] - V_interval[0]))); > + dstate_setinfo("battery.charge", "%3d", bp); > + } > + > /* - * - * - * - * - * - * - * - * - * - * - * - * - * - * - */ > > ret = send_cmd(m_msg, sizeof(m_msg), m_value, sizeof(m_value)); > ------ end patch ------ > > This is against NUT 2.7.1 and so will probably not apply cleanly on > the current latest and greatest. I would not apply it as is anyway > since it is quick and dirty and I am sure that it may be simplified &g...

On May 15, 2014, at 9:39 PM, Stefan Bruda wrote: > What bugs be though is that I cannot seem to be able to read the > remaining run time on battery. The battery charge is also widely > inaccurate (it drops to zero really fast and stays there). I read > somewhere that the usb.debug numbers may hold the key to this (at > least to the running time that is), but I don't know what

Hello, I own an older Tripp Lite SMART3000RM2U (protocol 3003). It does not work with usbhid-ups but it mostly works with the tripplite_usb driver (nut 2.7.1, the latest in the Gentoo tree), in the sense that the status (on line, on battery, etc.) is detected correctly, the machine is shut down on critical battery, and I can even get some information from the UPS. This is how it all looks:

...terval[0]))); > > + dstate_setinfo("battery.charge", "%3d", bp); > > + } > > + > > /* - * - * - * - * - * - * - * - * - * - * - * - * - * - * - */ > > > > ret = send_cmd(m_msg, sizeof(m_msg), m_value, sizeof(m_value)); > > ------ end patch ------ > > > > This is against NUT 2.7.1 and so will probably not apply cleanly on > > the current latest and greatest. I would not apply it as is anyway > > since it is quick and dirty and I am sur...