Re: [Nut-upsuser] Unable to find driver for a supported device

2016-10-12 Thread Charles Lepple
On Oct 12, 2016, at 3:28 PM, Nick Teague wrote: > > Alright. Sorry to bother you guys. Apparently after I rebooted the box, it > started working now on the tripplite-usb driver. One correct also. I didn't > have it installed from ports but from binary pkg. (pkg install nut) No worries - th

Re: [Nut-upsuser] Data Stale at random intervals

2016-10-12 Thread Charles Lepple
On Oct 12, 2016, at 8:13 PM, Daniel Shields wrote: > > Wow. Okay, well I let the debug run all day. Nothing in the logs even with > debug cranked to level 5. Attached are the last 1000 lines before it quit. > I'm really stumped now. gzipped and resent for the rest of the list. Can you ela

Re: [Nut-upsuser] trouble building nut for HID-USB

2016-10-12 Thread Charles Lepple
> On Oct 12, 2016, at 2:00 PM, Dorsey, Scott B. (LARC-D316)[LITES II] > wrote: > > It does in fact show exactly what you describe. Udev is working properly > with the device file being assigned to group > dialout, which the nut user is in. You were correct about my having had to > install

Re: [Nut-upsuser] Unable to find driver for a supported device

2016-10-12 Thread Nick Teague
Alright. Sorry to bother you guys. Apparently after I rebooted the box, it started working now on the tripplite-usb driver. One correct also. I didn't have it installed from ports but from binary pkg. (pkg install nut) I doubt this did anything but I did create nut.conf because it wasn't th

Re: [Nut-upsuser] trouble building nut for HID-USB

2016-10-12 Thread Dorsey, Scott B. (LARC-D316)[LITES II]
It does in fact show exactly what you describe. Udev is working properly with the device file being assigned to group dialout, which the nut user is in. You were correct about my having had to install the libusb-devel kit to make 2.7.4 build, but it does build properly and everything seems to

Re: [Nut-upsuser] Unable to find driver for a supported device

2016-10-12 Thread Nick Teague
# usbconfig -d ugen0.2 dump_device_desc ugen0.2: at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (60mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0008 idVendor = 0x09ae

Re: [Nut-upsuser] CP1500AVRLCD NOCOMM

2016-10-12 Thread Charles Lepple
On Oct 12, 2016, at 9:07 AM, Lane Russell wrote: > > Apologies, I did mean upsmon.conf. ups.conf "pollinterval" is not called out, > so I assume it's using the default of 2s. "pollfreq" and "pollfreqalert" are > both set to 10s in upsmon.conf at the moment. "deadtime" is set to 30s. No problem,