similar to: Fwd: Not receiving real data from a Eaton E series DX 1000H UPS

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 second one is running Debian 6.0 x64. Both of them are updated. I tried using different serial cable but the result is the same. The connection to the ups using Windows 7 and Winpower is working fine on

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 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, I would like to report that Tuncmatik Newtech Pro 1 KVA (http://www.tuncmatik.com/en-US/productDetail.asp?RecID=290) works with nut(2.4.1) blazer_usb, blazer_ser and megatec drivers. The UPS came with an usb cable and a java based software for both linux and windows, named ViewPower (http://www-power-software-download.com). This UPS has double interface a USB interface and a serial

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 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, FreeBSD 5.4, NUT from ports (2.0.3), serial on /dev/cuaa1, Ellipse 1200 USBS. I set the ups.conf up as : [ellipse] driver=mge-utalk port=/dev/cuaa1 desc="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) Could not get multiplier table: using raw

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 all, long time away from this list, glad to be around again! I have this Powercom Vanguard VGN VGD-20K31. Some details of this model: * 3-phase input, single phase output * Model has 240V / 12V9AH x 20 x 2SET, plus another set of 20 batteries. All in all, 3 sets * Serial connection to Windows 2k3 server with UPSMon Now I was strongly considering replacing the bundled no-good upsmoon

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 all, Does anyone know why when I run the following command, I get thousands of packages in the output, saying they've been excluded? [root at server yum.repos.d]# yum --security check-update | less Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirror.removed.com * epel: mirror.removed.com * extras: mirror.removed.com * updates: mirror.removed.com

From: "Roy.Li" <rongqing.li at windriver.com> Add error check when write file, the caller can detect if the disk filled up (or had an i/o error) and return a NOSAPCE nak to the other side. Signed-off-by: Ming Liu <ming.liu at windriver.com> Signed-off-by: Roy.Li <rongqing.li at windriver.com> --- common/tftpsubs.c | 4 +++- tftpd/tftpd.c | 12 ++++++++++-- 2

Dear Daniele, I have some news regarding the Driver: I applied the patch you sent me (https://github.com/zykh/nut/tree/issue-441) and it works correctly (obviously in Level 5 of Debug I see "missing CR...etc.."). As for now there are 2 modification I'd like to suggest you: - For Online Type UPSs the Megatec protocol describes that the battery voltage is provided in the form of V

From: "Roy.Li" <rongqing.li at windriver.com> Add error check when the write-buffer is finally flushed to the file, the caller can detect if the disk filled up (or had an i/o error) and return a NOSAPCE nak to the other side. Signed-off-by: Ming Liu <ming.liu at windriver.com> Signed-off-by: Roy.Li <rongqing.li at windriver.com> --- common/tftpsubs.c | 8 +++++---

Hi, They say one should never argue with people that know more than you, so please bear with me. On 2013/10/24 09:47 PM, hyouko at gmail.com wrote: > The driver is expecting either 'ACK' or no reply at all in case of > success and the command itself echoed back in case of errors. > On the other hand, your UPS replies '(ACK' in case of success and > '(NAK' on

[forwarded without attachments, for real this time] > Begin forwarded message: > > From: Gabriele TAORMINA <gabriele.taormina at legrand.com <mailto:gabriele.taormina at legrand.com>> > Subject: Re: [Nut-upsdev] Adding drivers to NUT? > Date: August 27, 2018 at 6:03:55 AM EDT > To: Daniele Pezzini <hyouko at gmail.com <mailto:hyouko at gmail.com>> >

Hi Johan, The driver is expecting either 'ACK' or no reply at all in case of success and the command itself echoed back in case of errors. On the other hand, your UPS replies '(ACK' in case of success and '(NAK' on failure. So.. when the driver first tries to stop pending shutdowns and you get the 'operation not permitted' error, the driver interprets it as a