similar to: MGE Pulsar ES 8+

Description: Replace many usleep and some sleep calls with nanosleep. usleep is stated in its manual page as removed by POSIX. Contrary to its predecessors, nanosleep semantics is well defined. The replacement, which is mostly in drivers, is untested. Supplements http://bugs.debian.org/633791. Last-Update: Sat, 13 Aug 2011 14:04:48 +0300 Index:

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

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

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

It look to me that overwriting UPSTYPE CP signal or polarity in ups.conf have no effect. Looking at drivers/main.c source show that &upstab[upstype].line_norm is set to custom CP in initinfo() only _AFTER_ the serial signals are actually set by upsdrv_initups().

It look to me that overwriting UPSTYPE CP signal or polarity in ups.conf have no effect. Looking at drivers/main.c source show that &upstab[upstype].line_norm is set to custom CP in initinfo() only _AFTER_ the serial signals are actually set by upsdrv_initups().

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 own a Yunto-Q 700 (made 2000 by online usv systems) and a Yunto-Q 1200 (made 2010). They both work with blazer_ser, but didn't shutdown. I straced the proprietary driver and found the ups expected the return time given with _5_ digits instead of 4, else the command was ignored by the ups. And the Yunto don't send rating/manufacturer informations. I don't want to commit this to

Hi, I am trying to talk to an MGE Pulsar Extreme UPS over RS232 with the mge-shut driver but I'm having some problems. It appears to init OK but I can't, say, turn the outlets off, eg.. harrow:~>upsc mge@localhost battery.charge: 78 battery.charge.low: 20 battery.runtime: 05760 driver.name: mge-shut driver.parameter.port: /dev/cuad1 driver.version: 2.0.3 driver.version.internal: 0.65

* I committed into CVS the gendb patch that I sent to the mailing list on September 12. Arnaud, I hope you approve of this patch; it is more reliable than the previous method in tracking the correct dependencies. * This, together with some other minor recent changes on the Development branch, is between the "before_PSE_3" and "after_PSE_3" tags. Arnaud: if you

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 am trying to talk to an MGE Pulsar Extreme UPS over RS232 with the mge-shut driver but I'm having some problems. It appears to init OK but I can't, say, turn the outlets off, eg.. harrow:~>upsc mge@localhost battery.charge: 78 battery.charge.low: 20 battery.runtime: 05760 driver.name: mge-shut driver.parameter.port: /dev/cuad1 driver.version: 2.0.3 driver.version.internal: 0.65

j T wrote: > >- allow the value to be NULL if a subdriver does not require > > initialization. > > Am I right in thinking that this is simply a case of doing: > > subdriver_t some_subdriver = { > /* ... */ > some_format_serial, > NULL, > } > > Rather than: > > subdriver_t belkin_subdriver = { > /* ... */ >

Hi, We are looking towards a 8+ CO line setup (20 extensions) in our office but we do not want an IVR(auto-attendant) feature. All incoming will be answered by a receptionist. I have read the multi-line configuration for cisco 7960 thread in this list but that way I believe we could only display 6 incoming lines. What will happen to the rest? Does the expansion module for the cisco 7960 work

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 Jim ii ?nut ??????????????????????????????????2.7.4-13 ??????????????????????????all ?????????network UPS tools - metapackage ii ?nut-client ???????????????????????????2.7.4-13 ??????????????????????????amd64 ???????network UPS tools - clients ii ?nut-server ???????????????????????????2.7.4-13 ??????????????????????????amd64 ???????network UPS tools - core system debian 11 I'am

HI i'am using schema upsmon call : NOTIFYCMD /sbin/upssched and this part of upsschede strategy (working fine) device.model: Ellipse ECO 650 root at ---:~# cat /etc/nut/upssched.conf # Network UPS Tools - upssched.conf sample file CMDSCRIPT /opt/nut/bin/upssched-cmd PIPEFN /var/run/nut/upssched.pipe LOCKFN /var/run/nut/upssched.lock #

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

Well, either I misunderstood what you wrote or (my initially written post follows, probably misguided at start) I think your log contradicts your statements: > when my bash script receive events from TIMER like LINE-STATUS-xx > NOTIFYTYPE is always ONBATT > in all other cases, NOTIFYTYPE is TRUE and same as it was called by upsmon in the log I see : * Initial ONBATT: Apr 1 17:07:39

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