Hi Peter,<br><br><div class="gmail_quote">2012/10/31 Peter Senna Tschudin <span dir="ltr"><<a href="mailto:peter.senna@gmail.com" target="_blank">peter.senna@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Tue, Oct 30, 2012 at 11:43 PM, Arnaud Quette <<a href="mailto:aquette.dev@gmail.com">aquette.dev@gmail.com</a>> wrote:<br>
><br>
><br>
> 2012/10/30 Peter Senna Tschudin <<a href="mailto:peter.senna@gmail.com">peter.senna@gmail.com</a>><br>
>><br>
>> On Mon, Oct 29, 2012 at 9:37 PM, Arnaud Quette <<a href="mailto:aquette.dev@gmail.com">aquette.dev@gmail.com</a>> wrote:<br>
>> > Hi Rodrigo and Peter,<br>
>> Hi Arnaud!<br>
><br>
><br>
> Hi Peter,<br>
><br>
>><br>
>> ><br>
>> > 2012/10/28 Rodrigo Vigna <<a href="mailto:skrull@gmail.com">skrull@gmail.com</a>><br>
>> >><br>
>> >> Hi,<br>
>> >><br>
>> >> NUT does not support SMS (<a href="http://www.sms.com.br" target="_blank">www.sms.com.br</a>) usb models. I found a simple<br>
>> >> piece of code that works. Maybe it could help you develop a driver.<br>
>> >><br>
>> >> <a href="https://github.com/petersenna/nobreakSMS" target="_blank">https://github.com/petersenna/nobreakSMS</a><br>
>> >><br>
>> >> If desired, I could provide a link for the manufacturer bloated<br>
>> >> software (26MB java)<br>
>> >><br>
>> >> Thanks and sorry for my poor english!<br>
>> ><br>
>> ><br>
>> > your english is good, and by all ways better than my brazilian ;)<br>
>> ><br>
>> > @peter: would you be interested in working with the NUT team to integrate<br>
>> > your work in NUT?<br>
>> Yes, how?<br></div></blockquote><div><br>Charles made a good comment on a protocol difference (padding) that may make it worth to create a blazer derivative.<br>but I'm not yet sure since it could well be another communication subdriver, as in the USB version...<br>
I have in mind, for some time now, to create a more advanced version, that would support Q5 (a superset of Q1), i.e blazer 3rd generation (counting the first 'megatec' driver).<br>I need to think a bit more, and check a few things.<br>
<br>knowing that you don't have your SMS handy, for the time being, that would be good if you could familiarize with blazer and the general design of NUT driver. it will be useful in all cases.<br><br>anyway, considering the easiness of creating a NUT driver, you may end up porting it very quickly as a new driver, and have Rodrigo testing it. as a second step, we can check for a potential driver consolidation.<br>
<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
><br>
> great!<br>
> in fact, this protocol is just a variation of Q1.<br>
> check the blazer_ser driver . we may have to check for some changes though ('M' instead of 'Q' for muting buzzer, for example)<br>
</div>I've identified some query/reply. See:<br>
<a href="https://github.com/petersenna/nobreakSMS/blob/master/userland/nobreakSMS.c#L322" target="_blank">https://github.com/petersenna/nobreakSMS/blob/master/userland/nobreakSMS.c#L322</a><br>
<br>
But one known issue is that I do not know how to specify the test time. See:<br>
<a href="https://github.com/petersenna/nobreakSMS/blob/master/userland/nobreakSMS.c#L406" target="_blank">https://github.com/petersenna/nobreakSMS/blob/master/userland/nobreakSMS.c#L406</a><br></blockquote><div><br>theoretically, it should be 'T<n>' where <n> is a number of minutes from 01 to 99.<br>
<br>in NUT, we just have a way to request a quick test ('T', such as in your driver) and a longer one using 'TL' (running until low battery):<br>(from blazer.c)<br>401: { "test.battery.start.deep", "TL\r" },<br>
402: { "test.battery.start.quick", "T\r" },<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This does the test for 10 seconds and I know that the time is on the<br>
query, but I did not understood how to change the time value. Do you<br>
know how to do it?<br>
<div class="im"><br>
><br>
>> ><br>
>> > note that we already have support for SMS Manager III on RS232, with the<br>
>> > blazer_ser driver (Q1 protocol).<br>
>> The USB version uses Cypress chip to do USB-RS232 conversion, in the<br>
>> end the USB version is also serial...<br>
><br>
><br>
> what are the USB vendorID and productID?<br>
</div>I do not know and cant reply until I'm back home in more than 30 days.<br>
I'm in France and left my SMS UPS in Brazil.<br>
(...)<br></blockquote><div> </div>Rodrigo answered this point to me privately, then again to the list: 04b4:5500</div><br>cheers,<br>Arnaud<br>-- <br>Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org" target="_blank">http://www.networkupstools.org</a><br>
Debian Developer - <a href="http://www.debian.org" target="_blank">http://www.debian.org</a><br>Free Software Developer - <a href="http://arnaud.quette.fr" target="_blank">http://arnaud.quette.fr</a><br><br>