similar to: Re: Nut-upsdev Digest, Vol 22, Issue 5

Hi Kjell, a few notes: - you should bump the DRV_VERSION upon every change - you should track the drivers TODO list in a comment header (such as "implement smart load segment detection" completed with your info, ...). That would help to bootstrap new contributors. - you can also use the alioth trackers (features request, or task) to give some external visibility on what remains to be

Also works if you want to shutdown one segment/outlet early in the power failure. It should stay off until utility power returns and then apply the configured delay - although I haven't tested this aspect. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: bcmxcp.c.diff Url:

I certainly saw the issue with the non-APIC HAL, but I don''t see any performance or CPU issues with the APIC MP HAL. -Nick -----Original Message----- From: Venefax <venefax@gmail.com> To: ''James Harper'' <james.harper@bendigoit.com.au>, ''Oliver Wilcock'' <oliver@owch.ca>, xen-users@lists.xensource.com Subject: RE: [Xen-users] Xen GPL

It seems the `libmodbus` library or headers were not found, or something similar - so the driver against it was not built. Did you install `libmodbus-dev` before the build? What does `config.log` in the build root say (and.or the summary shown after you run the `configure` script)? On Sat, Sep 16, 2023 at 7:46?PM FatGear <fatgear1 at free.fr> wrote: > Hi, > > I don't know what

Hello there, I don't think that's working,? I have done all your repo but i don't know how it's supposed to work. I have a idea, change vendor id and product id? to make the driver try to connect to the ups, what do you think of that ? With this driver maybe : usbhid-ups FatGear Le 16/09/2023 ? 20:40, Jim Klimov a ?crit?: > It seems the `libmodbus` library or headers were

Well, now that the `subdriver` option got added to `usbhid-ups` too, you can at least try that (by building again the current master). See command-line help for the subdrivers it would currently recognize, and copy e.g. the first word as the matching option, e.g.: ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x vendorid=... -x productid=... -x subdriver=... and try to lockpick your

I've patched bcmxcp.c such that it can power cycle the outlet load segments independently on a Powerware PW5125 UPS. I presume that it will work for any XCP protocol UPS with 2 load segments. Should these instant commands be called outlet.1.shutdown.return outlet.2.shutdown.return ? Where do the descriptions displayed by upscmd -l come from? Presently it shows outlet.1.shutdown.return -

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

?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

During the last month, I've been integrating a Powerware 5115 into an embedded system by writing a custom NUT daemon. This work has gone quite well and NUT has been very helpful, but it sure would be nice to have some additional instcmds for the 5115. The bcmxcp driver comments mention "manuals for the BCM/XCP". I'm wondering if I could get a copy of those so that I might

Hello There, I tried your advice and i don't think it works either, See the logs, " /tmp/nut# ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x vendorid=... -x productid=... -x subdriver=... Network UPS Tools - Generic HID driver 0.52 (2.8.0-2557-g81fca30b2) USB communication driver (libusb 1.0) 0.46 ?? 0.000000??? [D3] main_arg: var='port' val='auto' ??

<facepalm ;)> the ellispis "something=..." were supposed to be replaced by your device ID numbers, etc. On Sat, Sep 23, 2023, 18:26 FatGear <fatgear1 at free.fr> wrote: > Hello There, > > I tried your advice and i don't think it works either, > > See the logs, > > " > > /tmp/nut# ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x

Attached is a patch to hopefully improve the wording of some of the man pages. I will commit this in the next few days, but I wanted to give the driver authors a chance to comment. One thing that I feel is important is cross-referencing between the man pages. On the off-chance that someone does RTFM, it would be good if we make sure that a user doesn't have to read too far in order to find

Hi, I want to buy a UPS wfor a PE2800 but I'm mnot sure wich one to choose. is 1000 VA enough or do I need the 1500 VA version? 1) APC Smart-UPS 1000 VA Black SMART UPS 1000 VA BLACK 1000 VA LINE-INTERACTIV [SUA1000I] 2) Power Supply Apc-ups 1500va Floorstand Incl Control Cable Usb And Com Port Output Power 980w Other suggestions are also welcome As long as they can talk to the apcd

Dear NUT developers, I am using NUT + bcmxcp + Powerware 9315. I would like to use NUT to shut down my systems if the air conditioning fails and the room get too hot. I want the same shutdown sequence as would be produced when the UPS goes on battery. The UPS has a terminal block at the front for up to six different 'building alarms'. I can connect a thermostat (35C) to 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

I'm currently testing the bcmxcp driver for NUT, and it causes me some trouble. And when scanning the archives it seems like the 3110 USB problem reported recently. The bcmxcp daemon stops running, and the logs shows the following: Oct 6 14:22:32 host.dom.tld bcmxcp[82628]: Communications with UPS lost: Receive error (data): got -1 bytes instead of 28!!! Oct 6 14:22:33 host.dom.tld

On Feb 18, 2012, at 10:19 PM, Charles Lepple wrote: > Author: clepple-guest > Date: Sun Feb 19 03:19:02 2012 > New Revision: 3448 > URL: http://trac.networkupstools.org/projects/nut/changeset/3448 > > Log: > Don't allocate storage for variables in bcmxcp.h > > The header files should declare variables as extern, and they should be > allocated in only one .c

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 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