Jump to content
Flirc Forums

OneForAll URC-7140 and FLIRC-SE: IR Code and laggy response


matze2ooo
 Share

Recommended Posts

Hello everybody

 

To make it quick and clear :-) two questions here: 

 

1) 

I am using an OneForAll URC-7140 remote control. Is there any IR-code you can suggest to get all the keys working? Whats your experience? My TV-brand is LG so this codes are out of question.

 

I had no luck with all the Sony TV codes (1505, 1825, 1651), the flirc setup utility did not recognize a single key press. Someone in the forum suggested to use TV codes as chances are better to get every key on the remote working. 

 

2) 

XBMC reacted very laggy to key presses, I had to hold down a button for about 2 seconds to get some reaction on the GUI. I have already played around with the Inter-Key delay without any recognizable change. 

 

Thanks for your support and this great product!!!

 

Best, Matthias 

 

P.S: I have aleady upgraded to the latest firmware which is 3.5 atm if I remeber correctly. 

Edited by matze2ooo
Link to comment
Share on other sites

Hi.

Try using Samsung TV codes. I'm using one with my URC-6440.

Do you use RemoteMaster software to configure the remote? If yes then you can even create your own device upgrade which won't be recognized by any consumer hardware. I would use NEC1 protocol as I have good results with it and flirc.

Link to comment
Share on other sites

Thanks for your quick reply. I have tested a few Samsung codes with the same result. Buttons like volume_up, volume_down & mute are still not recognized, via the Flirc setup-GUI. However, play, stop, 1-9 and navigation work fine. I think I can do without volume control, as i am controlling everything via my amp. 

 

Unfortunately the Shutdown button isnt' working as well. I have double checked the cabling and powering on/off via front-button works fine. However I cant use the remote for this. But the Flirc tool recognized the keypress. What am I doing wrong here?

 

Is there some (hidden?) paramter i can give to flirc_util to capture the inputs received? 

Edited by matze2ooo
Link to comment
Share on other sites

In 3.5 firmware you should be able to at least have power up working correctly. It doesn't support power off yet. This has been fixed in firmware 3.6 which is in Flirc software 1.3.5 rc2 version (available on "beta" forum - don't be alarmed by the "beta" in the name of the forum, this is a release candidate version).

 

Have you recorded a power button with flirc_util record power? If yes then only thing I can think of why you can't power on the HTPC is that Flirc-SE is not getting power through USB when in S5 power state. Can you confirm somehow that USB ports are powered in S5 (power off) state? Maybe you have something that can be charged from USB port - then just plug it in when the HTPC is shutdown.

 

As for the volume keys not working: do you have volume punch through set up on the remote? When you switch to a device where you've set up the code for Flirc and press vol up/down does your AMP react? I have no problem at all with a Samsung TV code on my remote. I have PVR device button mode changed to TV and a Samsung TV code set on it. Every single button on the remote works and sends unique signal which is correctly recognized by Flirc. I think I've selected some newer TV model. Maybe that's the difference. You can also try some Panasonic TV (I haven't tried myself but I've read that they are OK).

 

You also can't have your remote too close to the Flirc when recording. It is very sensitive and when the distance is too small then the signal gets distorted. You should have the remote at least 1 meter (3 feets) from the Flirc. Or you can point the remote in a different direction, for example at the ceiling.

Link to comment
Share on other sites

It seems my HTPC correctly shut's down to the S5 state. The front USB port still is under current (tested with an bluetooth stick having an LED on it). I also have configued the power button using the GUI (not the flirc_util CLI tool). But still no luck. When I am on bash and I hit the power button on the remote the console returns "äääää", which tells me it receives some IR-code. But still no startup possible. Any other ideas? 

Edited by matze2ooo
Link to comment
Share on other sites

It seems my HTPC correctly shut's down to the S5 state. The front USB port still is under current (tested with an bluetooth stick having an LED on it). I also have configued the power button using the GUI (not the flirc_util CLI tool). But still no luck. When I am on bash and I hit the power button on the remote the console returns "äääää", which tells me it receives some IR-code. But still no startup possible. Any other ideas? 

 

Where did you find a power button in the GUI? From what I can tell there is still no power button for Flirc-SE available in the GUI. You NEED to record a power button using flirc_util in CLI.

 

BTW: Where can I download the latest beta version of the firmware? I would prefer to upgrade via flirc_util, as my HTPC has no keyboard attached to it :-) 

 

It is available in the Development section of the forum: http://forum.flirc.tv/index.php?/forum/93-firmware-30/

 

Currently there's no way to upgrade from CLI. You need to run Flirc GUI somewhere. It doesn't need to be on the HTPC :). Just plug the Flirc to another PC and upgrade it. You also can program it on another PC and then you don't even need to have Flirc software installed on HTPC.

Link to comment
Share on other sites

I have configured the power button on my remote via the GUI (see attached screenshot). Is this the wrong way to do it? I will give flirc_util a try. 

 

[EDIT]

Tried configuring via flirc_util record power and then hitting the power button on the remote control. The CLI utility returns success. However my system is still not starting via RC. 

post-18310-0-47810300-1424113511_thumb.p

Edited by matze2ooo
Link to comment
Share on other sites

The power button on the XBMC controller is for exiting the XMBC itself. It has nothing to do with the PC power on/off.

 

Do you have suspend detection enabled in Advanced settings? It may be required in firmware 3.5 as in that version Flirc disables the power button when PC is powered on. Have you already tried upgrading to 3.6?

Link to comment
Share on other sites

Do you have suspend detection enabled in Advanced settings? It may be required in firmware 3.5 as in that version Flirc disables the power button when PC is powered on. Have you already tried upgrading to 3.6?

 

Does "suspend detection" refer to "sleep detection" when using the CLI tool? I have tried both enabling and disabling sleep detection using flirc_util sleep_detect enable | disable without luck. 

 

I haven't tried 3.6 yet... will do so tomorrow. Thanks again!

Edited by matze2ooo
Link to comment
Share on other sites

3.6 refuses to run on my Gentoo Linux system (x86_64). I don't see why... 

 

xbmc temp # ls -l flirc_util
-rwxr-xr-x 1 xbmc xbmc 3044045 Feb  9 22:52 flirc_util

xbmc temp # ./flirc_util 
-bash: ./flirc_util: cannot execute binary file 

xbmc temp # file flirc_util 
flirc_util: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, for GNU/Linux 2.0.0, not stripped 

xbmc temp # uname -va 
Linux xbmc 3.16.5-gentoo #1 SMP Mon Nov 10 21:55:33 CET 2014 x86_64 Intel(R) Core(TM) i3-4130T CPU @ 2.90GHz GenuineIntel GNU/Linux
Edited by matze2ooo
Link to comment
Share on other sites

I have switched the underlaying OS in the meantime to Ubuntu Trusty as Gentoo was too much work to maintain.

 

I just can' run the beta version on my 64bit Linux. Although it seems statically compiled I looks for several libraries. Here is the strace output. Can you provide a 64bit compiled version of the Flirc Beta utility?

    Quote

    Dynamic section at offset 0xe81324 contains 43 entries:
      Tag        Type                         Name/Value
     0x00000001 (NEEDED)                     Shared library: [libusb-1.0.so.0]
     0x00000001 (NEEDED)                     Shared library: [libstdc++.so.6]
     0x00000001 (NEEDED)                     Shared library: [libdl.so.2]
     0x00000001 (NEEDED)                     Shared library: [libXt.so.6]
     0x00000001 (NEEDED)                     Shared library: [librt.so.1]
     0x00000001 (NEEDED)                     Shared library: [libpthread.so.0]
     0x00000001 (NEEDED)                     Shared library: [libX11.so.6]
     0x00000001 (NEEDED)                     Shared library: [libXau.so.6]
     0x00000001 (NEEDED)                     Shared library: [libXdmcp.so.6]
     0x00000001 (NEEDED)                     Shared library: [libXext.so.6]
     0x00000001 (NEEDED)                     Shared library: [libXi.so.6]
     0x00000001 (NEEDED)                     Shared library: [libXinerama.so.1]
     0x00000001 (NEEDED)                     Shared library: [libXrandr.so.2]
     0x00000001 (NEEDED)                     Shared library: [libXrender.so.1]
     0x00000001 (NEEDED)                     Shared library: [libfontconfig.so.1]
     0x00000001 (NEEDED)                     Shared library: [libexpat.so.1]
     0x00000001 (NEEDED)                     Shared library: [libfreetype.so.6]
     0x00000001 (NEEDED)                     Shared library: [libglib-2.0.so.0]
     0x00000001 (NEEDED)                     Shared library: [libxcb.so.1]
     0x00000001 (NEEDED)                     Shared library: [libgthread-2.0.so.0]
     0x00000001 (NEEDED)                     Shared library: [libm.so.6]
     0x00000001 (NEEDED)                     Shared library: [libgcc_s.so.1]
     0x00000001 (NEEDED)                     Shared library: [libc.so.6]
     0x00000001 (NEEDED)                     Shared library: [ld-linux.so.2]


Edited by matze2ooo
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...