similar to: Tripplite InternetOffice350 serial

---------- Forwarded Message ---------- Subject: [PATCH] New to nut project Date: Friday, 6. November 2009 From: Patrick Levesque <patrickl at verint.com> To: Thomas Jarosch <thomas.jarosch at intra2net.com> As requested, here is my patch file including all my modification to the 2.4.1 tarball from the web site. On Friday 06 November 2009 05:41:29 you wrote: > Hello Patrick,

I have been working on supporting the TrippLite Internet350SER (serial connection only using communication protocol 1004) in nuts.2.4.1. I sent a patch around 2009/11/9. I just look at the 2.4.3 release and the support for this model does not look to be added in either tripplite driver. Can I help to add support in the project? -- Pat This electronic message may contain proprietary and

I have tried to support a TrippLite Internet350SER UPS using a serial cable (The only connection on this model) using the 2.4 code branch. It uses the Protocol 1004 from the tripplite specification that can be use either used on serial or USB device. Since my device was only serial, I worked only on the serial integration. Since I found nothing in tripplite.c, tripplite-hid.c, tripplitesu.c to

Hello, I'm newbie with NUT, I'm trying to get work a *Tripp-Lite Internet350Ser*, a small UPS with serial port. The only reference about, is a modification patch that Mr. Patrick Levesque did for NUT 2.4.1 but the actual 2.6.1 looks to not have it yet. I tried all tripp and generic drivers but no success. Has anyone luck with this Tripp-Lite model? Thanks! Iv?n Escobar

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:

On Wed, Oct 1, 2008 at 7:30 AM, Roman Serbski <mefystofel at gmail.com> wrote: >> Definitely seems like a permissions problem. >> >> It's been a while since I messed with USB on FreeBSD. What do the >> permissions look like on /dev/ugen*? What modifications did you make >> to /etc/devfs.rules? > > Thanks a lot Charles! I think I managed to get NUT

Hello, I'm curious where I can find the config for the kernel included with the CentOS 5.2 x86_64 installer. I need to verify hardware compatibility (especially ethernet and SATA) prior to making a purchase decision, and reckon that seeing what's included with the installer would be the most direct way. Thanks for any leads, Ian

Hello, I'm trying to configure my user_attrs using LDAP as the userdb so that dovecot knows what secondary groups a user is a member of. The LDAP backend is an Open Directory implementation, which stores secondary group affiliations as memberUid attributes in cn=groupname,cn=groups,dc=dns,dc=name,dc=server. With ldapsearch, my query would be: ldapsearch -x -b

Hello, I have a ZFS filesystem (zpool version 26 on Nexenta CP 3.01) which I''d like to rollback but it''s having an existential crisis. Here''s what I see: root at bambi:/# zfs rollback bambi/faline/userdocs at AutoD-2010-09-28 cannot rollback to ''bambi/faline/userdocs at AutoD-2010-09-28'': more recent snapshots exist use ''-r'' to

I have a TrippLite SmartPro UP (SMART3000RM2U) that shipped with the DB9 cable# 73-0866. nut doesn't recognize the UPS using the tripplite driver. I found this page: http://www.tripplite.com/support/download/PA12/help/device.htm The link lists the SmartPro series as using the cables 73-0724 or 73-0844 and the Internet 350/525 is listed as using a cable 73-0866. I have a few 73-0844s

These patches allow this device to function in nut.. diff --git a/trunk/drivers/tripplite-hid.c b/new/drivers/tripplite-hid.c index c36da98..dddd13c 100644 --- a/trunk/drivers/tripplite-hid.c +++ b/new/drivers/tripplite-hid.c @@ -71,6 +71,8 @@ static usb_device_id_t tripplite_usb_device_table[] = { { USB_DEVICE(TRIPPLITE_VENDORID, 0x2005), battery_scale_0dot1 }, /* e.g. TrippLite

Thanks. As mentioned, deadtime can't be set for snmp-ups. You see this in the logs. Mar 31 09:08:30 freenas notifier: Fatal error: 'DEADTIME' is not a valid variable name for this driver. Mar 31 09:08:30 freenas notifier: Look in the man page or call this driver with -h for a list of valid variable names and flags. While looking at /var/log/messages I also see this when starting

Can anyone help getting a Tripplite SU2200XL to work with nut 2.0.3 using the supplied serial cable? Starting the ups service yields: Starting tripplitesu: Network UPS Tools - Tripp Lite SmartOnline driver 0.02 (2.0.3) Unable to detect Tripp Lite SmartOnline UPS on port /dev/ttyS0 I also have Tripplite's PowerAlert 12 software installed and when run it finds the UPS without a problem. So

We have multiple TrippLite Omni900LCD UPS. There are a couple pieces of equipment connected to each UPS. I would like to connect the UPSs to one computer through USB which would shutdown the appropriate equipment based on events monitored by upsmon using upssched. I've configured NUT using usbhid-ups driver and compiled/installed NUT. I've done some testing and it seems to work.

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

I've tried looking for documentation on configuring NUT for Ubuntu 12.04 over SNMP with a Tripplite UPS, but there isn't a lot of SNMP configurations tutorials out there from what I've seen. I haven't been able to get automatic shutdown to work. The driver I've been using is usbhid-ups which is generic for Tripplite, but I've reviewed several other UPS driver names and some

Hi list- I'm having problems with TrippLite SMX1500LCD not being detected by NUT under FreeBSD 6.3-RC2. NUT 2.2.1 was installed from ports with the following options: WITH_USB=true WITH_SNMP=true WITHOUT_IPV6=true WITH_LIBUPSCLIENT=true WITH_CGI=true I use USB cable shipped with TrippLite and 'usbdevs -v' shows the following: ... Controller /dev/usb2: addr 1: full speed, self

Hi Al, I'm currently not much available, so I've fwded your mail to the nut list... You might get more reactivity this way... 2007/11/20, Al Grimstad <al at grimstad.mv.com>: > Hi. I don't have the energy or time to subscribe to one of the nut > mailing lists, but this brief FYI may be useful. > > I believe there has been a regression with respect to nut and the

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

At the company I work for, we are using many TrippLite OMNI900LCD UPSs and are having difficulty setting the lower transfer threshold voltage. On our other model, the Eaton MGE-3S550, this can be set using upsrw to set the input.transfer.lowsetting, but on the Omni900, this option is not available. In our testing, it defaults to ~95v but we want to set it to 84v. More info: - OS = OpenSuse 13.1 -