[Nut-upsdev] NUT supports new VID/PID

abeyoungh at gmail.com abeyoungh at gmail.com
Thu Feb 15 04:24:00 GMT 2024


Hello Jim,

 

        Thanks for your prompt reply and happy lunar new year.

 

        I think my situation is first one. Actually I am from CyberPower UPS manufacture. In the past, CyberPower UPS works well with NUT. Today, I want to use another VID/PID to fulfill ODM business rather than CyberPower brand UPS. My engineer will apply standard USB power device description like as CyberPower’s USB design. The only difference is VID/PID. What I request is someone could help me finish following two items. 

A.	Offer the beta NUT version that should include below requirement to me. I will test it by myself. 

I.            New VID "0x0483", PID "0xA430"

II.          Corresponding existing (sub-)driver "usbhid-ups"

III.        Manufacture "CyberEnergy"

B.	Once the beta NUT is compatible with new UPS, help me pull request until formal NUT support my new VID/PID device. 

 

Can you help me or suggest proper person to complete above? How much should I pay for this, please let me know if anything that I should notice.

 

Thank you very much and look forward your further feedback, 

Eric Hsu

 

From: Jim Klimov <jimklimov+nut at gmail.com> 
Sent: Wednesday, February 7, 2024 4:10 PM
To: abeyoungh at gmail.com
Cc: nut-upsdev <nut-upsdev at alioth-lists.debian.net>
Subject: Re: [Nut-upsdev] NUT supports new VID/PID

 

Hello and welcome!

 

  It really depends on what it really means to "add support":

 

  If the needed abilities are already present in an existing driver and its sub-driver (`usbhid-ups` as you say, if this uses a HID protocol, or `nutdrv_qx` likely otherwise), and the issue is just about adding the IDs to the suitable handler so it "knows" it is compatible during device detection, then it is trivial. In fact, if you go to NUT GitHub Wiki page to look for "Building in-place" instructions, you can experiment locally and post a pull request with a checked-working change set.

 

  If this issue is however about adding a new (or extending an old) (sub-)driver, then I really hope some of the list members can help with the investigation and coding.

 

Hope this helps,

Jim Klimov

 

On Wed, Feb 7, 2024, 07:50 abeyoungh--- via Nut-upsdev <nut-upsdev at alioth-lists.debian.net <mailto:nut-upsdev at alioth-lists.debian.net> > wrote:

Hi all,

 

        I am looking for someone who help me request NUT to supports power device which has unregistered VID/PID. I will pay you for your service.

 

        Detail requirement

1.	New VID "0x0483", PID "0xA430"

2.       Corresponding driver "usbhid-ups"

3.       Manufacture "CyberEnergy"

 

I have no idea to handle this. If need more information, please let me know, thanks.

_______________________________________________
Nut-upsdev mailing list
Nut-upsdev at alioth-lists.debian.net <mailto: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/20240215/19051c7f/attachment.htm>


More information about the Nut-upsdev mailing list