Displaying 20 results from an estimated 2000 matches similar to: "NUT and UPS TS Shara"
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
2018 Feb 27
2
Work around for power recycling after shutdown.return - TSSHARA UPS - nutdrv_qx driver - megatec protocol
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
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
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 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.
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:
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".
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
2012 May 09
0
NUT
Hi Marcio,
first, please subscribe to the NUT mailing list prior to sending any
further mail:
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
next, most (if not all) people you mailed to are either retired from
the project, or not active anymore.
2012/5/8 Marcio - NHS <marcio at nhs.com.br>:
> Dear
2015 Feb 14
2
freenas USB connection error
Hi all,
I'm a new user trying to get a Proline UPS I1000 UPS to work with freenas 9.3
over USB. When running upsdrvctl I get a permission denied error.
Required debug info:
OS name and version,
# uname -a
FreeBSD freenas.local 9.3-RELEASE-p5 FreeBSD 9.3-RELEASE-p5 #2
r275790+f84e770: Tue Dec 23 23:35:33 PST 2014
root at
2014 Feb 18
2
nut driver for SMS (brazil) UPS
Hi,
Recently I got three units of this nobreak [0]:
The intention is connect it with some file server and/or web server.
I found the NUT via FreeNAS [1] , and the contribuition [2] of Ulisses and
Rodrigo about this vendor SMS, in Brazil.
But, initially, i'm trying to apply the Ulisses patch (for smsbrasil
driver) in a Debian Server, with no success.
Can anyone help me about the patch in
2015 Feb 15
0
freenas USB connection error
On Feb 14, 2015, at 2:43 PM, J Neethling <jneethling at webmail.co.za> wrote:
> 67611 blazer_usb CALL write(0x2,0x7fffffffd2a0,0xc)
> 67611 blazer_usb GIO fd 2 wrote 12 bytes
> " 0.280697 "
> 67611 blazer_usb RET write 12/0xc
> 67611 blazer_usb CALL write(0x2,0x7fffffffd2a0,0x35)
> 67611 blazer_usb GIO fd 2 wrote 53 bytes
>
2014 Nov 12
0
upsonic IRT1000 on ubuntu 14.04lts
On Nov 12, 2014, at 2:49 AM, Klint Gore <kgore4 at une.edu.au> wrote:
> Can someone give me a push in the right direction with this? I?m trying to get an upsonic IRT1000 to work on ubuntu 14.04lts using the usb connection. The most likely drivers (blazer_usb and usbhid-ups) don?t seem to recognize it or I?ve got the configuration parameters wrong. I?ve got no idea what driver it
2014 Nov 12
1
upsonic IRT1000 on ubuntu 14.04lts
-----Original Message-----
>From: Charles Lepple [mailto:clepple at gmail.com]
>Sent: Thursday, 13 November 2014 12:12 AM
>
>I am surprised that the blazer_usb configuration didn't work. If you leave off
>the matching options, does this find the UPS?
>
>[upsonicRT1000]
> driver=blazer_usb ## or nutdrv_qx
> port=auto
> desc="UPSonic RT1000"
2018 Mar 05
1
UPS Hunnox HNX-650
Hello, I have an UPS Hunnox HNX-650 (http://www.hunnox.com/), but it's
not quite running yet with NUT. Any hints? Thanks...
Some info:
* lsusb:
Bus 005 Device 003: ID 0001:0000 Fry's Electronics
* usb-devices:
T: Bus=05 Lev=01 Prnt=01 Port=02 Cnt=02 Dev#= 3 Spd=1.5 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0001 ProdID=0000 Rev=01.00
S:
2015 Sep 18
2
[HCL] Micropower LCD 1000 supported by blazer_usb
Device web page http://www.samurai-power.com/samurai-smart-1000-lcd
UPS is marked as Micropower LCD 1000, but in Slovenia is remarked as
Samurai LCD 1000
[ups]
driver = blazer_usb
port = auto
vendorid = 0001
productid = 0000
upsc ups
Init SSL without certificate database
battery.charge: 100
battery.voltage: 27.40
battery.voltage.high: 26.00
battery.voltage.low: 20.80
battery.voltage.nominal:
2015 Sep 10
2
blazer_usb Shutdown
Hi,
I am using a ALLNET 91500 UPS with blazer_usb driver
/usr/lib/ups/driver/blazer_usb -a ups91500 -L
Network UPS Tools - Megatec/Q1 protocol USB driver 0.10 (2.7.1)
I have this settings:
upsc ups91500 at localhost
battery.charge: 100
battery.runtime: 12000
battery.voltage: 27.50
battery.voltage.high: 27.3
battery.voltage.low: 18.0
device.type: ups
driver.flag.novendor: enabled
driver.name:
2015 Apr 03
0
I'm new to NUT in Windows, having problems with blazer_usb doing an UPS shutdown
On Apr 3, 2015, at 1:54 PM, Humberto M?ckel <hamberthm at gmail.com> wrote:
> I've successfully configured UPSMON to monitor the UPS status, and do the shutdown procedure by calling the SHUTDOWNCMD on a simple bat file I've made. This bat file is as follows:
>
> cd C:\Program Files (x86)\NUT\bin
> blazer_usb -a HAMUPS -k
> pause
>
> So this should send the
2017 Jun 10
2
Help with Elite 800VA usb UPS
>
> hmm, apparently the UPS doesn't close the replies to our queries with
> the expected CR and we (I) did not consider that case in nutdrv_qx --
> noted:
> https://github.com/networkupstools/nut/issues/441
>
> But blazer_usb, being less strict on the terminating CR of Q1 replies,
> should work with your device.
>
> > root at artu:~# upsc Elit at artu
> >