Jump to content


  • Posts

  • Joined

  • Last visited

Godzilla's Achievements


Newbie (1/14)



  1. "File | Upgrade Firmware" did not work, because the software wants me to select a FW file. But "File | Advanced | Force FW Upgrade" works! I am now on v3.9.0 Thanks.
  2. I just pulled an old original Flirc device out of my drawer and would like to update the firmware. The device connects to the GUI (Win10) and says the firmware is v1.0.0. I cannot find a download for a newer (or any) firmware. All "firmware download links" point to https://flirc.tv/downloads But there is only the GUI software. :(
  3. I have XBMC installed on my Win7-system. Using the command line would be possible of course. :) To be frankly, I am too lazy, because everything is working fine, now.
  4. Here is how you switch between two monitors (e. g. TFT and Plasma TV) with one click on my remote. my setup: Win7 desktop TFT-monitor (DVI) Plasma TV (HDMI) First you download and instell a little commandline-tool called "Display Changer". http://12noon.com/?page_id=80 Then let Display Changer list the available monitors dc64.exe -listmonitors The current monitor is "\\.\DISPLAY1". (I am not sure, but it seems Display1 is always the current one. Otherwise my script would not work.) So, what we want the script to do, is to set the second dosplay as acive and deactivate the current one. And we don't want to keep the current resolution (1680x1050 px) since the Plasma TV is FullHD (1920x1080 px). Instead we always want to use the native (read maximum) resolution. (same for colordepth and refreshrate) So we need one command to set the second display to be the primary one. (DisplayCharger is able to configure and arrange many monitors at the same time) dc64cmd.exe -monitor="\\.\DISPLAY2" -width=max -height=max -refresh=max -depth=max -primary And another command to disable the current monitor. dc64cmd.exe -monitor="\\.\DISPLAY1" -detach Display Changer is able to "remember" the first command and executes it not before we told it all our commands. So we add "-more" to the first line and "-apply" to the second. (This may be bad english. Sorry.) My final script looks like this: cd "C:\Program Files\12noon Display Changer\" dc64cmd.exe -monitor="\\.\DISPLAY2" -more -width=max -height=max -refresh=max -depth=max -primary dc64cmd.exe -monitor="\\.\DISPLAY1" -apply -detach Just save it as "switch_monitors.cmd", so you can doubleclick it to try it out. Everytime you execute the script the other monitor should become the active monitor. To execute this script by pressing a button on your remote, you first need to create a link to the script on your desktop. To create a link you just drag'n'drop the script while holding the ALT-key. Right-click the shortcut and select properties. Click on the field next to "Shortcut" and press your preferred key-combination (e.g. Ctrl+Shift+M) (Can anyone provide an english screenhot?) Click OK and try out the new hotkey. :) The last step is to map a button on your remote the the selected key-combination. I think you know how to do that. Good luck. advise: Use dc.exe if you don't have a 64-bit system. Remember the options you get when you press Win+P With this hotkey (and direction-keys and enter) you are able to switch the monitor arrangement blindly. In case you get two black displays. ;) Add "PAUSE" to the end of the script to see any errors while testing If you know a better way for switching between two monitors, let me know. I am not responsible if anything bad happens! Do it at your own risk!
  5. Here are my custom keyboard.xml-entries. Maybe this is helpful for someone.. <f1 mod="ctrl">XBMC.ActivateWindow(MyVideoLibrary,movietitles,return)</f1> <f2 mod="ctrl">XBMC.ActivateWindow(MyVideoLibrary,tvshowtitles,return)</f2> <f3 mod="ctrl">XBMC.ActivateWindow(music)</f3> <f4 mod="ctrl">XBMC.ActivateWindow(settings)</f4> <f5 mod="ctrl">XBMC.updatelibrary(video)</f5> <f6 mod="ctrl">XBMC.updatelibrary(music)</f6> <f7 mod="ctrl">XBMC.Quit()</f7> <f8 mod="ctrl">SubtitleDelayMinus</f8> <f9 mod="ctrl">SubtitleDelayPlus</f9> <f10 mod="ctrl">AudioDelayMinus</f10> <f11 mod="ctrl">AudioDelayPlus</f11> <f12 mod="ctrl">AudioNextLanguage</f12> <f1 mod="alt">PrevLetter</f1> <f2 mod="alt">NextLetter</f2>
  6. As I mention in this Post (), it seems the Samung-profile has duplicate buttons. The colored buttons red, green, yellow and blue have the same functionality as the buttons "a", "b", "c" and "d". Can anybody confirm or disprove this?
  7. I think I found the problem. As I mantioned before, the color-buttons ware the diffucilt ones. I mapped now everything exepct these buttons. Then I started to mapping the color-buttons. But the GUI said "already existing". So I deleted these buttons/frequencies to mep them correctly. But I had to do the erase-routine many times till I could finally map the first color-button. Even the GUI told me erasing was complet. As I figured out later, It seems the GUI was deleting my previously mapped button in chronological order!! :huh: Anyway, I had to remap my first 14 buttons! The GUI was fine and didn't say anything about "already existing". These Buttons were definately ereased! But the orogin of the problem is that the Samsung-profile seems to have duplicated buttons. The colored buttons red, green, yellow and blue have the same functionality as the buttons "a", "b", "c" and "d". I wonder why nobody noticed this before. :blink: So, problems seems to be solved for me. But I still think there is something wrong with the erasing-process.
  8. It only occures when I am pressing a button mor than one time. But two times is enough sometimes. My Harmony lights up wehen sending a signal, so I can assure you the signal is not repeated by the harmony as many times as flirc does send commands.
  9. This might be the last of your problems, but I would really like to see an icon for the flirc.exe file. :) It's just ugly in the Win7-Taskbar. :)
  10. This sounds like my problem. I will try this, but its hard, because I barly get a connection. :( Besides I already on FW v1.0. EDIT: FW-(Re)Update sucessfull. Will report further problems. EDIT2: I cleared the Config and remapped some buttons. Just the Direction-Buttons and Red and Green, to reproduce my previous problem. Everything worked fine, regarding the mapping. But now I got another issue. When I hit DOWN on the remote in XBMC Flirc semds many more Down-commands than my Harmony sends. And while I am writing this, Flirc seems to send a bunch of "ENTER/RETURN"-commands every now and then. (I mapped this key, too) There really is something wrong!! :(
  11. In case anybody is searching for a usb-extender to place the flirc-device next to his hi-fi-devices I recommend the Logitech USB-Extender wich comes with many of their keyboards and mice. Maybe you recently purchened a Logitech device and still got the extender in the packing, like I did. :) The benefit of this extender is the foot wich holds the flirc-device slightly up and gives it a good stand http://www.logitech.com/en-gb/349/4872 (search for "PN 993-000293")
  12. I suggest a bug(/feature request) tracking system. :)
  13. Flirc ist behavoring strange. I was programming my device. I tested it successfully a few times while I was programming it. Then I was programming the color-buttons on my Harmony 555 (using the Samsung TV-profile). I selected the key "Ctrl+F1" and pressed the red button on my harmony. The Flirc-GUI said the Button already exists. Same with "Ctrl+F2" and the green button. Because I have had already problems with this buttons, I startet XBMC to see if the prior buttons still work. Result: DirectionLeft and DirektionRight (ArrowKeys) didn't work anymore. But the red and the green button now had the funktion of "left" and "right". I saved the configuration: XBMC_20120520-1821_neue_ordnung_naja.zip Then I plugged out/in the device just in case this would make a difference. The GUI shows "connected". As soons as I hit any button on the remote the device gets disconnected. Somestimes it even connects just for a second befor the connected gets lost again. (without hitting any button). My USB-Hub doesn't show a green LED after the connection gets lost. I tried all my USB-Ports. It has worked the last few days without problem. (so USB-Port and Hub are not the problem, I think)
  14. Got the same problem. Needed some time to find out USB3.0 was the bad guy. :) Maybe this should be mentioned in FAQ or something. Anyway, great device!!
  15. I just got my FLIRC. Any new information about this idea?
  • Create New...