similar to: powercom UPS shoutdown discussion

Hello! After I type "upsmon", in syslog the following message appears: Aug 16 14:11:09 marto upsmon[7731]: Master privileges unavailable on UPS [Inform@localhost] Aug 16 14:11:09 marto upsmon[7731]: Reason: Access denied Can you tell me where my error is, my configuration files are: ups.conf: [Inform] driver = powercom port = /dev/ttyS0 desc = "inform guard" linevoltage = 220

And something else, that previously eluded from my thoughts:my "notifyme" script,i.e the script that is executed at an ups.status="OB" event, is: echo `date` >> /root/upsLog echo " No power, shutting down the system!" >> /root/upsLog sleep 30 control=`/usr/local/ups/bin/upsc Inform@localhost ups.status` if [ $control != OL ] then

So, this is the result of upsc Inform@localhost with the UPS connected to the mains: battery.charge: 97.7 driver.name: powercom driver.parameter.linevoltage: 220 driver.parameter.port: /dev/ttyS0 driver.parameter.type: KIN1500AP driver.version: 2.0.4 driver.version.internal: $ Revision: 0.5 $ input.frequency: 49.61 input.voltage: 236.3 input.voltage.nominal: 220 output.frequency: 49.10

Mr Claesson, with my current configuration, the ups.status when the UPS is disconnected from the mains is "OB". There is no more "OB BOOST". Now my upsd.users is: [root] password = password allowfrom = localhost upsmon master actions = SET instcmds = ALL and upsmon.conf is: RUN_AS_USER root MONITOR Inform@localhost 1 root password master MINSUPPLIES 1 SHUTDOWNCMD

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

We are communicating with Asterisk via AMI. Running Asterisk version 13.18.5 on an Ubuntu box. If you look at the event response, the Result field is filled with random characters. I'm not sure what to do because that is a completely random result. It makes no sense. We send the following command to asterisk via AMI Action: AGI ActionID: C44415 Channel: SIP/192.168.40.105-00001338

I'm trying to use LLVM to create compiler-rt.o on Windows. I use this command from the compiler-rt project: [nix-shell:~/downloads/llvm-project/compiler-rt]$ clang -nostdlib -S -emit-llvm lib/builtins/udivti3.c -g -target x86_64-windows -DCRT_HAS_128BIT The resulting LLVM IR is: ================================================================= ; ModuleID = 'lib/builtins/udivti3.c'

HI Matt, I am trying to replicate this particular problem. We are seeing more frequently where the Event: AsyncAGIExec is never being sent. The two scenarios I have seen in tests yesterday and today... We sendl an AMI action. For example, play a short file or hangup. AMI Events will indicate it did the work, but we never receive the Event: AsyncAGIExec with a result at all. Asterisk debug

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

Most probably you need to properly specify the calling convention the backend is using for calling the runtime functions. Or implement the stub for udivti3 that performs the necessary argument lifting. I guess there is no standard ABI document describing the intended calling convention here, so I'd just do what mingw64 does here and make everything here compatible. On Thu, Apr 26, 2018 at

Hi ALL, Powercom Imperial IMP-525AP seems to be fully compatible with NUT. Unfortunately, I can not disable beeper. upscmd -u {NUT_USER} -p {NUT_PASSWORD} powercom beeper.toggle returns *OK*, however, ups.beeper.status=enabled Thank you, Sergey ========== Additional info: 1) $ upsc powercom battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 30 battery.date: 2010/01/01

On Thu, Apr 26, 2018 at 3:44 AM, Anton Korobeynikov <anton at korobeynikov.info > wrote: > Most probably you need to properly specify the calling convention the > backend is using for calling the runtime functions. Thanks for the tip. Can you be more specific? Are you suggesting there is some config parameter I can set before running TargetMachineEmitToFile? Do you know what

Hello Does anybody know if it's possible to monitor a Powercom EBk 500 (RS232)? the trick is that I am using a raspberry pi, it does not have RS232 so I connected a keyspan RS232 to USB adapter, but so far I can?t make this work. Thanks for your time to read this. -Edgar -------------- next part -------------- An HTML attachment was scrubbed... URL:

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 know it's been a topic many times here, but I've searched the archives, googled for days, and I simply don't believe, that there is still no solution to this. I'm using a PowerCom BNT-600AP ups with usb port. I've downloaded the latest version from svn, compiled it, and tried to use it: * megatec(_usb) - no luck, it did not find the UPS (I?ve read in this list, that

Alexey, I posted this before, but never got a reply. So I'm reposting this again. In the present HID PDC implementation by PowerCOM, expect problems with the non-compliant implementation of the DelayBeforeShutdown and DelayBeforeStartup pages. Third party applications will expect that these follow the HID PDC specifications if you name them like this (and break terribly in the

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

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:

On Nov 11, 2014, at 3:30 PM, Maksym Bodaniuk <max.bodaniuk at gmail.com> wrote: > 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

Dear Sirs, First of all I would like to thank you for support PCM product in your project. Kindly please be informed that POWERCOM launch new USB-controller with productID 0X04. Updated USB-controller compatible with previous version which supported by your usbhid-ups driver. There is added some command and changed idProduct. Vendor ID stay the same 0X0d9f without changes. Detailed information