Re: [Nut-upsuser] No matching HID UPS found
# upsd Network UPS Tools upsd 2.7.2 fopen /var/run/nut/upsd.pid: No such file or directory listening on ::1 port 3493 listening on 127.0.0.1 port 3493 Connected to UPS [eaton]: nutdrv_qx-eaton upsc eaton@localhost Init SSL without certificate database battery.voltage: 13.50 device.type: ups driver.name: nutdrv_qx driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.7.2 driver.version.data: Q1 0.02 driver.version.internal: 0.06 input.frequency: 50.3 input.voltage: 224.4 input.voltage.fault: 224.4 output.voltage: 225.0 ups.beeper.status: enabled ups.delay.shutdown: 30 ups.delay.start: 180 ups.load: 39 ups.productid: 5161 ups.status: OL ups.temperature: 25.0 ups.type: offline / line interactive ups.vendorid: 0665 From the link you sent ... This is better than nothing (but not by much). If any of the above calculations is giving you incorrect readings, you are the one that put in the values in ups.conf(5), so don’t complain with the author. If you need something better, buy a UPS that reports battery.charge and battery.runtime all by itself without the help of a NUT driver. ... looks like I just bought junk? I guess I'll try to get the software that came with the UPS running ... 130 megabytes, including a java 1.3 jre On 2016-10-20 20:06, Charles Lepple wrote: On Oct 20, 2016, at 8:25 AM, jf...@sdf.org wrote: Using protocol: Q1 0.02 Can't autodetect number of battery packs [-1/13.50] Battery runtime will not be calculated (runtimecal not set) ... looks like it's connected to something, although maybe the driver is not quite right? That looks reasonable. Not all UPSes provide enough information to calculate runtime, but you can improve it slightly: http://networkupstools.org/docs/man/nutdrv_qx.html#_battery_charge What does "upsc easton" say? (make sure that upsd is running) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] No matching HID UPS found
> On Oct 20, 2016, at 8:25 AM, jf...@sdf.org wrote: > > Using protocol: Q1 0.02 > Can't autodetect number of battery packs [-1/13.50] > Battery runtime will not be calculated (runtimecal not set) > > ... looks like it's connected to something, although maybe the driver is not > quite right? That looks reasonable. Not all UPSes provide enough information to calculate runtime, but you can improve it slightly: http://networkupstools.org/docs/man/nutdrv_qx.html#_battery_charge What does "upsc easton" say? (make sure that upsd is running) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] No matching HID UPS found
Changed the driver as you suggest ... # upsdrvctl start Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - Generic Q* USB/Serial driver 0.06 (2.7.2) USB communication driver 0.32 Using protocol: Q1 0.02 Can't autodetect number of battery packs [-1/13.50] Battery runtime will not be calculated (runtimecal not set) ... looks like it's connected to something, although maybe the driver is not quite right? On 2016-10-20 18:39, Charles Lepple wrote: but no /dev/ttyUSB0 How can I get one? Just make one? All the rest are 4,0-67 plus one 5,0 They are created automatically by udev, so I'm guessing it won't work. What happens if you change "driver = usbhid-ups" to "driver = nutdrv_qx" in ups.conf? ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] No matching HID UPS found
Thanks for the response. No /dev/ttyUSB0. /dev/tty and /dev/tty1 ... /dev/tty63 /dev/ttyS0 ... /dev/ttyS3 but no /dev/ttyUSB0 How can I get one? Just make one? All the rest are 4,0-67 plus one 5,0 What ought the major number be? On 2016-10-20 07:33, Charles Lepple wrote: [please use reply-all to include the list - the headers are not mangled] On Oct 18, 2016, at 9:02 PM, jf...@sdf.org wrote: So, apparently, my Eaton is sending Bus 002 Device 010: ID 0665:5161 Cypress Semiconductor USB to Serial Do you get a device named "/dev/ttyUSB0" when you plug in the UPS? We do have an entry for 0665:5161 in the nutdrv_qx driver (and blazer_usb, which is deprecated in favor of nutdrv_qx) but given that it is the ID for a USB-to-serial converter, it might not be the same protocol. Give it a shot, and let us know how it goes. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] No matching HID UPS found
[please use reply-all to include the list - the headers are not mangled] > On Oct 18, 2016, at 9:02 PM, jf...@sdf.org wrote: > > So, apparently, my Eaton is sending > > Bus 002 Device 010: ID 0665:5161 Cypress Semiconductor USB to Serial Do you get a device named "/dev/ttyUSB0" when you plug in the UPS? We do have an entry for 0665:5161 in the nutdrv_qx driver (and blazer_usb, which is deprecated in favor of nutdrv_qx) but given that it is the ID for a USB-to-serial converter, it might not be the same protocol. Give it a shot, and let us know how it goes. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] No matching HID UPS found with TrippLite SMX1500LCD
On Mon, Feb 25, 2008 at 12:37 AM, Roman Serbski [EMAIL PROTECTED] wrote: I'm having problems with TrippLite SMX1500LCD not being detected by NUT under FreeBSD 6.3-RC2. NUT 2.2.1 was installed from ports with the following options: [...] #cat /etc/devfs.rules [nut_usb=10] add path 'uhid0' group wheel user uucp mode 0660 Hi, NUT support for USB HID on FreeBSD is still experimental at the moment, but you may be able to get the driver to detect the UPS by removing the uhid driver from the kernel. Since we use libusb and not the uhid API, the uhid kernel driver prevents libusb from seeing the UPS. -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] No matching HID UPS found with TrippLite SMX1500LCD
Selon Roman Serbski [EMAIL PROTECTED] le Lun 25 fév 06:37:23 2008 : Hi list- Hello, I'm having problems with TrippLite SMX1500LCD not being detected by NUT under FreeBSD 6.3-RC2. NUT 2.2.1 was installed from ports with the following options: WITH_USB=true WITH_SNMP=true WITHOUT_IPV6=true WITH_LIBUPSCLIENT=true WITH_CGI=true I use USB cable shipped with TrippLite and 'usbdevs -v' shows the following: ... Controller /dev/usb2: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 port 1 powered port 2 addr 2: low speed, power 100 mA, config 1, TRIPP LITE UPS(0x2005), Tripp Lite(0x09ae), rev 0.10 ... According to http://www.networkupstools.org/compat/stable.html it looks like SMX1500LCD is supported (by usbhid-ups). However, whenever I try to start nut I see the following error: No matching HID UPS found Driver failed to start (exit status=1) It seems that this product is not known. Could you please try to add an entry for it in src/sys/dev/usb/usbdevs ? Best regards, -- Th. Thomas. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] No matching HID UPS found with TrippLite SMX1500LCD
On Mon, Feb 25, 2008 at 5:49 PM, Charles Lepple [EMAIL PROTECTED] wrote: On Mon, Feb 25, 2008 at 12:37 AM, Roman Serbski [EMAIL PROTECTED] wrote: I'm having problems with TrippLite SMX1500LCD not being detected by NUT under FreeBSD 6.3-RC2. NUT 2.2.1 was installed from ports with the following options: [...] #cat /etc/devfs.rules [nut_usb=10] add path 'uhid0' group wheel user uucp mode 0660 NUT support for USB HID on FreeBSD is still experimental at the moment, but you may be able to get the driver to detect the UPS by removing the uhid driver from the kernel. Since we use libusb and not the uhid API, the uhid kernel driver prevents libusb from seeing the UPS. Thank you Charles. Right, uhid was included - I will recompile kernel and let you know. Regards, Roman ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] No matching HID UPS found with TrippLite SMX1500LCD
On Mon, Feb 25, 2008 at 1:31 PM, Thierry Thomas [EMAIL PROTECTED] wrote: Selon Roman Serbski [EMAIL PROTECTED] le Lun 25 fév 06:37:23 2008 : ... Controller /dev/usb2: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 port 1 powered port 2 addr 2: low speed, power 100 mA, config 1, TRIPP LITE UPS(0x2005), Tripp Lite(0x09ae), rev 0.10 ... According to http://www.networkupstools.org/compat/stable.html it looks like SMX1500LCD is supported (by usbhid-ups). However, whenever I try to start nut I see the following error: No matching HID UPS found Driver failed to start (exit status=1) It seems that this product is not known. Could you please try to add an entry for it in src/sys/dev/usb/usbdevs ? Thanks Thierry. Am I right that 0x2005 belongs to 'product' and 0x09ae to 'vendor'? Regards, Roman ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
