Jump to content
Flirc Forums

NJKA

Members
 View Profile  See their activity

  • Posts

    10

  • Joined

  • Last visited

  • Days Won

    2

 Content Type 

Posts posted by NJKA

  2. Minor descrepency

    in Firmware Bugs

    Posted

    Firmware: 153 aka fw_wake.bin

    Flirc Version 1.0.3

    Remote Harmony 885 (Using Samsung profile posted elsewhere)

    System Windows 7 x64

    Problem:

    No real problem per say but the def value for sensitivity is not correct or the format command is not setting the def sensitivity value correctly.

    Steps:

    From the Flirc.exe commandine type

    flirc.exe sensitivity 99 (used 99 on purpose so it outputs the info about the specified range/def value)

    Output result:

    invalid sensitivity specified, range[0-3], def 3

    Note the def 3 value.

    Now do

    flirc.exe format

    Once the format is complete do:

    flirc.exe sensitivity

    Output result:

    current sensitivity: 2

    Now this can be interpreted two ways, either the def 3 should actualy read def 2, or the format command should be setting the sensitivity to 3 and not 2.

    Like I said at the start, not a major problem, but a bug none the less.

    Also...just found another bug

    type:

    flirc.exe sensitivity help (to see if there was any help availible for the sensitivity command)

    Output result:

    sensitivy set: 0

    You must re-learn your remote buttons with every different sensitivity

    Thus invalid sensitivity values, result in setting the sensitivity to 0

    Expected result.

    Either some help info displayed; else the same error result from using flirc.exe sensitivity 99

    Regards

    Neal

  3. error: no space on device

    in Firmware Bugs

    Posted

    Firmware: 153 aka fw_wake.bin

    Flirc Version 1.0.3

    Remote Harmony 885 (Using Samsung profile posted elsewhere)

    System Windows 7 x64

    Problem:

    Getting "error: no space on device" using Flirc.exe from then commandline

    Steps:

    flirc.exe record wake or any other button, only in this case it was the wake key

    Output result

    Succesfully recorded button

    Test the command using the remote, nothing.

    so usualy I repeat the command flirc.exe record xxxx until i get an output result of:

    error: button exists

    Then I know it recorded ok.

    However doing this today resulted in

    error: no space on device

    What it looks like, is that the Flirc is *maybe??* recording a slightly different remote signal every time, thus filling up the internal memory.

    Attached is my config file, if that's of any use.

    Thanks

    Neal

    nospace.zip

  4. Double Key Presses

    in Firmware Bugs

    Posted

    Another option is to adjust the "Keyboard Properties" "Repeat rate" setting.

    From the Windows 7 Start menu type "keyboard" and select "Keyboard" under the "Control Panel" group

    In the "Keyboard Properties" dialog that appears adjust the "Repeat delay" & "Repeat rate" sliders until the problem goes away.

    Note this dialog effects all Keyboard Devices attached not just the Flirc device.

    You may also experience this problem with Harmony remotes depending on what your "Inter-key Deley" delay is set too.

    Neal

    Introducing Flirc Utilities

    in Developer Lounge

    Posted

    Attached is a small program that contains a set of functions to help test your flirc settings, and also adds a few other useful features.

    capturecw.png

    First up, a couple of notes

    It's designed to be viewable on a 10' display hence the slightly larger than usual font size.

    The app will start minimized, as it's designed to run on a HTPC and be hidden once setup. (unless you run with /nomin arguments)

    System requirements

    Windows 7, or possibly Windows With .Net Framework 4.

    All my testing has been done with Windows 7 and MCE, however the porgram uses no specific hooks into MCE so it should in theory work with other Windows & HTPC setups such as XMBC.

    Features:

    • Supports registering HotKeys for:
    • Putting the HTPC into sleep.
    • Restarting MCE (or XMBC etc) if it becomes locked up/non responsive. First tries to polielty close the application, if that does not succeed then the process is killed and then restarted.
    • Showing/hiding the desktop icons and the windows taskbar. This is not working 100% as the taskbar can reapear... known issue. This feature is really to try and create a slicker HTPC experiance so when switching between external applications you never ever see underlying OS's desktop, icons or the taskBar. On my setup I've also changed the desktop background to match Media Center which also helps with this illiusion.
    • Numeric to Alpha key input. So using your remote controls numeric keypad you can now type charaters. Works like texting on a phone. For example press 2 twice in quick sucession and the "a" key is sent rather than 2. You probably won't be able to write emails etc. At least wouldn't :-). But it can be useful for navigaing large music or movie collections. i.e. pressing 8 twice takes you the albums starting with T
      • Kylo browser support. Kylo is a browser designed for TV's.....Except they want you to use a Keyboard or buy thier loop thingy....not any more!

        This remappes the standard Standard Media Center Keys into mouse messages or the limited shortcut keys Kylo uses.

        Up/Down/Left/Right
        keys get remappd to mouse move messages, so you can use your remote to move the mouse pointer around.

        PageUp PageDown
        keys remappd to MouseWheel messages

        Enter
        key gets remapped to the left mouse down.

        CTRL+G
        key get remapped to CTRL+H take you back to the Home screen.

        CTRL+F, CTRL+B
        keys get mapped to browse back/ forward.

        Plus more.

        In theory it's possible, in future versions to expose this remapping so that the remote can be remapped to any other user defined keys on a per application basis.
        • The Key Events tab is for testing that your remote is behaving exactly as you intended, and is sending the keys you expected. (easier said than done)

        Here what you see is what you get. There is very little code between what you see and the program recieves. This is so that you can be sure there is nothing in my code that is interfearing:-) The only thing I do to the messages I get is use an helper method to convert the key code into a more readable form, for example so key virtual key with a value of 32 becomes "Space". You may see what you think appears like incorrect keys such as oemperiod or oemcomma. This is normal and correct.

        [*]The Check List tab is a very basic check list of all the keys on a Harmony Remote. So you simply press the corrisponding key on your Harmony Remote and it displays the Key mapped to it, and then moves to the next button for you to test and so on. If two keys are mapped to the same Key combination the keys are highlighted in red. This Can happen if the remote profile has different commands that output the same ir code.

        [*]Support for showing an on-screen refresh rate change notification. When the refresh rate changes the app will briefly fade in and out a small alpha blended banner showing the new refresh rate. . Some TVs may do this for you. My Pannasonic TV does not, hence this little helper. Useful for knowing when TMT is playing a movie at 24p or not.

        In order to display the flirc version and firmware versions the commandline file flirc.exe must be in the same folder as this app.

        Hopfully this may be useful to someone.

        Neal

        FlircUtilities.zip

    • Like 3

    Api for reading recorded keys

    in Developer Lounge

    Posted

    Any chance of adding a "recordedkeys" (or similar) to the api, to list all the currently recorded keys?

    i.e.

    flirc recordedkeys -->

    136 4

    8 52

    etc.

    I would then be able to write a utility map these HID values to there virtual keycode and then into human readable values such as space control alt etc.

    On another note do you have a complete list of the supported HID key values?

    Many Thanks

  7. Cannot Delete/Erase Command

    in Firmware Bugs

    Posted

    Attached....Hopefully :)... need to always use the Add to Post?.

    my_flirc_configbad.zip

    The 153 firmware version was the fw_wake.bin. I saw that before the official firmware page.

    Now switched to the official version from here http://blog.flirc.tv/?page_id=46.

    However I've noticed that the Version 1 firmware also has the record wake command, yet on the page at http://blog.flirc.tv/?page_id=46. you say this is not availible until Firmware 1.1!

    What is the current status of the sleep issue?

    My computer will wake from sleep fine using any key via a standard keyboard when entering an S3 sleep state.

    But I need to use the "special" record wake command with flirc.

    If I use the following from the commandline

    powercfg -devicequery wake_from_s3_supported

    The list does not show either the flirc device or an additional HID Keyboard device (only the HID Keyboard device for the normal keyboard.

    Another observation is that the Keyboard device for the Flirc has no Power Management tab in Device Settings.

    So it would look like, currently the Flirc is not registering it self to be an S3 wake supported device. Is this correct?

    Cheers

    Neal

  8. Cannot Delete/Erase Command

    in Firmware Bugs

    Posted

    Hi, I have a Harmony remote, which has two keys mapped to WinKey+Alt+Enter (Windows Media Center Start/Home)

    I have tried deleting the combination using Erase in the GUI and the delete command from the CommandLine, Both methods report they succeeded, however the mapping does mot get deleted.

    Attached is the config file if that is of any use.

    Using the Samsung Romote profile on a Harmony 885, under Windows 7

    Firmware version 153

    For the time being I'll just just format the device.

    ........

    Just tested the offending Key combo again after formatting and it deleted it fine this time, so maybe there is something in the coinfig file that may be useful for you.

    PS..

    Would be nice if the user saved config file was a readable xml file with entries for each mapped key, that way with problems like this, we could simply go in and manualy delete the offending xml keys, and then reload the file.

    Thanks

    Neal

×
×
  • Create New...