Displaying 17 results from an estimated 17 matches for "cp1000avrlcd".
2010 Mar 12
2
2.4.1 Voltages are Great for CP1000AVRLCD, but usbfs messages in logs (a lot)
...hanges to where the monitor lines go in the configs
and changes from ACCEPT, etc.. to LISTEN are fairly old now, the documentation
for setting up monitoring for multiple UPSs isn't that clear. (I may not have it
100% correct either - see 3 below). In my case, I have 2 server each with
identical CP1000AVRLCD upses where I simply want each to server as the master
for the machine they are attached to, but be able to monitor both from each
machine.
Third, each machine has identical configs (accept for swapping the master/slave
designations and IP addresses in the LISTEN lines). I have it working with th...
2008 Nov 26
1
Battery Volts shown as 20+ on Cyber Power UPS CP1000AVRLCD
Nut Developers,
I have unsuccessfully tried to solve a problem with the voltage value on my
Cyber Power UPS CP1000AVRLCD. Something is wrong with the battery voltage
calculation. It always reads around 20 volts with that's nuts (pardon the pun).
Right now:
battery.voltage : 20.3
You can take a look for yourself at http://www.3111skyline.com/nutindex.html
Is there a parameter I can check or adjust to get the...
2015 Jun 26
2
Driver macosx-ups failing on Yosemite
OSX Yosemite 10.10.3
Nut version 2.6.5
Installed via Macports
Device is Cyberpower CP1000AVRLCD
Device is visible and is monitored in the OSX control panel
Error-
macosx-ups -DD -a cyberpower
Network UPS Tools - Mac OS X UPS meta-driver 1.0 (2.6.5-Unversioned directory)
Warning: This is an experimental driver.
Some features may not function correctly.
0.000000 debug level is '2'...
2008 Dec 04
1
Battery Volts shown as 20+ on Cyber Power UPS CP1000AVRLCD [ DATA ]
Citeren "David C. Rankin" <drankinatty at suddenlinkmail.com>:
> Discharged battery.voltage:
>
> 17.4 Volts - (indicated on shutdown, discharging battery.charge 77%)
> 16.9 Volts - (indicated on shutdown, discharging battery.charge 51%%)
> 16.6 Volts - (indicated on shutdown, discharging battery.charge 33%)
>
> -- Shutdown Occurred at < 3% -- Battery
2011 Jul 27
1
Same Box, Moved install to different drive, now get Connection failure: Connection refused??
...driver.version.data: CyberPower HID 0.2
driver.version.internal: 0.34
input.transfer.high: 140
input.transfer.low: 90
input.voltage: 114.0
input.voltage.nominal: 120
output.voltage: 114.0
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.load: 22
ups.mfr: CPS
ups.model: UPS CP1000AVRLCD
ups.productid: 0501
ups.realpower.nominal: 88
ups.status: OL
ups.test.result: Done and warning
ups.timer.shutdown: -60
ups.timer.start: 0
ups.vendorid: 0764
but on the other box, I get 'connection refused' errors with upsc. What part of
the puzzle am I missing? I know this is a forest-for...
2015 Jun 27
2
Driver macosx-ups failing on Yosemite
...On Jun 26, 2015, at 9:25 PM, Charles Lepple <clepple at gmail.com> wrote:
>
> On Jun 26, 2015, at 8:35 AM, Sundeep Mediratta <smedius at gmail.com> wrote:
>
>> OSX Yosemite 10.10.3
>> Nut version 2.6.5
>> Installed via Macports
>> Device is Cyberpower CP1000AVRLCD
>> Device is visible and is monitored in the OSX control panel
>>
>> Error-
>>
>> macosx-ups -DD -a cyberpower
>
> Can you please increase the debug level to -DDD?
>
> --
> Charles Lepple
> clepple at gmail
sudo macosx-ups -DDDD -a cyberpower
N...
2015 Jun 27
4
Driver macosx-ups failing on Yosemite
On Jun 27, 2015, at 9:17 AM, Charles Lepple <clepple at gmail.com> wrote:
> On Jun 26, 2015, at 11:07 PM, Sundeep Mediratta <smedius at gmail.com> wrote:
>
>> 0.000233 upsdrv_initups(): Power Sources blob:
>> <CFArray 0x7ffd18605480 [0x7fff7443bed0]>{type = immutable, count = 1, values = (
>> 0 : <CFBasicHash 0x7ffd18605360 [0x7fff7443bed0]>{type
2013 Dec 14
2
Nut (git) upsdrvctl fails without "-u root start <upsname>", upsd fails on state file GID
...ix:~/pkg/bld/network-ups-tools-git> upsc phoinix_ups
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 20
battery.mfr.date: CPS
battery.runtime: 1050
battery.runtime.low: 300
battery.type: PbAcid
battery.voltage: 13.5
battery.voltage.nominal: 12
device.mfr: CPS
device.model: UPS CP1000AVRLCD
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/hiddev0
driver.version: 2.7.1-signed-9-g6fb35b3
driver.version.data: CyberPower HID 0.3
driver.version.internal: 0.38
input.transfer.high: 140
input.transfer.low: 90
i...
2015 Jun 27
0
Driver macosx-ups failing on Yosemite
On Jun 26, 2015, at 8:35 AM, Sundeep Mediratta <smedius at gmail.com> wrote:
> OSX Yosemite 10.10.3
> Nut version 2.6.5
> Installed via Macports
> Device is Cyberpower CP1000AVRLCD
> Device is visible and is monitored in the OSX control panel
>
> Error-
>
> macosx-ups -DD -a cyberpower
Can you please increase the debug level to -DDD?
--
Charles Lepple
clepple at gmail
2016 Dec 07
1
nut-git reporting 24 Volts with CP1350PFCLCD -- is that correct?
...n this thing). Also I woulds suspect 'battery.voltage' to
be 26.x if that was the case with new batteries. What say the nut experts? Is
this right? If not, what can I send you to help with the scaling? I recall
running tests and capturing data for Arjen 8-9 years ago with another
CyberPower CP1000AVRLCD that allowed the voltage to be set correctly. I don't
know if that is needed with this model as well. If so, let me know (and remind
me what you need -- it's been a while), and I'm happy to send it.
Note: https://github.com/networkupstools/nut/issues/140 referenced in FAQ 29
is NOT fix...
2013 Dec 15
0
Nut (git) upsdrvctl fails without "-u root start <upsname>", upsd fails on state file GID
On Dec 14, 2013, at 4:23 PM, David C. Rankin wrote:
> Do you know if the problem with upsdrvctl being able to probe/connect to the
> usb devices is the result of some default permission change in Linux in general.
> It seems to me that since nut used to work right out-of-the-box, then all/most
> distros must have had the default permissions on usb nodes set to 0666, where
>
2014 Aug 11
1
Cyberpower Value1200E might not need 0.667 battery scaling
...gt; /* USB IDs device table */
> static usb_device_id_t cps_usb_device_table[] = {
> - /* 900AVR/BC900D, CP1200AVR/BC1200D */
> + /* 900AVR/BC900D */
> { USB_DEVICE(CPS_VENDORID, 0x0005), NULL },
> - /* Dynex DX-800U? */
> + /* Dynex DX-800U?, CP1200AVR/BC1200D, CP825AVR-G, CP1000AVRLCD, CP1000PFCLCD, CP1500C, CP550HG, etc. */
> { USB_DEVICE(CPS_VENDORID, 0x0501), &cps_battery_scale },
> /* OR2200LCDRM2U, OR700LCDRM1U, PR6000LCDRTXL5U */
> { USB_DEVICE(CPS_VENDORID, 0x0601), NULL },
> @@ -59,12 +66,48 @@ static usb_device_id_t cps_usb_device_table[] = {
&g...
2014 Aug 09
0
Cyberpower Value1200E might not need 0.667 battery scaling
On Aug 8, 2014, at 9:15 AM, Charles Lepple <clepple at gmail.com> wrote:
> On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com> wrote:
>
>> On Aug 7, 2014, at 10:18 PM, Matthew Stapleton <matthew4196 at gmail.com> wrote:
>>
>>> I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut 2.7.2, it appears to report battery voltage
2008 Dec 20
2
Problems with nut on new openSuSE 11.1 (same ecstasy_ups)
Arjen,
I just installed openSuSE 11.1. I though it would be simple to setup the same
CyberPower CP1000AVRLCD on the same machine that we worked through the 20+
voltage issue with, but usbhis-ups driver is failing for some reason. I have
gotten the output I remember you needing from the last issue for you. What do
you think the problem might be? Here is the information:
First the logs from the install do...
2014 Aug 08
2
Cyberpower Value1200E might not need 0.667 battery scaling
On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com> wrote:
> On Aug 7, 2014, at 10:18 PM, Matthew Stapleton <matthew4196 at gmail.com> wrote:
>
>> I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut 2.7.2, it appears to report battery voltage too low due to the battery scaling function (In drivers/cps-hid.c). Even though the ups has usb id:
2013 Dec 14
2
Nut (git) upsdrvctl fails without "-u root start <upsname>", upsd fails on state file GID
On 12/14/2013 02:06 PM, David C. Rankin wrote:
> Charles,
>
> Setting uid:gid to root:nut on /dev/bus/usb/004/002 seemed to be the issue.
> The question now become how to automate this process so that the user isn't
> required to manually hunt down the usb dev and change gid to the nut gid? So
> far, either manually setting the gid or hand-rolling the udev files to do the
2013 Dec 15
2
Nut (git) upsdrvctl fails without "-u root start <upsname>", upsd fails on state file GID
...es/pci0000:00/0000:00:04.0/usb4/4-3':
ATTR{idVendor}=="0764"
ATTR{bcdDevice}=="0001"
ATTR{urbnum}=="161297"
ATTR{manufacturer}=="CPS"
ATTR{idProduct}=="0501"
ATTR{bDeviceClass}=="00"
ATTR{product}=="UPS CP1000AVRLCD"
looking at parent device '/devices/pci0000:00/0000:00:04.0/usb4':
ATTRS{idVendor}=="1d6b"
ATTRS{bcdDevice}=="0312"
ATTRS{serial}=="0000:00:04.0"
ATTRS{urbnum}=="35"
ATTRS{manufacturer}=="Linux 3.12.1-3-ARCH ohci_hcd&q...