search for: tripplites

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 for the quick response Charles! I may not have gotten the correct output from the snmpwalk, let me know if the attachment is usable. Thanks! New data added, here is the gdb output: Reading symbols from /usr/bin/snmp-ups...(no debugging symbols found)...done. (gdb) run -a tripplite -DD Starting program: /usr/bin/snmp-ups -a tripplite -DD warning: Could not load shared library symbols for

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

No, it's not. I'd defer to the list for tips on that one. First thing I'd try if no one else has ideas is checking lsusb and restarting the service. Thank you, David Zomaya Tripp Lite<http://www.tripplite.com/> ________________________________ From: Tom Cooper <tom at cooperfamily.xyz> Sent: Wednesday, May 20, 2020 7:00 PM To: David Zomaya Cc: nut-upsuser

On Feb 24, 2014, at 10:29 PM, Jason R Begley wrote: > Thanks for the quick response Charles! I may not have gotten the correct output from the snmpwalk, let me know if the attachment is usable. Thanks! Sorry, it's basically all comments. Do you have the stdout from the subdriver script? Also, how is the MIB file installed? > New data added, here is the gdb output: > Reading

Just started using NUT and having a problem. I'm not sure if it is even NUT that is causing the issue. I'm running the latest FreeNAS 9.3 release. Network UPS Tools upsmon 2.7.2. The UPS is a Tripplite SU6000RT4UHVPM with the SNMPwebcard installed. I'm trying to use the SNMPwebcard, not USB or Serial. I've updated the SNMPwebcard to the latest firmware version (see below). In

Glad to hear it's working, thanks Tom. Network UPS Tools team: is fixing this as simple as me telling you what new UPS protocols are HID-PDC compliant? Thank you, David Zomaya Tripp Lite<http://www.tripplite.com/> ________________________________ From: Tom Cooper <tom at cooperfamily.xyz> Sent: Wednesday, May 20, 2020 2:42 PM To: David Zomaya Cc: nut-upsuser Subject: Re:

David, Thanks again for your help today.  You're amazing. If the folks on the list could chime in - thoughts about what I could try next? May 20 19:57:28 elmer upsmon[3828]: Poll UPS [tripplite at localhost] failed - Data stale pi at elmer:/home/macbackup $ lsusb Bus 002 Device 006: ID 0bc2:3343 Seagate RSS LLC Bus 002 Device 005: ID 0bc2:3343 Seagate RSS LLC Bus 002 Device

On Mar 31, 2015, at 9:07 AM, Jason Gould <jgould at cddiagnostics.com> wrote: > I missed that snmp-ups set pollfreq to 30 by default. I?d hope that it would set deadtime to an appropriate value as well than, no? Is there a way to query what the settings are or what the defaults are? There is a TODO comment in snmp-ups that mentions doing something similar to usbhid-ups: just poll the

Hi, When I start upsd under normal conditions, I get this: -------------------------------------------------------------------------------- Network UPS Tools upsd 2.0.4 /etc/nut/upsd.conf is world readable Can't connect to UPS [tripplite] (tripplite_usb-auto): No such file or directory /etc/nut/upsd.users is world readable Synchronizing........ giving up

I have been working with NUT to get this working since upgrading to a web snmp card in a UPS. I keep getting seg faults when running snmp-ups also. Below is the output. kernel: [1365065.178230] snmp-ups[1940]: segfault at 0 ip b7555470 sp bf8d89e8 error 4 in libc-2.18.so[b74c2000+1a9000] Running: Arch i686 current Nut is current git Device is Tripp Lite SU2200XLa with WEBSNMPCARD running

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

I'm not seeing this in the log.  I'm guessing that's not great. May 20 19:57:28 elmer upsmon[3828]: Poll UPS [tripplite at localhost] failed - Data stale May 20 19:57:33 elmer upsmon[3828]: Poll UPS [tripplite at localhost] failed - Data stale May 20 19:57:38 elmer upsmon[3828]: Poll UPS [tripplite at localhost] failed - Data stale May 20 19:57:43 elmer upsmon[3828]: Poll UPS

On 2/24/2014 11:10 PM, Charles Lepple wrote: > On Feb 24, 2014, at 10:29 PM, Jason R Begley wrote: > >> Thanks for the quick response Charles! I may not have gotten the correct output from the snmpwalk, let me know if the attachment is usable. Thanks! > Sorry, it's basically all comments. Do you have the stdout from the subdriver script? Also, how is the MIB file installed?

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:

...these drivers? Is there another driver that's known to work with this UPS or can this one be "tweaked" to work? Can it be as simple as a baud rate mismatch? I'm not having much luck querying the serial port's settings. In ups.conf I have: [UPS-0040] driver = tripplitesu # driver = tripplite port = /dev/ttyACM0 desc = "TrippLite SU3000XLCD" using tripplitesu: upsdrvctl start Network UPS Tools - UPS driver controller 2.6.4 Network UPS Tools - Tripp Lite SmartOnline driver 0.03 (2.6.4) Warning: This is an experimental driver. S...

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

Hello List, David: I’ thanking you … :-) I’m using the tripplite_usb driver and the barcode on mine says: 9347AIOBC470902728 or 9347A10BC470902728. with pictures… https://drive.google.com/file/d/1SJWDr0g95KOD-FpbOPHUyl9bsbOKePlD/view?usp=sharing https://drive.google.com/file/d/1SFMT-GbZRcRO03gEy_7SszZ43-LYmEZM/view?usp=sharing

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 the cable is connected properly. The details: CentOS 4...

...e 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. Unfortunately all the USB ports are on the same bus for the computers that I could use for this and the TrippLites seem to use the same serial number. Any way to uniquely identify the UPSs to NUT? Or maybe to set a value in the UPS that could be used to identify the UPS? Thanks.