search for: prolifer

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

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

I have a 40GB IDE laptop hard drive I took out of a dead laptop and I was hoping to put some good use to it. The drive is inside a USB drive enclosure and I carry it in my laptop bag. Its not big enough to be a backup drive, and generally too big to BIOS boot from. The chipset on the enclosure is from Prolific and registers as a "Mass Storage Device" I haven't had good luck with

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

Got a community question at 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 and nutdrv-qx got no reasonable response from the devices. Jim -------------- next part -------------- An HTML attachment was scrubbed... URL:

Got a community question at 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 and nutdrv-qx got no reasonable response from the devices. Jim -------------- next part -------------- An HTML attachment was scrubbed... URL:

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

I'm back to trying to get my MGE Elipse (USB) talking to my FreeBSD system. It used to work fine on Linux (quite some time ago), and was sort-of working with the last release of nut. The system would see the UPS, but couldn't get reliable data from it. Now that I have upgraded to 2.2, I no longer see the UPS at all with nut. The usbdevs command shows it: drich at morpheus|505>

I am far from expert on these matters. But have a couple questions: 1. Are you sure that /dev/ttyUSB0 exists and is the result of the Prolific USB->serial converter? For example, if you yank the Prolific and reboot, is /ttyUSB0 there still? It is possible that there is another /dev/ttyUSBx out there.I doubt this but wonder. 2. I have recently been fuddled due to permission problems of

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

I have a USB to serial converter attached to my box. pl2303: Prolific PL2303 USB to serial adaptor driver if I login to the box and send/receive serial commands over this unit it works without error EVERY time. however, if I run the same command set from with-in the extensions.conf with System() I get errors in dmesg like "pl2303 ttyUSB0: pl2303_open - failed submitting read urb, error

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

Hello, I have two SMS PowerVision PV2200 BIFX, that came with a serial port, I used a serial - usb conversor to conect it to my pc it recognized as: lsusb -s 001:005 -vvv Bus 001 Device 005: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at

doctordruidphd wrote: > 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

I have multiple servers running stock CentOS 7 rsyslog 7.4.7-16.el7, which are configured to log locally and over TCP to a remote logserver, also running stock CentOS 7 rsyslog. The remote server uses imptcp to receive, and pretty basic rules to parse and commit to disk. I have several systems that log prolifically, but periodically, they stop soon after the remote log server HUPs (daily

Hello. I have an cheap seriell to usb adapter with the Prolific chipset hooked on my mac, but I don't know which tty to configure. OS X regognizes the device in its system profiler. /dev/ttys0 seems wrong. Can someone please enlighten me? Thank you for your help! Greetings, Robert Welz

Hello I installed CentOS 8 on a clean system.I tested a pl2303 ic with different PID. If i use HP PID 0x4349,i will receive junk data after connecting, but the pl2303 PID 0x2303 work normally. Does someone know about how to fix this situation? thanks Test video link: HP VID/PID - https://www.dropbox.com/s/9hj7im5tr4e1v1u/HP.mp4?dl=0 Prolific VID/PID -

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 > USB port because they require very specific behavior from those signals at

On Thu, Jul 9, 2020 at 5:00 AM <centos-request at centos.org> wrote: > 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