similar to: nut-git reporting 24 Volts with CP1350PFCLCD -- is that correct?

nut 2.7.2 linux 3.18.7 CyberPower CP1350PFCLCD The LCD shows the same for input and output, my multimeter also matches the input voltage. But nut is giving me different numbers. How do I debug this? input.voltage: 122.0 output.voltage: 138.0 I still need to check what it does on battery and what the other readings are. But the voltage stuck out at me.

[please use reply-all to include the list. thanks!] > On Nov 26, 2015, at 9:47 AM, Weedy <weedy2887 at gmail.com> wrote: > > nut 2.7.2 > linux 3.18.7 > CyberPower CP1350PFCLCD > > The LCD shows the same for input and output, my multimeter also > matches the input voltage. > But nut is giving me different numbers. How do I debug this? > > input.voltage:

Hi folks, new to list... nut 2.7.2 on Ubuntu 16.04 with Cyberpowersystems CP1350PFCLCD. After performing upscmd cp1350 at localhost test.battery.start.quick the result was "Done and warning". I searched through syslog but could find no additional information. What is the warning? Battery charge was 100% before test was performed. Here's the full output from upsc after test:

On Sat, Oct 31, 2020 at 2:42 PM Tim Dawson <tadawson at tpcsvc.com> wrote: > I'm going to guess that since your test runtime of 305 is very close to > the low limit of 300, that's the warning. Not yet a fail, but very, very > close. > I tried setting override.battery.runtime.low = 60 in ups.conf, and waited for the UPS to reach 100% charge, and ups.status to report only

On Saturday 31 October 2020 20:13:48 Rick Dicaire wrote: > On Sat, Oct 31, 2020 at 2:42 PM Tim Dawson <tadawson at tpcsvc.com> wrote: > > I'm going to guess that since your test runtime of 305 is very close > > to the low limit of 300, that's the warning. Not yet a fail, but > > very, very close. > > I tried setting > override.battery.runtime.low = 60

I'm going to guess that since your test runtime of 305 is very close to the low limit of 300, that's the warning. Not yet a fail, but very, very close. On October 31, 2020 11:41:39 AM CDT, Rick Dicaire <kritek at gmail.com> wrote: >Hi folks, new to list... >nut 2.7.2 on Ubuntu 16.04 with Cyberpowersystems CP1350PFCLCD. > >After performing upscmd cp1350 at localhost

Thanks Cristoph, I have that code in my backend, but unless I do the following, the registers are never considered 'live' into the call. / Handle a function call let isCall = 1, Defs = [ R0, R1, R2, R3, R4, R5, R6, R7, R8, R9, R10, R11, R12, R13, R14, R15, R16, R17, R18, R19, R20, R21, R22, R23, R24, R25, R26, R27, R28, R29, R30, R31, R32, R33, R34, R35, R36, R37, R38, R39, R40, R41,

Hi Micah, > In X86InstrInfo.td for Call Instructions, it mentions that Uses for > argument registers are added manually. Can someone point me to the > location where they are added as the comment doesn't reference a > where or how? the register uses are added by the function X86TargetLowering::LowerCall() during the DAG Lowering phase. This is the relevant code segment: // Add

Does anyone have any recommendations on how to connect 160 analogue phones to an asterisk PBX? Background information: A client wishes to replace their current PBX with a new VoIP system. Currently they have 2 PRIs. I intent to set up 2 asterisk PBXs with Debian GNU/Linux on raided drives. These drives will be mounted only read-only to recover gracefully from power-cycles. I am considering 2

I was doing some testing with the 2.6.0-1 beta Windows installer and a Cyber Power CP1350PFCLCD UPS, and ran into an infinite loop in the usbhid-ups driver if the UPS is lost on the UPS bus. This is on a Windows XP SP3 system. USB device access is via libusb 1.2.4.0 (driver mode, not filter) in case that matters. Everything seems to work just fine so far while the UPS is connected (so kudos,

Citeren "David C. Rankin" <drankinatty at suddenlinkmail.com>: > Discharged battery.voltage: > > 17.4 Volts - (indicated on shutdown, discharging battery.charge 77%) > 16.9 Volts - (indicated on shutdown, discharging battery.charge 51%%) > 16.6 Volts - (indicated on shutdown, discharging battery.charge 33%) > > -- Shutdown Occurred at < 3% -- Battery

Nut Developers, I have unsuccessfully tried to solve a problem with the voltage value on my Cyber Power UPS CP1000AVRLCD. Something is wrong with the battery voltage calculation. It always reads around 20 volts with that's nuts (pardon the pun). Right now: battery.voltage : 20.3 You can take a look for yourself at http://www.3111skyline.com/nutindex.html Is there a parameter I can check

"Kelly Uehling" <kellyu@mwcad.com> writes in comp.protocols.smb: >This has been an ongoing problem with Unix SMB file servers. While perusing >the autodesk.autocad.network newsgroup, I came across someone else having >the same problem with a Syntax 5.3 server. Syntax's response was as follows: > > By Syntax Technical Support (Support) on Thursday, September

Response in-line: Op 22-04-17 om 13:22 schreef Karol Herbst: > info.min and info.max doesn't always represent the actual voltage range we > can use. Do the same as with the entry based volting. > > Fixes "ERROR: Can't get value of subfeature in0_min: Can't read" errors > in sensors. > > Signed-off-by: Karol Herbst <karolherbst at gmail.com> >

info.min and info.max doesn't always represent the actual voltage range we can use. Do the same as with the entry based volting. Fixes "ERROR: Can't get value of subfeature in0_min: Can't read" errors in sensors. Signed-off-by: Karol Herbst <karolherbst at gmail.com> --- drm/nouveau/nvkm/subdev/volt/base.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)

Hi, guys, I have add devid support for EFI, (not putback yet) and test it with a zfs mirror, now the mirror can recover even a usb harddisk is unplugged and replugged into a different usb port. But there is still something need to improve. I''m far from zfs expert, correct me if I''m wrong. First, zfs should sense the hotplug event. I use zfs status to check the status of the

On Mon, Dec 1, 2014 at 3:38 PM, Terje Bergström <tbergstrom at nvidia.com> wrote: > On 29.11.2014 10:44, Alexandre Courbot wrote: >> On Fri, Nov 28, 2014 at 9:09 PM, Roy Spliet <seven at nimrod-online.com> wrote: >>> I'm not sure if I completely understand your reply, so forgive me if I am >>> stating some obvious things: >>> The reason why I

On Fri, Nov 28, 2014 at 8:12 PM, Vince Hsu <vinceh at nvidia.com> wrote: > Signed-off-by: Vince Hsu <vinceh at nvidia.com> Make sure you always write a short summary for your patches, even if the title sounds sufficient. At the very least this patch makes the code easier to read, so: Acked-by: Alexandre Courbot <acourbot at nvidia.com>

On 28/11/2014 12:13, Vince Hsu wrote: > The voltage value are calculated by the hardware characterized > result. > > Signed-off-by: Vince Hsu <vinceh at nvidia.com> > --- > > Resend this patch with the fuse change and proper patch prefix > per Thierry's request. Since the voltage table really is per-chipset, it would be insane to add that to the DT. If it was not

I'd like to put up on the wiki the known working 3.3v MotherBoards people are using in production... I am very interested w/ppl with dual te410's with lots of concurrent channels in use Please dont post just your fav spec boards JUST ppl with working stable installs with TE410s, if possible with url, if not the exact board number & ill google it when i post to the wiki thxs in