LinuxMCE Forums
General => Users => Topic started by: pw44 on February 23, 2010, 10:45:44 pm
-
Hia,
i'm facing a problem with usb uirt, which i'm not being able to solve. After installed, usb uirt works, but sometime later, it stops to respond.
I did disconnect, try anotehr usb port, reboot the core/hybrid, it appears, the log shows it is reading code, but after a period of time, it dies.... not reading codes (pointing the remote to it and pressing any key) or sends any code....
05 02/23/10 18:16:35.189 GSD-Sleep Post 89 : 0 <0xb58f2b90>
05 02/23/10 18:16:35.189 GSD-Sleep Pre 89 : 0 <0xb58f2b90>
01 02/23/10 18:16:35.533 UsbUirt transmit failed sending 0000 006a 0022 0002 0158 00b0 0016 0042 0016 0016 0016 0042 0016 0042 0016 0042 0016 0042 0016 0042 0016 0016 0016 0016 0016 0042 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0042 0016 0042 0016 0016 0016 0042 0016 0042 0016 0016 0016 0016 0016 0016 0016 0042 0016 0016 0016 0042 0016 0016 0016 0016 0016 0042 0016 0042 0016 0042 0016 0016 0016 05fe 0158 0057 0016 0e70! <0xb58f2b90>
05 02/23/10 18:16:35.533 GSD-Sleep Post 89 : 0 <0xb58f2b90>
05 02/23/10 18:16:35.533 _QueueProc Post - 89 : 0 <0xb58f2b90>
05 02/23/10 18:16:35.533 ---- _QueueProc Ignored - 89 <0xb58f2b90>
05 02/23/10 18:16:39.514 #### Pre-Process Queue = 1 <0xb60f3b90>
05 02/23/10 18:16:39.514 #### Pre-Process Queue = 2 <0xb60f3b90>
05 02/23/10 18:16:39.559 _QueueProc Pre - 192 : 0 <0xb58f2b90>
05 02/23/10 18:16:39.559 GSD-Sleep Pre 192 : 0 <0xb58f2b90>
01 02/23/10 18:17:54.341 UsbUirt transmit failed sending 0000 006a 0022 0002 0158 00b0 0016 0042 0016 0016 0016 0042 0016 0042 0016 0042 0016 0042 0016 0042 0016 0016 0016 0016 0016 0042 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0042 0016 0016 0016 0042 0016 0042 0016 0042 0016 0016 0016 0016 0016 0016 0016 0042 0016 0042 0016 0016 0016 0016 0016 0016 0016 0042 0016 0042 0016 0042 0016 0016 0016 05fe 0158 0057 0016 0e70! <0xb60f3b90>
05 02/23/10 18:19:04.878 Got a reload command from 0 <0xb60f3b90>
05 02/23/10 18:19:05.177 void ClientSocket::Disconnect() on this socket: 0x86b5348 (m_Socket: 7) <0xb79db6c0>
I did reload the router, regen the orbiter but is not working.
I did add my AV amplifier, it was controlled well for some minutes and then usb uirt stopped to work.
Anyone faced this before and have a hint?
TIA
Paulo
-
With mine sometimes it feels like it goes into a sleep mode. If I hold down a button for a few seconds or press it repeatedly it'll start working again.
-
Hi,
unfortunately, it's not my case... even after pressing a buttom at the remote, and seeing the red led flashing, the log shows nothing. It looks like the communication between uirt and linuxmce died. but electrically, it remains feeded...
-
These tend to be sensitive to EMI. I was having this problem when the wire was running by the television. I had to plug mine into a front usb port and be very careful to run the line away from any other cabling. Once I got the routing right, the USBUIRT works great. I have had no problems for the last 8 months or so.
hope this helps
josh
-
Sensible to EMI? Well, i think it should be shielded.... I will try to reroute the cable.. if it does not work i will buy a tira-2 oem, and mount it inside the computer case..... having the blaster plugged in the back.
Thx for the hint.
-
Hia,
did reroute the uirt, plugging on the front panel, away from PSU and monitor and other EMI sources, but it keeps dying after a while.....
The last log i got is:
== ATTEMPT FRESH START ==
1 02/24/10 14:42:31 /usr/pluto/bin/Spawn_Device.sh 60 (spawning-device) 24115 Dev: 60; Already Running list: 15,16,18,19,40,41,21,22,25,47,23,26,53,65,35,63,58,
== FRESH START ==
1 02/24/10 14:42:31 /usr/pluto/bin/Spawn_Device.sh 60 (spawning-device) device: 60 ip: localhost cmd_line: USB_UIRT_0038
0 02/24/10 14:42:31 60 (spawning-device) Entering 60
========== NEW LOG SECTION ==========
1 02/24/10 14:42:31 60 (spawning-device) Starting... 1
1 02/24/10 14:42:31 60 (spawning-device) Found /usr/pluto/bin/USB_UIRT_0038
05 02/24/10 14:42:32.058 Creating child 61 <0xb79de6c0>
05 02/24/10 14:42:32.059 Note: Device manager has attached a device of type 1784 that this has no custom event handler for. It will not fire events. <0xb79de6c0>
05 02/24/10 14:42:32.059 Note: Device manager has attached a device of type 1784 that this has no custom handler for. This is normal for IR. <0xb79de6c0>
05 02/24/10 14:42:32.059 Creating child 69 <0xb79de6c0>
05 02/24/10 14:42:32.059 Note: Device manager has attached a device of type 2167 that this has no custom event handler for. It will not fire events. <0xb79de6c0>
05 02/24/10 14:42:32.059 Note: Device manager has attached a device of type 2167 that this has no custom handler for. This is normal for IR. <0xb79de6c0>
05 02/24/10 14:42:51.733 Infrared Code not found for Command 194. Will not be processed by IRBase. <0xb5effb90>
05 02/24/10 14:42:51.733 #### Pre-Process Queue = 1 <0xb5effb90>
05 02/24/10 14:42:51.733 _QueueProc Pre - 194 : 0 <0xb56feb90>
05 02/24/10 14:42:51.733 GSD-Sleep Pre 194 : 0 <0xb56feb90>
05 02/24/10 14:42:51.733 Could not find Infrared Code for Command 194. <0xb56feb90>
05 02/24/10 14:42:51.733 #### Pre-Process Queue = 1 <0xb5effb90>
05 02/24/10 14:42:58.730 GSD-Sleep Post 194 : 7000 <0xb56feb90>
05 02/24/10 14:42:58.730 _QueueProc Post - 194 : 7000 <0xb56feb90>
05 02/24/10 14:42:58.731 _QueueProc Pre - 177 : 0 <0xb56feb90>
05 02/24/10 14:42:58.731 GSD-Sleep Pre 177 : 0 <0xb56feb90>
05 02/24/10 14:43:01.291 GSD-Sleep Post 177 : 2000 <0xb56feb90>
05 02/24/10 14:43:01.291 _QueueProc Post - 177 : 2000 <0xb56feb90>
05 02/24/10 15:06:56.544 Infrared Code not found for Command 245. Will not be processed by IRBase. <0xb5effb90>
05 02/24/10 15:06:56.560 #### Pre-Process Queue = 1 <0xb5effb90>
05 02/24/10 15:06:56.570 _QueueProc Pre - 245 : 0 <0xb56feb90>
05 02/24/10 15:06:56.570 GSD-Sleep Pre 245 : 0 <0xb56feb90>
05 02/24/10 15:06:56.570 Could not find Infrared Code for Command 245. <0xb56feb90>
05 02/24/10 15:06:56.819 GSD-Sleep Post 245 : 250 <0xb56feb90>
05 02/24/10 15:06:56.819 _QueueProc Post - 245 : 250 <0xb56feb90>
05 02/24/10 15:14:21.410 Infrared Code not found for Command 245. Will not be processed by IRBase. <0xb5effb90>
05 02/24/10 15:14:21.410 #### Pre-Process Queue = 1 <0xb5effb90>
05 02/24/10 15:14:21.427 _QueueProc Pre - 245 : 0 <0xb56feb90>
05 02/24/10 15:14:21.427 GSD-Sleep Pre 245 : 0 <0xb56feb90>
05 02/24/10 15:14:21.427 Could not find Infrared Code for Command 245. <0xb56feb90>
05 02/24/10 15:14:21.679 GSD-Sleep Post 245 : 250 <0xb56feb90>
05 02/24/10 15:14:21.679 _QueueProc Post - 245 : 250 <0xb56feb90>
01 02/24/10 15:20:53.128
*** ERROR creating Learn Watchdog Thread! ***
<0xbd8c8b90>
01 02/24/10 15:20:53.139
*** ERROR creating Learn Thread! ***
<0xbd8c8b90>
== ATTEMPT FRESH START ==
1 02/25/10 00:44:39 /usr/pluto/bin/Spawn_Device.sh 60 (spawning-device) 29838 Dev: 60; Already Running list: 15,16,18,19,40,41,21,35,22,65,23,63,58,25,26,
== FRESH START ==
1 02/25/10 00:44:39 /usr/pluto/bin/Spawn_Device.sh 60 (spawning-device) device: 60 ip: localhost cmd_line: USB_UIRT_0038
0 02/25/10 00:44:39 60 (spawning-device) Entering 60
========== NEW LOG SECTION ==========
1 02/25/10 00:44:39 60 (spawning-device) Starting... 1
1 02/25/10 00:44:39 60 (spawning-device) Found /usr/pluto/bin/USB_UIRT_0038
05 02/25/10 0:44:40.033 Creating child 61 <0xb786c6c0>
05 02/25/10 0:44:40.034 Note: Device manager has attached a device of type 1784 that this has no custom event handler for. It will not fire events. <0xb786c6c0>
05 02/25/10 0:44:40.034 Note: Device manager has attached a device of type 1784 that this has no custom handler for. This is normal for IR. <0xb786c6c0>
05 02/25/10 0:44:40.034 Creating child 69 <0xb786c6c0>
05 02/25/10 0:44:40.034 Note: Device manager has attached a device of type 2167 that this has no custom event handler for. It will not fire events. <0xb786c6c0>
05 02/25/10 0:44:40.034 Note: Device manager has attached a device of type 2167 that this has no custom handler for. This is normal for IR. <0xb786c6c0>
05 02/25/10 0:45:14.831 #### Pre-Process Queue = 1 <0xb5dffb90>
05 02/25/10 0:45:14.832 _QueueProc Pre - 192 : 0 <0xb55feb90>
05 02/25/10 0:45:14.832 GSD-Sleep Pre 192 : 0 <0xb55feb90>
05 02/25/10 0:45:14.832 #### Pre-Process Queue = 1 <0xb5dffb90>
05 02/25/10 0:45:22.390 GSD-Sleep Post 192 : 7000 <0xb55feb90>
05 02/25/10 0:45:22.390 _QueueProc Post - 192 : 7000 <0xb55feb90>
05 02/25/10 0:45:22.390 _QueueProc Pre - 177 : 0 <0xb55feb90>
05 02/25/10 0:45:22.390 GSD-Sleep Pre 177 : 0 <0xb55feb90>
05 02/25/10 0:45:24.954 GSD-Sleep Post 177 : 2000 <0xb55feb90>
05 02/25/10 0:45:24.954 _QueueProc Post - 177 : 2000 <0xb55feb90>
05 02/25/10 0:46:25.399 Got a reload command from 0 <0xb5dffb90>
05 02/25/10 0:46:25.661 void ClientSocket::Disconnect() on this socket: 0x9b22368 (m_Socket: 7) <0xb786c6c0>
Return code: 2
2 02/25/10 00:46:25 60 (spawning-device) Device requests restart... count=1/50 dev=60
Thu Feb 25 00:46:25 BRT 2010 Restart
========== NEW LOG SECTION ==========
1 02/25/10 00:46:33 60 (spawning-device) Starting... 1
1 02/25/10 00:46:33 60 (spawning-device) Found /usr/pluto/bin/USB_UIRT_0038
05 02/25/10 0:46:34.901 Connect() failed, Error Code 111 (Connection refused)) <0xb799a6c0>
05 02/25/10 0:46:35.898 Connect() failed, Error Code 111 (Connection refused)) <0xb799a6c0>
05 02/25/10 0:46:38.148 Creating child 61 <0xb799a6c0>
05 02/25/10 0:46:38.148 Note: Device manager has attached a device of type 1784 that this has no custom event handler for. It will not fire events. <0xb799a6c0>
05 02/25/10 0:46:38.148 Note: Device manager has attached a device of type 1784 that this has no custom handler for. This is normal for IR. <0xb799a6c0>
05 02/25/10 0:46:38.148 Creating child 69 <0xb799a6c0>
05 02/25/10 0:46:38.148 Note: Device manager has attached a device of type 2167 that this has no custom event handler for. It will not fire events. <0xb799a6c0>
05 02/25/10 0:46:38.148 Note: Device manager has attached a device of type 2167 that this has no custom handler for. This is normal for IR. <0xb799a6c0>
05 02/25/10 0:53:16.214 #### Pre-Process Queue = 1 <0xb60b2b90>
05 02/25/10 0:53:16.215 _QueueProc Pre - 192 : 0 <0xb58b1b90>
05 02/25/10 0:53:16.215 GSD-Sleep Pre 192 : 0 <0xb58b1b90>
05 02/25/10 0:53:16.215 #### Pre-Process Queue = 1 <0xb60b2b90>
05 02/25/10 0:53:19.779 Got a reload command from 0 <0xb60b2b90>
05 02/25/10 0:53:23.769 GSD-Sleep Post 192 : 7000 <0xb58b1b90>
05 02/25/10 0:53:23.769 _QueueProc Post - 192 : 7000 <0xb58b1b90>
05 02/25/10 0:53:23.772 void ClientSocket::Disconnect() on this socket: 0x8319368 (m_Socket: 7) <0xb799a6c0>
Return code: 2
2 02/25/10 00:53:24 60 (spawning-device) Device requests restart... count=1/50 dev=60
Thu Feb 25 00:53:24 BRT 2010 Restart
========== NEW LOG SECTION ==========
1 02/25/10 00:53:32 60 (spawning-device) Starting... 1
1 02/25/10 00:53:32 60 (spawning-device) Found /usr/pluto/bin/USB_UIRT_0038
05 02/25/10 0:53:34.446 Creating child 61 <0xb79606c0>
05 02/25/10 0:53:34.446 Note: Device manager has attached a device of type 1784 that this has no custom eventhandler for. It will not fire events. <0xb79606c0>
05 02/25/10 0:53:34.446 Note: Device manager has attached a device of type 1784 that this has no custom handler for. This is normal for IR. <0xb79606c0>
05 02/25/10 0:53:34.446 Creating child 69 <0xb79606c0>
05 02/25/10 0:53:34.446 Note: Device manager has attached a device of type 2167 that this has no custom eventhandler for. It will not fire events. <0xb79606c0>
05 02/25/10 0:53:34.446 Note: Device manager has attached a device of type 2167 that this has no custom handler for. This is normal for IR. <0xb79606c0>
05 02/25/10 0:54:09.477 #### Pre-Process Queue = 1 <0xb6078b90>
05 02/25/10 0:54:09.477 _QueueProc Pre - 192 : 0 <0xb5877b90>
05 02/25/10 0:54:09.477 GSD-Sleep Pre 192 : 0 <0xb5877b90>
05 02/25/10 0:54:09.485 #### Pre-Process Queue = 1 <0xb6078b90>
05 02/25/10 0:54:17.022 GSD-Sleep Post 192 : 7000 <0xb5877b90>
05 02/25/10 0:54:17.022 _QueueProc Post - 192 : 7000 <0xb5877b90>
05 02/25/10 0:54:17.022 _QueueProc Pre - 177 : 0 <0xb5877b90>
05 02/25/10 0:54:17.022 GSD-Sleep Pre 177 : 0 <0xb5877b90>
05 02/25/10 0:54:19.574 GSD-Sleep Post 177 : 2000 <0xb5877b90>
05 02/25/10 0:54:19.574 _QueueProc Post - 177 : 2000 <0xb5877b90>
Anyone aware why it could be dying?
TIA