similar to: Help please UPS infosec and NUT on Raspberry PI.

Hello, I am trying to make my UPS system working with NUT but with no success. I got "No supported UPS detected" message. I use the blazer_usb driver since it was proposed to me by the web site. My NUT version is : 2.7.1 (installed from standard RPM), release 2.41 The UPS identification: INFOSEC X4 RM PLUS linux-2qya:~ # /usr/lib/ups/driver/blazer_usb -a infosec Network UPS Tools -

Ubuntu 8.04 Nut : Version: 2.2.1-2.1ubuntu7.2 Hello, I choose the megatec driver and I connect through a serial cable. I receive a "This UPS has an unsupported combination of battery voltage/number of batteries" message. I know this is not an error but I don't really what I have to do next. Here is the result of /lib/nut/megatec -a infosec -DDD debug level is '3'

Dear list, I'm proud to report that the megatec driver supports the following devices: Infosec XP Pro 1000 Kebo 1200D 'D Series' Thanks for such great software! Cheers, Tamas Csillag

Hi Arnaud, Is there any news about this hardware,does nut managed it right now ? Is there any technical information to make it working on debian ? Thanks for your help, Regards, DaneZ _____ From: Arnaud QUETTE [mailto:Arnaud.QUETTE@mgeups.com] To: DaneZ [mailto:david.guillotte@danez.no-ip.org] Sent: Mon, 17 Jul 2006 09:07:03 +0200 Subject: Re: RE Fw: INFOSEC 500 XP

I'm pretty sure, I've install pkg-config, but I will check it monday after my holliday. This is my test steps: - Shutting down nut-client (upsmon) - Only nut-server (driver + upsd) is running - upsmon.conf have been revert to normal shutdown, no upssched - upsc myups return ups stats then: upsmon -K -DDDDD, here is the output: kill: No such process UPS: myups at

I?m wondering if what I have done is good : # get the source from github on my computer # autogen.sh # name=nut # ./configure --prefix=/ --sysconfdir=/etc/$name --mandir=/usr/share/man --libdir=/usr/lib --includedir=/usr/include --datadir=/usr/share/$name --with-statepath=/var/run/nut --with-altpidpath=/var/run/nut --with-drvpath=/lib/nut --with-pidpath=/var/run/$name

Hi Charles, I am done with few things: I made the cable - looks good, because I see some activities. I upgraded NUT to 2.7.3. but I have no success to start driver(this are the outputs) nut.cfg MODE = netserver ups.conf [infosec] driver = nutdrv_qx (or blazer_ser) port = /dev/ttyS1 desc = "XP Pro 2500 RM" output(nutdrv_qx cmd upsdrvctl -DDD start) Network UPS

Hi everybody, In a christmas sequel I've been offered one of the units mentioned above. I've tried to connect it to my Fedora 8 workstation but rapidly concluded it's not yet supported by NUT. So far, I've decompiled the Java classes of the manufacturer's application and noticed that it's most probably yet another kind of serial protocol through the USB. Since

I've download again nut source today from "https://github.com/networkupstools/nut/tree/voltronic-driver" and try compiliing the voltronic-driver. The drivers is working fine (ie computer is shutting down) except for the shutdown of the ups. I can shutdown the ups by sending the command "shutdown.return" but standard shutdown doesn't work. upsmon -K return: kill: No

Hello, I'm sorry if i'm not sending to the good email adress, please transfer this mail to the good one if necessary... I have tested and run the driver named "blazerd_usb" with differents products from the infosec company (tested on the following UPS : X2, X3, X4, E2, E3, E4) Is it possible to add the to the Hardware compatibility list ? Thank you, Regarde, Jeremy

Hi, Sorry for my poor english but it isn?t my native language. I?m testing an infosec E4 with nut-2.6.4-2.3 on Proxmox ve 3.0 (based on debian wheezy). The drivers that match this ups, is blazer_usb. Btw, I have try nut-2.6.5 with unstable repository from wheezy, but it still doesn?t fully work. I can shutdown my computer when battery is low, but unfortunately I can?t shutdown ups. Like said on

Great, it's working fine. I'm using upssched to shutdown computer after 15mn when on battery. Should I trigger "upsmon -c fsd" with my script? I mean, is it the normal way to shutdown both computer and ups. Best regards, -----Message d'origine----- From: Charles Lepple Sent: Monday, August 26, 2013 3:07 AM To: James HORLEY Cc: nut-upsuser list Subject: Re: [Nut-upsuser]

I compile nut with the voltronic-driver on my computer then I've copy the driver "/lib/nut/voltronic_ser" on the server. I can now shutdown the ups using "upscmd -u admin myups shutdown.return". My first question is, is it really ok to only take the driver whithout taking the whole package? I'm using upssched to shutdown server after 15mn on battery, the

On Aug 26, 2013, at 6:22 AM, James HORLEY wrote: > I've download again nut source today from "https://github.com/networkupstools/nut/tree/voltronic-driver" and try compiliing the voltronic-driver. This branch has been merged in, and will be part of 2.7.1 when it is released. > The drivers is working fine (ie computer is shutting down) except for the shutdown of the ups. >

Bonjour, Je souheterais utilis? la version qui permet le '-x generic',mais je ne sais pas ou la recuperer car ca devrait solutionner mon probleme (cf mail ci-dessous) DaneZ _____ From: DaneZ [mailto:david.guillotte@danez.no-ip.org] To: arnaud.quette@mgeups.com Sent: Sat, 08 Jul 2006 23:24:06 +0200 Subject: Fw: INFOSEC 500 XP en USB _____ Bonjour Arnaud, Je me

On Aug 1, 2013, at 8:15 AM, Charles Lepple wrote: > On Jul 29, 2013, at 7:12 AM, James HORLEY wrote: > >> There?s a software advised by the constructor that work on linux (http://www.power-software-download.com/viewpower.html), unfortunately it?s heavy (tomcat and java) and I don?t find it as flexible as NUT. > > We have a development branch called "voltronic-driver"

On Jul 31, 2013, at 9:07 AM, James HORLEY wrote: > I?m wondering if what I have done is good : > # get the source from github on my computer > # autogen.sh > # name=nut > # ./configure --prefix=/ --sysconfdir=/etc/$name --mandir=/usr/share/man > --libdir=/usr/lib --includedir=/usr/include --datadir=/usr/share/$name > --with-statepath=/var/run/nut

Hi Charles, >----- Original Message ----- >From: "Charles Lepple" <clepple at gmail.com> >To: "R?bert SZAKSZ" <robert at szaksz.eu> >Cc: nut-upsuser at lists.alioth.debian.org >Sent: Monday, November 16, 2015 3:20:17 PM >Subject: Re: [Nut-upsuser] Contact-closure UPS > >[please use reply-all when responding - the list does not modify the

No progress has been made: cable is UPS - PC 6 - 3 7 - 5 9 - 2 for ./blazer_ser -DDDDD -a infosec 0.000000 send_to_all: SETINFO driver.parameter.port "/dev/ttyS1" 0.000323 debug level is '5' 0.103068 send_to_all: SETINFO device.type "ups" 0.103104 send_to_all: SETINFO driver.version "2.7.3" 0.103118 send_to_all: SETINFO

Hi, I am considering installing several `servers' in a facility that needs to conform with the products listed at: DSD Approved Products http://www.dsd.gov.au/infosec/evaluation_services/epl/dap.html As far as i can see freebsd performs above and beyond, for all the required criteria in the act. Can we see freebsd listed as an approved product in the near future? Best Regards, Jason - RF