search for: hid2nut

Hello fellow devs, The discussion of https://github.com/networkupstools/nut/pull/431 slowly led the new driver submission from EVER Power Systems to being almost acceptable, with one raised issue being how they would "NUT-name" certain HID entries they could not find equivalents for in the existing NUT documentation. One proposal in the PR was to define a loosely-structured

...ported(). I guess it used to take the vendor and product ID separately, but now just takes a pointer to the USB device. So, remove everything after the first "hd" (so it passes in just the HIDDevice_t hd instead). It works pretty good after that. However, if I'm going to tailor my hid2nut table, it would really help if there was some master list of all the paths (input.voltage, battery.temperature, etc) NUT supports, instead of having to dig through different driver files to see what's available. Is there some list? Rob

Den 14-03-2014 21:29, Rob Groner skrev: > It works pretty good after that. However, if I'm going to tailor > my hid2nut table, it would really help if there was some master list > of all the paths (input.voltage, battery.temperature, etc) NUT supports, > instead of having to dig through different driver files to see what's available. Is there some list? How about http://www.networkupstools.org/docs/d...

...sly have to go into 2.2.2, and the best would be to keep the generic method (not subdrv delegation). So we have 2 possibilities (non exclusive. We may apply (1) quickly, while waiting for (2)) 1) change upsdrv_shutdown() to proceed with setvar instead of (or with) the current instcmd 2) modify the hid2nut mapping to better deal with the shutdown related vars and commands. Can you (all subdrivers maintainers) please ack this, make some tests on your side and report back your feeling about that. Arnaud -- Linux / Unix Expert R&D - MGE Office Protection Systems - http://www.mgeops.com Network UP...

...: - In newhidups.h, add an extra line to the subdriver_s struct; void (*extendvartable)(void); so it becomes; struct subdriver_s { char *name; int (*claim)(HIDDevice *hd); usage_tables_t *utab; hid_info_t *hid2nut; int (*shutdown)(int ondelay, int offdelay); char *(*format_model)(HIDDevice *hd); char *(*format_mfr)(HIDDevice *hd); char *(*format_serial)(HIDDevice *hd); void (*extendvartable)(void); }; - In the subdriver...

...ed. load.on load.off shutdown.return shutdown.stayoff I looked in the usbhid-ups file, and I see where, if it finds load.on.delay or load.off.delay, then it adds the 4 commands shown above. Now, load.on.delay and load.off.delay are the only two commands I *want* to support. So I put them in my hid2nut table: /* Commands to control UPS */ { "load.off.delay", 0, 0, "UPS.PowerSummary.DelayBeforeShutdown", NULL, DEFAULT_OFFDELAY, HU_TYPE_CMD, NULL }, { "load.on.delay", 0, 0, "UPS.PowerSummary.DelayBeforeStartup", NULL, DEFAULT_ONDELAY, HU_TYPE_CMD, NULL }, S...

...t; shutdown.stayoff > > > > I looked in the usbhid-ups file, and I see where, if it finds > load.on.delay or load.off.delay, then it adds the 4 commands shown above. > Now, load.on.delay and load.off.delay are the only two commands I **want** > to support. So I put them in my hid2nut table: > > > > /* Commands to control UPS */ > > { "load.off.delay", 0, 0, "UPS.PowerSummary.DelayBeforeShutdown", NULL, > DEFAULT_OFFDELAY, HU_TYPE_CMD, NULL }, > > { "load.on.delay", 0, 0, "UPS.PowerSummary.DelayBeforeStartup", NU...

...gt; ran usbhid-ups -DDDD -u root -x explore -x vendorid=3344 -x port=auto -a > myups >& /tmp/junda-tech.txt > > and then > > gen-usbhid-subdriver.sh < /tmp/junda-tech.txt' : > [...] > /* --------------------------------------------------------------- */ > /* HID2NUT lookup table */ > /* --------------------------------------------------------------- */ > > static hid_info_t jundatech_hid2nut[] = { > > { "unmapped.ups.powersummary.capacitymode", 0, 0, > "UPS.PowerSummary.CapacityMod...

* I committed into CVS the gendb patch that I sent to the mailing list on September 12. Arnaud, I hope you approve of this patch; it is more reliable than the previous method in tracking the correct dependencies. * This, together with some other minor recent changes on the Development branch, is between the "before_PSE_3" and "after_PSE_3" tags. Arnaud: if you

Hi, I have an UPS with only the marking D1000 on it and it came with Junda-Tech's UpsMate. Its USB id is 3344:0025, which is apparently a microprocessor. I've could get some of the HID interactions as described on the website, but there are some outstanding. Junda-Tech does not respond to any queries. Does anybody else have the same or a similar UPS with more information? What is the

Hi All I'm trying to get my Ultra UPS connected. It connects using a standard USB cable I have --with-drivers=hidups in the configure command and I have lsusb showing Bus 001 Device 002: ID 0d9f:0001 Powercom Co., Ltd Bus 001 Device 001: ID 0000:0000 I have /dev/usb/hiddev0 now matter what I try I keep getting upsdrvctl start Network UPS Tools - UPS driver controller 2.0.3 Can't

...{ "PowercomSerialNumber", 0x00020086 }, { "PowercomManufacturerName", 0x00020087 }, { "\0", 0x0 } }; static usage_tables_t powercom_utab[] = { powercom_usage_lkp, hid_usage_lkp, NULL, }; /* --------------------------------------------------------------- */ /* HID2NUT lookup table */ /* --------------------------------------------------------------- */ static hid_info_t powercom_hid2nut[] = { { "ups.serial", 0, 0, "PowercomUPS.PowercomSerialNumber", NULL, "%s", HU_FLAG_OK, stringid_conv...

...when + * certain request codes are written to USB endpoint */ + /*{ "OpenUPSExtra", 0xff000001 }, */ + {NULL, 0} +}; + +static usage_tables_t openups_utab[] = { + openups_usage_lkp, + hid_usage_lkp, + NULL, +}; + +/* --------------------------------------------------------------- */ +/* HID2NUT lookup table */ +/* --------------------------------------------------------------- */ + +static hid_info_t openups_hid2nut[] = { + {"ups.serial", 0, 0, "UPS.PowerSummary.iSerialNumber", NULL, "%s", 0, stringid_conversion}, +...

...------------------------------------------- */ /* DYNEX usage table */ static usage_lkp_t dynex_usage_lkp[] = { { "\0", 0x0 } }; static usage_tables_t dynex_utab[] = { dynex_usage_lkp, hid_usage_lkp, NULL, }; /* --------------------------------------------------------------- */ /* HID2NUT lookup table */ /* --------------------------------------------------------------- */ static hid_info_t dynex_hid2nut[] = { { "unmapped.ups.powersummary.iproduct", 0, 0, "UPS.PowerSummary.iProduct", NULL, "%.0f", HU_FLAG_O...