search for: upsdrv_makevartable

hi all, really simple fix for the bestups driver: In function: upsdrv_makevartable() you need to add the line addvar(VAR_VALUE, "battvoltmult", "Battery voltage multiplier"); There are a number of simple improvements I could make to this driver, but I'm assuming that since the above bug has been around since nut v2.4, not many people are using this drive...

...+ ret -110 > +.fi > + > +In this case, simply modify the general parameter "pollinterval" to a higher > +value (like 10 for 10 seconds). This should solve the issue. > + Should we make this the default for this driver? For instance, by adding poll_interval = 10; in upsdrv_makevartable? It would still allow people to override this (driver specific) default value, but might be a safer default than the present default that is set in main.c and main-hal.c. Best regards, Arjen -- Please keep list traffic on the list

...elkin_claim, belkin_utab, belkin_hid2nut, belkin_shutdown, belkin_format_model, belkin_format_mfr, belkin_format_serial, belkin_extendvartable, }; - In newhidups.c, at the end of upsdrv_makevartable(), add a single line that does: subdriver->extendvartable(); to actually extend the table of configuration options for the specific subdriver. -- Assuming that this sounds like a good idea, I also have a query; With respect to the subdriver_s struct, would it be better t...

...better solution is to wait until the subdriver has been determined, and then load the variables. But I don't know if this is possible; it might break the driver higher up. > As init() is more general-purpose than my extendvartable(), is it still ok > to have it be called from the end of upsdrv_makevartable()? > > I was just thinking that, while it's reasonable to expect that the > subdriver's vartable additions would happen there (hence the name > "extendvartable"), it's not necessarily the most obvious place for other > kinds of initialisation to happen when...

Dear Arnaud, Now I started to write a driver that simulates continous power breaks. (E.g. in every 30 minutes.) This could be used for testing of setup of client upsmons. I have to simulate a behaviour of a real UPS. The physical model contains an extra attribute: the charging current that needed to compute recharge time and actual battery charge during the recharge process. Can we call this

Dear Arnaud, Now I started to write a driver that simulates continous power breaks. (E.g. in every 30 minutes.) This could be used for testing of setup of client upsmons. I have to simulate a behaviour of a real UPS. The physical model contains an extra attribute: the charging current that needed to compute recharge time and actual battery charge during the recharge process. Can we call this

...scharging.) --- drivers/usbhid-ups.c | 40 +++++++++++++++++++++++++++++++++++++++- 1 file changed, 39 insertions(+), 1 deletion(-) diff --git a/drivers/usbhid-ups.c b/drivers/usbhid-ups.c index 954fa54..5a4d6db 100644 --- a/drivers/usbhid-ups.c +++ b/drivers/usbhid-ups.c @@ -748,6 +748,8 @@ void upsdrv_makevartable(void) #else 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 @@ s...

...from powercom's upsmon (reset?) + ret = ser_send(upsfd, "%c%c%c%c%c\r", 1, 2, 2, 3, 5); + ret = ser_get_line(upsfd, temp, sizeof(temp), ENDCHAR, "", + SER_WAIT_SEC, SER_WAIT_USEC); + } raw = get_id(); if (!raw) @@ -426,6 +445,7 @@ void upsdrv_help(void) void upsdrv_makevartable(void) { addvar(VAR_VALUE, "lowbattvolt", "Set low battery level, in volts"); + addvar(VAR_FLAG, "powercom", "Set signal lines for PowerCOM UPS (method straced from PowerCOM's upsmon)"); } void upsdrv_banner(void) --- nut-2.0.2/drivers/fentonups.h.o...

Hi Is there any way to have a newhidups subdriver register that is can handle settings from ups.conf, as per a "normal" nut driver? In, for example, belkinunv.c, there are various addvar() calls in the upsdrv_makevartable() function, but I can't work out where addvar() calls should be put in an HID subdriver. Thanks Jo Turner -)O(-

...of the SC series of UPSes, which are low > end versions of the Smart UPS series. > > I patched the apcsmart code to assume that ^Z command was present, > yielding full functionality for changing the eeprom values. To make > this more general, I added an additional variable (in > upsdrv_makevartable()), which when set to true in ups.conf assumed > that the ^Z command was present. > > I currently have this patch in my local version, 2.0.3, (2.0.3 is > available as a port for OpenBSD). I can forward-port this to the > 2.0.5 if you think it would be useful. Currently, the added v...

I and several other users have encountered problems using PowerCOM UPS of the BNT 1500A model. Looking over other responses and dealing with my own issues, I submit the following attached patch. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20110428/00d7d2f9/attachment.htm> -------------- next

...path); - free(raw); + if (raw) + free(raw); /* paranoia - cancel any shutdown that might already be running */ ret = ser_send(upsfd, "C\r"); @@ -406,6 +425,7 @@ void upsdrv_help(void) void upsdrv_makevartable(void) { + addvar(VAR_VALUE, "model", "force model"); } void upsdrv_banner(void) $OpenBSD$ --- drivers/fentonups.h.orig Tue Apr 25 23:32:16 2006 +++ drivers/fentonups.h Wed Apr 26 00:09:19 2006 @@ -81,5 +81,6 @@ struct { {...

...    &krauler_subdriver },    /* Krauler UP-M500VA */ +    { USB_DEVICE(0x0001, 0x0000),    NULL,        "MEC0003",     &krauler_subdriver },    /* Powercool PCRACK-1200VA */      /* End of list */      { -1,    -1,    NULL,    NULL,    NULL }  }; @@ -1651,6 +1660,9 @@ void    upsdrv_makevartable(void)      nut_usb_addvars();      addvar(VAR_VALUE, "langid_fix", "Apply the language ID workaround to the krauler subdriver (0x409 or 0x4095)"); + +    addvar(VAR_VALUE, "buflen_fix", "Apply the buflen workaround to the krauler subdriver"); +  #endif ...

Hi, Sorry for the forwarding. I sent this with the wrong "from" address and got rejected by the list. ---------- Forwarded message ---------- From: Carlos Rodrigues <cefrodrigues at mail.telepac.pt> Date: Jun 18, 2007 9:34 PM Subject: Re: Megatec - modem control lines [impact to megatec_usb] To: Arjen de Korte <nut+devel at de-korte.org> Cc: ups-dev-list <nut-upsdev at

Hello, I am developing a new NUT driver for brazilian UPS brand "Ragtech" by reverse engeneering. I have never been involved in NUT driver development, so I wish to ask some basic questions. Any help will be much appreciated! 1. Is there a mandatory C code style? I mean, any strong recommendation? If there are none, I prefer to keep mine. 2. What are the purposes of "instant

...* This should make the UPS turn itself back on once the * power comes back on; which is probably what we want */ buf[0]=0x02; buf[1]=0x01; buf[2]=0x00; buf[3]=0x00; execute_and_retrieve_query(buf, reply); } void upsdrv_help(void) { } void upsdrv_makevartable(void) { } void upsdrv_banner(void) { printf("Network UPS Tools - Sweex USB UPS driver %s (%s)\n\n", DRV_VERSION, UPS_VERSION); }

...ake the UPS turn itself back on once the * power comes back on; which is probably what we want */ buf[0]=0x02; buf[1]=0x01; - Hide quoted text - buf[2]=0x00; buf[3]=0x00; execute_and_retrieve_query(buf, reply); } void upsdrv_help(void) { } void upsdrv_makevartable(void) { } void upsdrv_banner(void) { printf("Network UPS Tools - Sweex USB UPS driver %s (%s)\n\n", DRV_VERSION, UPS_VERSION); }

...ake the UPS turn itself back on once the * power comes back on; which is probably what we want */ buf[0]=0x02; buf[1]=0x01; - Hide quoted text - buf[2]=0x00; buf[3]=0x00; execute_and_retrieve_query(buf, reply); } void upsdrv_help(void) { } void upsdrv_makevartable(void) { } void upsdrv_banner(void) { printf("Network UPS Tools - Sweex USB UPS driver %s (%s)\n\n", DRV_VERSION, UPS_VERSION); }

...  &krauler_subdriver },    /* Krauler UP-M500VA */ +//    { USB_DEVICE(0x0001, 0x0000),    NULL,        "MEC0003",     &krauler_subdriver },    /* Powercool PCRACK-1200VA */      /* End of list */      { -1,    -1,    NULL,    NULL,    NULL }  }; @@ -1650,7 +1616,6 @@ void    upsdrv_makevartable(void)      /* allow -x vendor=X, vendorid=X, product=X, productid=X, serial=X */      nut_usb_addvars(); -    addvar(VAR_VALUE, "langid_fix", "Apply the language ID workaround to the krauler subdriver (0x409 or 0x4095)");  #endif    /* QX_USB */  #ifdef QX_SERIAL @@ -1822...

This is 2nd version of the earlier patch featuring a few new features and fixes to the apcsmart driver, following the remarks in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02294.html Major changes from v1: - handle battery.charge and battery.runtime checks at main.c level - handle "immutable but writable" conflict gracefully at driver level -