Displaying 20 results from an estimated 800 matches similar to: "Weird Load and Battery Temp Readings"
2017 May 11
4
APC Back-UPS XS 1500G says "No battery"
I have a new-ish APC Back-UPS XS 1500G connected via USB. It's giving me
a "ups.alarm: No battery installed!" error. I also installed and
configured apcupsd to give that a try and it's giving me the same error.
I suspect this is a driver problem because while NUT claims the battery
isn't plugged in, it's giving me battery runtime/charge info. Both can't
be valid
2014 Oct 06
1
Return on experience with an Emerson/Liebert GXT3
Hi
On 10/03/2014 03:42 PM, Charles Lepple wrote:> On Oct 3, 2014, at 7:50 AM, paul.chavent at fnac.net wrote:
>
>
> This is what I was referring to (from the belkin-hid log):
>
>???? 1.325782??? Report[buf]: (5 bytes) => 05 53 00 48 00
>???? 1.325799??? Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x05, Offset: 16, Size: 16, Value: 0
>????
2012 Mar 21
5
Socomec sicon Netys 2000 PR ups USb driver for ubuntu
Hello i tried to connect my netys 2000 pr ups to ubuntu 11.10 and i have a problem connecting it. After readin a few post i realized to dianosse the connection.
I need help resolving the connextion issue
So here is the response to??/lib/nut/usbhid-ups -u root -DDDDD -a netys:
Network UPS Tools - Generic HID driver 0.35 (2.6.1)
USB communication driver 0.31
? ?0.000000 ? ? send_to_all: SETINFO
2015 Mar 13
3
Problems with NUT 2.7.2 on CentOS 7 and using the Mini-Box OpenUPS
I?m a new user of NUT and the OpenUPS - in the past I?ve used APC hardware and apcupsd on Centos 6.
I?ve built NUT 2.7.2 from source but used the OpenUPS HID driver v0.4 that?s in github. I?m using firmware version 1.5 on the openups which is the latest published version; I?ve also tried 1.7 which Mini-box sent to me but reverted to the published version. Their support seems a bit slow!
I?ve got
2009 Sep 20
2
TrippLite Eco Series UPS
I purchased a TrippLite ECO550UPS from Amazon a few days ago thinking
I was going to use it for my Windows Media Center HTPC. I've since
changed my mind and decided to use Mythbuntu but it I can't get my UPS
working with nut. I've tried all of the tripplite drivers and the
usbhid-ups driver. The tripplite_usb and usbhid_ups output is listed
below. The tripplite and tripplitesu drivers
2006 May 22
3
USB UPS and FreeBSD
I am looking at the newhid driver for this Pulsar EXtreme here but it gives
odd results, for example there is no status variable :)
eg
debug level is '2'
Checking device (0463/FFFF) (/dev/usb0//dev/ugen0)
- VendorID: 0463
- ProductID: ffff
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: /dev/usb0
Trying to match device
Device matches
HID descriptor retrieved
2017 May 12
0
APC Back-UPS XS 1500G says "No battery"
On May 11, 2017, at 1:51 PM, Jesse Molina <jmolina at swoncology.net> wrote:
>
> I suspect this is a driver problem because while NUT claims the battery isn't plugged in, it's giving me battery runtime/charge info. Both can't be valid at the same time.
>
> I am at a remote location from the computer and UPS, so I can't physically go over and check. I asked a
2016 May 28
2
Powercom INF-800 support
Hello.
Not listed as supported, so here is some info,
[root at vhost ~]# /usr/sbin/usbhid-ups -DD -a powercom
Network UPS Tools - Generic HID driver 0.38 (2.7.2)
USB communication driver 0.32
0.000000 debug level is '2'
0.001318 upsdrv_initups...
0.074753 Checking device (0529/0001) (003/002)
0.074835 Failed to open device, skipping. (Permission denied)
2015 Mar 13
0
Problems with NUT 2.7.2 on CentOS 7 and using the Mini-Box OpenUPS
[please keep the list CC'd. thanks!]
On Mar 13, 2015, at 10:53 AM, Philip Taylor <philip at kelsotowers.co.uk> wrote:
> I?ve set up UPSMON to simply execute ?shutdown -h now? and my system shuts down when I type ?upsmon -c fsd?. The problem is that the OpenUPS doesn?t shut down as a result; and therefore when the power comes back on, unless the battery has totally run out, the
2014 Oct 10
1
Return on experience with an Emerson/Liebert GXT3
Hi
On 10/06/2014 03:04 PM, Charles Lepple wrote:> I think I see what is going on.
>
>???? 0.368670??? Report[buf]: (5 bytes) => 05 4e 00 48 00
>???? 0.368698??? PhyMax = 0, PhyMin = 0, LogMax = 1, LogMin = 0
>???? 0.368723??? Unit = 00000000, UnitExp = 0
>???? 0.368747??? Exponent = 0
>???? 0.368776??? Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x05, Offset:
2014 Feb 25
0
Setting UPS values can be confusing
Windows 7 Pro x64, NUT 2.6.5-4 (interim release)
Product: Back-UPS RS 1200 FW:8.g3 .D USB FW:g3
Setting UPS values can be confusing. For example, battery.charge.low and
battery.runtime.low.
Using upsrw, the values will be retained after restarting the OS, but
not if the UPS is turned off/restarted.
In the driver log (below), it looks like the values are obtained from
the UPS, but if I set
2024 Mar 25
0
There is no voltage information
Hello all,
I think I've found the "regression" in Belkin/Liebert USB HID support
which worked for NUT v2.7.4 and reports zero voltages in 2.8.0 -- it was
actually caused by a bug fix: practically the only functional difference
per `git diff v2.7.4..v2.8.0 drivers/belkin-hid.c` is a change from `abs()`
to `fabs()` in order-of-magnitude comparisons like `if( abs(value - 1e-7) <
2024 Mar 25
0
There is no voltage information
Hello all,
I think I've found the "regression" in Belkin/Liebert USB HID support
which worked for NUT v2.7.4 and reports zero voltages in 2.8.0 -- it was
actually caused by a bug fix: practically the only functional difference
per `git diff v2.7.4..v2.8.0 drivers/belkin-hid.c` is a change from `abs()`
to `fabs()` in order-of-magnitude comparisons like `if( abs(value - 1e-7) <
2006 May 16
2
MGE Pulsar Extreme communication problems
Hi,
I am trying to talk to an MGE Pulsar Extreme UPS over RS232 with the
mge-shut driver but I'm having some problems.
It appears to init OK but I can't, say, turn the outlets off, eg..
harrow:~>upsc mge@localhost
battery.charge: 78
battery.charge.low: 20
battery.runtime: 05760
driver.name: mge-shut
driver.parameter.port: /dev/cuad1
driver.version: 2.0.3
driver.version.internal: 0.65
2023 Jan 13
1
battery.voltage Powercom Macan MRT-3000
Hello!
I left this line uncommented in powercom-hid.c for battery voltage:
{ "battery.voltage", 0, 0, "UPS.Battery.Voltage", NULL, "%.2f", 0, NULL },
and got some data different from the input voltage values
The Powercom support staff gave the following response to my question:
Dear Alex,
First of all , thank you for purchasing PCM MRT-3000 ups.
Regarding of your
2013 Feb 08
0
Very long delay for shutdown.restart on usbhid-ups powercom
I'm testing a Powercom UPS (branded as Control System 2 STD80S:
http://www.cs2.it/home.php?goto=prodotti&cat=0&idp=2&subid=0) with NUT.
It is a USB HID device, with ID 0d9f:0004.
I configured nut-server to use driver usbhid-ups and it works almost
correctly: upsd communicates right with the device, upsmon catches its
events...
But when I try to perform a Forced Shutdown, UPS pauses
2023 Nov 04
2
EPYC Quantum 1500va
Good Evening, I recently purchased an EPYC quantum UPS. I installed
NUT on the home assistant by connecting the UPS via USB and tried all
the various drivers in the list, the only one that seems to work is:
usbhid-ups
with this log:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
2014 May 29
2
Resetting replace battery status on Pulsar 1500
On 28 May 2014, at 21:59, Charles Lepple <clepple at gmail.com> wrote:
>> What would log it?
>
> The driver.
OK.
>> I could try running the driver with debugging and see if that shows anything of interest.
>
> That should help. Unfortunately for non-debug operation, it appears that most of the usbhid-ups instcmd messages are buried at debug level 3 or 5. That
2016 May 28
0
Powercom INF-800 support
On Sat, May 28, 2016 at 11:05 AM, abi <abi at abinet.ru> wrote:
> However I was unable to shutdown.return it. Maybe protocol is not fully
> compatible?
>
> 0.145757 Initiating UPS shutdown
> 0.145760 upsdrv_shutdown...
> 0.145763 instcmd(shutdown.return, [NULL])
> 0.145767 powercom_shutdown_nuf: value = (null), command = 5400
> 0.145770
2016 May 28
1
Powercom INF-800 support
On 28.05.2016 19:46, Larry Fahnoe wrote:
> On Sat, May 28, 2016 at 11:05 AM, abi <abi at abinet.ru
> <mailto:abi at abinet.ru>> wrote:
>
> However I was unable to shutdown.return it. Maybe protocol is not
> fully compatible?
>
> 0.145757 Initiating UPS shutdown
> 0.145760 upsdrv_shutdown...
> 0.145763