similar to: Cleaned up belkinunv diff

Description: Fix warning: variable set but not used [-Wunused-but-set-variable]. bugs.debian.org/633756. Related drivers were not tested. Last-Update: Sat, 13 Aug 2011 14:04:48 +0300 Index: b/drivers/belkinunv.c =================================================================== --- a/drivers/belkinunv.c 2011-05-31 13:36:49.000000000 +0300 +++ b/drivers/belkinunv.c

Description: Replace many usleep and some sleep calls with nanosleep. usleep is stated in its manual page as removed by POSIX. Contrary to its predecessors, nanosleep semantics is well defined. The replacement, which is mostly in drivers, is untested. Supplements http://bugs.debian.org/633791. Last-Update: Sat, 13 Aug 2011 14:04:48 +0300 Index:

Hi I'm sending this to you as it appears that you are the person who looks after and/or supervises the code for NUT's Belkin drivers. I'm using the address you use for the Nut-upsdev mailing list ( selinger at mathstat.dal.ca ). Anyway... I have a Belkin Universal UPS and, having just upgraded my Fedora Core system from 4 to 5 and had to go back through the system RC files

Is anyone besides me using gcc 4.*.*? I noticed that NUT generates an enormous amount of warning noise with that compiler, mostly due to implicit casts between signed/unsigned pointer types. Any volunteers to de-noise the code a bit? The easy way is to insert typecasts; the better way is to actually take care about signedness. -- Peter gcc -I../include -O -Wall -Wsign-compare -c -o everups.o

This is the patch to include SVN revision level in version number displays. There should be two enclosures; the patch itself and a new source file. common/upsversion.c. upversion.c defines a single function. upsversion(), that returns a version string for display. Some Makefile trickery ensures that this file will be recompiled whenever the project's SVN revision level has changed since it

I recently installed NUT 2.2.1 and set it up with a Belkin F6C100-UNV. I can monitor it via serial (belkinunv) or USB (usbhid-ups) cable, and both do seem to work fine, but I would prefer USB to avoid having to add a PCI serial card to the machine. I had to unplug something else to try it with a serial cable. Using 'belkinunv', there's a "-x wait" option: [ from

Hi, I was trying to hack the /etc/rc.d/init.d/halt script under RH 9.0 in a way to achieve a clean shutdown: - commanding the RAID arrays to readonly mode - turning off my hardware watchdog, ... etc. See details below. At the end of all this preparation, and very close to the last lines of the halt script, I would then issue: 1. /usr/bin/belkinunv -x wait /dev/ttyS0 2. (OR, with a smart ups:

All, I just bought a Belkin F6C1100-UNV and am trying to get it to work with NUT. I have tried many drivers ( "belkin", "belkinunv", "genericups upstype=4", and "genericups upstype=7", "bestups", "fentonups"). None of them seem to work. Does anyone have any experience with this device? If there is some utility that you all use to

I'm trying to set up a belkin f6c1100-unv UPS to work with nuts. From reading the mailing list, it sounds like the belkinunv serial driver should work and that the USB driver is potentially troublesome. Is this a correct impression? Also I may have missed this but if I do go with the serial (or USB port) is there any simple command line method for verifying basic connectivity? The

Zaid, I have a Belkin F6C800-UNV which has both a serial and USB connector. The serial connection is already working with the Belkinunv driver. I will connect via the USB and then compare both sets of variables. This should allow me to correlate and shed some light on the meaning of many of Belkin's non-standard "Usage" descriptors. With this information, it should be very easy

For the record, I was able to get the following working: Device: Belkin F6C1500-TW-RK Driver: belkin I tried the "belkinunv", which I use for my F6C1100-UNV, but it didn't work. At least there was a driver that worked! :-) Feel free to add it to the list of "tested" configs. Thanks, Dave ---------------------------------------------------------- Are Your Friends

I upgraded from V2.2 to V2.4. I use the "upslog" command to log the values of my belkin ups (belkinunv via serial port). It would occasionally start to record garbage, but it would always go back to normal in V2.2 if I restarted. In V2.4 it would not record the values, and the process would fail after the next interval had passed. I had set if for 300 seconds. I walked through the

I looked through the faq, but couldn't find an answer to this. I'm trying to configure nut-2.0.4-26 on SuSE linux 10.2. In ups.conf, I have [myups] driver = belkinunv port = /dev/undefined desc = "Local UPS" I'm trying to find out what the port should be set to. lsusb shows: Bus 001 Device 005: ID 050d:0980 Belkin Components Device Descriptor: bLength

Dear fellow NUT developers, after almost exactly two years as a NUT developer, I have concluded that this would be a good time to retire from active development. The project is in good shape, and the driver I was most involved with (usbhid-ups) is in better condition than ever, due to the excellent recent work of Arjen de Korte. Having already scaled back my activity for the last 6 months, I

While working on the mge-hid subdriver, I wanted to add the 'beeper.mute' command. Unfortunately, the description I intended to use was used already by the 'beeper.off' instcmd: CMDDESC beeper.off "Temporarily mute the UPS beeper" Now of course we could add another instcmd 'beeper.reallyoff', but instead I would prefer to bite the buller and do the following:

Hi Arjen My apologies fro drifting off topic in the other mailing list...:-) On the bottom of the Belkin UPS unit - is the model number: F6C120auUNV The "au" is for Australia I think. "man belkinunv" states that F6C120-UNV is supported - and I assumed that the "au" would not prevent this. I plugged in the USB to gather the information you requested. My intention

Hi all! The following files emits warnings when compiled with gcc 4.0: al175.c bcmxcp_ser.c belkinunv.c cyberpower.c everups.c powercom.c solis.c All warnings seem to be of this variety: everups.c:38: warning: pointer targets in passing argument 2 of 'ser_get_char' differ in signedness I suggest that those who fiddles with those drivers fixes the warnings and verifies that it works

On Sunday 08 December 2019 21:48:03 Charles Lepple wrote: > On Dec 7, 2019, at 7:01 PM, Gene Heskett <gheskett at shentel.net> wrote: > > What driver do I now put in /etc/nut/ups.conf? hid-generic doesn't > > seem to want to talk to it, and the original name _(usbhid-ups) > > doesn't work from new mobo. Oh wait, I can't spell. But that didn't > >

This will sound a bit odd. I have a current server running with a UPS. I'm in the process of replacing that server with another and obviously want Nut to monitor the new server. The new/old servers are in different locations, so I don't have access to the UPS while configuring the replacement server. I think I have the config ok, but what errors would you expect to see? Typically I'm

Hi Is there any way to have a newhidups subdriver register that is can handle settings from ups.conf, as per a "normal" nut driver? In, for example, belkinunv.c, there are various addvar() calls in the upsdrv_makevartable() function, but I can't work out where addvar() calls should be put in an HID subdriver. Thanks Jo Turner -)O(-