search for: hid_info_t

I don't understand how the info_len element from the hid_info_t structure is used in usbhid-ups. It appears to me that the only use of this element is now to indicate the length of the string: > float info_len; /* if ST_FLAG_STRING: length of the string */ The above is clear, if the element is flagged as a string, the size of this string is put in this var...

...segfault! The quick-and-dirty (but it hasn't failed me yet for 3 months in several installations) patch is below: --- nut-2.0.4/drivers/newhidups.c.orig 2006-08-09 11:35:32.000000000 +0400 +++ nut-2.0.4/drivers/newhidups.c 2006-08-09 11:35:44.000000000 +0400 @@ -452,7 +452,7 @@ hid_info_t *item; char *nutvalue; int retcode, evtCount = 0; - HIDItem *eventsList[10]; + HIDItem *eventsList[30]; upsdebugx(1, "upsdrv_updateinfo...");

...t calculation */ + i_ltc = value * cdischarge_scale; + + /* Output current = Power-in * Efficiency / Vout */ + i_out = v_ltc * i_ltc * .965 / v_out; + + snprintf(openups_scratch_buf, sizeof(openups_scratch_buf), "%.3f", i_out); return openups_scratch_buf; } @@ -304,7 +342,7 @@ static hid_info_t openups_hid2nut[] = { /* Battery */ {"battery.type", 0, 0, "UPS.PowerSummary.iDeviceChemistry", NULL, "%s", HU_FLAG_STATIC, stringid_conversion}, {"battery.mfr.date", 0, 0, "UPS.PowerSummary.iOEMInformation", NULL, "%s", HU_FLAG_STAT...

...N OF CHANGES: - 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 s...

Hi, I've been checking out NUT with an OpenUPS board over the last couple of weekends, and have noticed that it doesn't seem to report sensible values. This lead me to investigate usbhid-ups and delve into various issues. As mentioned in a github issue, one of the problems is with the report descriptor - dumping this from the usbhid-ups debug output and picking through it reveals that

...subdriver.sh < /tmp/junda-tech.txt' : > [...] > /* --------------------------------------------------------------- */ > /* HID2NUT lookup table */ > /* --------------------------------------------------------------- */ > > static hid_info_t jundatech_hid2nut[] = { > > { "unmapped.ups.powersummary.capacitymode", 0, 0, > "UPS.PowerSummary.CapacityMode", NULL, "%.0f", 0, NULL }, > { "unmapped.ups.powersummary.designcapacity", 0, 0, > "UPS.PowerSummary.DesignCapacity",...

was: Re: [Nut-upsdev] usbhid-ups.h: hid_info_t structure On 8/2/07, Peter Selinger <selinger at mathstat.dal.ca> wrote: > All this needs to be replaced by a re-designed, cleaned-up data > structure. It's on my to-do list, but nothing on that list will get > done by me anytime soon. As nothing is technically broken, and the &...

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

...sage_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_conversion }, { "ups.mfr", 0, 0, "PowercomUPS.PowercomManufacturerName", NULL, "%s", HU_FLAG_OK, stringid_conversion },...

...les_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}, + + /* Battery */ + {"battery.type", 0, 0, "UPS.PowerSummary.iDeviceChemistry", NULL, "%s", HU_FLAG_STATIC, stringid_conver...

...atic 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_OK, NULL }, { "unmapped.ups.powersummary.iserialnumber", 0, 0, "UPS.PowerSummary.iSerialNumber", NULL, "%.0f", HU_FLA...

...fixed-size array. Could you please test this. There should be no more segmentation fault. Thanks, -- Peter Schmier, Jacob wrote: > > > The source of the segmentation fault is in newhidups.c at line 534. > > 528 > 529 void upsdrv_updateinfo(void) > 530 { > 531 hid_info_t *item; > 532 char *nutvalue; > 533 int retcode, evtCount = 0; > 534 HIDItem *eventsList[10]; > 535 > 536 upsdebugx(1, "upsdrv_updateinfo..."); > 537 > 538 > > The array only holds pointers to 10 HID items. > > > =>G...

Hello, I'm using the stable amd64 port of Debian Linux. I installed (the latest) nut-2.0.1-4 and nut-usb packages for utilizing an APC Smart-UPS 1500 USB. I tried "apcupsd" first but "nut" makes an even more sophisticated impression on me and has more security options. I had problems with the newhidups driver. It didn't find a device with matching VendorID. And

Hi, Is there any further information on this UPS interface? I have an Upsonic UPS that is reporting the same interface, but I cannot make it work or get any sensible information from it. Thanks Jon --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 000706-2, 25/01/2007 Tested on: 26/01/2007 11:00:14 AM avast! is copyright (c) 2000-2007 ALWIL Software.

Hi, Is there any further information on this UPS interface? I have an Upsonic UPS that is reporting the same interface, but I cannot make it work or get any sensible information from it. Thanks Jon --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 000706-2, 25/01/2007 Tested on: 26/01/2007 11:00:14 AM avast! is copyright (c) 2000-2007 ALWIL Software.