Re: [Nut-upsuser] Cyberpower PR2200ELCDRT2U

2017-11-10 Thread Charles Lepple 
[please use reply-all to include the list. thanks!]

> On Nov 9, 2017, at 9:19 PM, Christoph Lampl  wrote:
> 
> Hey guys, :)
>  
> recently, I installed Cyberpower PR2200ELCDRT2U, however, I have not managed 
> to get this UPS working with FreeNAS 11, yet.
>  
> According to compatibility list, PR2200 should work fine, when using 
> powerpanel driver:
> http://networkupstools.org/ddl/Cyber_Power_Systems/
> http://networkupstools.org/ddl/Cyber_Power_Systems/PR2200.html

Looking at the PR6000LCD... entry, it looks like PR*LCD models might be 
different than the older PR* ones.

What do you get from "sudo usbconfig dump_device_desc"? (You can trim any 
non-UPS data - I'm mostly interested in idVendor and idProduct. Also, if you 
don't want to share the full serial number, it would be good to know how many 
characters there are.)

I suspect this UPS will work with the usbhid-ups driver, or if not, it can be 
made to work with minor NUT configuration changes. I forget how you choose a 
"generic" USB connection in FreeNAS - maybe someone else can chime in on that 
point?

> However, when trying to establish a connection between battery and FreeNAS 
> Server, either using usb cable or serial cable, I receive the same error 
> messages in the console of FreeNAS:
>  
> Nov 10 03:01:37 storageunit root: /usr/local/etc/rc.d/nut: WARNING: failed 
> precmd routine for nut

^ This command probably indicates that the NUT driver failed to start, so the 
NUT upsd process probably will not start, either.

> Nov 10 03:01:37 storageunit upsmon[8817]: UPS [PR2200ELCDRT2U]: connect 
> failed: Connection failure: Connection refused
> Nov 10 03:01:37 storageunit upsmon[8817]: Communications with UPS 
> PR2200ELCDRT2U lost

^ upsmon "Connection refused" errors (on FreeNAS, or other connections to 
localhost) are usually a consequence of upsd not starting, so this should 
resolve itself once you can get the driver running.

> I tried connecting to PR2200 using a Laptop with preinstalled Cyberpower 
> Personal Edition. Everything is working fine at this point and the software 
> displays battery details correctly! However, as soon as I try to establish a 
> connection between FreeNAS and Cyberpower PR2200, I receive these error 
> messages. I spent many hours in reconfiguring and trying new/different ports, 
> however, it looks like I’m going in the wrong direction, because I can’t get 
> this battery communicating with FreeNAS correctly.

I doubt this will be an issue here, but I would recommend choosing the port you 
want to ultimately use (serial, USB, network) and making sure that it still 
works with Cyberpower's software before switching to NUT. Some older UPSes (and 
likely not even from Cyberpower) did not deal well with switching between 
ports, and required a power cycle to switch.

> 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

Thanks!


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

Re: [Nut-upsuser] Cyberpower PR2200ELCDRT2U

2017-11-10 Thread Christoph Lampl 
Dear Charles,

thanks for your quick answer and your information! I didn't know there is a 
difference in the PR-series between old and new. So thanks for this valuable 
information!

usbconfig dump_device_desc shows:

ugen0.2:  at usbus0, cfg=0 md=HOST spd=LOW 
(1.5Mbps) pwr=ON (50mA)   


  bLength = 0x0012  

  bDescriptorType = 0x0001  

  bcdUSB = 0x0110   

  bDeviceClass = 0x  

  bDeviceSubClass = 0x  

  bDeviceProtocol = 0x  

  bMaxPacketSize0 = 0x0008  

  idVendor = 0x0764 

  idProduct = 0x0601

  bcdDevice = 0x0200

  iManufacturer = 0x0003

  iProduct = 0x0001   

  iSerialNumber = 0x 

  bNumConfigurations = 0x0001

Right now, I selected " Cyber Power Systems ups 3 OR2200LCDRM2U USB 
(usbhid-ups)" in the dropdown menu, in order to shift away from 
powerpanel-driver to usbhid-driver.

However, when choosing this driver, freenas shows this log:

Nov 10 23:04:45 storageunit upsd[17599]: mainloop: Interrupted system call
Nov 10 23:04:45 storageunit upsmon[17621]: upsmon parent: read

I guess, interrupted system call shows up, because FreeNAS is already trying to 
"read" a response from the battery from the previous attempt, however is still 
waiting? So, basically, the output is "upsmon parent: read"... however, this is 
all and there is no further output. But I think, there should be further 
output, shouldn't it? (some sort like "link established successfully").

Meanwhile I tried connecting the UPS PR2200ELCDRT2U to pfSense system. However, 
I'm receiving the same error there, too.

Nov 10 13:59:45   upsmon   49323   Poll UPS 
[PR2200ELCDRT2U] failed - Driver not connected
Nov 10 13:59:40   upsmon   49323   UPS PR2200ELCDRT2U 
is unavailable
Nov 10 13:59:40   upsmon   49323   Poll UPS 
[PR2200ELCDRT2U] failed - Driver not connected
Nov 10 13:59:35   upsmon   49323   Communications with 
UPS PR2200ELCDRT2U lost
Nov 10 13:59:35   upsmon   49323   Poll UPS 
[PR2200ELCDRT2U] failed - Driver not connected
Nov 10 13:59:35   upsd  49831   User monuser@127.0.0.1 logged 
into UPS [PR2200ELCDRT2U]
Nov 10 13:59:33   upsd  49831   Startup successful
Nov 10 13:59:33   upsd  49649   Can't connect to UPS 
[PR2200ELCDRT2U] (usbhid-ups-PR2200ELCDRT2U): No such file or directory

(newest entry is at top)

In pfSense, there was no option to select "powerpanel" as driver, so I *had* to 
use usbhid. I think it shows the same result like freenas. It is trying to 
establish a link, however, it gets refused immediately.

So, back to FreeNAS, after selecting usbhid as driver, I ran following commands 
from shell:

- upsc PR2200ELCDRT2U@localhost
- upscmd -l PR2200ELCDRT2U
- upsrw PR2200ELCDRT2U@localhost

  

And here ist he output:

---

upsc PR2200ELCDRT2U@localhost   
  
battery.charge: 100 

battery.charge.low: 35

Re: [Nut-upsuser] Cyberpower PR2200ELCDRT2U

2017-11-10 Thread 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] Problems in communication with Mustek PowerMust 1060 LCD

2017-11-10 Thread Manuel Wolfshant 

On 10/30/2017 03:19 PM, Alexa Catalin wrote:

System: Cenots Linux 6.9
Application: nut-2.7.5-0.20170613gitb1314c6  [with usb 0.1 from distro]
Device:  Mustek PowerMust 1060 LCD
Comunication log file: dump.txt

We are looking at the possibility of successful communicating with 
this device UPS Mustek PowerMust 1060 LCD.


PS: wolfy on the list gives me assistance and i can install any new 
compiled nut version from sources.



Hi list

Anyone with ideas on this one ? It looks like the driver communicates 
with the device but something is amiss.. and I am not at all familiar 
with the code so I cannot fiddle with it.


    wolfy




Thanks,
Catalin.

dump.txt


0.00[D1] debug level is '3'
0.004826[D2] Checking device (0665/5161) (001/003)
2.004392[D2] - VendorID: 0665
2.004420[D2] - ProductID: 5161
2.004532[D2] - Manufacturer: unknown
2.004541[D2] - Product: unknown
2.004550[D2] - Serial Number: unknown
2.004558[D2] - Bus: 001
2.004567[D2] - Device release number: 0002
2.004575[D2] Trying to match device
2.004619[D2] Device matches
2.004648[D3] nut_usb_set_altinterface: skipped 
usb_set_altinterface(udev, 0)
2.004679[D2] Skipping megatec protocol...
2.004689[D2] Trying mustek protocol...
2.731556[D3] send: QS
2.737382[D3] read: (229.7 231.6 229.7 023 50.1 27.5 --.- 1001
2.737456[D2] blazer_status: non numerical value [--.-]
2.737477[D2] Status read in 1 tries
2.737486Supported UPS detected with mustek protocol
7.737351[D3] send: error sending control message: Connection timed out
7.737382[D2] blazer_rating: short reply
7.737483[D1] Rating read 1 failed
   12.737303[D3] send: error sending control message: Connection timed out
   12.737347[D2] blazer_rating: short reply
   12.739509[D1] Rating read 2 failed
   13.019570[D3] send: F
   13.025314[D3] read: (231.7 229.7 231.6 023 50.1 27.5 --.- 1001
   13.025344[D2] blazer_rating: invalid start character [28]
   13.025359[D1] Rating read 3 failed
   13.025368Rating information unavailable
   13.025378No values provided for battery high/low voltages in ups.conf

   13.025398Using 'guestimation' (low: -0.87, high: -1.08)!
   13.025408Battery runtime will not be calculated (runtimecal not set)
   18.025409[D3] send: error sending control message: Connection timed out
   18.025529[D2] blazer_status: short reply
   18.026837[D1] Communications with UPS lost: status read failed!
   18.027010[D2] dstate_init: sock /var/run/nut/blazer_usb-serverups open 
on fd 5
   23.026403[D3] send: error sending control message: Connection timed out
   23.026442[D2] blazer_status: short reply
   23.026453[D1] Communications with UPS lost: status read failed!
   23.197877[D3] send: QS
   23.202242[D3] read: #230.0 004 24.00 50.0
   23.202271[D2] blazer_status: short reply
   23.202281[D1] Communications with UPS lost: status read failed!
   30.028309[D3] send: error sending control message: Connection timed out
   30.028341[D2] blazer_status: short reply
   30.028351Communications with UPS lost: status read failed!
   33.482321[D3] send: QS
   33.488175[D3] read: (231.6 229.7 229.7 022 50.1 27.5 --.- 1001
   33.488232[D2] blazer_status: non numerical value [--.-]
   33.488249Communications with UPS re-established
   38.488260[D3] send: error sending control message: Connection timed out
   38.518540[D2] blazer_status: short reply
   38.518560[D1] Communications with UPS lost: status read failed!
   43.518381[D3] send: error sending control message: Connection timed out
   43.518421[D2] blazer_status: short reply
   43.518433[D1] Communications with UPS lost: status read failed!
   43.770366[D3] send: QS
   43.776087[D3] read: (229.7 229.7 229.7 023 50.1 27.5 --.- 1001
   43.776150[D2] blazer_status: non numerical value [--.-]
   50.520298[D3] send: error sending control message: Connection timed out
   50.520333[D2] blazer_status: short reply
   50.520345[D1] Communications with UPS lost: status read failed!
   54.056946[D3] send: QS
   54.063021[D3] read: (229.7 229.7 229.7 023 50.1 27.5 --.- 1001
   54.063073[D2] blazer_status: non numerical value [--.-]
   59.062382[D3] send: error sending control message: Connection timed out
   59.062417[D2] blazer_status: short reply
   59.062429[D1] Communications with UPS lost: status read failed!
   64.062323[D3] send: error sending control message: Connection timed out
   64.062360[D2] blazer_status: short reply
   64.062372[D1] Communications with UPS lost: status read failed!
   64.345607[D3] send: QS
   64.352967[D3] read: (229.7 229.7 229.7 023 50.1 27.5 --.- 1001
   64.353017[D2] blazer_status: non numerical value