similar to: FE700VA over USB? controlling UPSes over network?

I have an excellent old Best Power FE700VA but am suprised it's unlisted.? I thought Best Power ones were for critical applications, mostly for POSIX-based (Unix, etc.) servers, so I want to run it on 64-bit Slackware GNU/Linux.? I'm wondering why, or if it may be added in the future, or if there are any other options.

On 01/21/2018 05:53 AM, Charles Lepple wrote: > My understanding was that many of the older Best Power units were downstream of generators, and as such, full-blown power outages of both mains and generator power were not expected. > > That said, it might be that the "bestfcom" driver predates when we were actively collecting specific model names for the Hardware Compatibility

People, A couple of decades before I was retired and was still working for other people I had cause to install UPSs and they usually had RS232 ports to allow the setting up of shutdown scripts to UNIX / Linux servers. Now, after not having to be concerned by those issues for some time - most of my little web sites have been on Digital Ocean or other suppliers VMs for a long time - I am

People, A couple of decades before I was retired and was still working for other people I had cause to install UPSs and they usually had RS232 ports to allow the setting up of shutdown scripts to UNIX / Linux servers. Now, after not having to be concerned by those issues for some time - most of my little web sites have been on Digital Ocean or other suppliers VMs for a long time - I am

Larry, I have not edited a single file, including anything to do with NUT, on the Synology via ssh.... ever. How is yours configured in the UI? Do you have it set to go into safe mode after a certain number minutes? Earlier, I was just copying and pasting the contents of some files to Roger but did not change anything. -- Todd Benivegna // todd at benivegna.com On Aug 14, 2020, 8:16 AM -0400,

Roger, Thanks for the idea to add additional items to the notifyflag. That proved the monitor was indeed working as expected and led me to find that my script had myriad issues when run under the nut user. All remedied now. As I progress, I may well end up migrating to the upssched. As a newbie I was simply following the documented "simple" way described here

Thanks Larry, no problem. I appreciate the input. Whenever you get a chance I’d really like to compare notes with someone who has NUT and a Synology to see why the heck mine doesn’t work! ;). I’m also using my Pi as the master like you. Thanks. Todd -- Todd Benivegna // todd at benivegna.com On Aug 14, 2020, 11:55 AM -0400, Larry Fahnoe <fahnoe at fahnoetech.com>, wrote: > On Fri, Aug

On Fri, 22 May 2020, Tom Cooper wrote: > Sadly I am still seeing a loss of communication. I will check the device number to see if it has changed.  > Not sure what else to look at. I guess I could create a corn job to restart the driver multiple times a day.  If there is a command such as upsc for which the output depends on the driver running correctly, then it might be better to run a

On Jan 21, 2018, at 1:12 AM, David Melik <dchmelik at gmail.com> wrote: > > I have an excellent old Best Power FE700VA but am suprised it's unlisted. I thought Best Power ones were for critical applications, mostly for POSIX-based (Unix, etc.) servers, so I want to run it on 64-bit Slackware GNU/Linux. I'm wondering why, or if it may be added in the future, or if there are

On Feb 12, 2018, at 11:53 PM, David Melik wrote: > > On 01/21/2018 05:53 AM, Charles Lepple wrote: >> If you hook up a terminal emulator to the comms port (1200 baud, 8/N/1 unless stickers and/or configuration DIP switches indicate otherwise), and type "f" <return>, do you get a status line like one of the following? >> >>

Hello I asked Tripplite the serial protocol implemented in the UPS model SU2200RTXLCD2U. The protocol is the 4006, which is not supported by the NUT. I connected my UPS unit to a serial terminal client (both from a Windows machine and a Linux machine), set the communication parameters to those indicated in the protocol spec, and tried to open the communication, unfortunately with no success. I

Roger, I get 4.3.8(1)-release There was good reason, BTW, for the script to NOT fine the journal script on my machine. I had not downloaded it yet. On 7/14/2019 9:06 AM, Roger Price wrote: > On Sun, 14 Jul 2019, David White wrote: > >> ... I saw nothing that looked like a problem with the report save the >> sections <scriptname> "Cannot access <scriptname>.

On Sat, Jul 22, 2017 at 7:48 AM, Charles Lepple <clepple at gmail.com> wrote: > > I also have not used a Synology device, but as I recall, they generally > expect to be the NUT master system. This may cause problems if you need to > do something fancy with upssched. > The Synology boxes work fine as NUT clients, *however* they provide very little ability to configure NUT

On 02/13/2018 03:49 AM, Charles Lepple wrote: > On Feb 12, 2018, at 11:53 PM, David Melik wrote: > > On 01/21/2018 05:53 AM, Charles Lepple wrote: >>> If you hook up a terminal emulator to the comms port (1200 baud, 8/N/1 unless stickers and/or configuration DIP switches indicate otherwise), and type "f" <return>, do you get a status line like one of the

Thank you for your answer. I will try to investigate the possibility that the Tripplite serial cable has a different pinout than a standard RS-232 serial cable. I wouldn't use the NUT at this point because I don't think I will be able to write a software update to adapt the NUT to my needs. My idea was first to test the protocol via a serial terminal client directly connected to the UPS,

> > > 2.117586 send_cmd(msg_len=2, type='G') > > 3.219418 libusb_get_interrupt: Connection timed out > > 3.219474 libusb_get_interrupt() returned 0 instead of 8 while > sending 3a 47 b8 0d 00 00 00 00 '.G......' > > 4.219593 libusb_get_interrupt: Connection timed out > > 4.219661 libusb_get_interrupt() returned

On Apr 13, 2018, at 3:55 AM, Jon Bendtsen <jon.bendtsen at jonix.dk> wrote: > > On 13/04/2018 07.56, zefanjas wrote: >> Hi, >> is there a command to get a list of connected slaves you can run on the >> nutserver? I want to monitor the slaves and if their are actually >> connected to server. > > if there is no such command in NUT, then on my Debian

So I finally got a test in after I changed my RPi to the master and everything else (including my Synology) to slaves.  Before I did that though, I timed the shutdown of my Synology since it is the slowest slave to shutdown.  It took 40 seconds to shutdown, so I changed HOSTSYNC in upsmon.conf on the master (“Proton”) to 60.  I then did a test ("sudo upsmon -c fsd”). The slaves shutdown, then

On Mon, 10 Aug 2020, Todd Benivegna wrote: > synoups: https://hastebin.com/xexafofiha.bash Wow! What a mess. It looks as if Synology wanted to write their own "NUT", but decided it would be easier to put their ideas in a script when they saw they could use upssched.conf to call it. NUT intends such a script for timer management. Synology use it for general system management.

Hey there, Has anyone tackled the best way to shut down a VM running Win10 running in RedHat's (CentOS 7) KVM/QEMU VM manager? I'm looking at this link to follow: