search for: tsshara

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 rapsberry pi on it they would cycle forever. I tested the shutdown.return using the upscmd and I didn't see this behavior, so I...

...1: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 reconnect > the usb after the power is back it would start another shudown.return cycle. > When I used my rapsberry pi on it they would cycle forever. Jairo, what's the exact model of the UPS? Version of NUT/nutdrv_qx?...

...gt;> > >> > 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 rapsberry pi on it they would cycle forever. >> >> Jairo, wha...

...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 reconnect > > the usb after the power is back it would start another shudown.return > cycle. > > When I used my rapsberry pi on it they would cycle forever. > > Jairo, what's the exact model of the UP...

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

...drv_qx-subdrivers Dan, do you have time to help them with this? The previous email in this thread has their modified blazer_usb.c. > Thank you very much for your cooperation. > > Best regards > > Leonardo Sosa > sosabrasil at gmail.com > > > 2014/1/29 <rodolfo at tsshara.com.br>: > > De: "Charles Lepple" <clepple at gmail.com> > Em: Quarta 29 de Janeiro de 2014 11:46, > Para: rodolfo at tsshara.com.br > Assunto: Re: NUT and UPS TS Shara > Hi Rodolfo, > > [please reply to <nut-upsdev at lists.alioth.debian.org>, no...

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

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 to communicate with our hardware, because our hardware is not able to create a Virtual COM. In order to do that, the file attached will pe...

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 [megatec_usb] Carlos Rodrigues (c) 2...

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:

Alexander Gordeev wrote: > Author: agordeev-guest > Date: Mon Aug 13 13:09:43 2007 > New Revision: 1049 > > Log: > drivers/megatec_usb.c: added credits to the banner message. Is this really needed/desirable? I think this kind of information needs to be put in the AUTHORS document. There are many more people on this list that put a lot of effort in NUT, without claiming credit

Hi! I don't know how I missed it before, but "bestups" seems to implement mostly the same protocol as megatec. Is anybody out there using this driver willing to try "megatec" to see if it works? AFAIK, the only difference seems to be the command that gets the UPS identification data ("I" on "megatec", "ID" on "bestups"), but

Hi! I don't know how I missed it before, but "bestups" seems to implement mostly the same protocol as megatec. Is anybody out there using this driver willing to try "megatec" to see if it works? AFAIK, the only difference seems to be the command that gets the UPS identification data ("I" on "megatec", "ID" on "bestups"), but