Dear Daniele,
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. 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). 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! I also checked the nutdrv_qx.c and i found "Krauler subdriver", but i'm not sure how it works. thanks in advance, Best Regards, Gabriele Taormina ________________________________ Da: Daniele Pezzini <[email protected]> Inviato: giovedì 12 luglio 2018 02:20 A: Gabriele TAORMINA Cc: [email protected]; Thierry DESTRUEL; Stefano PONGILUPPI Oggetto: Re: [Nut-upsdev] Adding drivers to NUT? > - I can send you the whole sources for our UPSs, do you need only Headers > and C files or also other files (i suppose Driver list)? If you can't generate a patch yourself (either `diff -u` or `git format-patch`, well probably even `git diff`, will do), send any file you've touched and tell us from what you started. > - Seen that we had some problems with the Blazer driver (the battery voltage > calculation were not correct for our UPSs) we copied it and modified a bit > while changing the name, is this possible or it's a problem for devs? Generally speaking, it's not a problem, as long as copyright and license are respected -- it's more a question of opportunity, then: is it worth creating a new driver if the changes are not big? Since you mention the blazer drivers, if your devices use a Q1-like protocol that is not already supported by the nutdrv_qx driver, if feasible, you should add a subdriver to it (or modify an existing one), rather than creating a new driver. See: https://networkupstools.org/docs/developer-guide.chunked/ar01s04.html#nutdrv_qx-subdrivers > We have no problems to send you protocols of our UPSs. Good to hear. If you send this first, we can decide together what's the best solution. ________________________________ 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. 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.
_______________________________________________ Nut-upsdev mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev
