search for: millivolts

Dear R experts: I need to get this plot, but also with 95% confidence interval bands: hour <- c(1, 2, 3, 4, 5, 6) millivolts <- c(3.5, 5, 7.5, 13, 40, 58) plot(hour, millivolts, xlim=c(1,10), ylim=c(0,1000)) pm <- lm(millivolts ~ poly(hour, 3)) curve(predict(pm, data.frame(hour=x)), add=TRUE) How can the 95% confidence interval band curves be plotted too? Sincerely, James Salsman P.S. I know I shoul...

...ush to market - pick the lowest hanging fruits, backlog the rest) so it was left on a backburner, awaiting a revival in upstream NUT. Another part was more technical, a sort of stalemate in design: many mapping tables in NUT involve data conversions (e.g. date formats, temperature units, integer milliVolts to floating-point Volts, text labels for numeric enum values, etc.) for data transfers from a device or writes back to it. In the current C codebase (*-mib.c, *-hid.c) there are helper methods to which we can point from the tables. An equivalent for DMF, with mappings conveyed by text files, involv...

...s=1862,1,1862 # # The following parameters may be omitted if their default value is acceptible # # # set the receive debounce time in milliseconds # debouncetime=123 # # set the transmit quiet dropoff burst time in milliseconds # bursttime=234 # # set the COR level threshold (specified in tenths of millivolts) # # valid values are {3125,6250,9375,12500,15625,18750,21875,25000} # corthresh=12500 # # Invert COR signal {y,n} # invertcor=y # # set the external tone mode; yes, no, internal {y,n,i} # exttone=y # # Now apply the configuration to the specified channels: # # # We are all done with our channel pa...

Hi, all I have installed TDM400 with 1 FXS and 1 FXP ports. Now I am goig through documentation on how to configure it. It mentions 3 protocols: Loopstart, Groundstart and Koolstart. Which one do I use? Can someone send me sample zaptel.conf file for Australia? This will save me some time and will be used as a working example. Thanks, Rudolf

...st > hanging fruits, backlog the rest) so it was left on a backburner, awaiting > a revival in upstream NUT. > > Another part was more technical, a sort of stalemate in design: many > mapping tables in NUT involve data conversions (e.g. date formats, > temperature units, integer milliVolts to floating-point Volts, text labels > for numeric enum values, etc.) for data transfers from a device or writes > back to it. In the current C codebase (*-mib.c, *-hid.c) there are helper > methods to which we can point from the tables. An equivalent for DMF, with > mappings conveyed b...

Ha! I got several on and off list requests for details, so I'll give a bunch of details here and then maybe I can move this to a wiki page others can help edit. WARNING! WARNING! WARNING! Be careful! My implementation required opening up high power components, and dealing with 120VAC mains power and high currents on 12VDC. If you decide to tackle any of this yourself, you need to understand

Hello, I found out about NUT just days ago while searching for a solution for my home setup. After some digging through the interwebs, I come to you with questions. I'm putting together a DIY 12V UPS, very similar to what this guy did: [1] https://baldpenguin.blogspot.com/2015/10/diy-12v-ups-for-home-network-equipment.html The objective is to keep a bunch of mini PCs and network gear

Looks very great, thanks for writing this! I gather you'd port this to the Wiki page you've started, too? A couple of comments: > So I run a NUT server on a Raspberry PI which is connected via USB to my DIY-NAS Arduino. DIY-UPS? > See drivers/arduino-hid.c for the list of supported IDs... Since NUT v2.8.1 [PR #1369], the `usbhid-ups` driver allows the user to specify a

On 5/16/24 08:59, Jim Klimov via Nut-upsuser wrote: > I agree with earlier posters, such documentation can help future > tinkerers. There is probably more than just one to hold the hand and > walk through the ordeals :) > > Perhaps a new page at https://github.com/networkupstools/nut/wiki > <https://github.com/networkupstools/nut/wiki> can be a good location... >