similar to: Introductions, questions

Hi! How can I find out what files wheren't transferred If I have error: rsync error: some files could not be transferred (code 23) at main.c(1045) running rsync? I've tried "rsync -v[v][v]" but had no success. It wasn't possible to make sure what where the files producing the error. Any idea? rsync is version 2.5.7 -- Thomas

Hey, I am wondering if anyone gotten nut to work with a Tripp Light Smart Pro 2U Rack/Towers (SMART2200RMXL2U). If so which driver did you use, or what driver do you think I should try? Also when trying use a nut driver, do you have to be a nut user? Thanks, Ricky -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I'm running Fedora Core 6 and need to monitor a Tripp Lite SMART2200RMXL2U. I've loaded the nut-2.0.3-2.1 RPM. The UPS is connected via the provided USB cable, and that much appears to work: # dmesg | grep -i tripp hiddev96: USB HID v1.10 Device [Tripp Lite TRIPP LITE SMART2200RMXL2U ] on usb-0000:00:1f.4-2 # lspci | grep -i usb 00:1f.4 USB Controller: Intel Corporation 82801BA/BAM

I've acquired and installed NUT 2.4.1 on a D-Link DNS323 NAS. With exception of Load and Battery Temp readings all works well. A upsc ups at localhost command returns; battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.date: 2001/09/25 battery.mfr.date: 2008/06/05 battery.runtime: 2122 battery.runtime.low: 120 battery.temperature: 3022999999999998800 battery.type:

Hi! Charles. This is the output with 'explore' # ./usbhid-ups -DDDD -u root -x explore -x vendorid=06da -a CENER_LA900_usb Network UPS Tools - Generic HID driver 0.37 (2.6.4) USB communication driver 0.32 0.000000 debug level is '4' 0.000676 upsdrv_initups... 0.288980 Checking device (06DA/0002) (008/004) 0.316956 - VendorID: 06da 0.317057 - ProductID: 0002

On Dec 11, 2014, at 5:43 AM, janc at telefonica.net wrote: > 0.339329 Entering libusb_get_report > 0.342986 Report[get]: (2 bytes) => 01 00 > 0.343085 Path: 008c0001.008c0003, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 0 > 0.343120 Entering libusb_get_report > 0.346953 Report[get]: (2 bytes) => 02 00 > 0.346993 Path: 008c0001.008c0002,

I recently installed NUT 2.4.3 and found that the USB drivers were logging an insane amount of data to syslog: usbhid-ups | daemon debug | Apr 16 18:29:40 | libusb_get_report: No error usbhid-ups | daemon debug | Apr 16 18:29:40 | libusb_get_report: No error usbhid-ups | daemon debug | Apr 16 18:29:40 | libusb_get_report: No error usbhid-ups | daemon debug | Apr 16 18:29:40 |

Hello! First time posting to this list. I recently purchased a Tripp-Lite OMNIPLUS1000LCD from Costco (USA). I have it attached via USB to a Dell computer with Ubuntu 8.04 server (all updates on it). I've gone through a lot of research on google and this list and can't figure out why my UPS will not connect using nut/usbhid-ups. My setup in ups.conf is: ------- [OMNI1000LCD]

These patches allow this device to function in nut.. diff --git a/trunk/drivers/tripplite-hid.c b/new/drivers/tripplite-hid.c index c36da98..dddd13c 100644 --- a/trunk/drivers/tripplite-hid.c +++ b/new/drivers/tripplite-hid.c @@ -71,6 +71,8 @@ static usb_device_id_t tripplite_usb_device_table[] = { { USB_DEVICE(TRIPPLITE_VENDORID, 0x2005), battery_scale_0dot1 }, /* e.g. TrippLite

Hello. I'm new to nut and don't know if I've missed something in setting it up or if my ups isn't quite supported. I'm using these: - svn version of nut (downloaded on 9/13/06) - a tripp lite SMART2200RMXL2U - debian sarge with 2.6.8 kernel - the tripplite_usb driver (newhidups says my ups is not supported) I figured out how to get the device perms correct.

Just built and installed nut 2.4.1 with a usb.conf that looks like [trippb] driver = usbhid-ups port = auto desc = "Tripp Lite SmartPro 2200RMXL2U" The OS is Ubuntu 8.04.2 with kernel version 2.6.24. When trying to start the driver I get $ sudo ./upsdrvctl start Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - Generic HID driver 0.34 (2.4.1)

I'm working on a gentoo server with Nut 2.0.5-r1 and libusb-0.1.12. I originally tried the hidups driver which seemed to work, but produced a large amount of unhandled events. Then I tried the newhidups which told me my ups wasn't supported. When I try using tripplite_usb -u root -DDDD /proc/bus/usb/002/002 I get that there isn't a match. But when I try using tripplite_usb -DDDD

I just noticed what I think is another incorrectly reported value. I found that on the second screen of upsstats.cgi, the one with bar graphs, that the reported battery voltage is 16.0V even though the battery charge is at 100% and the UPS is on AC power. I would have thought it should be more than 25V.

Peter, I have been doing some more testing and I find that if I modify the libusb.c file to set a report size in libusb_get_report to 16 the error messages go away. This is the code as it currently stands: static int libusb_get_report(usb_dev_handle *udev, int ReportId, unsigned char *raw_buf, int ReportSize ) { int ReportSize_test = 16; unsigned char raw_buf_test[ReportSize_test +

Hi, I'm running the latest stable nut (2.4.3). It doesn't appear to provide support for the Tripp Lite SmartOnline SU1000XLA. [sups] driver = usbhid-ups port = auto vendorid = 09ae productid = 4004 4337# upsdrvctl start Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 Using subdriver:

Hello i tried to connect my netys 2000 pr ups to ubuntu 11.10 and i have a problem connecting it. After readin a few post i realized to dianosse the connection. I need help resolving the connextion issue So here is the response to??/lib/nut/usbhid-ups -u root -DDDDD -a netys: Network UPS Tools - Generic HID driver 0.35 (2.6.1) USB communication driver 0.31 ? ?0.000000 ? ? send_to_all: SETINFO

On Dec 4, 2014, at 7:01 AM, janc at telefonica.net wrote: > 0.339848 Report[get]: (2 bytes) => 01 00 > 0.339928 Path: 008c0001.008c0003, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 0 > 0.343852 Report[get]: (2 bytes) => 02 00 > 0.343931 Path: 008c0001.008c0002, Type: Input, ReportID: 0x02, Offset: 0, Size: 1, Value: 0 > 0.343975 Report[buf]: (2 bytes) => 02

On Fri, Mar 28, 2014 at 8:12 AM, Charles Lepple <clepple at gmail.com> wrote: <<Snip>> > > I'll be honest, I haven't really done much with the CGI scripts lately. For debugging values, it is probably better to be closer to the driver. I'd recommend using "upsc" or the driver logs. > > To that end, the .ac.txt and .bat.txt files both show 24.0 V:

I?m a new user of NUT and the OpenUPS - in the past I?ve used APC hardware and apcupsd on Centos 6. I?ve built NUT 2.7.2 from source but used the OpenUPS HID driver v0.4 that?s in github. I?m using firmware version 1.5 on the openups which is the latest published version; I?ve also tried 1.7 which Mini-box sent to me but reverted to the published version. Their support seems a bit slow! I?ve got

On Mar 28, 2014, at 1:52 AM, Bill S wrote: > I just noticed what I think is another incorrectly reported value. I > found that on the second screen of upsstats.cgi, the one with bar > graphs, that the reported battery voltage is 16.0V even though the > battery charge is at 100% and the UPS is on AC power. I would have > thought it should be more than 25V. I'll be honest, I