[Nut-upsdev] NUT and UPS TS Shara

[Charles Lepple]

[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 Rodolfo, there is a newer driver called "nutdrv_qx". It will eventually replace blazer_*, so we will need to port your modifications from blazer_usb.c to a new subdriver in nutdrv_qx.

Here is the documentation for updating nutdrv_qx:

http://www.networkupstools.org/docs/developer-guide.chunked/ar01s04.html#nutdrv_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>, 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:
> 
> 
> Which version of NUT did you modify?
>          The version is 2.6.1 or before
> 
> In the current version of NUT, we have an improved driver for Megatec Qx protocols called nutdrv_qx. Your modifications should work in the new driver, but we need to know what version of blazer_usb.c you started with.
> ok
> > I am developing the possibility for the company I work called TS Shara, that produces nobreaks (UPS) in São Paulo, Brazil, to use your software (NUT) in order for our nobreaks (UPS) start working with a Linux platform/ environment. The objective is to achieve a control/monitoring system for our nobreaks (UPS), especially when they exchange information with a Linux platform. 
> > 
> > We are really interested and pleased with the software results. However, it was necessary to use a driver (tsshara.tar.gz) in order to work with our nobreaks (UPS). This occurs because our USB hardware (located in our UPS) does not create a Virtual Com when the UPS is connected to the computer.
> 
> Correct, all of the USB sub-drivers in blazer_usb and nutdrv_qx use libusb directly, and do not need a Virtual COM (/dev/ttyUSB*) port kernel driver. 
>          Ok. We use libusb directly and not need a virtual com port kernel driver.
> 
> > We would like to know if it is possible to input the sub-routine "sgs_command" located in blazer_usb.c.txt in the nut code? So that any user is able to download and install the software directly from the NUT site, without any other additional file like the one attached.
> 
> This should not be too hard. Is the major difference from cypress_command() that the commands are transferred in 7-byte chunks instead of 8-byte?
>          Correction: The chunks are up to 7 bytes. The size of chunk is indicated by the first byte. When this byte is = 0, this is end of transmission.
> 
> > We would also like that the software interface displaying all the status of the UPS is fully written in Portuguese. Is that possible?
> 
> In order to keep the network protocol and drivers simple, the status is not translated. However, clients such as the Python NUT-Monitor script, the CGI programs, wmnut and WinNUT could be translated.
>          ok 
> 
> NUT-Monitor has already been translated into Italian and French: scripts/python/app/locale/
> 
> https://github.com/networkupstools/nut/tree/master/scripts/python/app/locale/
> 
> > We are available to help in order to solve any problem that might happen.
> 
> Good to know, thanks! We look forward to working with you.
> 
> > <tsshara.tar.gz>
> 
> I looked at these binaries, and they appear to be old (NUT v2.6.3). I think it would be better if we merged the source code.
>          ok 
> 
> Also, we do not mind if you distribute binaries of NUT, but the GPL requires you to provide a way to get the source code you used to build that version. In this case, if you are distributing tsshara.tar.gz, you could do this by:
> 
> * including all of the NUT source code in that archive,
> * include a patch file, and say where to get the base version of NUT, or
> * provide a link to the modified source code 
> http://www.gnu.org/licenses/gpl-faq.html#GPLRequireSourcePostedPublic 
>     ok,
> -- 
> Charles Lepple
> clepple at gmail
> 

-- 
Charles Lepple
clepple at gmail



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20140131/cb29526e/attachment.html>