similar to: Looking for volunteers to test nut-scanner against APC USB UPSes

On Apr 25, 2013, at 9:42 AM, Christian Wiese wrote: > I created a pull request #27 which is fixing the issue. > > # nut-scanner -qNU > [nutdev1] > driver = "usbhid-ups" > port = "auto" > vendorid = "051D" > productid = "0002" > product = "Back-UPS ES 700G FW:871.O2 .I USB FW:O2" > serial = "5B1243T01934"

OK Eric, Den Tuesday 22 May 2007 08.56.08 skrev Eric S. Raymond: > Kjell Claesson <kjell.claesson at epost.tidanet.se>: > > Or install the udev rules and replug the ups. > > Did that. Manual startup of the driver now works without -u root, > indicating (I think) that the udev rools are doing their job. This >

Just a hunch about your snmpwalk, what happens if you format like this? snmpwalk -l authpriv -v 3 -u user -a MD5 -x DES -A authpassphrase -X privpassphrase {host address} so snmpwalk -l authpriv -v 3 -u nut -a MD5 -x DES -A NutScan at Password43LongerWord -X NutScan at Password43LongerWord apcups Thank you, David Zomaya Tripp Lite ________________________________ From: Nut-upsuser

OS: CentOS 7 NUT Version: 2.7 Installed NUT through: yum install nut UPS: APC smart UPS srt3000 with NMC I am trying to set up NUT with snmp for my apc ups. Heres the config; [ups6]                 Driver = snmp-ups                 Port: ups6.domain.name (also tried 192.168.24.9)                 Snmp_version = v3                 secLevel = authPriv                 secName = ups6

I'm trying to get SNMPv3 management working for an APC AP9617 card. It is newly refurbed, running sumx v3.7.2 and aos v3.7.3. In the SNMPv3 user profiles section I have (I don't care about the password leaking, it's temporary): User Name: nut Authentication Passphrase: NutScan at Password43LongerWord Privacy Passphrase: NutScan at Password43LongerWord Authentication protocol:

Hi, I've got a question about managing two UPSes under NUT. I have two similar model APC usb-connected UPSes to work with, but don't know how to manage them simultaneously from under Windows. Long story short, my ups.conf looks like this: --- ups.conf --- [ups1] driver= usbhid-ups port= auto serial=AS1054340323 [ups2] driver= usbhid-ups port= auto serial=AS1026662626 ---

Hello Ted, 2013/9/11 Ted Mittelstaedt <tedm at mittelstaedt.us> > Hi All, > > About a month ago APC announced they were including MODBUS protocol > support in their new APC UPSes. The technical note on this is here: > > http://www.apcmedia.com/**salestools/MPAO-98KJ7F/MPAO-**98KJ7F_R0_EN.pdf<http://www.apcmedia.com/salestools/MPAO-98KJ7F/MPAO-98KJ7F_R0_EN.pdf>

Hi All, About a month ago APC announced they were including MODBUS protocol support in their new APC UPSes. The technical note on this is here: http://www.apcmedia.com/salestools/MPAO-98KJ7F/MPAO-98KJ7F_R0_EN.pdf "Application Note #176 Modbus Implementation in APC Smart-UPS" The APC "announcement" appeared on their site in their user blogs by an APC employee, here:

Hi, all! I sucessfully install NUT by source, but it could not recognize my UPS device My UPS device is APC Smart-UPS 750VA USB & Serial 230V for China. Pruduct introduction: http://www.apc.com/products/resource/include/techspec_index.cfm?base_sku=SUA750ICH The page is in Chinese. It may be similar with this one:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Good day to all. In one of the offices I'm administering there are about 15 UPS marked with the brand "Ippon BackPro". This brand is widely popular in Russian Federation, while by itself is a 'Made in PRC' megatec clone. Depending on the model this UPSes have got either one standard serial RS-232C interface (cheaper models like

Hi, I have a small home LAN consisting of four PC's: one old Pentium III box acting as gateway / connection handler / printer server / file server / scanner server, and then one desktop and two laptops. I recently migrated this LAN from Slackware 10.2 to CentOS 4.3, and everything runs rather fine. One thing I have some trouble setting up is my Canon Perfection USB scanner for network use,

Folks, while I've got the above combination to compile and run under Solaris 10, it seems that there are still problems in the libusb/ugen driver stack from Sun and or the APC Smart UPS 1500, so things aren't actually working. It seems that the APC Smart UPS 1500RM doesn't return the HID descriptor length information in 0x21 as noted in a previous thread, but in my case, it also

On Sep 12, 2014, at 5:15 PM, Stan Gammons <sg063015 at gmail.com> wrote: > On 09/11/14 22:34, Charles Lepple wrote: >> On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote: >> >>> I see a libusb_get_interrupt message in the log. Could that be the problem? >> Yes, it seems related. >> >> 1.126896 upsdrv_initinfo...

On 4/28/20 1:58 PM, David Zomaya wrote: > snmpwalk -l authpriv -v 3 -u user -a MD5 -x DES -A authpassphrase -X > privpassphrase Evidently, even with argument identifiers order matters. That worked just fine and dandy. Now I guess I need to play with the order of the nut-scanner arguments to see if I get a similar result. thanks, nomad

On 09/17/14 22:31, Charles Lepple wrote: > On Sep 12, 2014, at 5:15 PM, Stan Gammons <sg063015 at gmail.com> wrote: > >> On 09/11/14 22:34, Charles Lepple wrote: >>> On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote: >>> >>>> I see a libusb_get_interrupt message in the log. Could that be the problem? >>> Yes, it

Hi Chad, Thanks for your report. Everything seems fine, apart from the battery.date (2052/00/36), which vaguely recall me something... I've added this info to the Testing and trunk driver.list Arnaud -- Please note my new email address: arnaudquette at eaton.com -- Linux / Unix Expert R&D - MGE Office Protection Systems - http://www.mgeops.com Network UPS Tools (NUT) Project Leader -

On 09/11/14 22:34, Charles Lepple wrote: > On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote: > >> I see a libusb_get_interrupt message in the log. Could that be the problem? > Yes, it seems related. > > 1.126896 upsdrv_initinfo... > 1.126906 upsdrv_updateinfo... > 1.127023 libusb_get_interrupt: Function not implemented >

On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote: > I see a libusb_get_interrupt message in the log. Could that be the problem? Yes, it seems related. 1.126896 upsdrv_initinfo... 1.126906 upsdrv_updateinfo... 1.127023 libusb_get_interrupt: Function not implemented 1.127030 Got 0 HID objects... 1.127036 Quick update... Come to think of it, this

On Sep 23, 2014, at 3:55 AM, Henning Brauer <hb-nut at bsws.de> wrote: > We have upd(4) attaching to these devices now. Either nut needs a > driver getting status from upd (trivial, will show up in the > hw.sensors sysctl tree) or we need some way for nut still being able > to talk to the ups directly, without upd and nut interfering with each > other. While a upd(4) driver

On 06/15/2017 04:32 PM, Arnaud Quette wrote: Hello > > .... still no reply from them ... > > is the guy you contacted Paul Henri? I wrote to a generic alias ( Ro-PQSupport ). Got a reply from a fellow Romanian who also CC:ed something looking like a list (List-EGPQCO-BUCRO-PQ ). I replied to both of them 5 days ago, received nothing since. > >>> Would you also