similar to: Frys Electronic / ATCL FOR UPS / Debian Jessie

[please use Reply-All to include the list - the list server does not modify the headers] > On Jan 11, 2017, at 1:49 PM, london jak wrote: > > Hi folks, > > Can?t seem to get this working with Frys Electronic / ATCL FOR UPS device connect direct via USB. > > > This post suggests it should work: > >

Hello, I am trying to get a "no-brand" (LMS DATA, model no LMSP1200RI) UPS to work with NUT. I now realise I should have checked compatibility with NUT before purchase. My other UPS (APC) works perfectly..... Anyway, I have spent a good day trying to get this thing working. #lsusb Bus 001 Device 003: ID 0001:0000 Fry's ElectronicsDevice Descriptor: bLength 18

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

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

Centos 6.7 Linux man8.m1.manifest.co.uk 2.6.32-573.12.1.el6.i686 #1 SMP Tue Dec 15 18:25:17 UTC 2015 i686 i686 i386 GNU/Linux Installed: nut.i686 2.6.5-2.el6 @epel nut-cgi.i686 2.6.5-2.el6 @epel nut-client.i686 2.6.5-2.el6 @epel I'm struggling to control an

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

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:

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

Hi, I just bought a cheap UPS and apparently I'm hitting the same issue that's described here: http://comments.gmane.org/gmane.comp.monitoring.nut.user/6146 Mine is a different brand: "Kanji" which appears to be the argentinian dealler for some generic chinese manufacturer. My model is also 800VA and identified in the same way, so maybe is the same UPS under a different brand:

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

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

Ok, not exactly an Asterisk problem, but... I picked up some SNOM 200 phones because SNOM's have been recommended for use with Asterisk and they have line buttons that can subscribe to presence. However, they don't appear to power up when connected to my Negear FS108P, which is an 802.3af Power-over-ethernet capable hub. I am pretty sure these are the SNOM 200b, in that the ethernet

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

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

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

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

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