Cyber Power Systems - CP850PFCLCD - Working

[Yatti420]

Any usb connection issues or anything bad logged?

Sent from my SGH-I257M using Tapatalk 2

 

[scurrier]

So far, no messages in the main log. I'm talking about the log that is shown at the bottom of the browser window when logged in.

I searched the log after startup for "nut", "ups", and "cyber" (which is in the name of my ups) and didn't come up with anything.

If I notice anything strange I'll try to remember to report back.

I'm really liking this UPS. I'm impressed by all of the things you can get it to display. Estimated time, input volts, output volts, VA, percentages of capacity, load, etc. Really nice. If you hold down the display button for 2 seconds you can get the display to stay on, which I prefer.

I saw some discussion in this forum a while back about issues with UPSs intentionally resetting themselves (by design) after power was restored and causing an improper shutdown on their attached systems. It was counter-intuitive behavior that people didn't expect but that had a semi-reasonable explanation. I need to figure out if this affects me. For now, I am just turning the UPS off and then back on after I restore power when I test it. I'll do the same when the inevitable real outage occurs.

 

[scurrier]

Darn, you cursed me. I figured I would check again so that you could have good information that it wasnt happening to me. But I just checked and about 50 minutes ago I got the "data for ups xxx is stale" message followed the next second by "ups xxx data is no longer stale."

Last it happened was at 4pm every 10 min or so. Then it was cool until 10:20pm. Not sure what's up. I should probably test the functionality again and make sure it's OK.

 

[Yatti420]

I dont believe it is an issue however.. It's more of an annoyance.. What disturbs me is why my 850 has zero issues.. Do they have different product revisions.. USB controller or something? I never gave mine a good look.. It's suppose to be an easy device to use.. Maybe the risk of choosing a Cyberpower.. It was my first UPS and very happy with it so far.. Can you see the info via upsd command "upsc ups"

Edit: I can't remember if these UPS support serial connection but I haven't tested it or know if it would cure stale data messages..

 

[scurrier]

I just tested it again and it still works fine. I'm not going to worry about it. I'm very happy with the apparent quality of this UPS.

 

[SweetAndLow]

Started debugging the driver. So far nothing is jumping out at me. It does query very frequently i think.

Code:

[root@FreeNAS] ~# /usr/local/libexec/nut/usbhid-ups -DDDDD -a ups
Network UPS Tools - Generic HID driver 0.38 (2.7.1)
USB communication driver 0.32
  0.000000    send_to_all: SETINFO driver.parameter.port "auto"
  0.000016    debug level is '5'
  0.000287    upsdrv_initups...
  2.298182    Checking device (0764/0501) (/dev/usb//dev/ugen1.5)
  6.296927    - VendorID: 0764
  6.296933    - ProductID: 0501
  6.296935    - Manufacturer: CP1000PFCLCD
  6.296937    - Product: CRDA103.981
  6.296939    - Serial Number: CPS
  6.296941    - Bus: /dev/usb
  6.296942    Trying to match device
  6.296953    Device matches
  6.300061    HID descriptor, method 1: (9 bytes) => 09 21 10 01 21 01 22 ac 01
  6.300066    i=0, extra=09, extra[i+1]=21
  6.300070    HID descriptor, method 2: (9 bytes) => 09 21 10 01 21 01 22 ac 01
  6.300072    HID descriptor length 428
  6.300932    Report Descriptor size = 428
  6.300942    Report Descriptor: (428 bytes) => 05 84 09 04 a1 01 09 24 a1 00 85 01 09 fe
  6.300948      75 08 95 01 15 00 26 ff 00 b1 23 85 02 09 ff b1 23 85 03 05 85 09 89 b1 23
  6.300954      85 04 09 8f b1 23 85 05 09 8b b1 23 85 06 09 2c b1 23 85 07 75 08 95 06 09
  6.300960      83 09 8d 09 8e 09 8c 09 29 09 67 b1 23 85 08 75 08 95 01 65 00 09 66 81 23
  6.300966      09 66 b1 a3 09 68 75 10 27 ff ff 00 00 66 01 10 81 23 09 68 b1 a3 09 2a 26
  6.300972      58 02 81 23 09 2a b1 a2 85 09 75 08 26 ff 00 05 84 09 40 67 21 d1 f0 00 55
  6.300978      06 b1 23 85 0a 09 30 b1 a3 09 02 a1 02 65 00 55 00 85 0b 75 01 95 06 25 01
  6.300984      05 85 09 d0 09 44 09 45 09 42 09 46 09 43 81 23 09 d0 09 44 09 45 09 42 09
  6.300989      46 09 43 b1 a3 75 02 95 01 81 01 b1 01 c0 85 0c 05 84 09 5a 75 08 15 01 25
  6.300995      03 b1 a2 09 5a 81 22 85 0d 09 fd 15 00 26 ff 00 b1 23 c0 05 84 09 1a a1 00
  6.301001      85 0e 05 84 09 40 75 08 67 21 d1 f0 00 55 07 b1 23 85 0f 09 30 b1 a3 85 10
  6.301007      75 10 09 53 15 4e 25 58 b1 a2 09 53 81 23 09 54 16 88 00 26 8e 00 b1 a2 09
  6.301013      54 81 23 c0 09 1c a1 00 85 12 75 08 09 30 15 00 26 ff 00 b1 a3 65 00 55 00
  6.301018      85 13 09 35 b1 a3 85 14 09 58 25 06 b1 a2 09 58 81 22 85 15 09 57 75 10 15
  6.301024      ff 26 ff 7f 35 c4 47 c4 ff 1d 00 66 01 10 b1 a2 85 16 09 56 b1 a2 85 17 09
  6.301030      6e 75 01 15 00 25 01 35 00 45 00 65 00 b1 a3 09 65 b1 a3 75 06 b1 01 85 18
  6.301036      75 10 09 44 26 84 03 66 21 d1 55 07 b1 a3 85 1a 06 01 ff 65 00 55 00 75 08
  6.301040      15 00 25 02 09 43 b1 a2 09 43 81 23 c0 c0
  6.301089    Using subdriver: CyberPower HID 0.3
  6.301094    Entering libusb_get_report
  6.301306    Report[get]: (2 bytes) => 01 01
  6.301309    PhyMax = 0, PhyMin = 0, LogMax = 255, LogMin = 0
  6.301312    Unit = 00000000, UnitExp = 0
  6.301313    Exponent = 0
  6.301316    hid_lookup_path: 00840004 -> UPS
  6.301318    hid_lookup_path: 00840024 -> PowerSummary
  6.301321    hid_lookup_path: 008400fe -> iProduct
  6.301324    Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 1
  6.301325    Entering libusb_get_report
  6.301551    Report[get]: (2 bytes) => 02 02
  6.301554    PhyMax = 0, PhyMin = 0, LogMax = 255, LogMin = 0
  6.301556    Unit = 00000000, UnitExp = 0
  6.301557    Exponent = 0
  6.301559    hid_lookup_path: 00840004 -> UPS
  6.301562    hid_lookup_path: 00840024 -> PowerSummary
  6.301564    hid_lookup_path: 008400ff -> iSerialNumber
  6.301566    Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID: 0x02, Offset: 0, Size: 8, Value: 2
  6.301568    Entering libusb_get_report
  6.301800    Report[get]: (2 bytes) => 03 04

The upsdrv_updateinfo --> libusb_get_interupt: Connection timed out seems strange though.

Code:

Exponent = 0
   5.246983     Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature, ReportID: 0x0c, Offset: 0, Size: 8, Value: 2
   5.246985     send_to_all: ADDCMD beeper.mute
   5.246990     send_to_all: ADDCMD load.off
   5.246993     send_to_all: ADDCMD load.on
   5.246997     send_to_all: ADDCMD shutdown.return
   5.247000     send_to_all: ADDCMD shutdown.stayoff
   5.247003     send_to_all: SETINFO device.type "ups"
   5.247006     send_to_all: SETINFO driver.version "2.7.1"
   5.247009     send_to_all: SETINFO driver.version.internal "0.38"
   5.247012     send_to_all: SETINFO driver.name "usbhid-ups"
   5.247014     upsdrv_initinfo...
   5.247017     send_to_all: SETINFO driver.version.data "CyberPower HID 0.3"
   5.247020     send_to_all: SETINFO driver.parameter.pollfreq "30"
   5.247022     upsdrv_updateinfo...
   5.493482     libusb_get_interrupt: Connection timed out
   5.493487     Got 0 HID objects...
   5.493490     Quick update...
   5.493493     Report[buf]: (3 bytes) => 16 ff ff
   5.493495     PhyMax = 1966020, PhyMin = -60, LogMax = 32767, LogMin = -1
   5.493497     Unit = 00001001, UnitExp = 0
   5.493498     Exponent = 0

 

[clicq]

You know, I wonder if the problem isn't the UPS itself, but the USB controller on the motherboard. SweetAndLow and I both have the ASRock E3C226D2I with the Intel C226 chipset, while scurrier has a motherboard with the Intel C222 chipset. Yatti420 has a motherboard with the Intel C202 chipset, which is a generation behind the C226 and C222 (and doesn't have USB 3 onboard, though I'm personally using a USB 2 port).

 

[SweetAndLow]

So i have a fix/work around to get things working properly. I had tried the MAXAGE thing but couldn't get the config loaded properly but someone else on the forum was using service nut stop/start and that actually loads the config properly.
1. services nut stop
2. mount -ur /
3. echo "MAXAGE 25" >> /usr/local/etc/nut/upsd.conf
4. mount -uw /
5. services nut start
6. ps auxw | grep ups # validate that the driver usbhid-ups started successfully.

 

[Yatti420]

Good job witb the fix!.. This should apply to the 1000va and above..

 

[SweetAndLow]

o well the fix isn't specific to my ups(1000cpflcd). What is happening is the driver isn't updating fast enough for upsd. upsd thinks the driver is gone and marks it as stale(default 15). Changing MAXAGE just tells upsd to wait a little longer before marking the ups as stale. This fix won't survive a reboot or bouncing the ups processes. So i have made a feature request bug to get upsd.conf configurability in the web ui(Feature #5046).

 

[cyberjock]

Interesting theory SweetAndLow. Please add a link to the thread you are referring to. I'd provide the link but I don't have it handy.

 

[Yatti420]

This should fix the pfclcd cyber power boxes.. The models (higher capacity) above mine..

 

[budmannxx]

Pretty sure this is the other thread:

http://forums.freenas.org/index.php?threads/20898/

SweetAndLow posted links to the relevant tickets there.

 

[DearestDreamer]

Thanks man. I decided on the 1350 model so I'll let everyone know how it works out.

I've got that exact same model, but whenever I run "upsc ups" I get "Connection failure: connection refused". I'm also using the 1000CFPL driver like everyone else. Did you do anything special to get yours working? I know mine worked with Cyberpower's windows utility. Removing it from the usb shows "/dev/ugen1.3: <CPS> at usb (disconnected)" so I suppose Freenas can see it?

X10SRL-F, Freenas 9.3.1-STABLE and I tried pretty much all USB ports on the chassis. upsd.conf simply shows:

LISTEN 127.0.0.1

I thought I had read everything and all but.. since I'm using the tree view on the left in FreeNAS, instead of the top tabs, I never saw that I had to enable a switch on the "Services" tab specifically. Oh boy

Works flawlessly now, awesome.

EDIT: While I tested the shutdown procedure, I experienced a power outage yesterday and everything shut down properly. I rebooted my system and none of the jails which had services running that were in the middle of writing experienced any problems. It's really great, I'm so glad this worked out in a real world scenario without any issues. I highly recommend everyone set it up, because it just saved me!

 

[Yatti420]

Good to hear..

 

[bodriye]

Why are battery voltages changed in your configs?
24V is the default but in Yatti420's config he overrides it with 12V. I am a little confused.

Code:

battery.voltage: 24.0		 
battery.voltage.nominal: 24

I looked at battery specs for cp850pfclcd:

Code:

Battery Size 12V/8.5Ah

for cp1000pfclcd:

Code:

Battery Size 12V/9Ah

it seems both batteries are 12V so default config of 24V is odd if battery.voltage signifies the battery size.

 

[Bidule0hm]

If the UPS needs two batteries then it's normal.

 

[bodriye]

If the UPS needs two batteries then it's normal.

The UPS has one battery. I posted battery size for 2 UPS models. cp1000pfclcd is the one you select in options for cp850pfclcd to work.