Hi! After some problems doing the automatic shutdown of the UPS on Debian, I have found this Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=293401 Now I fixed it calling always ups-monitor from the halt script despite being halt'ed' or powered off (and relying on the POWERDOWNFLAG be set). Which is the correct aproach or best solution to workarround this bug? And now my driver related question: I have an Eaton Ellipse 1000 and I'm using mge-shut driver (because usbhid-ups receive sporadic disconnects). Since then I see that the the driver lists few variables. With the usbhid-ups driver: battery.charge: 100 battery.charge.low: 30 battery.runtime: 5525 battery.type: PbAc driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.vendorid: 0463 driver.version: 2.2.2 driver.version.data: MGE HID 1.10 driver.version.internal: 0.33 input.transfer.high: 264 input.transfer.low: 184 outlet.0.desc: Main Outlet outlet.0.id: 1 outlet.0.switchable: no outlet.1.desc: PowerShare Outlet 1 outlet.1.id: 2 outlet.1.status: on outlet.1.switchable: no outlet.2.desc: PowerShare Outlet 2 output.frequency.nominal: 50 output.voltage: 230.0 output.voltage.nominal: 230 ups.beeper.status: enabled ups.delay.shutdown: 20 ups.delay.start: 30 ups.load: 0 ups.mfr: EATON ups.model: Ellipse 1000 ups.power.nominal: 1000 ups.productid: ffff ups.serial: 000000000 ups.status: OL CHRG ups.timer.shutdown: -1 ups.timer.start: -10 ups.vendorid: 0463 And now (using mge-shut via serial): battery.charge: 100 battery.charge.low: 30 battery.runtime: 1981 driver.name: mge-shut driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.version: 2.2.2 driver.version.internal: 0.66 outlet.0.desc: Main Outlet outlet.0.id: 1 outlet.0.switchable: 0 outlet.1.desc: PowerShare Outlet 1 outlet.1.id: 2 outlet.1.switchable: 0 output.voltage: 230 ups.delay.shutdown: -1 ups.delay.start: -1 ups.load: 19 ups.mfr: MGE UPS SYSTEMS ups.model: Ellipse 1000 ups.power.nominal: 1000 ups.serial: 000000000 ups.status: OL CHRG Another thing that I noticed is that every time the system boots, the UPS is not responding and I have to restart nut to get ups comm fixed. Basically my questions are: - Is there any fix for the usbhid-ups disconnects? - Will the mge-shut driver suport more features/variables (like the usbhid-ups)? - Why the ups is not responding after a reboot? Serial initialization? Thanks for the help and the good job with nut!
On Feb 22, 2010, at 12:49 PM, Marc Franquesa <mark at l3jane.net> wrote:> Hi! > > After some problems doing the automatic shutdown of the UPS on Debian,Please let us know the version of Debian (at the very least), and preferably the exact package version and revision.
Citeren Marc Franquesa <mark op l3jane.net>:> Basically my questions are: > > - Is there any fix for the usbhid-ups disconnects?Upgrade to nut-2.4.2. All versions prior to that are broken with the MGE and/or Eaton Ellipse series UPS. The problem is specific to the Ellipse series and was fixed only recently. Other than upgrading, there is nothing you can do about it.> - Will the mge-shut driver suport more features/variables (like the > usbhid-ups)?No. You may want to try newmge-shut instead, which uses the same driver core as usbhid-ups but with a serial interface instead of USB. Since this isn't affected by the USB issues that cause the usbhid-ups driver to disconnect, this will not suffer from the disconnect problems.> - Why the ups is not responding after a reboot? Serial initialization?Most likely a permissions problem or some other program keeps the serial port locked. Best regards, Arjen -- Please keep list traffic on the list