similar to: A new inutility for NUT

That's it. A Gnome Shell extension that uses upsc/upscmd to monitor devices and invoke instant commands. /dan walNUT.tar.gz (~3m) - https://docs.google.com/file/d/0BxWv_9cok7BKNXpyMFgya3dHZkE/edit?usp=sharing -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20130608/92d749b4/attachment.html>

Dear Daniele, I have some news regarding the Driver: I applied the patch you sent me (https://github.com/zykh/nut/tree/issue-441) and it works correctly (obviously in Level 5 of Debug I see "missing CR...etc.."). As for now there are 2 modification I'd like to suggest you: - For Online Type UPSs the Megatec protocol describes that the battery voltage is provided in the form of V

[forwarded without attachments, for real this time] > Begin forwarded message: > > From: Gabriele TAORMINA <gabriele.taormina at legrand.com <mailto:gabriele.taormina at legrand.com>> > Subject: Re: [Nut-upsdev] Adding drivers to NUT? > Date: August 27, 2018 at 6:03:55 AM EDT > To: Daniele Pezzini <hyouko at gmail.com <mailto:hyouko at gmail.com>> >

[please keep the discussion on the nut-upsdev list. thanks!] On Jan 30, 2014, at 10:20 AM, Jos? Sosa wrote: > Dear Mr. Lepple > > I am Leonardo Sosa and I am watching this issue with Rodolfo and Ronaldo. (in copy) > > See below our answers of your questions. > > What should I do now in order to include our code sgs_command in your code blazer_usb.c? As I mentioned to

2014-01-31 hyouko at gmail.com <hyouko at gmail.com>: > I changed a couple of things: > - https://github.com/zykh/nut/commit/ebae0e0e499e7983b4f26562451255a39abb023b#diff-38221201bf335e4da4e2dc77d5c6b3c2R478 > - https://github.com/zykh/nut/commit/ebae0e0e499e7983b4f26562451255a39abb023b#diff-38221201bf335e4da4e2dc77d5c6b3c2R482 Better links:

Dear Developer and Tester, I love NUT, because of the great interoperability. So I have the choice and freedom on the operating system or the device. Many thanks on all developers and the manufacturer, they support with informations, material, wages and so on. Dear Hyouko, I am interested in to know, why every manufacturer use their own protocol. The USB Power Device protocol is already 20

Hi folks, Dan is right, and this approach is the best for us to minimize the overhead. There may however be some points of improvement to give the right visibility to users, and avoid the confusion of "things being visible on the website though not yet published as a release". not much details from my side on this for now, though... cheers, Arno 2016-06-07 0:50 GMT+02:00 hyouko at

I added the sgs subdriver to nutdrv_qx: https://github.com/zykh/nut/tree/ts-shara (I assumed Rodolfo - surname? - is the author of the code, do you want me to change it?) I changed a couple of things: - https://github.com/zykh/nut/commit/ebae0e0e499e7983b4f26562451255a39abb023b#diff-38221201bf335e4da4e2dc77d5c6b3c2R478 -

hello, below the result of ./configure + full make output (do you need more?) I've installed python modules, but it didn't help Configuration summary: ====================== build serial drivers: yes build USB drivers: yes build SNMP drivers: yes build neon based XML driver: yes enable Avahi support: no build Powerman PDU client driver: no build IPMI driver: no build Mac OS X

On Dec 7, 2013, at 5:43 AM, Denis Yantarev wrote: > Ippon Back Power Pro responses are always padded to 64 bytes beyond \r payload terminator. When checking that command was successful (i.e. not echoed back) code relies on the response length reported by blazer_command which will always be 64. To fix this ippon_command should return actual payload length. This change also affects

Dear Sir , Can anyone tell me how to upload new ups driver to NUT website ? Best regards, Bluefish [cid:image001.jpg at 01D07C3E.C4ADB780] ?? ?? ?? ?????? ?????(??)???? ??????????107?????467?(?????) ??????5?1?A?2?4? 1-4F, Building 5, YuSheng lndustrial Park, No.467, Section Xixiang, National Highway 107, Xixiang, Bao An District, Shenzhen, China Tel: + 86-755-8601-6601 Ext. 8598 Fax:

Hi guys, Regarding building NUT on mac os x (yosemite), I tried Charles tweaks (ASCIIDOC_VERBOSE=-v + I?ve tried without internet connection) without success. Quick explanation for Charles regarding NUT WEBSITE: I would like to build it on my Mac because I?m experiencing some memory/performance issues with my VMs due to my quite old computer. bye, jean > Le 1 d?c. 2014 ? 20:54, Arnaud Quette

Sorry for the delay. >> make > Making all in protocols > make[1]: Nothing to be done for `all'. > make[1]: Nothing to be done for `all-am'. > cd nut/docs; /Applications/Xcode.app/Contents/Developer/usr/bin/make > html-chunked pdf > make[1]: Nothing to be done for `html-chunked'. > make[1]: Nothing to be done for `pdf'. > cd nut/docs/man;

Dear Daniele, thanks a lot for your support, i have some things that are not so clear for me: - I can send you the whole sources for our UPSs, do you need only Headers and C files or also other files (i suppose Driver list)? - Seen that we had some problems with the Blazer driver (the battery voltage calculation were not correct for our UPSs) we copied it and modified a bit while changing the

Roger, My clients are not comfortable with using the terminal commands to check the UPS status. They are converts from Windows and have little or no exposure to entering commands into a command line interface. The output in the GUI is what they have come to expect from software and they can launch via a click on an icon on the launcher as opposed to remembering a command. 73 & Cheers, Ken

Carsten, This is a common issue in technology when you have complex products that the majority of consumers of those products do not understand how they operate. If most UPS customers understood the importance of standardization they would have refused to purchase non-standard UPSes and all UPSes would have long ago standardized on a single management protocol. The normal thing is that product

Hi Rodolfo, [please reply to <nut-upsdev at lists.alioth.debian.org>, not nut-upsdev-owner, and if you have large attachments, upload them to a web server and post the URL. Thanks!] On Jan 29, 2014, at 7:59 AM, rodolfo at tsshara.com.br wrote: > <blazer_usb.c.txt> > Sorry, we forgot to send another file. We developed this code (blazer_usb.c.txt) so that your software is able

Dear Hyouko, Thank you very much ! Best regards, Bluefish -----????----- ???: hyouko at gmail.com [mailto:hyouko at gmail.com] ????: 2015?4?23? 7:25 ???: ??(bluefish_wei) ??: nut-upsdev at lists.alioth.debian.org ??: Re: [Nut-upsdev] How to upload new ups driver to NUT 2015-04-21 8:23 GMT+02:00 ??(bluefish_wei) <bluefish_wei at voltronicpower.com.cn>: > Can anyone tell me how to

Hi all, we should have been found the problem. Attach the patch inclusive of this problem and the previous (Riello IDG400 wrong values & not powering off). Best regards, -----Messaggio originale----- Da: Nut-upsdev [mailto:nut-upsdev-bounces+e.parisi=riello-ups.com at lists.alioth.debian.org] Per conto di nut-upsdev-request at lists.alioth.debian.org Inviato: mercoled? 7 marzo 2018 13:03 A:

Hello Dan, thanks for your input, I?ve tried to remove ?V' from sort -f -k 4.1,4.5rV -k 5n -t @ - command line => No more ?stray character? ! But I?m still stuck after with the : make: *** No rule to make target `-eindex.html', needed by `ups-html.txt'. Stop. Any idea here? > Le 3 d?c. 2014 ? 01:22, hyouko at gmail.com a ?crit : > > Sorry for the unresponsiveness. >