search for: upsdevic

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:

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

Hi Arnaud, attached there are a new patch (fixed ups.upspower.nominal in GPSER protocol and device.mfr) and three devdumps. Let me know if this time all is correct, Elio Parisi. Elio Parisi Centro Ricerche RPS SpA Viale Europa, 7 37045 Legnago VR Tel. +39 0442 635811 Fax. +39 0442 635934 Skype Id: - Voip: E-mail: E.Parisi at riello-ups.com Web: www.riello-ups.com

please tell me how i can use the hyperterminal to calibiration of my ups sua 1000VA. nut-upsdev-request@lists.alioth.debian.org wrote: Send Nut-upsdev mailing list submissions to nut-upsdev@lists.alioth.debian.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev or, via email, send a message with subject or body

1 - its on load blinking battery LEDs and not giving proper back up time . APC sua1000i nut-upsdev-request@lists.alioth.debian.org wrote: Send Nut-upsdev mailing list submissions to nut-upsdev@lists.alioth.debian.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev or, via email, send a message with subject or body

Hi, What driver should i use with APC BK-300C ? Michale Plourde Digicom Technologies

My personal experience with a number of UPSes that are monitored via USB cable is that communications errors such as the ones referenced in the issue you linked to below are a result of USB hardware incompatibilities between the USB chipset and the USB port on the motherboard.*? This is NOT specific to the NUT project as it affects both apcupsd and in fact, has been reported as an issue with

I'm still working on the interface to the UPS we're selling. USB works great with NUT in Linux, and natively through Windows battery support. Now I'm looking over the serial protocol. I can essentially make it anything I want, and it's VERY tempting to make my own protocol that is intuitive and simple, but I have a feeling every UPS maker does that. So, before I do that...is

>I'm afraid I am just the messenger - @bigon (Laurent Bigonville, on GitHub) is a Debian maintainer of NUT, and he was pointing out the >bug report filed with Debian: >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738122 >With other drivers, we sometimes see the "did not claim interface 0 before use" error if a driver gets out of sync with its PID file, >and

Hello, thank you for the idea. I'm already behind the permission problem, which originally apeared, but I did overcome it by rules settings. this is the result for 'ls -l /dev/bus/usb/004/007': ---- crw-rw-rw- 1 root nut 189, 390 pro 23 13:23 /dev/bus/usb/004/007 ---- Os is Debian 6.0.5 Squeeze Regards Dee Dne 22.12.2014 v 13:01 nut-upsdev-request at lists.alioth.debian.org

Also, which version of NUT is involved? There were recently PRs (merged to master-branch, eventually will be in 2.8.1) about more SNMP-UPS support including APCs e.g. 1674, 1679, 1113 (should be in 2.8.0)... Many distros still ship 2.7.4... Jim On Tue, Feb 28, 2023, 00:57 Greg Troxel <gdt at lexort.com> wrote: > mateuszx via Nut-upsdev <nut-upsdev at alioth-lists.debian.net>

Time, not sure who owner is, but I've tried as both admin and myself, to no avail. ?However, I told you that mesg is y, buti tried to send a mesg using ?' write ' ?and it says I have messages disabled. ????? ? I did that by opening two?terminals, on I logged in as ' su ', and sent the message from there. ?Is that peculiar? Might account for why I am notgetting anything from

Tim, Thanks for the feedback. ?I am the only user (standalone system), but I checked 'mesg' and made sure it was set?to 'mesg y' . ? And the execute permissions for wall are ? rwxr-sr-x ?and the filename is has a ?kind of orange highlightedbackground. Don't know what that means. John?"Science is organized common sense. Philosophy is organized piffle" -attributed to

I've got an update on this case Using tkmib I discovered that my UPS (NMC per say) sends its state by OID 1.3.6.1.4.1.318.1.1.1.11.1.1.0 .iso.org.dod.internet.private.enterprises.apc.products.hardware.ups.upsState.upsBasicState.upsBasicStateOutputState.0 = 0001010000000000001000000000000000000000000000000000000000000000 (mib used for this snmpget was powernet441.mib) (I got a description about

Hello Jim, That?s a great help for me. You?re a so kind person ~ Our engineer download the branches f17d9f5 as below and repackage it for test. After testing, The Beta NUT works well with ST VID "0x0483", PID "0xA430. Please tell me how to speed up for merging this to formal version. May I have your predict schedule if possible? Thanks.

FWIW, there is precedent with libusb{1,0}, libshut and libhid which abstract NUT operations from a "backend lib" to build against; similar for serial.c used by many drivers. Take care to not conflict by filenames with "real" third-party libs used by the build - especially to avoid mixups for headers and in docs/discussion. Jim On Thu, Feb 23, 2023, 22:16 MODRIS B?RZONIS

Hello, and thanks for the clarifications. As described, the change does not seem to be too complex on the NUT project's side, the PR posted below took about an hour with some research and this write-up, so I'm not sure I can put a price tag on it :) A donation at https://opencollective.com/networkupstools or https://github.com/sponsors/networkupstools would be welcome though, more so a

?Hello everybody, just a few notes to the doxygen X man issue: 1/ AFAIK doxygen can generate man pages, so why don't we just generate them and decide then whether they are ill fitted or usable... 2/ I'd definitely use doxygen when possible; I mean I don't know any alternative that's able to do (at least partial) validation of the documentation with the source 3/ I

[BackUPS] driver = apcsmart port = /dev/ttyS0 desc "Back-UPS BK-300 @ Cap a l'orignal" > ----- Original Message ----- > From: "Charles Lepple" <clepple@gmail.com> > To: "NUT-MList" <nut-upsdev@lists.alioth.debian.org> > Sent: Monday, June 19, 2006 2:38 PM > Subject: Re: [Nut-upsdev] Backups 300VA (BK-300C) Drivers >

So what would it take me to edit NUT's code for my case to work? My Network Management Card sends its output state using unfortunately only (I guess so) this OID: 1.3.6.1.4.1.318.1.1.1.11.1.1.0 Weirdly the standard way of obtaining Battery Status (drivers/apc-mib.c) 1.3.6.1.4.1.318.1.1.1.2.1.1.0 gives me good results. Unfortunately power status OID's value type differs (my: 64 digits