search for: nutdrv_atcl_usb

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 nutdrv_atcl_usb:./.libs/lt-nutdrv_atcl_usb.c:233: FATAL: couldn't find nutdrv_atcl_usb. Now I have no idea how to continue? Gesendet von Mail f?r Wi...

...l/007171.html All the versions of MinGW and msys plugins I'm using are exactly the ones listed on that guide written by Denis Serov. The procedure I used to compile is also the same as Denis suggested, but I made some changes on my own in the "build NUT" step since I added the "nutdrv_atcl_usb.c" source file from the last version of NUT, not present in the latest Windows build. Those are: - Patched file "nut-usbinfo.pl" as otherwise it will abort the make process with an error. In the section "process the driver name" with the following code (same as latest NUT...

...&PCateId=447 > > It came with a windows cd containing the windows software entitled UPSmart2000I version 3.7 and while I haven't installed it the screenshots show that you can get input and output voltage and battery voltage information out of the thing. > > The problem is the nutdrv_atcl_usb driver out of nut 2.7.2 doesn't seem to function, I get the following in my logs: > Nov 1 16:28:49 microserver nutdrv_atcl_usb[2242]: Warning: excessive comm failures, limiting error reporting > Nov 1 16:28:49 microserver nutdrv_atcl_usb[2242]: Communications with UPS lost: Query to UPS...

...ear to be identical, but I attached them just in case I'm missing something important. I tried changing the permissions and running as root just in case, and they made no difference. Hmm, maybe those aren't the /dev node names that it is using. Can please you send the output of: strace -o nutdrv_atcl_usb.strace /lib/nut/nutdrv_atcl_usb -a name -DD Also, if you run 'ldd /lib/nut/nutdrv_atcl_usb', is it linking against 'libusb-0.1.so.4' or libusb-compat? -- Charles Lepple clepple at gmail -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://...

...Device or resource busy > 0.029246 detached kernel driver from USB device... > 0.030559 USB device [0001:0000] opened > 0.866216 read: (8 bytes) => 03 00 00 00 00 00 00 00 > 0.866413 reply[0] = 0x03 -> OL > 0.867461 dstate_init: sock /var/state/ups/nutdrv_atcl_usb-ups open on fd 5 > 1.914346 read: (8 bytes) => 03 00 00 00 00 00 00 00 > 1.915850 reply[0] = 0x03 -> OL > 5.872047 status interrupt read: error submitting URB: Device or resource busy "Device or resource busy" usually means that another kernel driver or u...

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 localhost> then I can't test shutdown ups. When I run <upsd> with debugin level I view change of my UPS VALUES (OL) to (OB)...

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-l...

...th 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 > from debian sid (ubuntu is still stuck on nut version 2.7.1) to get the > 2.7.2 version with the nutdrv_atcl_usb driver. > I tried adding the "-u root" to the driver command line, that didn't > change anything. I might try to find a spare machine to run Debian on to > see if it works that way. > > On Tue Nov 04 2014 at 3:38:21 PM Charles Lepple <clepple at gmail.com> wrote:...

...447 > > It came with a windows cd containing the windows software entitled > UPSmart2000I version 3.7 and while I haven't installed it the screenshots > show that you can get input and output voltage and battery voltage > information out of the thing. > > The problem is the nutdrv_atcl_usb driver out of nut 2.7.2 doesn't seem to > function, I get the following in my logs: > >> Nov 1 16:28:49 microserver nutdrv_atcl_usb[2242]: Warning: excessive >>> comm failures, limiting error reporting >> >> Nov 1 16:28:49 microserver nutdrv_atcl_usb[2242]: Co...

...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 output: > > C:\MinGW\msys\1.0\home\Administrator\nut-2.6.5-7\drivers>nutdrv_atcl_usb > nutdrv_atcl_usb:./.libs/lt-nutdrv_atcl_usb.c:233: FATAL: couldn't find nutdrv_atcl_usb. > > Now I have no idea how to continue?...

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) > libc.so.6 => /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xb753600...

...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 reading took me to the NUTDRV_ATCL_USB driver that seems to be specifically for my type of UPS. The problem is it isn't present in the Windows port of NUT. ?What can I do? Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/2015...

Dear Steve, Thanks. Until today I could not install the nut in my raspberry. All installation good, but with my ups " Ovislink Chrome 1000VA" and "nutdrv_atcl_usb" driver, it inform me the following error details. I can startup nut but nutmon don't receive anything only (lost conection). My setup: root at pi1:/nut# lsusb Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bu...

...needed. If nothing else, it would be >> good to improve the diagnostics for that script. > > Here's the output (attached). I interrupted the process, but it > continues looping forever. > > Kind regards. > <debug.log> There is a very proof-of-concept-y driver (nutdrv_atcl_usb) in the atcl branch in GitHub. We can probably remove a bunch of the retry loops that it inherited from richcomm_usb. There should also be a tarball here fairly soon: http://buildbot.networkupstools.org/public/nut/builders/Debian-x64-gcc/builds/115 -- Charles Lepple clepple at gmail

On 31/12/13 21:00, Charles Lepple wrote: > > There is a very proof-of-concept-y driver (nutdrv_atcl_usb) in the atcl branch in GitHub. > > We can probably remove a bunch of the retry loops that it inherited from richcomm_usb. > > There should also be a tarball here fairly soon: > > http://buildbot.networkupstools.org/public/nut/builders/Debian-x64-gcc/builds/115 > That's...

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:

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/...

Come on, it started to be interesting!

Hello! I?ve posted this a while ago, I have an UPS that reports itself as ?ATCL FOR UPS?. I was suggested by you to use a Linux box and try whether the NUTDRV_ATCL_USB works or not with my UPS. I?ve done so and YES it works. Now I need to know how can I get a port of this driver to the Windows version of NUT. I?m a complete noob in programming, and I have basic C knowledge. PLEASE I need a helping hand ? Regards Humberto Gesendet von Mail f?r Windows 10 -----...

...install dependencies. > > Best regards, > Pere Rius > > > > -----Mensaje original----- > De: Charles Lepple [mailto:clepple at gmail.com] Enviado el: jueves, 17 de > julio de 2014 14:41 > Para: pere at riusnebot.com > CC: NUT List > Asunto: Re: About your driver NUTDRV_ATCL_USB(8) for install > > On Jul 13, 2014, at 9:46 AM, pere at riusnebot.com wrote: > >> Dear Charles Lepple, >> Sorry for my email intrusion. > > for next time: > > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser > >> I have an UPS called Ovis...