similar to: Powercom SXL-1000A-LCD

I am have a nice result whith blazer_ser driver! respect! # ./nut start Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - Megatec/Q1 protocol serial driver 1.51 (2.4.1) Supported UPS detected with megatec protocol Vendor information read in 1 tries Battery runtime will not be calculated (runtimecal not set) <================= !!! Starting nut. Network UPS Tools upsd 2.4.1

Hi list here is the patch to make fentonups recognize some PowerCOM's UPS's, and to setup terminal lines for them (at least for SMK-1500a) as powercom's original upsmon do. fentonups -x powercom works correctly with SMK-1500a (it screamed ''Communications with UPS lost - check cabling' or 'Short read during UPS id sequence' without this patch). Sorry for

There simply is no such functionality, or the driver can not read these values because of nesovmestimoti / oschibki? Maybe a fix? And whether further use of the NUT, so that my UPS shut off my server connected to it?

Hi Charles; I tried both of your suggestions: 1) run stty -f /dev/cuaU0 raw jusbefore running solis 2) Unplug/plug, and run solis right after. The problem still persists. [~]>stty -a -f /dev/cuaU0 speed 9600 baud; 0 rows; 0 columns; lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl -echoprt -altwerase -noflsh -tostop -flusho -pendin -nokerninfo -extproc

Hi. I have some problems with USB->Serial FTDI FT232BM chip drivers on FreeBSD 7.0... FreeBSD recognize the USB device, but when I making connection to /dev/cuaU0 or /dev/ttyU0 I cant send & receive any data from device. cu -l/dev/cuaU0 -s9600 - No response at all, can't even quit the program cu -l/dev/ttyU0 -s9600 - Sometimes working, but few bites/chars after - no response...

Hello, I'm new there. I bought an UPS Powercom BNT-600AP. It's compatible in NUT with driver powercom and protocol type KIN1500AP. But I have a simple problem: the 'upsc' shows wrong values in battery.charge (maybe in other rows also /ups.load, voltages?/) - if battery is 100% charged it shows only 92.6% or 93.0%. I thing I have wrong values in driver parameters: batteryPercentage,

Hi; I'm having some trouble to comunicate with my just bought (08/17/15) Ups. According to SOLIS(8): SUPPORTED HARDWARE This driver has been tested with : Solis 1000 VA Solis 1500 VA Solis 2000 VA Solis 3000 VA Back-UPS BZ1200-BR Back-UPS BZ2200BI-BR So solis is the one to go for. Here is my scenario: SW: nut-2.7.3 (compiled from ports) OS: FreeBSD

Hi, 2010/12/27 ??? <pointbre at naver.com> > First of all, thanks for your effort to NUT Project, > I'm developing remote monitoring solution for many devices based on linux > server. > In field test, we reached the power shutdown problem which may cause the > crack of linux file system. > I search the solution and find NUT project and i'm very glad that NUT >

Hello I have UPS Powercom Black Knight Pro 1200 (BNT-1200AP) I try to use nut, but powercom driver not understand my model Ok, i try to use type KIN1500AP and it's work But powercom driver can't set UPS's shutdown delay time Also i have powercom's original program (upsmon), and this program can do it What can i do for help to add this function to nut's powercom driver? For

Hello all! Some days ago we received new UPS?Powercom BNT-2000AP with USB interface to replace an old staff and I've spent three last days trying to connect it with NUT. I have a FreeBSD 8.4 box with NUT 2.7.2. # dmesg|grep -i powercom ugen0.3: <POWERCOM Co.,LTD> at usbus0 uhid0: <POWERCOM Co.,LTD HID UPS Battery, class 0/0, rev 1.10/0.01, addr 3> on usbus0 uhid0: <POWERCOM

Hi *Simon, i got a similar setup here (also a powercom-oem-product, but in my case labeled by a swiss "manufacturer") with the same problems, using powercom's upsmon works fine, while nut completely refuses to cooperate. after trying almost everything i somehow hopeless surfed on the official nut-page, when i saw that there are powercom-products which don't need the

Hey all, I've tried some very base configs with the powercom 2200, but I can't seem to get it to work. Has anyone dealt with these UPSes before, or know if they use the standard powercom drivers? I'd be more than happy to allow access to my test system so someone more knowledgeable can take a look (and am also willing to pay something for the solution of said problem.) -Dan

Hi! I've tried the Fenton Driver for my UPS. The Powercom driver doesn't work. Here is the results: Network UPS Tools - UPS driver controller 2.0.0 Network UPS Tools - Fenton UPS driver 1.21 (2.0.0) Unknown ups - please report this ID string: #PCM SMK-1000 2001 V9.0 Detected Unknown MK-1000 on /dev/ttyS0 Have you any ideas to make it compartible with NUT. Thanks! With

Hello everybody! I'm trying to use nut-2.4.1 with brand new UPS Powercom Imperial IMD-825AP USB. I've faced a problem that the driver powercom despite specifying type=IMP automatically re-detects the UPS as "KIN" and then interprets raw data incorrectly. The same problem was reported by other Powercom users on the official support forum ( http://forum.pcm.ru ). I suppose the

Hello, I’ve a problem with start driver for PowerCom KIN-600AP RM. The driver is “usbhid-ups”, see “No matching HID UPS found” when I trying to start driver. Ubuntu version is 18.04 LTS. My ups.conf: [powercom] driver = usbhid-ups port = auto vendorid = 0d9f productid = 0004 Start driver with: ./usbhid-ups -a powercom -DDDDD ... 0.032993 Unable to get HID descriptor (error sending

On April 28, 2017 9:11:59 AM GMT+03:00, "????????? ?????????" <vtk-alexb at mail.ru> wrote: >Hello all! > >Some days ago we received new UPS?Powercom BNT-2000AP with USB >interface to replace an old staff and I've spent four last days trying >to connect it with NUT. I have a FreeBSD 8.4 box with NUT 2.7.2. > ># dmesg|grep -i powercom >ugen0.3:

Dear Charles and Artem, I've recently bought a new PowerCom Imperial IMD825-AP LCD which identifies itself as 0x0d9f:0x0004. At first glance it seems that usbhid-ups driver works fine. But when I tried to shutdown UPS via DelayBeforeShutdown it started double beeping every couple seconds for indefinite time (the same problem described by Vincenzo Colonnella here:

Ok, so I previously thought I had to use usbhid-ups but when I eventually got it going this is what I got:- This Powercom device (0d9f/0002) is not supported by usbhid-ups. Please use the 'powercom' driver instead. So I switched to the powercom driver, but I have tried a whole bunch of likely suspects for the port setting, none of which have worked Tried so far:- com1 with these

Heya, after I bought an OptiUPS VS 575C and discovering it won't work with Linux (silly me) I sniffed the protocol, found out it's very similiar to the protocol in the powercom driver, so I ended up adding support for that UPS to that driver. The patch is against the current git HEAD and works fine for me since weeks now. The shutdown sequence also works fine (on Archlinux). This is my

On Sep 11, 2014, at 2:50 AM, Khokhlov Artem <khokhlov.a at pcm.ru> wrote: > Can you please kindly add our new USB-controller with productID 0X04 to NUT compatible list. Updated USB-controller compatible with previous version which is supported by your usbhid-ups driver. Confused. This commit was added in 2011: