Displaying 20 results from an estimated 1200 matches similar to: "nutdrv_atcl_usb"
2015 Mar 11
3
nutdrv_atcl_usb
Thank you for the commands...
Please find attached log...
Im not sure if the Load.on worked, because in the end I had to manually
start the UPS (with button).
Anyway, let me know should I need to perform some steps again (probably
yes, since I believe it was off).
Jakub
On 11.03.2015 20:11, hyouko at gmail.com wrote:
> 2015-03-11 14:21 GMT+01:00 Jakub Scepka <jakub.scepka at
2015 Mar 11
0
nutdrv_atcl_usb
2015-03-11 14:21 GMT+01:00 Jakub Scepka <jakub.scepka at 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:
[<username>]
password = <password>
actions = SET
instcmds = ALL
where
2015 Mar 11
2
nutdrv_atcl_usb
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, hyouko at gmail.com <hyouko at gmail.com> wrote:
> mmh.. it looks like someone forgot to hit 'reply all'.
>
> - relaying the originally attached files (gzipped, minus the two
>
2015 Mar 10
0
nutdrv_atcl_usb
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.scepka at 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
2014 Nov 09
4
nutdrv_atcl_usb
On Nov 8, 2014, at 7:01 PM, hyouko at 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 assume companies will copy bogus product IDs, but the use of the exact same USB string descriptor is odd.
Did you have a chance to compare the rest of
2015 Mar 05
5
nutdrv_atcl_usb
On Mar 5, 2015, at 2:34 AM, Jakub <jakub.scepka at 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
2015 Mar 17
0
nutdrv_atcl_usb
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
2015 Mar 09
0
nutdrv_atcl_usb
2014-11-09 16:29 GMT+01:00 Charles Lepple <clepple at gmail.com>:
> On Nov 8, 2014, at 7:01 PM, hyouko at 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 assume companies will copy bogus product IDs, but the
2014 Nov 05
0
nutdrv_atcl_usb
On Nov 5, 2014, at 1:36 AM, jani <jani.talikka at 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 besides the stock debian desktop is nut.
>
> The UPS still refuses to talk to the
2017 Mar 11
0
Need nutdrv_atcl_usb for Windows port
On Mar 10, 2017, at 5:25 PM, hamberthm at gmail.com wrote:
>
> UPDATE: I managed to build the windows port using a guide a user posted a while ago.
Which guide?
> I?ve also corrected a couple of variables like the SleepEx() function instead of the sleep() used in Linux. I?ve successfully compiled the EXE for nutdrv_atcl_usb but when I execute it via upsdrvctl it gives the following
2014 Nov 01
0
nutdrv_atcl_usb
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 <clepple at gmail.com> wrote:
> 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
2015 Apr 13
1
NUTDRV_ATCL_USB driver on Windows
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 to identify it as compatible but fails at sending commands.
Further
2014 Nov 01
2
nutdrv_atcl_usb
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:
> http://eastups.com/en/productshow.aspx?CateId=473&Id=164&PCateId=447
>
> It came
2017 Mar 10
2
Need nutdrv_atcl_usb for Windows port
UPDATE: I managed to build the windows port using a guide a user posted a while ago. I?ve also corrected a couple of variables like the SleepEx() function instead of the sleep() used in Linux. I?ve successfully compiled the EXE for nutdrv_atcl_usb but when I execute it via upsdrvctl it gives the following output:
C:\MinGW\msys\1.0\home\Administrator\nut-2.6.5-7\drivers>nutdrv_atcl_usb
2014 Nov 06
0
nutdrv_atcl_usb
On Nov 5, 2014, at 4:39 PM, jani <jani.talikka at gmail.com> wrote:
> The output of the ldd command is:
> root at 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)
>
2015 Feb 09
0
About your driver NUTDRV_ATCL_USB(8) for install
Dear Chales,
Thanks for your quick reply.
I have Raspberry with last Kernel [Linux pi1 3.18.6+ #753 PREEMPT Sun Feb 8
14:47:22 GMT 2015 armv6l GNU/Linux]
If <upsdrvctl>, <upsd> and <upsmon> are stopped <nutdrv_atcl_usb> Works well
without any error as "Device or resource busy".
If I run <upsc> command never receive any value from my ups <upsc
ups at
2014 Nov 05
2
nutdrv_atcl_usb
The output of the ldd command is:
root at 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 => /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xb7536000)
/lib/ld-linux.so.2
2014 Nov 05
2
nutdrv_atcl_usb
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 the driver, the error messages appear to
be identical, but I attached them just in case I'm
2014 Nov 06
2
nutdrv_atcl_usb
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: