search for: bestfcom

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 sending another "\r" (on an UPS that doesn't prompt for the time that will just se...

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 where some BestPower FerrUPS FE2.1KVA UPS detection fails because of extra whitespace in the model ID. diff -rupN release-orig/nut-2.7.1/drivers/bestfc...

...nut-upsuser at lists.alioth.debian.org Subject: Re: [Nut-upsuser] BestPower Ferrups driver glitch with f commands 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 brittle in its string matching. > We are running NUT v2.7.1 on CentOS 6.5 with the bestfcom dri...

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 issued for the model, whic...

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 13:41:31.000000000 -0700 +++ release-patched/nut-2.7.1/drivers...

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 brittle in its string matching. > We are running NUT v2.7.1 on CentOS 6.5 with the bestfcom dri...

...hoice 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. Function sync_serial() sends only <cr>, no command, and the UPS answers with a new line. Without prompt enabled bestfcom will loop forever. Called via upsdrvctl it will time out. So debugging the source helped. Setting the Fortress parameter 75 (prompt) to 1 solved this. Next the driver doesn't work. Error message is: [nut at ls1 ~]# bestfcom -D -D -D -a LI1420 Network UPS Tools - Best Ferrups/Fortress 0.11 (2...

..."The battery voltage at which the UPS sound a High Battery alarm" A better value to use in determining the percent battery voltage would be fc.idealbvolts which is calculated in the driver source... I propose the following patch to fix the battery.charge (% battery full) reading. --- bestfcom.c.orig 2012-07-31 12:38:59.000000000 -0500 +++ bestfcom.c 2013-05-11 09:39:52.155279710 -0500 @@ -332,7 +332,7 @@ /* Compute battery percent left based on battery voltages. */ battpercent = ((vbatt - fc.emptyvolts) - / (fc.fullvolts - fc.emptyvolts) * 100.0); + / (fc.idealbvo...

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

I've just started using nut , and one of my UPSes is a Best Ferrups 1.8kva bestfcom seems to be the driver that would support it, but as currently in 2.0.2 it doesn't work on the FE1.8kv. I've done some hacking this afternoon and have it basically working. This is the only Best I have, so if anyone else is working on this, I was hoping to co-ordinate so I don't b...

...nal 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? >>> >>> https://github.com/networkupstools/nut/blob/v2.7.4/drivers/bestfcom.c#L226-L244 >> Of course, I got Eaton Powerware's RS-232 cable for FE700VA/etc. but don't know what 'hook up a terminal emulator'... no Slackware GNU/Linux BASH command 'f,' or do I run (or install/compile) a certain program to enable/access that? > minicom or scree...

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 +++ nut-2.2.1/drivers/bestfcom.c 2008-06-13 14:05:00.000000000 -0500 @@ -277,8 +277,8 @@ /* AC line frequency */ acfreq = ((double)bcd2i(&fstring[54], 4) / 100.0); - /* Runtime rema...

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 List and the Device Dump Library. Does the manual linked below describe your model? > > http://unifiedpowerusa.com/wp-content/uploads/2017/04/ferrups-users-guide.pdf > > If you...

...d to turn off the hardware and software flow control (minicom: Ctrl-A then letter O, "Serial port setup"). I would also recommend double-checking the serial port name (sometimes motherboards swap the headers around). That said, if you have a maintenance window, it may be worth trying the bestfcom driver directly. It will set up all of the serial port parameters, and attempt to get an identification string. I'm not sure if this is the recommended place to get NUT for Slackware, but this looks promising: https://slackbuilds.org/repository/14.2/system/nut/ For testing, you only need to d...

...off the hardware and software flow control (minicom: Ctrl-A then letter O, "Serial port setup"). I would also recommend double-checking the serial port name (sometimes motherboards swap the headers around). > > That said, if you have a maintenance window, it may be worth trying the bestfcom driver directly. It will set up all of the serial port parameters, and attempt to get an identification string. > > I'm not sure if this is the recommended place to get NUT for Slackware, but this looks promising: https://slackbuilds.org/repository/14.2/system/nut/ I don't have a mai...

...why, or if it may be added in the future, or if there are any other options. 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 List and the Device Dump Library. Does the manual linked below describe your model? http://unifiedpowerusa.com/wp-content/uploads/2017/04/ferrups-users-guide.pdf If you hook up a terminal...

...SET_HANDLED; /* Future: failure if r==-1 */ } else if (!strcasecmp(varname, "input.transfer.high")) { - r = belkin_nut_write_int(REG_XFER_HI, atoi(val)); + belkin_nut_write_int(REG_XFER_HI, atoi(val)); return STAT_SET_HANDLED; /* Future: failure if r==-1 */ } Index: b/drivers/bestfcom.c =================================================================== --- a/drivers/bestfcom.c 2011-05-31 13:36:49.000000000 +0300 +++ b/drivers/bestfcom.c 2011-08-17 00:23:22.000000000 +0300 @@ -260,13 +260,10 @@ void upsdrv_updateinfo(void) double ampsout=0.0, vbatt=0.0, battpercent=0.0, loadp...

Dear Andreas, some googling revealed, you created a driver for the xanto series of online-usv.de. In what state it is currently? I've to manage a S2000 and would like to use nut for it, is it usable by now? Do you need another tester? TIA, Pete

...ps microdowell solis >> bcmxcp etapro nutdrv_atcl_usb tripplite >> bcmxcp_usb everups nutdrv_qx tripplitesu >> belkin gamatronic oldmge-shut tripplite_usb >> belkinunv genericups oneac upscode2 >> bestfcom isbmex optiups upsd >> bestfortress ivtscd powercom upsmon >> bestuferrups liebert powerpanel usbhid-ups >> bestups liebert-esp2 rhino victronups >> blazer_ser masterguard richcomm_usb >> " &...