search for: kebo

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

----- 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 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1...

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

...e 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 was a popular no-brand budget UPS sold here in the UK for a while. I've traced the manufacturer back to http://www.dianxing-kebo.com <http://www.dianxing-kebo.com/> . The UPS has a USB port on the back, but no serial port. It's currently connected via USB to my Linux...

...sdev/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 the original thread was about a Kebo UPS-650D, I think these are based on the same hardware. In fact they even seem to have the exact same VendorID/ProductID, as per: root at router:/usr/local/ups/bin# ./newhidups -DD -u root /dev/hiddev0 Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) debug level is '2...

...sdev/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 the original thread was about a Kebo UPS-650D, I think these are based on the same hardware. In fact they even seem to have the exact same VendorID/ProductID, as per: root at router:/usr/local/ups/bin# ./newhidups -DD -u root /dev/hiddev0 Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) debug level is '2...

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

...he 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 previously discussed Kebo is in there with the same vendorid/productid. May be useful to add a comment there as well (in fact, anywhere Kebo is mentioned), I have a feeling the Kebo may just work with this driver. Here are the diffs for nut_usb.c (svn diff): Index: nut_usb.c ===============================================...

...he 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 previously discussed Kebo is in there with the same vendorid/productid. May be useful to add a comment there as well (in fact, anywhere Kebo is mentioned), I have a feeling the Kebo may just work with this driver. Here are the diffs for nut_usb.c (svn diff): Index: nut_usb.c ===============================================...

...he 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 previously discussed Kebo is in there with the same vendorid/productid. May be useful to add a comment there as well (in fact, anywhere Kebo is mentioned), I have a feeling the Kebo may just work with this driver. Here are the diffs for nut_usb.c (svn diff): Index: nut_usb.c ======================================= --- nut...

...ver.version.internal: 1.5.4 input.frequency: 50.0 input.voltage: 235.0 input.voltage.fault: 165.0 input.voltage.maximum: 244.0 input.voltage.minimum: 218.0 output.voltage: 235.0 output.voltage.nominal: 225.0 ups.beeper.status: enabled ups.delay.shutdown: 0 ups.delay.start: 2 ups.load: 20.0 ups.mfr: KEBO ups.model: UPS-650VA VER7.03 ups.serial: unknown ups.status: OL ups.temperature: 0.0 [root at server etc]# I keep getting errors from the server regarding loosing and reconnecting with the UPS appx every 10 mins. here's the email my server generates... Communications with UPS UPS at loca...

Dear all.... any one can help me??? I am aware of monitoring disk space using nagios (disk partitions with check_disk). Now, I have a situation that I would like to monitor size of an individual file through nagios. e.g /var/lib/mysql/somedatabase/vlog.myd, this file will grow very fast and i would like to monitor if the size of this file crosses 1.5 G. I'm already used 'check_file'

...ds megatec_usb[28806]: Successfully reconnected" In my logs every minute or two. It does however, seem to work. See output below. --------------------------------------- [root at wizards nelg]# upsc myups battery.charge: 100.0 battery.voltage: 28.10 battery.voltage.nominal: 24.0 device.mfr: KEBO device.model: UPS-1000VA VER 1.3 device.serial: unknown device.type: ups driver.name: megatec_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: 0000 driver.parameter.subdriver: krauler driver.parameter.vendorid: 0001 driver.version: 2.4.3 driver.version.in...

...b.c:86: error: conflicting types for 'usb_comm_fail' ../../drivers/lakeview_usb.c:58: error: previous implicit declaration of 'usb_comm_fail' was here Also, I would prefer that we not use the name "Lakeview" for this subdriver. Can we use either "Sweex" or "Kebo"? -- - Charles Lepple

Thanks everyone, My problem is solved. yeah...i'm read the nrpe.pdf. On Wed, Nov 4, 2009 at 3:08 AM, Keith Keller <kkeller at speakeasy.net> wrote: > On Tue, Nov 03, 2009 at 08:08:27PM +0700, kebo jantan wrote: > > I just already. This on client > > > > [root at xmen ~]# ps -ef | grep -i snmp > > root 10505 10172 0 20:06 pts/0 00:00:00 grep -i snmp > > > > [root at cyclop ~]# ps -ef | grep -i nrpe > > root 10507 10172 0 20:06 pts/0 00...

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 I am running FC5 with nut coming from the fc5 extras repositories. I am trying to configure a Gamatronic D-Compact ups. The cable that 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:

...age: 235.0 > input.voltage.fault: 165.0 > input.voltage.maximum: 244.0 > input.voltage.minimum: 218.0 > output.voltage: 235.0 > output.voltage.nominal: 225.0 > ups.beeper.status: enabled > ups.delay.shutdown: 0 > ups.delay.start: 2 > ups.load: 20.0 > ups.mfr: KEBO > ups.model: UPS-650VA VER7.03 > ups.serial: unknown > ups.status: OL > ups.temperature: 0.0 > [ <http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser> root at server etc]# > > > I keep getting errors from the server regarding loosing and reconnecting &...

I want to propose to change the format of the entries in the data/driver.list file. Currently the format is (according to the header) # <manufacturer> <model name> <model extra> <driver> Of these fields, the <model extra> field is not very well defined now. For many devices, it contains information about the communication interface used (serial / USB / SNMP) while

Peter, attached is a proposed patch to fix compilation of generic-hid.c when libusb's usb.h is not in /usr/include (but the -I flag is provided by "libusb-config --cflags"). It fixes the build under OS X, where Fink installs libusb with --prefix=/sw. I changed "usb.h" to <usb.h> so that 'make depend' wouldn't generate a dependency on 'usb.h' with