similar to: Error "usbhid-ups[42466]: libusb_get_report: Unknown Error"

I'm using Nas4Free, and I'm getting the following message all the time in the Daemon log: usbhid-ups[42466]: libusb_get_report: Unknown Error I'm running Nas4Free 9.2.0.1 Shigawire Driver usbhid-ups Nut Version is 2.7.1 Internal verion 0.38 UPS Info from Nas4Free Manufacturer:CP1500PFCLCD Model:CRCA102*AF1 The model UPS I'm running is a Cyber Power CP1500PFCLCD, other

DDDDD output attached. On 04/12/12 19:53, Arnaud Quette wrote: > > > 2012/4/11 Robert Ayrapetyan <robert.ayrapetyan at gmail.com > <mailto:robert.ayrapetyan at gmail.com>> > > Seems I've missed confirmation mail somewhere, now registered. > > > > have you patched your 2.6.1 or used trunk + the patch? > I've used trunk + the patch.

OS = NAS4Free (FreeBSD Revision: 199506) 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

I'm trying to use a Nas4Free storage system. This same hardware worked fine on Freenas 0.7.2. O/S: Nas4Free 9.0.0.1.148 which comes with nut 2.6.4. UPS is an APC Back UPS RS 800. USB interface. Driver : usbhid-ups Port: auto my NAS is communicating with the UPS, but in testing power failures, I'm not getting the shutdown to be handled properly. When I pull the AC plug on the UPS,

On Oct 9, 2015, at 8:19 AM, Louis G. <louis at frentzgzesh.info> wrote: > > Charles, > > That was the PR1500LCDRT2U on the FreeBSD. I have not tried the CP900VR on the FreeBSD box yet. I can tell you that the CP900VR does work as expected on the Nas4Free one though. I am thinking it is the way the driver parses the USB hex identifier. There might be a filter that is not

I've setup nas4free (latest version 11.0.0.4, which has NUT 2.7.4) in a VM and configured it via webinterface to my APC UPS and set "shutdown mode" to "UPS goes on battery" with a timer of 30s. Then I started runtime calibration on the UPS and after 30s nas4free has shut down! I think this is not the correct behavior, since the status was "OB CAL". The system

On Aug 21, 2013, at 10:41 AM, Incze Andras wrote: > Having the next problem, manually adding via WinSCP in the upsd.users file the user for remote monitoring, saving the file, WinNUT client connects after "upsd -c reload" in NAS4Free console, but if I restart the NAS4Free system, the slave user disappears from upsd.users and remains only the master user. > NAS4Free is version

Thanks, the strange is that I could set in this way the master user. At NAS4Free forum cannot get help, I presented the problem there too, but no real help. On Thu, Aug 22, 2013 at 2:19 AM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 21, 2013, at 10:41 AM, Incze Andras wrote: > > > Having the next problem, manually adding via WinSCP in the upsd.users > file the

Hello Having the next problem, manually adding via WinSCP in the upsd.users file the user for remote monitoring, saving the file, WinNUT client connects after "upsd -c reload" in NAS4Free console, but if I restart the NAS4Free system, the slave user disappears from upsd.users and remains only the master user. NAS4Free is version 9.1.0.1 rev 724 and NUT is the version what is included.

Hello, I'm trying to integrate HAST to NAS4Free (FreeBSD 9.1-RC3). Now I have created version 9.1.0.1.531. http://sourceforge.net/projects/nas4free/files/NAS4Free-9.1.0.1/9.1.0.1.531/ Basic CARP + HAST + iSCSI target setup can be done, but very frequently I get hastctl hang when called: /sbin/hastctl status /sbin/hastctl dump Is it better for this method not to call from a script? or

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

Thank You very much !!! Now I see how was entered the master password in the file : "-v "concat(' password = ',//system/password)" -n \" I will test the proposed solution. Two questions - Do I need separate users for each WinNUT client or they can use the same user for monitoring&shutdown client machines ? - This is maybe a newbie question,

On Aug 22, 2013, at 5:15 AM, Incze Andras wrote: > Thanks, the strange is that I could set in this way the master user. That is odd. The development version of NAS4Free seems to be regenerating the entire upsd.users file: http://sourceforge.net/p/nas4free/code/848/tree/trunk/build/ports/nut/files/nut.sh.in To address your original concern (adding remote users for monitoring), I would

On Aug 23, 2013, at 12:49 PM, Incze Andras wrote: > There is some problem with formatting :( > > If I paste how was written, the structure is wrong formatted, is putted somewhere right after the end of 1st part with master in the generated file. Can you be more specific? You can attach text files if needed. > On Thu, Aug 22, 2013 at 3:32 PM, Charles Lepple <clepple at

There is some problem with formatting :( If I paste how was written, the structure is wrong formatted, is putted somewhere right after the end of 1st part with master in the generated file. On Thu, Aug 22, 2013 at 3:32 PM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 22, 2013, at 5:15 AM, Incze Andras wrote: > > > Thanks, the strange is that I could set in this way

>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) ?

>> >> I need some help here with getting this thing running. Every time I enable NUT on the server, I get a "on battery" status when I know that it is running on house power. This only occurs when I am monitoring it with FreeBSD(NAS4Free) > >Which version of FreeBSD is this based on? I also included the Motherboard and processor so if there is anything those

> 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

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 =