Post Reply 
 
Thread Rating:
  • 1 Vote(s) - 1 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Remote.xml for CEC through Samsung Tv's
08-23-2012, 04:59 AM
Post: #11
RE: Remote.xml for CEC through Samsung Tv's
(08-22-2012 11:40 PM)Dilligaf Wrote:  tail -F /home/pi/.xbmc/temp/xbmc.log Will give you a real time view of the log in an ssh session

It seems crazy for each one of us to have to determine by real-time monitoring of a log file which keys on the Samsung remote are actually CEC keys. I've searched, but cannot find it documented anywhere.

I did find this over at OpenELEC:

CEC OpenELEC

(Yes, I've donated. Have you?)
Find all posts by this user
Quote this message in a reply
08-23-2012, 02:40 PM
Post: #12
RE: Remote.xml for CEC through Samsung Tv's
(08-23-2012 04:59 AM)Buadhai Wrote:  
(08-22-2012 11:40 PM)Dilligaf Wrote:  tail -F /home/pi/.xbmc/temp/xbmc.log Will give you a real time view of the log in an ssh session

It seems crazy for each one of us to have to determine by real-time monitoring of a log file which keys on the Samsung remote are actually CEC keys. I've searched, but cannot find it documented anywhere.

I did find this over at OpenELEC:

CEC OpenELEC

Nice! I'll try - in a few weeks - this remote.xml and get back here.

Code:
Raspberry Pi 512MB + D-Link USB Hub + 1TB HDD (media) + wired network
XBMC Gotham
Samsung SD card 8GB - Class 10
USB hub powering Rpi
Custom Overclock: arm:1050/core:500/ram:500/volt:6v/gpu_mem:160 - CPU: 60°-65° with heat sinks
Find all posts by this user
Quote this message in a reply
08-23-2012, 09:37 PM
Post: #13
RE: Remote.xml for CEC through Samsung Tv's
(08-22-2012 11:40 PM)Dilligaf Wrote:  tail -F /home/pi/.xbmc/temp/xbmc.log Will give you a real time view of the log in an ssh session

OK I've just tried that and got this when I pressed the 'FAV.CH' button on my remote:
Code:
21:39:36 T:1138250816   DEBUG: CecLogMessage - received data: header:00030004 p0:002F4401 p1:00000000 p2:00000000 p3:00000000 reason:4
21:39:36 T:1182790720   DEBUG: CecLogMessage - >> 01:44:2f
21:39:36 T:1182790720   DEBUG: CecLogMessage - >> TV (0) -> Recorder 1 (1): user control pressed (44)
21:39:36 T:1182790720   DEBUG: CecCommand - processing command: initiator=0 destination=1 opcode=44
21:39:36 T:1182790720   DEBUG: CecLogMessage - key pressed: next favourite (2f)
21:39:36 T:1182790720   DEBUG: PushCecKeypress - received key e5 duration 0
21:39:36 T:1102831616   DEBUG: OnKey: 229 (e5) pressed, action is ContextMenu
21:39:36 T:1102831616   DEBUG: CFavourites::Load - no system favourites found, skipping
21:39:36 T:1102831616   DEBUG: CFavourites::Load - no userdata favourites found, skipping
21:39:36 T:1102831616    INFO: Loading skin file: DialogContextMenu.xml
21:39:36 T:1102831616   DEBUG: ------ Window Init (DialogContextMenu.xml) ------
21:39:36 T:1138250816   DEBUG: CecLogMessage - received data: header:00030008 p0:002F4501 p1:00000000 p2:00000000 p3:00000000 reason:8
21:39:36 T:1182790720   DEBUG: CecLogMessage - >> 01:45:2f
21:39:36 T:1182790720   DEBUG: CecLogMessage - >> TV (0) -> Recorder 1 (1): user control release (45)
21:39:36 T:1182790720   DEBUG: CecCommand - processing command: initiator=0 destination=1 opcode=45
21:39:36 T:1182790720   DEBUG: CecLogMessage - key released: next favourite (2f)
21:39:36 T:1182790720   DEBUG: PushCecKeypress - received key e5 duration 381
As a comparison, this is what happens if I press the blue button
Code:
21:37:25 T:1138250816   DEBUG: CecLogMessage - received data: header:00030004 p0:00714401 p1:00000000 p2:00000000 p3:00000000 reason:4
21:37:25 T:1182790720   DEBUG: CecLogMessage - >> 01:44:71
21:37:25 T:1182790720   DEBUG: CecLogMessage - >> TV (0) -> Recorder 1 (1): user control pressed (44)
21:37:25 T:1182790720   DEBUG: CecCommand - processing command: initiator=0 destination=1 opcode=44
21:37:25 T:1182790720   DEBUG: CecLogMessage - key pressed: F1 (blue) (71)
21:37:25 T:1182790720   DEBUG: PushCecKeypress - received key fe duration 0
21:37:25 T:1102831616   DEBUG: OnKey: 254 (fe) pressed, action is XBMC.ActivateWindow(Favourites)
21:37:25 T:1102831616   ERROR: Control 450 in window 10134 has been asked to focus, but it can't
21:37:25 T:1102831616   DEBUG: Activating window ID: 10134
21:37:25 T:1138250816   DEBUG: CecLogMessage - received data: header:00030008 p0:00714501 p1:00000000 p2:00000000 p3:00000000 reason:8
21:37:25 T:1182790720   DEBUG: CecLogMessage - >> 01:45:71
21:37:25 T:1182790720   DEBUG: CecLogMessage - >> TV (0) -> Recorder 1 (1): user control release (45)
21:37:25 T:1182790720   DEBUG: CecCommand - processing command: initiator=0 destination=1 opcode=45
21:37:25 T:1182790720   DEBUG: CecLogMessage - key released: F1 (blue) (71)
21:37:25 T:1182790720   DEBUG: PushCecKeypress - received key fe duration 376

So in the blue example it has (blue) which I guess is what is used in the remote.xml, but there's no corresponding value in the log for FAV.CH button. Is there another xml file I need to map some ID number to a button name?
Find all posts by this user
Quote this message in a reply
08-23-2012, 10:55 PM
Post: #14
RE: Remote.xml for CEC through Samsung Tv's
DEBUG: CecLogMessage - key pressed: next favourite (2f)
is from your log

The format is: -->
<!-- <device> -->
<!-- <button>action</button> -->
<!-- </device>

is from remote.xml so I would assume it would be
<next favorite>desired_action</next favorite>
or maybe
<2f>desired_action</2f>

But I don't know for sure

Pi problems?? Start here http://forum.stmlabs.com/showthread.php?tid=3918
http://elinux.org/R-Pi_Troubleshooting
http://elinux.org/RPi_config.txt
Find all posts by this user
Quote this message in a reply
08-23-2012, 11:36 PM
Post: #15
RE: Remote.xml for CEC through Samsung Tv's
Cheers, I shall give that a go with some other buttons.

But I noticed the FAV.CH brings up codec information when playing a video and looking at /opt/xbmc-bcm/xbmc-bin/share/xbmc/system/keymaps/remote.xml it seems the codecinfo is mapped to <title>
So mapping functions to <title> allows me to use the FAV.CH button.

Strange how there are no mentions in the log, I shall keep investigating.
Find all posts by this user
Quote this message in a reply
08-24-2012, 01:13 AM (This post was last modified: 08-24-2012 01:15 AM by tuxen.)
Post: #16
RE: Remote.xml for CEC through Samsung Tv's
Sorry I've been away with some family matters at the hospital. All keys work on my ue55d8000v2 all number keys, stop, play, rew, skip, even the program keys they works as page up/down. The only functions missing was the ones I've added I will modify the file to correct the small bugs, and post the requests I have also have some tags that work although they are not mentioned in the log. Just give me a little more time sorry about that.. Things happen. :/
Find all posts by this user
Quote this message in a reply
08-27-2012, 04:57 PM
Post: #17
RE: Remote.xml for CEC through Samsung Tv's
No rush!
Family first

Code:
Raspberry Pi 512MB + D-Link USB Hub + 1TB HDD (media) + wired network
XBMC Gotham
Samsung SD card 8GB - Class 10
USB hub powering Rpi
Custom Overclock: arm:1050/core:500/ram:500/volt:6v/gpu_mem:160 - CPU: 60°-65° with heat sinks
Find all posts by this user
Quote this message in a reply
09-04-2012, 10:40 AM
Post: #18
RE: Remote.xml for CEC through Samsung Tv's
(08-22-2012 11:40 PM)Dilligaf Wrote:  tail -F /home/pi/.xbmc/temp/xbmc.log Will give you a real time view of the log in an ssh session

When i run this in SSH session i only get a list of errors from the pi. It doesn't show any CEC input..

Quote:login as: pi
pi@192.168.1.5's password:
Last login: Tue Sep 4 11:34:21 2012 from 192.168.1.2
pi@raspbmc:~$ tail -F /home/pi/.xbmc/temp/xbmc.log
11:37:58 T:1155568704 ERROR: COMXCoreComponent::DecoderEventHandler OMX.broadcom.image_decode - OMX_EventError detected, nData1(0x80001005), port 0
11:37:58 T:1228649536 ERROR: COMXImage::Decode m_omx_decoder.WaitForEvent result(0x80001005)
11:37:58 T:1155568704 ERROR: COMXCoreComponent::DecoderEventHandler OMX.broadcom.image_decode - OMX_EventError detected, nData1(0x80001005), port 0
11:37:58 T:1368757312 NOTICE: Thread Jobworker start, auto delete: true
11:37:58 T:1155568704 ERROR: COMXCoreComponent::DecoderEventHandler OMX.broadcom.image_decode - OMX_EventError detected, nData1(0x80001005), port 0
11:37:58 T:1336759360 ERROR: COMXImage::Decode m_omx_decoder.WaitForEvent result(0x80001005)
11:37:58 T:1155568704 ERROR: COMXCoreComponent::DecoderEventHandler OMX.broadcom.image_decode - OMX_EventError detected, nData1(0x80001005), port 0
11:37:59 T:1368757312 ERROR: Previous line repeats 2 times.
11:37:59 T:1368757312 ERROR: COMXImage::Decode m_omx_decoder.WaitForEvent result(0x80001005)
11:37:59 T:1155568704 ERROR: COMXCoreComponent::DecoderEventHandler OMX.broadcom.image_decode - OMX_EventError detected, nData1(0x80001005), port 0
11:39:25 T:1368757312 NOTICE: Thread Jobworker start, auto delete: true
11:39:50 T:1336759360 NOTICE: Thread Background Loader start, auto delete: false
11:39:50 T:1155568704 ERROR: COMXCoreComponent::DecoderEventHandler OMX.broadcom.image_decode - OMX_EventError detected, nData1(0x80001005), port 0
11:39:50 T:1368757312 ERROR: COMXImage::Decode m_omx_decoder.WaitForEvent result(0x80001005)
11:39:50 T:1155568704 ERROR: COMXCoreComponent::DecoderEventHandler OMX.broadcom.image_decode - OMX_EventError detected, nData1(0x80001005), port 0
11:39:54 T:1336759360 NOTICE: Thread Background Loader start, auto delete: false
11:40:00 T:1336759360 NOTICE: Previous line repeats 1 times.
11:40:00 T:1336759360 NOTICE: Thread Jobworker start, auto delete: true
11:40:06 T:1228649536 NOTICE: Thread Background Loader start, auto delete: false
11:40:06 T:1245623360 NOTICE: Thread Jobworker start, auto delete: true
11:40:10 T:1075122176 ERROR: Window Translator: Can't find window tv
11:40:11 T:1228649536 ERROR: Previous line repeats 1 times.
11:40:11 T:1228649536 NOTICE: Thread Background Loader start, auto delete: false
11:40:11 T:1228649536 ERROR: GetDirectory - Error getting add
11:40:16 T:1228649536 NOTICE: Thread Background Loader start, auto delete: false

I have a samsung remote as well and it looks like this:
[url=https://www.dropbox.com/s/4ij7xxx7xudymmn/2012-09-02%2023.18.15.jpg]
I want to remap the buttons since i'm missing a few ones.
Find all posts by this user
Quote this message in a reply
09-05-2012, 12:11 AM
Post: #19
RE: Remote.xml for CEC through Samsung Tv's
I have the same remote and I've remapped a few of the extra keys.
As far as know, these are the only buttons that work on this remote.

Code:
<keymap>
    <global>
        <remote>
              <teletext>XBMC.ActivateWindow(Home)</teletext> <!--PRE-CH -->
              <red>ContextMenu</red>
              <green>Info</green>
              <yellow>XBMC.ActivateWindow(VideoLibrary,MovieTitles)</yellow>
              <blue>XBMC.ActivateWindow(VideoLibrary,TvShowTitles)</blue>
              <title>XBMC.ActivateWindow(Favourites)</title> <!--FAV.CH-->
        </remote>
    </global>
    <FullscreenVideo>
        <remote>
              <pageplus>NextSubtitle</pageplus><!--channelup-->
              <pageminus>AudioNextLanguage</pageminus><!--channeldown-->
              <select>OSD</select>
              <red>OSD</red>
              <green>Info</green>
              <yellow>CodecInfo</yellow>
              <blue>OSD</blue>
              <teletext>AspectRatio</teletext> <!--PRE-CH -->
              <back>XBMC.ActivateWindow(Home)</back> <!--exit-->
        </remote>
    </FullscreenVideo>
</keymap>
Find all posts by this user
Quote this message in a reply
09-05-2012, 01:10 PM
Post: #20
RE: Remote.xml for CEC through Samsung Tv's
nadnerb - do you have any value for contenxt menu?
i don't see any option for context menu in the default mapping nor in your mapping
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)

Sponsored Advertisement