similar to: USB match but cannot open??

Thinking of it, we can't conjure a libusb descriptor from thin air because the library can have internal state associated with it (allocated buffers, open-close count, etc.) On Tue, Nov 26, 2024, 21:06 Jim Klimov <jimklimov+nut at gmail.com> wrote: > Regarding the follow-up, IIRC `open` walks a device list returned by > libusb, checks each entry against the matcher, and tells

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

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

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

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,

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, 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

I get the following error on r809 (but it looks like the code change happened here). Does HIDDevice_t need to be defined/changed in one of the headers? if gcc -DHAVE_CONFIG_H -I. -I../../drivers -I../include -I../../include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -DINET6 -O2 -D_REENTRANT -DNETSNMP_USE_INLINE -Wall -Dlinux -I.

Compiling against http://www.networkupstools.org/source/2.7/nut-2.7.4.tar.gz. I also have libusb-0.1-4 installed but no joy. On Mon, Mar 23, 2020 at 2:45 AM Jim Klimov <jimklimov at cos.ru> wrote: > On March 23, 2020 12:50:11 AM UTC, Tyler Montney <montneytyler at gmail.com> > wrote: > >Came across this in the process of troubleshooting: > > >

Came across this in the process of troubleshooting: https://alioth-lists.debian.net/pipermail/nut-upsuser/2011-November/007249.html My whole reason for compiling from source is to add SSL support (as it doesn't seem available through the package manager). Apt list shows these installed: libusb-1.0-0-dev/stable,now 2:1.0.22-2 armhf [installed] libusb-1.0-0/stable,now 2:1.0.22-2 armhf

Great! Regarding libusb and nut-scanner, I think the *.so (exact) symlinks are part of *-devel packages. This was solved in NUT recently (maybe after 2.8.2 release already) by detecting and stashing the basename of realpath of the library present during build, so the exact *.so.X.Y.Z would be also tried. Also, nut-scanner now (in 2.8.2 IIRC) should not suggest the volatile bus/busport/device

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

An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20120214/96cc8043/attachment.html>

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>

All, I have: sales <- c(2300,900,155,102,42,10) names(sales) <- c("Christmas","Valentine's Day", "Mother's Day","Father's Day", "Thanksgiving","New Year's Day") barplot(sales,ylim=c(0,2500)) But it doesn't place all of the name labels on the plot. So I tried: sales <-

Just a note: recent PRs are naturally not in 2.8.0 release (April 2022), but would be in eventual 2.8.1 Jim On Sun, Jan 15, 2023, 00:51 Bruce Pleat <bpleat at gmail.com> wrote: > Part of what made my life harder is nut-scanner isn't in the package. > > Once I get a chance, I'll update to 2.8, but that'll be a little while off. > (Any clue how to get 2.8 included in

Part of what made my life harder is nut-scanner isn't in the package. Once I get a chance, I'll update to 2.8, but that'll be a little while off. (Any clue how to get 2.8 included in the package provider for my Raspberry Pi is presumably beyond the scope of this list, but if someone knows and wants to let me know, I wouldn't complain...) On Sat, Jan 14, 2023 at 3:12 PM Jim

Thanks! FWIW if you do get to test new code, https://github.com/networkupstools/nut/pull/1811 adds warnings for situations like yours. Would be great to check if it works actually, with many "same-serial" devices :) Jim On Sat, Jan 14, 2023, 23:39 Bruce Pleat <bpleat at gmail.com> wrote: > Thank you, looks like the regex idiosyncracy might have been the issue. > > My

Thank you, looks like the regex idiosyncracy might have been the issue. My current file: [sl] driver = usbhid-ups port = auto desc = "CyberPower UPS SL" product = "SL.*" productid = 0501 vendorid = 0764 #model = "SL Series" [ab] driver = usbhid-ups port = auto desc =