search for: ar01s03

Hi; I'm having some trouble to comunicate with my just bought (08/17/15) Ups. According to SOLIS(8): SUPPORTED HARDWARE This driver has been tested with : Solis 1000 VA Solis 1500 VA Solis 2000 VA Solis 3000 VA Back-UPS BZ1200-BR Back-UPS BZ2200BI-BR So solis is the one to go for. Here is my scenario: SW: nut-2.7.3 (compiled from ports) OS: FreeBSD

...gt; you installed via the ports tree (as opposed to binary packages), you >> should have most of the dependencies installed. You might also need >> libtool and autoconf, as mentioned in the second link below: >> >> http://www.networkupstools.org/docs/developer-guide.chunked/ar01s03.html#_source_code_management >> and >> http://www.networkupstools.org/docs/developer-guide.chunked/ar01s03.html#building >> > > Yes I did build it through ports. I try to build a debug version of it. Mario, I added a few debug statements throughout the solis driver: htt...

...UPS and the Raspberry Pi (or the NVR). Either the Raspberry Pi has to share the UPS status through something like upsd (or something similar, like apcupsd's NIS master mode), or the NVR has to send the shutdown signal to the Raspberry Pi. http://www.networkupstools.org/docs/user-manual.chunked/ar01s03.html#_advanced_configuration -- Charles Lepple clepple at gmail -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150121/fd4f65bb/attachment.html>

...f 10. You will also need to adjust the udev files manually to fix /dev/bus/usb permissions. > > If you do choose to build using the latest source code from Git, be aware that you will need more tools, as specified in the Developer Guide: http://networkupstools.org/docs/developer-guide.chunked/ar01s03.html#building > > It may be easier to use the 2.7.4 tarball, and add the patch which introduces Protocol 1330 support to the RPM spec file: https://github.com/networkupstools/nut/commit/4eff5b7068e9873ce11b5a296f403e8cdf0e3580 I've uploaded to http://wolfy.fedorapeople.org/nut a new set o...

(forwarding msg because of attachments too big) @Massimo: prefer to send references instead of actual documents, whenever you mail to the list. We have a 40Kb limit, to not overload our readers. Please also avoid Microsoft OpenXML (Ie, .xlsx, .docx, ...) and prefer PDF or anything else that is actually inter-operable . Thus I've converted the XLSX spreadsheet to PDF. To all: I've added

Hello I am trying to install the NUT on CentOS 6 (2.6.32-696.3.1.el6.x86_64). First I installed it using: yum install epel-release --enablerepo=extras yum install nut And when I run it by: sbin/upsdrvctl start (that's where it installed it using the package) I had the following message: "This TrippLite device (09ae:1330) is not (or perhaps not yet) supported by usbhid-ups. [...]"

libusb do you have installed >>> 1.2.6.0-2 ./configure --with-drivers=usbhid-ups Configuration summary: ====================== build serial drivers: yes build USB drivers: yes build SNMP drivers: no build neon based XML driver: yes enable Avahi support: no build Powerman PDU client driver: no build IPMI driver: no build Mac OS X meta-driver: no build i2c based drivers: no enable SSL

...u` on the files you modified against the > original ones: http://man7.org/linux/man-pages/man1/diff.1.html <http://man7.org/linux/man-pages/man1/diff.1.html> > > Also, we have some related chapters in our developer guide: > https://networkupstools.org/docs/developer-guide.chunked/ar01s03.html <https://networkupstools.org/docs/developer-guide.chunked/ar01s03.html> > > Ce message, ainsi que tous les fichiers joints à ce message, peuvent contenir des informations sensibles et/ ou confidentielles ne devant pas être divulguées. Si vous n'êtes pas le destinataire de ce m...

Setup that I was on mind is a little different, but I think your setup works well. In my setup the HUB is connected directly to the UPS, then the cables go to raspberry and device. In your setup the HUB is connected directly to the raspberry, then the cables go to UPS and Device. It?s Ok? In both configurations I need the same things: Male B->female A adaptor, HUB and 2 male A->

...ure script and the Makefile.am/.in files, might also be necessary for you to install automake, autoconf, and libtool to regenerate them. After installing, you can run "./autogen.sh" in the top level of the NUT directory. Details: http://www.networkupstools.org/docs/developer-guide.chunked/ar01s03.html#building -- Charles Lepple clepple at gmail

On 2016-01-28 8:18 AM, Charles Lepple wrote: > I definitely like your approach. Thanks for moving some of the "magic numbers" to named constants, as well. Thanks. Always nice to have real coders sanity check anything I've written with a "thumbs up" response. (I'm more a hardware guy) And sscanf was working like poo -- so I figured I'd parse it differently with

...factor of 10. You will also need to adjust the udev files manually to fix /dev/bus/usb permissions. If you do choose to build using the latest source code from Git, be aware that you will need more tools, as specified in the Developer Guide: http://networkupstools.org/docs/developer-guide.chunked/ar01s03.html#building It may be easier to use the 2.7.4 tarball, and add the patch which introduces Protocol 1330 support to the RPM spec file: https://github.com/networkupstools/nut/commit/4eff5b7068e9873ce11b5a296f403e8cdf0e3580

...c/xdg" in > + with Not_found -> Guestfs_config.sysconfdir // "xdg" in Hmm... the XDG basedir spec says [1]: "If $XDG_CONFIG_DIRS is either not set or empty, a value equal to /etc/xdg should be used." [1] https://specifications.freedesktop.org/basedir-spec/latest/ar01s03.html -- Pino Toscano

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, We would like to evaluate how ocfs2 will work with a debian distribution. Most of our systems people favor debian and so we are evaluating whether debian and ocfs2 work nicely + oracle 10gR2 rac. I know that debian is not supported by Oracle, but this is only for testing. Has anyone had experience with this? If so can you provide

...k my blog post in NUT documentation page. > http://blog.pointbre.com/2903/nutnetwork-ups-tool-korean-guidebook.html > > I hope my effort help NUT project. > could you please provide a unified diff against the latest trunk? Ie: http://new.networkupstools.org/docs/developer-guide.chunked/ar01s03.html#_submitting_patches check the paragraph 3.9 meanwhile, I've added your documentation to the new documentation section (commit r2823): http://new.networkupstools.org/documentation.html cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com Network UPS Tool...

...On Dec 19, 2012, at 9:00 AM, ajiskrishnan wrote: > Adding pace.c in /driver - pace.c has a few variable names that need to be discussed, and the descriptions are copy-and-pasted from one another. - Please note the indentation style: http://www.networkupstools.org/docs/developer-guide.chunked/ar01s03.html#_coding_style - printf() is not to be used for debugging messages - there are functions which take a log severity level. - It would be a good idea to log a message in upsdrv_shutdown() saying that shutdown is not supported. > Adding the modified /driver/Makefile.in and Makefile.am Are t...

...to adjust the > udev files manually to fix /dev/bus/usb permissions. > > > > If you do choose to build using the latest source code from Git, be > aware that you will need more tools, as specified in the Developer Guide: > http://networkupstools.org/docs/developer-guide.chunked/ar01s03.html#building > > > > It may be easier to use the 2.7.4 tarball, and add the patch which > introduces Protocol 1330 support to the RPM spec file: > https://github.com/networkupstools/nut/commit/4eff5b7068e9873ce11b5a296f403e8cdf0e3580 > I've uploaded to http://wolfy.fedorap...

Use ./configure --sysconfdir setting. --- builder/paths.ml | 2 +- mllib/guestfs_config.ml.in | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/builder/paths.ml b/builder/paths.ml index cbd9d4bd0..d7c4820bf 100644 --- a/builder/paths.ml +++ b/builder/paths.ml @@ -35,7 +35,7 @@ let xdg_config_home () = let xdg_config_dirs () = let dirs = try Sys.getenv

...and the Raspberry Pi (or the NVR). Either the Raspberry Pi has to share the UPS status through something like upsd (or something similar, like apcupsd's NIS master mode), or the NVR has to send the shutdown signal to the Raspberry Pi. http://www.networkupstools.org/docs/user-manual.chunked/ar01s03.html#_advanc ed_configuration -- Charles Lepple clepple at gmail -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150121/5f2a848c/attachment.html>

...ee (as opposed to binary > >> packages), you should have most of the dependencies installed. You > >> might also need libtool and autoconf, as mentioned in the second > >> link below: > >> > >> http://www.networkupstools.org/docs/developer-guide.chunked/ar01s03.html#_source_code_management > >> and > >> http://www.networkupstools.org/docs/developer-guide.chunked/ar01s03.html#building > >> > > > > Yes I did build it through ports. I try to build a debug version of > > it. > > Mario, > > I added a...