<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size: 12pt; color: rgb(0, 0, 0); font-family: Calibri, Helvetica, sans-serif, EmojiFont, "Apple Color Emoji", "Segoe UI Emoji", NotoColorEmoji, "Segoe UI Symbol", "Android Emoji", EmojiSymbols;" dir="ltr">
<p style="margin-top:0;margin-bottom:0">Dear Daniele,</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">I'm trying to create a subdriver for 'nutdrv_qx' instead of modifying the Blazer as you suggested, but i honestly don't understand how to integrate usb-serial devices (some of our UPSs have USB but serial protocol Q1).
i understand the serial version but not the USB one.</p>
<p style="margin-top:0;margin-bottom:0">i also checked the "Claim" function, but i can't see drivers that uses the VID and PID to match the device (for nutdrv_qx).</p>
<p style="margin-top:0;margin-bottom:0">if you have the name of a usb driver for nutdrv_qx could be really helpful and i will study on top of it, otherwise if you have any docs regarding this please send me the link!</p>
<p style="margin-top:0;margin-bottom:0">I also checked the nutdrv_qx.c and i found "Krauler subdriver", but i'm not sure how it works.</p>
<p style="margin-top:0;margin-bottom:0">thanks in advance,</p>
<p style="margin-top:0;margin-bottom:0">Best Regards,</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">Gabriele Taormina</p>
<div id="Signature">
<div id="divtagdefaultwrapper" dir="ltr" style=""><br>
<p style="color:rgb(0,0,0); font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
</p>
</div>
</div>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>Da:</b> Daniele Pezzini <hyouko@gmail.com><br>
<b>Inviato:</b> giovedì 12 luglio 2018 02:20<br>
<b>A:</b> Gabriele TAORMINA<br>
<b>Cc:</b> nut-upsdev@alioth-lists.debian.net; Thierry DESTRUEL; Stefano PONGILUPPI<br>
<b>Oggetto:</b> Re: [Nut-upsdev] Adding drivers to NUT?</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">> - I can send you the whole sources for our UPSs, do you need only Headers<br>
> and C files or also other files (i suppose Driver list)?<br>
<br>
If you can't generate a patch yourself (either `diff -u` or `git<br>
format-patch`, well probably even `git diff`, will do), send any file<br>
you've touched and tell us from what you started.<br>
<br>
> - Seen that we had some problems with the Blazer driver (the battery voltage<br>
> calculation were not correct for our UPSs) we copied it and modified a bit<br>
> while changing the name, is this possible or it's a problem for devs?<br>
<br>
Generally speaking, it's not a problem, as long as copyright and<br>
license are respected -- it's more a question of opportunity, then: is<br>
it worth creating a new driver if the changes are not big?<br>
Since you mention the blazer drivers, if your devices use a Q1-like<br>
protocol that is not already supported by the nutdrv_qx driver, if<br>
feasible, you should add a subdriver to it (or modify an existing<br>
one), rather than creating a new driver. See:<br>
<a href="https://networkupstools.org/docs/developer-guide.chunked/ar01s04.html#nutdrv_qx-subdrivers" id="LPlnk672186" class="OWAAutoLink" previewremoved="true">https://networkupstools.org/docs/developer-guide.chunked/ar01s04.html#nutdrv_qx-subdrivers</a><br>
<br>
> We have no problems to send you protocols of our UPSs.<br>
<br>
Good to hear. If you send this first, we can decide together what's<br>
the best solution.<br>
</div>
</span></font></div>
</div>
</div>
<br>
<hr>
<font face="Tahoma" size="2">
<p>Ce message, ainsi que tous les fichiers joints à ce message, peuvent contenir des informations sensibles et/ ou confidentielles ne devant pas être divulguées. Si vous n'êtes pas le destinataire de ce message (ou que vous recevez ce message par erreur), nous
vous remercions de le notifier immédiatement à son expéditeur, et de détruire ce message. Toute copie, divulgation, modification, utilisation ou diffusion, non autorisée, directe ou indirecte, de tout ou partie de ce message, est strictement interdite.
</p>
<br>
<p>This e-mail, and any document attached hereby, may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized,
direct or indirect, copying, disclosure, distribution or other use of the material or parts thereof is strictly forbidden.</p>
</font>
</body>
</html>