Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-31 Thread johnny



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 want my Inbox flooded again with over a hundred  
bounce/unsubscribe messages. You can use your Yahoo address to sign up  
for GitHub, and create an issue there - it will allow the same sort of  
discussion, but the emails come from github rather than yahoo, so we  
don't have the same problem. I also don't like doing "private  
consulting" for free. Keeping the discussion on the mailing lists (or  
on GitHub) ensures that other people can search for the answers there.


Ok I will start using this email address other than gmail/Hotmail/yahoo lol


* I was recommending using a Linux live CD rather than FreeBSD because  
Tripp Lite supposedly supports a few Linux distributions, and if your  
UPS is somehow not talking to Linux, it might be a bad firmware  
version or other issue covered by the warranty. I'm not suggesting  
switching to Linux permanently, just boot from the live CD and  
configure NUT on Linux so you can rule out any potential  
Linux-vs-FreeBSD issues.


ohhh I thought you meant try using FREEBSD Live CD.  As for TripLite,  
they "supporting" two variants.  OpenSUSE and Fedora, but olll  
versions  Fedora 8 and OpenSUSE 11.  Plus they provide their own  
software(?)  It's call PowerAlert Local (PAL)



* if you still want to test on FreeBSD, I'm not sure what this will  
definitively tell us that we don't already know. With pkg_add, it will  
probably be NUT v2.7.2, and I don't really want to debug an older  
version of NUT. You could build from source, but that will be more  
time-consuming, and we should rule out the other hardware variables  
first.


yeah if I have to compile the source on my own, it might take a while  
on FreeBSD.  I wasn't able to pull the pkg anyway... it error out  
(can't remember the error)




Regards,

- Charles Lepple





On Aug 26, 2015, at 4:09 AM, Johnny Wong  wrote:



Ok!  I finally go the Ethernet going... Is there a specific way you  
want me to install the NUT package?  I was just going to use pkg_add  
-r nut






Sent from Mail for Windows 10


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser


Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-26 Thread Johnny Wong
Ok!  I finally go the Ethernet going... Is there a specific way you want me to 
install the NUT package?  I was just going to use pkg_add -r nut


Sent from Mail for Windows 10



From: Charles Lepple
Sent: Monday, August 24, 2015 5:53 PM
To: Johnny Wong
Cc: nut-upsuser@lists.alioth.debian.org
Subject: Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3


On Aug 19, 2015, at 9:00 AM, Charles Lepple  wrote:
> 
> On Aug 19, 2015, at 12:08 AM, Johnny Wong  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 SMART1300LCDT or not.
>> 
> 
> Thanks for testing the USB cable and the other UPS - those are good data 
> points.
> 
> I am surprised that I did not run across this thread earlier: 
> http://article.gmane.org/gmane.comp.monitoring.nut.user/8700 (SMART1500RM2UN 
> disconnects every 40-45 seconds)
> 
> I also did not see any changes in the FreeBSD source code that specifically 
> mention the USB alt setting (although they have an unbelievable number of 
> different ways to spell that). I will still try to set up a FreeBSD 10.2 box 
> at some point for system testing.

I set up a FreeBSD 10.2 system, and tested a USB MGE Evolution against NUT 
v2.7.3. No USB issues so far, and it's been running since this morning.

> 
> You might also try booting from a Linux live CD and using their version of 
> NUT to see if the SMART1300LCDT still disconnects. Tripp Lite has said that 
> they only support certain distributions of Linux (I don't recall which, but I 
> would assume Red Hat is among them), so if you can prove that there are 
> problems with a supported Linux distribution, you might be able to get 
> warranty service.

Curious to hear how this goes.

-- 
Charles Lepple
clepple@gmail





___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-24 Thread Johnny Wong

I loaded up FreedBSD 10.2 on a really old C2D system, but I can't find a 
Ethernet driver for it... so I am unable to actually load NUT on it.  I will 
have to work more on it this weekend
Sent from Mail for Windows 10



From: Charles Lepple
Sent: Monday, August 24, 2015 5:53 PM
To: Johnny Wong
Cc: nut-upsuser@lists.alioth.debian.org
Subject: Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3


On Aug 19, 2015, at 9:00 AM, Charles Lepple  wrote:
>
> On Aug 19, 2015, at 12:08 AM, Johnny Wong  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 SMART1300LCDT or not.
>>
>
> Thanks for testing the USB cable and the other UPS - those are good data 
> points.
>
> I am surprised that I did not run across this thread earlier: 
> http://article.gmane.org/gmane.comp.monitoring.nut.user/8700 (SMART1500RM2UN 
> disconnects every 40-45 seconds)
>
> I also did not see any changes in the FreeBSD source code that specifically 
> mention the USB alt setting (although they have an unbelievable number of 
> different ways to spell that). I will still try to set up a FreeBSD 10.2 box 
> at some point for system testing.

I set up a FreeBSD 10.2 system, and tested a USB MGE Evolution against NUT 
v2.7.3. No USB issues so far, and it's been running since this morning.

>
> You might also try booting from a Linux live CD and using their version of 
> NUT to see if the SMART1300LCDT still disconnects. Tripp Lite has said that 
> they only support certain distributions of Linux (I don't recall which, but I 
> would assume Red Hat is among them), so if you can prove that there are 
> problems with a supported Linux distribution, you might be able to get 
> warranty service.

Curious to hear how this goes.

--
Charles Lepple
clepple@gmail







---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-24 Thread Charles Lepple
On Aug 19, 2015, at 9:00 AM, Charles Lepple  wrote:
> 
> On Aug 19, 2015, at 12:08 AM, Johnny Wong  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 SMART1300LCDT or not.
>> 
> 
> Thanks for testing the USB cable and the other UPS - those are good data 
> points.
> 
> I am surprised that I did not run across this thread earlier: 
> http://article.gmane.org/gmane.comp.monitoring.nut.user/8700 (SMART1500RM2UN 
> disconnects every 40-45 seconds)
> 
> I also did not see any changes in the FreeBSD source code that specifically 
> mention the USB alt setting (although they have an unbelievable number of 
> different ways to spell that). I will still try to set up a FreeBSD 10.2 box 
> at some point for system testing.

I set up a FreeBSD 10.2 system, and tested a USB MGE Evolution against NUT 
v2.7.3. No USB issues so far, and it's been running since this morning.

> 
> You might also try booting from a Linux live CD and using their version of 
> NUT to see if the SMART1300LCDT still disconnects. Tripp Lite has said that 
> they only support certain distributions of Linux (I don't recall which, but I 
> would assume Red Hat is among them), so if you can prove that there are 
> problems with a supported Linux distribution, you might be able to get 
> warranty service.

Curious to hear how this goes.

-- 
Charles Lepple
clepple@gmail




___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-22 Thread e430benz98
Do you need me to resend the email about the nas4free configure for NUT! 

Sent from my LG G3.

-Original Message-
From: Charles Lepple 
To: Johnny Wong 
Cc: "nut-upsuser@lists.alioth.debian.org" 
Sent: Sat, 22 Aug 2015 12:10 PM
Subject: Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

On Aug 22, 2015, at 1:15 PM, Johnny Wong  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 might not receive it due to Yahoo's DMARC 
policy.

-- 
Charles Lepple
clepple@gmail



___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-22 Thread Charles Lepple
On Aug 22, 2015, at 1:15 PM, Johnny Wong  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 might not receive it due to Yahoo's DMARC 
policy.

-- 
Charles Lepple
clepple@gmail




___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser


Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-22 Thread Johnny Wong
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@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  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 SMART1300LCDT or not.
>  

Thanks for testing the USB cable and the other UPS - those are good data points.

I am surprised that I did not run across this thread earlier: 
http://article.gmane.org/gmane.comp.monitoring.nut.user/8700 (SMART1500RM2UN 
disconnects every 40-45 seconds)

I also did not see any changes in the FreeBSD source code that specifically 
mention the USB alt setting (although they have an unbelievable number of 
different ways to spell that). I will still try to set up a FreeBSD 10.2 box at 
some point for system testing.

You might also try booting from a Linux live CD and using their version of NUT 
to see if the SMART1300LCDT still disconnects. Tripp Lite has said that they 
only support certain distributions of Linux (I don't recall which, but I would 
assume Red Hat is among them), so if you can prove that there are problems with 
a supported Linux distribution, you might be able to get warranty service.

-- 
- Charles Lepple
https://ghz.cc/charles/




___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-21 Thread Johnny Wong
there might be a problem with the 2nd lnk... here is the linkjust incase
http://sourceforge.net/p/nas4free/code/HEAD/tree/trunk/build/ports/nut/files/ 


 On Friday, August 21, 2015 3:24 PM, Johnny Wong  
wrote:
   

 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  
wrote:
   

 On Aug 19, 2015, at 12:08 AM, Johnny Wong  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 SMART1300LCDT or not.
>  

Thanks for testing the USB cable and the other UPS - those are good data points.

I am surprised that I did not run across this thread earlier: 
http://article.gmane.org/gmane.comp.monitoring.nut.user/8700 (SMART1500RM2UN 
disconnects every 40-45 seconds)

I also did not see any changes in the FreeBSD source code that specifically 
mention the USB alt setting (although they have an unbelievable number of 
different ways to spell that). I will still try to set up a FreeBSD 10.2 box at 
some point for system testing.

You might also try booting from a Linux live CD and using their version of NUT 
to see if the SMART1300LCDT still disconnects. Tripp Lite has said that they 
only support certain distributions of Linux (I don't recall which, but I would 
assume Red Hat is among them), so if you can prove that there are problems with 
a supported Linux distribution, you might be able to get warranty service.

-- 
- Charles Lepple
https://ghz.cc/charles/



   

  ___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-21 Thread Johnny Wong
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  
wrote:
   

 On Aug 19, 2015, at 12:08 AM, Johnny Wong  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 SMART1300LCDT or not.
>  

Thanks for testing the USB cable and the other UPS - those are good data points.

I am surprised that I did not run across this thread earlier: 
http://article.gmane.org/gmane.comp.monitoring.nut.user/8700 (SMART1500RM2UN 
disconnects every 40-45 seconds)

I also did not see any changes in the FreeBSD source code that specifically 
mention the USB alt setting (although they have an unbelievable number of 
different ways to spell that). I will still try to set up a FreeBSD 10.2 box at 
some point for system testing.

You might also try booting from a Linux live CD and using their version of NUT 
to see if the SMART1300LCDT still disconnects. Tripp Lite has said that they 
only support certain distributions of Linux (I don't recall which, but I would 
assume Red Hat is among them), so if you can prove that there are problems with 
a supported Linux distribution, you might be able to get warranty service.

-- 
- Charles Lepple
https://ghz.cc/charles/



  ___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-19 Thread Charles Lepple
On Aug 19, 2015, at 12:08 AM, Johnny Wong  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 SMART1300LCDT or not.
>  

Thanks for testing the USB cable and the other UPS - those are good data points.

I am surprised that I did not run across this thread earlier: 
http://article.gmane.org/gmane.comp.monitoring.nut.user/8700 (SMART1500RM2UN 
disconnects every 40-45 seconds)

I also did not see any changes in the FreeBSD source code that specifically 
mention the USB alt setting (although they have an unbelievable number of 
different ways to spell that). I will still try to set up a FreeBSD 10.2 box at 
some point for system testing.

You might also try booting from a Linux live CD and using their version of NUT 
to see if the SMART1300LCDT still disconnects. Tripp Lite has said that they 
only support certain distributions of Linux (I don't recall which, but I would 
assume Red Hat is among them), so if you can prove that there are problems with 
a supported Linux distribution, you might be able to get warranty service.

-- 
- Charles Lepple
https://ghz.cc/charles/



___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-18 Thread 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 Wong
Cc: nut-upsuser@lists.alioth.debian.org
Subject: Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3


On Aug 18, 2015, at 9:07 PM, Johnny Wong  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 "hidden"  I would 
> have to install the unhide package then
> 

What I mean is that you can't have more than one usbhid-ups process talking to 
the same UPS at one time - regardless of whether they write a PID file. In the 
case of running with "-D", you would need to double-check for any in the 
background (and there was a PID file named usbhid-ups-upstl1300.pid). "ps 
auxww|grep [u]sbhid-ups" should show only one driver in either case.

Still looking into the altsetting issue. I would have to shuffle a few machines 
around to get a copy of 10.2 running on a box that isn't being actively used 
for anything else, but maybe there is something in their source control logs.

-- 
Charles Lepple
clepple@gmail





___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-18 Thread Johnny Wong
You were right, there was 2 process running.  

What I did was kill both the usbhid-ups processes and reloaded the drivers 
again.  Which still took about 10 tries before it would see the UPS.

Once it was loaded, same thing.  It would disconnect and connect 

Sent from Mail for Windows 10



From: Charles Lepple
Sent: Tuesday, August 18, 2015 6:37 PM
To: Johnny Wong
Cc: nut-upsuser@lists.alioth.debian.org
Subject: Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3


On Aug 18, 2015, at 9:07 PM, Johnny Wong  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 "hidden"  I would 
> have to install the unhide package then
> 

What I mean is that you can't have more than one usbhid-ups process talking to 
the same UPS at one time - regardless of whether they write a PID file. In the 
case of running with "-D", you would need to double-check for any in the 
background (and there was a PID file named usbhid-ups-upstl1300.pid). "ps 
auxww|grep [u]sbhid-ups" should show only one driver in either case.

Still looking into the altsetting issue. I would have to shuffle a few machines 
around to get a copy of 10.2 running on a box that isn't being actively used 
for anything else, but maybe there is something in their source control logs.

-- 
Charles Lepple
clepple@gmail





___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-18 Thread e430benz98
I see what you are saying. I did use usbhid-ups without the -D and once in a 
awhile it will say it found a previous driver running and it was going to kill 
it 

Here is something I have been doing... If I keep issueing the command to load 
the drivers eventually it will load it even after removing the 
usb_set_altinterface from ups.conf. 

It almost looks like the inferface is dropping on and off regardless 

If that makes sense its almost like someone is pulling out the USB wire and 
plugging in and out 

Sent from my LG G3.

-Original Message-
From: Charles Lepple 
To: Johnny Wong 
Cc: "nut-upsuser@lists.alioth.debian.org" 
Sent: Tue, 18 Aug 2015 6:37 PM
Subject: Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

On Aug 18, 2015, at 9:07 PM, Johnny Wong  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 "hidden"  I would 
> have to install the unhide package then
> 

What I mean is that you can't have more than one usbhid-ups process talking to 
the same UPS at one time - regardless of whether they write a PID file. In the 
case of running with "-D", you would need to double-check for any in the 
background (and there was a PID file named usbhid-ups-upstl1300.pid). "ps 
auxww|grep [u]sbhid-ups" should show only one driver in either case.

Still looking into the altsetting issue. I would have to shuffle a few machines 
around to get a copy of 10.2 running on a box that isn't being actively used 
for anything else, but maybe there is something in their source control logs.

-- 
Charles Lepple
clepple@gmail



___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-18 Thread Charles Lepple
On Aug 18, 2015, at 9:07 PM, Johnny Wong  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 "hidden"  I would 
> have to install the unhide package then
> 

What I mean is that you can't have more than one usbhid-ups process talking to 
the same UPS at one time - regardless of whether they write a PID file. In the 
case of running with "-D", you would need to double-check for any in the 
background (and there was a PID file named usbhid-ups-upstl1300.pid). "ps 
auxww|grep [u]sbhid-ups" should show only one driver in either case.

Still looking into the altsetting issue. I would have to shuffle a few machines 
around to get a copy of 10.2 running on a box that isn't being actively used 
for anything else, but maybe there is something in their source control logs.

-- 
Charles Lepple
clepple@gmail




___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser


Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-18 Thread Johnny Wong
> 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
/var/run/syslog.pid
/var/run/mountd.pid
/var/run/istgt.pid
/var/run/upslog.pid
/var/run/upsmon.pid
/var/run/powerd.pid
/var/run/samba4/nmbd.pid
/var/run/samba4/smbd.pid
/var/run/samba4/winbindd.pid
/var/run/sshd.pid
/var/run/cron.pid
/var/run/rsyncd.pid
/var/run/lighttpd.pid
/var/run/spindown.pid
/var/run/upsd.pid
/var/run/usbhid-ups-upstl1300.pid

Sent from Mail for Windows 10



From: Charles Lepple
Sent: Tuesday, August 18, 2015 4:35 PM
To: Johnny Wong
Cc: nut-upsuser@lists.alioth.debian.org
Subject: Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3


On Aug 18, 2015, at 3:28 PM, Johnny Wong  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 "-D" prevents that.

>  Any recommendation on how to keep the drivers from disconnecting using the 
> usb_set_altinterface?  (PS.  Is there a specific value to use?)

>From the earlier usbconfig output, I only see "bAlternateSetting = 0x". 
>Adding that option (as you did just now) defaults to a parameter of zero. I 
>will look into this.

FYI, some history is here: https://github.com/networkupstools/nut/issues/138

--
Charles Lepple
clepple@gmail







---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-18 Thread Charles Lepple
On Aug 18, 2015, at 3:28 PM, Johnny Wong  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 "-D" prevents that.

>  Any recommendation on how to keep the drivers from disconnecting using the 
> usb_set_altinterface?  (PS.  Is there a specific value to use?)

>From the earlier usbconfig output, I only see "bAlternateSetting = 0x". 
>Adding that option (as you did just now) defaults to a parameter of zero. I 
>will look into this.

FYI, some history is here: https://github.com/networkupstools/nut/issues/138

-- 
Charles Lepple
clepple@gmail




___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser


Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-18 Thread Johnny Wong
well, it is "CLOSER" to working with the usb_set_altinterface
Also the port=auto in ups.conf doesn't pick it up.  I have to set port = 
/dev/ugen0.5 then the driver will pick it up.
the upsd is able to start... BUT  the ups connects and disconnects on a regular 
basis of about 1min interval
Communications with UPS upstl1300@localhost established
Broadcast Message from root@datanas.adhome.local
    (no tty) at 10:33 PDT...
Communications with UPS upstl1300@localhost lost
Broadcast Message from root@datanas.adhome.local
    (no tty) at 10:34 PDT...Communications with UPS upstl1300@localhost 
established

  


 On Tuesday, August 18, 2015 10:16 AM, Johnny Wong  
wrote:
   

 >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)
  51.943124 - VendorID: 09ae
  51.943149 - ProductID: 3016
  51.943157 - Manufacturer: unknown
  51.943165 - Product: unknown
  51.943175 - Serial Number: unknown
  51.943183 - Bus: /dev/usb
  51.943191 Trying to match device
  51.943219 Device matches
  51.943232 nut_usb_set_altinterface: calling usb_set_altinterface(udev, 0)
  51.943258 nut_usb_set_altinterface: usb_set_altinterface() should not be 
necessary - please email the nut-upsdev list with information about your UPS.
  51.945383 Report[get]: (2 bytes) => 34 64
  51.945402 Path: UPS.PowerSummary.RemainingCapacity, Type: Feature, 
ReportID: 0x34, Offset: 0, Size: 8, Value: 100
  51.947738 Report[get]: (2 bytes) => 3a 0a
  51.947754 Path: UPS.PowerSummary.RemainingCapacityLimit, Type: Feature, 
ReportID: 0x3a, Offset: 0, Size: 8, Value: 10
  51.950194 Report[get]: (2 bytes) => 38 1e
  51.950208 Path: UPS.PowerSummary.WarningCapacityLimit, Type: Feature, 
ReportID: 0x38, Offset: 0, Size: 8, Value: 30
  51.952619 Report[get]: (3 bytes) => 35 c5 02
  51.952634 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, ReportID: 
0x35, Offset: 0, Size: 16, Value: 709
  51.954503 Report[get]: (3 bytes) => 04 18 00
  51.954518 Path: UPS.BatterySystem.Battery.ConfigVoltage, Type: Feature, 
ReportID: 0x04, Offset: 0, Size: 16, Value: 24
  51.956255 Report[get]: (3 bytes) => 20 14 01
  51.956271 Path: UPS.BatterySystem.Battery.Voltage, Type: Feature, 
ReportID: 0x20, Offset: 0, Size: 16, Value: 0.000276
  51.957311 Report[get]: (2 bytes) => 2a 07
  51.957325 Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, 
ReportID: 0x2a, Offset: 0, Size: 8, Value: 7
  51.966043 Report[get]: (3 bytes) => 61 ff ff
  51.966058 Path: UPS.OutletSystem.Outlet.DelayBeforeStartup, Type: 
Feature, ReportID: 0x61, Offset: 0, Size: 16, Value: 65535
  51.967812 Report[get]: (3 bytes) => 16 ff ff
  51.967827 Path: UPS.OutletSystem.Outlet.TLDelayBeforeStartup, Type: 
Feature, ReportID: 0x16, Offset: 0, Size: 16, Value: -60
  51.969498 Report[get]: (3 bytes) => 15 ff ff
  51.969512 Path: UPS.OutletSystem.Outlet.DelayBeforeShutdown, Type: 
Feature, ReportID: 0x15, Offset: 0, Size: 16, Value: 65535
  51.969529 Report[buf]: (3 bytes) => 61 ff ff
  51.969539 Path: UPS.OutletSystem.Outlet.DelayBeforeStartup, Type: 
Feature, ReportID: 0x61, Offset: 0, Size: 16, Value: 65535
  51.969576 Report[buf]: (3 bytes) => 15 ff ff
  51.969586 Path: UPS.OutletSystem.Outlet.DelayBeforeShutdown, Type: 
Feature, ReportID: 0x15, Offset: 0, Size: 16, Value: 65535
  51.971318 Report[get]: (3 bytes) => 17 ff ff
  51.971332 Path: UPS.OutletSystem.Outlet.DelayBeforeReboot, Type: Feature, 
ReportID: 0x17, Offset: 0, Size: 16, Value: 65535
  51.972869 Report[get]: (2 bytes) => 11 02
  51.972884 Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature, 
ReportID: 0x11, Offset: 0, Size: 8, Value: 2
  51.974255 Report[get]: (3 bytes) => 03 14 05
  51.974270 Path: UPS.Flow.ConfigApparentPower, Type: Feature, ReportID: 
0x03, Offset: 0, Size: 16, Value: 1300
  52.009206 Report[get]: (3 bytes) => 47 27 01
  52.009223 Path: UPS.PowerConverter.Output.ActivePower, Type: Feature, 
ReportID: 0x47, Offset: 0, Size: 16, Value: 295
  52.077118 libusb_get_report: Unknown error
  52.077136 Can't retrieve Report 1e: Input/output error
  52.077151 upsdrv_updateinfo...
  52.077158 Got to reconnect!
 


 On Tuesday, August 18, 2015 10:05 AM, Johnny Wong  
wrote:
   

 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:  at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) 
pwr=ON (100mA)  bL

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-18 Thread 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
battery.charge.low: 10
battery.charge.warning: 30
battery.runtime: 709
battery.type: PbAC
battery.voltage: 0.0
battery.voltage.nominal: 24.0
device.type: ups
driver.flag.usb_set_altinterface: enabled
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 15
driver.parameter.port: /dev/ugen0.5
driver.parameter.productid: 3016
driver.parameter.synchronous: no
driver.version: 2.7.3
driver.version.data: TrippLite HID 0.81
driver.version.internal: 0.39
input.frequency: 5990.0
input.transfer.high: 150.0
input.transfer.low: 92.0
input.voltage: 0.0
input.voltage.nominal: 120
output.current: 260.00
output.frequency: 5990.0
output.frequency.nominal: 60
output.voltage: 0.0
output.voltage.nominal: 120
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.load: 40
ups.power: 288.0
ups.power.nominal: 1300
ups.productid: 3016
ups.status: OL
ups.timer.reboot: 65535
ups.timer.shutdown: 65535
ups.timer.start: 65535
ups.vendorid: 09ae
ups.watchdog.status: 0
 


 On Tuesday, August 18, 2015 5:44 AM, Charles Lepple  
wrote:
   

 On Aug 17, 2015, at 11:56 AM, Johnny Wong  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 test with another UPS brand.

> 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.

True, most people won't need to know the ./configure parameters. It looks like 
you found the driver path and the UPS name, so we're set for now. However, if 
you run across that part of the source code, it might be useful for later in 
case we need to rebuild a driver.

> 
> /usr/local/libexec/nut/usbhid-ups -a upstl1300 -DDD
> Network UPS Tools - Generic HID driver 0.39 (2.7.3)
> USB communication driver 0.32
>    0.00    debug level is '3'
>    0.006296    upsdrv_initups...
[...]
>  0.013551    Checking device (09AE/3016) (/dev/usb//dev/ugen0.5)
>    0.278818    - VendorID: 09ae
>    0.278835    - ProductID: 3016
>    0.278843    - Manufacturer: unknown
>    0.278852    - Product: unknown
>    0.278859    - Serial Number: unknown
>    0.278867    - Bus: /dev/usb
>    0.278876    Trying to match device
>    0.278925    Device matches
>    0.278937    nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0)

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]").

>    0.306126    HID descriptor, method 1: (9 bytes) => 09 21 11 01 00 01 22 6e 
>03
>    0.306148    HID descriptor, method 2: (9 bytes) => 09 21 11 01 00 01 22 6e 
>03
>    0.306156    HID descriptor length 878
>    5.279939    Unable to get Report descriptor: Input/output error

My other concern is that FreeBSD might not allow the method that we use to 
retrieve the Report Descriptor.

What do the following commands return (need to run them as root)?

usbconfig -u 0 -a 5 dump_device_desc
usbconfig -u 0 -a 5 dump_curr_config_desc
usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100

(I'm guessing on "-u 0 -a 5" based on .../dev/ugen0.5 -- that might change if 
the UPS USB cable is unplugged and re-inserted.)

> cat /var/etc/ups.conf
> [upstl1300]
>        driver = usbhid-ups
>        port = auto
>        pollfreq = 30
>        productid = 3016
> 
> Let me know what other information is required, I'll try my best to obtain it.

Thanks for sending ups.conf. That's all I can think of for now.

-- 
Charles Lepple
clepple@gmail




  ___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-18 Thread Johnny Wong
>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)
  51.943124 - VendorID: 09ae
  51.943149 - ProductID: 3016
  51.943157 - Manufacturer: unknown
  51.943165 - Product: unknown
  51.943175 - Serial Number: unknown
  51.943183 - Bus: /dev/usb
  51.943191 Trying to match device
  51.943219 Device matches
  51.943232 nut_usb_set_altinterface: calling usb_set_altinterface(udev, 0)
  51.943258 nut_usb_set_altinterface: usb_set_altinterface() should not be 
necessary - please email the nut-upsdev list with information about your UPS.
  51.945383 Report[get]: (2 bytes) => 34 64
  51.945402 Path: UPS.PowerSummary.RemainingCapacity, Type: Feature, 
ReportID: 0x34, Offset: 0, Size: 8, Value: 100
  51.947738 Report[get]: (2 bytes) => 3a 0a
  51.947754 Path: UPS.PowerSummary.RemainingCapacityLimit, Type: Feature, 
ReportID: 0x3a, Offset: 0, Size: 8, Value: 10
  51.950194 Report[get]: (2 bytes) => 38 1e
  51.950208 Path: UPS.PowerSummary.WarningCapacityLimit, Type: Feature, 
ReportID: 0x38, Offset: 0, Size: 8, Value: 30
  51.952619 Report[get]: (3 bytes) => 35 c5 02
  51.952634 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, ReportID: 
0x35, Offset: 0, Size: 16, Value: 709
  51.954503 Report[get]: (3 bytes) => 04 18 00
  51.954518 Path: UPS.BatterySystem.Battery.ConfigVoltage, Type: Feature, 
ReportID: 0x04, Offset: 0, Size: 16, Value: 24
  51.956255 Report[get]: (3 bytes) => 20 14 01
  51.956271 Path: UPS.BatterySystem.Battery.Voltage, Type: Feature, 
ReportID: 0x20, Offset: 0, Size: 16, Value: 0.000276
  51.957311 Report[get]: (2 bytes) => 2a 07
  51.957325 Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, 
ReportID: 0x2a, Offset: 0, Size: 8, Value: 7
  51.966043 Report[get]: (3 bytes) => 61 ff ff
  51.966058 Path: UPS.OutletSystem.Outlet.DelayBeforeStartup, Type: 
Feature, ReportID: 0x61, Offset: 0, Size: 16, Value: 65535
  51.967812 Report[get]: (3 bytes) => 16 ff ff
  51.967827 Path: UPS.OutletSystem.Outlet.TLDelayBeforeStartup, Type: 
Feature, ReportID: 0x16, Offset: 0, Size: 16, Value: -60
  51.969498 Report[get]: (3 bytes) => 15 ff ff
  51.969512 Path: UPS.OutletSystem.Outlet.DelayBeforeShutdown, Type: 
Feature, ReportID: 0x15, Offset: 0, Size: 16, Value: 65535
  51.969529 Report[buf]: (3 bytes) => 61 ff ff
  51.969539 Path: UPS.OutletSystem.Outlet.DelayBeforeStartup, Type: 
Feature, ReportID: 0x61, Offset: 0, Size: 16, Value: 65535
  51.969576 Report[buf]: (3 bytes) => 15 ff ff
  51.969586 Path: UPS.OutletSystem.Outlet.DelayBeforeShutdown, Type: 
Feature, ReportID: 0x15, Offset: 0, Size: 16, Value: 65535
  51.971318 Report[get]: (3 bytes) => 17 ff ff
  51.971332 Path: UPS.OutletSystem.Outlet.DelayBeforeReboot, Type: Feature, 
ReportID: 0x17, Offset: 0, Size: 16, Value: 65535
  51.972869 Report[get]: (2 bytes) => 11 02
  51.972884 Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature, 
ReportID: 0x11, Offset: 0, Size: 8, Value: 2
  51.974255 Report[get]: (3 bytes) => 03 14 05
  51.974270 Path: UPS.Flow.ConfigApparentPower, Type: Feature, ReportID: 
0x03, Offset: 0, Size: 16, Value: 1300
  52.009206 Report[get]: (3 bytes) => 47 27 01
  52.009223 Path: UPS.PowerConverter.Output.ActivePower, Type: Feature, 
ReportID: 0x47, Offset: 0, Size: 16, Value: 295
  52.077118 libusb_get_report: Unknown error
  52.077136 Can't retrieve Report 1e: Input/output error
  52.077151 upsdrv_updateinfo...
  52.077158 Got to reconnect!
 


 On Tuesday, August 18, 2015 10:05 AM, Johnny Wong  
wrote:
   

 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:  at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) 
pwr=ON (100mA)  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0110
  bDeviceClass = 0x  
  bDeviceSubClass = 0x
  bDeviceProtocol = 0x
  bMaxPacketSize0 = 0x0008
  idVendor = 0x09ae
  idProduct = 0x3016
  bcdDevice = 0x0002
  iManufacturer = 0x0003  
  iProduct = 0x0001  
  iSerialNumber = 0x0005  
  bNumConfigurations = 0x0001

usbconfig -u 0 -a 5 dump_curr_config_desc
 datanas: ~# usbconfig -u 0 -a 5 dump_curr_config_desc
ugen0.5:  at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) 
pwr=ON (100mA)
 Configuration index 0    bLength = 0x0009
    bDescriptorType = 0x0002
    wTotalLength = 0x0022
    bNumInterfaces = 0x0001
    bConfigurationValue = 0x0001
    iConfiguration = 0x  
    

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-18 Thread Johnny Wong
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:  at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) 
pwr=ON (100mA)  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0110
  bDeviceClass = 0x  
  bDeviceSubClass = 0x
  bDeviceProtocol = 0x
  bMaxPacketSize0 = 0x0008
  idVendor = 0x09ae
  idProduct = 0x3016
  bcdDevice = 0x0002
  iManufacturer = 0x0003  
  iProduct = 0x0001  
  iSerialNumber = 0x0005  
  bNumConfigurations = 0x0001

usbconfig -u 0 -a 5 dump_curr_config_desc
 datanas: ~# usbconfig -u 0 -a 5 dump_curr_config_desc
ugen0.5:  at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) 
pwr=ON (100mA)
 Configuration index 0    bLength = 0x0009
    bDescriptorType = 0x0002
    wTotalLength = 0x0022
    bNumInterfaces = 0x0001
    bConfigurationValue = 0x0001
    iConfiguration = 0x  
    bmAttributes = 0x00a0
    bMaxPower = 0x0032    Interface 0
  bLength = 0x0009
  bDescriptorType = 0x0004
  bInterfaceNumber = 0x
  bAlternateSetting = 0x
  bNumEndpoints = 0x0001
  bInterfaceClass = 0x0003  
  bInterfaceSubClass = 0x
  bInterfaceProtocol = 0x
  iInterface = 0x    Additional Descriptor  bLength 
= 0x09
  bDescriptorType = 0x21
  bDescriptorSubType = 0x11
   RAW dump:
   0x00 | 0x09, 0x21, 0x11, 0x01, 0x00, 0x01, 0x22, 0x6e,
   0x08 | 0x03 Endpoint 0
    bLength = 0x0007
    bDescriptorType = 0x0005
    bEndpointAddress = 0x0081  
    bmAttributes = 0x0003  
    wMaxPacketSize = 0x0008
    bInterval = 0x000c
    bRefresh = 0x
    bSynchAddress = 0x

usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100


 datanas: ~# usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100
REQUEST = <0x05 0x84 0x09 0x04 0xa1 0x01 0x09 0x24 0xa1 0x00 0x85 0x28 0x09 
0xfe 0x79 0x01 0x75 0x08 0x95 0x01 0x15 0x00 0x26 0xff 0x00 0xb1 0x03 0x85 0x29 
0x09 0xff 0x79 0x05 0xb1 0x03 0x85 0x2b 0x09 0xfd 0x79 0x03 0xb1 0x03 0x09 0x1a 
0xa1 0x02 0x85 0x30 0x09 0x40 0x67 0x21 0xd1 0xf0 0x00 0x55 0x07 0xb1 0x83 0x85 
0x31 0x09 0x30 0x75 0x10 0x95 0x01 0x15 0x00 0x27 0xff 0xff 0x00 0x00 0x67 0x21 
0xd1 0xf0 0x00 0x55 0x01 0xb1 0x02 0xc0 0x85 0x11 0x09 0x5a 0x75 0x08 0x95 0x01 
0x15 0x01 0x25 0x03 0x65 0x00 0x55 0x00 0xb1 0x82 0x09 0x02 0xa1 0x02 0x85 0x32 
0x75 0x01 0x95 0x07 0x15 0x00 0x25 0x01 0x81 0x03 0xb1 0x03 0x09 0x62 0x95 0x01 
0xb1 0xa2 0x09 0x62 0x81 0xa2 0xb1 0x01 0x81 0x01 0x09 0x69 0xb1 0xa2 0x09 0x69 
0x81 0xa2 0x95 0x06 0xb1 0x01 0x81 0x01 0x05 0x85 0x09 0xd0 0x95 0x01 0x81 0xa2 
0x09 0xd0 0xb1 0xa2 0x81 0x01 0xb1 0x01 0x95 0x06 0x09 0x42 0x09 0x46 0x09 0x44 
0x09 0x45 0x09 0x47 0x09 0x4b 0x81 0xa2 0x09 0x42 0x09 0x46 0x09 0x44 0x09 0x45 
0x09 0x47 0x09 0x4b 0xb1 0xa2 0xc0 0x85 0x2a 0x09 0x89 0x79 0x07 0x75 0x08 0x95 
0x01 0x15 0x00 0x26 0xff 0x00 0xb1 0x03 0x85 0x62 0x09 0x8f 0x79 0x08 0xb1 0x03 
0x85 0x33 0x09 0x2c 0xb1 0x03 0x85 0x34 0x09 0x66 0x81 0xa2 0x09 0x66 0xb1 0xa2 
0x85 0x3a 0x09 0x29 0xb1 0xa2 0x85 0x37 0x09 0x67 0xb1 0x03 0x85 0x36 0x09 0x83 
0xb1 0x03 0x85><$(yu&)y+y0@g!U10u'g!UZu%eU2u%bbiiBFDEGKBFDEGK*yu&by3,4ff:)7g6>











 


 On Tuesday, August 18, 2015 5:44 AM, Charles Lepple  
wrote:
   

 On Aug 17, 2015, at 11:56 AM, Johnny Wong  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 test with another UPS brand.

> 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.

True, most people won't need to know the ./configure parameters. It looks like 
you found the driver path and the UPS name, so we're set for now. However, if 
you run across that part of the source code, it might be useful for later in 
case we need to rebuild a driver.

> 
> /usr/local/libexec/nut/usbhid-ups -a upstl1300 -DDD
> Network UPS Tools - Generic HID driver 0.39 (2.7.3)
> USB communication driver 0.32
>    0.00    debug level is '3'
>    0.006296    upsdrv_initups...
[...]
>  0.013551    Checking device (09AE/3016) (/dev/usb//dev/ugen0.5)
>    0.278818    - VendorID: 09ae
>    0.278835    - ProductID: 3016
>    0.278843    - Manufacturer: unknown
>    0.278852    - Product: unknown
>    0.278859    - Serial Number: unknown
>    0.278867    - Bus: /dev/usb
>    0.278876    Trying to match device
>    0.278925    Device matches
>    0.278937    nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0)

Just for grins, can you 

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-18 Thread Charles Lepple
On Aug 17, 2015, at 11:56 AM, Johnny Wong  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 test with another UPS brand.

> 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.

True, most people won't need to know the ./configure parameters. It looks like 
you found the driver path and the UPS name, so we're set for now. However, if 
you run across that part of the source code, it might be useful for later in 
case we need to rebuild a driver.

> 
> /usr/local/libexec/nut/usbhid-ups -a upstl1300 -DDD
> Network UPS Tools - Generic HID driver 0.39 (2.7.3)
> USB communication driver 0.32
>0.00 debug level is '3'
>0.006296 upsdrv_initups...
[...]
>   0.013551 Checking device (09AE/3016) (/dev/usb//dev/ugen0.5)
>0.278818 - VendorID: 09ae
>0.278835 - ProductID: 3016
>0.278843 - Manufacturer: unknown
>0.278852 - Product: unknown
>0.278859 - Serial Number: unknown
>0.278867 - Bus: /dev/usb
>0.278876 Trying to match device
>0.278925 Device matches
>0.278937 nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 
> 0)

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]").

>0.306126 HID descriptor, method 1: (9 bytes) => 09 21 11 01 00 01 22 
> 6e 03
>0.306148 HID descriptor, method 2: (9 bytes) => 09 21 11 01 00 01 22 
> 6e 03
>0.306156 HID descriptor length 878
>5.279939 Unable to get Report descriptor: Input/output error

My other concern is that FreeBSD might not allow the method that we use to 
retrieve the Report Descriptor.

What do the following commands return (need to run them as root)?

usbconfig -u 0 -a 5 dump_device_desc
usbconfig -u 0 -a 5 dump_curr_config_desc
usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100

(I'm guessing on "-u 0 -a 5" based on .../dev/ugen0.5 -- that might change if 
the UPS USB cable is unplugged and re-inserted.)

> cat /var/etc/ups.conf
> [upstl1300]
> driver = usbhid-ups
> port = auto
> pollfreq = 30
> productid = 3016
> 
> Let me know what other information is required, I'll try my best to obtain it.

Thanks for sending ups.conf. That's all I can think of for now.

-- 
Charles Lepple
clepple@gmail




___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser


Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-17 Thread Johnny Wong
> 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 upstl1300 -DDD
Network UPS Tools - Generic HID driver 0.39 (2.7.3)
USB communication driver 0.32
   0.00 debug level is '3'
   0.006296 upsdrv_initups...
   0.007180 Checking device (0781/5583) (/dev/usb//dev/ugen0.6)
   0.013441 - VendorID: 0781
   0.013456 - ProductID: 5583
   0.013464 - Manufacturer: SanDisk
   0.013472 - Product: Ultra Fit
   0.013480 - Serial Number: 4C530123150905117592
   0.013487 - Bus: /dev/usb
   0.013495 Trying to match device
   0.013518 Device does not match - skipping
   0.013551 Checking device (09AE/3016) (/dev/usb//dev/ugen0.5)
   0.278818 - VendorID: 09ae
   0.278835 - ProductID: 3016
   0.278843 - Manufacturer: unknown
   0.278852 - Product: unknown
   0.278859 - Serial Number: unknown
   0.278867 - Bus: /dev/usb
   0.278876 Trying to match device
   0.278925 Device matches
   0.278937 nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0)
   0.306126 HID descriptor, method 1: (9 bytes) => 09 21 11 01 00 01 22 6e 
03
   0.306148 HID descriptor, method 2: (9 bytes) => 09 21 11 01 00 01 22 6e 
03
   0.306156 HID descriptor length 878
   5.279939 Unable to get Report descriptor: Input/output error
   5.279997 Checking device (046D/C509) (/dev/usb//dev/ugen0.4)
   5.287000 - VendorID: 046d
   5.287013 - ProductID: c509
   5.287020 - Manufacturer: Logitech
   5.287026 - Product: USB Receiver
   5.287032 - Serial Number: unknown
   5.287038 - Bus: /dev/usb
   5.287047 Trying to match device
   5.287060 Device does not match - skipping
   5.287086 Checking device (0557/2419) (/dev/usb//dev/ugen0.3)
   5.287156 - VendorID: 0557
   5.287167 - ProductID: 2419
   5.287174 - Manufacturer: unknown
   5.287180 - Product: unknown
   5.287185 - Serial Number: unknown
   5.287191 - Bus: /dev/usb
   5.287197 Trying to match device
   5.287206 Device does not match - skipping
   5.287227 Checking device (/0001) (/dev/usb//dev/ugen0.2)
   5.287285 - VendorID: 
   5.287295 - ProductID: 0001
   5.287302 - Manufacturer: unknown
   5.287308 - Product: unknown
   5.287314 - Serial Number: unknown
   5.287320 - Bus: /dev/usb
   5.287326 Trying to match device
   5.287334 Device does not match - skipping
   5.287353 Checking device (/) (/dev/usb//dev/ugen0.1)
   5.287427 - VendorID: 
   5.287436 - ProductID: 
   5.287443 - Manufacturer: 0x8086
   5.287448 - Product: XHCI root HUB
   5.287454 - Serial Number: unknown
   5.287460 - Bus: /dev/usb
   5.287466 Trying to match device
   5.287474 Device does not match - skipping
   5.287508 No appropriate HID device found
   5.287519 No matching HID UPS found


Here is the ups.conf if needed
cat /var/etc/ups.conf
[upstl1300]
    driver = usbhid-ups
    port = auto
    pollfreq = 30
    productid = 3016

Let me know what other information is required, I'll try my best to obtain it.
Regards,
Johnny Wong




 On Monday, August 17, 2015 5:27 AM, Charles Lepple  
wrote:
   

 On Aug 17, 2015, at 1:00 AM, Johnny Wong  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 
> http://www.tripplite.com/line-interactive-ups-system-desktop-tower-1300va-120v-usb-port-lcd-screen~SMART1300LCDT/
>  
> PROBLEM:  NUT is ABLE to see the UPS BUT it is not getting the right(?) 
> descriptor?  I am using the usbhid-ups driver set.  I have tried others, 
> tripplite, tripplite_usb, and blazer_usb and none works.  This is the closest 
> I can see it being “working”
 
For that USB ID (09AE/3016), usbhid-ups is the correct driver.

> According to 
> http://www.networkupstools.org/ddl/Tripp_Lite/SMART1300LCDT.html.  It was 
> “verified” working with NUT version 2.6.4  

In a message on nut-upsdev, Marco Walther just cited this thread: 
http://thread.gmane.org/gmane.comp.monitoring.nut.devel/6482 which mentions 
that the UPS works on Debian Linux 7.1. Marco's patch is against NUT 2.7.3, and 
it just corrects some scaling of the variables, so it would have gotten well 
past the problem you mentioned. It sounds like this might be an issue with the 
FreeBSD USB stack.

I am not familiar with NAS4Free, but what do you get when you start the driver 
in deb

Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3

2015-08-17 Thread Charles Lepple
On Aug 17, 2015, at 1:00 AM, Johnny Wong  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 
> http://www.tripplite.com/line-interactive-ups-system-desktop-tower-1300va-120v-usb-port-lcd-screen~SMART1300LCDT/
>  
> PROBLEM:  NUT is ABLE to see the UPS BUT it is not getting the right(?) 
> descriptor?  I am using the usbhid-ups driver set.  I have tried others, 
> tripplite, tripplite_usb, and blazer_usb and none works.  This is the closest 
> I can see it being “working”
 
For that USB ID (09AE/3016), usbhid-ups is the correct driver.

> According to 
> http://www.networkupstools.org/ddl/Tripp_Lite/SMART1300LCDT.html.  It was 
> “verified” working with NUT version 2.6.4  

In a message on nut-upsdev, Marco Walther just cited this thread: 
http://thread.gmane.org/gmane.comp.monitoring.nut.devel/6482 which mentions 
that the UPS works on Debian Linux 7.1. Marco's patch is against NUT 2.7.3, and 
it just corrects some scaling of the variables, so it would have gotten well 
past the problem you mentioned. It sounds like this might be an issue with the 
FreeBSD USB stack.

I am not familiar with NAS4Free, but what do you get when you start the driver 
in debug mode? You will need to get to a root shell, then run something like 
"/usr/local/libexec/nut/usbhid-ups -a upsname -DDD" (replacing "upsname" with 
the name in ups.conf). Apologies in advance if you need to go hunting for the 
exact path of the driver or ups.conf: the last person to have an issue with 
NAS4Free did not get back to the NUT lists with the ./configure settings that 
NAS4Free uses to compile NUT.

[please use reply-all]

-- 
Charles Lepple
clepple@gmail




___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser