similar to: Fw: trouble setting up kebo-1000d ups (usb)

First off, my apologies for bringing back this thread from the dead (September 2005, http://lists.alioth.debian.org/pipermail/nut-upsdev/2005-September/000150.html), however my problem seems relevant enough that I wondered what happened to this thread as it seems to have died after the message I quote below. Despite the fact that I am having trouble getting my Sweex 1000VA UPS (USB) to work, and

First off, my apologies for bringing back this thread from the dead (September 2005, http://lists.alioth.debian.org/pipermail/nut-upsdev/2005-September/000150.html), however my problem seems relevant enough that I wondered what happened to this thread as it seems to have died after the message I quote below. Despite the fact that I am having trouble getting my Sweex 1000VA UPS (USB) to work, and

Hello nut-upsuser, Hope, that its might be useful for someone: 1. Kebo UPS-600A Driver: genericups UPStype: 7 Config extras: SD = -RTS or SD = -TX (don't know why but both are suitable) 2. Kebo UPS-1200M Driver: fentonups Config extras: none Note: Looks like twin brother of Microlab UPS-1200M :) Driver ask me to report ID string: "Unknown

Folks, I'm fairly new to this whole Linux UPS thingie, but I'd quite like to have a look at getting my UPS to work under Linux and would be grateful for any help in getting a driver. I have a reasonable working knowledge of Linux and software development, and thus am happy to modify config files, alter kernel settings, etc, although I'm no C guru. I have a Kebo UPS-650D, which

Dear list, I'm proud to report that the megatec driver supports the following devices: Infosec XP Pro 1000 Kebo 1200D 'D Series' Thanks for such great software! Cheers, Tamas Csillag

can somebody recall me with we have a such entry in the HAL .fdi, hotplug and udev files? thanks, -- Arnaud

Hi Volker Kuhlmann and Richard Nelson, As both of you are interested in where I got up to with getting my Dynamix 1000 VA UPS working with Linux, here is the details. It works.. But not too well, as the driver still seems to need some work, and is not in the main nut source as far as I know. It also seems to sometimes not respond when it should. The manufacture has uses the same format as

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

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

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

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

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

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

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

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