Re: [Nut-upsdev] UPS CYBERPOWER CP1300EPFCLCD MISSING FROMCOMPATIBILITY LIST

On Mar 10, 2018, at 4:57 PM, Ron J Taylor wrote: > > Hello Charles, > Nice to make your acquaintance. J > Thanks for your detailed reply. I appreciate it greatly. I want to learn. You're welcome! > > I have read and tried to get my head around the information you

Re: [Nut-upsdev] UPS CYBERPOWER CP1300EPFCLCD MISSING FROMCOMPATIBILITY LIST

On Mar 10, 2018, at 12:40 AM, Ron J Taylor wrote: > > Hi > I have just purchased a Cyberpower CP1300EPFCLCD UPS. > > It is not listed in your Compatibility List > http://networkupstools.org/stable-hcl.html Thanks, we'll add that to the list. We have a few updates queued up for when we cut

Re: [Nut-upsdev] [networkupstools/nut] Riello IDG400 wrong values & not powering off (#530)

On Feb 26, 2018, at 12:06 PM, Elio Parisi wrote: > - the second problem I think is related to the first because the > shutdown command that I sent to UPS by NUT monitor works without problems; Can you please weigh in on the discussion on GitHub?

Re: [Nut-upsdev] [PATCH 2/3] Add generic facility to override HID report descriptor in usbhid-ups

On Feb 3, 2018, at 7:19 PM, Russell King wrote: > > + addvar(VAR_VALUE, "hid_descriptor", "Replacement HID descriptor file"); Hi Russell, I was adding a quick note to the usbhid-ups man page about this parameter, and I had a few thoughts: * Maybe we should call it

Re: [Nut-upsdev] [networkupstools/nut] Riello IDG400 wrong values & not powering off (#530)

On Feb 26, 2018, at 4:58 AM, Elio Parisi wrote: > > Hi Charles, > this type of UPS doesn't support realtime autonomy calculation, instead a > fixed countdown must be used. > > How we can fix non supported values? If a value is not supported, the driver should not

[Nut-upsdev] Fwd: [networkupstools/nut] Riello IDG400 wrong values & not powering off (#530)

Elio or others at Riello, can you please check out the following issue on Github? https://github.com/networkupstools/nut/issues/530 Begin forwarded message: > > From: latimeria > Subject: [networkupstools/nut] Riello IDG400 wrong values & not powering off > (#530) > Date: February 25, 2018 at

Re: [Nut-upsdev] [PATCH 1/3] Skip non-feature HID reports

On Feb 16, 2018, at 6:55 AM, Russell King wrote: > > Hence, libusb_get_report() always requests the report ID as a feature > report, and never uses the report type that was stored. > My apologies. I saw the HIDData_t pointer (with its report type field) getting passed down to HIDGetItemData(),

Re: [Nut-upsdev] [PATCH 1/3] Skip non-feature HID reports

have both Input and Feature entries for the same Usage IDs). -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] No answer from upsrw command

.battery.start.quick, [NULL]) > > 2232.749549send: T > > 2233.136727read: > > 2233.136780instcmd: command [test.battery.start.quick] handled Not all UPSes support the standard commands, especially with a de facto standard like the Qx protocol. For testing

Re: [Nut-upsdev] [HCL] Riello IPG 600 supported by riello_usb / incorrect battery.charge and ups.temperature values

[when responding, please use Reply-All to include the list. Thanks!] On Nov 16, 2017, at 6:30 AM, Andrés Valdaliso wrote: > > Hello everyone, > > I recently bought a Riello IPG 600 UPS > (http://www.riello-ups.com/products/1-ups/39-iplug) to prevent hardware > damage to

Re: [Nut-upsdev] Tripplite Smart Int 1000 - wrong numbers

On Oct 10, 2017, at 11:50 AM, Thomas Charron wrote: > > I do have some of the more modern protocol documentation for Tripplite from > the tripplite engineers, if someone is working on updating the Tripplite > drivers. Is this something we can publish on the protocol

Re: [Nut-upsdev] Tripplite Smart Int 1000 - wrong numbers

On Oct 10, 2017, at 1:37 AM, tuhar...@misbb.sk wrote: > > Charles, maybe we are getting closer :-) >> The tripplite_serial_protocol branch has some debug statements that will >> show up if you run "sudo drivers/tripplite -D -a name-of-ups" from the nut >> directory. > Network UPS Tools -

Re: [Nut-upsdev] Tripplite Smart Int 1000 - wrong numbers

My apologies, I forgot a step. See below. > On Oct 9, 2017, at 1:59 PM, tuhar...@misbb.sk wrote: > > Hi, Charles > > I'm trying compilation but there is no configure command in the cloned git > directory of nut. > > > Dňa 08.10.2017 o 23:47 Charles Lepple napísal(

Re: [Nut-upsdev] Tripplite Smart Int 1000 - wrong numbers

On Oct 8, 2017, at 4:34 PM, tuhar...@misbb.sk wrote: > > Thank You for You reply, Charles > > > Dňa 07.10.2017 o 14:30 Charles Lepple napísal(a): >> Is the "lan4.1" cable different from this one? >> http://networkupstools.org/cables.html#_tripp_lite &

Re: [Nut-upsdev] Tripplite Smart Int 1000 - wrong numbers

On Oct 7, 2017, at 8:30 AM, Charles Lepple <clep...@gmail.com> wrote: > >> I also miss values such as output.voltage, battery.runtime etc, but maybe >> this model simply dosen't have the numbers reported. > > We have to calculate an estimate of battery.runtime in tri

Re: [Nut-upsdev] Tripplite Smart Int 1000 - wrong numbers

[please use reply-all to keep the list CC'd, thanks!] On Oct 6, 2017, at 1:29 PM, tuhar...@misbb.sk wrote: > > Hello, > > I've got Tripplite Smart Int 1000 UPS with lan4.1 serial interface. Quite > sympathetic UPS, I must say from first glance. I have made a proper serial > cable (btw i hate

Re: [Nut-upsdev] [HCL] CyberPower EC350G supported by usbhid-ups

On Sep 28, 2017, at 7:23 PM, Matt Beisser wrote: > > [shutdown sequence] > I have tested and verified the shutdown sequence works. > > [manufacturor] > https://www.cyberpowersystems.com/product/ups/ec350g/ > Thanks.

Re: [Nut-upsdev] Patch for phoenixcontact modbus driver

On Sep 19, 2017, at 3:21 AM, Spiros Ioannou wrote: > > I attach a patch for phoenixcontact_modbus.c > > This patch does the following: > > * Marks driver as DRV_BETA > * Fixes stale data detection when cable is disconnected > > I can open a pull request if needed. Looks

Re: [Nut-upsdev] CyberPower UPS Omission

On Sep 11, 2017, at 10:09 PM, Jason Berg wrote: > I am happy to provide you the output of "upsc" but I do not know what that > is. "Does it mean UPS console"? Basically - "UPS client" was the original author's intent, I think.

Re: [Nut-upsdev] CyberPower UPS Omission

On Sep 11, 2017, at 5:40 PM, Jason Berg wrote: > > The Hardware Compatibility List page on our website said to report any > omissions in the list to this address. I bought a CyberPower UPS Model > LX1500GU. It looks similar to the CP1500AVRLCD. My intention is to configure

Re: [Nut-upsdev] Openups patch proposal

On Jul 22, 2017, at 9:13 AM, Alphonse wrote: > > Note that there is still a 'libusb_get_string: Invalid argument' message into > the log, but only when starting or resuming the system. I should mention that this is now in the master branch as commit e6d77c87d0b0 I added

Re: [Nut-upsdev] Openups patch proposal (KDE, etc.)

On Jul 23, 2017, at 4:50 AM, Alphonse wrote: > > Another point is bugging me: the ups is not repported as a battery in kde nor > in the output of 'solid-hardware list'. > Do you have an idea for this problem? > Thanks! > To be honest, most of the NUT development effort

Re: [Nut-upsdev] Openups patch proposal

On Jul 22, 2017, at 9:40 AM, Alphonse wrote: > > This is weird (for me): I have added the 'explore' option into the ups > configuration, and restarted the driver, but now it tells that the device is > offline! It is back to normal without this option. > I have attached

Re: [Nut-upsdev] Openups patch proposal

On Jul 21, 2017, at 3:21 PM, Alphonse wrote: > > Hello, > I have an openups2 ups. It works very well with nut, except two things: > 1) It keeps sending a 'libusb_get_string: invalid argument' message to the > log; > 2) It does not report any command. > > Following >

Re: [Nut-upsdev] Proposed new documentation "Configuration Examples"

On Jun 9, 2017, at 10:16 AM, Roger Price wrote: > > Most of the questions asked in the nut-user mailing list seem to me to be > either erudite technical discussion of new and exotic UPS units, or n00b > questions of the style "I have this old UPS so I installed NUT but it didn't > work". > >

[Nut-upsdev] new driver- or vendor-specific variable prefix?

Not to pick on anyone in particular, but for the sake of organization, I think we might need to address the need for variables beyond the standard ones defined here: http://networkupstools.org/docs/developer-guide.chunked/apas01.html From

Re: [Nut-upsdev] NUT namespace: RFC for new variable addition

On May 24, 2017, at 7:56 AM, Jim Klimov <jimkli...@cos.ru> wrote: > > On May 24, 2017 1:08:09 PM GMT+02:00, Charles Lepple <clep...@gmail.com> > wrote: >> I don't think "dephasing" is common usage, but "phase shift" should >> suffice

Re: [Nut-upsdev] NUT namespace: RFC for new variable addition

On May 24, 2017, at 5:11 AM, Arnaud Quette wrote: > > Hi all, > > here is another one, related to ATS (automatic transfer switch) this time. > > in order to track "dephasing" between input sources (1 and 2), I'd like to > add a new variable: "input.phase.shift" > >

Re: [Nut-upsdev] Many open green PRs in NUT, wanna merge?

uration/compilation side that seems to be the result of rushing to add features initially. I suspect that there will be a few issues that crop up during packaging, and given the time it takes to rebuild and check .debs for the PPA on other branches, this is not something I look forward to doing in my

Re: [Nut-upsdev] [nut-upsuser] Copeland Engineering Dockmaster

On Mar 19, 2017, at 6:49 PM, Charles Lepple wrote: > > I started modifying one of the drivers to do the reads, but it may not be of > much use until we understand what needs to be written, as you mentioned here: > >> but commenting-out the writing portion makes the data c

Re: [Nut-upsdev] New UPS information - Liebert GXT4 via US

On Apr 17, 2017, at 5:54 AM, Christo Simeonoff wrote: > > Hi UPS List members, > > I have purchased a number of Emerson Power / Liebert GXT4 UPS units. > I have these working correctly under nut, but limited detsils are being > reported. What is reported (upsc

Re: [Nut-upsdev] [nut-upsuser] Copeland Engineering Dockmaster

Drew, Another thing to consider is the NUT driver documentation. This is the template, but since it originally predated the USB drivers, feel free to draw on the other man pages for inspiration: https://github.com/networkupstools/nut/blob/master/docs/man/skel.txt - Charles

Re: [Nut-upsdev] [nut-upsuser] Copeland Engineering Dockmaster

On Mar 19, 2017, at 10:56 AM, Drew from Zhrodague wrote: > > [] I've spoken with one of the developers, and he's offered to share > some technical documentation with me. I'll report here with whatever I can. > He's on vacation in China. Hopefully this

Re: [Nut-upsdev] modbus driver for phoenix contact industrial UPS

On Mar 14, 2017, at 5:28 AM, Spiros Ioannou wrote: > > Is there any indication on the usual time it takes for a driver to be > checked/included on the master? > (We are planning on setting up hundreds of those UPS boxes and it would be > great to have an estimate) > As an

Re: [Nut-upsdev] [nut-upsuser] Copeland Engineering Dockmaster

[moved to nut-upsdev while we figure out the protocol] > On Mar 9, 2017, at 11:22 AM, Drew from Zhrodague > wrote: > > I'm able to cat /dev/usb/hiddev0 and /dev/hidraw0 - I pipe this through > hexdump and I get different types of data from each: > > > hiddev: >

Re: [Nut-upsdev] 2.7.4 make install fails: libnutclient.so.0.0.0 missing

On Dec 10, 2016, at 3:42 PM, Roger Price wrote: > > I upgraded an operating system to openSUSE 42.2, kernel 4.4 and recompiled > nut 2.7.4. ./configure, make clean and make went well, but make install > failed. Make reports > > Making install in clients > make[1]: Entering directory

Re: [Nut-upsdev] nut-git reporting 24 Volts with CP1350PFCLCD -- is that correct?

On Dec 7, 2016, at 1:35 PM, David C. Rankin wrote: > I just built and installed network-ups-tools-git-v2.7.4.r161.g7bf209a on > Archlinux for a CyberPower CP1350PFCLCD ups. After hitting the FAQ 29. "My USB > UPS is supported but doesn’t work!" udev issue because

Re: [Nut-upsdev] [HCL] CyberPower Cyber Power Systems CP685AVR supported by usbhid-ups

[please use Reply-All - this list does not modify the reply-to header] > On Nov 23, 2016, at 10:30 AM, Craig STCR wrote: > > It looks like the CyberPower Cyber Power Systems CP685AVR supported by > usbhid-ups has a favorable device dump linked to the Devices Dumps >

Re: [Nut-upsdev] [HCL] supported by

[please use Reply-All - this list does not modify the reply-to header] > On Oct 29, 2016, at 2:37 PM, Francois Cukier wrote: > > root@Monitor:/etc/nut# upsc ups1 > Init SSL without certificate database > battery.runtime: 133200.00 This runtime seems high. The driver

Re: [Nut-upsdev] CyberPower SX650G no driver.

On Oct 18, 2016, at 9:35 AM, Raymond Day wrote: > > How do I run the git one? I guess it's up to date. Don't, for now. There have been a few posts on the mailing list explaining what to pass to ./configure (or ./autogen.sh, which calls configure) to get the Git version

Re: [Nut-upsdev] CyberPower SX650G no driver.

(please use Reply-All to keep the list CC'd, thanks) > On Oct 18, 2016, at 8:53 AM, Raymond Day wrote: > > Wow that was fast thank you Charles. > > Put "upsc" in the /etc/nut/ups.conf and then went to start it with > "upsdrvctl start" but I get this then: No, sorry, I

Re: [Nut-upsdev] CyberPower SX650G no driver.

On Oct 18, 2016, at 8:21 AM, Raymond Day wrote: > > > # To find out if your driver supports any extra settings, start it with > # the -h option and/or read the driver's documentation. > [serverups] ^ this is the name of the UPS that you should pass to "upsc"

Re: [Nut-upsdev] nutdrv-qx powercool 1500VA USB UPS

> On Oct 10, 2016, at 4:29 PM, Matthew Wire wrote: > > Here is the complete log for two minutes from startup. thank you compressed to fit on the mailing list. > > On 9 October 2016 at 23:41, hyo...@gmail.com wrote: > > 12.243069 send: Q1 > >

Re: [Nut-upsdev] driver for Victron Multiplus RS485

[please use Reply-All - this list does not modify the reply-to header] > On Oct 3, 2016, at 4:15 PM, Jon 'Boli' Copeland wrote: > > Hi All, > > I'd like to modify an existing driver to support my Victron Multiplus > inverter/charger. This device is not supported by the victron driver. > > I do

[Nut-upsdev] reassessing the HCL ratings scale

topic of the HCL, I also think it might be handy to list some of the more common vendors at the top of the "Manufacturer" filter dropdown. Suggestions for criteria would be appreciated. -- Charles Lepple clepple@gmail ___ Nut-upsdev ma

Re: [Nut-upsdev] ./configure excludes USB drivers and documentation

. libusb-1.0 switched from usb.h to libusb.h, and the internal libusb.h inside NUT is different (but does not seem to interfere with the public header). -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian

Re: [Nut-upsdev] updating the NUT website

t seems to be the > real match for 'bestpower-mib.c' (see how '.1.3.6.1.4.1.2947.1.1.8.0' > is mapped to 'manufacturing date', while > http://powerquality.eaton.com/Support/Software-Drivers/Downloads/connectivity-firmware/bestpwr2.mib > -which appears to be a newer revision of that

Re: [Nut-upsdev] updating the NUT website

ckage branch. I don't think I have enough experience with submodules to say what I would prefer, so I'll leave that up to you. Let me know if you'd like help with anything else. -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] updating the NUT website

Makefile:796: *** target pattern contains no '%'. Stop. Any ideas? Also, what do I do afterwards to push to GitHub? -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/

[Nut-upsdev] updating the NUT website

to the NEWS file in the NUT repository, then that pulls in any other changes from that branch. Does it make sense to create a NUT branch based off of the 2.7.4 release, and put all of the NEWS/download updates there? We can then merge that back into master as needed. -- - Charles Lepple https://ghz.cc

Re: [Nut-upsdev] Lyonn ULT-2000 MKR supported by

http://networkupstools.org/docs/man/snmp-ups.html -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] A lot of EAGAIN (Resource temporarily unavailable) using nutdrv_qx

libusb-1.0 in the roadmap? So far, there have not been any good arguments for libusb-1.0 that would offset the amount of testing needed. Feel free to experiment, though. For timing purposes, it should be sufficient to write a small loop that sends the command for your UPS, and reads the res

Re: [Nut-upsdev] Tripp-Lite SMART1500LCDT

orkupstools/nut/pull/122 I don't have a lot of experience with that branch, but it sounds promising. (I would prefer to identify the underlying problem rather than work around it by closing and reopening the USB device more frequently, though, especially given the testing needed for other UPSes.)

[Nut-upsdev] Countdown to 2.7.4

for closed issues as well), that would be helpful. -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] Patching CyberPower UPS drivers

chunked/ar01s03.html#_source_code_management http://buildbot.networkupstools.org/snapshots (note that "2.7.3.1" is not a real version number, it's just something greater than 2.7.3 - the links include the full Git revision, and only the first 5-8 characters are needed from that) -- Cha

Re: [Nut-upsdev] Patching CyberPower UPS drivers

better than comment characters (which don't nest), and removing it completely is even better (fewer false positives when searching). If nothing else, it's in version control. Diff attached. Thanks, -- Charles Lepple clepple@gmail powerp-txt.c.diff Description: Binary data ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] UPS Trust OXXTRON 1300VA not working

ide much information - it is similar to genericups (OL/OB/LB). -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] UPS Trust OXXTRON 1300VA not working

ls.org/docs/man/richcomm_usb.html If the richcomm_usb driver does not show proper status changes, then the UPS is different than the previous model with the same name, and the real protocol is not known. -- Charles Lepple clepple@gmail ___ Nut-upsd

Re: [Nut-upsdev] [HCL] NHS Laser Senoidal 5000VA supported by gamatronic

the elapsed time as battery.runtime.elapsed. I have created a Github issue to clarify the documentation, and another to patch the driver to be consistent with the other NUT drivers: https://github.com/networkupstools/nut/issues/257 -- Charles Lepple c

[Nut-upsdev] Request for OpenSSL assistance (blocking I/O on Solaris)

of the client-side SSL I/O calls with while() loops. Any suggestions? -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] [HCL] NHS Laser Senoidal 5000VA supported by gamatronic

Since this might be hard to work around with the current driver, we can put a note in the DDL, but at this point I don't know what the note should say. -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] [HCL] NHS Laser Senoidal 5000VA supported by gamatronic

al: 120 > output.current: 0.0 > output.frequency: 60.0 > output.voltage: 119.7 > ups.alarm: Input Bad > ups.firmware: LSPWM(15).55 > ups.id: ny7bd8723tbecabc > ups.load: 000 > ups.mfr: NHS Sistemas de Energia > ups.model: Laser Senoidal 5000VA > ups.power.nominal: 05

Re: [Nut-upsdev] Some thoughts on loss of communication

cation failure, and most of the drivers already have timeouts built in. As a backup, the distribution startup/shutdown scripts should probably have timeouts as well - this used to be implemented as a delay between sending SIGTERM and SIGKILL. -- Charles Lepple clepple@gmail ___

Re: [Nut-upsdev] lost communication with UPS

to upsd, or the driver loses the connection to the UPS, upsmon should not shut down unless the last status message received was "OB". > As I said, thanks to all the help I received from Charles Lepple, I was able > to get this UPS working, and it has worked fine for many m

Re: [Nut-upsdev] UPS serial protocol

itoring features and test commands. If your customers' desired feature list matches that, you should be all set. -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] problem with compiling on Cygwin64

build the USB drivers. Which version of libusb do you have installed? -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] problem with compiling on Cygwin64

th-drivers=dummy-ups,usbhid-ups -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] NOTIFYCMD shell script problem driving me NUTS

expand the NUT documentation on this topic. -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] [HCL] Micropower LCD 1000 supported by blazer_usb

On Sep 21, 2015, at 7:38 AM, Charles Lepple <clep...@gmail.com> wrote: > > (please keep the list CC'd) > >> On Sep 21, 2015, at 5:09 AM, Uroš Gaber <uros.ga...@gmail.com >> <mailto:uros.ga...@gmail.com>> wrote: >> >> Hi. >> No for me nut

Re: [Nut-upsdev] problem with NOTIFYCMD

o run as root, I would recommend adjusting your firewall accordingly. -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] Regarding the Asium P700

w.networkupstools.org/docs/man/blazer_usb.html> -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] [HCL] Micropower LCD 1000 supported by blazer_usb

ny regressions? -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] [HCL] Asium P700

-spam measures result in mass unsubscription of non-Yahoo email users of these lists. Please consider submitting future information from a non-Yahoo email address, or create an issue on the NUT Github project: https://github.com/networkupstools/nut/issues -- Charles Lepple clepple@gmail ___

Re: [Nut-upsdev] blazer_usb Shutdown

to pick on Fideltronik, but they were the first entry I found.) -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] USB HID Spec help (passing strings)

ly using "lsusb -v -d VID:" on your device (might need to be run as root, depending on permissions). Next to the iSerialNumber value, it will try to fetch the corresponding string descriptor and print it. -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] USB HID Spec help (passing strings)

(Harvard architecture chips like PICs make this harder, but there is a C __attribute__ or something that you should be able to use). Otherwise, does your USB framework allow callbacks for arbitrary requests? -- Charles Lepple clepple@gmail ___ Nut

[Nut-upsdev] [meta] Yahoo, Gmail and DMARC

: although not yet affected, I included nut-upsdev@ since the problem could also manifest itself there.] -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman

Re: [Nut-upsdev] Small patch to scale the values for TRIPP-LITE SMART*LCDT's (please test)

leave, the better we can identify any patterns. If there is firmware version information in the USB descriptors, we might want to limit the scaling to certain versions. Thanks, -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut

Re: [Nut-upsdev] Ovislink

On Jul 16, 2015, at 5:09 AM, p...@paulcarmichael.org wrote: On 10/07/15 04:26, Charles Lepple wrote: On Jul 9, 2015, at 9:43 AM, p...@paulcarmichael.org wrote: Is there currently a way of implementing NUT with an Ovislink Chrome 1500 UPS? Not sure. There was a thread in February talking

Re: [Nut-upsdev] Good news

echo hi | wall, does it broadcast a message? If not, I'd say that's a bug in wall, but you could configure upsmon to run a different program to send a message. -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev

Re: [Nut-upsdev] no /etc/default/nut

=yes However, there is no '/etc/default/nut' . Do I need to create it ? No, /etc/default/nut is an old name - prior to systemd, NUT on Debian consulted /etc/nut/nut.conf to determine which daemons to start. I assume that systemd is backwards-compatible. -- Charles Lepple clepple@gmail

Re: [Nut-upsdev] No messages

. -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] New questions

On Jul 14, 2015, at 12:50 PM, john hart jsa...@yahoo.com wrote: Here is the previous email that I sent directly to Charles Lepple. I am now sending to the correct email with cc to Charles. I am looking at, and trying to understand the rest of the conf files

Re: [Nut-upsdev] Strange

/syslog. -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] Totally beyond me

Science is organized common sense. Philosophy is organized piffle -attributed to Bertrand Russel From: Charles Lepple clep...@gmail.com To: john hart jsa...@yahoo.com Cc: nut-upsdev@lists.alioth.debian.org nut-upsdev@lists.alioth.debian.org Sent: Monday, July 13, 2015 7:24 PM Subject

Re: [Nut-upsdev] Totally beyond me

extra pointers to the documentation that we have. -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] Ovislink

On Jul 10, 2015, at 9:02 AM, p...@paulcarmichael.org wrote: On 10/07/15 14:30, p...@paulcarmichael.org wrote: On 10/07/15 04:26, Charles Lepple wrote: On Jul 9, 2015, at 9:43 AM, p...@paulcarmichael.org wrote: Is there currently a way of implementing NUT with an Ovislink Chrome 1500 UPS

Re: [Nut-upsdev] [HCL] Fideltronik INIGO Viper 1200 supported by nutdrv_qx

://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/ddl/Fideltronik_INIGO/Viper_1200.html -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut

Re: [Nut-upsdev] Ovislink

: http://lists.alioth.debian.org/pipermail/nut-upsuser/2015-February/009527.html What does 'lsusb' list about this UPS? Is this even the right place to ask such a question? Sure, either the nut-upsdev or nut-upsuser lists will reach the developers. -- Charles Lepple clepple@gmail

Re: [Nut-upsdev] UPS integration into NUT

: http://www.usb.org/developers/hidpage/pdcv10.pdf -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] New snmp-ups subdriver for Huawei

] http://www.networkupstools.org/ups-protocols.html Stuart, if we add the copy of the MIB to that protocols page, do you have a source link? Thanks, -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http

Re: [Nut-upsdev] [Nut-upsuser] Nut-2.7.3 gcc-3.3.6

:15: map: No such file or directory nutclient.h:29:15: set: No such file or directory nutclient.h:30:21: exception: No such file or directory This is going to be slightly harder to auto-detect. You have g++, but apparently it cannot find STL. -- Charles Lepple clepple@gmail

Re: [Nut-upsdev] [Nut-upsuser] Nut-2.7.3 gcc-3.3.6

-upsuser later. -- Charles Lepple clepple@gmail ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Re: [Nut-upsdev] neon (was libusb_get_string: invalid argument (other usbhid-ups users, please test))

, and by the corresponding nut-scanner module. I'm not familiar with archlinux or AUR, but if you still have the logs, we can certainly take a look. It might be that NUT is looking for an older version of libneon, or that there is another dependency that is needed at build time. -- Charles Lepple

Re: [Nut-upsdev] libusb_get_string: invalid argument (other usbhid-ups users, please test)

it. I tried my MGE UPS on a Linux box as well, and it does not get interrupt events there, either. - Charles Lepple On Jun 11, 2015, at 9:13 AM, Charles Lepple clep...@gmail.com wrote: Greg, I'm still not 100% on what is going on, but after comparing the call stack with a debug session here

Re: [Nut-upsdev] libusb_get_string: invalid argument

sure i am working with the updated version. On Tue, 9 Jun 2015, Charles Lepple wrote: On Jun 9, 2015, at 4:55 PM, Greg Hersch wrote: (gdb) bt #0 libusb_get_string (udev=0x43110, StringIdx=0, buf=0x40204 buf , buflen=20) at libusb.c:496 #1 0x00015330 in HIDGetIndexString (udev

Re: [Nut-upsdev] libusb_get_string: invalid argument

to the ./configure line should do it. Arnaud, am I missing something obvious here? After making device.part HU_STATIC, there shouldn't be any other string descriptors retrieved in drivers/tripplite-hid.c. -- Charles Lepple clepple@gmail ___ Nut-upsdev

Re: [Nut-upsdev] Nut and liebert ups

://www.networkupstools.org/support.html (under Request help) Best regards Jean-marie ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev -- Charles Lepple clepple@gmail

Re: [Nut-upsdev] libusb_get_string: invalid argument

libusb_get_string: Invalid argument I think this is from trying to retrieve the value corresponding to device.part - which should also only be attempted once at startup. Try the attached patch? Also, I would be interested in the output of lsusb -vvv -d 09ae: for your UPS. -- Charles Lepple

Re: [Nut-upsdev] upsmon and Chloride UPS

. It uses these protocols : RCCMD ( that is more interesting ) and MopUps ( their Own protocol ). Roger That seems consistent with the brochure Ted found. Those protocols don't sound familiar, though. 2015-05-29 4:06 GMT+02:00 Charles Lepple clep...@gmail.com: On Thu, May 28

  1   2   3   4   5   6   7   >