similar to: NUTDRV_ATCL_USB driver on Windows

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

Hello Charles and first of all, thank you so mucho for replying. I really appreciate your help. This is the guide I was talking about: http://lists.alioth.debian.org/pipermail/nut-upsdev/2016-April/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

I think I may be of some help in this matter. Since I am running a bunch of Raspberry Pi's with NUT and it took a lot of hacking to make it possible. You could probably copy and paste this right into a shell script and just run it ... # Do an rpi-update FIRST to prevent USB strangeness #some depencies from repo sudo apt-get -y install m4 libtool libudev-dev automake #fixing autoconf for

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

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

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

On Feb 9, 2015, at 6:48 AM, PERE (yahoo.es) <pererivers at yahoo.es> wrote: > 0.028188 Can't set USB configuration: could not set config 1: 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

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

Hello again! I'm yet again the guy from the blazer_usb problem and the ATCL one too. This time I have a third UPS (the last one In my collection) that i'm trying to make work instead of the ATCL one since there's no driver for it on windows. This UPS is another no-brand box (actually it is a "kozumi", but that's just a rebrand), and apparently it's much more basic

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

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 Ovislink 1000VA and it use a UPSMART2000R (with ?ATCL FOR UPS?). > I?m a beginner Linux user and I ?will install your new driver <nutdrv_atcl_usb > to work

On Dec 26, 2013, at 10:28 PM, Ariel Wainer wrote: > On 27/12/13 00:06, Charles Lepple wrote: >> Could you please send the debug output? (if it is more than ~ 30KB >> gzipped, just send it directly to me.) I was going to use the debug >> output from the earlier thread to generate those C files, but yeah, >> there are some additional bits needed. If nothing else, it would

Dear Charles, Thanks for your quick reply, but I can't install nut_2.7.2 in my raspberry. 1) I create a [nut] directory and use wget to download three files: [nut_2.7.2-1.dsc] [nut_2.7.2.orig.tar.gz] [nut_2.7.2-1.debian.tar.xz] 2)I unpack: dpkg-source -x nut_2.7.2-1.dsc 3) I use command root at pi1:/nut/nut-2.7.2# debuild -us -uc . .. And I have the following error code:

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:

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

On Nov 1, 2014, at 8:09 AM, jani <jani.talikka at 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 control message: Operation not permitted What does 'ls -l

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

On Jan 1, 2014, at 3:50 PM, Ariel Wainer wrote: > On 01/01/14 17:33, Charles Lepple wrote: >> Disappointing. I will add a note in the man page for that, too. (Maybe >> it is only after the UPS is in the low battery state? You mentioned >> that it did shut down when you did the capture with the Windows >> software.) > > Yes, but I think it was because the battery

On Jan 10, 2014, at 4:46 PM, Ariel Wainer wrote: > On 10/01/14 01:53, Charles Lepple wrote: >> I am curious about why the Interrupt Out packet is sent by the Windows software if it isn't to turn off the UPS. Is it possible to do some more testing with shorter timeouts so that the battery doesn't get depleted? You would need to record the exact time when it shuts down, I think.

On 10/07/15 04:26, Charles Lepple wrote: > On Jul 9, 2015, at 9:43 AM, paul at paulcarmichael.org wrote: > >> Is there currently a way of implementing NUT with an Ovislink Chrome 1500 UPS? > > Not sure. There was a thread in February talking about an Ovislink Chrome 1000, but I don't think we ever resolved what was causing the "Device busy" error: > >