search for: richcomm

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 find any driver for Richcomm serial interface, there's a richcomm_usb however. I've tried all of the genericups d...

...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: Vendor=0925 ProdID=1234 Rev= 0.01 S: Manufacturer=Richcomm Tech S: Product=UPS2004 C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid E: Ad=81(I) Atr=03(Int.) MxPS= 6 Ivl=10ms So the ups is detected. But when I try to run upsdrvctl -u nut start or upsdrvctl -u root start I get Network UPS Tool...

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 richcomm_usb driver, and everything seems to work all right: service upsdrv start * Starting UPS drivers ... Network UPS Tools - UPS driver controlle...

...rt on the back, but no serial port. It's currently connected via USB to my Linux box. There is Windows software supplied with the UPS which purports to provide information on input/output voltage, load, battery status, etc. The software is called PowerManager and is made by a company called RichComm (website appears to be at www.richcomm.com <http://www.richcomm.com/> ). According to their website, the PowerManager software can control various UPS brands. I've seen reference on Google to it working specifically with Starpower and UPguardS UPS devices as well as the Kebo ones. I...

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...

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...

On Thu, Dec 4, 2008 at 4:51 PM, Arjen de Korte <adkorte-guest at alioth.debian.org> wrote: > Author: adkorte-guest > Date: Thu Dec 4 21:51:28 2008 > New Revision: 1596 > > Log: > Added new richcomm_usb driver based on the lakeview_usb driver (using libusb). Sorry if I wasn't clear - I was advocating *renaming* the lakeview_usb driver to richcomm_usb. Is there another reason to keep both in the tree? I'm pretty sure that this device with the Lakeview Research VID is actually made by...

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 drive...

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:...

Is there a particular reason why we are setting the alternate interface to 0 in drivers/libusb.c? I have seen some documentation which indicates that this should already done by the OS when the device is enumerated. If that is the case, then there is no reason why we should hardcode the alternate interface to 0. If I remove the following code, tripplite_usb seems to work*:

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 very keen on compiling from scratch. tia Iain

Hello and welcome! Just recently there was a trip down the memory lane with another device with Richcomm-based hardware, and ultimately nutdrv_qx driver happened to support that one: https://github.com/networkupstools/nut/issues/2395 Some key take-aways were: * try starting the driver with bumped debug verbosity (e.g. from command line, or using a `debug_min` setting with NUT v2.8.0 and newer) to...

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 no success. All of them report that the UPS is not connected to mains (or randomly switches between states) and no battery information. I also tried all the "various" listed drivers to no ava...

...[FAILED] NUT Starting UPS daemon: Network UPS Tools upsd 2.4.1 not listening on 127.0.0.1 port 3493 [FAILED] ups.conf [Kebo] # driver = newhidups # driver = megatec_usb driver = richcomm_usb port = auto # mfr = Kebo UPS-1000D # vendorid = 0925 # productid = 1234 # subdriver = krauler # subdriver = agiler # bus = "00[1-5]" service upsd start NUT Starting UPS model drivers: Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - Richcomm dry-con...

...to setup NUT 2.6.0 to work with it. blazer_ups driver doesn't recognize the UPS :( The Manufacturer provides 'PowerD' software for linux with installation instractions on a CD (see example below). --------===------- Welcom to PowerManager System! -----===----- Copyright(C) 2001 Richcomm Technologies, Inc. 2001.10 . +-+==================+The Current Time Settings +===========================+-+ System Shutdown Delay Time When AC Power Failed: [250] Sec. System Shutdown Delay Time When Battery Low: [25] Sec. Turn off UPS after System Shutdown: YES +----------------------...

Hello all! Some days ago we received new UPS?Powercom BNT-2000AP with USB interface to replace an old staff and I've spent four last days trying to connect it with NUT. I have a FreeBSD 8.4 box with NUT 2.7.2. # dmesg|grep -i powercom ugen0.3: <POWERCOM Co.,LTD> at usbus0 uhid0: <POWERCOM Co.,LTD HID UPS Battery, class 0/0, rev 1.10/0.01, addr 3> on usbus0 uhid0: <POWERCOM