On Jun 2, 2017, at 8:28 AM, zefanjas <nut at zefanjas.de>
wrote:> I couldn't get the GXT4 working with usbhid-ups driver. So I need some
> advise to continue to get this device working. The GXT3 seems to be
> working ok with NUT (http://networkupstools.org/ddl/Liebert/GXT3.html).
>
> Here is my ups.conf
>
> [ups]
> driver = usbhid-ups
> port = usb-0000:00:1d.0-1.2/input0
> desc = "Emerson Liebert GXT 4"
>
The value for the port string is ignored, though it must be present - you can
change that to "auto" or "dummy" if you want. (See the
usbhid-ups man page for details if you need to distinguish between multiple
UPSes on a single system:
http://networkupstools.org/docs/man/usbhid-ups.html#_extra_arguments )
You can also add "productid=0000" here, and try running the driver and
upsd. (Either use the usbhid-ups command line below, and run "sudo
/sbin/upsd", or kill the driver and run "sudo service nut-server
restart"
> My system is running Ubuntu 16.04 with nut version 2.7.2-4ubuntu1.
>
> This is what dmesg says:
>
> [26530.061874] usb 2-1.2: new full-speed USB device number 11 using
ehci-pci
> [26530.156677] usb 2-1.2: New USB device found, idVendor=10af,
> idProduct=0000
> [26530.156684] usb 2-1.2: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [26530.156689] usb 2-1.2: Product: Liebert GXT4
> [26530.156693] usb 2-1.2: Manufacturer: Emerson Network Power
> [26530.156696] usb 2-1.2: SerialNumber: 1607000058AFC23
> [26530.174243] hid-generic 0003:10AF:0000.0008: hiddev0,hidraw2: USB HID
> v1.00 Device [Emerson Network Power Liebert GXT4]
>
> When I want to start the driver with "upsdrvctl start" it
outputs:
>
> Network UPS Tools - UPS driver controller 2.7.2
> Network UPS Tools - Generic HID driver 0.38 (2.7.2)
> USB communication driver 0.32
> This Liebert device (10af:0000) is not (or perhaps not yet) supported
> by usbhid-ups. Please make sure you have an up-to-date version of NUT. If
> this does not fix the problem, try running the driver with the
> '-x productid=0000' option. Please report your results to the NUT
user's
> mailing list <nut-upsuser at lists.alioth.debian.org>.
Added that productid:
https://github.com/networkupstools/nut/tree/Liebert_GXT4
If you had to manually change permissions, you could add the following to
/lib/udev/rules.d/62-nut-usbups.rules for the next reboot:
# Liebert GXT4 - usbhid-ups
ATTR{idVendor}=="10af", ATTR{idProduct}=="0004",
MODE="664", GROUP="nut"
>
> I've attachted the output of the following commands.
> * lsusb -v
> * /lib/nut/usbhid-ups -DDDD -x productid=0000 -a ups
>
Most of the numbers look good, but it is unclear why some values (such as
Voltage and ConfigVoltage) are not being reported correctly:
0.230714 Report[get]: (5 bytes) => 05 51 00 48 00
0.230729 Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x05,
Offset: 0, Size: 16, Value: 1
0.230738 Report[buf]: (5 bytes) => 05 51 00 48 00
0.230750 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x05,
Offset: 16, Size: 16, Value: 0
(This should not affect the OB/LB status, though I would advise testing just the
same.)
After starting the driver and upsd, what does "upsc ups" return? If
you can also include "upsrw ups" and "upscmd -l ups" output,
we can update the DDL.
[the list does not modify reply-to headers, so please use Reply-All to include
the list. Thanks!]