Displaying 5 results from an estimated 5 matches for "process_boolean_info".
2012 Mar 21
5
Socomec sicon Netys 2000 PR ups USb driver for ubuntu
Hello i tried to connect my netys 2000 pr ups to ubuntu 11.10 and i have a problem connecting it. After readin a few post i realized to dianosse the connection.
I need help resolving the connextion issue
So here is the response to??/lib/nut/usbhid-ups -u root -DDDDD -a netys:
Network UPS Tools - Generic HID driver 0.35 (2.6.1)
USB communication driver 0.31
? ?0.000000 ? ? send_to_all: SETINFO
2018 Feb 04
0
[PATCH 2/3] Add generic facility to override HID report descriptor in usbhid-ups
...se
addvar(VAR_VALUE, "notification", "Set notification type, (ignored, only for backward compatibility)");
#endif
+
+ addvar(VAR_VALUE, "hid_descriptor", "Replacement HID descriptor file");
}
#define MAX_EVENT_NUM 32
@@ -1093,16 +1095,52 @@ static void process_boolean_info(const char *nutvalue)
static int callback(hid_dev_handle_t udev, HIDDevice_t *hd, unsigned char *rdbuf, int rdlen)
{
int i;
- const char *mfr = NULL, *model = NULL, *serial = NULL;
+ const char *mfr = NULL, *model = NULL, *serial = NULL, *descfile;
#ifndef SHUT_MODE
int ret;
#endif
upsdeb...
2014 May 29
0
Resetting replace battery status on Pulsar 1500
...d_infoval: found Done and passed (value: 1)
That part seems to contradict the following:
32.407365 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Feature, ReportID: 0x02, Offset: 8, Size: 8, Value: 0
32.407367 hu_find_infoval: found !replacebatt (value: 0)
32.407369 process_boolean_info: !replacebatt
There is also this LCM (Life Cycle Monitoring) part:
22.677035 hid_lookup_path: 00840004 -> UPS
22.677037 hid_lookup_path: ffff0018 -> LCMSystem
22.677039 hid_lookup_path: ffff001a -> LCMAlarm
22.677045 hid_lookup_path: 00ff0001 -> not found in lo...
2014 May 29
2
Resetting replace battery status on Pulsar 1500
On 28 May 2014, at 21:59, Charles Lepple <clepple at gmail.com> wrote:
>> What would log it?
>
> The driver.
OK.
>> I could try running the driver with debugging and see if that shows anything of interest.
>
> That should help. Unfortunately for non-debug operation, it appears that most of the usbhid-ups instcmd messages are buried at debug level 3 or 5. That
2018 Feb 04
5
[PATCH 0/3] OpenUPS updates
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