Displaying 20 results from an estimated 9000 matches similar to: "Can not find the Belkin F6H375-USB"
2007 Jul 28
1
Support removed for newer Belkin 1200 VA UPS?
Have had no issue until I ran apt-get dist-upgrade this morning:
# /lib/nut/newhidups -u nut -DDDDDD auto
Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5)
debug level is '6'
Checking device (0000/0000) (001/001)
- VendorID: 0000
- ProductID: 0000
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: 001
Trying to match device
Device does not
2005 Aug 01
3
Belkin F6C550-AVR UPS
Hi,
I got a Belkin F6C550-AVR UPS today and was trying to get it working
with NUT, I used the "hidups" driver and got some data out of it,
mainly the following:
battery.charge: 100
battery.runtime: 120
driver.name: hidups
driver.parameter.port: /dev/usb/hiddev0
driver.version: 2.0.0
ups.mfr: Unknown
ups.model: Unknown
ups.serial: Unknown
ups.status: OL
the versions of NUT that I tried
2005 Aug 01
3
Belkin F6C550-AVR UPS
Hi,
I got a Belkin F6C550-AVR UPS today and was trying to get it working
with NUT, I used the "hidups" driver and got some data out of it,
mainly the following:
battery.charge: 100
battery.runtime: 120
driver.name: hidups
driver.parameter.port: /dev/usb/hiddev0
driver.version: 2.0.0
ups.mfr: Unknown
ups.model: Unknown
ups.serial: Unknown
ups.status: OL
the versions of NUT that I tried
2007 Aug 25
2
Nut 2.2.0 also broke Belkin 1200 Universal UPS' as well.
Bus 003 Device 002: ID 050d:1100 Belkin Components
# /lib/nut/usbhid-ups -a belkin
Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.2.0-)
No matching HID UPS found
Hmm best to stick with 2.0.4.
Justin.
2007 Aug 25
2
Nut 2.2.0 also broke Belkin 1200 Universal UPS' as well.
Bus 003 Device 002: ID 050d:1100 Belkin Components
# /lib/nut/usbhid-ups -a belkin
Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.2.0-)
No matching HID UPS found
Hmm best to stick with 2.0.4.
Justin.
2007 Feb 16
3
Belkin F6C100-UNV + newhidups
Mr. Selinger,
I'm CCing you directly since it appears (insofar as I can tell) that you
are one of the delelopers for the newhidups driver.
This is the third time I've submitted this (hence the CC this time).
Hopefully mailman takes it. I've tweaked my SPF records, and I'm hoping
that was the problem.
My sincere apologies if this has gone through and I just haven't seen it
2006 Aug 25
2
Add USB vendor/device id for Belkin F6C120-UNV
I just moved my UPS over from serial to USB and found that I needed to
add it to the hotplug USB list to make things work.
Belkin F6C120-UNV
- Bus 002 Device 004: ID 050d:0912 Belkin Components
It seems to be working OK on 2.0.4 with newhidups. Attached is a patch
which I think should add the appropriate device id's in the right places
to the trunk code.
Jon
-------------- next part
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
2006 Dec 08
2
F6C1500-TW-RK
is there a way to override the productid (like -x productid=1234)
when using newhidups? just thought i'd try it with the F6C1500-TW-RK
over usb.
i was able to get hidups to work using the below settings, but it
provides limited information.
my ups.conf entry:
[belkin]
driver = hidups
port = /dev/usb/hiddev0
and the output of upsc:
gateway:/etc/nut# upsc
2007 Feb 21
5
nut suddenly stopped working...
I almost had nut_2.0.5-3_i386.deb (from
http://packages.debian.org/unstable/admin/nut - installed via dpkg, not via
repository) working:
* problems with getting it to come up during boot
* monitoring via knutclient was OK
* shutdown on low battery worked adequately, if not quite as described)
and newhidups suddenly stopped talking to my Belkin F6C550-AVR . It's only
been in use for a
2006 Oct 17
1
Belkin F6C900-UNV
I have a new Belkin F6C900-UNV. I see that it's not listed in belkin-hid.c
The VendorID is 0x050d like all the Belkin UPSes, and the ProductID is 0x0900.
I haven't had a chance to actually test the development version of nut
yet, since I'm running Fedora Core 6, which still has nut 2.0.3.
`newhidups -DD -a myups` gives the error of:
Checking device (050D/0900) (001/002)
- VendorID:
2006 Jan 12
3
newhidups... at last.
Hi Arnaud, hi all
I wish you all the best for 2006.
Enjoying of some less stressed time, I follow your advice, Arnaud, to
switch our UPS management on the newhidups driver. ( Enfin ! ;)
Our goal is to support (soon) the new MGE ASR ELLIPSE ( and of course also
the old ELLIPSE and EXTREME models ).
I rebuild the libusb-0.1.10a packages to conform to our installation process.
I perform the same
2007 Jul 28
1
nut 2.0.5-3+b1 reports low battery, previous versions do not
Package: nut
Version: 2.0.5-3+b1
Running: Debian Testing
Arch: x86_64
BUG: (the battery is relatively new (6mos) and there have been no recent
power outages)
Jul 28 04:29:44 p34 upsmon[2402]: UPS belkin at localhost battery is low
Jul 28 05:13:15 p34 upsmon[2402]: UPS belkin at localhost battery is low
Jul 28 05:14:05 p34 upsmon[2402]: UPS belkin at localhost battery is low
FIX: (go back to
2007 Mar 27
4
NUT-2.0.5: newhidups on RedHat ES4
Hello everybody,
After succeeded in "tuning" nut-2.0.0's hidups and 2.0.3's newhidups on
customized Linux kernels, we are now facing a new challenge : trying to
install nut-2.0.5 on a RedHat ES4 which is based on a 2.6.9 kernel.
I picked up the 2.0.5 source package and follow the INSTALL doc until step
6. So far so good.
RH ES4 is managed by udev, therefore I presume we
2007 Jun 06
1
New Belkin 550VA UPS not recognized with Nut 2.0.4?
# /lib/nut/newhidups -DDDDD -u nut /dev/usb/hiddev0
Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4)
debug level is '5'
Checking device (0665/5161) (001/003)
- VendorID: 0665
- ProductID: 5161
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: 001
BELKIN 550VA UPS BATTERY BACKUP
Should I be using a different driver?
2008 Jan 12
4
Belkin F6H375 not seen by nut 2.2.1
I recently bought a Belkin F6H375 UPS. It connects to the computer via USB.
Searching the Internet led me to believe that the megatec_usb driver in nut
supports this UPS, however I've been unable to get it to work.
I have this in ups.conf:
[belkinusb]
driver = megatec_usb
port = auto
desc = "Belkin USB"
Here's what happens when I try to use it:
~ #
2007 Feb 23
2
how do I find the association between a usb port and a /dev entry?
I looked through the faq, but couldn't find an answer to this.
I'm trying to configure nut-2.0.4-26 on SuSE linux 10.2.
In ups.conf, I have
[myups]
driver = belkinunv
port = /dev/undefined
desc = "Local UPS"
I'm trying to find out what the port should be set to.
lsusb shows:
Bus 001 Device 005: ID 050d:0980 Belkin Components
Device Descriptor:
bLength
2006 Oct 19
1
Belkin F6H650 on USB port
Hi,
is there a way to use my Belkin F6H650 on the USB port?
I already installed usbhid-support, but neither the hidups worked (reports
"/dev/usb/hiddev0 is not a UPS") nor genericups with upstype=7 and the
hiddev set as device ("ioctl TIOCMSET: Invalid argument") worked.
I have installed the debian sarge package of nut 2.0.1 (2.0.1-4)
Regards,
Philipp
2006 Aug 15
2
newhidups subdriver_matcher incorrectly matches USB hub
I ran into the following issue today and would like some feedback from
the group.
Setup:
I am using a MGE Pulsar Evolution 2200 UPS connected through a Belkin
(F5U218-MOB) 4-Port USB Hub.
Scenario:
The newhidups subdriver_matcher function calls
belkin_subdriver->belkin_claim. The belkin_claim function in
belkin-hid.c matches the VendorID of the hub to Belkin's VendorID
(0x050d), causing
2006 May 07
3
Yet another HID device - Cyberpower AE550
Hope it's not too rude to just drop this here for y'all...
Checking device (0764/0501) (001/005)
- VendorID: 0764
- ProductID: 0501
- Manufacturer: CPS
- Product: UPS AE550
- Serial Number: unknown
This one and their 485 don't provide a load measurement -- the Windows drivers kick it onto battery for a timed period and measure the drain to guess the runtime -- apparently all their