similar to: Combination serial and usb driver?

Do your drivers/Makefile.am rules for the resulting new program specify dependencies to use similar to other USB-capable drivers? e.g. ```` blazer_usb_SOURCES = blazer.c blazer_usb.c $(LIBUSB_IMPL) usb-common.c blazer_usb_LDADD = $(LDADD_DRIVERS) $(LIBUSB_LIBS) -lm ```` Jim On Sat, Nov 2, 2024 at 2:30?AM William R. Elliot <bill at wreassoc.com> wrote: > Hello again all. > > I am

Hello again all. I am trying to use USB functions (non-HID) and I get a linker error for functions that are in the included usb-common.h file. Specifically, at the start, these functions: - warn_if_bad_usb_port_filename - nutusb_open - is_usb_device_supported Clearly the headers are there or I don't think the driver would compile. Can someone point me in the right direction please? Thank

Hello all, In my new driver I have a function that searches for the position of a known substring in a delimited string. I am trying to populate a series of integer variables with the position value of various substrings. The first call to the function performs correctly but the remaining calls in the code series are not being executed (there are six more calls after the first successful

Hello, always nice to hear about new drivers :) OTOH, check for any variables you might have been re-using, so their earlier state impacts later runs - whether buffers allocated statically (or by caller without rewinding the pointer and maybe nulling the contents), or position counters, etc. Similarly, be sure to pre-initialize anything of value and not start out with random bits from the stack.

An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20241022/a5e3106d/attachment.htm>

Sounds great! By `connection error` it looks like the `upsc` client had nowhere to go. Is `upsd` started (and does it `LISTEN` on locahost or asterisk per `upsd.conf`)? Jim On Sat, Oct 26, 2024, 08:13 William R. Elliot <bill at wreassoc.com> wrote: > Hello again. > > I now have large chunks of the new driver working in the foreground and > wanted to see what upsc reports

Hello all. Implementation is serial protocol over USB (hey, it is what it is). I am able to find the device (regex) and open it, send it a command and get a response. The problem is that I see all of the transactions in my USB sniffing tool (8-byte chunks) but the buffer that is used for the response in 'get_interrupt' is missing one or more of the beginning chunks (using printf

Hi Billy, switching back this thread to -upsdev 2012/2/27 William R. Elliot <bill at wreassoc.com>: > I have been able to set the 'FSD' from the driver and it is picked up by > upsmon.? That gives me the functionality that I was asked to put in the > driver.? If that is against the rules then I'll make an adjustment when the > allowed method is defined.? :-) yup,

Hello again. Back in the day (2007) I wrote a USB-capable driver for my Masterguard/Phoenixtec UPSes (in case you locally archived this list, this very mail is a reply to a rather long thread from then), which I used ever since. However, the world has been going on since then and I need to get away with the old 2.0.4 binaries currently in use. These boxes (I use two A3000-19 and two A700-19) are

Hi, I had an issue where after returning the power from a shutdown.return the ups would do another shutdown.return during the boot, and kept this forever. After some investigation I found the problem is a bug on the ups - TSSHARA model, driver nutdrv_qx: every time I shutdown with return, and reconnect the usb after the power is back it would start another shudown.return cycle. When I used my

Hi Guys! I would like use my ups with ub 77 usb to serial cable, because I don't have enough serial port. After the revision 2431 liebert(gtx2 /esp-2) drivers have bugs and I use rev2431 driver (liebertgtx2). It doesn't work with this cable. The Liebert App(Multilink) works with this cable. Do you have any idea ? Thanks your help. -- Best Regards, Robert -------------- next part

hi, we working together with robert to make liebert ups with nut. there was a good revision 2431 which gives a good result for us. this revision call the driver gxt2. after that you change the name to esp2. unfortunately this version (and the current head too) contains the same bug what was previously fixed in the gxt2 branch. it'd be useful to port the fixes to the new esp2 branch too. the

The developer guide currently says that there is "no official list of alarm words". Is that still true? If not, can someone point me to the official list? Thanks, Bill -- This email has been checked for viruses by AVG antivirus software. www.avg.com

I just upgraded my Win7 32bits installation to 2.14.0 after deinstalling 2.12.x First thing I moved the win-library from 2.12 to 2.14 and executed a update.packages(ask='graphics',checkBuilt=TRUE) (Swiss mirror). This aborts with the console message: Error in if (any(diff)) { : missing value where TRUE/FALSE needed And the antivirus (AVG) pops up complaining that colorspace.dll

2012/2/28 Arnaud Quette <aquette.dev at gmail.com>: > Hi Charles > > 2012/2/28 Charles Lepple <clepple at gmail.com>: >> On Feb 28, 2012, at 3:44 AM, Arnaud Quette wrote: >> >>> Hi Billy, >>> >>> switching back this thread to -upsdev >>> >>> 2012/2/27 William R. Elliot <bill at wreassoc.com>: >>>> I

An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20241024/4b16b621/attachment.htm>

An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20241026/ce542852/attachment.htm>

On Jun 26, 2017, at 7:03 AM, Andrea de Lutti <adelutti at gmail.com> wrote: > > Are there no warnings for battery test? not sure if you saw my reply on 2016-06-17: Do you mean a notification that a test is in progress, or something for the results? There is the REPLBATT message in upsmon when the battery test fails, but I don't think the generic Qx protocol supports the RB

From private E-mail: > > My question to you is how I should go about getting > > the changes back into the system. My work has been exclusively on the ONEAC > > driver and man page. The driver .c file is almost completely redone. > >how can you warrant compat? >Ie, if it's a full rewrite, what have you done to ensure that >currently supported devices will still

Did you follow step-by-step the guidelines explained in the HowTo to join ADS? We too have a W2K3 server updated to last sp and post-sp updates by Windows' automatic update and we encountered no problems following the HowTo. By example, the line "security" of smb.conf file must be set "ADS", not "domain" as in yours... In addition, the HowTo says