search for: ablerex

...t this UPS to work? I am using the laster development nuts. My /proc/bus/usb/devices content: ==== cut ==== T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=ffff ProdID=0000 Rev= 1.00 S: Manufacturer=UIS Ablerex S: Product=Ablerex USB Interface 049e C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 0 Cls=03(HID ) Sub=00 Prot=00 Driver=(none) ==== cut ==== "newhidups -DD -u root -x generic -x vendorid=ffff auto" gave me this: debug level is '2' Checking device (FFFF/0000)...

...USB_TIMEOUT); p_raw_buf_test = raw_buf_test + (ReportSize_test - ReportSize); memcpy(raw_buf, p_raw_buf_test, ReportSize); return rc; } else return 0; } From this I now get Detected a UPS: UIS Ablerex/Ablerex USB Interface 049e Using subdriver: EXPLORE HID 0.1 parsing 00860004 parsing Flow hid_lookup_usage: found 84001e parsing FlowID hid_lookup_usage: found 84001f Path depth = 3, Path: 00860004.Flow.FlowID, Node1/2/3:, 860004, 84001e, 84001f 0: Usage(00860004) 1: Usage(0084001e) 2: Usage(008400...

...y for your device? In particular, do the instant commands (and particularly "upsdrvctl -k") work properly? In this case, we could hopefully mark the device as "supported" and merge the driver to the main branch. There is still the question of whether to keep separate code for Ablerex and Krauler. From what I understand, each of these subdrivers works for each of the devices. But the Krauler driver is now more advanced (with the retry feature), so we could remove the Ablerex subdriver (provided Jon tests the Krauler one to make sure it still works for the Ablerex device). If I...

Hello, I own some Ablerex MARS 3000 (MS3000RT) UPS. Following the thread here : http://osdir.com/ml/monitoring.nut.user/2006-04/msg00091.html I would have the following issues : 1. The battery charge displayed seems wrong : It always shows 100.0 - even when the battery is disconnected for replacement. 2. Battery voltage 2.2...

Hello! Looks like Lau Kim Ping stepped on another Ablerex box, just like I did: http://lists.alioth.debian.org/pipermail/nut-upsdev/2005-December/000461.html The problems he is describing are exactly the same I had. Eventually I ran out of ideas and moved on to other things, but I still wish to get the thing to work. --Max -- Open WebMail Project (h...

Hi, Is there any further information on this UPS interface? I have an Upsonic UPS that is reporting the same interface, but I cannot make it work or get any sensible information from it. Thanks Jon --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 000706-2, 25/01/2007 Tested on: 26/01/2007 11:00:14 AM avast! is copyright (c) 2000-2007 ALWIL Software.

Hi, Is there any further information on this UPS interface? I have an Upsonic UPS that is reporting the same interface, but I cannot make it work or get any sensible information from it. Thanks Jon --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 000706-2, 25/01/2007 Tested on: 26/01/2007 11:00:14 AM avast! is copyright (c) 2000-2007 ALWIL Software.

...ich is already in the list but taken when I was using an old version of nut, as well as one for Guardian LCD 1500 AP ( IGA1500LCD ) which is not in your list at all ( see https://lists.alioth.debian.org/pipermail/nut-upsuser/2017-January/010493.html as well when I first reported about it ) a) Ablerex MARS MS3000RT battery.charge: 100 battery.voltage: 108.48 battery.voltage.high: 104.00 battery.voltage.low: 83.20 battery.voltage.nominal: 96.0 device.mfr: Ablerex device.model: MS3000RT device.type: ups driver.name: blazer_ser driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyUSB0 dr...

[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 patches, if any, have you applied? What you are seeing from lsusb is not "data" from the UPS; it is simply a detailed parsing of t...

...t running on RHEL5 and actually do something useful for me. Few questions: 1) I want it to notify me by email on power loss and power back events. I can't find any sample scripts for this purpose... Where shall I look for them? 2) So far, I've backported the package from Fedora and got my Ablerex running (previously used with Upsilon / Megatec on a Windows server). The major problem so far is that it keeps flooding my logs just as someone reported last year: http://www.mail-archive.com/nut-upsuser at lists.alioth.debian.org/msg03762.html Is there a way to somehow mute these messages? up...

...diff'd them > correctly. I have not touched the megatec_ser.c file so I have not > included it. I have now got knutclient talking to the driver and it > seems to be displaying what it should. So as a first pass this will > work with the Upsonic CS1500 UPS that reports itself as Ablerex. > > Regards > Jon > > *** megatec.c.orig 2007-01-29 08:12:19.000000000 +1100 > --- megatec.c 2007-01-31 18:28:33.000000000 +1100 > *************** > *** 243,251 **** > char buffer[RECV_BUFFER_LEN]; > int ret; > > ! upsdebugx...

Hello again! Thanks to the precious help from Henning Brauer, I managed to solve an issue with my UPS (a rebranded UPS speaking in Ablerex-ese over USB). Under OpenBSD 4.3, the UPS was claimed by HID. Now that I recompiled the kernel, adding a USB_quirk, this is what I get when I insert the USB cable: ugen0 at uhub0 port 2 "UIS_ABLER USB to Serial" rev 1.00/1.00 addr 2 So far, so good (Henning confirmed this). Trouble is,...

I've posted this before being subscribed but was thwarted by moderation. I have a new UPS, actual manufacturer unknown. It comes with USB and serial connections, and a CD with windows software and some old unix software for serial support only. I'm using pretty much bleeding edge linux, and I want to avoid rs-232 if possible. Am I hopelessly naive? This is what lsusb says: Bus 006

Hello, Somewhat off-topic, but seeking some input from other tech folk on this list. I have a Tripp-Lite SMART 2200 (a white tower that looks similar to, but predates the black SMART2200NET) that just failed its monthly battery test so I bought new batteries and replaced the old ones. Sadly once put back together, plugged in and enabled it did not power up--no lights, sounds, smoke, etc. I took

People, A couple of decades before I was retired and was still working for other people I had cause to install UPSs and they usually had RS232 ports to allow the setting up of shutdown scripts to UNIX / Linux servers. Now, after not having to be concerned by those issues for some time - most of my little web sites have been on Digital Ocean or other suppliers VMs for a long time - I am

People, A couple of decades before I was retired and was still working for other people I had cause to install UPSs and they usually had RS232 ports to allow the setting up of shutdown scripts to UNIX / Linux servers. Now, after not having to be concerned by those issues for some time - most of my little web sites have been on Digital Ocean or other suppliers VMs for a long time - I am

Hi! I have finally set up NUT more or less the way I want it to work, but after live testing, it turned out that the UPS (Ablerex VS000361, serially connected using megatec driver) does not switch on the load after the shutdown has been initiated & completed and power came back on. Is there any magic command that I'm missing that I have to issue to instruct the unit to switch the load back on when power comes back?...

Hi, a few days ago, I bought some of those Mustek UPSes that have both a serial and a USB connector. Currently only the serial port is supported by the megatec driver. This works fine so far. Now I have seen there is a megatec_usb driver, which currently only supports 2 other UPSes. How can I help to find out whether the PowerMust might actually work with the megatec_usb driver? -- Regards,

...for other missing entries (r1041). The only remaining things are (I've not checked the matching driver yet): - Mustek Powermust 600USB (OMRON/87XXUPS) - LIEBERT/PowerSure Personal XT - Cypress Semiconductor USB to Serial - Powercom - unknown driver And I'm still reluctant with Krauler and Ablerex entries (non compliant IDs), though I leaved these in the fdi file for now. Arnaud -- Free Software Developer - http://arnaud.quette.free.fr/ Debian Developer - http://people.debian.org/~aquette/ Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Ubuntu Media Center (UMC) Pr...

Citeren Arjen de Korte <adkorte-guest at alioth.debian.org>: > Author: adkorte-guest > Date: Mon Nov 24 13:13:44 2008 > New Revision: 1578 > > Log: > Use new usb_device_id_t and is_usb_device_supported() > for selection of the subdriver. Alexander, It would be nice if you could double check that I didn't horribly break something here. I don't expect any