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

On Oct 28, 2016, at 8:43 AM, Dorsey, Scott B. (LARC-D316)[LITES II] wrote: > > So, no suggestions for diagnosing intermittent driver loading issues? > >> You might also benefit from adjusting these variables: >> http://lists.alioth.debian.org/pipermail/nut-upsuser/2016-October/010352.html > >

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

So, no suggestions for diagnosing intermittent driver loading issues? > You might also benefit from adjusting these variables: > http://lists.alioth.debian.org/pipermail/nut-upsuser/2016-October/010352.html I tried changing the polling interval, it doesn't seem to make any difference. Either

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

"lsusb" always shows the UPS. It's always there with an ls -al. I can start the thing, and it doesn't load wait a minute and try again and it doesn't load wait another minute and it loads then try to restart a minute later and it doesn't load. > You might also benefit from

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

> 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

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

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] trouble building nut for HID-USB

[please use Reply-All - this list does not modify the reply-to header.] > On Oct 10, 2016, at 8:53 AM, scott.b.dor...@nasa.gov wrote: > > I have a user running centos 6.8 with a brand new Tripplite HID (protocol > 4016) > UPS. So I installed nut 6.5 from EPEL and it sometimes worked, and it >

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

I have a user running centos 6.8 with a brand new Tripplite HID (protocol 4016) UPS. So I installed nut 6.5 from EPEL and it sometimes worked, and it sometimes didn't, and it seemed to be very inconsistent about loading the device driver. So, looking around and after spending some time

Re: [Nut-upsuser] Trouble with NUT?

V-S -Original Message- From: Charles Lepple [mailto:[EMAIL PROTECTED] Sent: Saturday, October 27, 2007 19:59 To: Drew Vonada-Smith Cc: Nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] Trouble with NUT? On 10/27/07, Drew Vonada-Smith [EMAIL PROTECTED] wrote: OS

Re: [Nut-upsuser] Trouble with NUT?

On 10/27/07, Drew Vonada-Smith [EMAIL PROTECTED] wrote: OS is ClarkConnect 4.2, which is based on CentOS4/RHEL 4. Which version of the kernel? Do you know if anything like SELinux or grsecurity are enabled? upsdrvctl -u root start upsserver all looks OK on results: Network UPS Tools -

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

Thanks for the advise. I may dig into this at a not to distant date. Right now, I'm waiting for some more info from some other people. There maybe some very good news regarding this ups in the not to distant future. Stay tuned. Eli Quoting Arnaud Quette [EMAIL PROTECTED]: gamatronic

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

Arnaud Quette wrote: gamatronic units are also supported by the gamatronic driver (much derived from the old sec driver). You should give it a try. About the newhidups issue, the given path might refer to some SEC protocol. But that needs some decoding (ie get the data for each path,

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

Hi Peter First let me say that I have appreciated you're help up to now and was quite amazed at how quickly (real time) we were able to get nut to detect the ups. I understand that the rest of this is a different kettle of fish altogether, so I do understand you're reluctance to dig into

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

Peter I think thats that. Just connected the UPS via serial cable and it seems to be working. So, I think I will revert to the stable version supplied by FC extras. I will keep the work that we've done together for a little while in case you decide to conitnue to work with me to get this to

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

Oops, that's what I get for being a newbie with nut. I didn't realize that LB stands for low battery and OB on battery, when the brand new ups is fully charged and plugged into the wall. After unplugging the ups from the wall, almost immediately a shutdown is triggered. So, obviously something

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

Yeah... I've been doing that I'll try going down the list again, but the best that I'm getting upsc is ups.status: LB OL After unplugging the ups from the wall, and waiting more than 5 seconds, which is the polling frequency in my upsmon.conf the status doesn't change. Eli On Monday, 19

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

Eli Wapniarski wrote: upsdrvctl -D -u root start produces Network UPS Tools - UPS driver controller 2.1.0 Starting UPS: Gamatronic_D-Compact exec: /usr/bin/ -a Gamatronic_D-Compact execv: Permission denied Driver failed to start (exit status=1) I think I understand the problem

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

Firstly forget about my link comment. I misread something. I get the same results if I ups.conf contains [Gamatronic_D-Compact] driver= newhidups port = auto desc = Gamatronic D-Compact running newhidups -DD -u root -x vendorid=0925 -a Gamatronic_D-Compact produces Network UPS

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

Thanks Peter If this is a duplicate please forgive me. I need to make a correct a couple of typos on point 2) below. If you're willing to get this done, so am I. I bought three of them 2 are connected to Linux boxes so I am very interested in getting nut to work. Anyhoot, I made the

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

Dear Eli, you need one more modification: in drivers/newhidups.c, line 37, add your subdriver to the list: static subdriver_t *subdriver_list[] = { generic_subdriver, mge_subdriver, apc_subdriver, belkin_subdriver, tripplite_subdriver, NULL }; Note that it is probably called

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

OK Peter The modification that you mentioned was indeed included in the discussion and was made accordingly. Instead of using kebo I used richcomm because the info that I've been getting seems to indicate that the interface was manufactured by Richcomm not kebo or gamatronic for that matter. I

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

Eli, you should be doing the next step. Run the driver and upsd (not upsmon), and see what output you can get from upsc. -- Peter Eli Wapniarski wrote: OK... Waiting for whats next Eli On Friday, 16 =D7=91June 2006 18:02, Peter Selinger wrote: Yup, that's fine. It doesn't matter at

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

You can try starting the driver with upsdrvctl, instead of calling the (newhidups) driver directly. It might make a difference. -- Peter Eli Wapniarski wrote: K.. upsd -u root produces=20 Network UPS Tools upsd 2.1.0 Can't connect to UPS [Gamatronic_D-Compact] (Gamatronic_D-Compact): No

[Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

Hi I am running FC5 with nut coming from the fc5 extras repositories. I am trying to configure a Gamatronic D-Compact ups. The cable that came with the ups has a serial connector on one end and a usb on the other. cat /proc/bus/usb/devices produces T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

Eli, Gamatronic is not currently supported by the newhidups driver. You have two options: (1) look at the file data/driver.list or http://www.networkupstools.org/compat/ to find a serial driver that matches your device, and/or (2) post the output of newhidups -DD -u root -x

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

Hi Peter Thanks for responding. Running newhidups -DD -u root -x generic -x vendorid=0925 auto produces Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.3) Fatal error: 'generic' is not a valid flag for this driver. However, newhidups -DD -u root -x vendorid=0925 auto Network UPS Tools:

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

Hi Eli, sorry, I forgot to say: you should first get and compile the newest development tree of NUT from the SVN repository. The -x generic flag will not work with 2.0.3. See http://www.networkupstools.org/source.html -- Peter Eli Wapniarski wrote: Hi Peter Thanks for responding.

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

OK Peter Here goes. I uninstalled the 2.03 and then compiled and installed using the following ./configure --prefix=/usr --with-user=nut make make usb make install make install-usb One funny thing to note. when I run the command newhidups, without specifying the location /usr/bin, for some