search for: richcomm_usb

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

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

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

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 ups.productid: 1234 ups.serial: unknown ups.status: OL ups.vendorid: 0925 finally tested the shutdown and it wo...

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

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

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

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

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

..."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 drivers and the megatec driver even a USB to Serial converter cable (Prolific chipset) but no luck. Any suggestion about which driver to choose or what I'm doing wrong? I'm using NUT on FreeNAS 0.7.2 which uses NUT 2.60. Below is the link t...

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

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

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

...om> wrote: > > I tried to configure the UPS Trust OXXTRON 1300VA but i didn't succeed. > > i tried the blazer_usb driver and others but i didn't succeed. > > > My lsusb says > > Bus 002 Device 005: ID 0925:1234 Lakeview Research > It might work with richcomm_usb: https://lists.alioth.debian.org/pipermail/nut-upsuser/2012-April/007551.html but that USB ID on a production device isn't very useful (the equivalent of the 555-1212 phone number). Also, richcomm_usb does not provide much information - it is similar to genericups (OL/OB/LB). -- Charles Lep...

Hello all! I get a compilation error with '--without-snmp' option. Can someone help please? Thanks in advance Sergey Env: === 1. Nut-2.6.2 2. gcc-3.3.6 ----- ./configure -q --prefix=/usr --with-drivers=richcomm_usb --with-user=upsd --with-group=upsd --with-cgi --with-cgipath=/www/cgi-bin --with-htmlpath=/www --with-statepath=/var/state/ups --without-wrap --without-snmp --without-serial --without-ssl --without-neon --without-ipmi --without-freeipmi Configuration summary: ====================== build serial dr...

...ixtec Power Co., Ltd.) Version: 5.01 Speed: Up to 1.5 Mb/sec Manufacturer: CTN Location ID: 0xfa144400 / 10 Current Available (mA): 500 Current Required (mA): 100 I have tried the following NUT drivers (all of them?), but none can connect to the UPS: blazer_usb usbhid-ups bcmxcp_usb richcomm_usb tripplite_usb Any suggestions? Thanks in advance, David -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20110826/b474d3db/attachment.html>

...ixtec Power Co., Ltd.) Version: 5.01 Speed: Up to 1.5 Mb/sec Manufacturer: CTN Location ID: 0xfa144400 / 10 Current Available (mA): 500 Current Required (mA): 100 I have tried the following NUT drivers (all of them?), but none can connect to the UPS: blazer_usb usbhid-ups bcmxcp_usb richcomm_usb tripplite_usb Any suggestions? Thanks in advance, David -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20110826/b474d3db/attachment.html>

...output (attached). I interrupted the process, but it > continues looping forever. > > Kind regards. > <debug.log> There is a very proof-of-concept-y driver (nutdrv_atcl_usb) in the atcl branch in GitHub. We can probably remove a bunch of the retry loops that it inherited from richcomm_usb. There should also be a tarball here fairly soon: http://buildbot.networkupstools.org/public/nut/builders/Debian-x64-gcc/builds/115 -- Charles Lepple clepple at gmail

...upscode2 >> bestfcom isbmex optiups upsd >> bestfortress ivtscd powercom upsmon >> bestuferrups liebert powerpanel usbhid-ups >> bestups liebert-esp2 rhino victronups >> blazer_ser masterguard richcomm_usb >> " >> >> My lsusb is showing "Bus 001 Device 008: ID 04e2:1410 Exar Corp. >> XR21V1410 USB-UART IC" >> >> And i don't know what to do next. >> >> Fatgear >> >> -------------- next part -------------- An HTML attachment...

...bestfcom????? isbmex??????? optiups????????? upsd >> bestfortress? ivtscd??????? powercom???????? upsmon >> bestuferrups? liebert?????? powerpanel usbhid-ups >> bestups?????? liebert-esp2? rhino victronups >> blazer_ser??? masterguard?? richcomm_usb >> " >> >> My lsusb is showing "Bus 001 Device 008: ID 04e2:1410 Exar Corp. >> XR21V1410 USB-UART IC" >> >> And i don't know what to do next. >> >> Fatgear >> -------------- next part --...