Displaying 20 results from an estimated 1000 matches similar to: "Work around for power recycling after shutdown.return - TSSHARA UPS - nutdrv_qx driver - megatec protocol"
2018 Feb 28
2
Work around for power recycling after shutdown.return - TSSHARA UPS - nutdrv_qx driver - megatec protocol
Answers bellow.
2018-02-28 1:41 GMT-03:00 Daniele Pezzini <hyouko at gmail.com>:
> 2018-02-27 14:51 GMT+01:00 Jairo Rotava <jairo.rotava at gmail.com>:
> > 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
2018 Feb 28
0
Work around for power recycling after shutdown.return - TSSHARA UPS - nutdrv_qx driver - megatec protocol
Hello,
I think that on this file nutdrv_qx_megatec.c the definition for
shutdown.stayoff may be wrong. In the file the definition is "S%sR0000\r"m
while on the megatec protocol description (
http://networkupstools.org/protocols/megatec.html) the command is just
"S%s\r".
When I changed it my system was abe to at least stay off, and stopped
making an instant power recycling.
2018 Feb 28
0
Work around for power recycling after shutdown.return - TSSHARA UPS - nutdrv_qx driver - megatec protocol
2018-02-27 14:51 GMT+01:00 Jairo Rotava <jairo.rotava at gmail.com>:
> 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
2018 Mar 02
1
Work around for power recycling after shutdown.return - TSSHARA UPS - nutdrv_qx driver - megatec protocol
2018-02-28 21:11 GMT+01:00 Jairo Rotava <jairo.rotava at gmail.com>:
> Hello,
>
> I think that on this file nutdrv_qx_megatec.c the definition for
> shutdown.stayoff may be wrong. In the file the definition is "S%sR0000\r"m
> while on the megatec protocol description (
> http://networkupstools.org/protocols/megatec.html) the command is just
> "S%s\r".
2014 Jan 31
2
NUT and UPS TS Shara
[please keep the discussion on the nut-upsdev list. thanks!]
On Jan 30, 2014, at 10:20 AM, Jos? Sosa wrote:
> Dear Mr. Lepple
>
> I am Leonardo Sosa and I am watching this issue with Rodolfo and Ronaldo. (in copy)
>
> See below our answers of your questions.
>
> What should I do now in order to include our code sgs_command in your code blazer_usb.c?
As I mentioned to
2014 Jan 29
1
NUT and UPS TS Shara
Hi Rodolfo,
[please reply to <nut-upsdev at lists.alioth.debian.org>, not nut-upsdev-owner, and if you have large attachments, upload them to a web server and post the URL. Thanks!]
On Jan 29, 2014, at 7:59 AM, rodolfo at tsshara.com.br wrote:
> <blazer_usb.c.txt>
> Sorry, we forgot to send another file. We developed this code (blazer_usb.c.txt) so that your software is able
2023 Jan 15
1
PR to test for users of Qx devices (blazer and nutdrv_qx)
Cheers,
One PR waiting to get into 2.8.1 release timeframe is
https://github.com/networkupstools/nut/pull/1652 stemming from issue
https://github.com/networkupstools/nut/issues/1279
The gist of it is that "battery.voltage" and "battery.charge" were not
always reported correctly with nutdrv-qx driver (might be handled better by
blazer drivers though), and the overrides
2010 Mar 25
1
new TSSHARA SOHO II ups
Hi all, My name is Sergio Penen and I'd like to contribute to the project by
developing a new driver for TS SHARA SOHO II usb ups.
I'm almost done decoding the protocol and already have some basic
functionality working with NUT. However I've some doubts on how to integrate
this driver with NUT and I wonder if you could give me some guidance in that
sense. To be more specific: In order
2023 Jan 17
1
PR to test for users of Qx devices (blazer and nutdrv_qx)
Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net>
>
> Cheers,
>
> One PR waiting to get into 2.8.1 release timeframe is https://github.com/networkupstools/nut/pull/1652 stemming from issue https://github.com/networkupstools/nut/issues/1279
>
> The gist of it is that "battery.voltage" and "battery.charge" were not always reported
2023 Jan 17
1
PR to test for users of Qx devices (blazer and nutdrv_qx)
Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net>
>
> Cheers,
>
> One PR waiting to get into 2.8.1 release timeframe is https://github.com/networkupstools/nut/pull/1652 stemming from issue https://github.com/networkupstools/nut/issues/1279
>
> The gist of it is that "battery.voltage" and "battery.charge" were not always reported
2014 Jan 31
1
NUT and UPS TS Shara
2014-01-31 hyouko at gmail.com <hyouko at gmail.com>:
> I changed a couple of things:
> - https://github.com/zykh/nut/commit/ebae0e0e499e7983b4f26562451255a39abb023b#diff-38221201bf335e4da4e2dc77d5c6b3c2R478
> - https://github.com/zykh/nut/commit/ebae0e0e499e7983b4f26562451255a39abb023b#diff-38221201bf335e4da4e2dc77d5c6b3c2R482
Better links:
2016 Aug 31
3
nutdrv-qx powercool 1500VA USB UPS
Further analysis it looks like the status string matches the q1 subdriver
but a lowercase "f" is sent to request it instead of "Q1\r". What do you
think?
---------- Forwarded message ----------
From: "Matthew Wire" <devel at mrwire.co.uk>
Date: 30 Aug 2016 22:51
Subject: powercool 1500VA USB UPS
To: <nut-upsuser at lists.alioth.debian.org>
Cc:
I have
2016 Feb 15
1
nutdrv_qx - Device not supported
Hi
Thank you very much for the feedback. I will download and try to get it
working on the Raspberry Pi.
Regards
Tom
On Sun, Feb 14, 2016 at 1:49 AM, hyouko at gmail.com <hyouko at gmail.com> wrote:
> > I have the RCT 3KVA Axpert solar hybrid inverter. It is also known as
> the
> > MPP Solar PIP-MS series, the IPS-4000WM and the Voltronic Axpert MKS. I
> am
>
>
2007 Jul 01
3
ST7 RS232 USB Bridge (STMicroelectronics) UPS
I used a brazilian UPS from "TS-Shara" which uses the megatec
serial protocol and it works perfectly. Now I have another one from the
same brand (TS-Shara) and it uses a USB cable. I found the following:
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 3 Spd=1.5 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0483 ProdID=0035 Rev= 2.00
S:
2015 Apr 04
2
nutdrv_qx hangs after send: QS
Hi,
I am trying to get NUT 2.7.2 working on my Solaris 11.2 system with a
PowerWalker 2000 VI PSW UPS. I have carefully configured the software such
that it 'works' using custom values in the ups.conf file:
driver = nutdrv_qx
port = auto
desc = "my UPS"
protocol = voltronic-qs
subdriver = cypress
vendorid = 0665
productid = 5161
The problem I'm experiencing is that after a
2014 Jan 31
0
NUT and UPS TS Shara
I added the sgs subdriver to nutdrv_qx:
https://github.com/zykh/nut/tree/ts-shara
(I assumed Rodolfo - surname? - is the author of the code, do you want
me to change it?)
I changed a couple of things:
- https://github.com/zykh/nut/commit/ebae0e0e499e7983b4f26562451255a39abb023b#diff-38221201bf335e4da4e2dc77d5c6b3c2R478
-
2018 Jun 10
1
nutdrv_qx for windows
Hello!
We have FSP DPV 1000 USB and we want to use NUT to get data from this
UPS. Unfortunately we have only Windows and current Windows port doesn't
have nutdrv_qx, which should support this UPS.
Is there any possibility of getting nutdrv_qx for Windows? Please help.
2012 Aug 29
1
NUT with pfsense 2.0.1
Hi all
I need to control an UPS TSSahara usign NUT in pfsense and it is not
working.
Can somenone help ?
ups.conf
user=root
[tsshara]
driver = megatec_usb
port = auto
vendorid = 0483
productid = 0035
desc = "No Break TS-Shara"
[myups]
driver=usbhid-ups
port=auto
/usr/local/libexec/nut/megatec_usb -u root -a tsshara -DD
Network UPS Tools 2.2.2 - Megatec protocol driver 1.5.14
2014 Nov 01
3
nutdrv_qx and Best Power equipment
Hi Daniele,
I finally got a Best Power Patriot Pro II fixed up with a new battery and cable, and tried it with nutdrv_qx (since it uses a variant of the Q1 protocol). It auto-detected the use of Q1.
It looks like things mostly work:
bestups:
battery.charge: 100.0
battery.voltage: 13.9
battery.voltage.nominal: 12
device.mfr: Best Power
device.model: Patriot Pro II 400
device.type: ups
2016 Feb 13
2
nutdrv_qx - Device not supported
Hi
I have the RCT 3KVA Axpert solar hybrid inverter. It is also known as the
MPP Solar PIP-MS series, the IPS-4000WM and the Voltronic Axpert MKS. I am
trying to monitor the inverter using NUT on a Raspberry Pi (I have tried
Ubuntu as well with the same results). I have tried most of the drivers
with no success. The inverter came with the ViewPower software so I
assumed that my best chance