Re: [Nut-upsuser] Dynamix UPS-650VA
On Thu, May 8, 2008 at 4:20 AM, Peter McKenna [EMAIL PROTECTED] wrote: That's correct. I used to be able to toggle it in Nut 2.0 and the response from upsc would show off/on, but if you unplugged it it would still beep. I assumed there where other less critical beep alerts being turned off. Then it never actually worked, it only appeared to work. The driver was probably assuming the beeper was on at startup and just changing its internal state when you issued the toggle command without actually getting that state from the UPS. Can you check the logs (/var/log/messages or similar, depending on the distribution you're using) to see if there's any message there indicating the beeper.toggle command didn't succeed? -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Dynamix UPS-650VA
On Mon, 2008-05-05 at 09:49 +0100, Carlos Rodrigues wrote: On Mon, May 5, 2008 at 4:05 AM, Peter McKenna [EMAIL PROTECTED] wrote: Thanks for your reply Carlos. The ignoreoff suggestion didn't work. The driver appeared to not connect. Hmmm, my bad. I only added the ignoreoff option _after_ 2.2.1. The Temp reading has never worked returning 0.0. That means the UPS doesn't have a temperature sensor. The beeper did work in 2.0. I could toggle it with an instant command, but now doesn't work with the same command. upsc just shows it as disabled. The beeper has always worked when the ups is unplugged. Define doesn't work. The beeper can still be heard after you try to disable it, or the driver still shows the beeper as disabled? In many models the beeper status flag is bogus (this is mentioned in the manpage btw) and never changes (it is always enabled or disabled). I'm not sure if in 2.0 the driver exposed the beeper status or not... PS: Please keep the list CC:ed when replying. Thanks. Define doesn't work. The beeper can still be heard after you try to Disable it? That's correct. I used to be able to toggle it in Nut 2.0 and the response from upsc would show off/on, but if you unplugged it it would still beep. I assumed there where other less critical beep alerts being turned off. BTW battvolts 11.5:13 seems to give the best results for the charge reading with this model. Why is it 13 V when it's a 12 V battery? Regards, Peter ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Dynamix UPS-650VA
On Mon, May 5, 2008 at 4:05 AM, Peter McKenna [EMAIL PROTECTED] wrote: Thanks for your reply Carlos. The ignoreoff suggestion didn't work. The driver appeared to not connect. Hmmm, my bad. I only added the ignoreoff option _after_ 2.2.1. The Temp reading has never worked returning 0.0. That means the UPS doesn't have a temperature sensor. The beeper did work in 2.0. I could toggle it with an instant command, but now doesn't work with the same command. upsc just shows it as disabled. The beeper has always worked when the ups is unplugged. Define doesn't work. The beeper can still be heard after you try to disable it, or the driver still shows the beeper as disabled? In many models the beeper status flag is bogus (this is mentioned in the manpage btw) and never changes (it is always enabled or disabled). I'm not sure if in 2.0 the driver exposed the beeper status or not... PS: Please keep the list CC:ed when replying. Thanks. -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Dynamix UPS-650VA
On Mon, May 5, 2008 at 10:24 AM, Jean Delvare [EMAIL PROTECTED] wrote: On Mon, 5 May 2008 09:49:12 +0100, Carlos Rodrigues wrote: On Mon, May 5, 2008 at 4:05 AM, Peter McKenna [EMAIL PROTECTED] wrote: The Temp reading has never worked returning 0.0. That means the UPS doesn't have a temperature sensor. Wouldn't it be better if the driver didn't expose the temperature value at all in this case? The version currently in the subversion repository does that since yesterday afternoon. :) Although it is of limited usefulness for the general population, because most models that don't have a temperature sensor return a fixed value (mine always returns 25.0) making it impossible to tell if it is bogus or not... -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Dynamix UPS-650VA
On Mon, 5 May 2008 09:49:12 +0100, Carlos Rodrigues wrote: On Mon, May 5, 2008 at 4:05 AM, Peter McKenna [EMAIL PROTECTED] wrote: The Temp reading has never worked returning 0.0. That means the UPS doesn't have a temperature sensor. Wouldn't it be better if the driver didn't expose the temperature value at all in this case? -- Jean Delvare ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Dynamix UPS-650VA
On Mon, May 5, 2008 at 10:47 AM, Jean Delvare [EMAIL PROTECTED] wrote: Yes I know, mine always returns 29.2... Too bad that the manufacturers don't make it clearer when a thermal sensor is present and when it's not. And it would be easy to do. The protocol specifies that an non-existent value should be expressed as a non-numeric field (eg. @@.@). The only thing we can do, I suppose, is look at the UPS device name string and have a blacklist in the driver for devices which are known to not have a thermal sensor. The benefit might not be worth the maintenance cost though. Yeah, the benefit isn't worth it, especially since the subset of models that provide bogus values seems to map almost completely to the subset of models that provide absolutely no device string whatsoever... -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Dynamix UPS-650VA
Hi I've got a UPS branded as a Dynamix UPS-650VA. I used NUT v2.0 with it and tried various drivers the ippon one seemed to work best. Now with 2.2.1 it only works with the megatec driver and while it seems to work well, the status always shows OFF. upsc reports the following. battery.charge: 100.0 battery.voltage: 12.70 battery.voltage.nominal: 11.5 driver.name: megatec driver.parameter.battvolts: 4:12 driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.version: 2.2.1- driver.version.internal: 1.5.13 input.frequency: 50.2 input.voltage: 234.0 input.voltage.fault: 165.0 input.voltage.maximum: 235.0 input.voltage.minimum: 234.0 output.voltage: 234.0 output.voltage.nominal: 240.0 ups.beeper.status: disabled ups.delay.shutdown: 0 ups.delay.start: 2 ups.load: 0.0 ups.mfr: KEBO ups.model: UPS-650VA VER7.00 ups.serial: unknown ups.status: OFF ups.temperature: 0.0 Temp reading also doesn't work and beep status just says disabled. Other readings seem plausible. If anybody knows anything about this UPS and how to fix the status, temp beep status etc, I would be happy to collaborate with them in writing/testing any modifications to the driver. Best Regards, Peter McKenna ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
