jason
-
Posts
3,732 -
Joined
-
Last visited
-
Days Won
229
Posts posted by jason
-
-
After I made that post I did somre work with it and got it to work. Here is what I did.
- Used the Flirc software to set the delay to maximum as indicated above.
- I also deselected all the other options that were preselected. (I think these were XBMC & the Harmony ones)
- Using the Harmony software I set the remote as indicated in one of your links above.
After making these changes the Harmony/Flirc combination works fine now. While I did the programming of both devices on a Win 7 computer, the Flirc is actually installed in a small scratch built HTPC running Mythbuntu 14.0x and only acting as a frontend. It's an I3 with dedicated Nvidia GPU so there is no lack of mips here for what it does.
I should have spent more time with it before I made the post above so my apologies for the false trouble report.
No apology necessary, and I apologize greatly for any frustration or confusion. My product is supposed to take any of that away, so I feel at a great loss when someone gets stuck or struggles.
So do you think it was the options in the advanced configuration? Any chance you can tell us what that is? (may help others) perhaps, 'sequence modifiers' was selected, and that can definitely cause problems.
Thank you for following up.
-
We really need to get a profile sorted out for playstation 4. Even I don't know what to do with command line stuff (I'm not a tech person)
Okay, sounds good. Chris, I'm going to have free cycles soon. Can you help put together a new sub forum for playstation 4 keymappings? Let's compile everything there, and I will update my GUI.
-
There won't be any issues. We tested a few weeks ago. While the chip is a little bigger, the heat sink will do as its intended. The hot spot won't be at the end of the chip.
-
1
-
-
One just arrived, a rosewill, doesn't work. = (
-
I could solve this in an hour if I had a F$@$n remote that works.
I've bought so many media center remotes on amazon that come with a dongle, none of them work. Some error that says do not initialize.
-
How can I tell what bootloader they are? I the first one I purchased is probably 2 years old or more and the other 3 are maybe 18 months.
I'm using Linux. I removed the FLIRC, closed the software, then reinserted it and restarted the software again. It now sees the FLIRC again. I forced a FW update and it completed properly. I cleared the memory and recorded keys onto it. It was not as easy as the other one I just did. Lots of glitches with it not remembering buttons again like in my original post. And same symptoms when used with XBMC.
Oh well, at least one is fixed except for the delay thing. If I leave the delay at 6, that is the worst setting for scrolling through big lists. I could grow a beard while I wait to get from the A's to the Z's. It's still slow at a setting of 2 but at least I can control the rest of XBMC without false clicking everything in sight.
Thanks,
RLW
any chance you can show me a video of it scrolling?
I'll send you a new one. pm me your address.
-
Further to my last post, I rebooted my computer and then the FLIRC software could see the FLIRC again. But it was acting weird so I tried to force a FW upgrade. I failed partway through with this message "Could not upgrade firmware. Contact Support".
Thanks,
Robert
you catch the fw version?
-
okay, I'm really glad it's not my algorithm. I'm making a 'few' in manufacturing right now and was about to lose my fucking mind. Excuse my language.
Okay, so the scrolling thing is going to be definitely new. I'm detecting key presses differently now, which helps a lot with noise. Now it's just timing. Keep your interkey delay at 6. Let me know what that 'feels' like. I will be making a release soon which has a more appropriate default.
Any chance you know when you bought your devices? They shouldn't brick, unless you are on windows (in which case we can recover from this), or if you have a very old device. Bootloader 1.2 or so.
-
sorry, I apologize, I noted above I got my threads crossed. Your description was very good. Please see my latest reply.
Flirc is really sensitive. When you record, point it up at the ceiling, otherwise you'll get these results.
Yes, we can revert, but I can't revert for select people without solving the problem. I have too many devices out and my old algorithm wasn't good enough to cover every remote. I need to adapt my new one to cover yours.
-
when you record your keys, make sure not to point the remotes directly at flirc, you should be a good distance away. There is no reason that remote shouldn't work.
-
can you be more descriptive? What is going on?
Do you get double presses every single time? Do you get them occasionally?
Edit: ** sorry, I'm getting mixed up with threads **
-
what kind of remote are you using?
-
The problem does indeed exist with the Harmony 650. I have 3 of these and 3 Flircs. All were running 3.0. When I upgraded one of the Flirc devices to 3.5, it became practically unusable. I did change the delay as indicated on the Flirc to the maximum value, which impoved things a bit, but it's not perfect, double clicks about 1 out of 15 times now, and now the entire setup is pretty sluggish compared to the other two HTPCs.
If I could downgrade to 3.0 I would, but after seeing the commentary in this topic, I'm rather afraid to try it as I don't want to end up with a completely non-working setup.
Can you give me more info? What are you running this on? What kind of remote are you using? Is the only problem double clicks?
-
The think is that this is my first time using the Flirc GUI to program my remote. I originally set it up using Logitech's software. After deleting some drivers I found Flirc GUI to be the only way to use my remote.
It's not really a bother considering I can program it to the way I had it with Logitech's Flirc profile, but can anybody tell me why I can't use the Harmony software anymore?
make sure under file->advanced 'built in profiles' is checked.
-
If you upgraded from firmware version 2.x to 3.x, re-recording all the buttons is a mandatory step.
Jason, I think that some warning should be added to Flirc GUI so when it detects that user is on 2.x firmware then it informs the user about that before proceeding with the upgrade.
I do only on the advanced configuration. I will do this on the startup routine too.
-
Hey Jason, were you able to look at the screenprint attachment I sent after my post above?
It seems all the posts regarding this subject on various forums end without a resolution. Again, is it even possible, with the use of the flirc and the command line to turn on a PS4 from standby and exit programs like Netflix and get back to the PS4 home screen???
At this point, the flirc hasn't allowed me to do anything a standard keyboard won't do, and I don't need a flirc in the chain between my universal remote and PS4 when I can learn keyboard commands.
I must have missed the request or the like.
I don't have a PS4, so I really have to rely on the community to help out.
Chris helped put this together after various users input: https://flirc.zendesk.com/hc/en-us/articles/203167509-Setting-up-Flirc-with-PS4
Are you missing the shortcut in that gui?
Do you mean that no key is able to wake up your PS4 in suspend? That shouldn't be the case. Are you on the latest firmware?
-
The problem does indeed exist with the Harmony 650. I have 3 of these and 3 Flircs. All were running 3.0. When I upgraded one of the Flirc devices to 3.5, it became practically unusable. I did change the delay as indicated on the Flirc to the maximum value, which impoved things a bit, but it's not perfect, double clicks about 1 out of 15 times now, and now the entire setup is pretty sluggish compared to the other two HTPCs.
If I could downgrade to 3.0 I would, but after seeing the commentary in this topic, I'm rather afraid to try it as I don't want to end up with a completely non-working setup.
what's sluggish? You are referring to the harmony?
-
try going to file->advanced and disabling built in profiles
-
Can we do a team viewer session?
-
let's connect again when you are home. We'll figure it out.
A good test would be to plug it into another computer with none of the flirc software on it. It should just work. -
I am running Kodi on a Windows 8 machine, and use a Harmony Smart Control to navigate. After working fine for several months my Flirc seemed to stop receiving commands. Any button press was ignored. The receiver also failed to receive commands when in Windows' start menu. I used to use it to enter my PIN to login, but now that won't even work so that tell me it's not a software issue, at least not related to Kodi.
I reinstalled Windows, and that was of no help. I used the Flirc utility to upgrade the Flirc firmware to 3.4, that didn't help. I used Zadig to upgrade the driver to libusbk 3.0.7.0, but that fixed nothing. Last time I had a similar problem I fixed it by downloading libusb1.0.dll and placing it in my syswow64 folder, but I already tried that again and it didn't help.
What can I do?
Edit: The Flirc software does state Flirc is connected, and I'm able to record commands. I tried programming a universal remote, and I was able to record commands, but my computer fails to receive the commands.
make sure in device manager, you only have 1 libusbk device. There are two interfaces on flirc, interface0 and interface1. Interface1 is libusbk, interface0 is supposed to be the windows HID keyboard, if you accidentally replace that, the keyboard wont work
-
OK solved it...
That was the exact symptom I had, but doing the above didn't fix anything.
As mentioned in another thread, THIS is what you have to do: https://flirc.zendesk.com/hc/en-us/articles/200712568-Logitech-Harmony-Remotes
Setting up the Flirc profile in Harmony software resolved all the strange issues I was having. Basically I replaced my old "Media Center PC" profile with a new "Flirc / XBMC" profile.
Doesn't fix the inherent harmony remote lag, but it actually is the snappiest I've seen it so far, so seems good to me. Not sure what triggered off the difference between 3.4 to 3.5, but glad it is resolved now.
I've spoken to the harmony guys, it's built in. (the lag)
-
Yeah, I can not reproduce this with the harmony, or the harmony profile.
However, I can reproduce this with other remotes. I will be following up with the firetv team, the problem seems to be on there end. -
I will incorporate this feature. But I wont be free to do so for 3-4 weeks.
FW Update -> Poor Results
in Firmware Bugs
Posted
glad it's working, I'll get the bum unit replaced. Please keep me in the loop and try and see if you can come up with the reason why it doesn't 'feel' the same. I really want to solve that. Thanks for the help and patience.