similar to: Any ideas what protocol GE VH3000 UPS might talk?

On 6/24/24 11:30, Jim Klimov via Nut-upsuser wrote: > Got a community question at > https://github.com/networkupstools/nut/issues/2466 > <https://github.com/networkupstools/nut/issues/2466> with at least two > users (and UPSes) in trouble. > > Curiously, they identify as |067b:2303 Prolific Technology| like a > common USB-Serial dongle brand. Experiments with blazer

On 6/24/24 12:50, gene heskett via Nut-upsuser wrote: > On 6/24/24 11:30, Jim Klimov via Nut-upsuser wrote: >> Curiously, they identify as |067b:2303 Prolific Technology| like a >> common USB-Serial dongle brand. Experiments with blazer and nutdrv-qx >> got no reasonable response from the devices. >> >> Jim >> > The cure Jim, is eliminate the prolific by

On Wed, Jul 8, 2020 at 8:46 AM H <agents at meddatainc.com> wrote: > > I believe I mentioned that the UPS has the serial port, the computer thus > has USB. > > yes, but is it 'basic serial UPS' or is it 'enhanced serial UPS' ? the former do NOT use the rx/tx data of the serial port at all, they ONLY use the serial port control signals, and they probably

On Wed, Jul 08, 2020 at 01:40:27PM -0500, Chris Adams wrote: > Once upon a time, John Pierce <jhn.pierce at gmail.com> said: > > yes, but is it 'basic serial UPS' or is it 'enhanced serial UPS' ? the > > former do NOT use the rx/tx data of the serial port at all, they ONLY use > > the serial port control signals, and they probably will NOT work with a

hello everyone, I've been testing the NUT solution as opposed to the undocumented LanSafe application to control my Eaton UPS. I am on a Slackware 13.37 system with a 2.6.37.6 kernel. NUT version is 2.4.3 . I installed the tarball by compiling it directly on my system (as a slackbuild package). The UPS is an Eaton Powerware 9155, but I don't know how to obtain the manufacturing date. The

Hi Occasionally I get emails from my NUT system saying that one of my UPSes lost power for about a minute. Losing power: Date: 15. nov 2010 17.40.25 CET regaining power: Date: 15. nov 2010 17.41.34 CET 69 seconds later. But why? None of the 3 other UPSes reports any power loss. What is the problem? So I made some scripts that logs the input, output and frequency at the time of power loss,

Hi Users NUT, I want monitor a UPS of brand SMS (Sinus Double 8 KVA) using a raspberry-pi. In compatibility list, is listed to use the blazer_ser driver. I use a USB adapter to RS-232 conected in to the No-Breake. Follow the comands e confs. root at rasp:/home/pi# lsusb *Bus 001 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port* Bus 001 Device 003: ID 0424:ec00 Standard

Yes I do have Linux. I have assigned the ups.conf file as seen below.. [testups] Driver = usbhid-ups Port = /dev/ttyUSB0 When I try to start the ups driver I get the following error... $ sudo upsdrvctl start Network Ups Tools - UPS driver controller 2.7.1 Network Ups Tools - Generic HID driver 0.38 (2.7.1) USB communication driver 0.32 No matching HID UPS found Driver failed to start (exit

> Am 16.03.2018 um 14:21 schrieb isdtor <isdtor at gmail.com>: > > Nicolas Kovacs writes: >> Hi, >> >> I have to install CentOS 7 for a client, to act as cache & filtering >> proxy using Squid. >> >> I'd like to use this piece of specialized hardware : >> >>

Hello! At first, i want to run the latest HandBrake (version 0.93) on a Mac with Mac OS 10.4 (Tiger). The problem is, that Handbrake is developed for Mac OS 10.5 (XCode SDK is not compatible to Mac OS 10.4 one). So i decided to try it with wine/darwine. Because wine is better supported on Linux and you can get easier newer version (apt-get), i decided to run HandBrakeCLI.exe on Debian Etch

Jim Klimov via Nut-upsdev <nut-upsdev at alioth-lists.debian.net> writes: > Nearby there's also a `generic_modbus" name. Wondering if the new driver > should be (similar to) `generic_gpio`. sound good. It would be nice if there were an abstraction layer for various GPIO access methods, rather than hard-coding linux, even if there is only one implementation of the

Did refactoring to better split library specifics, now see open/close/read lines that any library should support. Need to split into 2 files, may to go for library? On 2/22/23 20:17, Greg Troxel wrote: > Jim Klimov via Nut-upsdev <nut-upsdev at alioth-lists.debian.net> writes: > >> Nearby there's also a `generic_modbus" name. Wondering if the new driver >>

FWIW, there is precedent with libusb{1,0}, libshut and libhid which abstract NUT operations from a "backend lib" to build against; similar for serial.c used by many drivers. Take care to not conflict by filenames with "real" third-party libs used by the build - especially to avoid mixups for headers and in docs/discussion. Jim On Thu, Feb 23, 2023, 22:16 MODRIS B?RZONIS

Hi There, We have this rather large-ish floor-standing Best Axxium Pro, Model Series 0650. I tried using both the "bestups" and "blazer_ser" drivers with it, but no go. So before I go any further: *Should* one of these work with it and, if not, do I have any options? (E.g.: Modify a current driver, resuscitate one that was started and abandoned, etc.? I can code.) My test

Hi, is there a way to use my Belkin F6H650 on the USB port? I already installed usbhid-support, but neither the hidups worked (reports "/dev/usb/hiddev0 is not a UPS") nor genericups with upstype=7 and the hiddev set as device ("ioctl TIOCMSET: Invalid argument") worked. I have installed the debian sarge package of nut 2.0.1 (2.0.1-4) Regards, Philipp

Great, thanks! Also just for context, this sounded reminiscent of one of the first NUT drivers, `genericups` (for simple contact-closure support, with IIRC serial-port connections rather than GPIO). Nearby there's also a `generic_modbus" name. Wondering if the new driver should be (similar to) `generic_gpio`. @Community verdict: Then there was also an effort some years ago to name

I am trying to use software to program a scanner radio (BCD396t and UASD software). The software installs and seems to run properly, reading and writing database files. But I cannot connect to the scanner, through a USB-to-serial cable. OS: ubuntu-8.10, kubuntu-8.10, debian/lenny (tried them all) lsusb identifies the cable as follows: Bus 002 Device 002: ID 067b:2303 Prolific Technology, Inc.

Hi, I had an issue where after returning the power from a shutdown.return the ups would do another shutdown.return during the boot, and kept this forever. After some investigation I found the problem is a bug on the ups - TSSHARA model, driver nutdrv_qx: every time I shutdown with return, and reconnect the usb after the power is back it would start another shudown.return cycle. When I used my

Hello, this is to let you know I will start working on a modbus driver for the PhoenixContact QUINT-UPS industrial DC UPS, model 2320461. https://www.phoenixcontact.com/online/portal/us?uri=pxc-oc-itemdetail:pid=2320461&library=usen&pcck=P-22-07-01-01&tab=1 I will reuse some parts of the nutdrv-modbus branch, but this will be a model specific driver, not a generic one. Unfortunately

I have an installation where we're replacing a rather old Linux box with a new one that has no parallel ports. The old box has two parallel ports going to Okidata printers. The IOGEAR GUC1284B USB to Parallel Adapter cable looks like it might be a simple solution to this, but I would like to know that it works before getting a couple. Comments? Bill -- INTERNET: bill at celestial.com