similar to: Online-UPS Xanto support status?

Hi Henning, you should get in touch with Carlos, who his developing a generic megatec driver (available from svn: http://eu1.networkupstools.org/source.html) Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer -

On 1/23/07, Henning Brauer <hb-nut@bsws.de> wrote: > good new first: the megatec driverin 2.0.5 now works with the Online > Xanto S3000R here - well, for the very basics. > > the UPS has NO way ofidentifying itself. It also does not respond to > the power ratings query ("F"). I previously used a hacked up fentonups > driver. This means the driver cannot figure out

Good morning, i have an Xanto S1000 USV the Manufactor is ONLINE USV-Systeme AG. I tried all the buildin drivers, also the driver for the driver for the Generic UPS, nothing worked for this UPS so now my question has anyone else this UPS and functional driver? Thanks and Greets Dennis

good new first: the megatec driverin 2.0.5 now works with the Online Xanto S3000R here - well, for the very basics. the UPS has NO way ofidentifying itself. It also does not respond to the power ratings query ("F"). I previously used a hacked up fentonups driver. This means the driver cannot figure out the battery voltage and thus no battery charge level, which is a problem in our

Dear Andreas, some googling revealed, you created a driver for the xanto series of online-usv.de. In what state it is currently? I've to manage a S2000 and would like to use nut for it, is it usable by now? Do you need another tester? TIA, Pete

please keep the list cc'ed when replying me. ---------- Forwarded message ---------- From: Andreas Thienemann <andreas@bawue.net> Date: 15 nov. 2005 15:36 Subject: Re: RE New xanto driver for NUT To: Arnaud Quette <aquette.dev@gmail.com> Hello Arnaud, On Tue, 15 Nov 2005, Arnaud Quette wrote: > is there really a need to separate it from the megatec. > we're currently

please keep the list cc'ed when replying me. ---------- Forwarded message ---------- From: Andreas Thienemann <andreas@bawue.net> Date: 15 nov. 2005 15:36 Subject: Re: RE New xanto driver for NUT To: Arnaud Quette <aquette.dev@gmail.com> Hello Arnaud, On Tue, 15 Nov 2005, Arnaud Quette wrote: > is there really a need to separate it from the megatec. > we're currently

* Charles Lepple <clepple at gmail.com> [2014-09-20 01:12]: > On Sep 19, 2014, at 5:18 PM, Stan Gammons <sg063015 at gmail.com> wrote: > > Looks like this patch fixed the problem. I see the status change now. > Good to hear. > I'm not familiar with the OpenBSD release process. Is that patch on track to be a part of the final 5.6 release? no, 5.6 is already cut.

Network UPS Tools version 2.0.5 has been released. http://www.networkupstools.org/ Direct access: - Download: http://www.networkupstools.org/source/2.0/nut-2.0.5.tar.gz - News: http://www.networkupstools.org/source/2.0/new-2.0.5.txt - ChangeLog: http://www.networkupstools.org/source/2.0/ChangeLog

Network UPS Tools version 2.0.5 has been released. http://www.networkupstools.org/ Direct access: - Download: http://www.networkupstools.org/source/2.0/nut-2.0.5.tar.gz - News: http://www.networkupstools.org/source/2.0/new-2.0.5.txt - ChangeLog: http://www.networkupstools.org/source/2.0/ChangeLog

corrupted checksums happen all the time with the 6-port serial card, even when only using one port (and I don't give a shit about the other ports, if anybody has a one-port laying around...) so stop whining already. $OpenBSD$ --- drivers/bcmxcp_ser.c.orig Wed Aug 23 11:15:54 2006 +++ drivers/bcmxcp_ser.c Wed Aug 23 11:26:37 2006 @@ -168,8 +168,8 @@ int get_answer(unsigned char *data, unsi

* Henning Brauer <hb-nut at bsws.de> [2014-09-20 13:39]: > * Charles Lepple <clepple at gmail.com> [2014-09-20 01:12]: > > On Sep 19, 2014, at 5:18 PM, Stan Gammons <sg063015 at gmail.com> wrote: > > > Looks like this patch fixed the problem. I see the status change now. > > Good to hear. > > I'm not familiar with the OpenBSD release process. Is

On Sep 19, 2014, at 5:18 PM, Stan Gammons <sg063015 at gmail.com> wrote: > Looks like this patch fixed the problem. I see the status change now. Good to hear. I'm not familiar with the OpenBSD release process. Is that patch on track to be a part of the final 5.6 release? -- Charles Lepple clepple at gmail

Hi developers, I would like to propose making a release soon from the current NUT trunk. There have been a lot of important changes since 2.0.5: new drivers added/refined (e.g. megatec_usb); the switch to Automake; the renaming of newhidups to usbhid-ups; automatic installation of hotplugging files; IPv6 support; improvements to the tripplite_usb driver; improvements to the gamatronic driver;

On 09/19/14 07:23, Charles Lepple wrote: > On Sep 19, 2014, at 7:26 AM, Stan Gammons <sg063015 at gmail.com> wrote: > >> --enable-debug-log was in the original makefile. I added --enable-debug. At this point I guess trying to build from source or go back to OpenBSD 5.5 are the only options left. > Ah, my confusion was that --enable-debug-log was wrapped in ".ifdef

Hi Alexander, How to megatec driver communication windows c++.NET or C#.net. Thanks. Yi?it YALNIZ?A -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20141023/2384ce84/attachment.html>

The documentation says the bridge will work as far as all interfaces have the same MTU, but I also read on this and other mailing lists people having problems when using jumbo frames. What is the current status of jumbo frames support in the bridge? It could also be useful to have the same info on the wiki page. Thanks. -- Luca Lesinigo -------------- next part -------------- An HTML

Hi, after my publisher has to shut down his business at the end of last year, it took several months to organize everything. But it's done! I'm happy to announce: The Dovecot book is available again. You can order it at Createspace: https://www.createspace.com/5942312 Or Amazon: https://www.amazon.com/dp/1534895701 https://www.amazon.co.uk/dp/1534895701

OK, I have removed the autoconf test for s6_addr32 (which is no longer used), and wrote a new test for IN6_IS_ADDR_V4MAPPED. The latter is probably portable, but since we're already in the business of testing, it does not hurt to do so. Arjen, I wonder about server/access.c, line 60-61: return (IN6_IS_ADDR_V4MAPPED(ip6) && ((((const u_int32_t *)ip6)[3] &

On Sep 23, 2014, at 3:55 AM, Henning Brauer <hb-nut at bsws.de> wrote: > We have upd(4) attaching to these devices now. Either nut needs a > driver getting status from upd (trivial, will show up in the > hw.sensors sysctl tree) or we need some way for nut still being able > to talk to the ups directly, without upd and nut interfering with each > other. While a upd(4) driver