Jump to content
Flirc Forums

spoyser

Members
  • Posts

    12
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by spoyser

  1. Version 1.0.1 is now available, if you have the repository installed this should update automatically (depending upon your XBMC settings)

     

    32bit XBMC on Macs, and 64bit on Linux should now be supported.

  2. I am using openelec x86_64 v3.0.6 on an Intel Nuc unit with a Celeron 847 1.1 ghz processor. Here is the link to the XBMC log file:

    http://xbmclogs.com/show.php?id=35931

    and you will notice that the generated libraries path is Linux/86_64/libflirc.so not Linux/i864/libflirc.so or any other valid libraries path as I had supposed above. Can I just create a 86_64 dir and copy the i864/libflirc.so to it?

     

    Many thanks for that, yes can you try creating that folder and copying the libflirc.so file into it, please confirm if that works and we can update the plugin.

     

    If that doesn't work is there any chance you could try try a 32bit version of OpenElec?

     

    I assume the udev location is fine then if that is what the documentation states, thanks for finding that out.

  3. Thanks for the information provided that may have helped.

     

    Given what you have said about the file ending up in the wrong place suggests you may not have been logged in as root, can you confirm this?

     

    Can you also post a copy of the XBMC log so we can see where it is actually looking for the library files.

     

    Also, what hardware are you running it on?

  4. Jason has recently updated the readme with some instructions but basically you need to create a UDEV rule in order for XBMC to write to the FLIRC device  (you just gotta love Linux!).

    To do this you must create a file called 51-flirc.rules in the directory etc/udev/rules.d/

    This file is simply a text file containing this:

    SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0666", GROUP="pi"


    You must be the root user in order to do this.

    You will also have to reboot after this.
  5. Seems okay here,

     

    volume up maps to '='

     

    next chapter maps to ']'

     

    Can you look in the script.flirc/resources/language/english/strings.xml file and post the values for these strings:

     

        <string id="2029">Volume Up</string>
        <string id="12029">=</string>
        <string id="2044">Next Chapter</string>
        <string id="12044">]</string>
  6. If not already, insert Flirc into USB of PC on which Flirc GUI software is installed

    Navigate to flirc installation directory, in Windows XP this is normally C:\Program Files\Flirc\

    In there, there is another directory called cli change to this directory (cd cli)

    From this directory you can run the command line program flirc.exe

    You can check the flirc is recognised by entering

    flirc.exe version

    To change the sensitivity enter

    flirc.exe sensitivity 0

    (as I said in previous post, 0 seems to work fine, you could try other values, 3 didn't work for me)

    If successful you will get a message about having to reprogram the device, TBH I'm not sure if that is actually necessary so try the remote first to see if it works, if it doesn't reprogram it via the GUI

    Alternatively, from the Run menu:

    "C:\Program Files\flirc\cli\flirc.exe" sensitivity 0

    (make sure you put the quotes in the right places)

    HTH

×
×
  • Create New...