similar to: bestfortress driver establishes/loses/establishes communication and so on...

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 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 >

<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

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

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

Well, now that the `subdriver` option got added to `usbhid-ups` too, you can at least try that (by building again the current master). See command-line help for the subdrivers it would currently recognize, and copy e.g. the first word as the matching option, e.g.: ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x vendorid=... -x productid=... -x subdriver=... and try to lockpick your

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 There, I tried your advice and i don't think it works either, See the logs, " /tmp/nut# ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x vendorid=... -x productid=... -x subdriver=... Network UPS Tools - Generic HID driver 0.52 (2.8.0-2557-g81fca30b2) USB communication driver (libusb 1.0) 0.46 ?? 0.000000??? [D3] main_arg: var='port' val='auto' ??

<facepalm ;)> the ellispis "something=..." were supposed to be replaced by your device ID numbers, etc. On Sat, Sep 23, 2023, 18:26 FatGear <fatgear1 at free.fr> wrote: > Hello There, > > I tried your advice and i don't think it works either, > > See the logs, > > " > > /tmp/nut# ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x

I could not make the bestfortress driver 0.02 work for my Best Fortress LI675VA, so I have made a patch for the driver. The reason was, that all responses are preceded and terminated by CR LF, but the driver would discard everything after the first CR LF. The following patch discards everything up to the first LF. It also adds a debugging feature of displaying the accepted data (level 5 i.e. -D

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:

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

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.

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:

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