hoodride Wrote:So I received my replacement about 30 days ago, finally had more than thirty minutes to myself to figure why this one didn't work either. Step one, like Malard has said about 5 pages back: replace the batteries, they suck. The replacement dispatched does work for me, but only within a range of about 18 inches. Anyone want to buy a very lightly used Nyxboard?
try changing the usb dongle's port or sticking it in a usb hub to boost range
Malard Wrote:try changing the usb dongle's port or sticking it in a usb hub to boost range
Hi Malard, et all--
got my nyx 2days ago . my problem with RF range is slightly different.
I tried all possible USB ports (back and front) on my zotac mini-itx used as mediaCenter in the living room (no obstacles, clear line of sight): the reception was about 2meters ONLY!
Then I tested the same dongle on another zotac mini-itx that I use as a linux server in my studio and with surprise it worked perfectly for 5+ meters.
Main difference is that on my linux-server i've XBMC-PVR (latest stable, Aug 2011) but the mediaCenter runs XBMC Dharma. Is there a problem with Dharma release? There's a way to make it work or I'm obliged to upgrade to an unstable version under development?
Any help appreciated..
cheers!
Hi, received mine today, except for the sensor noise it looks very good but I have two questions:
1- How to make xbmc recognize the device to use the keyboard.nyxboard.xml file automaticaly. I just updated to last git eden version and it doesn't work. Nothing on the system/peripherals.
2- How to improve the range, it's a disaster for me. I can't use the remote in my couch, it's between 3 and 4 meters from the htpc (a zotac). I already change the batteries, didn't change anything.
I'm having intermittant problems with the device. I was able to get it to enumerate at first, but now it's not.
Here's the dmesg output.
Code:
[ 1098.404033] hub 2-0:1.0: unable to enumerate USB device on port 9
[ 1098.652035] hub 2-0:1.0: unable to enumerate USB device on port 9
[ 1098.900035] hub 2-0:1.0: unable to enumerate USB device on port 9
[ 1099.148042] hub 2-0:1.0: unable to enumerate USB device on port 9
[ 1099.396035] hub 2-0:1.0: unable to enumerate USB device on port 9
[ 1099.644037] hub 2-0:1.0: unable to enumerate USB device on port 9
[ 1099.892046] hub 2-0:1.0: unable to enumerate USB device on port 9
[ 1100.140049] hub 2-0:1.0: unable to enumerate USB device on port 9
[ 1100.388141] hub 2-0:1.0: unable to enumerate USB device on port 9
[ 1100.636045] hub 2-0:1.0: unable to enumerate USB device on port 9
[ 1100.884034] hub 2-0:1.0: unable to enumerate USB device on port 9
[ 1101.132034] hub 2-0:1.0: unable to enumerate USB device on port 9
[ 1101.380032] hub 2-0:1.0: unable to enumerate USB device on port 9
[ 1101.628034] hub 2-0:1.0: unable to enumerate USB device on port 9
[ 1101.876034] hub 2-0:1.0: unable to enumerate USB device on port 9
[ 1102.124033] hub 2-0:1.0: unable to enumerate USB device on port 9
[ 1102.372035] hub 2-0:1.0: unable to enumerate USB device on port 9
[ 1102.620036] hub 2-0:1.0: unable to enumerate USB device on port 9
[ 1102.868032] hub 2-0:1.0: unable to enumerate USB device on port 9
here's the lsusb output
Code:
root@XBMCLive:~# lsusb -vv
Bus 002 Device 038: ID 22b8:003b Motorola PCS
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 32
idVendor 0x22b8 Motorola PCS
idProduct 0x003b
bcdDevice 1.00
iManufacturer 1 Motorola
iProduct 2 Motorola NYXboard, 2.4GHz device
iSerial 3 ??????????
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 116
bNumInterfaces 4
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 1 Keyboard
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 76
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x000a 1x 10 bytes
bInterval 10
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 136
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x000a 1x 10 bytes
bInterval 2
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 226
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x000a 1x 10 bytes
bInterval 10
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 3
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 54
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 6
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 6
Device Status: 0x0000
(Bus Powered)
It worked kinda shakey for the first few key-presses, but now it's not enumerating at all. I rebooted, pressed buttons, tried a different USB port, pressed buttons.. I replaced the batteries..
The only thing I was not able to do was "reset the unit to factory settings".. I know it's a key combo, but its not in the instructions.
I think I figured it out... I have 3 bluetooth dongles in the room. I unplugged all of them except the target, then I plugged them back in after pairing. How can I prevent this from happening in the future?
outleradam Wrote:MaxPower 100mA
Looks like you have the same output from your "lsusb -v" that I do: MaxPower 100mA. Get close to the usb and try operating the remote. It has been suggested that we purchase an external powered hub to extend the range, but I am looking for a solution.
any idea what order numbers have been shipped? i think i was 525 and still havent relieved an email yet.
lsusb -v: MaxPower 100mA
same for me
I tried unplugging every other usb devices, didn't change anything.
Is there a button for the context menu? If not, can anyone suggest a mapping.
Here's my keymap.xml, in case anyone finds it useful.
Code:
<keymap>
<global>
<keyboard name="Motorola Nyxboard Hybrid">
<f3>RunScript(script.tvrage.com)</f3>
<f3 mod="shift">XBMC.ActivateWindow(videolibrary,tvshowtitles)</f3>
<f4 mod="shift">XBMC.ActivateWindow(videolibrary,recentlyaddedepisodes)</f4>
<f5 mod="shift">XBMC.ActivateWindow(VideoFiles,/storage/.xbmc/userdata/playlists/video/Movies.xsp)</f5>
<f6 mod="shift">XBMC.ActivateWindow(VideoFiles,/storage/.xbmc/userdata/playlists/video/Kids Movies.xsp)</f6>
<home>XBMC.ActivateWindow(Home)</home>
</keyboard>
</global>
</keymap>
hoodride Wrote:Looks like you have the same output from your "lsusb -v" that I do: MaxPower 100mA.
yeah my lsusb -vv is the same, although in the announcement over at the pulse-eight forum apparently motorola state the device needs to draw the full 500mA available to it... and interestingly when i measure the power by placing a multimeter in the middle, i only saw it drawing 20mA!
personally i don't mind buying a powered USB hub if it solves the range issue... HOWEVER this will be a last resort, after exhausting all other possibilities, because surely i shouldn't have to!
EDIT: just read up on the
USB wiki page and it states that the power is 100mA for each unit load and that a USB 2 device can use up to 5 unit loads, ! phew! so it could be that the 100mA reported in lsusb is the max it can draw per unit load, so which bit of lsusb tells you how many unit loads the device uses/requires?
Anyone in Australia received theirs yet? The tracking numb just says it's been handed on for international deliver but that was on the 28/9.......seems to be taking forever
gobbledigook Wrote:this will be a last resort, after exhausting all other possibilities, because surely i shouldn't have to!
I feel the exact same way. Some (yet) unknown linux config is the cause here.
gobbledigook Wrote:so it could be that the 100mA reported in lsusb is the max it can draw per unit load, so which bit of lsusb tells you how many unit loads the device uses/requires?
Wishful thinking, bud. I think that lsusb would display 0mA in that situation.
Investigations are still taking place in Motorola to find out what the actual issue is, but my post on the pulse-eight forums is a _known_ way to resolve it. Not the only way I am sure
hoodride Wrote:Looks like you have the same output from your "lsusb -v" that I do: MaxPower 100mA. Get close to the usb and try operating the remote. It has been suggested that we purchase an external powered hub to extend the range, but I am looking for a solution.
hey, I just checked the non-verbose lsusb output...
It's saying Bus 002, Device 001 is a 1.1root hub and Bus 001, Device 001 is a 2.0 Root hub. This leads me to believe that getting the device on bus 002 may resolve the issue.
I was able to increase the range by using a USB extender cable/dock I have for my bluetooth keyboard.
Tonight I will get this thing on my 001 USB Bus (Linux Foundation 2.0 root hub) and see if that changes anything.
outleradam Wrote:This leads me to believe that getting the device on bus 002 may resolve the issue.
Bus 002 is simply one of the other ports or sets of ports, sorry. I bet if you look at the verbose output of lsusb (lsusb -v) that you will see that the bus numbers push 0mA which is no limit.