similar to: MGE Evolution mge-utalk Driver Not Connected error

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

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

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've got two MGE Ellipse 1500 UPS connected via usb to an ubuntu jaunty system with nut and libupsclient1 2.4.1-2ubuntu4. As soon as I start the driver for the second one, they start fighting each other and I get no data. I found an older post to this list that said: If you want to monitor multiple UPSes through usbhid-ups, you *must* make sure that each one can be uniquely identified

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 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! 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'

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

I'm trying to set up nut with a MGE UPS equiupped with a network management card, but encountered a problem. UPS: MGE Pulsar M 3000 Network Management card (installed in the UPS): 66102 (2006 edition) Operating system: FreeBSD Nut port version: 2.0.5 Nut driver: snmp-ups According to MGE in Norway this card is supported by nut, but only the old version of the card (66244) is listed on

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

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'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

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 U-Talk protocol (page 34 of http://networkupstools.org/protocols/mge/9261zwfa.pdf) but I can?t seem to figure out how to send the device the

Hello, I'll be back with my MGE Evolution 2200 connected with RS232 I upgrade nut 2.0.1 in nut 2.2 + psp as you ask me PSP autodetect my UPS and autoconfigure NUT. not really diffcult ! So I didn't change anything but I always have in my syslog these event Nov 13 11:09:22 mezenc upsmon[3865]: Poll UPS [mgeups at localhost] failed - Data stale Nov 13 11:09:27 mezenc upsmon[3865]: Poll

hello, at first I'm sorry my english isn't perfect but I tried to be clear I work with mandriva 2007 and with nut 2.0.1 installed with urpmi my UPS is a MGE Evolution 2200 connected with RS232 in my ups.conf I try to use mge-utalk driver and also mge-shut both seem to work I don't really known which I add to use It's the first point. As I saw on web site, I add maxage 25 in