search for: overcurrent

...None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 255 Hub Descriptor: bLength 9 bDescriptorType 41 nNbrPorts 2 wHubCharacteristic 0x000a No power switching (usb 1.0) Per-port overcurrent protection bPwrOn2PwrGood 1 * 2 milli seconds bHubContrCurrent 0 milli Ampere DeviceRemovable 0x00 PortPwrCtrlMask 0xff Hub Port Status: Port 1: 0000.0100 power Port 2: 0000.0100 power Device Status: 0x0003 Self Powered Remote Wakeup Enabled Bus 002 Device...

...? ? ? None ? ? ? ? ? Usage Type ? ? ? ? ? ? ? Data ? ? ? ? wMaxPacketSize ? ? 0x0004 ?1x 4 bytes ? ? ? ? bInterval ? ? ? ? ? ? ?12 Hub Descriptor: ? bLength ? ? ? ? ? ? ? 9 ? bDescriptorType ? ? ?41 ? nNbrPorts ? ? ? ? ? ? 5 ? wHubCharacteristic 0x000a ? ? No power switching (usb 1.0) ? ? Per-port overcurrent protection ? bPwrOn2PwrGood ? ? ? 10 * 2 milli seconds ? bHubContrCurrent ? ? ?0 milli Ampere ? DeviceRemovable ? ?0x00 ? PortPwrCtrlMask ? ?0xff ?Hub Port Status: ? ?Port 1: 0000.0100 power ? ?Port 2: 0000.0100 power ? ?Port 3: 0000.0100 power ? ?Port 4: 0000.0100 power ? ?Port 5: 0000.0100 power...

Hi nut-upsdev, I have just got OMRON BX35F. Only object files and usage information is included. Where should I start to help you to get it supported? Any interest in supporting it at all?

On Sep 6, 2014, at 4:16 PM, Leslie Rhorer <lrhorer at mygrande.net> wrote: > Oh, hey! That seems to have worked. I'm sure the UPS got plugged into a different port one of the (many) times the server was removed from the relay rack, and it was on a USB 3.0 port. I moved it to a 1.0 port and everything seems to be working just fine. The specifics of the motherboard and its USB

...e '1': + dstate_setinfo("battery.test.status", "Battery bad - replace"); + break; + case '2': + status_set("CAL"); + break; + case '3': + status_set("OVER"); + dstate_setinfo("battery.test.status", "Overcurrent?"); + break; + case '4': + /* The following message is confusing, and may not be accurate: */ + /* dstate_setinfo("battery.test.status", "Battery state unknown"); */ + break; + case '5': + status_set("OVER"); + dstate_setinfo(...

...None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 12 Hub Descriptor: bLength 11 bDescriptorType 41 nNbrPorts 8 wHubCharacteristic 0x000a No power switching (usb 1.0) Per-port overcurrent protection TT think time 8 FS bits bPwrOn2PwrGood 10 * 2 milli seconds bHubContrCurrent 0 milli Ampere DeviceRemovable 0xb7 0xc8 PortPwrCtrlMask 0xa0 0x08 Hub Port Status: Port 1: 0000.0000 Port 2: 0000.0100 power Port 3: 0000.0100 power Port 4: 0000.0100...

On 9/6/2014 12:47 PM, Charles Lepple wrote: > On Sep 6, 2014, at 12:39 PM, Leslie Rhorer <lrhorer at mygrande.net> wrote: > >> I made a number of hardware and software changes, including an upgrade to the latest software versions for that distro (Debian Wheezy), > > Can you be more specific about the changes? Well, I did an automated upgrade (apt-get upgrade), I changed

...e None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 Hub Descriptor: bLength 11 bDescriptorType 41 nNbrPorts 8 wHubCharacteristic 0x000a No power switching (usb 1.0) Per-port overcurrent protection TT think time 8 FS bits bPwrOn2PwrGood 10 * 2 milli seconds bHubContrCurrent 0 milli Ampere DeviceRemovable 0x00 0x60 PortPwrCtrlMask 0x17 0x15 Hub Port Status: Port 1: 0000.0100 power Port 2: 0000.0100 power Port 3: 0000.0100 power Port 4: 0000.0100 powe...

...Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 255 Hub Descriptor: bLength 9 bDescriptorType 41 nNbrPorts 2 wHubCharacteristic 0x000a No power switching (usb 1.0) Per-port overcurrent protection bPwrOn2PwrGood 1 * 2 milli seconds bHubContrCurrent 0 milli Ampere DeviceRemovable 0x00 PortPwrCtrlMask 0x00 Hub Port Status: Port 1: 0000.0100 power Port 2: 0000.0303 lowspeed power enable connect Device Status: 0x0001 Self Power...

...None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 Hub Descriptor: bLength 9 bDescriptorType 41 nNbrPorts 3 wHubCharacteristic 0x0009 Per-port power switching Per-port overcurrent protection TT think time 8 FS bits bPwrOn2PwrGood 10 * 2 milli seconds bHubContrCurrent 0 milli Ampere DeviceRemovable 0x00 PortPwrCtrlMask 0xff Hub Port Status: Port 1: 0000.0108 power oc Port 2: 0000.030b lowspeed power oc enable connect Port 3: 0000.0108 po...

I've been noticing that my group of Polycom IP 501 phones seems to randomly reset themselves nearly every night (I guess it usually happens at night, since I've never seen it happen while I've been at work during the day).. When I say "reset", I mean, the hands free volume and ring volume are set to the default and the call logs (received calls, missed calls, placed calls)

> Hello everyone. I try to connect four PowerMust 2000 ups's via usb to one > computer using megatec_usb driver. But megatec_usb completly ignores port > directive in ups.conf, I even try port = /dev/null and megatec_usb founds > ups and it works. The 'port' is not used for USB connected devices, it's only needed for compatibility reasons. > Problem is that

I have a CentOS-5.6 remote server in a house in Italy, where there are occasional thunder-storms. There was one yesterday, when the electricity went off 3 times, for a second or so on each occasion. My server, an HP MicroServer, came back (re-booted) on 2 of the 3 occasions, but not on the third. I assume that the problem arises because the machine does not close down properly. (Although it is

...None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 255 Hub Descriptor: bLength 9 bDescriptorType 41 nNbrPorts 2 wHubCharacteristic 0x000a No power switching (usb 1.0) Per-port overcurrent protection bPwrOn2PwrGood 1 * 2 milli seconds bHubContrCurrent 0 milli Ampere DeviceRemovable 0x00 PortPwrCtrlMask 0xff Hub Port Status: Port 1: 0000.0300 lowspeed power Port 2: 0000.0300 lowspeed power Device Status: 0x0003 Self Powered Remote Wakeup Enable...

The DDRdrive X1 OpenSolaris device driver is now complete, please join us in our first-ever ZFS Intent Log (ZIL) beta test program. A select number of X1s are available for loan, preferred candidates would have a validation background and/or a true passion for torturing new hardware/driver :-) We are singularly focused on the ZIL device market, so a test environment bound by synchronous writes