similar to: System Shutting Down Shortly After Boot, COMMBAD, "Writing Error", "Data Receiving Error"

Hello all. Try this driver (for nut 2.2.0). See attach. - Trust, KP625AP, Egys models stay as it was - add Powercom's Black Knight Pro model support ( BNT-400/500/600/800/801/1000/1200/1500/2000AP 220-240V ) - add Powercom's King Pro model support ( KIN-425/525/625/800/1000/1200/1500/1600/2200/3000/5000AP[-RM] 100-120,200-240 V) - add Powercom's Imperial model support ( IMP-xxxAP,

Hey all, Finally got around to hooking up my Powercom BNT-1500AP to nut. It's the old serial interface. Connects okay and gets most information, but a couple of data are way off. Any config recommendations or upgrade recommended? I've played with config a little, but no hits yet. Details: NUT version 2.4.3 ups.conf: [ups] driver = powercom port = /dev/ttyS0

I have had a similar problem to many other people for the last few months with my Cyberpower UPS. It was working properly after reboot about one in five times; the rest of the time it would endlessly disconnect and reconnect, according to syslog messages. The latest I was able to find towards a solution is http://www.mail-archive.com/nut-upsuser at lists.alioth.debian.org/msg06671.html The root

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

Hello all, Last week I rescued and UPS from the trash (it's really amazing the kind of things you can find in the trash of the university research labs). No manual, no cd, no cables, just the unit. It's name is "Blizzo 500", and blizzo was just the rebranding of a spanish reseller which has been out of the scene for nearly two years now, at least according to the wayback

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 >

I have only RS-232 on the box (meanwhile, it was manufactured on march of 2011) Here is my configs: nut.conf: * * MODE = netserver ups.conf: * * [KIN1500] driver = powercom port = notUsed desc = "Powercom KING PRO KIN-1500AP RM" upsd.conf: * * LISTEN 192.168.1.2 3493 upsd.users: * * [monuser] password = xxxxxxxx upsmon master

Hi, I have a UPS of the Israeli company Sustainer, model S-1000C (http://www.sustainer.co.il/data/files/specifications%20smart%20en.pdf - don't worry, it's in english...). I've been trying to connect to it from Debian to no avail for a long time now. The company has attached to it a program called Commander Pro (for windows) and RPMs of UPSmart for old versions of Redhat and

Hi, I've sent the following message 3 weeks ago, yet have recieved no reply at all. I don't want to nag, but could anyone please help me? Thanks, Dror ------------------ Hi, I have a UPS of the Israeli company Sustainer, model S-1000C (http://www.sustainer.co.il/data/files/specifications%20smart%20en.pdf - don't worry, it's in english...). I've been trying to connect to

Hello. What about driver for my UPS? I have changed the powercom driver for myself, but I have made it not absolutely correctly. However, somehow this driver works. Now i have protocol spec for powercom BNT series and attach it to this email. It can be interesting to authors? -- ? ?????????, ??????? ??????? mailto:alex@reutman.ru JID: alex@reutman.ru ICQ: 5052225 -------------- next part

Dino, Alexey, there are a number of users suffering issues with your Powercom devices. Could you (Dino, and Keven if possible) please have a look at the below one, from Angela, and check for a fix? I've scheduled to release 2.6.1 next week, and having that fixed is part of the list. 2011/5/16 Angela Williams <angierfw at gmail.com> > Hi All > > On Friday 13 May 2011 at

hi i bought a ultra ULT31502 ups someone seem able to run this ups with nut just see Dean thread on: http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=770423&Tab=11&NoMapp=0 i use suse 10.1, i installed nut the ups is connected directely to my computer with an usb cable lsusb return Bus 001 Device 004: ID 0d9f:0001 Powercom Co., Ltd with lsmod, i can see

Gidday all - I'm a new user to nut. I've got some cheap powerpal UPSs working fairly well. However I also have a new Dynamix UPS-1700D and an old Powercom KIN-1700 something unit that I cannot make work right. The best method I've found is "trial and error" which sounds a bit last-resort. Is there any better way to find out what protocol is used? -- Criggie

Hi, As my subject says, I am struggling with the shutdown behaviour of my NUT slaves, when the communication to the master is bad (COMMBAD). From upsmon.conf: # -------------------------------------------------------------------------- # SHUTDOWNCMD "<command>" # # upsmon runs this command when the system needs to be brought down. Ok.... obviously, in the

Hello Is it possible to limit the frequency of specific notifications? In 2.7.4 it seems to be possible only for REPLBATT via RBWARNTIME, but that's it. My specific problem is that the UPS got disconnected and before I got hold of the server to turn the upsmon off my mailbox got flooded with hundreds of messages. It probably doesn't make sense for all notification types, but for

Source: xen Version: 4.1.4-2 Severity: important Hi, using RUN+="socket:" in udev rules files has been deprecated for a while. In udev 183 support for that has been removed [1] >From the NEWS file: * udev: RUN+="socket:..." and udev_monitor_new_from_socket() is no longer supported. udev_monitor_new_from_netlink() needs to be used to subscribe to events.

I'm running nut-2.8.0-3.el8.x86_64 on CentOS Stream 8 talking with an APC Smart-UPS RT 5000 RM XL via a Network Management Card AP9619 (version A10). Up to today I would receive occasional COMMBAD messages, then 5 minutes later I'd see a COMMOK.Maybe 1 or two a day. Today I updated the firmware on the AP9619 from 3.7.2 to SUMX 3.9.3 and AOX 3.9.4, the most recent releases available for

Well, this is some ugly text formating, let me fix that :)? ## Samba Conf ##[global]? ?workgroup = plop? ?server string = %h serveur ? ?security = user?? ?netbios name = plop? ?dns proxy = no? ?log file = /var/log/samba/log.%m? ?max log size = 1000? ?syslog = 0? ?panic action = /usr/share/samba/panic-action %d? ?log level = 3? ?server role = standalone server? ?passdb backend = tdbsam? ?obey pam

Gents, Any clue on what could be the problem and how to solve it ? My conf and error inside the following pastebin : smb error win7 - Pastebin.com | ? | | ? | | ? | ? | ? | ? | ? | | smb error win7 - Pastebin.com## Samba Conf ## [global] ? ?workgroup = plop ? ?server string = %h serveur ? ?security = user ? ? ?netbios name = plop ? ?dns proxy = no ? ?log file = /var/log/sam... | | | | Afficher