Bug#501087: [Nut-upsdev] Bug#501087: nut: support for a tripplite avr750u
2008/10/4 Raphael Geissert [EMAIL PROTECTED]: 2008/10/4 Arjen de Korte [EMAIL PROTECTED]: Citeren Arnaud Quette [EMAIL PROTECTED]: you missed to add an entry in drivers/tripplite-hid.c -tripplite_claim() for that ;-) And beware that you need to put it in the correct place as well. Some Tripp Lite HID devices (incorrectly) report battery voltage in decivolts so we need to apply a correction factor here. So there are basically two groups in this function. One that reports battery voltage in decivolts (productid 1003, 2005 and 2007) and one that reports battery voltage in volts (productid 3012, 4002, 4003). Before committing this change, we need to see the output of 'upsc' to know what it reports. In the attached patch I've added it to the first group, as I'd expect it to behave just like 1003 (the avr550u model). applied to the trunk, thanks. -- Arnaud -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501087: [Nut-upsdev] Bug#501087: nut: support for a tripplite avr750u
2008/10/4 Raphael Geissert [EMAIL PROTECTED]: 2008/10/4 Charles Lepple [EMAIL PROTECTED]: I don't know much about the Tripp Lite devices covered by the usbhid-ups driver, but the usual debug suggestions apply. You can run the driver with -DDD on the command line, and look for messages related to battery charge. Attaching the output of usbhid-ups -. @Arnaud: there's no windows software it is a java applet which does not like neither the java 5 nor 6 installations of my box. and obviously, no source? you can try to ask TL to disclose the Usage Table (ie the lookup between the unknown values 0x and the corresponding names and meanings). This shouldn't hurt theim too much ;-) and would help us a lot... -- Arnaud -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501087: [Nut-upsdev] Bug#501087: nut: support for a tripplite avr750u
On Sat, Oct 4, 2008 at 8:44 AM, Arnaud Quette [EMAIL PROTECTED] wrote: 2008/10/4 Raphael Geissert [EMAIL PROTECTED]: Package: nut Version: 2.2.2-8 Severity: wishlist Tags: patch [...] * the battery charge information, at least as displayed by knutclient 0.9.4, is either 0% or 100%, the latter only being displayed when the UPS is fully charged. * the runtime info is only updated after a test.battery.start.quick/deep, there's no calibrate.start/stop for it. I don't know much about TL devices, and I've not dug the ml, but Charles might have an answer to that. I don't know much about the Tripp Lite devices covered by the usbhid-ups driver, but the usual debug suggestions apply. You can run the driver with -DDD on the command line, and look for messages related to battery charge. Going out on a limb here, maybe it's something that we have to explicitly poll (versus waiting for it to be reported on the interrupt pipe), for the times when it is below 100%. In any case, it's probably a good idea to first verify that knutclient agrees with upsc. -- - Charles Lepple -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501087: [Nut-upsdev] Bug#501087: nut: support for a tripplite avr750u
Citeren Arnaud Quette [EMAIL PROTECTED]: Attached is a patch adding support for tripplite's avr750u UPS. Issues: * productid still needs to be specified in ups.conf you missed to add an entry in drivers/tripplite-hid.c -tripplite_claim() for that ;-) And beware that you need to put it in the correct place as well. Some Tripp Lite HID devices (incorrectly) report battery voltage in decivolts so we need to apply a correction factor here. So there are basically two groups in this function. One that reports battery voltage in decivolts (productid 1003, 2005 and 2007) and one that reports battery voltage in volts (productid 3012, 4002, 4003). Before committing this change, we need to see the output of 'upsc' to know what it reports. and an entry in the hotplug script for the sake of completion. Don't forget the udev and hal scripts either. We probably need to come up with some automation here, so that we have to put this in only one place and have these scripts generated automagically. Best regards, Arjen -- Please keep list traffic on the list -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501087: [Nut-upsdev] Bug#501087: nut: support for a tripplite avr750u
Citeren Charles Lepple [EMAIL PROTECTED]: Going out on a limb here, maybe it's something that we have to explicitly poll (versus waiting for it to be reported on the interrupt pipe), for the times when it is below 100%. The usbhid-ups driver polls for practically all variables. The polling frequency is determined by a flag that is passed in the HID2NUT lookup table: (default) - every 'pollfreq' seconds (default: 30) HU_FLAG_QUICK_POLL - every 'pollinterval' seconds (default: 2) HU_FLAG_SEMI_STATIC - when something has been written to the UPS HU_FLAG_STATIC - only at startup In the current 'tripplite-hid' subdriver, the 'battery.charge' has no special flags assigned, so it will be polled every 'pollfreq' seconds. Depending on the accuracy of the charge calculation and the load that is applied, it is quite possible that there is basically nothing reported between 100% and 0%. Best regards, Arjen -- Please keep list traffic on the list -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501087: [Nut-upsdev] Bug#501087: nut: support for a tripplite avr750u
2008/10/4 Arjen de Korte [EMAIL PROTECTED]: Citeren Arnaud Quette [EMAIL PROTECTED]: Attached is a patch adding support for tripplite's avr750u UPS. Issues: * productid still needs to be specified in ups.conf you missed to add an entry in drivers/tripplite-hid.c -tripplite_claim() for that ;-) And beware that you need to put it in the correct place as well. Some Tripp Lite HID devices (incorrectly) report battery voltage in decivolts so we need to apply a correction factor here. So there are basically two groups in this function. One that reports battery voltage in decivolts (productid 1003, 2005 and 2007) and one that reports battery voltage in volts (productid 3012, 4002, 4003). Before committing this change, we need to see the output of 'upsc' to know what it reports. I missed that one. thanks for pointing it ;-) @Raphael: would you be able to test a trunk version for fine tuning? and an entry in the hotplug script for the sake of completion. Don't forget the udev and hal scripts either. We probably need to come up with some automation here, so that we have to put this in only one place and have these scripts generated automagically. I've thought about that, and have already done something similar for LIRC. the base idea is to have something grep'able (like an empty USB_DEVICE macro) and a defined format, like: /* comment, like device vendor/name... */ USB_DEVICE(0x463, 0x) thanks Arjen and Charles, Arnaud -- Linux / Unix Expert RD - MGE Office Protection Systems - http://www.mgeops.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ Free Software Developer - http://arnaud.quette.free.fr/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501087: [Nut-upsdev] Bug#501087: nut: support for a tripplite avr750u
2008/10/4 Arjen de Korte [EMAIL PROTECTED]: Citeren Charles Lepple [EMAIL PROTECTED]: Going out on a limb here, maybe it's something that we have to explicitly poll (versus waiting for it to be reported on the interrupt pipe), for the times when it is below 100%. The usbhid-ups driver polls for practically all variables. The polling frequency is determined by a flag that is passed in the HID2NUT lookup table: (default) - every 'pollfreq' seconds (default: 30) HU_FLAG_QUICK_POLL - every 'pollinterval' seconds (default: 2) HU_FLAG_SEMI_STATIC - when something has been written to the UPS HU_FLAG_STATIC - only at startup In the current 'tripplite-hid' subdriver, the 'battery.charge' has no special flags assigned, so it will be polled every 'pollfreq' seconds. Depending on the accuracy of the charge calculation and the load that is applied, it is quite possible that there is basically nothing reported between 100% and 0%. iirc, we've already seen this before, but I don't recall the details, and don't have enough time to dig... the question is: does the windows software report some real battery charge? @Raphael: it's another question for you ;-) Arnaud -- Linux / Unix Expert RD - MGE Office Protection Systems - http://www.mgeops.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ Free Software Developer - http://arnaud.quette.free.fr/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501087: [Nut-upsdev] Bug#501087: nut: support for a tripplite avr750u
2008/10/4 Arjen de Korte [EMAIL PROTECTED]: Citeren Arnaud Quette [EMAIL PROTECTED]: you missed to add an entry in drivers/tripplite-hid.c -tripplite_claim() for that ;-) And beware that you need to put it in the correct place as well. Some Tripp Lite HID devices (incorrectly) report battery voltage in decivolts so we need to apply a correction factor here. So there are basically two groups in this function. One that reports battery voltage in decivolts (productid 1003, 2005 and 2007) and one that reports battery voltage in volts (productid 3012, 4002, 4003). Before committing this change, we need to see the output of 'upsc' to know what it reports. In the attached patch I've added it to the first group, as I'd expect it to behave just like 1003 (the avr550u model). I've also attached the output of upsc. and an entry in the hotplug script for the sake of completion. Don't forget the udev and hal scripts either. We probably need to come up with some automation here, so that we have to put this in only one place and have these scripts generated automagically. That would be much easier; in the attached patch I added the ups info to hal, hotplug, udev, and drivers/tripplite-hid.c (btw, why isn't that info stored in tripplite-hid.h?). Best regards, Arjen -- Please keep list traffic on the list Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html avr750u.2.patch Description: Binary data upsc.stdout Description: Binary data
Bug#501087: [Nut-upsdev] Bug#501087: nut: support for a tripplite avr750u
2008/10/4 Arnaud Quette [EMAIL PROTECTED]: I missed that one. thanks for pointing it ;-) @Raphael: would you be able to test a trunk version for fine tuning? Sure, why not? :) [...] thanks Arjen and Charles, Arnaud -- Linux / Unix Expert RD - MGE Office Protection Systems - http://www.mgeops.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ Free Software Developer - http://arnaud.quette.free.fr/ Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501087: [Nut-upsdev] Bug#501087: nut: support for a tripplite avr750u
2008/10/4 Charles Lepple [EMAIL PROTECTED]: I don't know much about the Tripp Lite devices covered by the usbhid-ups driver, but the usual debug suggestions apply. You can run the driver with -DDD on the command line, and look for messages related to battery charge. Attaching the output of usbhid-ups -. @Arnaud: there's no windows software it is a java applet which does not like neither the java 5 nor 6 installations of my box. BUT: according to the screenshots in the help pages, the following information is available (using their terms): * Input Voltage * Battery charge remaining * Input Frequency * Nominal Input Voltage * Input Frequency Rating * Low Transfer Voltage * High Transfer Voltage Going out on a limb here, maybe it's something that we have to explicitly poll (versus waiting for it to be reported on the interrupt pipe), for the times when it is below 100%. In any case, it's probably a good idea to first verify that knutclient agrees with upsc. -- - Charles Lepple Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html tripp Description: Binary data
Bug#501087: [Nut-upsdev] Bug#501087: nut: support for a tripplite avr750u
Citeren Raphael Geissert [EMAIL PROTECTED]: Attaching the output of usbhid-ups -. That sucks... :-( This device doesn't seem to report any measured voltage value, so I wouldn't be surprised if the battery charge would something like an online/onbatt flag too (100% @ online and 0% @ offline). [...] BUT: according to the screenshots in the help pages, the following information is available (using their terms): * Input Voltage Maybe one of the custom fields in the report descriptor report this in some odd way. I doubt it. * Battery charge remaining * Input Frequency * Nominal Input Voltage * Input Frequency Rating Check, all available. * Low Transfer Voltage * High Transfer Voltage Can't find these in the report descriptor. Could be in the custom fields. Best regards, Arjen -- Please keep list traffic on the list -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
