similar to: mge-utalk ESV8+ comm problem

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

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 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, 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)

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

Hi Sabine and Christoph, I've just committed a few changes to mge-utalk (r2749). can you please try a snapshot and report back the results: http://new.networkupstools.org/download.html#Snapshots cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer -

I have an MGE Pulsar Evolution 1100 connected to a Debian box, with nut-2.0.1 (the standard "sarge" packages). I have it connected through USB, and I'm using newhidups. However, about once a day the driver looses contact with the UPS and I have to restart NUT to get it to drop the "data stale" nonsense (it happens more often than this, but most times it recovers without

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'

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

I'm running nut 2.0.1 with an MGE pulsar evolution 3000 with the mge-utalk (serial) driver on NetBSD 3.1 . I had a very strange occurance in my basement datacenter this early AM. the following was logged by upslog: 20080219 023452 100.0 123.0 049.0 [OL CHRG] NA 60.00 20080219 023522 100.0 122.8 049.0 [OL CHRG] NA 60.00 20080219 023552 098.0 123.0 049.0 [OL DISCHRG] NA 60.00 20080219 023622

Hi, I find the following feature with MGE Pulsar evolution 2200: [root@hat ups]# /usr/sbin/upsd Network UPS Tools upsd 2.0.2 Connected to UPS [hat_PC_ups]: mge-utalk-ttyS0 Synchronizing........ giving up [root@hat ups]# upsc hat_PC_ups@localhost Error: Data stale Is there a way to make the sync part longer? After 5-10 seconds, however, things work fine: [root@hat ups]# upsc

Hi David, 2017-03-21 20:06 GMT+01:00 David Baker <david at baker.im>: > Hi, > > > Thanks for checking in ? I managed to re-compile it but was getting the > same error ? I then had other things to do so didn?t get further in my > investigation. > same error being "Can't chdir to /var/state/ups: No such file or directory"? if so, ensure that you use

Hi, I've recently got a Raspberry Pi working with NUT and my MGE Pulsar ESV+, using the U-TALK driver, a USB Serial adapter and original cable. I've overcome the documented problems with these units and have it running, except for one little niggle! It's installed in central Europe, where the utility voltage is 240v, it's constantly in trim mode and pushing the voltage down to

Hi, Apologies if this is a known problem. I have just joined the list and haven't done an exhaustive search of the archives. Also I am no UPS expert, so please excuse me if some of my terminology is poor. I use an MGE Pulsar Extreme 700C connected via RS232 to the linux server it powers. I have recently upgraded to a new linux distribution. Both new and old use 2.6 kernels, although

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

Hello, I'm trying to communicate with a MGE Pulsar STS 16 using nut under Linux, but I've had no luck so far. I haven't saw it supported in the doc, so if there's anything I can try... Thanks, Arnaud. -- Perso: http://launay.org/blog/ H?bergement: http://www.nocworld.com/

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

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

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