search for: p34

Hello, I use the following in my ups.conf: # USB: [apc] driver = usbhid-ups port = auto desc = "APC 1500VA" pollfreq = 5 On my new motherboard (an Intel DP55KG), every once and awhile I get this: Broadcast Message from nut at box.com (somewhere) at 17:48 ... Communications with UPS apc at localhost lost Broadcast Message from nut at box.com

Package: nut Version: 2.0.5-3+b1 Running: Debian Testing Arch: x86_64 BUG: (the battery is relatively new (6mos) and there have been no recent power outages) Jul 28 04:29:44 p34 upsmon[2402]: UPS belkin at localhost battery is low Jul 28 05:13:15 p34 upsmon[2402]: UPS belkin at localhost battery is low Jul 28 05:14:05 p34 upsmon[2402]: UPS belkin at localhost battery is low FIX: (go back to old version for now and enable a hold on the package) # dpkg -l | grep -i nut ii...

...h.debian.org/pipermail/nut-upsuser/2007-July/003014.html http://permalink.gmane.org/gmane.comp.monitoring.nut.user/2552 I still have this problem: $ dpkg -l | grep -i nut ii nut 2.2.0-2 The core system I thought this bug was fixed :( syslog:Dec 10 18:56:15 p34 upsmon[2672]: UPS belkin at localhost battery is low syslog:Dec 10 18:57:05 p34 upsmon[2672]: UPS belkin at localhost battery is low syslog:Dec 10 19:01:00 p34 upsmon[2672]: UPS belkin at localhost battery is low Any work-arounds available if I want to run 2.2.0-2? This was a bug one of the de...

When I disconnect my UPS from the wall, I have to wait 15-30 seconds before the USB drier 'polls' this information and tells me that the UPS is on battery power (via knutclient or syslog via nut): ups@p34 POWER ALERT on Fri Jan 26 12:49:29 EST 2007 With a serial connection, I would get the alerts IMMEDIATELY (0.5-1 seconds) after disconnecting the UPS. My new machine does not have a serial port built-in, only a serial header, and of course does not come with an included cable, so I chose to use...

...o... Got to reconnect! upsdrv_updateinfo... Got to reconnect! Can't retrieve Report 19: Broken pipe upsdrv_updateinfo... Got to reconnect! Can't retrieve Report 15: Broken pipe upsdrv_updateinfo... Got to reconnect! upsdrv_updateinfo... # From the system logs: Broadcast Message from nut at p34.internal.lan (somewhere) at 6:01 ... Communications with UPS apc at localhost lost Broadcast Message from nut at p34.internal.lan (somewhere) at 6:02 ... Communications with UPS apc at localhost established Broadcast Message from nut at p34.internal.lan (somewhere) at 6:0...

-> ups at p34 POWER ALERT on Sat Aug 25 07:40:01 EDT 2007 -> UPS belkin at localhost battery is low The last good version is 2.0.4, someone e-mailed me from this list before exactly why this happened it was about ignoring bad events from the usb-dev subsystem/kernel but I guess my question is this going to...

Hello, Dist: Debian Testing Kernel: 2.6.38.3 Software: nut 2.6.0-1 I believe this is a chipset bug, are there any plans for a workaround? The messages have changed over the kernel versions for this problem, but the problem itself still exists: Apr 21 09:17:25 p34 usbhid-ups[3737]: libusb_get_string: error sending control message: Broken pipe Apr 21 09:44:20 p34 usbhid-ups[3737]: libusb_get_string: error sending control message: Broken pipe Error from 2009 (still a problem) http://lists.alioth.debian.org/pipermail/nut-upsuser/2009-October/005530.html This...

Dear Sir , Can anyone tell me how to upload new ups driver to NUT website ? Best regards, Bluefish [cid:image001.jpg at 01D07C3E.C4ADB780] ?? ?? ?? ?????? ?????(??)???? ??????????107?????467?(?????) ??????5?1?A?2?4? 1-4F, Building 5, YuSheng lndustrial Park, No.467, Section Xixiang, National Highway 107, Xixiang, Bao An District, Shenzhen, China Tel: + 86-755-8601-6601 Ext. 8598 Fax:

...p10=g(-4,0) p11=g(-4,0.5) p12=g(-4,1) p13=g(-4,2) p14=g(-4,3) p15=g(-4,4) p16=g(-4,5) p17=g(-3,-.5) p18=g(-3,0) p19=g(-3,.5) p20=g(-3,1) p21=g(-3,2) p22=g(-3,3) p23=g(-3,4) p24=g(-3,5) p25=g(-2,-.5) p26=g(-2,0) p27=g(-2,.5) p28=g(-2,1) p29=g(-2,2) p30=g(-2,3) p31=g(-2,4) p32=g(-2,5) p33=g(-1,-.5) p34=g(-1,0) p35=g(-1,.5) p36=g(-1,1) p37=g(-1,2) p38=g(-1,3) p39=g(-1,4) p40=g(-1,5) p41=g(-0.5,-0.5) p42=g(-0.5,0) p43=g(-0.5,0.5) p44=g(-0.5,1) p45=g(-0.5,2) p46=g(-0.5,3) p47=g(-0.5,4) p48=g(-0.5,5) p49=g(0,-0.5) p50=g(0,0) p51=g(0,.5) p52=g(0,1) p53=g(0,2) p54=g(0,3) p55=g(0,4) p56=g(0,5) p57=g(0.5...

...nce you appear to be working for Voltronic Power, I'd like to take the chance to ask if it's possible for you to release (and give us permission to redistribuite) the protocols adopted by your various devices (present and past): we have already done some work [4] and support for P15/P16/P30/P34/P35/P36 protocols is under way, too.. but we still lack some information and, obviously, knowing the protocols in full directly from the manufacturer would be a lot better (not to mention the huge amount of time I would save in reverse engineering...). [1] https://github.com/networkupstools/nut/...

...nce you appear to be working for Voltronic Power, I'd like to take the chance to ask if it's possible for you to release (and give us permission to redistribuite) the protocols adopted by your various devices (present and past): we have already done some work [4] and support for P15/P16/P30/P34/P35/P36 protocols is under way, too.. but we still lack some information and, obviously, knowing the protocols in full directly from the manufacturer would be a lot better (not to mention the huge amount of time I would save in reverse engineering...). [1] https://github.com/networkupstools/nut/...

...I have two between subject variables: location (2 different locations) and age group (young and old), and one within-subject variable: valence (positive, neutral, negative). I am looking at an Stevens(one between, two within) in Notes on the use of R for psychology experiments and questionnaires (P34 in this article). In Stevens' example, he first create a matrix and put the data in a multivariate format using cbind.data.frame() function. Ela.mat <- matrix (c(19,.....28), nrow=16, byrow=T) Ela.mul <- cbind.data.frame(subj=1:16, gp=factor(rep(1:2,rep(8,2))), Ela.mat) dimnames(Ela.mu...

...working for Voltronic Power, > I'd like to take the chance to ask if it's possible for you to release > (and give us permission to redistribuite) the protocols adopted by > your various devices (present and past): we have already done some > work [4] and support for P15/P16/P30/P34/P35/P36 protocols is under > way, too.. but we still lack some information and, obviously, knowing > the protocols in full directly from the manufacturer would be a lot > better (not to mention the huge amount of time I would save in reverse > engineering...). > > > [1] https:/...

...NG_5_0, 5.0-RELEASE-p16) 2003-09-25 13:34:14 UTC (RELENG_4_8, 4.8-RELEASE-p10) 2003-09-25 13:34:31 UTC (RELENG_4_7, 4.7-RELEASE-p20) 2003-09-25 13:34:52 UTC (RELENG_4_6, 4.6-RELEASE-p23) 2003-09-25 13:35:18 UTC (RELENG_4_5, 4.5-RELEASE-p34) 2003-09-25 13:35:33 UTC (RELENG_4_4, 4.4-RELEASE-p44) 2003-09-25 13:35:48 UTC (RELENG_4_3, 4.3-RELEASE-p40) FreeBSD only: NO For general information regarding FreeBSD Security Advisories, including descriptions of the fields above, security branches, and the foll...

...tronic Power, >> I'd like to take the chance to ask if it's possible for you to release >> (and give us permission to redistribuite) the protocols adopted by >> your various devices (present and past): we have already done some >> work [4] and support for P15/P16/P30/P34/P35/P36 protocols is under >> way, too.. but we still lack some information and, obviously, knowing >> the protocols in full directly from the manufacturer would be a lot >> better (not to mention the huge amount of time I would save in reverse >> engineering...). >> &...

...TC (RELENG_6_0, 6.0-RELEASE-p12) 2006-09-19 14:06:21 UTC (RELENG_5, 5.5-STABLE) 2006-09-19 14:07:13 UTC (RELENG_5_5, 5.5-RELEASE-p5) 2006-09-19 14:08:10 UTC (RELENG_5_4, 5.4-RELEASE-p19) 2006-09-19 14:09:09 UTC (RELENG_5_3, 5.3-RELEASE-p34) 2006-09-19 14:11:35 UTC (RELENG_4, 4.11-STABLE) 2006-09-19 14:13:53 UTC (RELENG_4_11, 4.11-RELEASE-p22) CVE Name: CVE-2006-4334, CVE-2006-4335, CVE-2006-4336, CVE-2006-4337, CVE-2006-4338 For general information regarding FreeBSD Security Advi...

...TC (RELENG_6_0, 6.0-RELEASE-p12) 2006-09-19 14:06:21 UTC (RELENG_5, 5.5-STABLE) 2006-09-19 14:07:13 UTC (RELENG_5_5, 5.5-RELEASE-p5) 2006-09-19 14:08:10 UTC (RELENG_5_4, 5.4-RELEASE-p19) 2006-09-19 14:09:09 UTC (RELENG_5_3, 5.3-RELEASE-p34) 2006-09-19 14:11:35 UTC (RELENG_4, 4.11-STABLE) 2006-09-19 14:13:53 UTC (RELENG_4_11, 4.11-RELEASE-p22) CVE Name: CVE-2006-4334, CVE-2006-4335, CVE-2006-4336, CVE-2006-4337, CVE-2006-4338 For general information regarding FreeBSD Security Advi...

...TC (RELENG_6_0, 6.0-RELEASE-p12) 2006-09-19 14:06:21 UTC (RELENG_5, 5.5-STABLE) 2006-09-19 14:07:13 UTC (RELENG_5_5, 5.5-RELEASE-p5) 2006-09-19 14:08:10 UTC (RELENG_5_4, 5.4-RELEASE-p19) 2006-09-19 14:09:09 UTC (RELENG_5_3, 5.3-RELEASE-p34) 2006-09-19 14:11:35 UTC (RELENG_4, 4.11-STABLE) 2006-09-19 14:13:53 UTC (RELENG_4_11, 4.11-RELEASE-p22) CVE Name: CVE-2006-4334, CVE-2006-4335, CVE-2006-4336, CVE-2006-4337, CVE-2006-4338 For general information regarding FreeBSD Security Advi...

...NG_5_0, 5.0-RELEASE-p16) 2003-09-25 13:34:14 UTC (RELENG_4_8, 4.8-RELEASE-p10) 2003-09-25 13:34:31 UTC (RELENG_4_7, 4.7-RELEASE-p20) 2003-09-25 13:34:52 UTC (RELENG_4_6, 4.6-RELEASE-p23) 2003-09-25 13:35:18 UTC (RELENG_4_5, 4.5-RELEASE-p34) 2003-09-25 13:35:33 UTC (RELENG_4_4, 4.4-RELEASE-p44) 2003-09-25 13:35:48 UTC (RELENG_4_3, 4.3-RELEASE-p40) FreeBSD only: NO For general information regarding FreeBSD Security Advisories, including descriptions of the fields above, security branches, and the foll...

...t;>> I'd like to take the chance to ask if it's possible for you to release >>> (and give us permission to redistribuite) the protocols adopted by >>> your various devices (present and past): we have already done some >>> work [4] and support for P15/P16/P30/P34/P35/P36 protocols is under >>> way, too.. but we still lack some information and, obviously, knowing >>> the protocols in full directly from the manufacturer would be a lot >>> better (not to mention the huge amount of time I would save in reverse >>> engineering...