Displaying 7 results from an estimated 7 matches for "075d".
Did you mean:
0755
2011 Jan 03
1
Can't get iDowell to work
...odowell UPS:
http://idowell.eu/
I cannot get it recognised by the drivers. This is what I get when I plug in
the USB connector:
Jan 3 19:27:26 compaq kernel: usb 3-2: new low speed USB device using
uhci_hcd and address 47
Jan 3 19:27:26 compaq kernel: usb 3-2: New USB device found, idVendor=075d,
idProduct=0300
Jan 3 19:27:26 compaq kernel: usb 3-2: New USB device strings: Mfr=3,
Product=1, SerialNumber=2
Jan 3 19:27:26 compaq kernel: usb 3-2: Product: iBox
Jan 3 19:27:26 compaq kernel: usb 3-2: Manufacturer: iDowell
Jan 3 19:27:26 compaq kernel: usb 3-2: SerialNumber: 00000001
Jan...
2014 Apr 05
2
I can't make changes to ups.delay.shutdown to stick
...15
battery.runtime: 650
battery.type: Pb acc
device.mfr: iDowell
device.model: iBox
device.serial: 00000001
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 0300
driver.parameter.vendorid: 075d
driver.version: 2.6.5
driver.version.data: iDowell HID 0.1
driver.version.internal: 0.37
input.transfer.high: 254
input.transfer.low: 105
output.frequency.nominal: 50
output.voltage: 230.0
output.voltage.nominal: 230
ups.delay.shutdown: 20
ups.delay.start: 30
ups.load: 33
ups.mfr: iDowell
ups.model...
2014 Apr 05
0
I can't make changes to ups.delay.shutdown to stick
On Apr 5, 2014, at 7:18 AM, Mick wrote:
> $ upsrw -s "ups.delay.shutdown"="30" iDowell at localhost
> Username (suzy): admin
> Password:
> OK
This command is sending the value to the UPS (via the usbhid-ups driver).
> $ upsc iDowell at localhost ups.delay.shutdown
> 30
And this command ends up reading the value back from the UPS.
> However, following
2014 Apr 05
2
I can't make changes to ups.delay.shutdown to stick
...T
> variable names to HID identifiers are incorrect.
I can't really test the UPS in anger because it is feeding other devices (ADSL
modem and a couple of routers) which I do not want to lose power to.
This is what the USB device reports:
===================================
# lsusb -vv -d 075d:0300
Bus 003 Device 009: ID 075d:0300
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor...
2015 May 29
4
UPower: 95-upower-hid.rules update
...UPOWER_VENDOR}="APC"
-ATTRS{idVendor}=="06da", ENV{UPOWER_VENDOR}="Liebert"
+ATTRS{idVendor}=="0592", ENV{UPOWER_VENDOR}="Powerware"
+ATTRS{idVendor}=="06da", ENV{UPOWER_VENDOR}="Phoenixtec Power Co., Ltd"
+ATTRS{idVendor}=="075d", ENV{UPOWER_VENDOR}="iDowell"
ATTRS{idVendor}=="0764", ENV{UPOWER_VENDOR}="Cyber Power Systems"
ATTRS{idVendor}=="09ae", ENV{UPOWER_VENDOR}="TrippLite"
ATTRS{idVendor}=="0d9f", ENV{UPOWER_VENDOR}="PowerCOM"
ATTRS{idVend...
2014 Apr 05
3
I can't make changes to ups.delay.shutdown to stick
On Apr 5, 2014, at 10:39 AM, Charles Lepple wrote:
> On Apr 5, 2014, at 8:52 AM, Mick <michaelkintzios at gmail.com> wrote:
>
>>> The upsrw command was designed for changing variables that are typically
>>> stored in non-volatile memory on the UPS. Unfortunately, your UPS doesn't
>>> seem to do that.
>>
>> Well, if it doesn't do that,
2012 Mar 08
18
some fixes, improvements, and new features (EPO and DYING) for NUT
Here are a series of my recent changes to NUT.
The first few in the set are primarily little fixes and improvements.
In among those are a few for .gitignore files which of course you can
ignore for SVN, and there's one for a commit to a generated file which
of course should not be tracked in any VCS.
Then there are a couple or three to do with generating the header files
used by