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
> 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?
I have run nut driver in debug level 6.
Here is the log: http://www.filedropper.com/ups_1
Please have a look, i cannot see a pattern since i dont know what to look for.
DMESG:
[269391.234426] hid-generic 0003:06DA:.0003: hiddev0,hidraw0: USB HID v1.00
Device [PPC Offline UPS] on
I'm having trouble with a TrippLite SU3000XLCD. I'm using a Raspberry Pi
running Raspbian (wheezy) with NUT 2.6.4.
I can monitor my older TrippLite UPSs, mostly SU1000RT2Us, with this Pi and a
USB to serial adapter.
My first thought with the SU3000XLCD was to use the USB port instead of the
# 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
[please use reply-all to include the list - the headers are not mangled]
On Oct 20, 2016, at 3:22 PM, Fairfax, Charles A. wrote:
>
> I’m having trouble with a TrippLite SU3000XLCD. I’m using a Raspberry Pi
> running Raspbian (wheezy) with NUT 2.6.4.
>
> I can monitor my older TrippLite
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
7 matches
Mail list logo