similar to: Tripplite SmartUPS

Charles, maybe we are getting closer :-) > The tripplite_serial_protocol branch has some debug statements that will show up if you run "sudo drivers/tripplite -D -a name-of-ups" from the nut directory. Network UPS Tools - Tripp-Lite SmartUPS driver 0.91 (2.7.4-432-gafd90f5a) ?? 0.000000??? [D1] debug level is '1' ?? 0.177766??? [D1] W value = 0x86 ?? 0.177782??? [D1] L

2009/5/3 Thomas Juerges > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Arnaud, > Hi Thomas, > I just checked the 2.4.1 version of nut and found that you forgot to add > my old UPS model (APC Smart-UPS 900). I guess it is because you were > busy at the time when I sent you the patch. So here it goes again. :) > uh, right sorry. I was pretty sure I applied

Hi, I am using kernel 3.7-rc6. I have written a test application for extended attributes and have for some folders a wired behaviour: #include <stdio.h> #include <string.h> #include <attr/xattr.h> char attrs[1024]; ssize_t attrslen; int i; char value[1024]; ssize_t valuelen; int main(int argc, char *argv[]) { if (argc != 2) { fprintf(stderr, "Syntax: testxattr

We recently had to replace an old APC SmartUPS 3000 with a newer 3000VA (the 2U one). It has both serial and USB in the back (with an RJ-45 on the end of the serial cable). I can't get the apcsmart driver to connect. I figured it should work the exact same as the old UPS, with /dev/ttyS0 as the port (I'm using the same port on the server that the last one was plugged into). I even

Hi, Charles I'm trying compilation but there is no configure command in the cloned git directory of nut. D?a 08.10.2017 o 23:47 Charles Lepple nap?sal(a): > On Oct 8, 2017, at 4:34 PM, tuharsky at misbb.sk wrote: >> Thank You for You reply, Charles >> >> >> D?a 07.10.2017 o 14:30 Charles Lepple nap?sal(a): >>> Is the "lan4.1" cable different

Hi, I received the message: btrfs: unlinked 34 orphans Just out of couriosity: what does it mean ? Thanks in advance Bye, David Arendt -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Hej! Hope nut-upsuser is an appropriate place to post additional info about the smartups protocol, please tell me if not. I got an APC Smartups 2200 (5U Rack Mount, European/230V version, 48V batteries) a couple of days ago, was very happy to find the protocol description at http://www.networkupstools.org/protocols/apcsmart.html, and started to play. At the point when everything was working

I'm trying to setup a server controlling 8 ups, 6 APC Smartups 1500 and two 1000. Because of the number of ups, i connected them using usb cables. I'm using Debian Etch AMD64 and nut 2.2.0 from testing (already tried 2.0 from stable, but had problems reading the ups serials and all the following problems of 2.2). This is my ups.conf: [ups2] driver = usbhid-ups port =

I've having trouble understanding the NUT compatibility page. Is it compatible with the OMNISMART300? Or the OMNI900LCD? The compatibility page said for instance SMART550 -- tripplite_usb SmartUPS -- tripplite OMNI650LCD -- usbhid_ups so I'm not sure if an OMNISMART300 is like a Smart, or a SMART, or an OMNI, or even if it's supported at all. Thanks in advance for any help!

Hello list- Anyone with Tripplite SMX1500XLRT2U (http://www.tripplite.com/EN/products/model.cfm?txtModelID=2687) successfully integrated with NUT through serial port? I'm trying to connect to SMX1500XLRT2U using serial cable shipped with UPS under FreeBSD 6.3-STABLE and NUT 2.2.2 installed from ports. Unfortunately, it looks like it couldn't be recognized. %dmesg | grep sio sio0:

I do have some of the more modern protocol documentation for Tripplite from the tripplite engineers, if someone is working on updating the Tripplite drivers. Their protocols are horrible. Thomas On Tue, Oct 10, 2017 at 1:37 AM, <tuharsky at misbb.sk> wrote: > Charles, maybe we are getting closer :-) > >> The tripplite_serial_protocol branch has some debug statements that

On Oct 10, 2017, at 1:37 AM, tuharsky at misbb.sk wrote: > > Charles, maybe we are getting closer :-) >> The tripplite_serial_protocol branch has some debug statements that will show up if you run "sudo drivers/tripplite -D -a name-of-ups" from the nut directory. > Network UPS Tools - Tripp-Lite SmartUPS driver 0.91 (2.7.4-432-gafd90f5a) > 0.000000 [D1] debug

Hi everyone, On a newly installed AIX-LPAR (oslevel 5.3.9) we added the current samba version 3.2.8. Installation and configuration did not reveal any problem. The problems show about 5 Minutes after services startup. After starting the samba services the winbind daemon uses lots of CPU time and memory. Wbinfo -u and wbinfo -g work after initial startup. We cannot connect to any share on the

Hello all, after migration from 3.0.26a to 3.4.2 we get lots of the following messages in our winbind-idmap logfile. Has anybody seen this before? [2009/11/10 10:51:14, 0] winbindd/idmap.c:201(smb_register_idmap_alloc) idmap_alloc module ldap already registered! [2009/11/10 10:51:14, 0] winbindd/idmap.c:201(smb_register_idmap_alloc) idmap_alloc module tdb already registered! [2009/11/10

I'm having trouble with a TrippLite SU3000XLCD. I'm using a Raspberry Pi running Raspbian (wheezy) with NUT 2.6.4. I can monitor my older TrippLite UPSs, mostly SU1000RT2Us, with this Pi and a USB to serial adapter. My first thought with the SU3000XLCD was to use the USB port instead of the serial port as that's the "modern" thing to do. When I plugged the USB cable in

Hi All, I've got two APC SmartUPS's that behave differently with nut, I have a SmartUPS1400 & a SmartUPS1250. I'm fairly sure this isn't a nut problem but more likely a problem with the age of the SmartUPS1250 and the apcsmart driver not being able to identify it. Under the APC Powerchute software the same monitoring & command parameters are available for both

We're looking at replacing some old APC SmartUPS 5000s with something that has USB so NUT can more easily talk with it (and yes, I've tried USB-RS232 adapters and every one I tried started kicking out errors within a few hours). One of the bids we have is for a "Tripp Lite UPS Smart Online 5000VA 4500W Rackmount 5kVA 200V/240V" as the potential replacement unit. I have no

Thanks, now I started getting messages from the list. As you advised, I renamed the mib file NETCARD.mib to Tripplite and ran command ./gen-snmp-subdriver.sh -H 10.200.254.39 -c public -n Tripplite Here is what it says: snmp_build: unknown failuresnmpget: Error building ASN.1 representation (Can't build OID for variable) COUNT = 0 / 0 Creating tripplite-mib.h Creating tripplite-mib.c Done.

I have a SmartUPS 750 (SUA750) which has the temperature and humidity SmartSlot card installed. When NUT 2.2 communicates with this UPS over /dev/ttyS0 using apcsmart, using the APC Smart cable connected to the SUA750 serial port, and this ups.conf: [su700] driver=apcsmart port = /dev/ttyS0 I can see the ambient temperature and humidity data with "upsc su700 at

[Please keep the list CC'd. Thanks!] On Feb 13, 2014, at 4:55 AM, ??? ????? wrote: > Can you try adding "-v 1" to the snmpwalk command? If that works, we can add it to gen-snmp-subdriver.sh. > > Yes, I tried it before, ran command "snmpwalk -v 1 -On -c public 10.200.254.39 .1.3.6.1.4.1.935" > > Output: > .1.3.6.1.4.1.935 = NULL > Error: OID not