LinuxMCE Forums
General => Users => Topic started by: colinjones on August 18, 2008, 10:12:28 pm
-
Presuming that you created this as a child of the MD, did you set up at least one pipe (audio or video)?
Otherwise, although LMCE knows it can control the equipment it doesn't know you want it to. Basically I believe the pipes basically describe to LMCE a chain of devices involve in producing video or audio. So it knows if it wants to produce video, say, it knows which devices to turn on, set volume and inputs etc - otherwise it has no way of knowing that that particular device is involved in any way.
-
Yes, that's what I meant. Hmmmm... sounds all ok...
Now take a look at your dcerouter log... tail it, and then do things that should trigger TV commands. You should see it generating messages that capture all the devices on the pipe, and then repeating the same messages to each of them. Actually, you probably want to review this log as it starts all the devices up from a reload. Check that it is capturing all the devices in the query, issuing the commands to start them, and they successfully start. Then do something that should control the TV like play media - it should attempt to turn the TV on first, set the input and volume....
-
Hmm - can see roughly what you were doing and it mentioning the pipe to send messages down, but I can't really troubleshoot it with you as I have no pipes/equipment setup at the moment to compare with! Perhaps someone else can step in?
Also, you might want to review the TV device 180 log to see if it is logging any problems with the messages it is receiving...
-
Sorry Dave, was half asleep! I was thinking a GSD RS232 device - they create a log like 180_TVName.log
Perhaps with IR devices, the IR device itself logs messages for the TV device as the commands pass through it?
-
???
This has just started happening to me. It almost looks as though when done locally, it doesn't have the correct "Parameter" code:
From your posts on same command "Enter/Go" (OK button in the center of the D-Pad on my remote)
From The MD
Received Message from 175 (mce_usb2 / Bedroom (Master)) to 65 (OnScreen Orbiter / Bedroom (Master)), type 1 id 190 Command:Enter/Go, retry none, parameters: <0x718e0b90>
08 08/19/08 13:45:28.133 Received Message from 65 (OnScreen Orbiter / Bedroom (Master)) to 65 (OnScreen Orbiter / Bedroom (Master)), type 1 id 193 Command:Off, retry none, parameters: <0x548a6b90>
08 08/19/08 13:45:28.133 Parameter 21(Force): 1 <0x548a6b90>
08 08/19/08 13:45:28.133 Parameter 97(PK_Pipe): 0 <0x548a6b90>
From The Web Admin
Received Message from 175 (mce_usb2 / Bedroom (Master)) to 65 (OnScreen Orbiter / Bedroom (Master)), type 1 id 190 Command:Enter/Go, retry none, parameters: <0x71483b90>
08 08/19/08 20:23:28.649 Received Message from 65 (OnScreen Orbiter / Bedroom (Master)) to 65 (OnScreen Orbiter / Bedroom (Master)), type 1 id 25 Command:Set Text, retry none, parameters: <0x4e43db90>
08 08/19/08 20:23:28.649 Parameter 3(PK_DesignObj): <0x4e43db90>
08 08/19/08 20:23:28.649 Parameter 9(Text): <0x4e43db90>
08 08/19/08 20:23:28.649 Parameter 25(PK_Text): 670 <0x4e43db90>
08 08/19/08 20:23:28.649 Received Message from 65 (OnScreen Orbiter / Bedroom (Master)) to 176 (LIRC Embedded Transmit / Bedroom (Master)), type 1 id 191 Command:Send Code, retry none, parameters: <0x4e43db90>
08 08/19/08 20:23:28.649 Parameter 9(Text): 0000 006B 0000 0013 0074 0073 0013 003B 0013 003B 0013 003B 0013 003B 0013 003B 0013 003A 0013 0062 0013 003B 0013 003B 0013 003B 0013 003A 0013 0061 0013 003B 0013 003A 0013 0062 0013 003C 0013 0099 0013 0371 <0x4e43db90>
So from the admin it calls a different "Parameter" and then sends the "Pronto Code" as Text.
Tonight when I get home, I want to try viewing the logs from the USB-UIRT, using the same MCE remote (which works) and see if the output is the same.
This should be Mantis'd Let someone who know how the system works have a gander.
Regards,
Seth
-
I have done quite a bit of work with the IR stuff.
The difference between the test and actual use is that during the test, things such as repeat rate and delay are not taken into account. Therefore, I would Imagine that dialing these in should help for your button presses on the remote to get detected. The only other thing I could think of would be either the pipes are somehoe messed up, or you have multiple MCE remote templates.
The repeats in 0710 are not user adjustable, but I added the feature a while back. Instructions to pull in the required changes are here: http://forum.linuxmce.org/index.php?topic=5510.msg32690#msg32690 (http://forum.linuxmce.org/index.php?topic=5510.msg32690#msg32690) (no compiling required, just copying new files over). You could try adjusting the delay and repeats for the IR and see if that fixes it.
-
No transmit at all? You have dealt with the transmit bug haven't you? Seth details it here and in the wiki...
-
rodercot - yes just copy the files I listed in the thread- you don't really have to have a dev environment set up as they are all .php files, and therefore no compilation is needed.
-
Another thing to mention is that USBUIRT has its own code base, so bugs could bedifferent between a USBUIRT and some other IR transceiver. Though, of course, they also have some shared code. Do you have a USBUIRT available to compare to?
-
Hey Dave,
I was also having this problem and there is a post of mine floating around. I then got myself a USBUIRT and had the same problem as you described originally.
So basically with the MCE and the USBUIRT i get this problem, however both my test boxes needed to be used rather urgently for something else so I have had time to look into this. Once work decides to pay me I will be going down and buying some more kit so I can start playing again. :P
Cheers.