similar to: Dynamix 650 VA USB UPS

Network UPS Tools version 2.6.3 has been released: http://www.networkupstools.org/ Direct access: - Download: http://www.networkupstools.org/source/2.6/nut-2.6.3.tar.gz - News: http://www.networkupstools.org/source/2.6/new-2.6.3.txt - ChangeLog: http://www.networkupstools.org/source/2.6/ChangeLog Arnaud and the NUT team -------------- next part -------------- An HTML attachment was scrubbed...

Hi, I have a Fenton Powerpal L660, when I try and configure nut with either the metatec or fentonups driver, and start upsd, the UPS instantly turns itself off. It used to work, until I changed my motherboard and CPU, which means it has a different bios and serial port setup. This is happening with Nut 2.0.1 and also Nut 2.0.5. I have an AMD64 bit processor, Mandriva 2007 64 bit. Any

Like Glen Ogilvie, I got a newer Dynamix 650 VA with USB connection, and was having trouble getting NUT to communicate with it. This appears to be the UPS that megatec_usb was built for - Vendor: 0x0001, Product: 0x0000, uses Megatec's software, has USB chip attached to internal serial lines, and has terrible USB implementation with fake HID tables. But megatec_usb would consistently fail.

2007/2/19, Glen Ogilvie <nelg@linuxsolutions.co.nz>: > Hi, > > I have a Fenton Powerpal L660, when I try and configure nut with either the > metatec or fentonups driver, and start upsd, the UPS instantly turns itself > off. > > It used to work, until I changed my motherboard and CPU, which means it has > a different bios and serial port setup. > > This is

2007/2/19, Glen Ogilvie <nelg@linuxsolutions.co.nz>: > Hi, > > I have a Fenton Powerpal L660, when I try and configure nut with either the > metatec or fentonups driver, and start upsd, the UPS instantly turns itself > off. > > It used to work, until I changed my motherboard and CPU, which means it has > a different bios and serial port setup. > > This is

Hi, I've got two Dynamix UPS's, both of which are USB and don't seem to work with NUT yet. Can anyone give me some advise on where I should start with working on getting them working. I can do a little C programming, so happy to give things a go but need some guidance. Brian R. Smith (who also subscribes to this list) has one as well. I've attached the output of lsusb -v and

Hi Volker Kuhlmann and Richard Nelson, As both of you are interested in where I got up to with getting my Dynamix 1000 VA UPS working with Linux, here is the details. It works.. But not too well, as the driver still seems to need some work, and is not in the main nut source as far as I know. It also seems to sometimes not respond when it should. The manufacture has uses the same format as

Hi James, I'm referring to your post here: http://lists.alioth.debian.org/pipermail/nut-upsuser/2010-September/006201.html Have you got by chance any more info on the Dyamix 1000VA model? I was foolish to buy the USB version because it had a better display on the front. Is there any way to get this to go? I have tried all the USB drivers in NUT (on pfsense 2.0RC1) and none do anything

Hello everyone, has anyone ever tried to make this device work with Linux and NUT? This is what udevadm monitor says: UEVENT[1215983089.652345] add /devices/pci0000:00/0000:00:0f.2/usb1/1-1 (usb) UEVENT[1215983089.652427] add /class/usb_endpoint/usbdev1.4_ep00 (usb_endpoint) UEVENT[1215983089.657975] add /devices/pci0000:00/0000:00:0f.2/usb1/1-1/1-1:1.0 (usb) UDEV

Gidday all - I'm a new user to nut. I've got some cheap powerpal UPSs working fairly well. However I also have a new Dynamix UPS-1700D and an old Powercom KIN-1700 something unit that I cannot make work right. The best method I've found is "trial and error" which sounds a bit last-resort. Is there any better way to find out what protocol is used? -- Criggie

Here's a suggested change for receiver.c in version 2.5.2. It works in aix 4.3.3. *** receiver.c.org --- receiver.c *************** *** 427 **** ! rprintf(FERROR,"mkstemp %s failed\n",fnametmp); --- 427 ---- ! rprintf(FERROR,"mkstemp %s failed: %s\n",template,strerror(errno)); (Sorry, my version of diff doesn't seem to have the format I'm used to

Hi Alexander, thanks for your good work on the megatec_usb driver. I have made a few more (cosmetic) changes. Is the driver now working stably for your device? In particular, do the instant commands (and particularly "upsdrvctl -k") work properly? In this case, we could hopefully mark the device as "supported" and merge the driver to the main branch. There is still the

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

We've used rsync with an old ssh for a couple of years with no problems. Now trying to switch to openssh 3.0.2p1 so we can use protocol 2. Rsync makes the connection via ssh and does it's work. The problem is after rsync runs and exits on the server side the sshd session keeps running and isn't closing the connection. So the rsync client hangs waiting for the connection to end. Is

We needed the group id bit to always be set on directories when rsync creates them. We always run rsync from a script with just the -ltR options. The destination file system uses acl's to control file access so new files need to inherit the properties of the directories they're in. (This is for IBM's global storage architecture on Aix or Linux). I made the following changes to make

Hello. I have this UPS: Krauler UP-D1200VA Megatec USB protocol Vendor ID: 0x0001, Device ID: 0x0000 #KRAULER UP-D1200VA VER6.00 #220.0 004 23.50 50.0 Currently I have nut 2.2.0 installed from sources. Installation was successful except that I had to change a string in 52-nut-usbups.rules from: SUBSYSTEM!="usb_device", GOTO="nut-usbups_rules_end" to:

Hey all, thanks for your work on nut. I recently got myself a new cheap UPS, and have thus far determined very little about it. I can run whatever you like to help identify and work with it. So far I've played around with various settings and have had some limited success with the megatec_usb driver (Debian testing version): ----ups.conf---- [plexus] driver=megatec_usb model=500VA mfr=Plexus

Hi! I've uploaded Samba 3.0.1 RPMs for SLES 8, SuSE 8.2 and SuSE 9 including some CVS fixes to ftp://ftp.sernet.de/pub/samba http://ftp.sernet.de/pub/samba Merry Christmas from G?ttingen, Volker -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available Url :

Has anybody managed to get Fedora Core 3 and the zapata drivers working with the TDM400P cards? Everything is going fine until I do modprobe mcfxs Any ideas? It's a straight install of Fedora Core 3. Graeme -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20041129/026e1455/attachment.htm

Hi! I am trying to get an Atlantis-Land 1501 UPS to work under OpenBSD. The UPS works OK under Linux + megatec_usb driver+nut_2.2.2. What I get under OpenBSD is: root at puffwall:~ # dmesg OpenBSD 4.3 (GENERIC) #698: Wed Mar 12 11:07:05 MDT 2008 deraadt at i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III ("GenuineIntel" 686-class, 128KB L2