similar to: Microdowell (cpsups) driver segfault

Hi, I've installed Nut 2.0.5 on a RedHat 9 box. I have a GeekSquad 1500 UPS. (GeekSquad is a BestBuy brand) I've found out that it's actually a CyberPower 1500 AVR LCD. I'm using it with the serial cable. I'm unable to get it working with any of the drivers provided with NUT. I've tried cpsups, cyberpower and powerpanel. here's the output of the different drivers

Hi there First a big thank you to all nut developers. I tried the 2.0.4 as well as the 2.0.5-pre1 versions with my CyberPower OP1000E connected to a serial to USB converter. All I got was the following: # /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5-pre1 Network UPS Tools - CyberPower text protocol UPS driver .05 (2.0.5-pre1) Warning: This is an

Hi Recently i bought a MicroDoWell BP50, and with it followed a USB 2 serial converter. When i plug it into my 2.6.19 kernel, dmesg shows hiddev96: USB HID v1.10 Device [Cyber Power System CPS RS232 USB BRIDGE for UPS] on usb-0000:00:04.2-2 usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver So, i figured i should use usbhid-ups,

Hi, I'm running a Debian server (amd64) with the latest nut package (2.0.3-4). The server is connected to a Cyberpower OP750E ups. This seems to be connectable using nut with the cpsups driver. I've configured /etc/nut/ups/conf with the correct information. Here is what i get when trying to load the driver : serveurmeteo:/home/did# /sbin/upsdrvctl -v start myups Network UPS Tools -

Hello, i am newbie to this soft, but at this moment i like it. I have a few microdowell ups, but i can't get it working with nut 2.0.2 version. I saw that in 1.* was microdowell driver, but in 2.0.2 it doesn't. How can i get work nut 2.0.2 with microdowell ups? Thank You! Viktorija

Hey All: I have a CyberPower OP1250 and I'm trying to mod the cpsups driver to work with it. I added the following lines to cpsups.c /* Added: Andrew Tubbiolo EXPERIMENTAL Aug 15, 2008 */ if(!strcmp(abbr, "#1250VA ")) { dstate_setinfo("ups.mfr", "%s", "CyberPower"); dstate_setinfo("ups.model",

Hello, i just want to know, when will be Microdowell B BOX N30 ups support? If it planned? Or is any way to get work nut with this device? I am using nut latest stable version. Thank you in your advice! -- Best Regards, Viktorija

Hi I got an offer for some microdowell enterprise N- series UPS'ses. The NUT homepage only lists the B.Box BP series. Does anyone know if the Enterprise N- series works with NUT? JonB

I'd like to share some of my experience with this UPS. I've compiled nut from the Debian sid sources. Version is 2.2.1. I'm using the powerpanel driver. It seems shutdown.return does in fact what shutdown.return should do. I'll just copy&paste some of my notes made yesterday: Commands were issued as follows: "upscmd -u admin -p admin bbox at localhost

This weekend, I've been doing some work with the cpsups driver. I'm getting to the point that it seems to be working well, and I've managed to fix some of the trouble with it. How do I go about submitting it to the trunk?

I've just noticed that cpsups isn't listed anymore in driver.list. Any reason not have removed it from the source too? Still on the way to 2.4; any update on your confidence level to remove nitram and cyberpower too? -- Arnaud

Hi, I want to set a make a contingency table which will look like this.. The problem is that I can't  set the table like the following.                      col1     col2       Total     row1              a         b         n10                      rp1       rp2        100                      cp1       cp2       rtp1   ---------------------------------------------     row2            

Hi all, first message to the list. :-) I've got an iBox made by iDowell: http://store.apple.com/uk/product/TR423ZM/A This seems to be similar to the smaller Microdowell UPS: http://idowell.eu/ I cannot get it recognised by the drivers. This is what I get when I plug in the USB connector: Jan 3 19:27:26 compaq kernel: usb 3-2: new low speed USB device using uhci_hcd and address 47

I have two UPSs, one is not connected to a computer. I am looking for a gadget that I can plug in to the other one so I can see the time remaining without a computer.

Citeren Arnaud Quette <aquette.dev at gmail.com>: > Author: keyson-guest > Date: Wed Feb 4 15:03:36 2009 > New Revision: 1765 > > Log: > - Added mocrodowell.c/h into drivers/. add man/microdowell.8. Adjusted > drivers/Makefile.am and man/makefile.am. Adjusted the code for 2.4.0 in the > microdowell.c. Besides the things already mentioned by others and the obvious

I have an old (1997) Best Ferrups (model FE18KVA) that I am trying to monitor for the first time, but all the Best drivers fail to communicate with it. In ups_sync() in bestuferrups.c and bestfcom.c, the "time" command is sent and a one-line response is read. However, on my UPS, that command returns the current time and then prompts for a new time setting. I worked around that by just

Hello, is it to possible to monitor Microdowell B-Box N30 with latest nut? I have tried but wihout any success. Others ups works fine with nut. What about driver to this ups model? Best Regards, Viktorija

The tripplite driver was developed on a machine with a reliable serial connection, and inherited the assumption that the serial line connection would not drop, reorder, or fail character read and writes. This patch adds significantly improved failure mode handling and also does basic checks of data validity. There's also a few minor cleanups/beautification. I've tested this code on my

Description: Replace many usleep and some sleep calls with nanosleep. usleep is stated in its manual page as removed by POSIX. Contrary to its predecessors, nanosleep semantics is well defined. The replacement, which is mostly in drivers, is untested. Supplements http://bugs.debian.org/633791. Last-Update: Sat, 13 Aug 2011 14:04:48 +0300 Index:

It seems the `libmodbus` library or headers were not found, or something similar - so the driver against it was not built. Did you install `libmodbus-dev` before the build? What does `config.log` in the build root say (and.or the summary shown after you run the `configure` script)? On Sat, Sep 16, 2023 at 7:46?PM FatGear <fatgear1 at free.fr> wrote: > Hi, > > I don't know what