[Nut-upsdev] Cpsups driver with a CyberPower OP1000E

[Arjen de Korte]

>>Could you try again with the latest revision from the trunk?
> Sure, works like a charm now:
> # drivers/powerpanel -a myups -DDD
> Network UPS Tools -  CyberPower text protocol UPS driver 0.11 (2.1.0)
> Warning: This is an experimental driver.
> Some features may not function correctly.
>
> debug level is '3'
> command:
> reply  : <none>
> warning: sent "\r", expected "#2\r" but got ""command: P4

Hmmm, it seems I forgot a newline somewhere. I (wrongly) assumed that
using upsdebugx might flood the logs, but that isn't the case when running
in the foreground, so we'll go back to using upslogx.

> reply  : (46 bytes) => 23 31 30 30 30 56 41 20 20 20 20 2c 32 2e 31 30 32
> 2c 30 30 30 30 30 30 30 30 30 30 30 30 2c 43 59 42 45 52 20 50 4f 57 45 52
> 20 20 20 20
> Detected CYBER POWER     1000VA     on /dev/ttyUSB0

Good!

> command: P3
> reply  : <none>

Your UPS doesn't support listing the battery information. That's OK, we
don't really need that anyway.

> command: P2
> reply  : (22 bytes) => 23 31 30 30 30 2c 30 37 30 30 2c 32 33 30 2c 30 34
> 37 2c 30 36 33

Looks fine.

> command: P1
> reply  : (15 bytes) => 23 32 33 30 2c 32 37 30 2c 31 38 30 2c 32 30

Same here.

> command: P6
> reply  : (40 bytes) => 23 32 36 32 2c 32 36 34 2c 32 36 36 2c 32 36 38 2c
> 32 37 30 2c 32 37 32 2c 32 37 34 2c 32 37 36 2c 32 37 38 2c 32 38 30

Setting the "input.transfer.high" seems to be possible...

> command: P7
> reply  : (40 bytes) => 23 31 37 30 2c 31 37 32 2c 31 37 34 2c 31 37 36 2c
> 31 37 38 2c 31 38 30 2c 31 38 32 2c 31 38 34 2c 31 38 36 2c 31 38 38

...and "input.transfer.low" too. Fine!

> command: P8
> reply  : <none>

That could be expected, it isn't possible to set the low battery warning
level. Not surprisingly, since it also doesn't list battery parameters.
Again, not a problem.

> command: D
> reply  : (34 bytes) => 23 49 32 33 31 2e 30 4f 32 33 31 2e 30 4c 30 32 38
> 42 31 30 30 54 30 33 39 46 30 34 39 2e 39 53 90 80

Status looks like what we expect.

> command: C
> reply  : <none>

Cancelling a pending shutdown is not supported. No problem.

> command: D
> reply  : (34 bytes) => 23 49 32 33 31 2e 30 4f 32 33 31 2e 30 4c 30 32 38
> 42 31 30 30 54 30 33 39 46 30 34 39 2e 39 53 90 80

No change in the status.

Looking at the output of upsc, we could remove some leading zero's on a
few values. I'll patch that up later today.

Best regards, Arjen