similar to: Fatal EEPROM fault!

On Thursday 23 March 2017 09:29:55 Sonic wrote: > Hello, > > Sorry if any of this is obvious - I'm new to NUT. > > NUT via upsc is displaying (edited for length): > > device.model: Eaton 5P 2200 > device.type: ups > driver.name: usbhid-ups > ups.alarm: Fatal EEPROM fault! > ups.status: ALARM OL CHRG > ups.test.interval: 604800 > ups.test.result: Done and

>> last night we had what looked like a power spike and 3 machines plugged >> into 2 Eaton UPS went down instantly. I heard the click the UPS makes when >> it shuts the load on the ports and then shuts itself down (ie same thing if >> I simulate with upsmon -fsd). The machines instantly came back, there was no >> actual downtime, and the machine next to them which is

On Thu, Mar 23, 2017 at 11:26 AM, Gene Heskett <gheskett at shentel.net> wrote: > Have you the file to be used to update the EEPROM with? Eaton shows a firmware file: https://powerquality.eaton.com/Support/Software-Drivers/Downloads/5P-UPS-firmware.asp However I'm not sure if it is for the questionable EEPROM and if so maybe it is downlevel from the current reported firmware. upsc

Hello Charles, Thank you so much for your help. Just run upsc and it is possible that input.transfer.low is the one because we used power regulator to bring down the power around 84v and then the ups sent the power loss message to PC. Do you think some others may take effect for the low voltage? Just have the upsc result attached. Then I retried input.transfer.low, default.input.transfer.low,

Device Manufacturer: Eaton Device Name: 5S1500LCD ---------------------------------------------------------- upsc output: battery.charge: 100 battery.charge.low: 20 battery.runtime: 3515 battery.type: PbAc device.mfr: EATON device.model: Ellipse PRO 1500 device.serial: 0000000000 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

Device Manufacturer: Eaton Device Name: 5S1500LCD ---------------------------------------------------------- upsc output: battery.charge: 100 battery.charge.low: 20 battery.runtime: 3515 battery.type: PbAc device.mfr: EATON device.model: Ellipse PRO 1500 device.serial: 0000000000 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

On Jun 4, 2014, at 6:38 PM, Shen Chuan wrote: > $ sudo upsrw -s battery.charge.low=70 -u * -p * ups > OK Not sure this does what you originally asked, though. Does upsc show any settings related to sensitivity? -- Charles Lepple clepple at gmail

Hey Charles, Latest update. Looks like in ups.conf I setup default.input.transfer.low = 84. After I took that line out, restart upsdrvctl, upsmon, and upsd, the command of sudo upsrw -s input.transfer.low=70 -u * -p * ups return OK. Still need to verify if it works by using voltage regulator and will keep you updated. Thank you for your help Regards Shen On Thu, Jun 5, 2014 at 8:54 AM,

Linux-2.4.28 libusb-0.1.8 nut-2.6.5 [+most recent drivers from GIT] - from tarball EATON 3S700DIN [mfr.date 09/28/14] ---------------------------------- ISSUES: I) Too many kernel logs: --- In /var/log/kernel.log usbdevfs: usb_submit_urb returned -28 In /var/log/daemon.log: usbhid-ups[744]: libusb_get_interrupt: No error usbhid-ups[744]: libusb_get_interrupt: error submitting URB: No space left

Hi Dag 2010/2/28 Dag Atle Nettum <dagatle at innit.no> > Hello > > > > I understand you are the project leader of Nut. > > > > In my company we have a Eaton 9135 6000 UPS, we are running NUT 2.4.1 > (Debian squeeze) > > > > The ups is connected with a USB cable but it reports a temperature of 300 > degredes. > > > > Can I send you

Hello Charles, Thank you so much for your reply. Yes. 40v was too low. In windows, those range started from 76v, 85v, and 96v. Just tried upsrw command to modify input.transfer.low and input.transfer.boost.low. There were some error messages returned. Tried another one battery.charge.low and it returns ok. $ sudo upsrw -s input.transfer.low=70 -u * -p * ups Unexpected response from upsd: ERR

But runs normally if started. On a rpi4 running an uptodate raspbian buster, how do I set it to auto start at boot time? Thanks. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D.

Dear All, I am running Slackware64-14.1(Linux marto 3.10.17 #1 SMP Fri Feb 14 16:39:21 CST 2014 x86_64 Intel(R) Pentium(R) CPU G3250 @ 3.20GHz GenuineIntel GNU/Linux) with kernel 3.10.17 and nut package nut-2.6.5-x86_64-1_SBo, buit from source using the build script http://slackbuilds.org/repository/14.1/system/nut/ In the README.Slackware it is suggested that the commands for killing the

On Mon, Mar 27, 2017 at 3:04 AM, Arnaud Quette <arnaud.quette at gmail.com> wrote: > as per confirmation from Eaton support team, and looking at the link above, > the latest FW is "02.12.0025". Hi Arno, According to that link, unless I'm missing something, as the 5P2200RT is a 2U sized unit (2 rack spaces) the proper firmware should be "03.00.0000". Firmware

I have a brand new Eaton 5E UPS purchased in Australia. Details: Eaton 5E Model: 5E650iUSB-AU Date: best I can find is the shipping date to supplier on box label - May 2014 OS: Ubuntu 14.04 Server edition Nut 2.7.1 Installed via apt-get install nut I have two problems I would like to fix. First the beeper is annoying and loud and I worry it will wake everyone up at night. I read that you can

On Jul 26, 2014, at 9:58 AM, Leith Bade <leith at leithalweapon.geek.nz> wrote: > First the beeper is annoying and loud and I worry it will wake everyone up at night. I read that you can mute the beeper temporarily (and this works) but that most UPSs do not allow you to permanently turn it off (I tried using upsrw but it said beeper.status was read only). Can you send the variable list

On 12/06/2013 10:57 PM, Kris Jordan wrote: > [...] > (*) Some UPS's do provide extra options to determine when they will > restore power to load. That would be a nice feature. Anyway, it is a strange thing that I can set the waiting time for power to be restored if main power comes back before offdelay has elapsed, but the UPS ignores this setting if main power comes back after

2017-03-23 14:29 GMT+01:00 Sonic <sonicsmith at gmail.com>: > Hello > Hi Chris > Sorry if any of this is obvious - I'm new to NUT. > > NUT via upsc is displaying (edited for length): > > device.model: Eaton 5P 2200 > device.type: ups > driver.name: usbhid-ups > ups.alarm: Fatal EEPROM fault! > ups.status: ALARM OL CHRG > ups.test.interval: 604800

Angel Tsankov wrote, On 12/24/2013 1:22 AM: > On 12/06/2013 10:57 PM, Kris Jordan wrote: > > [...] >> (*) Some UPS's do provide extra options to determine when they will >> restore power to load. > > That would be a nice feature. > > Anyway, it is a strange thing that I can set the waiting time for > power to be restored if main power comes back before

Hi, This might be a simple thing to fix, but I can?t figure it out. We replaced the battery for the first time in our Eaton 5PX a couple of weeks ago, but we haven?t been able to clear the ?ups.alarm: replace battery!? status. Details of our installation are: OS: Debian 6 NUT version: 2.7.4 Installation method: from source tarball UPS device: Eaton 5PX2000IRT, 240V, 1800W, 2000VA, bought in