Difference between revisions of "Connections/Control"
From LinuxMCE
(Created page with "==Links== *Media Directors *Laptop Media Directors *Nettop Media Directors *[[:Category:MediaDirectorTu...") |
|||
| Line 1: | Line 1: | ||
==Links== | ==Links== | ||
| − | *[[:Category: | + | *[[:Category:Serial|Serial]] |
| − | *[[:Category: | + | *[[:Category:USB|USB]] |
| − | *[[:Category: | + | *[[:Category:Bluetooth|Bluetooth]] |
| − | *[[:Category: | + | *[[:Category:Infrared|Infrared]] |
| + | *[[:Category:Connect_Control_Tutorial|General Connect/Control Tutorials]] | ||
==About== | ==About== | ||
| + | |||
| + | Try to connect your controlled gear directly to the device that is controlling it. If you have an AV receiver with an RS232 port, connect it directly to the RS232 port on the Media Director instead of using an RS232-to-USB adapter. If you have a home automation controller with a USB plug, connect it directly to the core's USB port instead of a USB hub. | ||
| + | Hubs and adapters can have issues with the power management side of the USB spec. This can cause devices to simply drop off without warning, and not notify the kernel that they were dropped off. This can cause LinuxMCE to reassign a new device ID, which trips up the plug-and-play (PnP) code. | ||
Latest revision as of 14:01, 8 November 2011
Links
About
Try to connect your controlled gear directly to the device that is controlling it. If you have an AV receiver with an RS232 port, connect it directly to the RS232 port on the Media Director instead of using an RS232-to-USB adapter. If you have a home automation controller with a USB plug, connect it directly to the core's USB port instead of a USB hub. Hubs and adapters can have issues with the power management side of the USB spec. This can cause devices to simply drop off without warning, and not notify the kernel that they were dropped off. This can cause LinuxMCE to reassign a new device ID, which trips up the plug-and-play (PnP) code.
