similar to: drivers/bcmxcp.c portability issue

Fellows, time has come for a new NUT release: I'm planning on 2.6.1 next week (max Friday 27), and I'm currently processing remaining patches. If you have some more on your side, please send in. cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer -

On Jul 2, 2013, at 5:16 PM, Kjell Claesson wrote: >> I hope other people can also test this. >> >> Regards >> Alf Hogemark > > Due to some crashes on the disks and lack of time I don't have the git on the > pc now. But maybe some other can commit this. I'd like to ask people to specifically try the bcmxcp branch on GitHub - it includes some changes

Hi Here is a very minor patch for the bcmxcp.c driver, mainly fixing the function name used in debug statement, and at the same time fix indentation. Regards Alf Hogemark From 86c7940d0ea11b5b38a7f4518095ee2428d658c7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alf=20H=C3=B8gemark?= <alf at i100.no> Date: Mon, 1 Jul 2013 21:11:40 +0200 Subject: [PATCH] bcmxcp: Fix method name outputted in

Hi all, I just acquired a new UPS and have been trying to get it to work with NUT. It's an Eaton/Powerware 9120 700i with both USB and RS-232 interfaces. I first tried the USB interface (using bcmxcp_usb) and found that the UPS worked fine for a few minutes but then NUT lost communication and didn't get it back. In addition the UPS itself seemed to lock up at one point such that the

Hi Inspired by the changes by Prachi Gandhi to use the command map from the UPS in the bcmxcp driver, I think the map should be used, if available, to control all commands the driver adds using "dstate_addcmd". The following patch is an attempt at doing so. The patch is against the bcmxcp branch. Since my UPS also supports : #define PW_UPS_ON (unsigned char)0x89 /* UPS on

at least for an HP R3000XR with the 6-cereal card, the first CPU is said 6-port card, not the inverter. so get the firmware version from the last CPU, not the first. I wonder wether it makes more sense to store them all, aka ups.firmware.cpu0 etc. $OpenBSD$ --- drivers/bcmxcp.c.orig Wed Aug 23 11:16:01 2006 +++ drivers/bcmxcp.c Wed Aug 23 11:21:26 2006 @@ -742,10 +742,7 @@ void

l?rdagen den 29 juni 2013 11.28.14 skrev Mike.: 8<------------------snip--------------------- Hi Mike, > > Thanks for the quick reply. > > I checked the log file (which, admittedly, I should have done before I > posted about the problem :) ). > > Here's the command and the corresponding log message: > > # upsrw -u au -p ap -s outlet.1.delay.shutdown=12

List: I have an Eaton (Powerware) Model 5115 and am using the bcmxcp_usb driver on a OpenBSD 4.9 system. The upsdrvctl start appears to work and I get a message in my daemon log stating that it successfully started. I can successfully start the upsd daemon. I get a successful start messaage from the upsmon program, but it soon complains of 'stale' data. It looks like the driver

On 6/29/2013 at 6:16 PM Kjell Claesson wrote: |l??rdagen den 29 juni 2013 11.28.14 skrev Mike.: |8<------------------snip--------------------- |Hi Mike, |> |> Thanks for the quick reply. |> |> I checked the log file (which, admittedly, I should have done before I |> posted about the problem :) ). |> |> Here's the command and the corresponding log message: |>

Hi All, I am using Speex for encoding/decoding the audio stream for my streaming application. I have used almost the same code In the sampleenc.c and sampledec.c, except that I have used The buffers from the mic as input for encoder and encoded audio As input for decoder, instead of files input. My Problem is the audio played on the receiving side after decoding Is only a "hush" or it

The meter map is basically a bitmap that indicates what variables are output (and in what format) by the UPS. You will likely see a variable, 'not mapped' or nothing. The variables and 'not mapped' items are output by the UPS in the measurement block, and the map tells nut how to read it. 'Unmapped' means that there is a variable there that nut is ignoring, and the xcp

Hi All, I'm a system administrator of a large data center, and I've recently replaced the machine that acted as the nut master for our cluster/cloud. The machine that was interfacing with our Powerware 9135 450KVA 3 phase UPS, not to confused with Eaton's Powerware 9135, and was a Fedora Core 4 box running nut version 2.0.3-4 connected by a serial cable. We are using these versions

I'm trying to get a Powerware 5125 UPS running using the bcmxcp driver, but I get the following errors: video2:~# /sbin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4) Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Communications with UPS lost: Error executing

Hi I have now done some work to clean up the bcmxcp driver somewhat, and then addede support for a number of more ups variables, so if you have hardware supporting it, you should get more output from "upsc" command, for example. I do not have hardware to test this, so I hope someone do have hardware and are willing to test. The changes should be ok, it is just add new mappings from

Hello! It looks like bcmxcp driver doesn't fit my device: UPS Model ? ? ? ? ? ? ? ? ? ?PW9125 UPS Firmware Version ? ?FP: 1.10 INV: 1.10 VA Rating ? ? ? ? ? ? ? ? ? ? ?3000 VA Web/SNMP card is present. Minicom connection to /dev/ttyS0 gives nice banner and control menu, but they prevent nut driver from working correctly (I guess). UPS should be switched into "Pass-Through" mode

Hello! It looks like bcmxcp driver doesn't fit my device: UPS Model ? ? ? ? ? ? ? ? ? ?PW9125 UPS Firmware Version ? ?FP: 1.10 INV: 1.10 VA Rating ? ? ? ? ? ? ? ? ? ? ?3000 VA Web/SNMP card is present. Minicom connection to /dev/ttyS0 gives nice banner and control menu, but they prevent nut driver from working correctly (I guess). UPS should be switched into "Pass-Through" mode

Hi, Got this mail. It looks like he has a ups with revision before K, and need another startup. The 'PW_SET_REQ_ONLY_MODE' is not implemented, so to make it work we have to follow the protocol and send a 'PW_ID_BLOCK_REQ'. This in comsetup of bcmxcp_ser.c Also the standard id block ends with 'Statistics Map', so we have to Skip after reading the length of the 'Size

Hi, just through setting up nut-2.0.2 I ran into a shutdown problem. As I have already spend some time on it and don't know any further, I like to ask for advice. Situation: Powerware 9125 serially connected using /dev/cua0 nut compiled and installed fine system shall - broadcast a message and shut down if ups on battery for 30+ s - wait 120 s - broadcast another message - give system 120

Hi Just to let you know that I have updated the pull request 33, adding these as well : bcmxcp: Add mapping for input.quality to meters bcmxcp: Output more info hardware capabilities in debug mode bcmxcp: Add support for reading topology map and setting ups.description Alf

Greetings, I have been using the bcmxcp_usb driver heavily over the last two years as part of a very successful product, first from NUT 2.4.1 and now from NUT 2.6.0. Now I have a need to do setvar of the outlet.n.delay.start variables, so recently I modified bcmxcp.c to do that. I've tested it and it works well for my purposes. My plans are to begin shipping that modified driver as part