similar to: Need nutdrv_atcl_usb for Windows port

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

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

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

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

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

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

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

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

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

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:

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

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 from debian sid (ubuntu is still stuck on nut version 2.7.1) to get the 2.7.2 version with the

Hi! I would like to ask about current state of Windows port. Is it frozen? It will be cool to know the plans :) Where are a lot of Windows-branches at GitHub. What is the most actual one? The Windows builder looks like turned off, am I right that it is not available currently and where were no builds after version 2.6.5-6? I couldn't find any info about proper environment to build Windows

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 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) >

On Nov 3, 2014, at 9:01 PM, jani <jani.talikka at 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 at 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 ran

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

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