similar to: Is anyone working on the bestfcom driver ?

To deal with small model string differences that are present on the BestPower FerrUPS 2.1Kva ups, I have the patch below. The change in formatting seams to exist in firmware 9.28 and I think even older firmware. The patch is against the 2.7.1 bestfcom driver. Please pardon any errors in my patch submission has I have only submitted a patch once or twice before. This patch should fix a situation

Hello, I have a Best Ferrups 3.1KVA and I noticed that the percent battery voltage reported from upsc never gets above 69.9%. I believe there is a mistake in the driver. The battery percentage is calculated based on the High Battery Alarm Setpoint (59.6V) instead of the Ideal Voltage which is about 54V (4 batteries x 13.6V). I examined the source code and found that the variable fc.fullvolts is

I have an old (1997) Best Ferrups (model FE18KVA) that I am trying to monitor for the first time, but all the Best drivers fail to communicate with it. In ups_sync() in bestuferrups.c and bestfcom.c, the "time" command is sent and a one-line response is read. However, on my UPS, that command returns the current time and then prompts for a new time setting. I worked around that by just

He may be able to get the nut packages from the distro CD,but no updates. Gene, if you are running Fedora 10, an update to 12 would be well worth it, and the nut rpm's are in the standard repo ========================================================== Chris Candreva -- chris at westnet.com -- (914) 948-3162 WestNet Internet Services of Westchester http://www.westnet.com/

If you have a BestPower FerrUPS 2.1kva or similar UPS, and use the bestfcom driver, could you please test the following patch? https://github.com/networkupstools/nut/compare/bestfcom_FE I'd like to merge it in for the next release of NUT, but I have no confirmation as to whether it works, or makes things worse. Thanks, -- Charles Lepple clepple at gmail -------------- next part

Hi, my UPS is a Best Fortress LI1420 with the monitoring master running fedora 7. I have to replace the manufacturer's software "Checkups II" because it's not working with releases after fc4. My choice is the nut package. But it isn't just installing rpm's and configure the parameter files. ? The first hurdle to take was realising the UPS doesn't send a prompt.

The problem will only affect newer firmwares on the BestPower FerrUPS 2.1kva units. Additional white-space was the issue. I added a if clause to the bestfcom driver to account for this without breaking what was there. Here is the patch: diff -rupN release-orig/nut-2.7.1/drivers/bestfcom.c release-patched/nut-2.7.1/drivers/bestfcom.c --- release-orig/nut-2.7.1/drivers/bestfcom.c 2013-07-31

On Wed, 8 Feb 2023, Aki Tuomi wrote: > Can you try setting imapc_sasl_mechanisms to login, maybe it works better? And Stephan Bosch <stephan at rename-it.nl> wrote: > Can you make a protocol log (tcp dump of commands sent by client and > replies sent by server) for one of these sessions? e.g. using ngrep if > connections aren't secured. I was using imaps initially.

Greetings to you all, We are attempting to use NUT to interface with a BestPower FerrUPS FE2.1KVA. We are using the bestfcom driver because the driver listed our UPS as supported. The driver fails, however, because "fc" commands do not exist on the unit. We are running NUT v2.7.1 on CentOS 6.5 with the bestfcom driver. We setup a serial tap and see the UPS error out on the fc command

I had a power hiccup yesterday and a server connected to a Best Ferrups 18KVA shutdown. The problem is that the UPS is reporting remaining runtime in minutes but nut treats it as seconds (so nut thought it only had 46 seconds left). Simple patch: diff -urN nut-2.2.1-dist/drivers/bestfcom.c nut-2.2.1/drivers/bestfcom.c --- nut-2.2.1-dist/drivers/bestfcom.c 2008-06-13 14:04:07.000000000 -0500

On Feb 7, 2014, at 3:44 PM, Ritter, Nicholas wrote: > Greetings to you all, > > We are attempting to use NUT to interface with a BestPower FerrUPS FE2.1KVA. We are using the bestfcom driver because the driver listed our UPS as supported. The driver fails, however, because "fc" commands do not exist on the unit. There is a upsdrv_init_nofc() function, but it seems to be

I did the testing you suggested, and it was indeed the whitespace. I added another if clause test to the function and everything seems to work. I have working driver that I will email a patch for this list. My coworker says the model ID is configurable though, so we will try that first, which would negate the need to patch the driver. ________________________________________ From: Charles Lepple

I'm migrating a legacy uw-imap system to Dovecot, on a Rocky (RHEL) 8 server running Dovecot 2.3.16-3 from their repos. I am using a master user to import all users for an imaps connection from the old server to the new. On a trial run however, it worked for about half the users. Half are giving an error of the form: dsync(user): Error: imapc(host:993): Command '1 AUTHENTICATE PLAIN

On 02/20/2018 06:16 PM, Charles Lepple wrote: > Do you have a pinout for that cable? Unsure, but after recent suggestions, it may be working.? Already had NUT from SlackBuilds.org (SBo) installed, but reinstalled to add the group:user. > I forget if it is the default, but you might need to turn off the hardware and software flow control (minicom: Ctrl-A then letter O, "Serial port

On Mar 19, 2018, at 4:00 AM, David Melik wrote: > >> Then you can launch the driver with at least one "-D" flag: >> >> /usr/libexec/nut/bestfcom -a ups -D > > I thought there was a lot more to it than that, but after I ran that stuff, the driver outputs. However, /etc/rc.d/rc.ups initialization script might not do anything yet (only the command you gave,

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 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

Do any known UPS's keep internal logs of events? I am currently using a slightly modified version if usbhid-ups to talk to a HP T/R2200 G2, which is internally a TrippLite UPS. The UPS is randomly turning off its output power, at intervals of once every week or two, even though during this failure it reports that input and output voltages are still around 248V (240V is nominal). The only

This is the patch to include SVN revision level in version number displays. There should be two enclosures; the patch itself and a new source file. common/upsversion.c. upversion.c defines a single function. upsversion(), that returns a version string for display. Some Makefile trickery ensures that this file will be recompiled whenever the project's SVN revision level has changed since it

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