Nut upsdev - Feb 2014 - Question on support for Upsonic Commercial UPS CXR 2000 - 2000VA/1200W - Rack/Tower on Freebsd 9.1.

On 2/5/14, 9:55 PM, Charles Lepple wrote:
> On Feb 5, 2014, at 9:03 PM, Chris Duffy wrote:
>
>>> Please run this:
>>>
>>>     /usr/local/libexec/nut/blazer_usb -a UPSonic -u root -D
>>>
>>> and send the output back to the list.
>>>
>> Output from the above command:
>>
>>    0.000000    debug level is '1'
>>    0.248714    Supported UPS detected with megatec protocol
>>    1.268575    Permissions problem: Input/output error
>> Network UPS Tools - Megatec/Q1 protocol USB driver 0.09
(2.6.5-Unversioned directory)
> Hmm, "Input/output error" is somewhat different than a
permissions problem, so this points to some FreeBSD-specific weirdness.
Unfortunately, it looks like this has been seen before, with no apparent
resolution at the time:
>
>    
http://lists.alioth.debian.org/pipermail/nut-upsuser/2012-December/008164.html
>
> Can you try it with -DDDD to see if the error is on the send side?
Here is the new output plus dmesg:

/usr/local/libexec/nut/blazer_usb -a UPSonic -u root -DDDD

    0.000000    debug level is '4'
    0.009364    Checking device (06DA/0005) (/dev/usb//dev/ugen1.3)
    0.016405    - VendorID: 06da
    0.016419    - ProductID: 0005
    0.016438    - Manufacturer: PPC
    0.016442    - Product: USB UPS
    0.016446    - Serial Number: unknown
    0.016449    - Bus: /dev/usb
    0.016452    Trying to match device
    0.016457    Device matches
    0.016485    Trying megatec protocol...
    0.017411    send: Q1
    0.252545    read: (244.4 244.4 229.9 028 50.0 2.19 23.1 00000001
    0.252589    Status read in 1 tries
    0.252602    Supported UPS detected with megatec protocol
    1.288032    send: Unknown error
    1.288085    Permissions problem: Input/output error
Network UPS Tools - Megatec/Q1 protocol USB driver 0.09 
(2.6.5-Unversioned directory)


dmesg output:


ugen1.3: <PPC> at usbus1 (disconnected)
uhid0: at uhub3, port 1, addr 3 (disconnected)
ugen1.3: <PPC> at usbus1
uhid0: <PPC USB UPS, class 0/0, rev 2.00/0.03, addr 3> on usbus1

>
> Also, any output from dmesg related to ugen?
>

-- 
Chris Duffy
Product Support
Small Tree Communications
www.small-tree.com
Direct 651-209-6509 X305
Mobil 651-303-9613
Skype:cjdwoodbury
Yahoo:chris_duffy6288
AIM/Google:cjdwoodbury at gmail.com

On Feb 6, 2014, at 8:41 AM, Chris Duffy wrote:
>   0.016485    Trying megatec protocol...
>   0.017411    send: Q1
>   0.252545    read: (244.4 244.4 229.9 028 50.0 2.19 23.1 00000001
>   0.252589    Status read in 1 tries
>   0.252602    Supported UPS detected with megatec protocol
>   1.288032    send: Unknown error
>   1.288085    Permissions problem: Input/output error
> 
Interesting that it gets past the first send/read pair.
> dmesg output:
> 
> 
> ugen1.3: <PPC> at usbus1 (disconnected)
> uhid0: at uhub3, port 1, addr 3 (disconnected)
> ugen1.3: <PPC> at usbus1
> uhid0: <PPC USB UPS, class 0/0, rev 2.00/0.03, addr 3> on usbus1

Well, that's frustrating.

The chain of command is something like this:

NUT USB-based drivers -> libusb -> ugen kernel driver -> device

The uhid driver tries to offer access to HID devices, but most USB devices that
were designed to work on Windows abuse the HID protocol to avoid requiring a
kernel driver.

There is a "quirks list" that effectively kicks uhid out of the way,
and that has been necessary for other UPSes on FreeBSD, such as the following:

http://www.freebsd.org/cgi/query-pr.cgi?pr=134766

I'm not sure of the exact steps to take next, but I can look into it.

-- 
Charles Lepple
clepple at gmail

Thx Charles,

So since this is a new type of UPSonic UPS, do you think
the vendor screwed up or is it just some quirk on Freebsd?

Yes, if you can look into this I would appreciate it.
I do not see anyone else on the Web attempting to use
this new device yet.....but.......

Regards
chris

On 2/6/14, 8:24 AM, Charles Lepple wrote:
> On Feb 6, 2014, at 8:41 AM, Chris Duffy wrote:
>
>>    0.016485    Trying megatec protocol...
>>    0.017411    send: Q1
>>    0.252545    read: (244.4 244.4 229.9 028 50.0 2.19 23.1 00000001
>>    0.252589    Status read in 1 tries
>>    0.252602    Supported UPS detected with megatec protocol
>>    1.288032    send: Unknown error
>>    1.288085    Permissions problem: Input/output error
>>
> Interesting that it gets past the first send/read pair.
>
>> dmesg output:
>>
>>
>> ugen1.3: <PPC> at usbus1 (disconnected)
>> uhid0: at uhub3, port 1, addr 3 (disconnected)
>> ugen1.3: <PPC> at usbus1
>> uhid0: <PPC USB UPS, class 0/0, rev 2.00/0.03, addr 3> on usbus1
>
> Well, that's frustrating.
>
> The chain of command is something like this:
>
> NUT USB-based drivers -> libusb -> ugen kernel driver -> device
>
> The uhid driver tries to offer access to HID devices, but most USB devices
that were designed to work on Windows abuse the HID protocol to avoid requiring
a kernel driver.
>
> There is a "quirks list" that effectively kicks uhid out of the
way, and that has been necessary for other UPSes on FreeBSD, such as the
following:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=134766
>
> I'm not sure of the exact steps to take next, but I can look into it.
>

-- 
Chris Duffy
Product Support
Small Tree Communications
www.small-tree.com
Direct 651-209-6509 X305
Mobil 651-303-9613
Skype:cjdwoodbury
Yahoo:chris_duffy6288
AIM/Google:cjdwoodbury at gmail.com