similar to: Re: [Nut-upsuser] Ablerex 625L USB version

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.

[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

*********************** Your mail has been scanned by InterScan MSS. *********************** Has anyone managed to get 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:

Hi all, My name is Sergio Penen and I'd like to contribute to the project by developing a new driver for TS SHARA SOHO II usb ups. I'm almost done decoding the protocol and already have some basic functionality working with NUT. However I've some doubts on how to integrate this driver with NUT and I wonder if you could give me some guidance in that sense. To be more specific: In order

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 (http://openwebmail.org)

Hi Jon, your patches are malformed because (presumably) your email client wrapped this lines. Could you please send these as a unified diff ("diff -u"), and send them in attachments, rather than as a copy-and-paste? Thanks, -- Peter Jon Gough wrote: > > Peter, > Here are the files I have worked on. I hope I have diff'd them > correctly. I have not touched the

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.29 is also static ...and wrong. The initial assumption of being the voltage

Hi Charles, Sorry for the long email, I feel this deserves a fuller explanation. On Wed, Feb 14, 2018 at 10:30:18PM -0500, Charles Lepple wrote: > On Feb 3, 2018, at 7:19 PM, Russell King wrote: > > > > Input and Output reports are used for interrupt endpoints rather than > > control endpoints. HIDGetItemData() only ever requests feature > > report IDs, and

I think having this logic buried within libhid/libusb (libusb:libusb_open(), line 179 to 206) is ultimately a mistake, albeit one that I am probably responsible for. Would it make sense to confine libhid to low-level operations, and leave the decision of trying to reopen vs. retrying to open to the high-level driver, in this case usbhid-ups? I envision that the code in usbhid-ups:reconnect_ups()

On Feb 3, 2018, at 7:19 PM, Russell King wrote: > > Input and Output reports are used for interrupt endpoints rather than > control endpoints. HIDGetItemData() only ever requests feature > report IDs, and requesting non-feature report IDs as feature IDs may > lead to undesirable results and errors. This one made me scratch my head a bit. I don't think it's unreasonable

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,

Hello everybody! I am trying to get an Atlantis-Land OnePower Line Interactive S1501 UPS (actually it is made by Ablerex) to talt to my Linux box through its USB port (no more RS-232...), either using the supplied program (UPSilon2000, works under Win and Linux) or whatever else. The UPSilon2000 program apparently works OK *if* it can talk to the UPS via a serial port; since my UPS has

Hello everybody! I am trying to get an Atlantis-Land OnePower Line Interactive S1501 UPS (actually it is made by Ablerex) to talt to my Linux box through its USB port (no more RS-232...), either using the supplied program (UPSilon2000, works under Win and Linux) or whatever else. The UPSilon2000 program apparently works OK *if* it can talk to the UPS via a serial port; since my UPS has

[snip hex dump analysis] > > It is possible that the blazer_usb driver initialization has put the UPS > into a bad state. If you can schedule some downtime, you might want to try > usbhid-ups again after powering the UPS down completely and unplugging it > for a little while. (Often, a few seconds after the output is off and the > AC has been removed, you will hear relays

Hi again, Thanks for the prompt reply. Just for the record i am running debian unstable/sid with nut 2.7.4-3 # dpkg -l 'nut*' | grep ^ii ii nut 2.7.4-3 all network UPS tools - metapackage ii nut-client 2.7.4-3 amd64 network UPS tools - clients ii nut-server 2.7.4-3 amd64 network UPS tools - core

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

Hi Alexander, thanks for your good work on the megatec_usb driver. I have made a few more (cosmetic) changes. Is the driver now working stably 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

On 06/25/2017 08:43 PM, Charles Lepple wrote: > > This brings me to the Device Dump List: http://new.networkupstools.org/ddl/ (or http://networkupstools.org/ddl/ if the first link is not working). I am providing below two dumps for one UPS which 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

Hi there! I'm a n00b NUT user trying to get it 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 /