similar to: mge-shut lowbatt config param

We have several systems in remote locations and I have found that the ones in the US are having issues.. We are an Australian company and can't source a 110V UPS locally so we arrange to have one bought for the site when it's installed. It seems that in the US we are getting "Pulsar EX 1500" UPSs but locally we buy "Pulsar 1500". NUT seems to work find with the

Hello nuters, FreeBSD, Ellipse USBS 800, serial line, nut 2.02 everything works fine. But I'm only able to get an automatic shutdown when reaching the built-in 30% level. I the "lowbatt parameter" is set to anything, it's simply ignored. This is a problem as I want to shutdown around 90% to avoid the battery to drain out when multiple shutdowns occur. Any idea ?

Hi, I have the above UPS connected to a FreeBSD 6.2 box and it shows 'data stale' very frequently (every few minutes). I have tried the usual trick of setting maxage, poll interval, etc etc but to no avail. When I wind up logging I see (on mge-shut) entering shut_get_report(id: 0d, len: 1800) shut_wait_ack(): ACK received entering shut_get_report(id: 16, len: 1800) shut_wait_ack():

Hi, I am trying to talk to an MGE Pulsar Extreme UPS over RS232 with the mge-shut driver but I'm having some problems. It appears to init OK but I can't, say, turn the outlets off, eg.. harrow:~>upsc mge@localhost battery.charge: 78 battery.charge.low: 20 battery.runtime: 05760 driver.name: mge-shut driver.parameter.port: /dev/cuad1 driver.version: 2.0.3 driver.version.internal: 0.65

Hi, I have a FreeBSD 9.2 system with NUT 2.6.5 (installed via the ports tree) with an MGE Pulsar 1500 connected. A while ago it complained it needed the battery replaced and it was finally replaced last week, however I can't find out how to reset the flag in NUT. I've looked in upsc, upsrw and upscmd but none seem to have a suitable option. The UPS is connected via RS232 and upsc output

I am running NUT 2.2.0 compiled from the FreeBSD ports tree. [inchoate 14:50] ~ >upsc ups1 at localhost battery.charge: 59 battery.charge.low: 20 battery.charge.restart: 0 battery.runtime: 6350 battery.type: PbAc battery.voltage: 43.0 driver.name: usbhid-ups driver.parameter.offdelay: 120 driver.parameter.ondelay: 13 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version:

On 28 May 2014, at 21:59, Charles Lepple <clepple at gmail.com> wrote: >> What would log it? > > The driver. OK. >> I could try running the driver with debugging and see if that shows anything of interest. > > That should help. Unfortunately for non-debug operation, it appears that most of the usbhid-ups instcmd messages are buried at debug level 3 or 5. That

Hi everyone, We just got an MGE Comet EX 11 RT with extra battery (all 250kg of it..) and I have talked to it with NUT. One thing I see is the frequency.. input.frequency: 500 output.frequency: 500 It appears to be in tenths of a Hz vs Hz as I see on a Pulsar Extreme. I'm using NUT 2.0.3 on FreeBSD 6.1 Thanks. -- Daniel O'Connor software and network engineer for Genesis Software -

I'm struggling to configuring nut for MGE Pulsar Ellipse 800 (at least Ellipse 800) for two boxes - home firewall and file server. I'm using Debian 4.0 Etch, every one of them. I'm built (after some dangerouse experiments) a testing configuration, where boxes are plugged to line, server playing as a master, firewall as a slave, and UPS connected to an electric heater about 300 Wats (no

Hi, I am trying to talk to an MGE Pulsar Extreme UPS over RS232 with the mge-shut driver but I'm having some problems. It appears to init OK but I can't, say, turn the outlets off, eg.. harrow:~>upsc mge@localhost battery.charge: 78 battery.charge.low: 20 battery.runtime: 05760 driver.name: mge-shut driver.parameter.port: /dev/cuad1 driver.version: 2.0.3 driver.version.internal: 0.65

On 28 May 2014, at 10:54, Charles Lepple <clepple at gmail.com> wrote: > On May 26, 2014, at 8:21 PM, Daniel O'Connor wrote: > >> However if I do either of the tests upscmd just reports 'OK' and nothing happens. > > Anything in syslog? Not that I can see :( What would log it? I could try running the driver with debugging and see if that shows anything of

Hello, My MGE Pulsar Evolution 800 had some hardware troubles (it may be the batteries according to the manual). The fault was not detected so the power was cut to the load and nothing appears in the log files. Arnaud: do you know if the UPS have some way to report this kind of troubles to the PC so that NUT can handle it with a shutdown sequence ? Philippe

On 26 May 2014, at 23:26, Charles Lepple <clepple at gmail.com> wrote: > On May 26, 2014, at 4:05 AM, "Daniel O'Connor" <doconnor at gsoft.com.au> wrote: > >> I've looked in upsc, upsrw and upscmd but none seem to have a suitable option. > > Is there a "battery.test" command, or similar? There are these commands.. test.battery.start.deep

Hi, I was experimenting with Logstash + elasticsearch on FreeBSD 9 - initially I downloaded it by hand (I forgot to check for a port) and it worked fine. I then tried the port and this forced me to use a different java version (was jdk-16.0.3p4_25 now openjdk6-b27) and it seems that the new one causes a panic. Unfortunately crashdumps aren't working properly, however I did get the panic

Hello all, I wonder if the improvements to a driver called "newmge-shut" which have been mentioned in October 06 got it to the 2.0.5 release? I tried my setup again with this release and still get this "communication lost -> established -> lost -> established" cycle. USB was not working because of the Solaris 8 installation. Regards, Ingo -------------- next part

Hi I have Pulsar 1000 (MGE) and mge-shut 2.0.5-3. By default mge-shut don;t reboot ups after upsmoc -c fsd, only permanent powerdown. After I add ondelay=30 in config, all nice, ups restarted after 10 sec. But according man mge-shut ondelay measured in tens of seconds and by default equal 3. -- Olleg Samoylov

Hi, I just got at work an MGE UPS Comet EX RT 7 and I can communicate fine with it through mge-shut, it detects correctly when on battery. I am using Nut 2.0.3 on Linux (RHEL 3). I am trying to simulate a low battery condition to test my shutdown procedure by setting lowbatt to 98%: driver.parameter.lowbatt: 98 but the ups reaches this value, goes to 97% and still no LB. I tried to change,

I made the following devd script.. sh cd /tmp fetch mkdir /usr/local/etc/devd sed -Ene 's/SYSFS\{idVendor\}==\"(.*)\", SYSFS\{idProduct\}==\"(.*)\", MODE=.*/attach 100 {\ device-name "ugen[0-9]+";\ match "vendor" "0x\1";\ match "product" "0x\2";\ action "chown @RUN_AS_GROUP@

Hi, I have a customer who just bought an APC Back-UPS XS 1300 LCD and I thought I'd try the latest NUT with it (on an old-ish FreeBSD 6.x system). It sees the UPS but I can't actually query it for data, in the usbhid-ups debug output I see.. 30.840512 HIDGetEvents: failed to buffer report: Result too large 30.840600 Got -34 HID objects... 30.840681 Quick update...

On May 26, 2014, at 4:05 AM, "Daniel O'Connor" <doconnor at gsoft.com.au> wrote: > I've looked in upsc, upsrw and upscmd but none seem to have a suitable option. Is there a "battery.test" command, or similar?