search for: guestimates

Hi, it's me again. I haven't yet tested my UPS with full load, but I have tried to insert some values in ups.conf, I have kept the example on the blazer_usb driver help page: runtimecal = 240,100,720,50 When I try to start the driver, I receive root at artu:~# upsdrvctl start Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2)

Thanks a lot, I will do it and keep you informed. Best regards Andrea 2017-06-12 12:34 GMT+02:00 Manuel Wolfshant <wolfy at nobugconsulting.ro>: > On 06/12/2017 12:56 PM, Andrea de Lutti wrote: > > > >> > I have also successfully tested the battery... >> > >> > upscmd -uadmin -pups Elit at artu test.battery.start.quick >> >> I would also

> > > root at artu:~# upsc Elit at artu > > Init SSL without certificate database > > battery.voltage: 13.90 > > battery.voltage.high: -1.08 > > battery.voltage.low: -0.87 > > device.type: ups > > driver.name: blazer_usb > > driver.parameter.pollinterval: 2 > > driver.parameter.port: auto > > driver.version: 2.7.2 > >

Hi, I have tried several drivers for make my Elite UPS working. With blazer_usb I can contact it, but I have no informations. This is the best result. OS: Ubuntu Xenial 16.04.2 LTS NUT Version: Nut 2.7.2-4Ubuntu1 (Installed from Ubuntu Software Center) Device name: Elite UPS 800VA (http://www.elit-ups.com/ita/pro_ups.html, discontinued) I can provider their *not working* linux monitoring tool

Hi All, I read rumors of a potential Asterisk 1.4.12 release for last week. I would like to start testing Asterisk 1.4 on Solaris, but, the fix for the segfault in res_features is only in the current development trunk. I would much rather test a release version, and as such, need to wait for the release of 1.4.12, my question is, do we have a guestimate on when it will be released, 1 week, 2

> > hmm, apparently the UPS doesn't close the replies to our queries with > the expected CR and we (I) did not consider that case in nutdrv_qx -- > noted: > https://github.com/networkupstools/nut/issues/441 > > But blazer_usb, being less strict on the terminating CR of Q1 replies, > should work with your device. > > > root at artu:~# upsc Elit at artu > >

Hi, it's me again. I haven't yet tested my UPS with full load, but I have tried to insert some values in ups.conf, I have kept the example on the blazer_usb driver hel page: runtimecal = 240,100,720,50 When I try to start the driver, I receive root at artu:~# upsdrvctl start Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2)

Narrowband (8 kHz), wideband (16 kHz), and ultra-wideband (32 kHz) compression in the same bitstream What is the meaning of this? can i find more information about this somewhere? And what is packel loss concealment, an you enable this somewhere? thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL:

...sing it as a replacement for MP3. But it seems at this point (not certain about this) that Vorbis doesn't really have much optimization implemented yet. By this I mean, for example, implementing something like MMX x86 optimzations in order to speed up the decompression. At this point, rough guestimates suggest that Vorbis uses up about 2x the CPU cycles on a PC to decompress relative to MP3. What are the possibilities and what is the plan? I (we) might actually be able to contribute to this effort, as we might stand to benefit from it. Paul --- >8 ---- List archives: http://www.xiph.org...

So....seems so better... Each time I rebbot, I miss the /var/run/nut folder... root at artu:~# upsdrvctl start Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2) Can't chdir to /var/run/nut: No such file or directory Driver failed to start (exit status=1) root at artu:~# upsd Network UPS Tools upsd 2.7.2 fopen

In some cases, str() does not print the "names" attribute of the object: u <- structure(c(5, 6), names = c("a", "b"), color = "blue") str(u) # atomic [1:2] 5 6 # - attr(*, "color")= chr "blue" Is it a bug or a design choice? Originally asked here: https://stackoverflow.com/q/47185756/6656269

Just trying to debug my theora encoder... just wondering if someone could give me some insight on a few thigns... In the yuv_buffer i'm sending in... i am just setting y_stride = y_width = videoWidth uv_stride = videoWidth/2 y_height = videoHeight uv_height = videoHeight/2 Making the y buffer (width*height) and each of u and v (width*height/4) Am i correct in doing this ? I knwo stride

Thanks mates, as suggested I have added runtimecal = 240,100,720,50 default.battery.voltage.low = 10.4 default.battery.voltage.high = 13.8 (the actual charging voltage) In ups.conf I have also added the startup procedure in rc.local file, everything is fine... I have only to make a deep test. Is there a way to add a NOTIFYMSG value for the battery test? Thank you lots Andrea

Here is the previous email that I sent directly to Charles Lepple. ?I am now sending to the correct email with cc to Charles. ---------------- I am looking at, and trying to understand the rest of the conf files. ?But first want to askabout something from this message:[CODE]root at debian:/home/john# upsdrvctl startNetwork UPS Tools - UPS driver controller 2.7.2Network UPS Tools - Megatec/Q1

Hello list, first of all, I'd like to report that my UPS N-Power MEV-3000LT (http://www.380v.ru/catalogue/micro-ups/mega-vision , in Russian), which is not in the hardware compatibility list, is mostly supported by the blazer_ser driver. I have very strong grounds to believe that this (and other) N-Power UPS'es are rebranded for Russian and Italian markets from their counterparts

2012/2/6 thomas schorpp <thomas.schorpp at googlemail.com>: > Hi, Hi Thomas, > I want the driver report the battery status from ABM charging controllers > -patch attached- : thanks for your patch. since it introduces a new variable (battery.status.abm), I prefer to step back and think to something useful more widely. thus, I'm thinking about a generic

THANKYOUTHANKYOUTHANKYOUTHANKYOU!!!!!! There was a smaller patch posted to the list for lines -1389,9 +1390,10 a couple years ago, it helped some - BUT - it was still buggy. I have a Compaq R3000, I will get this patch integrated pronto and test Note that since the UPS relies on the voltage from the battery pack to determine state of charge, it is quite useful to add in the battery pack

On Mon, Dec 3, 2012 at 8:49 PM, Duncan Sands <baldrick at free.fr> wrote: > Lenny came out in 2009, and > was the latest stable Debian release until 6 months ago, so it's not even > that > old. To put that in perspective, Lenny was released around r64555. That's pretty old. On Mon, Dec 3, 2012 at 8:49 PM, Duncan Sands <baldrick at free.fr> wrote: > What is the

Hello, windows10pro version 1511 os build 10586.29 nut 2.6.5-6 windows binary package device ups: poweron vs 950 when I do testing shutdown it does not shutdown. Thank's. driver debug output: C:\Program Files (x86)\NUT\bin>blazer_usb -DD -a myups Network UPS Tools - Megatec/Q1 protocol USB driver 0.10 (Windows-v2.6.5-5-7-g72f380c) 0.000000 debug level is '2' 0.000000

On Jun 7, 2017, at 12:54 AM, Andrea de Lutti <adelutti at gmail.com> wrote: > > > Hi, I have tried several drivers for make my Elite UPS working. > With blazer_usb I can contact it, but I have no informations. This is the best result. > > OS: Ubuntu Xenial 16.04.2 LTS > NUT Version: Nut 2.7.2-4Ubuntu1 (Installed from Ubuntu Software Center) > Device name: Elite UPS