similar to: Best Power cable?

+-----------------------------------------------------------------+ | | | Black APC 940-0024C Smart Signalling UPS Cable Wiring Diagram | | This information is verified and tested to be 100% correct. | | |

I have several Best "Fortress LI660", manufactured ~1995, which use bestfortress(8). nut has been monitoring two of them just fine for years via a USB/serial adaptor and homemade TXD/RXD/COMMON cable. I am now trying to properly set up LB shutdown and have a few questions. 1) ups.shutdown.delay is set in the driver: dstate_setinfo("ups.delay.shutdown",

[please use reply-all when responding - the list does not modify the reply-to header.] > On Nov 16, 2015, at 8:24 AM, R?bert SZAKSZ <robert at szaksz.eu> wrote: > > Hello, > > I have one UPS Infosec XP Pro 2500 RM and it works with windows sw RUPS2000. > Now I want to install this UPS as virtual server on vmware ESXi vMA - (SUSE SLES 11SP2 linux). > On this linux I

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

Hello, I have one UPS Infosec XP Pro 2500 RM and it works with windows sw RUPS2000. Now I want to install this UPS as virtual server on vmware ESXi vMA - (SUSE SLES 11SP2 linux). On this linux I have NUT 2.6.0 and I stopped now with configuration of genericups driver. Working cable (direct cable pin1-pin1 ... pin9-pin9) connection on Windows: PIN | PC | UPS

On Nov 23, 2015, at 10:21 AM, Olav Seyfarth <olav at seyfarth.de> wrote: > > I've noticed this tread: > http://lists.alioth.debian.org/pipermail/nut-upsdev/2014-November/006801.html > But unless I misunderstood something, the driver bestups should still > work in jessie, right? It should still work. > Might this be a clable issue? > > The cable is the original

Hi Charles, thank you VERY MUCH for all your hints. > If you have a jumper wire handy, you can connect the PC's TxD to RxD I should have tried to connect from another computer in the first place. Or access another device known to work from this computer. It turned out that the shield I used to connect the mainboard connector to the PC case expected another mainboard pin layout. So all I

Hello again, I have a Sola 305 (aka Powerware 3110) here connected via a serial INT-0051 cable which I am trying to get working with nut. The driver.list file indicates that nut supports the Sola 305 when connected via the INT-0025C cable using the genericups driver with upstype set to 7 but it does not mention the INT-0051. I was able to use the "Basic CheckUPS II" utility provided

I'm not 'overly' new to asterisk, but I am very new to the Digium card / Telco aspect of it. I was able to get a TE110p card, installed.. and hooked a t1 up to it. I'm using zttool to just look at 'some' output. Here is what it looks like when I just load it up: Current Alarms: No alarms. ? ? ? ? Sync Source:

Ethernet NIC driver for VMware's vmxnet3 From: Shreyas Bhatewara <sbhatewara at vmware.com> This patch adds driver support for VMware's virtual Ethernet NIC: vmxnet3 Guests running on VMware hypervisors supporting vmxnet3 device will thus have access to improved network functionalities and performance. Signed-off-by: Shreyas Bhatewara <sbhatewara at vmware.com>

Ethernet NIC driver for VMware's vmxnet3 From: Shreyas Bhatewara <sbhatewara at vmware.com> This patch adds driver support for VMware's virtual Ethernet NIC: vmxnet3 Guests running on VMware hypervisors supporting vmxnet3 device will thus have access to improved network functionalities and performance. Signed-off-by: Shreyas Bhatewara <sbhatewara at vmware.com>

Ethernet NIC driver for VMware's vmxnet3 From: Shreyas Bhatewara <sbhatewara at vmware.com> This patch adds driver support for VMware's virtual Ethernet NIC: vmxnet3 Guests running on VMware hypervisors supporting vmxnet3 device will thus have access to improved network functionalities and performance. Signed-off-by: Shreyas Bhatewara <sbhatewara at vmware.com> --- VMware

Ethernet NIC driver for VMware's vmxnet3 From: Shreyas Bhatewara <sbhatewara at vmware.com> This patch adds driver support for VMware's virtual Ethernet NIC: vmxnet3 Guests running on VMware hypervisors supporting vmxnet3 device will thus have access to improved network functionalities and performance. Signed-off-by: Shreyas Bhatewara <sbhatewara at vmware.com> --- VMware

Ethernet NIC driver for VMware's vmxnet3 From: Shreyas Bhatewara <sbhatewara at vmware.com> This patch adds driver support for VMware's virtual Ethernet NIC : vmxnet3 Guests running on VMware hypervisors supporting vmxnet3 device will thus have access to improved network functionalities and performance. Signed-off-by: Shreyas Bhatewara <sbhatewara at vmware.com> ---

Ethernet NIC driver for VMware's vmxnet3 From: Shreyas Bhatewara <sbhatewara at vmware.com> This patch adds driver support for VMware's virtual Ethernet NIC : vmxnet3 Guests running on VMware hypervisors supporting vmxnet3 device will thus have access to improved network functionalities and performance. Signed-off-by: Shreyas Bhatewara <sbhatewara at vmware.com> ---

Ethernet NIC driver for VMware's vmxnet3 From: Shreyas Bhatewara <sbhatewara at vmware.com> This patch adds driver support for VMware's virtual Ethernet NIC: vmxnet3 Guests running on VMware hypervisors supporting vmxnet3 device will thus have access to improved network functionalities and performance. Signed-off-by: Shreyas Bhatewara <sbhatewara at vmware.com>

Ethernet NIC driver for VMware's vmxnet3 From: Shreyas Bhatewara <sbhatewara at vmware.com> This patch adds driver support for VMware's virtual Ethernet NIC: vmxnet3 Guests running on VMware hypervisors supporting vmxnet3 device will thus have access to improved network functionalities and performance. Signed-off-by: Shreyas Bhatewara <sbhatewara at vmware.com>

I am trying to get this UPS talking with NUT (2.2.0) under Fedora 7/CentOS5. I have searched the mailing list and found some infos: http://lists.alioth.debian.org/pipermail/nut-upsdev/2007-February/001799.html but I'm not really sure how that helps me. USB would be cool but I don't really need that, it just has to work. I have also found a document that shows the pinout of the com port

Hi list, on my previous (lenny or squeeze) machine, I had it up and running, but that machine and configs are gone - and on my new jessie machine (see device and config details below) I cannot start the driver: # /lib/nut/bestups -DDDDD -a Patriot_Pro_II_750 0.000000 debug level is '5' 0.000806 send_to_all: SETINFO device.type "ups" 0.000842 send_to_all:

> What driver are you using? You can try the "masterguard" driver, or "megatec". I have tried the "masterguard" driver. The "megatec" doesn't work as well, it says that it is not detecting a Megatec protocol UPS. I think I will try swapping the RXD and TXD pins. Steve