jason
-
Posts
3,758 -
Joined
-
Last visited
-
Days Won
233
Posts posted by jason
-
-
Jason,
The FLIRC that was on 2.3 started acting wierd then said "Boot Loader detected, can not update firmware, contact support" (wording may not be exact) I took it over to another machine and now the firmware is v3.0. I grabbed the 3.1 FLIRC and erased and reprogrammed it using an old Firefly Mini that I have and it's working again.
Dude, gremlins! I want to help you solve the problem because I really like the concept and they worked for me for six weeks flawlessly. If you want we can take this PM.
Chris
So yours is working?
-
I'm sure we can resurrect it. Traveling back home. I'll see what I can do when I return.
-
I tried 3 with no change in behavior, I changed it to 6 and no change. I reseated the FLIRC and the remote went completely dead. I brought up the learning software and tried pressing keys, nothing on the on screen keyboard lit up. I tried programming a key and it came back with Key already exists. I tried erasing the configuration and reloading it, the remote still acted dead. I tried a different remote, no change, both are Hauppauge 45 RC6 remotes. I then pulled it out and watched a show :) using an old remote and usb reciever I had. I plugged it back in and the remote was working again like it was before, keys getting stuck. I went back and read almost the entire thread here and found the entry about sequnce modifiers, I unchecked it and left the Interkey delay at 6 and everything seems to be working normally. I went back and checked the Interkey delay and set it back to 3 and noted that the sequence modifer was checked again, I unchecked it and looked again. Sequence modifiers was checked again. I left it alone and tested the remote, everything appears to be working properly.
Hope this helps in isolating the issue. If there is anything else I can do, please let me know. I will keep you aprised of any changes in the behaviour.
ah, interesting, and you're on 3.1?
-
Same problem also here with same setup. Interkey 0 and noise cancelling helped a bit, but often when pressing up und down the command is issued twice.
Latest FW 3.1 running with Fire TV profile.
Interkey delay is too small, need to crank it up to 3.
-
My FLIEC with the 2.3 firmware is doing it now too. It started after a reboot of the machine
Interkey delay should be at 3.
-
The way it works now, if you don't have a sleep button mapped, but still have sleep detection enabled, any key will wake the machine up. Give that a try and let me know.
-
Absolutely can, but before you do, try upgrading to 3.1. File->advanced, force firmware upgrade.
Then try again. If it's still the same, it's probably a really noisy source close by. Try turning off the lights or the TV, once they are recorded, it should work fine.
-
Some of those posts i've written are really getting old too :/
I like to think thread would make a good basic PDF... though it may need some updating.
But I completely agree with what Elrondolio says, the need for easy documentation is still required no matter how easy the product is. it used to be something I tried to do but alas in recent year work got in the way :(
CHRIS!!
I needed two exclamations because your user name has one.
-
Thank you for your reasoned and accurate reply, Jason. I want to again make clear that I'm not trying to attack either you or your very useful product. I find the Flirc to be a wonderful device that fills an absolute need in a lot of hardware situations where other devices are lacking. In no way do I believe you or your product is a total failure. Quite to the contrary, you've clearly designed a solid piece of kit that has great software that backs it up... if only it was documented. The fact that someone must rely on tooltips for even basic documentation and that even short (but useful) help for flirc_util commands must be found directly through flirc_util is the only issue I'm expressing. I've documented software and written manuals most of my career and I can't imagine that writing a twenty page manual would take more than a weekend. Documentation has a lifecycle that doesn't need to produce perfection at the start... it continues to improve throughout the life of a product in my experience.
I have indeed read through all of the articles you have on your troubleshooting page and find them well written and focused. I believe you've done very well with that online resource and it is a required and valuable one for any hardware or software product. I have also found some great information and clearly dedicated support that both you and some passionate users provide on this forum, again a resource that is implemented well and is, I believe, another of those required and valuable tools needed for any hardware or software product.
I've had no issue personally figuring out and using record_api as well as a few other of those useful commandline functions once I've dug in a bit. But I'm not the average user. This product absolutely needs a beginner and intermediate user's basic pdf manual that is easily downloaded right next to the software. One that steps a neophyte user (that this piece of hardware is mostly focused at) through the concepts of the product, not just its implementation (but that as well, of course). One that duplicates the help provided in the commandline utility in addition to basic usage guidelines. Somewhere for someone I recommend this hardware to begin at the first day it arrives in the mail.
I very much look forward to recommending the Flirc once again once that documentation lifecycle has begun. I'll certainly not be steering people *away* from the Flirc, but will focus my active recommendations only on the more advanced users I run across from now on, those who won't be frustrated with some digging as it stands. In the meantime, I'll very much be enjoying the use of the device in my own home.
Thanks again, Jason. Have a wonderful weekend.
Any interest in helping do documentation for compensation?
:)
-
I really appreciate the feedback. Thank you so much. I'll do better with the documentation, but I really have to say in defense, it's not quite as awful of a picture as you're painting. It really makes me sound like a total failure and the product should never be recommended again. The advanced settings are very poorly documented, you're absolutely right. But they were never really intended for use and have been added to compensate for very small variations that don't fit the norm. That's not an excuse, it's my fault, and I'll fix it.
record_api is a super advanced feature, and it's just going to go beyond someone who isn't comfortable reading the IEEE USB HID spec.I have no intentions of documenting that anymore than the help section of flirc_util:
usage:
record_api 'arg1 arg2' arg1 is key-modifier
arg2 is HID key
example:
flirc record_api 136 4 '136' represents right cmd + left cmd
'4' represents 'a' in HID
Key modifiers are defined in the IEEE HID Spec as follows:
LEFT CONTROL 1
LEFT SHIFT 2
LEFT ALT 4
LEFT CMD|WIN 8
RIGHT CONTROL 16
RIGHT SHIFT 32
RIGHT ALT 64
RIGHT CMD|WIN 128
For starters to help, I've put together a series of help articles here:
At every opportunity I have, I add an article. Most people just got to the forums or email me, because it's easier than searching. That's not something I can do much about.
If you hover over the advanced settings in the GUI, you get a tooltip describing what it is and what it does.
Ideally, I'll have some help contents right in the GUI, and it's just a matter of time before it makes it on my list of priorities. I've got a new product launching this Friday, and I'm terribly excited about it: https://twitter.com/flirc/status/535914395650383872
But thank you for the criticism, it's not unfounded.
-
raise the interkey delay in the Flirc GUI under advanced.
-
I've been following this thread religiously and there are two problems that can happen and the multiple people posting are either experiencing one or the other.
Flirc is essentially a keyboard, so consider
Problem
1) When you hit a key on the remote, one key is received on your machine, there is a delay, and then several keys are seen. Like if you had a keyboard and just pressed and held the button down.
2) When you hit a key, several keys are received rapidly.
These are two very different problems and users aren't distinguishing them here, and rightfully so, as the problem statement is too many keys are received.
So let's talk about the solutions we've figured out.
1a) If you have a harmony remote, lower the repeat value in the harmony software: in the remote, go to the troubleshooter and lower the value to 0 or 1
1b) if you don't, lower the interkey_delay in the flirc advanced software.
2a) raise the interkey_delay in the flirc advanced software
I think there is one more cause for 2, but I haven't determined what it is yet, I'm still working on it. It's going to require some special firmware that I started on.
I'll put a sticky at the top of this thread for others, this seems to be the solution.[edit by Chris: A separate sticky has been made to make the issue easier to find for those who may be experiencing it. Continue to discus it here though] -
No, I re-architechted the firmware to set it up to be easier, which was in the 3.x firmware. That also included much better support for other remote controls that always gave flirc problems.
I quietly released a second product:
http://www.streacom.com/news-item/introducing-flirc-se/
That's going to ramp up soon.
I have a third product that I pre-announced (teased): https://twitter.com/flirc/status/535914395650383872That's going to be released this coming Friday.
I need to try and get the website ready for the new product.
I also need to work on another version of firmware that captures the waveform from the remote so not only can I examine what others are seeing, I can reproduce it at home.
After that version of firmware, I'll continue on that feature. I assure you, it's not intuitive to make intuitive. The work I did already for 3.x was an enormous under the hood change.
Thanks for the patience. I'm sorry, I hadn't realized how tough this was going to be when I estimated and signed up for it. But it's on my list.
-
Open up the Flirc GUI, then go to the full keyboard, then pair your remote with the ones Rob has put above. For example, if you know which button you want as the home button, pair that button with escape. It looks like you also need to add the file Rob posted above and put it on your android in: /system/usr/keylayout/
I'm willing to bet that you need then go on your android, system keyboard preferences and select one called Vendor_20a0_Product_0001. But this is all a guess, I don't have an android TV. I'll try and put in better support in the flirc gui so you don't need to use the keyboard controller view.
-
I'm going to be tied up on planes for 10 hours. Shoot me an email at the support email address and I'll send you the old firmware while I try to figure out what to do next.
-
My pleasure.
Well at the very least I can get you back on the previous version. I'm certain it's something particular with the protocol. I just need to sit down and look at it. Go to advanced and do a force firmware upgrade. What is the bootloader.
Also make sure your not point the remote to close to Flirc. Point it up at the ceiling and see if that helps.
-
Well get it fixed. Hang in there I'm traveling. What kind of remote do you have?
-
I purchased my Flirc in May of 2013. Originally I planned to use it with XBMC, but about the same time I installed it - and it did work - I switched to Plex and a full wireless keyboard.
Now I have gone back to XBMC and would like to be able to use my Harmony Ultimate One remote exclusively to navigate. So, I dusted off the Flirc and tried to get it working.
Unfortunately, the Flirc is recognized by the OS (as a libusbK USB device) but the Flirc software does not see it. It simply says 'disconnected' in the bottom right of the software, and and says "Please connect flirc".
This is occurring after reboots, and on two separate machines.
The OS on both machines is Windows 7, 64-bit.
Suggestions?
Thanks for any guidance or help.
- Joe
are you on the very latest that's available on the website?
-
Yes, this will work. You can bind to any keyboard key. The keys you are linking to are system media center keys. The application doesn't need to be in focus and those will still go to the media application like itunes or whatever is playing the file.
-
So happy it's working better for you now. I'll make an article about this. Thanks so much and keep us posted.
-
This is it. I'm positive. I have the same trouble all the time. You can't point it at Flirc withing a foot when programming because the sensitivity is too high. When I do it, I aim the remote up at my ceiling on purpose for this reason.
It will have just gone from 'not sensitive enough' to 'holy shit how is this still working'
-
1
-
-
okay can you help me out.
What is actually happening.
Fire up a text editor, and press the button on your remote.Is it as if you were to take a keyboard, and rapidly press a button, or is it as if you were holding a button down on your keyboard, in which case, the button is seen by the computer, there is a delay, and then multiple keys are received.
-
Oh! Yeah, I've tried using a different remote. Of course lights are on, as is the TV.
I'm using my Apple remote to control Philips Hue lights, which I've written applescripts to control on my Mac. Thus, the Apple Remote triggers the lights via my Mac's IR receiver. I've had that setup for 18 months and it's been flawless. I bought Flirc because the Apple remote only has a few buttons, and I'd like to do more... but Flirc seems to need to have the remote be pointed directly at it, whereas the Apple Mini's IR receiver just needs the signal line to be clear regardless of whether or not the remote is pointed anywhere near it. And, again, since I taught my universal remote the Apple remote button presses, it's the same universal remote that I'm using with both Flirc (for some buttons) and the Mac Mini's IR receiver (with other buttons). In a perfect world, I'd just use Flirc for all of the functions, but Flirc seems very finicky in terms of receiving the remote signal unless it's pointed directly at it, whereas the Mac Mini IR receiver doesn't have a problem.
Moving Flirc to the other side of the room, where the TV/stereo/etc is would solve all of this. If only my Airport Extreme router allowed its usb port to work with usb keyboards, this would be so easy.
I got an idea.
Can you try clearing your config, sit on your couch, and do the records from where you will be using the remote. Maybe it will record a slightly less strong signal and it's hash will be more representative of what the signal looks like from your use case.
-
Sorryi mean have you tried another remote? Are the lights or tv on? If you turn those off does it get better? Maybe something is noisy
Keys stuck
in Firmware Bugs
Posted
Are you seeing a few rapid key presses, or does the key feel like it's being stuck held down?