jason
-
Posts
3,736 -
Joined
-
Last visited
-
Days Won
229
Posts posted by jason
-
-
I'm working on a debug mode to help with this exact thing, but it seems like the tivo remote is just extremely slow. I'll try and pick one up if I can't finish my debug firmware.
-
Definitely upgrade to v3.3 firmware.
That should fix it, much improved algorithm for noise rejection and false signals. You'll have to re-record buttons.
-
-
Hi,
I am new to this forum and read through the topic, but it seems that my question has not been addressed yet. Sorry if I have overlooked it.
I got everything setup and running. The only question I am having is:Is there a way to get the Harmony one to reboot the AFTV?
I tried setting up a custom sequence but no luck there.
Thanks
Paul
if there is a keyboard combination that does this, it is possible, otherwise no one has figure out what that combination is yet. You can hook up a keyboard and try and figure it out and then I can create a shortcut in the firetv menu of the flirc gui.
-
Unfortunately, with current Flirc possibilities, you can't access keys from HID Customer usage table with codes above 0xFF. Each recorded button takes 6 bytes: 4 bytes for IR code hash and 2 bytes for the HID code. To use codes from Customer usage tables the second byte must have value of 102 (decimal) so you only have a single byte for key code. To address 0x224 you would need 2 bits extra.
I think there are 2 possible ways (both require changes to firmware and software):
1. Extend structure from 6 to 7 bytes to allow bigger code space - this unfortunately would mean that the capacity would drop (from current 169 to about 144 from a quick calculation) but I think it would be a waste of space because there are not so many usage cases for those codes (so in most cases the additional byte would always be 0) - this requires changes to both firmware and software.
2. Add extra markers like the mentioned value 102 (0x66). There is for example a key code 101 (0x65) - Keyboard Application - I don't think there are any usage cases for this key to be used with Flirc. Using this value as a key code could send a key from Customer usage table with code 0x100 + modifier value. There are also F13-F24 keys that, at least on Windows are not usable anyway, so their codes could also be used as more markers to bump the value higher. To sum it up:
- For key code 0x66, send modifier value as a key code from Customer usage table,
- For key code 0x65, send modifier value + 0x100 (0x100 to 0x1FF range) as a key code from Customer usage table,
- For key code 0x73 (F24), send modifier value + 0x200 (0x200 to 0x2FF range) as key code from Customer usage table.
With values from above proposition you would be able to record AC Back button using:
flirc_util record_api 36 115
It all depends on whether or not Jason can/want to implement this. This also only require a change to the firmware. No software changes would be required.
Have we confirmed that it actually is the browser back button that is the missing key? Looks like Chris just threw it out there and no one really confirmed it.
I'm willing to do it, in fact I'll try this right now, but would love a bit of reassurance.
-
any news on this???
Sorry, I'm trying to catch up.
Can you upgrade to firmware version 3.3?
-
Nope. Doesn't matter. I should clarify somewhere. Your the second to ask uncouple days.
-
Yeah usb org needs to update my vendor name which will make its way to Linux.
Make sure enable sleep detect is enabled in the GUI. Any key will then wake the machine. If you record the wake key, then only the wake key will wake the machine
-
when you are recording, record the same button twice in a row. You might be using a remote that alternates signals on each consecutive press.
-
So it seems like there are a few issues with the firetv. I don't have any problems with mine. Although I'm using plex. Let's work together.
Plug a keyboard in your firetv, and let's see if we can figure out what the keyboard keys are for the desired functions. I'll get the GUI updated as soon as possible once we've identified the correct keyboard keys. I'm booked until saturday, then I'm back on flirc. -
I just got in a Flirc from Amazon, and I'm trying to set it up to use my FiOS remote. Everything was working perfectly for about 5 minutes, until I made the dumb mistake of updating the firmware. Now, the unit will not program any buttons correctly. It seems to be clearing the configuration correctly, because the command line says 0 buttons programmed. However, when trying to record buttons using the GUI, it doesn't work. It will record the first button correctly (up), but when moving onto the next (left), it says "Button already exists". No matter how many times I clear the configuration, it still says the same thing. I can manually erase the buttons, but even when doing that, the buttons all seem to have the same action. If I program up first, everything goes up.
It seems like the firmware update messed up the Flirc, because I can't think of anything else that I did between it working and it not working. Please help.
can you snap a picture of your fios remote for me? Also, just shoot me an email at my support address and I'll give you a new firmware image. I need a remote like this and I can update the firmware.
-
All you need to program Flirc is Flirc software and hardware on the same machine :). And yes, you are reading it correctly. You can program Flirc on one machine and then just plug it in on another and it will work. Flirc software is only needed for programming. It's not used in normal day to day operation.
There is a nice solution for building on multiple distros but it is based on virtualization. It is called Vagrand. It supports multiple virtualization apps but Virtualbox is most popular. You create a config file (contains name of base system image for example) and you can add a bootstrap file which is called on first boot to install all that is needed for the task. After that you just call vagrant start in the directory where the config file is and it clones the base system image, starts the machine in headless mode (so no window with virtualized OS console) and if this is a first boot it runs bootstrap script. After that you have an SSH access to the machine (or multiple machines at the same time). When you end your work you just need to shutdown, suspend or even delete machines (if you delete then it will be created again if you want to start it).
On the other hand you should not have any problems with creating chrooted 12.04 environment using debootstrap.
---edit---
I've tested debootstraping Ubuntu 12.04 (precise) on Ubuntu 14.04:
mkdir precise_root debootstrap precise precise_root mount -o bind /dev precise_root/dev mount -o bind /proc precise_root/dev chroot precise_root /bin/bash
I've added /bin/bash to chroot because I have zsh on the machine as a default shell.
I'm using schroot. I like the fact that it shares the home directory, and haven't figured out how to do that with just chroot.
-
I installed the GUI on my regular workstation (Ubuntu 14.04) and all is working fine. One Harmony 350 programs just fine and works great except that it repeats too quickly so I need to eliminate repeats on many keys. Also, if I save a configuration to disk and later load it back into the software, will it automatically transfer to a Flirc unit if there is one plugged in? If not, how do I get a set of commands from stored file to a Flirc? Since I have multiple Flirc units to manage and all will need the same program installed, this is important.
mike
the configuration stays on the device.
You save the configuration with:
flirc_util saveconfig <filename>
It won't automatically load. You have to:
flirc_util loadconfig <filename>
Let me know if that answers your question.
-
Yes, absolutely, point it at the ceiling. Flirc is very sensitive.
-
:( :( :(
P.S. Jason, I recall reading you had deliberatly left command line ...err... commands out of the GUI. I didn't catch why, but maybe if you put them under and "ADVANCED" tab?
Why the unhappy face? Chris! is actually helping with documentation. Day job is killing me this week. I have time off after this week where I will pick up the pace again.
I don't think the GUI is missing anything the commandline has anymore other than these;
ability to delete indexes (will get to this)
Record API (don't inticipate on putting that in, this was probably what you are referring too. Wayyyy to complicated.)
-
Oh, you can definitely wake up your machine. Make sure 'sleep detect' is enabled in the advanced settings of the GUI. Power on is the feature that's still in progress.
** EDIT **
Also, make sure you are on v3.3 of the firmware. If not, you must have the 'wake' key recorded which can be found on the keyboard controller view.
On firmware version 2.x, you have to enabled sleep detect, and record the wake key. Only that new key will wake up the machine.
On firmware version 3.3+, you have to have sleep detect enabled. If sleep detect is enabled, any key will wake the machine, but if the wake key is recorded, only the wake key will wake the machine.
-
1
-
-
Jason,
Ubuntu 12.04 is an LTS and it's not even near its EOL. Every Ubuntu LTS (starting with 12.04) has a 5 year support, so 12.04 will still be supported for 2 years and a few months. I know that it is already outdated, but for sure it is still alive :). Of course the system being still supported doesn't mean that you need to still support it yourself - especially that you are doing it all alone and the software is only needed for actual programming, which can always be done on another machine.
To support new distros and still support 12.04 you would actually need to build multiple versions and discern them in your apt repository based on version name.
BTW I don't use Ubuntu on desktop any more because of it ageing very fast for each particular version. I'm using Arch Linux at work and at home for at least 2 or 3 years now with much success (rolling release distribution for the win :)) and I haven't thought even once of returning to Ubuntu.
I'm using mint, and based on debian. I can't stand what ubuntu is doing to linux. They aren't helping anymore.
Looks like you're right. I'm having trouble getting a system up and running. I don't want to manage multiple virtual machines or a machine with 100 distributions on it. So I'm using chroot on one system and it's working out nicely. But I'm going absolutely nuts because 12.04 isn't installing and everything I read is pointing to EOL. I'll just need some time to figure out why it's not working.
-
Poweron doesn't work yet. I'll need a software update. I keep wanting to get to it, but my day job is killing me. Taking next week off so I'll address it this weekend. Very sorry for the inconvenience, it should only take me a few hours.
-
1
-
-
Ah okay, I don't have a solution for you right now. I just checked your linux version. 12.04 is a few years old now and is end of life'd.
I'll need some time to resolve this. I'm really sorry. Best bet is the beta that I published. Just have to deal with the upgrade loop bug. Just upgrade every time you launch, should be fine even though it says it didn't upgrade or there is still a newer version.
-
don't worry, the xbmc controller in my GUI is just a bunch of keyboard shortcuts conveniently labeled so you don't have to look them up. All you need is media portal's keyboard shortcuts and you can program them manually with the GUI keyboard controller.
-
OK....looks like yawor was right....the remote react better now....but still have (much less now) the double press problem....which delay time should i choose ?
You should leave your interkey delay at 3.. Thank you Yawor.
-
Any progress?
mike
updated, you can give it a shot now
-
Let me try and fire off a static compile. Are you on 64 or 32 bit?
-
Just a thought, if the current HW makes it difficult to implement and it breaks principals for programming, isn't it also then very difficult to get this reliable without huge investment in time?
If yes,wouldn't a gen2 HW be a much better base? Why not postpone support for this feature in current HW and instead focusing on cleaning up bugs in current SW (for example the Native Harmony profile) and try to get out a new hardware version of Flirc. As I have understood, your code base is now prepared to do so, correct? :)
You're very smart.
I'm going to do everything I can so that bringing this feature, it will work on any version of hardware/chip.
Using Flirc with Amazon fireTV
in How To
Posted
I tried sending these keys with a new firmware image, and it's not working. Also not sure if browser back is in fact the 0x224 yet.