Jump to content

ptr727

Members
  • Posts

    29
  • Joined

  • Last visited

  • Days Won

    3

ptr727 last won the day on May 11 2014

ptr727 had the most liked content!

ptr727's Achievements

Newbie

Newbie (1/14)

7

Reputation

  1. Hi, thanks for the Shield profile, I switched from a Roku to a Shield (no IR), and was pulling my hair out trying to get a MCE IR USB receiver working with a MCE profile in my URC MX-890 remotes. I used a Panasonic TC-P65VT50 as profile in Complete Control, and I programmed the shield profile and the media keys profile in Flirc. The time between presses was so slow, I changed the "Minimum Repeat When Pressed" to 1 in CC, reprogrammed, more bearable. Still much slower than the native remote, but the same situation with Roku where the native remote is fast, IR not so much. The inter key delay settings in the Flirc advanced UI is greyed out, don't know if there is another way to get keys to be more responsive? When I program the home button, it launches my default browser on my Win10 PC, looks like the programming key is passed to the PC? I was an early adopter of the first generation units, but gave up after I found them to be prone to interference and key-press loops, basically drove my wife crazy, who in turn drove me crazy. The new unit seems to work great so far. Anyway, just wanted to say thank you.
  2. The dimmer modules use simple forward phase dimming of the 120V AC signal, it is not a low voltage PWM dimmer, thus the interference will be at 60Hz plus harmonics. Even if the electrical interference were at or around IR modulation frequencies, then a well designed system will not allow crosstalk, i.e. noise on the power line will not interfere with signal on the processing line. This is no different to an audio amplifier, where with a well designed unit you will not hear AC hiss, but on a poorly designed unit you will hear the AC hiss. Given that electrical noise from dimmers and fluorescent lights are common in home environments, flirc should not be susceptible to interference from these devices. And to be clear, my observation is a correlation between dimming lights and the flirc not working, I did not investigate causation. P.
  3. After ordering replacement flircs, taping around flircs, using USB extender cables, nightly they still go wonkers. I do however now believe that the problem is due to susceptibility to electrical interference. At 10pm my home lighting control system dims the outside lights to 50%, at 10pm like clockwork the flircs start going crazy. I manually turn the lights off, flirc behaves, I manually turn the lights back to 100%, flirc behaves, I dim the lights, flirc goes crazy. Thus I highly suspect that the flirc has insufficient electromagnetic interference protection, and that electrical line noise is a cause of these problems. P.
  4. I've encountered this from time to time, even with fully up to date flircs. I found that after a "flir_util.exe format" I can again program the firmware.
  5. I ordered one new unit, I'll use it as a comparison, maybe something was bad with the batch of 6 I ordered April 2013. I also taped one of the flircs, leaving only the front open where my IR emitter is attached. We'll see what happens. Just difficult to come to a conclusion as the failure is so unpredictable. P.
  6. You mean that during recording of keys there were duplicates due to environmental noise, that recorded itself and then plays itself? I looked at settings, there are no duplicate entries, only the individual keys I recorded. Could it be triggered by heat during media playback the HTPC gets hotter and the flirc doesn't like that? I've seen posts here where people cover the flirc with tape to keep stray IR out, I could try that? P
  7. I'm experiencing similar problems. My Flirc would work all day, and then in the middle of the night suddenly go crazy, looks like a stuck key, only resolve is to unplug it. Plugging it back in it either keeps going crazy, or it does not work at all. I have 6 flirc's, happens periodically with two of them, one in a NUC one in a ZBOX, both in AV closets, both running openELEC, one v3.2 and one v4.0. Using URC MX890's and MRF350's, and programmed using the (recommended) Panasonic TC-P65VT30 profile. I've formatted, reflashed, reprogrammed them, same happens. I've swapped them around, same happens. 99% of the time late night, this time just now, around 11pm. I bought my flircs April 2013. Maybe they are all bad? Any ideas? P.
  8. Hmm, no cli folder on my machine using release installer? Using google I did find this: Is there is CLI for the released version? Where do I get usage instructions? P.
  9. I see mention of a commandline interface/cli in some forum posts, where do I get it, what does it do, where do I get documentation? Thx P.
  10. Hi, I meant that the default MCE and XBMC screen keyboard layouts could/should include these buttons. I.e. show all buttons that are commonly found on MCE style remotes, and automatically map them to the correct commands/keystrokes. E.g. MCE button will take you to main screen in MCE and XBMC, there is an explicit WM_COMMAND for that, or windows key + alt + enter. P.
  11. Hi, I'd like to program all my FLIRC's with the same setup. Does the file save and load automatically program the connected FLIRC, or is there a more obvious way to program the device? P.
  12. Hi, new FLIRC user, just received 4 units. I am trying to get reliable XBMC/openELEC control using URC MX-890 remotes. I am using Zotac ZBOX ID84 machines, they do come with USB IR receivers, but the URC Complete Control programming app does not include a standard MCE profile that works with the Zotac IR remote. I did learn program the remote, but its operation is unreliable, especially the play and up keys. I am trying to use FLIRC and as recommended in the Harmony Remote thread, I am using a Panasonic TC-P65VT30 remote as template. Seems to work ok, but I am missing a few useful buttons that are present on the Zotac MCE remote, and most other MCE remotes. MCE button: Go to XBMC / MCE home page. Power on button: Wake the machine from sleep. Power off button: Put the machine to sleep. Context button (c key): Context menu. Info button (i key): Item info or OSD info OSD button (o key): On screen display and diagnostic info I did see the two threads on power commands, but since openELEC/XBMC and Windows MCE work out of the box with the MCE remote power on/off buttons, I'm wondering if it is not possible to implement whatever native power wake/sleep commands are already supported? Thx P.
×
×
  • Create New...