similar to: Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

> What does that revision number correspond to in FreeBSD release numbers? (e.g. 9.3, 10.0) FreeBSD 10.2-RELEASE #0 r286738M the last person probably wasn't able to give the ./configure probably because most people uses the precompiled iso to install NAS4Free.? if you need the ./configure I might have to look for their source on GitHub or something. /usr/local/libexec/nut/usbhid-ups -a

On Aug 17, 2015, at 1:00 AM, Johnny Wong <e430benz98 at yahoo.com> wrote: > > OS = NAS4Free (FreeBSD Revision: 199506) What does that revision number correspond to in FreeBSD release numbers? (e.g. 9.3, 10.0) > NUT Version = 2.7.3 for other parts of NUT version is listed below > NUT is part of the NAS4Free distribution > Device = Tripp Lite SMART1300LCDT URL

I have gotten the links to the ./configure for NUT for NAS4Free see nas4free build makefile http://sourceforge.net/p/nas4free/code/ ... t/Makefile config files: http://sourceforge.net/p/nas4free/code/ ... nut/files/ I hope this give some insights On Wednesday, August 19, 2015 6:00 AM, Charles Lepple <clepple at gmail.com> wrote: On Aug 19, 2015, at 12:08 AM, Johnny Wong

Here are couple of things I tried. 1) Changed the USB cable. Same problem 2) I put an old CyberPower CP550SL w/USB&SERIAL and it recognize it right away via the USB port I don?t know if that will give you any insight or eliminate certain things with the Tripp Lite SMART1300LCDT or not. Sent from Mail for Windows 10 From: Charles Lepple Sent: Tuesday, August 18, 2015 6:37 PM To: Johnny

Here are all the usbconfig outputs you have requested. I have left a message with the Dev for NAS4Free to give up the ./configure for NUT portion.? I am hoping they will... usbconfig -u 0 -a 5 dump_device_desc? datanas: ~# usbconfig -u 0 -a 5 dump_device_desc ugen0.5: <TRIPP LITE UPS Tripp Lite> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (100mA)? bLength = 0x0012 ? bDescriptorType =

Did my last message get through? I got a message from the list saying it "bounced" or something like that? Sent from Mail for Windows 10 From: Charles Lepple Sent: Wednesday, August 19, 2015 6:00 AM To: Johnny Wong Cc: nut-upsuser at lists.alioth.debian.org Subject: Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3 On Aug 19, 2015, at 12:08 AM, Johnny Wong

So when the UPS is communicating with the driver... it seems to work.? Problem is now that it keeps disconnecting.? Any recommendation on how to keep the drivers from disconnecting using the usb_set_altinterface?? (PS.? Is there a specific value to use?)? Or this confirms there is an issue with the usbhid-ups driver with the FreeBSD 10.2 kernel? upsc upstl1300 battery.charge: 100

> Is it possible that there is another copy of the driver running in the background? There is apparently an issue where we only >write a PID file when the driver goes into the background, and "-D" prevents that. I don't see another usbhid-ups running ... unless its "hidden".... I would have to install the unhide package then.... /var/run/devd.pid

On Aug 19, 2015, at 9:00 AM, Charles Lepple <clepple at gmail.com> wrote: > > On Aug 19, 2015, at 12:08 AM, Johnny Wong <e430benz98 at yahoo.com> wrote: >> >> Here are couple of things I tried. >> >> 1) Changed the USB cable. Same problem >> 2) I put an old CyberPower CP550SL w/USB&SERIAL and it recognize it right away via the USB

On Aug 17, 2015, at 11:56 AM, Johnny Wong <e430benz98 at yahoo.com> wrote: > > > What does that revision number correspond to in FreeBSD release numbers? (e.g. 9.3, 10.0) > > FreeBSD 10.2-RELEASE #0 r286738M Okay, thanks. I think this is the first report of FreeBSD 10.2, so hopefully it is not an issue inherent in the OS. I will see if I can upgrade one of my machines to

>Just for grins, can you try adding "usb_set_altinterface" to the ups.conf section for your UPS, and see if that changes this part of the log? (That is, after "[upstl1300]"). Here is the output with the usb_set_altinterface?added to ups.conf or at least partially output because it keeps going in a loop. ? 46.820206???? Checking device (09AE/3016) (/dev/usb//dev/ugen0.5) ?

On Aug 19, 2015, at 12:08 AM, Johnny Wong <e430benz98 at yahoo.com> wrote: > > Here are couple of things I tried. > > 1) Changed the USB cable. Same problem > 2) I put an old CyberPower CP550SL w/USB&SERIAL and it recognize it right away via the USB port > I don?t know if that will give you any insight or eliminate certain things with the Tripp Lite

Tripp Lite SMART1300LCDT # upsc ups battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 30 battery.runtime: 2951 battery.type: PbAC battery.voltage: 0.0 battery.voltage.nominal: 24.0 device.mfr: Tripp Lite device.model: TRIPP LITE UPS device.serial: 2250AVLSM872100251 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

On Aug 7, 2013, at 10:43 AM, Matthew Lenz wrote: > Tripp Lite SMART1300LCDT > > # upsc ups [...] > battery.voltage: 0.0 > battery.voltage.nominal: 24.0 [...] > input.frequency: 5990.0 > input.transfer.high: 150.0 > input.transfer.low: 92.0 > input.voltage: 0.0 > input.voltage.nominal: 120 > output.current: 100.00 > output.frequency: 5990.0 >

Just got back from vacation. A few things: * please don't use your yahoo.com email address to post to the NUT list. As of ~April 2014, Yahoo's spam policies are no longer compatible with mailing lists. Nobody with a gmail/hotmail address (other than people on the To/CC lines) will receive it, and eventually, the gmail/hotmail users will get kicked off the list.) I don't

On Aug 18, 2015, at 3:28 PM, Johnny Wong <e430benz98 at yahoo.com> wrote: > > So when the UPS is communicating with the driver... it seems to work. Problem is now that it keeps disconnecting. Is it possible that there is another copy of the driver running in the background? There is apparently an issue where we only write a PID file when the driver goes into the background, and

On Aug 18, 2015, at 9:07 PM, Johnny Wong <e430benz98 at yahoo.com> wrote: > >> Is it possible that there is another copy of the driver running in the background? There is apparently an issue where we only write a PID file when the driver goes into the background, and "-D" prevents that. > > I don't see another usbhid-ups running ... unless its

On Aug 22, 2015, at 1:15 PM, Johnny Wong <e430benz98 at yahoo.com> wrote: > > Did my last message get through? I got a message from the list saying it "bounced" or something like that? > I was just about to send an email about that. Your message got into the list archives: http://article.gmane.org/gmane.comp.monitoring.nut.user/9312 ...but it is possible that others

On Wed, Aug 7, 2013 at 6:47 PM, Charles Lepple wrote: > On Aug 7, 2013, at 10:43 AM, Matthew Lenz wrote: > >> Tripp Lite SMART1300LCDT >> >> # upsc ups > [...] >> battery.voltage: 0.0 >> battery.voltage.nominal: 24.0 > [...] >> input.frequency: 5990.0 >> input.transfer.high: 150.0 >> input.transfer.low: 92.0 >> input.voltage: 0.0

I?m setting up a new system and installed a new UPS with nut. System Specifics: OS: Debian 3.16.36 Nut version: 2.7.2 Install method: apt-get Device: TRIPPLITE SMART1300LCDT using usbhid-ups driver Problem: The output from upsc has a few incorrect values. They appear to be a matter of scale. root at server:/etc/nut# upsc tripplite at localhost Init SSL without certificate database