similar to: Ablerex 625L USB version

Displaying 20 results from an estimated 9000 matches similar to: "Ablerex 625L USB version"

2015 Jun 08
2
libusb_get_string: invalid argument
On Sun, 7 Jun 2015, Charles Lepple wrote: > [please use reply-all to include the list, as the list does not override the Reply-To header.] > > On Jun 7, 2015, at 5:02 PM, Greg Hersch <hersch.greg at gmail.com> wrote: > >> Here is the driver debug log. If I just let it run, it pops up with >> libusb_get_string_invalid argument over and over again, mixed in the
2017 Oct 11
4
Junda-tech
Hi, I have an UPS with only the marking D1000 on it and it came with Junda-Tech's UpsMate. Its USB id is 3344:0025, which is apparently a microprocessor. I've could get some of the HID interactions as described on the website, but there are some outstanding. Junda-Tech does not respond to any queries. Does anybody else have the same or a similar UPS with more information? What is the
2017 Mar 11
2
[nut-upsuser] Copeland Engineering Dockmaster
[moved to nut-upsdev while we figure out the protocol] > On Mar 9, 2017, at 11:22 AM, Drew from Zhrodague <drewzhrodague at zhrodague.net> wrote: > > I'm able to cat /dev/usb/hiddev0 and /dev/hidraw0 - I pipe this through hexdump and I get different types of data from each: > > > hiddev: > > 0002420 00a7 ffa0 00ff 0000 00a7 ffa0 00ff 0000 > 0002430 00a7
2007 Jan 28
0
Fwd: Re: [Nut-upsuser] Ablerex 625L USB version
[Note: trimmed HTML] ---------- Forwarded message ---------- From: selinger@mathstat.dal.ca (Peter Selinger) To: jon.gough@eclipsesystems.com.au (Jon Gough) Date: Sun, 28 Jan 2007 02:20:48 -0400 (AST) Subject: Re: [Nut-upsuser] Ablerex 625L USB version Hi Jon, I can't figure out which version of NUT you are running, because you have pruned that information from your output. Also, which
2012 Jan 30
8
Support for Online Yunto and Zinto
Hello, I have a Yunto e a Zanto ups connected with usb with id 06da:0002 and 06da:0601. I have seen that people had some success using megatec driver. But now megatec is replaced by blazer-usb and I am not able to use my upses under nut. Can you help me? Thanks! Mario
2016 Jan 23
2
Powercool?
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
2007 Feb 05
5
Powercom black knight 800VA (usb)
Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20070205/5ad69acc/attachment.pgp
2016 Sep 08
2
blazer_usb MEC0002 problem Fry's Electronics (Turbo-X)
Hi, I have two ups (Turbo-X 1000SD, Turbo-X 1500SD). The both report themselves as # lsusb Bus 008 Device 002: ID 0001:0000 Fry's Electronics The are produced by MEC and report MEC0002 as product (although the working one report it in dmesg but not in lsusb) The 1000 (bcdUSB 1.00) works with blazer_usb while the 1500 (bcdUSB 1.10) doesn't. I am attaching lsusb and blazer_urb output
2007 Jul 06
3
energizerups and bestups -> megatec?
Hi! I don't know how I missed it before, but "bestups" seems to implement mostly the same protocol as megatec. Is anybody out there using this driver willing to try "megatec" to see if it works? AFAIK, the only difference seems to be the command that gets the UPS identification data ("I" on "megatec", "ID" on "bestups"), but
2007 Jul 06
3
energizerups and bestups -> megatec?
Hi! I don't know how I missed it before, but "bestups" seems to implement mostly the same protocol as megatec. Is anybody out there using this driver willing to try "megatec" to see if it works? AFAIK, the only difference seems to be the command that gets the UPS identification data ("I" on "megatec", "ID" on "bestups"), but
2010 Sep 18
1
Dynamix 1000 VA USB and NUT
Hi, I've got two Dynamix UPS's, both of which are USB and don't seem to work with NUT yet. Can anyone give me some advise on where I should start with working on getting them working. I can do a little C programming, so happy to give things a go but need some guidance. Brian R. Smith (who also subscribes to this list) has one as well. I've attached the output of lsusb -v and
2006 Apr 14
1
Mustek Powermust 600USB and newhidups
So, I have this Mustek Powermust 600USB (no serial port) here temporarily. It seems to be a hid device. The output from "lsusb -v" and "newhidups -DDDDD" (with "generic" and "vendorid=06da") are (respectively): ----------------------------------------------------------------------------------------------- Bus 001 Device 002: ID 06da:0003 Phoenixtec Power
2006 May 11
1
Tripp Lite OMNI1000LCD
Greetings, Any suggestions? I think I'm close but I can't quite get tripplite_usb to talk to my OMNI1000LCD. I'm new to NUT and couldn't find an answer using Google. With any luck, I've simply missed the obvious. The system I'm using, kaylee, is a debian stable system with some debian testing installed and a 2.6.15.4 kernel. I downloaded NUT 2.0.3 and built it from
2007 Jan 31
3
Re: [Nut-upsuser] Ablerex 625L USB version
Peter, I have been doing some more testing and I find that if I modify the libusb.c file to set a report size in libusb_get_report to 16 the error messages go away. This is the code as it currently stands: static int libusb_get_report(usb_dev_handle *udev, int ReportId, unsigned char *raw_buf, int ReportSize ) { int ReportSize_test = 16; unsigned char raw_buf_test[ReportSize_test +
2023 Oct 29
1
usbhid-ups not loading with Arduino Leonardo on Ubuntu 23.10
Apologies for the long post. I'm trying to include what I hope are the relevant bits (output of lsusb -v and usbhid-ups) Long term goal: I've got a DIY UPS that I would like to get working with my QNAP NAS (which uses Linux and NUT underneath the hood) Immediate short-term problem: I can't get past running usbhid-ups on Ubuntu 23.10 with an Arduino Leonardo. I have an Arduino Micro
2015 Jun 09
0
libusb_get_string: invalid argument
Hi Charles. I patched, reconfigured, remake'd, remake install'd - but no change. however, some more likely helpful information below for you. Thank you On Mon, Jun 8, 2015 at 12:34 PM, Greg Hersch <hersch.greg at gmail.com> wrote: > > > On Sun, 7 Jun 2015, Charles Lepple wrote: > >> [please use reply-all to include the list, as the list does not override >>
2005 Sep 07
3
Liebert PowerSure PSA 500
Hello everyone, Charles suggested (about a week ago) that I repost to this list. I took a moment to run some additional tests ... The basics: -- UPS: Liebert PowerSure PSA 500 (from the 230 VAC / 50 Hz line) -- Kernel: 2.6.11.5 (from sources), USB support (down to and including CONFIG_USB_HIDDEV) compiled in statically (not as a module) -- Rest of OS: Basically still from the original SuSE
2017 Nov 01
0
Junda-tech
Any other inputs or suggestions? I got some info from junda-tech in mandarin about the JD09U04, which is the technical information of a chip with that number. I have sent them another message, but no response so far. On 17/10/17 15:34, LLSJ Kr?ger wrote: > Bus 003 Device 003: ID 3344:0025 Leaguer Microelectronics (LME) > Device Descriptor: > ? bLength??????????????? 18 > ?
2017 Mar 19
0
[nut-upsuser] Copeland Engineering Dockmaster
On 3/11/17 9:15 AM, Charles Lepple wrote: > [moved to nut-upsdev while we figure out the protocol] > >> On Mar 9, 2017, at 11:22 AM, Drew from Zhrodague <drewzhrodague at zhrodague.net> wrote: >> >> I'm able to cat /dev/usb/hiddev0 and /dev/hidraw0 - I pipe this through hexdump and I get different types of data from each: >> > I was trying to reconcile
2006 Jan 13
1
help with TRIPP LITE SMART550USB
Hi I have a Tripp lite smartusb550 using fedora 3 (2.6.12-1.1381_FC3smp). Managed to establish communication with the ups using the tripplite_usb driver but get the following errors Any help to make it work will be appreciated cheers Julio -----------------------------------------------------------------------------------------------------------------------------------------------------