#x27; driver.
Older 9120 talk upscode, so if serial it could be 'upscode2'
Regards
Kjell Claesson
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
d to the
right owner.
This should be handled by udev. But I have seen some dist's that
had some problem with this.
Regards
Kjell Claesson
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
torsdagen den 6 juni 2013 14.58.53 skrev Jim Seymour:
> Hi There,
Hi Jim,
> We have this rather large-ish floor-standing Best Axxium Pro, Model
> Series 0650.
>
That would be the tower model.
> I tried using both the "bestups" and "blazer_ser" drivers with it, but
> no go. So before I go any fu
other meter values.
>
Yes we did not have the complete meter map when we started out the driver. So
this is an old remain. But it is the same. What is done is that the PhaseA VA
is divided with the nominal VA * 100 so it gives the same as % load on Phas
tisdagen den 1 december 2015 09.14.59 skrev Marks, Connor:
Hi Marks.
> Yes I do have Linux. I have assigned the ups.conf file as seen below..
>
> [testups]
> Driver = usbhid-ups
> Port = /dev/ttyUSB0
>
You need to change the driver to mge-shut (hid over seria
Hi,
Made a test build of the Testing branch. The problem is that upsmon
and upsc is not respecting the revision change of libupsclient.so.
It is now libupsclient.so.1, but i get this.
/usr/sbin/upsmon: error while loading shared libraries: libupsclient.so.0:
cannot open shared object file: No s
I
only have ..so.1 I did not think it would help, and it did not.
> On Thu, Feb 21, 2008 at 2:09 PM, Kjell Claesson
>
> <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > Made a test build of the Testing branch. The problem is that upsmon
> > and upsc i
Den Thursday 21 February 2008 20.30.51 skrev Charles Lepple:
> On Thu, Feb 21, 2008 at 2:09 PM, Kjell Claesson
>
Sorry forgot.
Also used parameter
--without-hal
Kjell
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.or
OK Charles,
I found the problem. The autotools is playing a trick with me.
And this is Gentoo specific, so no problem with the nut config.
Kjell
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/li
Den Monday 03 March 2008 14.07.17 skrev AE sysadmin:
> Hi,
>
Hi Vova,
> I am unable to monitor my RS232S connected device with
> any of the monitors I have tried - either splitting COM1 or
> sharing it results in device side timeouts.
>
> I did not test the device from NUT as it is not supported of
Den Tuesday 20 May 2008 03.21.22 skrev Charles Lepple:
> On May 19, 2008, at 6:27 PM, David Mathog wrote:
> > No idea why it thinks it is a Liebert.
>
> It's only looking at the USB vendor ID, and the only Liebert USB UPS
> that we heard about had that vendor ID. (Then again, these may be
> complet
Hi Alexander,
Den Sunday 08 June 2008 02.45.36 skrev Alexander I. Gordeev:
> On Sat, 07 Jun 2008 00:40:28 +0400, Axel Gembe <[EMAIL PROTECTED]> wrote:
> > Uses Megatec USB Phoenix Subdriver, USB Id is 06da:0002.
Hmm.. This may cause trouble in the hal enabled drivers. Check this section of
the u
Den Tuesday 10 June 2008 18.21.33 skrev Axel Gembe:
> Alex wrote:
> > Hi, i just got a Phoenix Technologies PH1200UPSB 1200va serial-port ups
> > and it is only partially supported by bestups driver (needs manual ID or
> > driver rewriting).
>
> ... Try the patch I posted earlier which adds another
Hi Arnaud,
Den Tuesday 24 June 2008 16.01.10 skrev Arnaud Quette:
> I forgot to cc you guys on the future evolution of the HAL support
> (it's replacement in fact, called DeviceKit)
> A mailing list dedicated to DeviceKit is under creation.
> If some of you are interested in, just answer back.
>
>
Den Thursday 26 June 2008 13.08.02 skrev du:
Hi Jean-Luc,
> I've just tested: it i fine with key=info.subsystem.
>
> But it is not (as you say) "the entry matching my unit", it is at the
> top level:
>
>
>
>
>
Yep that the only place you find 'info.bus'. Nice that it solved the
problem
Hi Arjen,
Den Thursday 26 June 2008 15.41.19 skrev Arjen de Korte:
> >> I've just tested: it i fine with key=info.subsystem.
> >>
> >> But it is not (as you say) "the entry matching my unit", it is at the
> >> top level:
> >>
> >>
> >>
> >>
> >>
> >
> > Yep that the only place you find '
Den Friday 04 July 2008 14.22.18 skrev Arnaud Quette:
> Here are some Powerware compatibility info I got by a colleague, and
> authorized to publish.
>
> @Kjell: can you take over checking our driver.list and other info source
> to see if there's a gap?
Hi Arnaud,
The list seems OK. even got the
Den Monday 07 July 2008 15.16.36 skrev Arnaud Quette:
OK Arnaud,
> > I have all the info I need, but i lack the hardware to test it on.
>
> yep, I know. That's still part of the planned actions.
> But the current scope is still limited to MGE Office Protection Systems.
> The other Eaton owned compa
Hi David,
Den Friday 11 July 2008 21.53.45 skrev David Mathog:
>
> ./configure --with-usb --with-user=nut --with-group-nut
As you configured it to run as user nut, and group nut
> upsmon.conf:
> RUN_AS_USER monuser
This line in the upsmon.conf should be
RUN_AS_USER nut
If you look at this ps
Hi,
Have a question regarding 'outlet.n.status'.
In the new-names.txt it say on/off. The problem is
that I get more than just on/off.
I can get:
1 = On/Closed, 2 = Off/Open, 3 = On with Pending Off, 4 = Off with Pending On,
5 = Unknown, 6= Reserved/Unknown, 7= Failed and Closed, 8=Failed and O
Hi all,
Have a strange behaviour that I don't know how to debug.
This is when I use the Eaton PW5125 ups. I have it connected
And running in standby.
Starting up the drivers (pw3105 and pw5125) and they run.
Start up the upsd and can read info from both of them. The 3105 is
supplying the computer
Den Sunday 21 December 2008 18.08.07 skrev Charles Lepple:
Hi Charles,
Sorry for the delay but I have to check things out and make some builds.
> Is this a released version of NUT, or from SVN? (If SVN, which revision?)
This is from svn revision 1665. I have made an svn ebuild so i build directly
Den Sunday 21 December 2008 22.57.14 skrev Arjen de Korte:
> Citeren Charles Lepple :
Hi Arjen,
> >> This is strange. I have no debugging info but i built it with -g , but
> >> it would
> >> not give me anything but ??:0 as output. So i built it with -gstabs, and
> >> guess what it does not seg
Den Monday 22 December 2008 02.24.56 skrev Charles Lepple:
> Is it possible that the ebuild is stripping the symbols from the
> binaries (either with the "strip" command, or implicitly through
> "install -s")?
>
You are absolutly right about that. The ebuild strip when installing.
So I made my own
Den Monday 22 December 2008 14.46.50 skrev Charles Lepple:
> The code in http://boxster.ghz.cc/projects/nut/changeset/1429 handles
> things differently, but I am confused as to why the new code doesn't
> catch that case properly if the old code worked.
As I wrote in an earlier mail, I can't realy
Hi Arjen,
On top of things as always
-
Log:
Fix potential segmentation fault (NULL pointer
argument wasn't handled)
Can confirm that it work's OK now. No segfault.
Regards
/Kjell
___
Nut-upsdev mailing list
Nu
s still active, I know they have this info.
Im at the moment on a low level of activity, due to many other things to do,
but I keep up with the list traffic and try to have the bcmxcp driver working.
But it need more work.
Regards
Kjell Claesson
___
Nut
Den Wednesday 31 December 2008 21.57.24 skrev Charles Lepple:
Hi Charles,
> 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.
>
That is OK.
> One thing that I
Den Sunday 04 January 2009 13.50.03 skrev Arnaud Quette:
I answer this to,
> Hi Johan,
>
> this wasn't that urgent! compatibility info have still ~ 2 weeks to enter
> the tree!
> so take your time, and don't go awaking your son ;-)
>
> 2009/1/2 Johan Adler
>
> > OK. "upsc " while online, unplugged
onsdag 04 februari 2009 23:24:11 skrev Arjen de Korte:
Hi Arjen,
(Sorry for the bottom quote of original mail)
As I put it in the trunk I feel that I have to fix some of the code.
Send a copy of the mail to Elio. I have made some changes to the code,
as you suggested. But I leave it up to Elio t
fredag 06 februari 2009 08:36:28 skrev Arjen de Korte:
Hi,
A little miss understanding.
> Citeren Kjell Claesson :
> >> > 629 dstate_setinfo("ups.realpower", "%d",
> >> > (int)((float)(p[4]*256 + p[5]) * 0.6)) ;
> >>
måndag 16 februari 2009 16:17:19 skrev Arnaud Quette:
> 2009/2/16 Arjen de Korte >
>
> > Citeren Arnaud Quette :
> >
> > Kjell,
> >
> >> have you taken a look at that one?
> >>
> >> -- Arnaud
> >
> > I (attempted) to fix this in r1763. Since I don't own (or have access to)
> > a compatible UPS,
onsdag 18 mars 2009 12:11:47 skrev Philip Ward:
Hi Philip,
The best is to do a separate include like hpmib.h (or cpqmib.h),
Like the pwmib.h for Powerware.
The R5500XR use the CPQPOWER.MIB. You may find info here:
http://www.snmplink.org/cgi-
bin/nd/m/Ent/H/Hewlett%20Packard%20(HP)/%5BALL%5D%20
måndag 23 mars 2009 21:07:15 skrev Arjen de Korte:
Hi Arjen,
> Citeren Kjell Claesson :
> > Author: keyson-guest
> > Date: Mon Mar 23 17:37:37 2009
> > New Revision: 1817
> >
> > Log:
> > data/driver.list, add Eaton Powerware 9130 compatibility with bc
> On Thu, 1 Oct 2009, Stuart D. Gathman wrote:
Hi Gabor,
> > keep simulation parameters in a separate config file from driver
> > parameters.
>
> Meanwhile file docs/developers.txt writes (watch the third sentence):
Yep, And that is described in line two of the next paragraph.
> | Note: this doe
Hi David,
> Arjen,
>
> I read the following in the upgrade notes and just wanted to see what
> the
> status was for the cyberpower driver? The note reads:
>
> - The cpsups and nitram drivers have been replaced by the powerpanel
> driver, and removed from the tree. The cyberpower driver m
Hi Rich,
> 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.
>
Yes the driver can hav
OK Arnaud
> - Arjen, Charles, Kjell, Alex: can you please check your drivers?
>
> - All: I may have missed or overcome something! please review this file.
> and send back your comments.
>
I don't know about this one:
"HP""ups" "5" "R3000 XR" "" "bcmxcp"
"HP""ups" "5"
Hi
>
> indeed.
> more generally, I think that the current 2 seconds polling interval
> was well adapted to dumb units, but not that much to smart ones.
>
This is something that been on my mind also. Some high end ups'es
is giving a lot of data on each poll.
> I have another incomplete reflexion
Hi Tim,
> I ran into a portability issue with drivers/bcmxcp.c in nut-2.4.1 on
> my UnixWare 7.1.4 machine. The error I get is
> .
> UX:acomp: ERROR: "/opt/src/utils/nut-2.4.1/drivers/bcmxcp.c", line 835:
> integral constant expression expected .
>
> Looking at the code we see
> .
> i
> Hello!
Hello Jon,
>
> I have installed the nut package from the OpenBSD 4.4 packages tree,
> nut-2.2.1p0
>
Maybe this page give you some hint. I'm not so good at openbsd.
https://calomel.org/nut_ups.html
> I have a new APC Smart-UPS 750 which I plan to connect via USB. When I
> try to start t
Hi all,
Arjen can you enlighten me about the function of the blazer upsdrv_shutdown
function.
I think they are in the wrong order.
Regards
Kjell
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/li
OK Arjen,
> Citeren Kjell Claesson :
> > Arjen can you enlighten me about the function of the blazer
> > upsdrv_shutdown function.
>
> We first stop any pending shutdowns and then send it a shutdown with
> delay command.
>
Now I got it. I walked throug the blazer_instc
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 'St
Follow up.
--- Begin Message ---
Once upon a time, Chris Adams said:
> I have an older Powerware 9315 UPS that I monitor from a Linux box
> running Network UPS Tools and the bcmxcp driver. I upgraded that
> server, including a much newer version of NUT (2.4.3), and now it can't
> monitor my UPS.
--- Begin Message ---
On 2011-01-14 20.52, Chris Adams wrote:
Hi Chris,
> I have an older Powerware 9315 UPS that I monitor from a Linux box
> running Network UPS Tools and the bcmxcp driver. I upgraded that
> server, including a much newer version of NUT (2.4.3), and now it can't
> monitor my U
torsdagen den 29 mars 2012 18.38.17 skrev Arnaud Quette:
> Hi Peter,
>
> sorry for the lag in answering... crowded week.
>
> One thing bothers me. I don't see parameters like "battery.runtime.low"
>
> > here. How will the UPS notice the NUT that it is running critically low?
> > Or
> > better s
47 matches
Mail list logo
