Re: [Nut-upsuser] Enhanced driver troubleshooting

2023-04-24 Thread gene heskett
On 4/24/23 19:54, Jim Klimov wrote: For the final part after the build, I'd do this to make sure systemd units get defined, activated and started: :; make -j 4 all && make -j 4 check && \ { sudo systemctl stop nut-monitor nut-server || true ; } && \ { sudo systemctl stop nut-driver.servi

Re: [Nut-upsuser] Enhanced driver troubleshooting

2023-04-24 Thread Jim Klimov via Nut-upsuser
For the final part after the build, I'd do this to make sure systemd units get defined, activated and started: :; make -j 4 all && make -j 4 check && \ { sudo systemctl stop nut-monitor nut-server || true ; } && \ { sudo systemctl stop nut-driver.service || true ; } && \ { sudo systemctl

Re: [Nut-upsuser] Enhanced driver troubleshooting

2023-04-24 Thread gene heskett
On 4/24/23 17:11, Jim Klimov wrote: You mentioned the RPi runs a buster-based OS? yup raspios, buster. I'd have moved on but the bullseye python is too new and linuxcnc can't use it. The lcnc guys are busy making it work for bookworm and haven't had time to backport for bullseye. I have a c

Re: [Nut-upsuser] upsset.conf : Restriction directives need updating

2023-04-24 Thread Jim Klimov via Nut-upsuser
Thanks, I'll post an update :) Jim On Mon, Apr 24, 2023 at 10:37 PM Phil Stracchino via Nut-upsuser < nut-upsuser@alioth-lists.debian.net> wrote: > The good news: > While gathering information for this post, I solved the ORIGINAL problem > I was going to post about, which was figuring out how to

Re: [Nut-upsuser] Enhanced driver troubleshooting

2023-04-24 Thread Jim Klimov via Nut-upsuser
You mentioned the RPi runs a buster-based OS? I suppose the simplest way is you can forgo the init-scripts and retain just the systemd services (as listed in the article - including the nut-driver-enumerator which would create nut-driver@myups.service based in the ups.conf section). Jim On Mon,

[Nut-upsuser] upsset.conf : Restriction directives need updating

2023-04-24 Thread Phil Stracchino via Nut-upsuser
The good news: While gathering information for this post, I solved the ORIGINAL problem I was going to post about, which was figuring out how to change the low-battery limit on my CyberPower PR3000LCDRTXL2U UPS with expansion chassis. With three battery packs, the default 20% is absurd. How

Re: [Nut-upsuser] Enhanced driver troubleshooting

2023-04-24 Thread gene heskett
On 4/24/23 14:05, Jim Klimov wrote: "I'd thought you'd never ask" (C) Can you give this walkthrough a shot? https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests Jim I used this section of that link to build the new one: This go

Re: [Nut-upsuser] Graceful shutdown

2023-04-24 Thread Roger Price
On Sun, 23 Apr 2023, Prometheus via Nut-upsuser wrote: I am trying to configure a graceful shutdown on my TrippLite UPS what would i need to configure to achieve this keeping in mind I’m using a USBHID driver by default Perhaps one of the chapters in this collection of configuration examples

Re: [Nut-upsuser] Enhanced driver troubleshooting

2023-04-24 Thread gene heskett
On 4/24/23 14:05, Jim Klimov wrote: "I'd thought you'd never ask" (C) Well, since the Kohler starts in about 5 seconds, this is just keeping me out of the bars. :o)> Can you give this walkthrough a shot? https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-o

Re: [Nut-upsuser] Enhanced driver troubleshooting

2023-04-24 Thread Jim Klimov via Nut-upsuser
"I'd thought you'd never ask" (C) Can you give this walkthrough a shot? https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests Jim On Mon, Apr 24, 2023 at 8:00 PM gene heskett wrote: > On 4/24/23 13:12, Greg Troxel wrote: > > gene

Re: [Nut-upsuser] Enhanced driver troubleshooting

2023-04-24 Thread gene heskett
On 4/24/23 13:12, Greg Troxel wrote: gene heskett writes: Jim, would an upgrade to the install on my rpi4b running a medium sized 80+ yo lathe give me better control over a: device.mfr: CPS device.model: CP625HGa device.type: ups driver.name: usbhid-ups driver.parameter.offdelay: 120 where tha

Re: [Nut-upsuser] Enhanced driver troubleshooting

2023-04-24 Thread gene heskett
On 4/24/23 13:12, Greg Troxel wrote: gene heskett writes: Jim, would an upgrade to the install on my rpi4b running a medium sized 80+ yo lathe give me better control over a: device.mfr: CPS device.model: CP625HGa device.type: ups driver.name: usbhid-ups driver.parameter.offdelay: 120 where tha

Re: [Nut-upsuser] Enhanced driver troubleshooting

2023-04-24 Thread Greg Troxel
gene heskett writes: > Jim, would an upgrade to the install on my rpi4b running a medium > sized 80+ yo lathe give me better control over a: > device.mfr: CPS > device.model: CP625HGa > device.type: ups > driver.name: usbhid-ups > driver.parameter.offdelay: 120 > where that offdelay seems hard co

Re: [Nut-upsuser] Enhanced driver troubleshooting

2023-04-24 Thread gene heskett
On 4/24/23 08:31, Jim Klimov via Nut-upsuser wrote: As a follow-up, that R&D led to several other issues and PRs, now mostly merged and summarized in https://github.com/networkupstools/nut/issues/1781#issuecomment-1519824607 (with a few points still awaiting completion). They added new features

Re: [Nut-upsuser] Enhanced driver troubleshooting

2023-04-24 Thread Jim Klimov via Nut-upsuser
As a follow-up, that R&D led to several other issues and PRs, now mostly merged and summarized in https://github.com/networkupstools/nut/issues/1781#issuecomment-1519824607 (with a few points still awaiting completion). They added new features to NUT master branch, including: * drivers/upsdrvquery