Re: [Nut-upsuser] Cyberpower PR2200ELCDRT2U

[Ben Kamen]

On 11/10/2017 07:59 AM, Charles Lepple wrote:
> [please use reply-all to include the list. thanks!]
>
>
>> OS Name and Version: FreeNAS 11.0U4, no custom modifications
>> Cyberpower PR2200 Firmware: 4.520
>> RMCARD205 Firmware: 1.0.9
> for reference, I think this version of FreeNAS includes NUT 2.7.4.
>
> If this works with a different driver, would you please send a snapshot of 
> the information you get from upsc, upscmd and upsrw as mentioned here? 
> http://networkupstools.org/stable-hcl.html#footnotes
>

If he's using the RMCARD205 (I think that's what I have) with the newer MIB2.0, 
that's the driver I mentioned on the dev list that I'm working on.

It supports a boatload of good stuff he 0.1 doesn't -- but it's not done yet. 
I've been battling client projects including one FPGA project with bugs both in 
the Xilinx FPGA IP and the Xilinx linux kernel driver that controls the FPGA 
IP. (yay)

I'm getting there though.

 -Ben

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] CentOS rpm package installation

[Ben Kamen]

On 06/22/2017 06:13 PM, Manuel Wolfshant wrote:
>
> You are trying to install packages built for Fedora 27 on a CentOS 6 system. 
> This is not possible.
> You can
> -  either use the [old] nut packages from the Fedora EPEL 6 
>   repository. Using EPEL is very simple 
> nowadays, all you need to do is to run the following command:
> yum install epel-release --enablerepo=extras
> ( by default you might not even need the "--enablerepo=extras" part, the 
> repository comes already enabled)
> After that you just run yum install nut ( or nut-client 
> or whatever you need )
> - or you can trust me ( I am a packager for Fedora since 2007 and also what 
> they call a "sponsor" which basically means, among others, that I could also 
> teach people how to package for Fedora and EPEL - but for the last 2-3 years 
> I focused strictly on creating packages that can be used on CentOS systems ) 
> and use the packages I made available via https://wolfy.fedorapeople.org/nut/ 
> . If you want  to use my packages, you will need to download and install them 
> manually, using ( after downloading the needed packages ) a command similar 
> to:
> yum install ./nut*rpm
> If you encounter any issues with my packages ( NOT with nut itself but when 
> installing or dl-ing the packages  ! ) feel free to contact me directy either 
> by mail or via IRC ( I am " wolfy " on #centos-social/Freenode ) and I will 
> be glad to assist you.

Ha!

I was just emailing NUT-Dev about the latest (and CentOS 6) and was about to 
compile manually.

i'll check your packages out.

(I'd actually like to learn how to create packages for situations like this)

In the meantime, thanks for the RPM!

 -Ben


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] NUT support for CyberPower PR1500LCDRTXL2Ua

[Ben Kamen]

On 2016-01-18 6:07 PM, Charles Lepple wrote:

[please use reply-all to include the list. thanks!]

On Jan 18, 2016, at 5:08 PM, Ben Kamen  wrote:


(is the USBHID worth using?)


  - - -

Sounds like you are on the right track with the text protocol. There are two 
different sscanf() format strings - it looks like yours follows similar 
conventions ('I' for input voltage, 'O' for output voltage, etc.). Yours might 
have been cut off, since it seems like the driver tries to read 35 bytes first, 
then an additional 23 if it does not succeed. Note that your result does not 
have 'S', which I would guess is status.



Yea, I'm gonna stick with serial.

I think I'm going to re-write this a little maybe so it just waits for the 
string out the 0x0d so it's a little less length dependent and see.

(so the routine still times out - but complains more about incomplete strings 
than delay of reception.)

an ASCII translation mode sure would be nice. Hahahahah..

BRB...

 -Ben

--
Ben Kamen - O.D.T., S.P.
--
eMail: b...@benjammin.net  http://www.benjammin.net
Fortune says:
Military secrets are the most fleeting of all.
-- Spock, "The Enterprise Incident", stardate 5027.4
-  -
NOTICE: All legal disclaimers sent to benjammin.net/benkamen.net
or any of it's affiliated domains are rendered null and void on
receipt of communications and will be handled/considered as such.


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] NUT support for CyberPower PR1500LCDRTXL2Ua

[Ben Kamen]

On 2016-01-18 4:56 PM, Ben Kamen wrote:


the line that fails looks like:

D
#I120.0O120.0L018B100T027H060.0F060

Where can I look in the source code for where that's sent and parsed? (perhaps 
I can assist updating the driver)

 -Ben

___ 


I see the problem (I think)


in the file powerp-txt.c in the function powpan_status()


/*
 * WRITE D\r
 * READ #I119.0O119.0L000B100T027F060.0S..\r
 *  01234567890123456789012345678901234
 *  0 1 2 3
 *  01234567890123456789012345678901234
 *  #I120.0O120.0L018B100T027H060.0F060
 *
 */

The top set response was written into the file -- the bottom set is what I'm 
getting from the UPS which isn't working... it's a little different.

Now to figure out what the parms mean so I can fix the function to maybe handle 
either string.

 -Ben

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] NUT support for CyberPower PR1500LCDRTXL2Ua

[Ben Kamen]

BTW,

 I did a run with a higher debug level that resulted with this...

[root@cornelius ups]# powerpanel -a office -D -D -D -D -D -D -D -D
Network UPS Tools - CyberPower text/binary protocol UPS driver 0.25 (2.6.5)
Warning: This is an experimental driver.
Some features may not function correctly.

   0.00 debug level is '8'
   0.011347 Trying text protocol...
   0.112558 send: (2 bytes) => 0d 0d
   0.213400 read: (3 bytes) => 23 2d 32
   0.365066 send: (3 bytes) => 50 34 0d
   0.608547 read: (52 bytes) => 23 50 52 31 35 30 30 4c 43 44 52 54 58 4c 
32 55 61 20
   0.608592  20 20 20 2c 34 2e 33 35 30 2c 50 53 55 45 56 32 30 30 30 31 31 
33 2c 43 59
   0.608620  42 45 52 20 50 4f 57 45 52
   0.608645 CyberPower UPS with text protocol on /dev/ttyS0 detected
   0.608679 send_to_all: SETINFO device.type "ups"
   0.608709 send_to_all: SETINFO driver.version "2.6.5"
   0.608761 send_to_all: SETINFO driver.version.internal "0.25"
   0.608790 send_to_all: SETINFO driver.name "powerpanel"
   0.608818 send_to_all: SETINFO ups.mfr "CyberPower"
   0.608845 send_to_all: SETINFO ups.model "[unknown]"
   0.608873 send_to_all: SETINFO ups.serial "[unknown]"
   0.608901 send_to_all: SETINFO ups.delay.start "60"
   0.608929 send_to_all: SETINFO ups.delay.shutdown "60"
   0.608959 send_to_all: SETINFO ups.model "PR1500LCDRTXL2Ua"
   0.608987 send_to_all: SETINFO ups.firmware "4.350"
   0.609016 send_to_all: SETINFO ups.serial "PSUEV2000113"
   0.609043 send_to_all: SETINFO ups.mfr "CYBER POWER"
   0.760850 send: (3 bytes) => 50 33 0d
   0.912565 read: (29 bytes) => 23 31 32 2c 34 78 31 2c 39 2c 30 30 2c 30 
30 35 2c 34
   0.912607  38 30 2c 31 32 2c 34 78 32 2c 39
   0.912664 send_to_all: SETINFO battery.voltage.nominal "12"
   0.912696 send_to_all: SETINFO battery.packs "4"
   0.912727 send_to_all: SETINFO battery.capacity "9"
   1.064328 send: (3 bytes) => 50 32 0d
   1.205572 read: (31 bytes) => 23 31 35 30 30 2c 31 33 35 30 2c 31 32 30 
2c 34 37 2c
   1.205621  36 33 2c 31 32 2e 30 2c 35 33 2c 35 37
   1.205659 send_to_all: SETINFO ups.power.nominal "1500"
   1.205710 send_to_all: SETINFO ups.realpower.nominal "1350"
   1.205741 send_to_all: SETINFO input.voltage.nominal "120"
   1.205770 send_to_all: SETINFO input.frequency.low "47"
   1.205799 send_to_all: SETINFO input.frequency.high "63"
   1.357356 send: (3 bytes) => 50 31 0d
   1.458526 read: (21 bytes) => 23 31 32 30 2c 31 35 30 2c 30 38 30 2c 33 
35 2c 30 30
   1.458557  33 30 30
   1.458596 send_to_all: SETINFO input.transfer.high "150"
   1.458626 send_to_all: SETINFO input.transfer.low "80"
   1.458655 send_to_all: SETINFO battery.charge.low "35"
   1.458680 send_to_all: ADDCMD test.battery.start.quick
   1.458705 send_to_all: ADDCMD test.battery.stop
   1.458730 send_to_all: ADDCMD beeper.enable
   1.458754 send_to_all: ADDCMD beeper.disable
   1.458778 send_to_all: ADDCMD beeper.on
   1.458802 send_to_all: ADDCMD beeper.off
   1.458826 send_to_all: ADDCMD shutdown.stop
   1.610423 send: (3 bytes) => 50 36 0d
   1.823554 read: (44 bytes) => 23 31 34 30 2c 31 34 31 2c 31 34 32 2c 31 
34 33 2c 31
   1.823599  34 34 2c 31 34 35 2c 31 34 36 2c 31 34 37 2c 31 34 38 2c 31 34 
39 2c 31 35
   1.823622  30
   1.823650 send_to_all: SETFLAGS input.transfer.high RW
   1.823682 send_to_all: ADDENUM input.transfer.high "140"
   1.823711 send_to_all: ADDENUM input.transfer.high "141"
   1.823740 send_to_all: ADDENUM input.transfer.high "142"
   1.823768 send_to_all: ADDENUM input.transfer.high "143"
   1.823796 send_to_all: ADDENUM input.transfer.high "144"
   1.823824 send_to_all: ADDENUM input.transfer.high "145"
   1.823853 send_to_all: ADDENUM input.transfer.high "146"
   1.823881 send_to_all: ADDENUM input.transfer.high "147"
   1.823909 send_to_all: ADDENUM input.transfer.high "148"
   1.823938 send_to_all: ADDENUM input.transfer.high "149"
   1.823966 send_to_all: ADDENUM input.transfer.high "150"
   1.975763 send: (3 bytes) => 50 37 0d
   2.174605 read: (44 bytes) => 23 30 38 30 2c 30 38 31 2c 30 38 32 2c 30 
38 33 2c 30
   2.174662  38 34 2c 30 38 35 2c 30 38 36 2c 30 38 37 2c 30 38 38 2c 30 38 
39 2c 30 39
   2.174685  30
   2.174714 send_to_all: SETFLAGS input.transfer.low RW
   2.174748 send_to_all: ADDENUM input.transfer.low "80"
   2.174778 send_to_all: ADDENUM input.transfer.low "81"
   2.174807 send_to_all: ADDENUM input.transfer.low "82"
   2.174835 send_to_all: ADDENUM input.transfer.low "83"
   2.174864 send_to_all: ADDENUM input.transfer.low "84"
   2.174893 send_to_all: ADDENUM input.transfer.low "85"
   2.174921 send_to_all: ADDENUM input.transfer.low "86"
   2.174950 send_to_all: ADDENUM input.transfer.low "87"
   2.174979 send_to_all: A

[Nut-upsuser] NUT support for CyberPower PR1500LCDRTXL2Ua

[Ben Kamen]

Hey all,

 I ended up picking up the module listed in Subject line.

I switched over my config but apparently not all going smoothly.

My config is:

[office]
driver = powerpanel
port   = /dev/ttyS0
desc   = "Office UPS"



When I test the driver running power-panel as a test, I get:


[root@cornelius init.d]# powerpanel -a office -D -D -D -D
Network UPS Tools - CyberPower text/binary protocol UPS driver 0.25 (2.6.5)
Warning: This is an experimental driver.
Some features may not function correctly.

   0.00 debug level is '4'
   0.011515 Trying binary protocol...
   0.213611 send: (2 bytes) => 46 0d
   0.667149 read: timeout
   0.667192   \_: (0 bytes) =>
   0.768409 send: (2 bytes) => 46 0d
   1.223223 read: timeout
   1.223270   \_: (0 bytes) =>
   1.324495 send: (2 bytes) => 46 0d
   1.777587 read: timeout
   1.777634   \_: (0 bytes) =>
   1.798033 Trying text protocol...
   1.898845 send: (2 bytes) => 0d 0d
   1.95 read: (3 bytes) => 23 2d 32
   2.151843 send: (3 bytes) => 50 34 0d
   2.399718 read: (52 bytes) => 23 50 52 31 35 30 30 4c 43 44 52 54 58 4c 
32 55 61 20
   2.399766  20 20 20 2c 34 2e 33 35 30 2c 50 53 55 45 56 32 30 30 30 31 31 
33 2c 43 59
   2.399794  42 45 52 20 50 4f 57 45 52
   2.399818 CyberPower UPS with text protocol on /dev/ttyS0 detected
   2.551420 send: (3 bytes) => 50 33 0d
   2.703743 read: (29 bytes) => 23 31 32 2c 34 78 31 2c 39 2c 30 30 2c 30 
30 35 2c 34
   2.703786  38 30 2c 31 32 2c 34 78 32 2c 39
   2.855643 send: (3 bytes) => 50 32 0d
   2.996719 read: (31 bytes) => 23 31 35 30 30 2c 31 33 35 30 2c 31 32 30 
2c 34 37 2c
   2.996765  36 33 2c 31 32 2e 30 2c 35 33 2c 35 37
   3.148635 send: (3 bytes) => 50 31 0d
   3.249251 read: (21 bytes) => 23 31 32 30 2c 31 35 30 2c 30 38 30 2c 33 
35 2c 30 30
   3.249287  33 30 30
   3.401125 send: (3 bytes) => 50 36 0d
   3.615723 read: (44 bytes) => 23 31 34 30 2c 31 34 31 2c 31 34 32 2c 31 
34 33 2c 31
   3.615799  34 34 2c 31 34 35 2c 31 34 36 2c 31 34 37 2c 31 34 38 2c 31 34 
39 2c 31 35
   3.615823  30
   3.767688 send: (3 bytes) => 50 37 0d
   3.964712 read: (44 bytes) => 23 30 38 30 2c 30 38 31 2c 30 38 32 2c 30 
38 33 2c 30
   3.964781  38 34 2c 30 38 35 2c 30 38 36 2c 30 38 37 2c 30 38 38 2c 30 38 
39 2c 30 39
   3.964806  30
   4.116667 send: (3 bytes) => 50 38 0d
   4.256708 read: (30 bytes) => 23 32 30 2c 32 35 2c 33 30 2c 33 35 2c 34 
30 2c 34 35
   4.256746  2c 35 30 2c 35 35 2c 36 30 2c 36 35
   4.408610 send: (3 bytes) => 50 35 0d
   4.509005 read: (3 bytes) => 23 2d 32
   4.660827 send: (3 bytes) => 50 39 0d
   4.761975 read: (4 bytes) => 23 d5 df f0
   4.863075 send: (2 bytes) => 43 0d
   4.964149 read: (2 bytes) => 23 30
   5.064982 send: (2 bytes) => 44 0d
   5.27 read: (35 bytes) => 23 49 31 31 39 2e 30 4f 31 31 39 2e 30 4c 
30 31 38 42
   5.266710  31 30 30 54 30 32 37 48 30 36 30 2e 30 46 30 36 30
   5.266834 Parsing status string failed
   5.266876 Communications with UPS lost: Status read failed!
   5.267201 dstate_init: sock /var/run/nut/powerpanel-office open on fd 5
   5.368488 send: (2 bytes) => 44 0d
   5.569134 read: (35 bytes) => c0 88 80 57 00 81 0d 23 49 31 32 30 2e 30 
4f 31 32 30
   5.569183  2e 30 4c 30 31 38 42 31 30 30 54 30 32 37 48 30 36
   5.569208 Parsing status string failed
   5.569231 Communications with UPS lost: Status read failed!
   7.374181 send: (2 bytes) => 44 0d
   7.575264 read: (35 bytes) => 23 49 31 32 30 2e 30 4f 31 32 30 2e 30 4c 
30 31 38 42
   7.575313  31 30 30 54 30 32 37 48 30 36 30 2e 30 46 30 36 30
   7.575351 Parsing status string failed
   7.575377 Communications with UPS lost: Status read failed!


Maybe better off just switching to different driver?

(is the USBHID worth using?)

I'm running CentOS 6.7 on this system. not sure if the gnome USB UPS drivers 
are installed. (meh)

Thanks,

 -Ben

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

[Nut-upsuser] NUT and non-APCC UPSs doing calibration runs

[Ben Kamen]

I'm looking to buy some new UPSs and am thinking of parting ways with APC to 
explore other brands.

Can anyone suggest another brand that handles doing calibration runs (or maybe 
another brand doesn't need them) that I can automate with NUT?

Thanks,

 -Ben

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] UPS Groups?

[Ben Kamen]

On 2014-10-15 1:50 PM, Michael Stinaff wrote:

Maybe this will clear up what I was initially thinking.
In this diagram all lines on the right of the UPSs are power lines and all 
lines on the left are serial/usb lines.

  .---.
   +--|UPS+-+++---...
   |  | A1| |||
   |  '---' .---+--. .---+--. .---+--.
   ||Server| |Server| |Server|
   ||  A1  | |  A2  | |  A3  |
   |  .---. '---+--' '---+--' '---+--'
   | +|UPS| |||
   | || A2+-+++---...
   | |'---'
   | |
.-+-+.
|Central |
|NUT Host|
'-+-+'
   | |
   | |.---.
   | +|UPS+-+++---...
   |  | B1| |||
   |  '---' .---+--. .---+--. .---+--.
   ||Server| |Server| |Server|
   ||  B1  | |  B2  | |  B3  |
   |  .---. '---+--' '---+--' '---+--'
   |  |UPS| |||
   +--| B2+-+++---...
  '---'


Mmmm... ASCII art

So reminiscent of the 80's.

Makes me wanna power up my BBS system and look at the old screens again. ;)

I love it.

(thumbs up)

 -Ben

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] NUT-HAL (for use with USB UPS's and Gnome)

[Ben Kamen]

On 2013-11-20 6:20 PM, Charles Lepple wrote:


No need to switch to serial if USB is working - there should be a nut-usb 
package or similar. You will probably have to remove nut-hal to install 
nut-usb. The nut+upsd+upsmon solution is mutually exclusive with nut-hal, but 
they use the same device-specific code, and it sounds like your device is 
compatible.


What yum shows me is: (this is on my NUT master server though just FYI)


Installed Packages
nut.x86_64  2.6.5-2.el6 
  @epel
nut-cgi.x86_64  2.6.5-2.el6 
  @epel
nut-client.x86_64   2.6.5-2.el6 
  @epel
nut-devel.x86_642.6.5-2.el6 
  @epel
Available Packages
nut-client.i686 2.6.5-2.el6 
  epel
nut-devel.i686  2.6.5-2.el6 
  epel
nut-hal.x86_64  2.6.5-2.el6 
  epel
nut-xml.x86_64  2.6.5-2.el6 
  epel



The usbhid-ups drivers are included with nut.x86_64

So I guess my only question is:

Will nut's UPS driver happily coexist with the GNOME's UPS "stuff"?
Or do I need to disable GNOME from sticking its fingers into NUT's control
of the UPS?

Thanks,

 -Ben


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] NUT-HAL (for use with USB UPS's and Gnome)

[Ben Kamen]

On 2013-11-20 6:20 PM, Charles Lepple wrote:

On Nov 18, 2013, at 10:39 AM, Ben Kamen wrote:


My first attempt to post this bounced -- this is a 2nd try.


Sorry about that - Alioth, the server that hosts the lists, was down due to 
disk failure:

http://lists.debian.org/debian-infrastructure-announce/2013/11/msg1.html


Oops! hahaha. I was wondering. ;)


I've recently installed a CyberPower OR500 on a CentOS 6.4 system.

nut comes RPM'd as nut-hal -- and I've played a little with it - but I'm trying 
to figure out
just what it provides at that point. (looking at the docs, I'm not quite sure)


The idea was that the HAL-based drivers would make the UPS appear like a 
battery to the GNOME power management software, but then HAL was deprecated. So 
we never really finished the documentation.


I'd like NUT on this system to allow my NUT master server to just monitor and 
email notification as the system
NUT-HAL is running on is standalone on its UPS and that's fine with me.

I just want to know when the system has power issues and work NUT's monitoring 
in with my Munin master server as well.

Should I move to the full NUT version on this system (and switch to Serial and 
not USB?)



No need to switch to serial if USB is working - there should be a nut-usb 
package or similar. You will probably have to remove nut-hal to install 
nut-usb. The nut+upsd+upsmon solution is mutually exclusive with nut-hal, but 
they use the same device-specific code, and it sounds like your device is 
compatible.


I'll take a look and reply back.

Thanks Charles!

--Ben


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

[Nut-upsuser] NUT-HAL (for use with USB UPS's and Gnome)

[Ben Kamen]

My first attempt to post this bounced -- this is a 2nd try.

-

I've recently installed a CyberPower OR500 on a CentOS 6.4 system.

nut comes RPM'd as nut-hal -- and I've played a little with it - but I'm trying 
to figure out
just what it provides at that point. (looking at the docs, I'm not quite sure)

I'd like NUT on this system to allow my NUT master server to just monitor and 
email notification as the system
NUT-HAL is running on is standalone on its UPS and that's fine with me.

I just want to know when the system has power issues and work NUT's monitoring 
in with my Munin master server as well.

Should I move to the full NUT version on this system (and switch to Serial and 
not USB?)

Thanks,

 -Ben

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Support for APC Smart-UPS X 3000

[Ben Kamen]

On 2013-09-17 4:48 PM, Douglas Parsons wrote:

Just my experiences speaking, look at another brand. I use MGE/Eaton and have 
had much better life and the quality has been much better. APC does not release 
the protocol for comunicating with the UPS and so to get NUT to work you have 
to sniff the traffic and then figure out what the commands and responses 
mean.(thus reverse engineered) APC also will change the protocol between 
models. (Thus why that model is not listed, it may work, it may not)

I have had four APC brand UPS units melt the batteries. We bought 13 identical 
units in one order. One blew up on power up. One had loose connections giving a 
false ground issue. Four did not have all the holes tapped out for mounting. 
And 6 were rusty. Those were the last APC units we bought.


I am also frustrated with APC's designs that regularly roast batteries by 
pushing them to the edge of their max charge current by design.

I have too many APC units and am planning on phasing them out as I can.

 -Ben



--
Ben Kamen - O.D.T., S.P.
--
eMail: b...@benjammin.net  http://www.benjammin.net
Fortune says:
Intuition, however illogical, is recognized as a command prerogative.
-- Kirk, "Obsession", stardate 3620.7
-  -
NOTICE: All legal disclaimers sent to benjammin.net/benkamen.net
or any of it's affiliated domains are rendered null and void on
receipt of communications and will be handled/considered as such.


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] APC Measure UPS support

[Ben Kamen]

On 2013-02-17 9:32 PM, Ben Kamen wrote:

Hey all,

  I have a measure-UPS card and the external cabled module.

They're supposed to operate the same... does NUT auto detect them when using 
the apcsmart driver or are there config parms required?

The the smart-slot unit is hooked to an SNMP/WEB card (and works through SNMP 
which isn't a fair compare) -- so I can't really test compare the two right now 
-- but I thought I'd ask before I go through all the tinkering.



As a quick update, the 't' and 'h' commands work via serial terminal returning 
local temp/humidity for the cabled module just like they do for the SmartSlot 
card.


So the question is "how to enable".

Thanks,

 -Ben




___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

[Nut-upsuser] APC Measure UPS support

[Ben Kamen]

Hey all,

 I have a measure-UPS card and the external cabled module.

They're supposed to operate the same... does NUT auto detect them when using 
the apcsmart driver or are there config parms required?

The the smart-slot unit is hooked to an SNMP/WEB card (and works through SNMP 
which isn't a fair compare) -- so I can't really test compare the two right now 
-- but I thought I'd ask before I go through all the tinkering.

Thanks,

 -Ben  



___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser