On Apr 13, 2015, at 6:56 AM, Humberto Möckel hamber...@gmail.com wrote:
Hello again! I'm the guy from the blazer_usb shutdown problem the other day.
Now I moved on installing the system in another work PC with another kind of
rebranded UPS. This ups is a double battery 1000VA UPS brand.
Hello again! I'm the guy from the blazer_usb shutdown problem the other
day. Now I moved on installing the system in another work PC with another
kind of rebranded UPS. This ups is a double battery 1000VA UPS brand.
Device identifies itself as ATCL FOR USB on device description.
Blazer_usb seems
Thanks! Now merged into master, it'll be in the upcoming 2.7.3.
As icing on the cake, we'd appreciate a upsc/upsrw/upscmd dump for our own DDL:
http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/ddl/
https://github.com/networkupstools/nut-ddl
[attachments were 100kB; trimmed]
Begin forwarded message:
From: Jakub Scepka (private) jakub.sce...@gmail.com
Subject: Re: [Nut-upsuser] nutdrv_atcl_usb
Date: March 13, 2015 at 4:30:08 PM EDT
To: hyo...@gmail.com hyo...@gmail.com
Cc: nut-upsuser nut-upsuser@lists.alioth.debian.org
2015-03-11 14:21 GMT+01:00 Jakub Scepka jakub.sce...@gmail.com:
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.
First, be sure to have in upsd.users a valid entry to set vars and
execute instant commands:
2015-03-11 21:43 GMT+01:00 Jakub Scepka (private) jakub.sce...@gmail.com:
Thank you for the commands...
Please find attached log...
Looking at the log it seems that the only commands understood by the
UPS are the two shutdown.return with ups.delay.start=0.
If this is the case, I must confess I
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'.
-
2014-11-09 16:29 GMT+01:00 Charles Lepple clep...@gmail.com:
On Nov 8, 2014, at 7:01 PM, hyo...@gmail.com wrote:
Since this UPS seems to be supported by UPSmart2000I, it could use a
serial-over-usb implementation of the megatec protocol.
Dan, that is a good point - I had not considered it. I
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
On Mar 9, 2015, at 11:28 AM, hyo...@gmail.com wrote:
2014-11-09 16:29 GMT+01:00 Charles Lepple clep...@gmail.com:
On Nov 8, 2014, at 7:01 PM, hyo...@gmail.com wrote:
Since this UPS seems to be supported by UPSmart2000I, it could use a
serial-over-usb implementation of the megatec protocol.
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
It seems like it works (partially?) with NUT/driver you mentioned.
I will test it more when I return home.
root@Failure:/lib/nut# ./nutdrv_qx -a test -x subdriver=fuji -u root -x
productid= -x vendorid=0001 -DD
Network UPS Tools - Generic Q* USB/Serial driver 0.13 (2.7.2.5)
USB
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.
Come on, it started to be interesting!
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
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
On Nov 5, 2014, at 1:36 AM, jani jani.tali...@gmail.com wrote:
Ok, I installed a fresh Debian testing (jessie) onto a laptop to try making
sure it wasn't my current Ubuntu server causing the issue. Kernel is
3.16-3-686-pae #1 SMP Debian 3.16.5-1 (2014-10-10). The only thing installed
The output of the ldd command is:
root@minime:~# ldd /lib/nut/nutdrv_atcl_usb
linux-gate.so.1 (0xb7722000)
libusb-0.1.so.4 = /lib/i386-linux-gnu/libusb-0.1.so.4 (0xb76fe000)
libpthread.so.0 = /lib/i386-linux-gnu/i686/cmov/libpthread.so.0
(0xb76e2000)
libc.so.6 =
On Nov 5, 2014, at 4:39 PM, jani jani.tali...@gmail.com wrote:
The output of the ldd command is:
root@minime:~# ldd /lib/nut/nutdrv_atcl_usb
linux-gate.so.1 (0xb7722000)
libusb-0.1.so.4 = /lib/i386-linux-gnu/libusb-0.1.so.4 (0xb76fe000)
libpthread.so.0 =
For reference, here's the thread discussing the development of that driver:
http://news.gmane.org/find-root.php?message_id=52B4C54E.1050106%40ariwainer.com.ar
It seems to have worked under Kubuntu 13.10.___
Nut-upsuser mailing list
I'm running Ubuntu 14.04.1 LTS with kernel 3.13.0-39-generic x86_64. The
security mechanisms I haven't played with at all, and up until last week
nut was running just fine on an Eaton E series NV UPS with a USB connection
(from memory it used the blazer_usb driver). I installed the nut packages
Ok, I installed a fresh Debian testing (jessie) onto a laptop to try making
sure it wasn't my current Ubuntu server causing the issue. Kernel
is 3.16-3-686-pae #1 SMP Debian 3.16.5-1 (2014-10-10). The only thing
installed besides the stock debian desktop is nut.
The UPS still refuses to talk to
Hello again, I ran the commands again, checking to make sure the UPS was
still device 005/002, and the results is:
root@microserver:~# ls -l /dev/bus/usb/005/002
crw-rw-r-- 1 root nut 189, 513 Nov 4 12:55 /dev/bus/usb/005/002
I tried setting permissions of /dev/bus/usb/005/002 to 777 and
On Nov 3, 2014, at 9:01 PM, jani jani.tali...@gmail.com wrote:
Hello again, I ran the commands again, checking to make sure the UPS was
still device 005/002, and the results is:
root@microserver:~# ls -l /dev/bus/usb/005/002
crw-rw-r-- 1 root nut 189, 513 Nov 4 12:55 /dev/bus/usb/005/002
On Nov 1, 2014, at 1:30 AM, jani wrote:
Hi Charles,
I just bought a UPS that announces itself as 'ATCL FOR UPS' with VendorId of
0001. It seems to be a re-badged unit manufactured by Guangdong East Power
company, and besides the little brand stamp it looks identical to:
Hi Charles,
Here is the output of those. I also ran the driver a second time with
debug level 4, just in case there were any extra hints in there.
cheers,
Jani
On 1 November 2014 22:12, Charles Lepple clep...@gmail.com wrote:
On Nov 1, 2014, at 1:30 AM, jani wrote:
Hi Charles,
I just
On Nov 1, 2014, at 8:09 AM, jani jani.tali...@gmail.com wrote:
Hi Charles,
Here is the output of those. I also ran the driver a second time with debug
level 4, just in case there were any extra hints in there.
Here's the culprit:
5.338858 status interrupt read: error sending
26 matches
Mail list logo
