similar to: Atlantis-Land UPS with Cypress CY7C63723 chip (cypress_m8 driver) support

Displaying 20 results from an estimated 2000 matches similar to: "Atlantis-Land UPS with Cypress CY7C63723 chip (cypress_m8 driver) support"

2006 Feb 10
1
newhidups capture - Atlantis-Land HID UPS
Hello Charles! As promised, I just checked out the CVS and recompiled everything. In the attached .txt is what is coming out from my UPS. I am wondering about all those zeroes. Also, this morning I plan to connect the UPS to a Win box running the monitoring program supplied with the UPS (UPSilon2000) and a USB sniffer program. If you have any suggestions on what to look for in the data,
2006 Sep 22
1
Ablerex 625L USB version
*********************** 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:
2006 Sep 11
3
new ups for database?
I have a Belkin F6H500ukUNV ups that I am attempting to get working under nut, however it does not appear to be detected by nut, I'm assuming that I need to feed some information back to you guys to get it included in the database somwhere. I've included (what I can think might be) the relivant outputs. Please let me know if you require anything else. dmesg output /sbin/newhidsups
2005 Dec 13
1
Re: [Nut-upsuser] Atlantis-Land UPS with Cypress CY7C63723 chip
Hello Peter! Peter Selinger wrote: > This is useful information. I don't think the device is currently > supported, but the information printed above is enough to write a > subdriver for it. Note that the purpose of the "-x generic" option is > precisely to produce this output. [...] >> Apparently the UPS is recognized but no communication is >>
2016 Sep 08
2
blazer_usb MEC0002 problem Fry's Electronics (Turbo-X)
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
2006 Nov 15
1
Tripp Lite OMNI900LCD
I am having an issue running NUT and using an TrippLite OMNI900LCD. When I run ./upsdrvctl start I get : [player@V0002-S002 bin]$./upsdrvctl start Network UPS Tools - UPS driver controller 2.1.0 Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.1.0) Detected a UPS: Tripp Lite /TRIPP LITE UPS Using subdriver: TrippLite HID 0.1 (experimental) dstate_setflags: base variable
2006 Oct 18
2
newhidups with APC Smart-UPS 1500
I tested your fix (newhidups -DDD /dev/null) using both and APC Back-UPS 350 an APC Smart-UPS RT 2000 XL. No more segmentation fault due to the fixed-size array. ~Jacob -----Original Message----- From: nut-upsdev-bounces@lists.alioth.debian.org [mailto:nut-upsdev-bounces@lists.alioth.debian.org] On Behalf Of Peter Selinger Sent: Monday, October 16, 2006 12:12 PM To: Schmier, Jacob Cc: NUT
2007 May 11
11
tripp lite smart2200RMXL2U error reading protocol
I'm working on a gentoo server with Nut 2.0.5-r1 and libusb-0.1.12. I originally tried the hidups driver which seemed to work, but produced a large amount of unhandled events. Then I tried the newhidups which told me my ups wasn't supported. When I try using tripplite_usb -u root -DDDD /proc/bus/usb/002/002 I get that there isn't a match. But when I try using tripplite_usb -DDDD
2006 May 02
5
Newhidups gets unbound after a while
Hi everybody, If we let the feature running, it appears that the driver gets unbound after a while ( variable from quarter of hour to 6 hours ) and cannot reconnect. This behavior appear with both MGE Ellipse ASR and non-ASR models with connection to an UHCI and OHCI controllers. The USB core is from 2.4.28 kernel. We use nut-2.0.3. Start, powerfail and recovery detections, UPS shutdown work
2020 Jun 28
2
AVR750U Low Power not Triggering Shutdown
Hello, I am having difficulty using NUT to shut down my Netgate SG-1100 (a pfSense router) when the power level of the UPS gets critically low. Here is some relevant information: - OS: pfSense 2.4.5-RELEASE-p1 (FreeBSD 11.3-STABLE) - NUT version: 2.7.4 - Installed from: pfSense package 2.7.4_7 - UPS: AVR750U (Device release number 2) - I have included my config files, output from `upsc`, and
2006 Jul 24
3
Tripp Lite Smart1000LCD driver problem
Thanks Kjell for the help with the build problem. Thanks for your input, too, Charles. Now I have a new problem that I think has already been solved. I have Tripp Lite Smart1000LCD UPS (usb), but I can't get the newhidups driver to communicate correctly. I found a thread on the development list from last December where Jonathan Freedman described had a problem with this UPS in a thread
2017 Dec 18
2
Tripp-Lite BCPERS450 shutdown/restart problems
I have a Tripp-Lite BCPERS450, connected to a system running Ubuntu 16.04.3 LTS and NUT 2.7.2-4ubuntu1.2. I had to make my own /lib/systemd/system-shutdown/nutshutdown, but now everything is working except for powering on and off the UPS. Regardless of the settings of offdelay and ondelay in upsconf, and regardless of whether the AC power is on, when I say "upsdrvctl shutdown" the UPS
2007 Feb 26
1
Tripp Lite USB UPS
Hello all, About a month ago Peter and Charles were kind enough to try to help me with getting a Tripp Lite USB UPS to work with NUT. I reported quite a bit of initial success, and then other things here fell apart. Between work, fence building and a week-long out of town business trip, I have had to drop this from my list of things to do lately. I am back at it, and I believe I will have
2015 Aug 15
2
Small patch to scale the values for TRIPP-LITE SMART*LCDT's
Hi, I just decided to fix some scaling issues for my UPS (TRIPP-LITE SMART1500LCDT). Apparently that issue existed for some time (and I knew about it as well:-() See http://thread.gmane.org/gmane.comp.monitoring.nut.devel/6482 for a thread. My little patch is attached (against 2.7.3). It seems to be working better for me but I don't have any other TRIPP-LITE's to test that I did
2015 Aug 15
2
Small patch to scale the values for TRIPP-LITE SMART*LCDT's
Hi, I just decided to fix some scaling issues for my UPS (TRIPP-LITE SMART1500LCDT). Apparently that issue existed for some time (and I knew about it as well:-() See http://thread.gmane.org/gmane.comp.monitoring.nut.devel/6482 for a thread. My little patch is attached (against 2.7.3). It seems to be working better for me but I don't have any other TRIPP-LITE's to test that I did
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
2016 May 03
2
New UPS Support: Eaton 5S 1000
Oops... changing that to --with-user=nut solved one problem. I have the driver, upsd and upsmon running now. Thank you! Now I'm back to another issue, every 2 seconds I get in the logs: May 3 13:45:23 myhost upsd[2587]: Connected to UPS [eaton]: usbhid-ups-eaton It seems happy to do this forever. On Tue, May 3, 2016 at 8:17 AM, Charles Lepple <clepple at gmail.com> wrote: > On
2006 Jun 14
3
Trouble Configuring NUT with Gamatronic USB
Hi I am running FC5 with nut coming from the fc5 extras repositories. I am trying to configure a Gamatronic D-Compact ups. The cable that came with the ups has a serial connector on one end and a usb on the other. cat /proc/bus/usb/devices produces T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P:
2005 Dec 13
0
Re: [Nut-upsuser] Atlantis-Land UPS with Cypress CY7C63723 chip
[please keep the list CC'd] On 12/13/05, ngpost1 <ngpost1@etitech.net> wrote: > Charles, > > Another question: > > When I ran the newhidups -DD.... test, there apparently was no > communication with the UPS. Since I assume is talks with the Megatec > protocol, I wanted to force the protocol in the command line. As far as I know (and I am no expert on
2015 Jun 09
2
libusb_get_string: invalid argument
On Jun 8, 2015, at 8:23 PM, Greg Hersch <hersch.greg at gmail.com> wrote: > Hi Charles. I patched, reconfigured, remake'd, remake install'd - but > no change. however, some more likely helpful information below for > you. Thank you Odd. Are you sure that the new version of usbhid-ups got installed to the same path you are running? Also, there is no protection against