search for: variac

On 5/21/2017 10:39 AM, Charles Lepple wrote: > Mike, > > Thanks for the info. I have enough to add an entry to the DDL, but I have a few more questions inline. > > On May 14, 2017, at 1:21 PM, Mike wrote: >> >> [updated] >> >> OpenBSD 6.1/amd64 >> NUT 2.7.4p0 (from OpenBSD package) >> >> >> Results of upsc: >> >>

...need to do a bit of testing to determine if, for instance, the ACPresent bit could be used for this purpose, or if it needs to be combined with other bits. (The UPS.Output.ff010043 path is non-standard, so maybe this would tell us something about this case, too.) It might be helpful to test with a variac, and ramp the voltage up and down to see which bits change as the UPS goes from battery to boost to passthrough. -- Charles Lepple clepple at gmail

...000 Error: too many non-option arguments. Try -h for help. so I added a -a parameter to point to the ups name configured in ups.conf, and that worked. The output from that command is zipped and attached. [snip] > > If it were the input voltage, I would recommend experimenting with a variac, but you are probably not going to see much of a range on the output before the buck/boost circuits kick in. So it's still an option, but it might not be worth the trouble for an UPS in service (or if you don't have a variac handy). Here's the results of the varying voltage tests: in...

Dear helpers, does anyone know a function to fit a model with: - y mean that is regressed on a set of explanatory variables - y variace behaving as a garch or as a garch in mean Thank you so much for your help, Carlo

...t; > > It's looking as if the output.voltage value is not correct. ;) Found this thread: https://github.com/networkupstools/nut/issues/337#issuecomment-257284089 Unfortunately, I am not seeing a common factor here. If it were the input voltage, I would recommend experimenting with a variac, but you are probably not going to see much of a range on the output before the buck/boost circuits kick in. So it's still an option, but it might not be worth the trouble for an UPS in service (or if you don't have a variac handy). > Results from upsrw: Thanks! Committed (though the w...

...figured in > ups.conf, and that worked. The output from that command is zipped and > attached. Heh, that's embarrassing that the "-a" has been missing for so long. Noted. > > [snip] >> >> If it were the input voltage, I would recommend experimenting with a variac, but you are probably not going to see much of a range on the output before the buck/boost circuits kick in. So it's still an option, but it might not be worth the trouble for an UPS in service (or if you don't have a variac handy). > > > Here's the results of the varying vol...

...an. > > It could be the 0-9 index of the user-settable voltage limits, page 19 of: > http://www.gruberpower.com/pdf-files/Best%20Power%20Patriot%20Pro%20II%20User%20Manual.pdf > Could you try and change it and see what happens to the 'M' reply? It seems to match. I can do some variac testing some other time, but the current setting (0) corresponds to the LED pattern for the first entry in the table. When I incremented it a few times, it increased. > Or maybe it's a status of some sort: the driver now keeps querying the > UPS with 'M', so if you could try and...

...s of reference. In earlier tests, I did note that when the unit was placed on battery that the upsstats.cgi screen reported that the input voltage from 119V to 120V and did not go to zero as I expected it would. I also noted that the output voltage remained at 136V. I do have a old General Radio variac kicking around with no line cord or sockets that I can cobble something together with if these files do not provide enough data. On Wed, Mar 26, 2014 at 9:22 AM, Charles Lepple <clepple at gmail.com> wrote: > On Mar 23, 2014, at 11:12 PM, Bill S wrote: > >> The output of the driv...

...$transect) flormat=as.matrix(florabund) abund.nb <-manyglm(flormat~transect*vegtype, family="nagative.binomial") predict(abund.nb, type= "response") ##Checking Model Assumptions plot(abund.nb) meanvar.plot(flormat~transect, col=as.numeric (vegtype)) #direct plot of mean-variace relationship anova(abund.nb, p.uni="adjusted") It's after running the last code line [>anova(abund.nb, p.uni="adjusted")], when I get thiis error: Error in XvarIn[nterms - i, varseq > i + minterm] <- 0 : (subscript) logical subscript too long Any idea what...

I recently purchased a CyberPower CP1500PFCLCD UPS as a replacement UPS for a headless server running Slackware 14.1 with the 3.10.7 kernel. I then downloaded the NUT 2.7.1 tarball on the server and following the directions installed the software. The installation went well and the UPS will shutdown the server using the forced down test and then it powers back up as it should. The

...could be the 0-9 index of the user-settable voltage limits, page 19 of: >> http://www.gruberpower.com/pdf-files/Best%20Power%20Patriot%20Pro%20II%20User%20Manual.pdf >> Could you try and change it and see what happens to the 'M' reply? > > It seems to match. I can do some variac testing some other time, but the current setting (0) corresponds to the LED pattern for the first entry in the table. When I incremented it a few times, it increased. > Implemented: https://github.com/zykh/nut/tree/bestups Before I merge it (well.. provided that it works..), I'd like to kn...

> Sure enough, it turned off after about 30 seconds (t=228). I unplugged it for about five seconds, and it came back on three minutes after I plugged it back in. However, the bypass bit inversion might be responsible for this: > > 228.304623 send: 'Q1' > 228.515426 read: '(119.0 119.0 000.0 000 60.0 13.5 XX.X 00001010' > 228.515494 ups_infoval_set: non

On Nov 1, 2014, at 9:28 PM, hyouko at gmail.com wrote: > Provided that the subdriver works, I'd like to see, if possible, the logs of: > - driver startup > - a command that succeeds > - a command that fails > - q1 when online and all's ok > - q1 on battery > - setting pins_shutdown_mode Attached is a log of most of these conditions. Looks like reading the status for

Sorry for my delay, I've only just read this mail. At first glance the driver looks like it should work, I will test it tomorrow (if possible) and let you know. I'll also give a reply to your questions. Many thanks for the work you've already put into this. -------------------------------------------------- From: <hyouko at gmail.com> Sent: Monday, June 30, 2014 12:42 AM To:

Sorry for the huge delay and thanks Charles for taking care of this topic. >> I'm running OpenSuse 13.1 and I have a Lupus 500 USB (Fideltronik) >> >> After quite a bit of playing around I managed to get the status of the UPS using the blazer_usb driver and running NUT 2.6.5. >> But unfortunately none of the Instcmds such as load.off etc. worked. > > Can you post

...hutdown you can't disable the beeper. I've tested quite a lot and all the status messages appear logical, just in case here is my interpretation of the ups status bits (8 bits) MSB first 7: Utility failure 6: Battery low 5: Not 100% certain but probably bypass mode ( I haven't got a variac to mess about with my supply to test this) 4: UPS alarm (alarm shows on ups LCD display when this bit is set. It comes on when battery is critically low or when ups is overloaded) 3: Haven't a clue it's set all the time, nothing seems to change it 2: Haven't a clue it's always off...