similar to: [nut-commits] svn commit r1596 - in trunk: drivers man tools

Hi, I'm having a hard time configuring a Mustek Powermust 600VA ups to work via USB with nut. I read somewhere that nut works OK via the rs232 cable, but unfortunately I don't have a COM port in my computer. The kernel detects the ups as an Xbox pad :) and loads the xpad module. I tried running /lib/nut/megatec with different /dev/ttySx but it displays megatec protocol UPS was not

Hi all, i've read a thread about this UPS from Peter van Valderen. He tried to develop a driver for this specific type of UPS. I've downloaded nut-2.2.2 and tried to apply the patches (lakeview.patch & lakeview.v2.patch) but both resulted in rejected chunks. I've tried to ./configure with type lakeview and then a make, but the make command fails. Does anybody has any

Thanks for reply. when i try richcomm_usb or blazer_usb or other usb i get the output of : sudo /lib/nut/usbhid-ups -a trust -DD this is the output: Network UPS Tools - Generic HID driver 0.37 (2.6.4) USB communication driver 0.32 Error: UPS [trust] is for driver richcomm_usb, but I'm usbhid-ups! i tried to set the ups.conf to: [trust] driver = usbhid-ups port = auto vendorid = 0925

I have a Gentoo linux (OpenRC) desktop connected to a UPS, the brand is Vultech, but lsusb gives me this: Bus 003 Device 006: ID 0925:1234 Lakeview Research and I found an article about this hardware here, someone had it working with the richcomm_usb driver: http://verahill.blogspot.it/2012/12/kstar-australia-1500-va-ups-on-debian.html So, I installed nut and configured my UPS to work with the

Hi, are this UPS supported by any other driver than "richcomm_usb". The device works with richcomm_usb, but only signals online, offline etc. Not voltage, batterylevels etc. Bus 006 Device 009: ID 0925:1234 Lakeview Research Bus 006 Device 009: ID 0925:1234 Lakeview Research Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10

Hi, I'm trying to configure my ups with nut which is a locally made one. It uses a rs232 port to talk to the computer and comes with a software called "Powermanager Lite" which is provided by Richcomm and supports Windows, Linux and UNIX. According to the manual it uses the Richcomm circuitry to talk to the computer and uses a drycontact protocol. Unfortunately I couldn't

----- Forwarded Message ---- From: Terry Powling <terrypowling at yahoo.co.uk> To: nut-upsuser at lists.alioth.debian.org Sent: Sat, 27 February, 2010 22:30:05 Subject: trouble setting up kebo-1000d ups (usb) Trying to setup Kebo ups-1000D with usb port. lsusb Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 0925:1234 Lakeview Research Bus 002 Device

I set the ups.conf to: driver = richcomm_usb port = auto now it is connected. There were the vendor variable and product id wrong. These are the variables i get in my OMV service output: device.mfr: Richcomm dry-contact to USB solution device.model: UPS USB MON V1.4 device.serial: unknown device.type: ups driver.name: richcomm_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto

I am a complete novice in this area so please bear with me. I have installed nut version 2.6.2-1 for my debian 64bit system. I am trying to implement 'nut' for a new VIX2120 home UPS and have determined that I need the richcomm_usb driver [usb 0925:1234]. But it is not in /lib/nut although referenced in the documentation (driver.list) How do get hold of a copy? Due to ignorance I am not

--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the

--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the

On Wed, Dec 3, 2008 at 10:19 PM, <clepple+buildbot at ghz.cc> wrote: > The Buildbot has detected a new failure of FreeBSD-6.2-i686. > Full details are available at: > http://buildbot.ghz.cc/public/nut/FreeBSD-6.2-i686/builds/123 Looks like this was the error: ../../drivers/lakeview_usb.c:58: warning: implicit declaration of function `usb_comm_fail'

Heya, first time posting to a mailing list so please excuse me if I do something wrong :) I'm new to NUT and trying to get things working on my TrueNAS, I have a "Vultech 1500VA" UPS which comes with the software "PowerManager II" and it seems to be using the "richcomm_usb" driver. There are 5 devices in the compatibility list and I tried all of them, sadly to

Hallo all. I tried to configure the UPS Trust OXXTRON 1300VA but i didn't succeed. i tried the blazer_usb <http://www.networkupstools.org/docs/man/blazer_usb.html> driver and others but i didn't succeed. My lsusb says Bus 002 Device 005: ID 0925:1234 Lakeview Research Bus 004 Device 002: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 004 Device 004: ID 0424:2228 Standard

Greets... ..just bought a cheap UPS today, works in debian 7.0 wrt nut 2.6.4 using richcomm_usb driver... ....output of upsc..... //// root at debian7:~# upsc starpower at localhost device.mfr: Richcomm dry-contact to USB solution device.model: UPS USB MON V1.4 device.serial: unknown device.type: ups driver.name: richcomm_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto

sent two 0 byte packets to the driver, then it sent 'URB_FUNCTION_SYNC_REST_PIPE_AND_CLEAR_STALL' down the pipe which seems to come back up as well, and then the UPS turned off. I'll play around later with what happens in that regard, although it may be a bit tricky to figure out when the battery is low without having it plugged in ;-) Also, about nut-usbups.rules.in... The

sent two 0 byte packets to the driver, then it sent 'URB_FUNCTION_SYNC_REST_PIPE_AND_CLEAR_STALL' down the pipe which seems to come back up as well, and then the UPS turned off. I'll play around later with what happens in that regard, although it may be a bit tricky to figure out when the battery is low without having it plugged in ;-) Also, about nut-usbups.rules.in... The

sent two 0 byte packets to the driver, then it sent 'URB_FUNCTION_SYNC_REST_PIPE_AND_CLEAR_STALL' down the pipe which seems to come back up as well, and then the UPS turned off. I'll play around later with what happens in that regard, although it may be a bit tricky to figure out when the battery is low without having it plugged in ;-) Also, about nut-usbups.rules.in... The

On Mon, Dec 1, 2008 at 7:43 PM, Alexander Gordeev <agordeev-guest at alioth.debian.org> wrote: > Author: agordeev-guest > Date: Tue Dec 2 00:43:04 2008 > New Revision: 1589 > > Log: > * added lakeview_usb driver. Could we possibly rename this driver before it gets into 2.4? As I mentioned in another thread, Lakeview Research is probably not the manufacturer. Note that

Digitus DN-170014 root at home:/home/scripts# upsc ups device.mfr: Richcomm dry-contact to USB solution device.model: UPS USB MON V1.4 device.serial: unknown device.type: ups driver.name: richcomm_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.6.4 driver.version.internal: 0.04 ups.mfr: Richcomm dry-contact to USB solution ups.model: UPS USB MON V1.4