similar to: Shutdown problem with Mecer 1000VA Online UPS

Hi Johan, The driver is expecting either 'ACK' or no reply at all in case of success and the command itself echoed back in case of errors. On the other hand, your UPS replies '(ACK' in case of success and '(NAK' on failure. So.. when the driver first tries to stop pending shutdowns and you get the 'operation not permitted' error, the driver interprets it as a

Hi, They say one should never argue with people that know more than you, so please bear with me. On 2013/10/24 09:47 PM, hyouko at gmail.com wrote: > The driver is expecting either 'ACK' or no reply at all in case of > success and the command itself echoed back in case of errors. > On the other hand, your UPS replies '(ACK' in case of success and > '(NAK' on

Hello, the code below the failing part mentions this flavor of protocol, drivers/blazer_ser.c:463 /* * If a command is invalid, it will be echoed back. * As an exception, Best UPS units will report "ACK" in case of success! */ I prepared a patch, it adds a similar check and also checks (in both occurencies) for blazer_command()<0, the latter

On Aug 11, 2013, at 2:12 PM, ????????? ???????? wrote: > I see no problem with how the device communicates the Blazer/Megatec protocol. > I must have found a bug in the driver. It is possible that the shutdown was tested with a different implementation of the protocol. What do you get from the "I" command? On Aug 11, 2013, at 11:25 AM, ????????? ???????? wrote: > So I

On Jul 2, 2013, at 5:16 PM, Kjell Claesson wrote: >> I hope other people can also test this. >> >> Regards >> Alf Hogemark > > Due to some crashes on the disks and lack of time I don't have the git on the > pc now. But maybe some other can commit this. I'd like to ask people to specifically try the bcmxcp branch on GitHub - it includes some changes

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

Sorry for a bit longer delay than I anticipated, I was stuffed with the work. This is the next iteration of the patch adding some functionality to apcsmart driver, and relying on 'ignorelb' recently added. Follow up from previous thread: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02331.html Main differences is that V3 is split into many small patches, so the

Hello, > What do you get from the "I" command? A string of 8 spaces. >> So I believe the compatibility list deserves two new lines. > >Probably best to delay adding this to the HCL until we can get the driver to shut down the UPS properly. I debugged the problem. From the source, drivers/blazer.c:418 /* * If a command is invalid, it

Hello again! Sorry for not being able to test this before. Ulisses, please apply the patch to fix typo in my e-mail address. I've compiled it against nut-2.6.5 about 10 hours ago. It was everything fine until now. I'm seeing CHRG but the ups led wasn't blinking at all. Vendor software was strangely showing charging also. I am assuming this is expected behavior. I've set the

Hi Kirill, just to notify you that your al175 driver is being removed from the NUT tree, as of 2.4.0-pre1. if you wish to see it entering the tree again, please contact the Development mailing list to talk about it. Merry Christmas and happy New Year. Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader -

Hello to all list members, I'm trying to make my UPS work with nut-2.2.2 (using Debian Testing, but compiled from source code) for a week ago, with not success. It's a Unitek Alpha 1000Ps, and I supossed it would work with megatec_usb driver, as other Unitek models. It has an USB interface, and when I plug it into my system I've got this message: chopito:/home/jordi# dmesg | tail

Hi Arnaud, Hi Scott, Hi list, Here is a patch to support the Zinto D from ONLINE USV-Systeme AG. I already sent a version to Russell Kroll (2006-04-09), without no response and I cannot find support for Zinto in svn until now. I found a discussion on this list about the Xanto from ONLINE, but the Zinto seems to use different commands. The commands are quite similar to those for Opti-UPS, so I

Hello all, long time away from this list, glad to be around again! I have this Powercom Vanguard VGN VGD-20K31. Some details of this model: * 3-phase input, single phase output * Model has 240V / 12V9AH x 20 x 2SET, plus another set of 20 batteries. All in all, 3 sets * Serial connection to Windows 2k3 server with UPSMon Now I was strongly considering replacing the bundled no-good upsmoon

Best fortress support was understandably dropped, but we still use them, and someone else may want the driver I ported to nut-2.0. We also often attach the serial cable from a UPS to a network terminal server, since servers these days don't come with very many serial ports. (They call them "legacy" ports.) I submitted a patch to support these for nut-1.x, and it was rejected

cmd test.battery.start.deep was not tested yet. cmd test.battery.start.quick works as expected. cmd test.battery.start 120 works as expected. cmd test.battery.stop works as expected. cmd beeper.toggle works as expected. cmd shutdown.return works as expected. cmd shutdown.reboot does not work entirely. After a minute, UPS is shut down but didn't come back. (Issuing shutdown.stop power up it

Hi, Charles. Are you by any chance planning to address my problems where NUT does not know how to schedule a shutdown of this Tripp-Lite UPS? If not, could you point me in the right direction? My best understanding of the situation of the moment is that the right control is UPS.OutletSystem.Outlet.DelayBeforeShutdown but that NUT does not know to use that. Thanks.

Merry Christmas to you all and best wishes! I ran into exactly the same problem as described. OS: FreeBSD 9.0-Rel UPS: Eaton E-Series NV 600H NUT: from Ports, nut-2.6.5_1 driver: blazer_usb I am sure the problem is not permission-related as it occurs even when the driver runs as root. My tested recipe for USB permissions is: 1. run usbconfig to find where the device is connected. In my case:

Use the name from ups.conf in front of "@localhost". ?The re?sult is quite different ;) root at artu:~# upsc Elit at artu Init SSL without certificate database Error: Driver not connected > What if you try nutdrv_qx without specifying megatec? (It should > autodetect.) > ?Here is the result: ? root at artu:~# upsdrvctl start Network UPS Tools - UPS driver controller

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