similar to: updateinfo and stale data

Hi, I'm running into an issue while using FreeBSD 5.4, NUT from ports (2.0.3), serial on /dev/cuaa1, Ellipse 1200 USBS. The ups.conf is : [ellipse] driver=mge-utalk port=/dev/cuaa1 desc="Telecom Closet Ellipse" When I go to start it I get : Network UPS Tools - UPS driver controller 2.0.3 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.87 (2.0.3)

Ah, the perils of auto-upgrades. Last night, Fedora Core 3 upgraded my perfectly working nut installation to 2.0.2. I was informed of that because every xterm in the house (about 8 over a Linux box, two laptops and a G4 server) started beeping at 3:20am and didn't stop until I shut down nut. Keep in mind this configuration has been working for about two years. Here's the messages I get

Hello, I have a MGE Comet S31. I installed nut for Debian/Sarge and configured the mge-utalk protocol. I get the following syslog messages Sep 28 11:10:41 neckarsulm upsmon[25505]: Poll UPS [comet@mastermind] failed - Variable not supported by UPS Sep 28 11:10:46 neckarsulm mge-utalk[25284]: updateinfo: Cannot update ups.temperature Sep 28 11:10:46 neckarsulm mge-utalk[25284]: updateinfo: Cannot

Hello, I recently had a failure with my old MGE ESV8 ups, it just died on me so I had to get a new one. I found a MGE ESV8+ cheap and everything seems to work fine with it except the communication with the computer. The old ESV8 (non +) worked fine with NUT after applying some patches I got from the mailing list, but I think they are in the source tree now. I'm using the same cable that

Hi All, I have an mge pulsar esv 14+ rackmount UPS connected via straight through serial cable to a USB to serial adaptor (My motherboard does not have a native RS232 port). I am running Ubuntu Server 9.04 x64, and nut 2.4.1-2ubuntu4 installed via APT. I am getting the error: Poll UPS [ups1 at localhost] failed - Driver not connected My conf files: (ups.conf) [ups1] driver=mge-utalk

Dear Sirs, I have an old but very well-working UPS MGE Pulsar ESV8+ Rack. I'd like to use it to power FreeBSD 9.0-Rel server. Of fortunately I have problem with recommended driver - mge-utalk, nut 2.6.4 (installed from FreeBSD Ports). I get messages: Could not get multiplier table: using raw readings. and updateinfo: Cannot update system status I saw similar thread on mailing list with no

Hi, i had purchase a MGE-Ellipse 500 and i'm trying to use the DB9 F / RJ45 cable send by MGE with UPS. Which driver i'm suppose to use: mge-utalk or mge-shut ? When i try mge-utalk i've got this message: # upsdrvctl start Network UPS Tools - UPS driver controller 2.0.0 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.80.3 (2.0.0) Startup timer elapsed, continuing... and there is

Some one might have answerd this, but I can not find any think yet I am trying to load a SOLA 610 700va ups up and keep getting : --------------------------------- Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.88 (2.0.5) .Detected Pulsar ESV11+ on /dev/cuaa0 Network UPS Tools - Best UPS driver 1.03 (2.0.5) Unknown model detected - please

On 18.4.2013 ?. 22:24 ?., Arnaud Quette wrote: > > 2013/4/18 Pladi Computers Ltd. <pladi at lovechnet.com > <mailto:pladi at lovechnet.com>> > > UPS: > http://www.eaton.com/Eaton/ESeriesUPS/DXUPS/index.htm?wtredirect=www.eaton.com/DXUPS > > I have the same problem on two different computers. The first one > is running Ubuntu 12.10 i386 , the

Dear all, I am trying to figure out the meaning of the following message: [root@hat ups]# /usr/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.2 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.85 (2.0.2) .Detected Evolution 2200 on /dev/ttyS0 updateinfo: Cannot update system status ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This is an MGE pulsar evolution on ttyS0. Cheers,

Hi, Since last night, all my servers spew out the following error when trying to run an update, either via yum-cron or manually: # yum check-update Loaded plugins: fastestmirror, priorities Determining fastest mirrors ... 194 packages excluded due to repository priority protections Updateinfo file is not valid XML: <open file

Hi, Still running into serial issues on the mge-shut with the MGE Ellipse 1200 USBS. I had mge-utalk sort of talking to it, but was told to use mge-shut and get nothing out of it. This is at a remote site that I have to leave tomorrow so if I don't get it running I can't leave it in place. Help? Thanks, Tuc

Credit goes to "cppcheck". Signed-off-by: Thomas Jarosch <thomas.jarosch at intra2net.com> --- drivers/mge-utalk.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/drivers/mge-utalk.c b/drivers/mge-utalk.c index c6114c7..616e2ad 100644 --- a/drivers/mge-utalk.c +++ b/drivers/mge-utalk.c @@ -465,7 +465,8 @@ void upsdrv_shutdown(void) { char

Hi! I have a MGE Pulsar ES 8+ UPS. Here is the response of some commands: - Si --> 3000 44 0 - Si 1 --> Pulsar ES8+ 0 - Ai --> 5 0 It's not recognized very well by the current (from CVS) mge-utalk driver: [root@srv01 ~]# /home/rog/src/nut/drivers/mge-utalk -i 20 -DDD -u root /dev/ttyS0 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.86 (2.1.0) debug level is '3'

Hello My server with another UPS (MGE Pulsar Evolution2200 USB) is OK. All scripts work Is it possible to work with a UPS MGE CometExtrem 6 on serial port Which driver can I use ? I tried with mge-shut ou mge-utalk without any success when I start driver with upsdrvctl with mge-utalk I have (after a long time) Can't connect to UPS [MGE_cometEX] (mge-utalk-MGE_cometEX): No such

Hello, I'm using an MGE Evolution 1500 with a Debian Sarge 2.4.27 smp server. NUT is using the mge-utalk driver. [ups1500] driver = mge-utalk port = /dev/ttyS0 Seens I did a test.battery.start, my UPS goes off (beep!) once per week (same day, same hour). I guess there should be a very easy explanation for this, unfortunatly, I haven't found it yet. I've tried to upgrade

Hi everybody, Sorry for the eternity it took to solve the UTalk problems, but I've been busy on so many fronts... I've updated the CVS Testing tree, which will soon become 2.0.3 stable release, with mge-utalk 0.87. This release fixes the UTalk problems you have recently faced. If possible, please test it and report back if it work or not with your unit. To do so: 1) Retrieve the source

Hi, FINALLY got my UPS working, YEA!!!! But now it brings up even more issues.. (BOOO!!) 1) I'm thinking this is a UPS issue, but when I pull the plug on my UPS, it goes from 100 to 30 in just a short amount of time (Minutes). This causes the machine to shut down. But once it gets to 0, its beeped its little heart out for a few more HOURS providing power to the non-system items perfectly.

Hi all ! I have communication issues between my station and my old Pulsar EX10 UPS, (U-Talk) connected by RS232, when using v2.4.1 of nut-server. I tried to come back to version 2.2.2 and then, communication start and is operational. Maybe it's linked to bug 498655, but i haven't seen any answer ? http://www.mail-archive.com/debian-bugs-dist at lists.debian.org/msg566711.html Here are

Hi David and Charles Le 3 mars 2017 2:35 PM, "Charles Lepple" <clepple at gmail.com> a ?crit : > On Mar 3, 2017, at 8:21 AM, Charles Lepple <clepple at gmail.com> wrote: > > > > On Mar 2, 2017, at 3:38 PM, David Baker <david at baker.im> wrote: > >> > >> I?ve read the documentation, and it would appear that this can be set > by the