search for: subdriver

j T wrote: > >- allow the value to be NULL if a subdriver does not require > > initialization. > > Am I right in thinking that this is simply a case of doing: > > subdriver_t some_subdriver = { > /* ... */ > some_format_serial, > NULL, > } > > Rather than: > > subdriver_t belkin_subdriver = { >...

...an answer. I added you manually, but check your spam folder just in case it ended up there. > Yes, I do have a MIB file that was on CD that came with the UPS, attached it to this message. > > Thanks for the link, started following it and at the step concerning runninh script scripts/subdriver/gen-snmp-subdriver.sh downloaded the archive nut-2.6.2.tar.gz but there is no script gen-snmp-subdriver.sh in it, only file path-to-subdriver.sh in directory scripts/subdriver/. Then through google found the script gen-snmp-subdriver.sh and put in directory scripts/subdriver/ and ran it: Hmm, we&...

Hi I'd like to know what you guys think to the following idea. Please be aware, C/C++ are not exactly my strongpoint (couldn't be much further from it actually..!), so I'm not sure whether this is all legal code. -- SYNOPSIS: Allow a newhidups subdriver to register that it can handle settings in ups.conf (and via -x on the command line), as per the normal serial drivers. DESCRIPTION OF CHANGES: - In newhidups.h, add an extra line to the subdriver_s struct; void (*extendvartable)(void); so it becomes; struct subdrive...

Hi, Nut-upsusers, I am having problem configuring NUT to work with Tripplite UPS through SNMP. There is a Tripplite SmartOnline SU10KRT3/1X and attempts to monitor it using NUT though SNMP are failing... OS: Enterprise Linux 6, Nut version: 2.6.5. ups.conf is configured: [trippliteups] driver = snmp-ups port = 10.200.254.39 desc = "ProductionServer"

...n R Begley wrote: > > > 0.073855 load_mib2nut: trying classic method with 'delta_ups' mib > > 0.073878 Entering nut_snmp_get_str() > > 0.073899 nut_snmp_get((null)) > > 0.073918 nut_snmp_walk((null)) > > Arnaud, > > The gen-snmp-subdriver.sh script is setting mib2nut[i]->oid_auto_check to > NULL for new drivers (with no instructions on what to use in place of > NULL). However, this seems to be only used with the "classic method" for > detecting an UPS. > > Is the intent to phase out the classic method, or...

...and ProductId supported, and introduce then a generic way to make a claim function. For the moment, some claim function just look at the VendorId. But a vendor can do other things than UPS, or make a new UPS that don't use the same USB protocol as the last UPS this vendor created, leading to a subdriver that claim an hardware it cannot support. Having a list of supported UPS and looking for match as well in VendorId and in ProductId solve this problem. But it bring another problem (life is never simple ;-) : What if a producer make a new product under a new ProductId, but this product can perfect...

...ing a Powermust Office 650 USB USV. Using today's trunk megatec_usb detects its vendorid 0665 productid 5161 but uses the agiler driver for it which apparently does not work (timeout...). I think this device is using that USB-to-serial chip but a different protocol behind. I got the phoenix subdriver working with the device but I had to extend subdriver_list[] by &phoenix_subdriver in order to be able to specify it on the command line. Could you please fix this in the trunk? With that change the following ups.conf settings work fine with the USV: [powermust] driver = megatec_usb po...

Thanks, now I started getting messages from the list. As you advised, I renamed the mib file NETCARD.mib to Tripplite and ran command ./gen-snmp-subdriver.sh -H 10.200.254.39 -c public -n Tripplite Here is what it says: snmp_build: unknown failuresnmpget: Error building ASN.1 representation (Can't build OID for variable) COUNT = 0 / 0 Creating tripplite-mib.h Creating tripplite-mib.c Done. The output files are attached, but I think it is not s...

On Feb 25, 2014, at 4:23 PM, Arnaud Quette wrote: > gen-snmp-subdriver.sh simply hasn't done its job, for some reasons. > well, 1 clear is that's it not a completed effort... at all > but, still IIRC, it should have produced at least a bit more Hi Arnaud, I may not have been specific enough in my description. The crash that Jason saw is with the versi...

...- { "driver.version.internal", ST_FLAG_STRING, sizeof(DRIVER_VERSION), NULL, NULL, DRIVER_VERSION, HU_FLAG_ABSENT, NULL }, > - { "driver.version.data", ST_FLAG_STRING, sizeof(APC_HID_VERSION), NULL, NULL, APC_HID_VERSION, HU_FLAG_ABSENT, NULL }, Just curious, why were the subdriver versions removed? -- - Charles Lepple

Thanks to the great help here, I now have a UPS spitting out something resembling a report descriptor. So since I seem destined to have to create a new USB HID subdriver, I figured I'd get started on the path. I followed all of the directions on the web....I used the script to generate the usbhid subdriver, feeding it the output of the usbhid-ups driver from reading my UPS. All that worked pretty well. I copied it in the right dir, and made the changes to us...

On 2015/03/28 20:02, Charles Lepple wrote: > On Mar 25, 2015, at 9:21 PM, Stuart Henderson <stu at spacehopper.org> wrote: > > > Hi, the diff inline below adds a new subdriver for snmp-ups to support > > Huawei UPS, based on an observed walk from a UPS5000-E with a few bits > > filled in from the MIBs (copy at http://junkpile.org/HUAWEI_UPS_MIB/). > > Sample output from upsc follows the diff. > > Hi Stuart, > > Thanks for the patch. It bui...

> Author: agordeev-guest > Date: Wed Oct 3 00:09:21 2007 > New Revision: 1136 > > Log: > - drivers/megatec_usb.c: added ability to do subdriver-specific > initialization, and moved some shared code to agiler init function > since krauler doesn't need it. [...] I'm not very thrilled about this patch: 1) Down at the subdriver level, one shouldn't use ser_get_line() anymore, but usb->get_interrupt() instead or al...

...e a way to make it list likely drivers back to the user when they are a close match and check validity for each one until it gets a good connection? Part of auto select? What NUT currently does in `usbhid-ups` (some other drivers may handle similar stuff differently), is it goes through a list of subdrivers built into the binary and calls those subdrivers' `claim()` methods to see if they report the device is deemed known to that subdriver. Primarily this goes by USB VendorID:ProductID matching, in some cases also clues like manufacturer string (e.g. "mge" and "phoenixtec/liebert&q...

...eper status only every 'pollfreq' (default 30) seconds, so it may have missed the change. > After more testing the indexes work as follows > > 0x0a = load.on / cancel.shutdown.stayoff / cancel.shutdown.return For future reference only (since the following ones are not used in the subdriver): - 0x1A -> cancel shutdown.return, - 0x2A -> cancel shutdown.stayoff, - 0x24 -> load on Are these still valid? > 0x10 and 0x18 are shutdown.stayoff and shutdown.return respectively both > with 30 sec delay > 0x20 and 0x28 = 35 sec delay > 0x30 and 0x38 = 40 sec delay > 0x4...

Here is a summary of the changes I made to newhidups today (between the tags after_PSE_6 and after_PSE_9, roughly). * all the vendor-specific code that was in various "switch" statements has now been moved to the individual subdriver (apc-hid, mge-hid, belkin-hid) files. This also includes the vendor-specific Usage tables. In future, it should be quite easy to add new subdrivers: essentially this involves adding two files and one table entry in newhidups.c. I added a document docs/hid-subdrivers.txt that is intende...

...the list, 2015-03-29 14:17 GMT+02:00 Stuart Henderson <stu at spacehopper.org>: > On 2015/03/28 20:02, Charles Lepple wrote: > > On Mar 25, 2015, at 9:21 PM, Stuart Henderson <stu at spacehopper.org> > wrote: > > > > > Hi, the diff inline below adds a new subdriver for snmp-ups to support > > > Huawei UPS, based on an observed walk from a UPS5000-E with a few bits > > > filled in from the MIBs (copy at http://junkpile.org/HUAWEI_UPS_MIB/). > > > Sample output from upsc follows the diff. > > > > Hi Stuart, > > >...

Hi! I've (finally) decided to try and make my PowerWalker work with megatec_usb. So far it seems the agiler subdriver is the way to go, but it doesn't work. The initial detection process sometimes succeeds in 1 out of 5 "Q1" commands, but that's about it (which is better than what the krauler subdriver can do... absolutely nothing). So, what needs to be done to obtain more information? I don'...

On Feb 28, 2014, at 1:05 PM, Tim Dawson wrote: > Git: > > Network UPS Tools - BCMXCP UPS driver 0.28 (2.7.1) > RS-232 communication subdriver 0.20 > > > 2.7.1: > > Network UPS Tools - BCMXCP UPS driver 0.26 (2.6.5-3857M) > RS-232 communication subdriver 0.20 > > > I'm not so much noting the "2.6.5" in the dev, but the 0.28 vs 0.26 bcmxcp version skew . . . (and yes, I don't have these rev...

Dear Daniele, i understand perfectly, i'd like to explain you why we choosed to clone the blazer_usb driver: some of our devices uses Voltronic Q1 protocol and we tried the Krauler Subdriver (it was the one with the right "commands", Q1, F, etc.), but the issues were 2: - first: the Krauler Subdriver expects a different number of bytes in answer because in debug i see "Short Reply" (if i send Q1 to the UPS it will answer with 47 Bytes, CR terminated), from what i un...