# 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
drive
> 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?
Th
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
> 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?
___
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
[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
Hello,
Network UPS Tools - Generic HID driver 0.38 (2.7.2)
USB communication driver 0.32
No matching HID UPS found
Driver failed to start (exit status=1)
I followed a thread with the same title, more or less, having permission
problems. I applied that solution. My problem seems different.
# l
Selon Roman Serbski <[EMAIL PROTECTED]> le Lun 25 fév 15:22:42 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(0x200
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
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 th
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
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 pat
Hi list-
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 'u
13 matches
Mail list logo
