similar to: Blazer_usb Permissions problem: Input/output error

Hello, i've a problem, this is my configuration: - Atlantis Land UPS with serial port - a generic RS232 to USB cable adapter (QinHeng Electronics HL-340 USB-Serial adapter for linux). The problem is in the syslog file where i find: [...] Aug 19 09:07:25 ProLiant megatec[1126]: Communications with UPS lost: No status from UPS. Aug 19 09:07:26 ProLiant megatec[1126]: Communications with UPS

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

Hello All, I tested our new UPS yesterday. I noticed that while the blazer_ups drivers support this device, the newer nutdrv_qx does not. I suppose that this should not be the case, as nutdrv_qx will replace blazer_ups(?). Versions: I installed Nut on Ubuntu 13.10 (64 bit) from the standard package (2.6.4-2.3ubuntu2), and I also installed from the source tarball (2.7.1), into a different

Thank you for the rapid response. I will try and investigate getting answers to some of your points but I'm a little new to Solaris so I'll need some time. Glancing at the configure output, it looks like it built against v0.1.7 of libusb (yes i think that is derived from the one you mention), checking for libusb version via pkg-config... 0.1.7 found checking for libusb cflags... checking

On Mar 5, 2015, at 2:34 AM, Jakub <jakub.scepka at gmail.com> wrote: > Come on, it started to be interesting! Do you have one of these UPSes? If so, here was Dan's email about a branch to test: > If you still can't get it to work with nutdrv_atcl_usb, another > approach could be worth considering. > > Since this UPS seems to be supported by UPSmart2000I, it could

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

Hey all, I ended up picking up the module listed in Subject line. I switched over my config but apparently not all going smoothly. My config is: [office] driver = powerpanel port = /dev/ttyS0 desc = "Office UPS" When I test the driver running power-panel as a test, I get: > [root at cornelius init.d]# powerpanel -a office -D -D -D -D >

Ubuntu 8.04 Nut : Version: 2.2.1-2.1ubuntu7.2 Hello, I choose the megatec driver and I connect through a serial cable. I receive a "This UPS has an unsupported combination of battery voltage/number of batteries" message. I know this is not an error but I don't really what I have to do next. Here is the result of /lib/nut/megatec -a infosec -DDD debug level is '3'

Thank you for your reply Charles, this is the "upsc" result: root at artu:~# upsc ups at localhost Init SSL without certificate database Error: Unknown UPS Trying with nutdrv_qx, protocol megatec the driver does not start... 2017-06-08 14:47 GMT+02:00 Charles Lepple <clepple at gmail.com>: > On Jun 7, 2017, at 12:54 AM, Andrea de Lutti <adelutti at gmail.com> wrote:

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

Hi list, on my previous (lenny or squeeze) machine, I had it up and running, but that machine and configs are gone - and on my new jessie machine (see device and config details below) I cannot start the driver: # /lib/nut/bestups -DDDDD -a Patriot_Pro_II_750 0.000000 debug level is '5' 0.000806 send_to_all: SETINFO device.type "ups" 0.000842 send_to_all:

[As posted as Ubuntu Question #184284 on Launchpad] Hi, I try to set up nut (2.4.3) on my Lucid (10.04.3 LTS) to make use of my old but very trusty UPS (Best Power Fortress 660 LI). Yes, this UPS is old (about 16 years), but with its third battery pack last week it is as good as new. It runs perfectly well with Windows XP, Vista and even Windows 7. But not so with Ubuntu and nut. After

Hello all, been 5 years since I posted on this list, glad to be back :) I have a number of X-power Tigra 1kVA online UPS units. From some knowledgeable folks working for the local distributor, I learnt that from inside this looked like a Best 610 ups unit. Before, I had this UPS hooked via serial to my Windows 2003 server. For monitoring, some winpilot/upspilot software was also provided.

Hello! I'm trying to use nut with a Ippon Smart Winner 3000 UPS (http://shop.key.ru/photo/items/45535.jpg) which looks like a custom-labeled OEM model of the megatec branch. I tried both the megatec_usb and the blazer_usb drivers for it, with a obvious config section: [ippon] driver = blazer_usb port = auto vendorid = 06da productid = 0003 desc = "Ippon Smart Winner 3000" If I

On Thu, Jun 26, 2014 at 10:20 PM, Steve Ballantyne <steve.ballantyne at gmail.com> wrote: >> However, we don't have all of the 09AE/0001 protocols decoded in the >> tripplite_usb driver. > > I can try to help out on this front? :-) Definitely. >> > 9.783126 Unknown input voltage range: 0x02 >> > 9.783308 Unknown number of switchable

Hello Charles, Thanks for the feedback. I will try to answer some of these questions: > 09AE/0001 is essentially a USB-to-serial converter, and is not > compatible with usbhid-ups. (Theoretically, we could have a companion > driver that talks the same protocols over a real RS-232 port, but the > hardware I used to develop the tripplite_usb driver only has a USB > port.) Ah, that

Hi all, I have problem with UPS from PowerWalker model VFI 2000 RT LCD over USB (didn't try serial yet). UPS should work via HID driver but ups.status is not rendered properly. Specification of UPS says USB HID compatible. HID driver is the only one which talks with UPS as i try a few from /lib/nut. I use driver usbhid-ups (which communicate with ups), but subdriver resolving is

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

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

<nut-upsuser at lists.alioth.debian.org> I am doing my best to avoid have to spend $280 for a network monitoring card to put into a $190 UPS just to have some good remote monitoring capabilities. Rather, I would like to monitor my many 1U Tripp Lite's on my network using a Raspberry Pi running Raspian and using NUT. However, I cannot seem to get it working. And I while the hardware