similar to: Trust UPS Oxxtron 1300VA (17679)

On Jan 22, 2016, at 6:02 PM, Andreas Cattelan <ilmondodiwit at gmail.com> 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:

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

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

Hello, I have just installed nut_2.6.0 from Debian testing, do anyone know the correct driver for this ups? The blazer_usb don't report battery-charge, the bundled software report charge and runtime. root at pluto<~>upsc powerwalker battery.voltage: 40.86 battery.voltage.nominal: 36.0 beeper.status: enabled device.mfr: device.model: HV 1K device.type: ups driver.name: blazer_usb

I am running dovecot 2.1.7 on Debian Squeeze 64 bit, config information at the end of the email. I am working on a Kerberos/GSSAPI based setup that requires cross-realm authentication. I have regular GSSAPI working, I can log in using pam_krb5 with password based logins or with the GSSAPI support when using a kerberos ticket in the default realm. However when I attempt to authenticate using

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

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

On Wed, Dec 3, 2008 at 4:05 PM, Arjen de Korte <nut+devel at de-korte.org> wrote: > Citeren Charles Lepple <clepple at gmail.com>: > >> Note that this is the same VID/PID as on this example on the Lakeview >> Research home page: >> >> http://www.lvr.com/usb_on_a_budget.htm >> >> We can include the name "Lakeview Research" in the

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

Arnaud, should we move tools/ up to the beginning of the subdirectory list? It seems that it is writing some *.in files during 'make dist', which should undergo variable substitution. (There will probably be other dependency issues to resolve, but that would be the first step.) On a related note, I would like to add some code to nut-usbinfo.pl to blacklist bogus vendor IDs (e.g. 0x0000,

Hi Rok, I retired from working on NUT a few months ago, so I don't have the most up-to-date info. But the guys on the nut-upsdev mailing list (cc'd above) are very helpful. Both of your devices (or nearly identical ones) have been seen on the mailing lists before. The Sweex was first mentioned in a message by Eli Wapniarski on 14 Jun 2006 on nut-upsuser, and was most recently discussed

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

Does asterisk support using an H.323 provider for outgoing calls? From everything I have found, it looks like it does. However, I have had no success in getting it to work. I would really appreciate if somebody could give me a hand. I am using the channel that comes with asterisk. I have also tried using the channel from inaccessnetoworks but have not had any more success. My provider

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'

Hello guys, Please help me to resolve the issue. I bought 'SVEN Power Pro+ 500 USB' UPS few days ago and tried 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!

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

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

I'm totally new to this, so heres hoping i can give you the info you need ... I have a new Trust usb UPS hooked up to my iMac (running Lion) The UPS shows up in the system report with the following info: Product ID: 0x0003 Vendor ID: 0x06da (Phoenixtec Power Co., Ltd.) Version: 5.01 Speed: Up to 1.5 Mb/sec Manufacturer: CTN Location ID: 0xfa144400 / 10 Current Available (mA):

I'm totally new to this, so heres hoping i can give you the info you need ... I have a new Trust usb UPS hooked up to my iMac (running Lion) The UPS shows up in the system report with the following info: Product ID: 0x0003 Vendor ID: 0x06da (Phoenixtec Power Co., Ltd.) Version: 5.01 Speed: Up to 1.5 Mb/sec Manufacturer: CTN Location ID: 0xfa144400 / 10 Current Available (mA):