Displaying 20 results from an estimated 2000 matches similar to: "Fry's Electronics UPS..."
2020 May 15
0
Unable to get NUT working
Hi all,
just landed here so apologize. I've googled a lot but I can't find a way
to get my UPS working with NUT.
here my ( relevant ) details:
lsusb
...
...
Bus 001 Device 027: ID 0001:0000 Fry's Electronics
...
...
lsusb -v -d 0001:0000
Bus 001 Device 027: ID 0001:0000 Fry's Electronics
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB
2016 Jan 23
1
Powercool?
On 23/01/16 16:52, Charles Lepple wrote:
> [please use reply-all to include the list on your response]
>
> On Jan 23, 2016, at 11:14 AM, Tim Clarke <tim.clarke at manifest.co.uk> wrote:
>> 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
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
2015 Apr 24
0
Fry's Electronics UPS...
On Apr 23, 2015, at 1:16 PM, James Hammond <james_r_hammond at hotmail.com> wrote:
> I am running Ubuntu 14.04 and using NUT version 2.73 installed from apt-get package.
Hmm, the version below says 2.7.1, not 2.7.3.
> Driver debug output:
>
> root at unifi:/lib/nut# ./blazer_usb -DD -a nutdev1
> Network UPS Tools - Megatec/Q1 protocol USB driver 0.10 (2.7.1)
>
To get
2006 Jul 24
1
Fw: INFOSEC 500 XP en USB et drivers newhidups avec '-x generic'
Bonjour,
Je souheterais utilis? la version qui permet le '-x generic',mais je ne sais pas ou la recuperer car ca devrait solutionner mon probleme (cf mail ci-dessous)
DaneZ
_____
From: DaneZ [mailto:david.guillotte@danez.no-ip.org]
To: arnaud.quette@mgeups.com
Sent: Sat, 08 Jul 2006 23:24:06 +0200
Subject: Fw: INFOSEC 500 XP en USB
_____
Bonjour Arnaud,
Je me
2013 Jan 13
0
Evolution 850 not recognized by NUT 2.6.5?
Hello list,
? ?Cannot make Evolution 850 to be recognized, maybe the problem is "Warning: incomplete endpoint descriptor" in lsusb? Details are as follows. NUT installed by download of debian package.
Any ideas/suggestions are highly welcome, thanks in advance!
--ValenteM
= ? ?= ? ? = ? ? =
Ubuntu server 12.04.1 LTS (GNU/Linux 3.2.0-35-generic x86_64)
sudo dpkg -i
2009 Mar 04
3
Nut with megatec_usb
Hi,
I'm new in the list and I'm having a little bit trouble to put the
megatec_usb to work.
I've been using NUT for a while with the apc and megatec driver (serial),
with no problem.
The server is a Ubuntu 8.04.2 with NUT version 2.2.1-2.1ubuntu7.2, the
default package version in this ubuntu release.
I've configured the ups.conf as follows:
[sms]
driver = megatec_usb
2009 Mar 04
3
Nut with megatec_usb
Hi,
I'm new in the list and I'm having a little bit trouble to put the
megatec_usb to work.
I've been using NUT for a while with the apc and megatec driver (serial),
with no problem.
The server is a Ubuntu 8.04.2 with NUT version 2.2.1-2.1ubuntu7.2, the
default package version in this ubuntu release.
I've configured the ups.conf as follows:
[sms]
driver = megatec_usb
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
2011 Feb 08
1
Plexus 800VA UPS on ReadyNAS Duo
Hi
I Bought a cheap Plexus 800VA UPS from ebuyer :
http://www.ebuyer.com/product/240319 to use with my Netgear ReadyNAS duo.
Initial version of NUT was very old and NAS didn't detect it although in the
NAS log it said "UPS Disconnected". Syslog did send the following :
Jan 25 12:46:36 nas-27lfc kernel: usb 1-1: new low speed USB device using
uhci_hcd and address 2
Jan 25 12:46:37
2013 Nov 22
0
Fwd: [HCL] Novex NUPS-650 supported by blazer_usb
Novex NUPS-650
USB information
$ lsusb -s 002:027 -v
Bus 002 Device 027: ID 0001:0000 Fry's Electronics
Device Descriptor:
??bLength ???????????????18
??bDescriptorType ????????1
??bcdUSB ??????????????1.00
??bDeviceClass ???????????0 (Defined at Interface level)
??bDeviceSubClass ????????0
??bDeviceProtocol ????????0
??bMaxPacketSize0 ????????8
??idVendor ??????????0x0001 Fry's
2013 Jun 23
1
Bluetooth 4.0 with chip BCM20702A0 on CentOS6.4
Hi All,
I bought a USB Bluetooth dongle.
However, it's not working for me. Please help, how to debug and get more
information as I can not see any error or warning message from system log
message.
I checked http://thread.gmane.org/gmane.linux.bluez.kernel/22183/focus=22211,
however, also find another page
2017 Jan 04
0
Guardian LCD 1500 AP ( IGA1500LCD )
Hello
In case anyone is interested and for the sake of updating the
documentation from http://networkupstools.org/stable-hcl.html , I would
like to report that nut v2.7.4 talks successfully ( at least partially
) with the UPS from $topic, which is part of the product line from
http://www.informups.com/guardian_guardian_lcd600va_2000va.html ( Inform
is a Turkish manufacturer that was
2008 Dec 01
1
Unitek Self Protek Mistral 1000ipF
Hi,
just try the Unitek Self Protek Mistral 1000ipF with nut and I doesn't work.
How can I correctly configure it (if the driver support it).
Best regards,
In my dmesg:
[42953293.620000] usb 1-2: new low speed USB device using uhci_hcd and
address 7
[42953293.760000] usb 1-2: no configurations
[42953293.760000] usb 1-2: can't read configurations, error -22
[42953293.880000] usb 1-2: new
2007 Dec 28
1
Plexus UPS 1000V - megatec_usb
Hi,
Just purchashed this UPS.
The megatec_usb driver appears to be communicating with the UPS -
however, the ups.status field always states "off"
/usr/local/ups/bin/megatec_usb -a plexus -DD
Network UPS Tools 2.2.1 - Megatec protocol driver 1.5.9 [megatec_usb]
Carlos Rodrigues (c) 2003-2007
Serial-over-USB transport layer for Megatec protocol driver [megatec_usb]
Andrey Lelikov (c)
2007 Dec 28
1
Plexus UPS 1000V - megatec_usb
Hi,
Just purchashed this UPS.
The megatec_usb driver appears to be communicating with the UPS -
however, the ups.status field always states "off"
/usr/local/ups/bin/megatec_usb -a plexus -DD
Network UPS Tools 2.2.1 - Megatec protocol driver 1.5.9 [megatec_usb]
Carlos Rodrigues (c) 2003-2007
Serial-over-USB transport layer for Megatec protocol driver [megatec_usb]
Andrey Lelikov (c)
2007 May 05
1
powermust usb
Hi,
I have a powermust with a usb connector.
I searched the archive and found this post:
http://lists.alioth.debian.org/pipermail/nut-upsdev/2006-April/000816.html
Must I abandon hope of controlling this UPS via USB
with NUT?
Added this line to
/etc/udev/rules.d/70-nut-usbups.rules:
# OMRON - usbhid-ups
SYSFS{idVendor}=="06da", SYSFS{idProduct}=="0003",
2016 Jul 26
0
Two UPS with same vendor ID
Hello
I have two completely different UPS that turn out to use the same driver.
Both work with blazer_usb
my LSUSB says:
Bus 001 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial
Bus 001 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial
my lsusb -vd 0665: says:
pi at elektra:~ $ lsusb -vd 0665:
Bus 001 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial
2010 Sep 16
1
Soyntec Sekury A600 VA
Hi all!
FYI, after some research in your list I think that blazer_usb is the
best driver for my Soyntec Sekury A600 UPS (which is not in the
hardware supported lists). I connected it with my system using USB
port (it also has serial RS-232) This is the report I have:
battery.voltage: 13.60
battery.voltage.nominal: 12.0
beeper.status: enabled
device.type: ups
driver.name: blazer_usb
2005 Jan 03
1
USB booting
folks,
the following is lsusb -v for my 250gb usb hard drive.
I note the Protocol line mentions zip:
ie
bInterfaceProtocol 80 Bulk (Zip)
does that mean its one of those USB-ZIP devices ?
If so, to the parameters below say anything about the CHS settings needed ?
tia,
PS - HPA, you were correct wrt what I missed :-}
Bus 001 Device 002: ID 1058:0401 Western Digital Technologies,