vincent_pang at prolink2u.com
2022-Jul-18 01:26 UTC
[Nut-upsdev] To Join - Hardware compatibility list
Hello All Members, Our company UPS product will like to be in this community. Can we join or got any requirement to meet? Thank you & Best Regards, Vincent Pang Sales Manager Fida International (S) Pte Ltd Blk 16 Kallang Place #06-02 Singapore 339156 DID (65) 6357 0664 | M (65) 9800 9506 | E <mailto:vincent_pang at prolink2u.com> vincent_pang at prolink2u.com T (65) 6357 0668 | W <http://www.prolink2u.com/> www.prolink2u.com <https://www.facebook.com/global.prolink> <https://www.linkedin.com/company/prolink2u> <https://www.youtube.com/user/PROLiNKGlobal/videos> If you are neither the email addressee(s) nor responsible for delivery of the message to such person(s), you may not copy, disclose or distribute this message to anyone. If you have received this message in error, kindly destroy it and notify the sender. Any views, opinions and other information presented in this email or its attachments are solely those of the author and do not necessarily represent those of the company and its affiliates or subsidiaries. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20220718/a6ff1635/attachment-0001.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 4539 bytes Desc: not available URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20220718/a6ff1635/attachment-0005.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 1438 bytes Desc: not available URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20220718/a6ff1635/attachment-0006.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 1585 bytes Desc: not available URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20220718/a6ff1635/attachment-0007.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 1521 bytes Desc: not available URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20220718/a6ff1635/attachment-0008.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 5153 bytes Desc: not available URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20220718/a6ff1635/attachment-0009.png>
Hello, and welcome! As far as I know there are no "formal requirements", just the general netiquette for mailing list communications (or github issues for that matter). Vendors are encouraged to at least publish protocols used by their devices for monitoring and management (we can host a copy on the NUT website), and ideally develop and maintain a NUT driver so your devices can be supported out of the box. It would also help both sides to have NUT as the officially recommended toolkit for customers to shut down their servers when power is lost, instead of developing some of your own. * Note: existing NUT for Windows builds are very old (a decade); recently I rebased that codebase over the current master, but the resulting branch would need some attention and testing to become an MSI package for end-users and a "first-class citizen" in NUT ecosystem. Help is welcome :) If your devices support a common method of communications like SNMP or USB-HID, and that goes beyond the bare-minimum standard data points with vendor extensions, this may mean generation of a sub-driver file to map your data points to NUT standard items. Most other devices support a variant of Megatec Qx family of protocols (serial or USB) and if custom support is needed - you should develop a subdriver for nutdrv_qx instead. I haven't seen too many devices lately that would not fall into one of those 3 categories; however recent submissions did include some I2C drivers for (Linux) embedded batteries, and several modbus drivers, for example. Note that for USB drivers either way you would need to update some driver to recognize the Vendor and Product ID (and possibly other matching data if your USB chips are generic with same IDs as everyone else has), and NUT may be strict about protocol conformance (declared and actual bit-lengths of different data in messages, notably some firmwares were seen to encode Logical Min/Max mismatches). There is quite a bit of information in https://github.com/networkupstools/nut/tree/master/docs for developers, packagers and usres. Welcome aboard, Jim Klimov On Mon, Jul 18, 2022 at 4:43 AM <vincent_pang at prolink2u.com> wrote:> Hello All Members, > > > > Our company UPS product will like to be in this community. > > Can we join or got any requirement to meet? > > > > Thank you & Best Regards, > > *Vincent Pang* > > Sales Manager > > > > Fida International (S) Pte Ltd > > Blk 16 Kallang Place #06-02 Singapore 339156 > > *DID *(65) 6357 0664 | *M (65*) 9800 9506 | *E *vincent_pang at prolink2u.com > > *T *(65) 6357 0668 | *W *www.prolink2u.com > > > > > > <https://www.facebook.com/global.prolink> > <https://www.linkedin.com/company/prolink2u> > <https://www.youtube.com/user/PROLiNKGlobal/videos> > > If you are neither the email addressee(s) nor responsible for delivery of > the message to such person(s), you may not copy, disclose or distribute > this message to anyone. If you have received this message in error, kindly > destroy it and notify the sender. Any views, opinions and other information > presented in this email or its attachments are solely those of the author > and do not necessarily represent those of the company and its affiliates or > subsidiaries. > > > > > _______________________________________________ > Nut-upsdev mailing list > Nut-upsdev at alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20220720/6fac2656/attachment-0001.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 4539 bytes Desc: not available URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20220720/6fac2656/attachment-0005.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 1438 bytes Desc: not available URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20220720/6fac2656/attachment-0006.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 1585 bytes Desc: not available URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20220720/6fac2656/attachment-0007.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 1521 bytes Desc: not available URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20220720/6fac2656/attachment-0008.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 5153 bytes Desc: not available URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20220720/6fac2656/attachment-0009.png>