search for: upsdrv_initinfo

Hello All, This is my first post to the list & I have tried to do as much searching and debugging on my own as I can bear. Please HELP! I am currently using up to date Centos 5.2 32-bit - kernel version: 2.6.18-92.1.10.el5PAE #1 SMP. I am using a Tripplite OMNIVS1500 via usb connection. I am using the tripplite_usb driver. I have tried to user versions 2.2.0 from an rpm, 2.2.2 & and the

Hello All, This is my first post to the list & I have tried to do as much searching and debugging on my own as I can bear. Please HELP! I am currently using up to date Centos 5.2 32-bit - kernel version: 2.6.18-92.1.10.el5PAE #1 SMP. I am using a Tripplite OMNIVS1500 via usb connection. I am using the tripplite_usb driver. I have tried to user versions 2.2.0 from an rpm, 2.2.2 & and the

...char mch, *mstr; /* first see if it's in the mtab2 */ - if (check_mtab2(raw)) + if (check_mtab2(raw, 1)) return; mch = raw[17]; @@ -175,28 +178,36 @@ static char *get_id(void) void upsdrv_initinfo(void) { int modelnum, i, ret; - char temp[256], model[32], *raw; + char temp[256], qmodel[32], *model, *raw = NULL; - raw = get_id(); + model = getval("model"); -...

On 09/11/14 22:34, Charles Lepple wrote: > On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote: > >> I see a libusb_get_interrupt message in the log. Could that be the problem? > Yes, it seems related. > > 1.126896 upsdrv_initinfo... > 1.126906 upsdrv_updateinfo... > 1.127023 libusb_get_interrupt: Function not implemented > 1.127030 Got 0 HID objects... > 1.127036 Quick update... > > Come to think of it, this might also depend on how OpenBSD provides libusb-0.1. What version of libusb-compat...

...t;ups.load", 1.0 }, + { "OV", "output.voltage", 2.0 }, + { "OF", "output.frequency", 0.1 }, + { "NF", "input.frequency", 0.1 }, + { "BT", "ups.temperature" }, +}; /* model "IO" is parsed differently in upsdrv_initinfo() */ static ezfill _initv[] = { @@ -105,6 +117,10 @@ r=-2; upsdebugx(1, "READ: <unsupported command>"); } + if ( _buf[0] == 0x06 ) + { + upsdebugx(2, "READ: <command done>"); + } else { upsdebugx(2, "READ: \"%s\"", _buf...

It look to me that overwriting UPSTYPE CP signal or polarity in ups.conf have no effect. Looking at drivers/main.c source show that &upstab[upstype].line_norm is set to custom CP in initinfo() only _AFTER_ the serial signals are actually set by upsdrv_initups().

It look to me that overwriting UPSTYPE CP signal or polarity in ups.conf have no effect. Looking at drivers/main.c source show that &upstab[upstype].line_norm is set to custom CP in initinfo() only _AFTER_ the serial signals are actually set by upsdrv_initups().

...: > On 09/11/14 22:34, Charles Lepple wrote: >> On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote: >> >>> I see a libusb_get_interrupt message in the log. Could that be the problem? >> Yes, it seems related. >> >> 1.126896 upsdrv_initinfo... >> 1.126906 upsdrv_updateinfo... >> 1.127023 libusb_get_interrupt: Function not implemented >> 1.127030 Got 0 HID objects... >> 1.127036 Quick update... >> >> Come to think of it, this might also depend on how OpenBSD provides libusb-0.1. What ver...

...status. 0=off 1=on */ inverter = bcd2i(&fstring[16], 2); Index: b/drivers/etapro.c =================================================================== --- a/drivers/etapro.c 2011-05-31 13:36:49.000000000 +0300 +++ b/drivers/etapro.c 2011-08-17 00:23:22.000000000 +0300 @@ -213,7 +213,6 @@ upsdrv_initinfo(void) void upsdrv_updateinfo(void) { - char status[256]; int x, flags; double utility, outvolt, battvolt, loadpct; @@ -292,7 +291,6 @@ upsdrv_updateinfo(void) status_init(); - status[0] = '\0'; if (!(flags & 0x02)) status_set("OFF"); else if (flags &...

Citeren Michal Soltys <msoltyspl-guest at alioth.debian.org>: > @@ -417,10 +414,12 @@ > if (flags & SER_CC) { > iset = IGN_CCCHARS; > aset = ""; > + sec = 6; usec = 0; > } > if (flags & SER_CS) { > iset = IGN_CSCHARS; > aset = ""; > + sec = 6; usec = 0; > } > > memset(buf, '\0', buflen);

On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote: > I see a libusb_get_interrupt message in the log. Could that be the problem? Yes, it seems related. 1.126896 upsdrv_initinfo... 1.126906 upsdrv_updateinfo... 1.127023 libusb_get_interrupt: Function not implemented 1.127030 Got 0 HID objects... 1.127036 Quick update... Come to think of it, this might also depend on how OpenBSD provides libusb-0.1. What version of libusb-compat do you have? However, checking...

...S driver : entering load_mib2nut(cpqpower) 0.034384 load_mib2nut: trying classic method with 'cpqpower' mib 0.038862 load_mib2nut: using cpqpower mib 0.042973 Detected HP RT3000 G2 UPS on host mcups2.cal.org (mib: cpqpower 1.5) 0.043021 SNMP UPS driver : entering upsdrv_initinfo() 0.047657 upsdrv_initinfo(): adding command 'load.off' 0.051990 upsdrv_initinfo(): adding command 'load.on' 0.056720 upsdrv_initinfo(): adding command 'shutdown.stop' 0.061107 upsdrv_initinfo(): adding command 'load.off.delay' 0.065899...

...ev/ttyACM?. My driver completely supports hotplugging, so I can plug or unplug the usb cable before or after the driver has started. In any case, the driver connects, disconnects or reconnects to the UPS. The way I did this is by doing connection to the serial port and detection of UPS model all in upsdrv_initinfo(), with upsdrv_initups() doing almost nothing. Is this alright? 4. I wish to be able to pass to the driver some custom options besides the "port = " that appears in ups.conf (for example, only manage a device that reports a specific serial number). What is the standard way to do this?...

...39;1' 0.000260 SNMP UPS driver : entering upsdrv_initups() 0.027868 load_mib2nut: trying netvision mib 0.029798 load_mib2nut: using netvision mib 0.031731 Detected NETYS 3 kVA on host 192.168.0.227 (mib: netvision 0.1) 0.031751 SNMP UPS driver : entering upsdrv_initinfo() 0.031785 getting data: ups.mfr (.1.3.6.1.4.1.4555.1.1.1.1.1.3.0) 0.033823 entering su_setinfo(ups.mfr) 0.033836 getting data: ups.model (.1.3.6.1.4.1.4555.1.1.1.1.1.1.0) 0.035731 entering su_setinfo(ups.model) 0.035744 getting data: ups.serial (.1.3.6.1.4.1...

...} iIndex++; } + return TRUE; } - else + else { upsdebugx(1, "Invalid response received from Command List block"); + return FALSE; + } } } @@ -1141,6 +1155,7 @@ void upsdrv_initinfo(void) int iRating = 0, iIndex = 0, res, len; int ncpu = 0, buf; int conf_block_len = 0, alarm_block_len = 0, cmd_list_len = 0; + bool_t got_cmd_list = FALSE; /* Init BCM/XCP alarm descriptions */ init_alarm_map(); @@ -1299,11 +1314,13 @@ void upsdrv_initinfo(void)...

On 09/11/14 21:43, Charles Lepple wrote: > On Sep 11, 2014, at 9:48 PM, Stan Gammons <sg063015 at gmail.com> wrote: > >> I have an APC USB UPS that was working on OpenBSD 5.5 with NUT 2.7.1 When I installed the latest 5.6 snapshot with NUT 2.7.2 the UPS no longer sends status messages when it loses line power. I asked over on the OpenBSD ports list and so far haven't had

...portlen = 81) 0.355182 Found HID device 0.355210 Detected a UPS: Phoenixtec Power/USB Cable (V2.00) 0.355234 find_nut_info: unknown info type: load.off.delay 0.355256 find_nut_info: unknown info type: load.on.delay 0.355278 find_nut_info: unknown info type: load.off.delay 0.355305 upsdrv_initinfo... 0.355333 upsdrv_updateinfo... 0.607995 libusb_get_interrupt: Connection timed out 0.608075 Got 0 HID objects... 0.608109 Quick update... 0.608182 dstate_init: sock /var/run/nut/usbhid-ups-CENER_LA900_usb open on fd 5 0.608229 upsdrv_updateinfo... 0.859959 libusb_get_interrup...

...: ffa00001.ffa00002.ffa1000c, Type: Output, ReportID: 0x00, Offset: 0, Size: 8, Value: 0.000000 > Network UPS Tools: 0.29 USB communication driver - core 0.32 (2.3.0-1150) > > Report descriptor retrieved (Reportlen = 78) > =46ound HID device > Detected a UPS: ?/UPS USB MON V1.4 > upsdrv_initinfo... > upsdrv_updateinfo... > Quick update... > dstate_init: sock /var/state/ups/usbhid-ups-sweex_PP100 open on fd 5 > upsdrv_updateinfo... > Quick update... > upsdrv_updateinfo... > Quick update... > Signal 2: exiting > upsdrv_cleanup... > > [This keeps repeating to...

...portlen = 81) 0.365283 Found HID device 0.365310 Detected a UPS: Phoenixtec Power/USB Cable (V2.00) 0.365332 find_nut_info: unknown info type: load.off.delay 0.365355 find_nut_info: unknown info type: load.on.delay 0.365377 find_nut_info: unknown info type: load.off.delay 0.365407 upsdrv_initinfo... 0.365433 upsdrv_updateinfo... 0.617132 libusb_get_interrupt: Connection timed out 0.617233 Got 0 HID objects... 0.617278 Quick update... 0.617346 dstate_init: sock /var/run/nut/usbhid-ups-CENER_LA900_usb open on fd 5 0.617464 upsdrv_updateinfo... 0.869136 libusb_get_interrup...

On Dec 11, 2014, at 5:43 AM, janc at telefonica.net wrote: > 0.339329 Entering libusb_get_report > 0.342986 Report[get]: (2 bytes) => 01 00 > 0.343085 Path: 008c0001.008c0003, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 0 > 0.343120 Entering libusb_get_report > 0.346953 Report[get]: (2 bytes) => 02 00 > 0.346993 Path: 008c0001.008c0002,