Re: [Nut-upsuser] nutdrv_atcl_usb

2015-03-11 Thread Jakub Scepka
Would you be so kind and provide some examples (commands), please?
I would run them today in the evening and report back with the logs.
Thank you.

Jakub S.


On Tue, Mar 10, 2015 at 11:44 PM, hyo...@gmail.com hyo...@gmail.com wrote:

 mmh.. it looks like someone forgot to hit 'reply all'.

 - relaying the originally attached files (gzipped, minus the two
 screenshots, to keep size down).

 2015-03-09 23:20 GMT+01:00 Jakub Scepka (private) jakub.sce...@gmail.com
 :
  Hi everyone!
 
  Here is summary for our fellows wit the same/similar UPS to save them 3
  weeks of life :)
 
  First of all I'm running Ubuntu 14.10 (Utopic) on a normal laptop (not
  VirtualMachine!) and I had to download the source from:
 
  https://github.com/zykh/nut/tree/nutdrv_qx-fuji  (Thank you Charles)
 
 
  #sudo apt-get remove nut
  #sudo su
  #apt-get install autoconf
  #apt-get install libtool
  #apt-get install libusb-dev
 
  #./configure --without-ssl --with-usb --with-user=nut --with-group=nut
  #make
  #make install
 
 
  #lsusb -vvv -d 0001:
 
  (see attached lsusb.log)
 
 
 
  Content of ups.conf:
 
  [ups]
  driver=nutdrv_qx
  protocol=megatec
  subdriver=fuji
  port=auto
  vendorid=0001
  productid=
 
 
  #/usr/local/ups/bin$ sudo ./nutdrv_qx -a ups -D
  (see attached log.log)
  - I have tried to pull the plug
  - reinsert / reconnect it (220V)
  - poweroff the UPS (by button)
  - and power on (by button)
 
  #/usr/local/ups/sbin$ sudo ./upsdrvctl start
  Network UPS Tools - UPS driver controller 2.7.2.5
  Network UPS Tools - Generic Q* USB/Serial driver 0.13 (2.7.2.5)
  USB communication driver 0.32
  Using protocol: Megatec 0.02
  No values for battery high/low voltages
  Using 'guesstimation' (low: 31.20, high: 39.00)!
  Battery runtime will not be calculated (runtimecal not set)
 
  # /usr/local/ups/sbin$ sudo ./upsd
  Network UPS Tools upsd 2.7.2.5
  fopen /var/state/ups/upsd.pid: No such file or directory
  listening on 0.0.0.0 port 3493
  Connected to UPS [ups]: nutdrv_qx-ups
 
 
  NUT monitor (GUI):
  see screenshot3.png
  and screenshot4.png
  I have tested (and it worked like a charm):
  - beeper.toggle
  - test.battery.start
  - test.battery.stop
 
  THANKS TO ALL OF YOU PEOPLE
 
  --
  Originally my planes were to install NUT on a router (DD-WRT/Tomato) or
 on
  QNAP NAS (ARM arch.) but packages for these devices are too old and I
 don't
  know (so far) anything about compiling on/for these devices.
  My next logical step was to install Debian Virtual Machine on ESX server
 and
  compile NUT on it.
  But, this setup suddenly didn't worked, I blame ESX USB passthrought, or
  maybe I'm missing something else... Who knows... :)
 
  See nutdrv_qx_5xD.txt (commands: ./nutdrv_qx -a ups -D and
 ./nutdrv_qx
  -a ups -D -u root)
  or debianVM.txt (command: lsusb)
  if you are interested...
  It look similar to this:
  http://comments.gmane.org/gmane.comp.monitoring.nut.user/8970
  --
 
 
  BR
 
  Jakub
 
 
 
 
  On 09.03.2015 16:27, hyo...@gmail.com wrote:
 
  Nice!
  By the way, to avoid the initial protocol autodetection procedure and
  to speed up the startup, you should set 'protocol=megatec'.
  Do the various instant commands seem to work? Can you test them all
  and report back the logs (a debug level of 5 should be enough)?
  Also, what's the output of 'lsusb -vvv -d 0001:' (as root)?
 
 

 So far, so good!
 However, I need a little more testing before I can merge this into master.

 If possible, I'd like you to test and report back the logs (still with
 a debug level of 5) of:
 - shutdown.stayoff with ups.delay.shutdown set to 30 seconds;
 - shutdown.stayoff with ups.delay.shutdown set to 60 seconds;
 - shutdown.return with ups.delay.shutdown set to 30 seconds and
 ups.delay.start set to 60 seconds;
 - shutdown.return with ups.delay.shutdown set to 30 seconds and
 ups.delay.start set to 0 seconds;
 - shutdown.return with ups.delay.shutdown set to 60 seconds and
 ups.delay.start set to 60 seconds;
 - shutdown.return with ups.delay.shutdown set to 60 seconds and
 ups.delay.start set to 0 seconds;
 - shutdown.stop executed after one of the previous commands (while
 ups.delay.shutdown elapses);
 - load.on executed after one of the previous shutdowns (after a
 successful shutdown.stayoff or while ups.delay.start elapses);
 - load.off and then load.on.

 Thanks in advance for your patience.

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

Re: [Nut-upsuser] Fwd: Data stale error after short while

2015-03-09 Thread Jakub Scepka
I just would like to confirm that I face very similar issue when I want to
connect UPS to VM machine (on ESX server). I blame VmWare USB passthrough.


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


Re: [Nut-upsuser] nutdrv_atcl_usb

2015-03-06 Thread Jakub Scepka
Suddenly yes, I also ended with Communications with UPS lost: Query to UPS
failed (on Ubuntu 14.10)
and have tried everything in this thread.

Mine is called EUROCASE - UPS EA200N 2000VA, 2000VA, line interactive
it looks exactly as EAST UPS - Pure Sine Wave UPS with LCD Display 2000VA
or even brand Vivaldi.

I would say is the same hardware with different branding.

Mine is shipped with windows software UPSmart2000I
EAST uses UPSmart (name is very similar too).

It would be nice to try EAST UPS (windows) software with my UPS, to make
sure is the same HW.

I didnt tried yet nutdrv_qx-fuji

BR

Jakub








On Thu, Mar 5, 2015 at 5:08 PM, Charles Lepple clep...@gmail.com wrote:

 On Mar 5, 2015, at 2:34 AM, Jakub jakub.sce...@gmail.com wrote:

  Come on, it started to be interesting!

 Do you have one of these UPSes?

 If so, here was Dan's email about a branch to test:

  If you still can't get it to work with nutdrv_atcl_usb, another
  approach could be worth considering.
 
  Since this UPS seems to be supported by UPSmart2000I, it could use a
  serial-over-usb implementation of the megatec protocol.
 
  A very first early version of the nutdrv_qx driver that should support
  it can be found here:
  https://github.com/zykh/nut/tree/nutdrv_qx-fuji
 
  (USB subdriver 'fuji'; but it shouldn't be necessary to set it, as the
  driver is expected to automatically select it according to the
  iManufacturer/iProduct strings)
 
  Note that the user I first developed it for abruptly stopped replying
  to my mails (maybe his UPS went boom.. who knows?), so I don't really
  know if it works or not: quite a lot of testing may be needed.

 --
 Charles Lepple
 clepple@gmail




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