similar to: newhidups capture

I'm trying to use a rackmount Smart-UPS from APC with the USB connector, and I'm running into some issues. They seem to stem from the fact that the Report Descriptor is much larger than any other UPS I've seen (61939 bytes). Here is the quick fix that I put in libusb.c after getting the HID descriptor, and before getting the Report descriptor, which seems to work okay:

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

The (2.2.1) upshid-ups driver reports battery.temperature rather than ups.temperature. Here's a quick patch to have it show up in the status page... --- clients/upsstats.c.DIST 2008-03-04 09:15:40.000000000 +0000 +++ clients/upsstats.c 2008-03-04 09:16:20.000000000 +0000 @@ -787,6 +787,11 @@ return 1; } + if (!strcmp(cmd, "BATTTEMP")) { +

I know this isn't exactly the right place to ask, but I figure at least *someone* on this list has done it once. I recently acquired an AP9617 web/snmp management board for my UPS. The web and telnet part of it work great. However, I can't get *anything* from the snmp interface. I've triple-checked the community name and access settings (currently are wide open). I've ensured

Perhaps someone else could confirm this, I have an APC UPS with a built-in network management card with environmental sensor for temp/humidity. The OID index for the sensors appears to be .1 (the last component for each of the OIDs listed below). The original source code has them at .0 drivers/apccmib.h #define APCC_OID_IEM_TEMP ".1.3.6.1.4.1.318.1.1.10.2.3.2.1.4.1" #define

Hi, I was wondering if there was any support in NUT for networked APC UPS's. All the configuration examples I see in the documentation are for USB/Serial connections to the UPS. I could mess around with serial/USB cables, but I'd really rather talk to the UPS over the network. I don't want all my servers relying on a single machine with a serial connection. -matthew

Hi, I was wondering if there was any support in NUT for networked APC UPS's. All the configuration examples I see in the documentation are for USB/Serial connections to the UPS. I could mess around with serial/USB cables, but I'd really rather talk to the UPS over the network. I don't want all my servers relying on a single machine with a serial connection. -matthew

Hi. Could anyone please provide info on how nut makes ups restart after power is back? I've configured nut to communicate with APC SmartUPS 750 via 'newhidups' driver and this works w/o probs in case of shutting the system down. The UPS would stay on though. After the power returns, I'd expect UPS to restart so that servers would start either. This would never happen, and I have to

Hello list. I'm contemplating buying new batteries and putting an older APC Smart-UPS 3000XL back into service. Would that work well with NUT? Any drawbacks to consider? Thank you, Tobias -- Tobias Balle-Petersen Kontrapunkt Group / System Administrator

We recently had to replace an old APC SmartUPS 3000 with a newer 3000VA (the 2U one). It has both serial and USB in the back (with an RJ-45 on the end of the serial cable). I can't get the apcsmart driver to connect. I figured it should work the exact same as the old UPS, with /dev/ttyS0 as the port (I'm using the same port on the server that the last one was plugged into). I even

Hello. I've been running a two machine setup with a mge-shut for some time without problems, and now I'm configuring a three machine setup with an APC Smart 1500. The UPS has three machines connected to it, in a peculiar way: one windows machine is connected via USB. The second windows machine is using an agent to monitor messages from the first windows machine. Then, I have a GNU/Linux

Well, after our first real extended power outage, I found out that even though the UPS 1000 RM is recognized okay, it does not work properly. It never seems to see any change in UPS status. It looks very similar to the other issue I reported with the APC CyberFort 350. I never was able to get to the bottom of the CyberFort issue, but I'll bet it's the same issue as we have with the

Greetings: I've been following through the instructions on how to connect an APC BackUPS 650 ES to USB, and have it monitored with NUT... I know my system can SEE the UPS, as DMESG shows this: hiddev96: USB HID v1.10 Device [APC Back-UPS ES 650 FW:818.w1.D USB FW:w1] on usb-0000:00:04.2-1 usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver I can see

Network UPS Tools version 2.0.5 has been released. http://www.networkupstools.org/ Direct access: - Download: http://www.networkupstools.org/source/2.0/nut-2.0.5.tar.gz - News: http://www.networkupstools.org/source/2.0/new-2.0.5.txt - ChangeLog: http://www.networkupstools.org/source/2.0/ChangeLog

Network UPS Tools version 2.0.5 has been released. http://www.networkupstools.org/ Direct access: - Download: http://www.networkupstools.org/source/2.0/nut-2.0.5.tar.gz - News: http://www.networkupstools.org/source/2.0/new-2.0.5.txt - ChangeLog: http://www.networkupstools.org/source/2.0/ChangeLog

Shamelessly reusing the announcement Arnaud sent about three months ago for nut-2.2.1: "We're preparing to release 2.2.1-pre2, so if you have some fixes to backport on Testing, consider announcing it and doing asap. As always, compatibilities update and bugfixes only!" Regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1

* Is there a way to configure NUT so that it recognizes the huge additional battery pack that has been attached to the 2200XL? The 51minutes runtime is a number consistent with the load we have placed on a stock standalone 2200XL. With the extra large battery pack we've added, the runtime should be more than 2.5 hours. * I see the "Bizzare configuration" graphic on the

Here's a patch (against 2.2.2) which adds battery.temperature to the ietf-mib snmp driver. While looking at ietfmib.h I noticed that the value for IETF_OID_IN_LINES is actually that for upsOutputNumLines.0. Does anyone know whether that's deliberate or a typo? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/x-patch

Hello Peter! Peter Selinger wrote: > This is useful information. I don't think the device is currently > supported, but the information printed above is enough to write a > subdriver for it. Note that the purpose of the "-x generic" option is > precisely to produce this output. [...] >> Apparently the UPS is recognized but no communication is >>

[please keep the list CC'd] On 12/13/05, ngpost1 <ngpost1@etitech.net> wrote: > Charles, > > Another question: > > When I ran the newhidups -DD.... test, there apparently was no > communication with the UPS. Since I assume is talks with the Megatec > protocol, I wanted to force the protocol in the command line. As far as I know (and I am no expert on