Author Topic: MS MCE Blaster transmit on an MD problems  (Read 3569 times)

rodercot

  • Guest
MS MCE Blaster transmit on an MD problems
« on: August 18, 2008, 09:16:02 pm »
 Hey all,
 
 I was informed that the MS MCE remote would transmit in 710. I am using 710RC2. I have a model 1040 1.0a MS transceiver it is plugged into the MD and works fine.

 I setup the TV yesterday in that room with it. I made the template for a Konka Kc-3225 - learned the codes via the usbuirt on the core then set the device back to Lirc Embedded transmit (Bedroom Master) but I still get no activity from that MCE dongle to the Tv.

 Now on the md if I go to ui - advanced - ir codes - Kc 3225 and test the codes on the MD they work just fine but as soon as I try and use it normally I see nothing.

 What is the difference between testing the codes and using the codes as far as the system is concerned.

 Andrew have you had any luck with this at all.

 The template I made is for a KC-3225 Konka television. It uses IR and is controlled via the infrared category.

 I setup the Tv with the Wizard once the template was made and told it to use IR.

 Regards,

 Dave
« Last Edit: August 19, 2008, 12:30:12 pm by rodercot »

colinjones

  • Alumni
  • LinuxMCE God
  • *
  • Posts: 3003
    • View Profile
Re: MS MCE Blaster on MD problems
« Reply #1 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.

rodercot

  • Guest
Re: MS MCE Blaster on MD problems
« Reply #2 on: August 19, 2008, 11:49:02 am »
Colin,

 If you mean did I setup pipes for the TV? If So, then Yes, via the wizard. Audio and Video both from the output of the MD to the cmpt1 input on the TV.

 The TV looks to be a child of the MCE USb2 - Lirc Embedded Transmit - which I guess are all under the MD indirectly.
 
 Seth,

 Are your TV's like this on the MD's as well? If you got admin - advanced - devices - expand tree - Generic pc as md - mceusb2 - Lirc Embedded Transmit - TV

 Dave

colinjones

  • Alumni
  • LinuxMCE God
  • *
  • Posts: 3003
    • View Profile
Re: MS MCE Blaster transmit on an MD problems
« Reply #3 on: August 19, 2008, 02:57:48 pm »
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....

rodercot

  • Guest
Re: MS MCE Blaster transmit on an MD problems
« Reply #4 on: August 19, 2008, 07:57:42 pm »
Colin,

 Here are some log files  with a few button presses on the remote.  The thing that I cannot figure out is why it works when I goto ui - advanced - ir codes - the tv. press a few buttons like mute, volume etc.. they all work through the MCE transceiver then.


 
Code: [Select]
08 08/19/08 13:44:58.324 Received Message from 175 (mce_usb2 / Bedroom (Master)) to 65 (OnScreen Orbiter / Bedroom (Master)), type 1 id 203 Command:Move Right, retry none, parameters: <0x718e0b90>
08 08/19/08 13:44:58.326 Received Message from 65 (OnScreen Orbiter / Bedroom (Master)) to 65 (OnScreen Orbiter / Bedroom (Master)), type 1 id 192 Command:On, retry none, parameters: <0x548a6b90>
08 08/19/08 13:44:58.326   Parameter 21(Force): 1 <0x548a6b90>
08 08/19/08 13:44:58.326   Parameter 97(PK_Pipe): 0 <0x548a6b90>
08 08/19/08 13:44:58.326   Parameter 98(PK_Device_Pipes):  <0x548a6b90>
08 08/19/08 13:44:58.326 Received Message from 65 (OnScreen Orbiter / Bedroom (Master)) to 63 (Generic PC as MD / Bedroom (Master)), type 1 id 192 Command:On, retry none, parameters: <0xaacf8b90>
08 08/19/08 13:44:58.326   Parameter 21(Force): 1 <0xaacf8b90>
08 08/19/08 13:44:58.326   Parameter 97(PK_Pipe): 0 <0xaacf8b90>
08 08/19/08 13:44:58.326   Parameter 98(PK_Device_Pipes):  <0xaacf8b90>
08 08/19/08 13:44:58.326   Parameter 125(Already processed): 1 <0xaacf8b90>
08 08/19/08 13:44:58.326 Received Message from 65 (OnScreen Orbiter / Bedroom (Master)) to 180 (KC 3225 / Bedroom (Master)), type 1 id 192 Command:On, retry none, parameters: <0xb6bdbb90>
08 08/19/08 13:44:58.326   Parameter 98(PK_Device_Pipes):  <0xb6bdbb90>
08 08/19/08 13:44:58.326 Received Message from 65 (OnScreen Orbiter / Bedroom (Master)) to 180 (KC 3225 / Bedroom (Master)), type 1 id 91 Command:Input Select, retry none, parameters: <0xb6bdbb90>
08 08/19/08 13:44:58.327   Parameter 71(PK_Command_Input(Component 1)): 712 <0xb6bdbb90>
08 08/19/08 13:44:58.333 Received Message from 65 (OnScreen Orbiter / Bedroom (Master)) to 175 (mce_usb2 / Bedroom (Master)), type 1 id 687 Command:Set Screen Type, retry none, parameters: <0x548a6b90>
08 08/19/08 13:44:58.333   Parameter 48(Value): 0 <0x548a6b90>
08 08/19/08 13:45:00.659 Received Message from 175 (mce_usb2 / Bedroom (Master)) to 65 (OnScreen Orbiter / Bedroom (Master)), type 1 id 203 Command:Move Right, retry none, parameters: <0x718e0b90>
08 08/19/08 13:45:02.108 Received Message from 175 (mce_usb2 / Bedroom (Master)) to 65 (OnScreen Orbiter / Bedroom (Master)), type 1 id 203 Command:Move Right, retry none, parameters: <0x718e0b90>
08 08/19/08 13:45:03.461 Received Message from 175 (mce_usb2 / Bedroom (Master)) to 65 (OnScreen Orbiter / Bedroom (Master)), type 1 id 203 Command:Move Right, retry none, parameters: <0x718e0b90>
08 08/19/08 13:45:06.844 Received Message from 175 (mce_usb2 / Bedroom (Master)) to 65 (OnScreen Orbiter / Bedroom (Master)), type 1 id 203 Command:Move Right, retry none, parameters: <0x718e0b90>
08 08/19/08 13:45:07.561 Received Message from 175 (mce_usb2 / Bedroom (Master)) to 65 (OnScreen Orbiter / Bedroom (Master)), type 1 id 203 Command:Move Right, retry none, parameters: <0x718e0b90>
08 08/19/08 13:45:08.093 Received Message from 175 (mce_usb2 / Bedroom (Master)) to 65 (OnScreen Orbiter / Bedroom (Master)), type 1 id 203 Command:Move Right, retry none, parameters: <0x718e0b90>
08 08/19/08 13:45:09.145 Received Message from 175 (mce_usb2 / Bedroom (Master)) to 65 (OnScreen Orbiter / Bedroom (Master)), type 1 id 202 Command:Move Left, retry none, parameters: <0x718e0b90>
08 08/19/08 13:45:09.362 Received Message from 175 (mce_usb2 / Bedroom (Master)) to 65 (OnScreen Orbiter / Bedroom (Master)), type 1 id 202 Command:Move Left, retry none, parameters: <0x718e0b90>
08 08/19/08 13:45:09.692 Received Message from 175 (mce_usb2 / Bedroom (Master)) to 65 (OnScreen Orbiter / Bedroom (Master)), type 1 id 202 Command:Move Left, retry none, parameters: <0x718e0b90>
08 08/19/08 13:45:12.483 Received Message from 175 (mce_usb2 / Bedroom (Master)) to 10 (Media Plug-in / Living Room/Family Room), type 1 id 97 Command:Mute, retry none, parameters: <0x718e0b90>
05 08/19/08 13:45:12.484 An orbiter sent the media handler message type: 1 id: 97, but there's no stream in ea 2 <0x912d1b90>
08 08/19/08 13:45:14.719 Received Message from 175 (mce_usb2 / Bedroom (Master)) to 10 (Media Plug-in / Living Room/Family Room), type 1 id 97 Command:Mute, retry none, parameters: <0x718e0b90>
05 08/19/08 13:45:14.720 An orbiter sent the media handler message type: 1 id: 97, but there's no stream in ea 2 <0x912d1b90>
08 08/19/08 13:45:16.050 Received Message from 175 (mce_usb2 / Bedroom (Master)) to 10 (Media Plug-in / Living Room/Family Room), type 1 id 97 Command:Mute, retry none, parameters: <0x718e0b90>
05 08/19/08 13:45:16.051 An orbiter sent the media handler message type: 1 id: 97, but there's no stream in ea 2 <0x912d1b90>
08 08/19/08 13:45:18.057 Received Message from 175 (mce_usb2 / Bedroom (Master)) to 10 (Media Plug-in / Living Room/Family Room), type 1 id 97 Command:Mute, retry none, parameters: <0x718e0b90>
05 08/19/08 13:45:18.057 An orbiter sent the media handler message type: 1 id: 97, but there's no stream in ea 2 <0x912d1b90>
08 08/19/08 13:45:19.241 Received Message from 175 (mce_usb2 / Bedroom (Master)) to 10 (Media Plug-in / Living Room/Family Room), type 1 id 97 Command:Mute, retry none, parameters: <0x718e0b90>
05 08/19/08 13:45:19.242 An orbiter sent the media handler message type: 1 id: 97, but there's no stream in ea 2 <0x912d1b90>
08 08/19/08 13:45:19.465 Received Message from 175 (mce_usb2 / Bedroom (Master)) to 10 (Media Plug-in / Living Room/Family Room), type 1 id 97 Command:Mute, retry none, parameters: <0x718e0b90>
05 08/19/08 13:45:19.465 An orbiter sent the media handler message type: 1 id: 97, but there's no stream in ea 2 <0x912d1b90>
08 08/19/08 13:45:20.575 Received Message from 175 (mce_usb2 / Bedroom (Master)) to 10 (Media Plug-in / Living Room/Family Room), type 1 id 89 Command:Vol Up, retry none, parameters: <0x718e0b90>
08 08/19/08 13:45:20.576 Received Message from 175 (mce_usb2 / Bedroom (Master)) to 63 (Generic PC as MD / Bedroom (Master)), type 1 id 89 Command:Vol Up, retry none, parameters: <0xa8cf4b90>
08 08/19/08 13:45:20.576 Forwarding 89 Command:Vol Up up pipe to 180 (KC 3225) <0xb6bdbb90>
08 08/19/08 13:45:22.024 Received Message from 175 (mce_usb2 / Bedroom (Master)) to 10 (Media Plug-in / Living Room/Family Room), type 1 id 89 Command:Vol Up, retry none, parameters: <0x718e0b90>
08 08/19/08 13:45:22.025 Received Message from 175 (mce_usb2 / Bedroom (Master)) to 63 (Generic PC as MD / Bedroom (Master)), type 1 id 89 Command:Vol Up, retry none, parameters: <0xa8cf4b90>
08 08/19/08 13:45:22.025 Forwarding 89 Command:Vol Up up pipe to 180 (KC 3225) <0xb6bdbb90>
08 08/19/08 13:45:25.401 Received Message from 175 (mce_usb2 / Bedroom (Master)) to 65 (OnScreen Orbiter / Bedroom (Master)), type 1 id 194 Command:Toggle Power, retry none, parameters: <0x718e0b90>
08 08/19/08 13:45:25.405 Received Message from 65 (OnScreen Orbiter / Bedroom (Master)) to 175 (mce_usb2 / Bedroom (Master)), type 1 id 687 Command:Set Screen Type, retry none, parameters: <0x548a6b90>
08 08/19/08 13:45:25.405   Parameter 48(Value): 0 <0x548a6b90>
08 08/19/08 13:45:28.122 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>
08 08/19/08 13:45:28.134 Received Message from 65 (OnScreen Orbiter / Bedroom (Master)) to 63 (Generic PC as MD / Bedroom (Master)), type 1 id 193 Command:Off, retry none, parameters: <0xaacf8b90>
08 08/19/08 13:45:28.134   Parameter 21(Force): 1 <0xaacf8b90>
08 08/19/08 13:45:28.134   Parameter 97(PK_Pipe): 0 <0xaacf8b90>
08 08/19/08 13:45:28.134   Parameter 125(Already processed): 1 <0xaacf8b90>
08 08/19/08 13:45:28.134 Received Message from 65 (OnScreen Orbiter / Bedroom (Master)) to 180 (KC 3225 / Bedroom (Master)), type 1 id 193 Command:Off, retry none, parameters: <0xb6bdbb90>
08 08/19/08 13:45:28.134 Received Message from 65 (OnScreen Orbiter / Bedroom (Master)) to 180 (KC 3225 / Bedroom (Master)), type 1 id 193 Command:Off, retry none, parameters: <0xb6bdbb90>
08 08/19/08 13:45:28.136 Received Message from 65 (OnScreen Orbiter / Bedroom (Master)) to 175 (mce_usb2 / Bedroom (Master)), type 1 id 687 Command:Set Screen Type, retry none, parameters: <0x548a6b90>
08 08/19/08 13:45:28.136   Parameter 48(Value): 0 <0x548a6b90>
08 08/19/08 13:45:32.775 Received Message from 175 (mce_usb2 / Bedroom (Master)) to 65 (OnScreen Orbiter / Bedroom (Master)), type 1 id 194 Command:Toggle Power, retry none, parameters: <0x718e0b90>
08 08/19/08 13:45:32.791 Received Message from 65 (OnScreen Orbiter / Bedroom (Master)) to 175 (mce_usb2 / Bedroom (Master)), type 1 id 687 Command:Set Screen Type, retry none, parameters: <0x548a6b90>
08 08/19/08 13:45:32.791   Parameter 48(Value): 0 <0x548a6b90>
08 08/19/08 13:45:34.247 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:34.248 Received Message from 65 (OnScreen Orbiter / Bedroom (Master)) to 65 (OnScreen Orbiter / Bedroom (Master)), type 1 id 192 Command:On, retry none, parameters: <0x548a6b90>
08 08/19/08 13:45:34.248   Parameter 21(Force): 1 <0x548a6b90>
08 08/19/08 13:45:34.248   Parameter 97(PK_Pipe): 0 <0x548a6b90>
08 08/19/08 13:45:34.248   Parameter 98(PK_Device_Pipes):  <0x548a6b90>
08 08/19/08 13:45:34.248 Received Message from 65 (OnScreen Orbiter / Bedroom (Master)) to 63 (Generic PC as MD / Bedroom (Master)), type 1 id 192 Command:On, retry none, parameters: <0xaacf8b90>
08 08/19/08 13:45:34.248   Parameter 21(Force): 1 <0xaacf8b90>
08 08/19/08 13:45:34.248   Parameter 97(PK_Pipe): 0 <0xaacf8b90>
08 08/19/08 13:45:34.248   Parameter 98(PK_Device_Pipes):  <0xaacf8b90>
08 08/19/08 13:45:34.248   Parameter 125(Already processed): 1 <0xaacf8b90>
08 08/19/08 13:45:34.248 Received Message from 65 (OnScreen Orbiter / Bedroom (Master)) to 180 (KC 3225 / Bedroom (Master)), type 1 id 192 Command:On, retry none, parameters: <0xb6bdbb90>
08 08/19/08 13:45:34.248   Parameter 98(PK_Device_Pipes):  <0xb6bdbb90>
08 08/19/08 13:45:34.248 Received Message from 65 (OnScreen Orbiter / Bedroom (Master)) to 180 (KC 3225 / Bedroom (Master)), type 1 id 91 Command:Input Select, retry none, parameters: <0xb6bdbb90>
08 08/19/08 13:45:34.248   Parameter 71(PK_Command_Input(Component 1)): 712 <0xb6bdbb90>
08 08/19/08 13:45:36.291 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:36.301 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:36.301   Parameter 21(Force): 1 <0x548a6b90>
08 08/19/08 13:45:36.301   Parameter 97(PK_Pipe): 0 <0x548a6b90>
08 08/19/08 13:45:36.301 Received Message from 65 (OnScreen Orbiter / Bedroom (Master)) to 63 (Generic PC as MD / Bedroom (Master)), type 1 id 193 Command:Off, retry none, parameters: <0xaacf8b90>
08 08/19/08 13:45:36.301   Parameter 21(Force): 1 <0xaacf8b90>
08 08/19/08 13:45:36.301   Parameter 97(PK_Pipe): 0 <0xaacf8b90>
08 08/19/08 13:45:36.301   Parameter 125(Already processed): 1 <0xaacf8b90>
08 08/19/08 13:45:36.301 Received Message from 65 (OnScreen Orbiter / Bedroom (Master)) to 180 (KC 3225 / Bedroom (Master)), type 1 id 193 Command:Off, retry none, parameters: <0xb6bdbb90>
08 08/19/08 13:45:36.302 Received Message from 65 (OnScreen Orbiter / Bedroom (Master)) to 180 (KC 3225 / Bedroom (Master)), type 1 id 193 Command:Off, retry none, parameters: <0xb6bdbb90>
08 08/19/08 13:45:36.304 Received Message from 65 (OnScreen Orbiter / Bedroom (Master)) to 175 (mce_usb2 / Bedroom (Master)), type 1 id 687 Command:Set Screen Type, retry none, parameters: <0x548a6b90>
08 08/19/08 13:45:36.304   Parameter 48(Value): 0 <0x548a6b90>


 Dave
« Last Edit: August 19, 2008, 08:06:56 pm by rodercot »

colinjones

  • Alumni
  • LinuxMCE God
  • *
  • Posts: 3003
    • View Profile
Re: MS MCE Blaster transmit on an MD problems
« Reply #5 on: August 20, 2008, 12:15:10 am »
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...

rodercot

  • Guest
Re: MS MCE Blaster transmit on an MD problems
« Reply #6 on: August 20, 2008, 12:20:04 am »
Hi Colin,

 There is no log for the TV, I looked for exactly that. I cannot see as the TV would be receiving anything as the emitter is not lighting at all under normal use, the transceiver lights up as it receives the commands but nothing gets out to the TV.

 Dave

colinjones

  • Alumni
  • LinuxMCE God
  • *
  • Posts: 3003
    • View Profile
Re: MS MCE Blaster transmit on an MD problems
« Reply #7 on: August 20, 2008, 12:50:10 am »
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?

rodercot

  • Guest
Re: MS MCE Blaster transmit on an MD problems
« Reply #8 on: August 20, 2008, 02:46:24 am »
Here is what the code looks like when testing the tv from the Advanced - IR code window on the Md. The is when it actually sends the command to the emitter from the MCE usb2.



 
Code: [Select]
08 08/19/08 20:23:28.648 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>
08 08/19/08 20:23:29.999 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:30.000 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:30.000   Parameter 3(PK_DesignObj):  <0x4e43db90>
08 08/19/08 20:23:30.000   Parameter 9(Text):  <0x4e43db90>
08 08/19/08 20:23:30.000   Parameter 25(PK_Text): 670 <0x4e43db90>
08 08/19/08 20:23:30.000 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:30.000   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>
08 08/19/08 20:23:31.178 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:31.179 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>

 Dave

seth

  • Guru
  • ****
  • Posts: 485
  • A day w/o LinuxMCE is like a day w/o sunshine!
    • View Profile
Re: MS MCE Blaster transmit on an MD problems
« Reply #9 on: August 20, 2008, 01:28:51 pm »
 ???
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
Code: [Select]
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
Code: [Select]
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
".....Because Once you've LinuxMCE'd....."
System stats located at my user page:

http://wiki.linuxmce.org/index.php/User:Seth

jondecker76

  • Alumni
  • wants to work for LinuxMCE
  • *
  • Posts: 763
    • View Profile
Re: MS MCE Blaster transmit on an MD problems
« Reply #10 on: August 20, 2008, 01:45:29 pm »
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 (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.

rodercot

  • Guest
Re: MS MCE Blaster transmit on an MD problems
« Reply #11 on: August 20, 2008, 02:16:00 pm »
Jon, Seth,

 I just set up my test MD with the Same TV and I get exactly the same problem. No transmit on use.

 I cannot understand how the pipes would be setup wrong. You have an MD with an output going to the input on the TV, Which is setup in the Wizard via Sarah. So unless the wizard is not setting the up properly.

 Now I notice that if I goto - devices - md - I have pipes for the tv- Audio None - KC3225 - Component 1 - Video None - KC3225 - Component 1.
 
 But if I goto Devices - A/V equipment - Master Bedroom - It shows the TV with no pipes - but if I click on the connection wizard the pipes are there. I also have a Live TV 6141 which is the Live TV for the sat rcvr in the living room and it shows it's pipe as connected and controlled from the core/hybrid in the living room.

 If I drill down to advanced - generic pc as md - mceusb_2 - Lirc embedded transmit - kc3225 (tv). There are no pipes listed in there but if I go one more level down to LiveTV(kc3225) it shows the a/v pipes for the tuner portion of this tv, which I assume is normal.

 I did some browsing the source files this morning - man there are a lot of support files for the driver for this transceiver - anyhow, I could not find anywhere in those files what tells the transceiver which port to output on.

 rgds,

 Dave

rodercot

  • Guest
Re: MS MCE Blaster transmit on an MD problems
« Reply #12 on: August 20, 2008, 02:52:12 pm »
Jon,

 Can we just copuy those files as downloads and then place them in the proper directories or do we need to set-up a developement system.

 I notice when browsing the source there are several steps in the source folder. Do we only need to copy what you specified in your thread.

 Thanks,

 Dave

colinjones

  • Alumni
  • LinuxMCE God
  • *
  • Posts: 3003
    • View Profile
Re: MS MCE Blaster transmit on an MD problems
« Reply #13 on: August 20, 2008, 03:07:22 pm »
No transmit at all? You have dealt with the transmit bug haven't you? Seth details it here and in the wiki...

jondecker76

  • Alumni
  • wants to work for LinuxMCE
  • *
  • Posts: 763
    • View Profile
Re: MS MCE Blaster transmit on an MD problems
« Reply #14 on: August 20, 2008, 03:11:54 pm »
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.