jason
-
Posts
4,008 -
Joined
-
Last visited
-
Days Won
256
Posts posted by jason
-
-
No problem, so sorry about the trouble.
-
I'm also having no luck with the upgrade. On Win 8.1 64-bit. It always displays -16.-16 as the version, even after restarting the GUI.
When trying to upgrade the firmware it says
Your firmware version is: -16.-16
The latest firmware version is: 2.2
And then locks up the GUI when trying to upgrade.
Here's some flirc_util.exe output that replicates the commands above. I'm new to all this so let me know if you need anything else, and thanks for any help!
>flirc_util.exe version
[E] determine_iface(101): version not supported, loading def: ver1
Flirc Version v1.2.0 [v1.2.0]
[E] fl_ver1_version_str(866): usb tx result > 0: -2
(null)
>flirc_util.exe settings
[E] determine_iface(101): version not supported, loading def: ver1
Settings:
sleep detection: NA
noise canceler: Enabled
inter-key delay: 0
state: 0
builtin profiles: NA
[E] get_size(103): Error reading high byte of size
-3.000000
>flirc_util.exe dump 63
[E] determine_iface(101): version not supported, loading def: ver1
Reading:
0000 Error
>flirc_util.exe status
[E] determine_iface(101): version not supported, loading def: ver1
Last upgrade attempt: Error
Incredibly helpful, I know what's wrong. Thanks a million. I'll post an update in a few minutes.
-
sorry not login but upgrade.
Close the GUI, and reopen it. Are you on windows?
There is a bug, and I can't reproduce it enough to figure out what's going on. So any help on that would be appreciated. However, it's just reading the version wrong, the device is fine.
-
Sorry about this guys. I figured out the problem. Released an update. Upgrade to v2.3 and the problem will be fixed.
-
Make sure in advanced settings, built-in profiles is not disabled
-
I'll fix it. Not to worry.
-
Awesome, I'm so puzzled why you had that trouble. I'm sorry about that, and thanks for letting me know you are up and running again.
-
No, I've disabled that. I got burned by it. Here is how.
If you are in the middle of an upgrade, or you get one error while upgrading, a part of the program is corrupt. If you then try to do a dfu leave, then the application will run, which is corrupt, and the device could get bricked.
If it ever goes to upgrade mode, and a program starts to download, it will always assume that that program is invalid unless it gets to the end.
-
Your mailbox is full so I'll just copy the message I was going to send you here:
Wow, I'm surprised it's just you!I have a bit of experience with Linux and currently hold the title of "Linux System Operator" at work... I hope to be a Jr. Sys Admin in a few years. If you need anything that I might be able to help with just let me know, I'd be more the happy to help out.I've still had no issues with using this with my xbmcbuntu set up, I'm actually running out of keys to use on my remote. I've also introduced the FLIRC to a few friends and I want another one for a different room so I'm going to be ordering a total of 4.Cheers!Okay, try PMing me again, I should have fixed the storage problem.
-
Illiac -
I have already implemented the manually deleting of buttons with the commandline, I will push the update this weekend.
As far as your bootloader problem, you have a USB issue. Bad power supply which is shared with USB is causing problems. If you are using a hub, try removing the hub or powering it.
Flirc should not be getting stuck in bootloader mode without the user doing so.To get it out of bootloader mode, fire up the gui. After the GUI loads the firmware, you can close the GUI and use the commandline.
-
I just tried it and it works. There might be a usb button problem. Leave the flirc plugged into your raspbmc, then hold the arrow key down. After about 5-10 seconds flirc will register and start working. I'll look into it. I've let the rpi sit for 24/hours, came back, and it worked without the initial 5-10 second hicup.
-
Turns out the flirc-xbmc repo was infact all I needed here. I added the src files to the .xbmc/addons section and added the udev rule as well. On the reboot of the Rasbmc the Flirc gui was started and I was good to go. I am still not sure if I actually needed to program the up, down, left, right, enter and back keys but I did. I did then load a configuration which pointed by default to a flirc config and in the end the system is up and running. Hopefully this helps someone else out in the future. Now on to the long press configurations to see if I can get these working.
thanks for posting this!
-
I just hit the same problems and I can add to it that Flirc software will not save or load configuration, also will not clear configuration.
If I save configuration to my PC it works only rarely, loading from previously saved never works
What a headache :(
Two Flircs both firmware 2.2 9 - tried to force reflash as well
Software 1.2.0
Can someone please save my sanity ?
In the latest version of the GUI, go to advanced, and disable built in profiles.
-
I'm not sure, there was similar behavior, but only with firmware v2.0, but I fixed that bug.
I am going to release an update to my commandline tonight. Basically, you can use the following command to display your config and delete a particular index:
⚡ flirc_util settings
sleep detection: Enabled
noise canceler: Disabled
inter-key delay: 3
state: 0
builtin profiles: Enable
Memory Info:
keys recorded: 11
keys remaining: 158
memory used: 7%
Recorded Keys:
Index hash key
----- --------- ---
0 5563511F play/pause
1 55424110 vol_up
2 150608B0 vol_up
3 34424110 vol_down
4 F40508B0 vol_down
5 B4A1EC0D stop
6 D5E25310 fast_forward
7 56FDA56E rewind
8 9629E3CA rewind
9 F4A5EC0D prev_track
10 B469B3AD prev_track
⚡ ./objs/Darwin_x86_64/clang/flirc_util/flirc_util delete_index 5
-
What doesn't work with the firmware? Do none of your keys respond anymore?
-
Re run as sudo or make a udev rule. Should be instructions on the download site for the udev.
-
Thanks so much, these posts make my day. No team, just me.
Let me know before you get another one, shoot me an email.
-
LOL sorry for the caps. i use it for work and forget to turn it off.
but thanks for the quick response.
Okay, I'm going to lose sleep over this. Where do you work that requires you to type in capital letters?
-
-
I need to publish it, but it's not going to be what you need. But the good news is you don't need an API.
Flirc translates remote control buttons into keyboard keys. That's how I get all the media center applications to know about flirc without needing built in support. You can open up a text editor and use your remote control to type into the editor. You'll first need to use my application for pairing those keys.
Does that answer your question?
The API is other developers can integrate a pairing application into their own application. -
Interkey delay as referred to in the advanced section of the flirc GUI is an adjustable setting for the firmware for the spacing in between signals while holding down a button on your remote. If you are rapid firing your button on your remote, and then the button feels like it gets 'stuck' temporarily like are holding the button, then lower this value. I doubt you will get this on the harmony. Those are terrible remotes for rapid firing. You can't adjust this in the harmony one. I don't know about the 650. (for example on my harmony remote, I can press the button 5 times in one second. The remote will output 5 button presses over 5 seconds, it's the most obnoxious piece of shit ever). I told logitech about it.
-
it's a problem in the firmware, it doesn't know you aren't pressing a remote button. I will have a more advanced input capture in the future, however, I will get a tool out to fix this shortly.
-
Sorry for the delay.
I've updated the config for you.
I will soon have something to do this for you.Thanks so much.
-
I'll have a fix for that soon. For now, send your configuration to me, I'll see if I can find it.
Flirc with v2.2 not working after boot (with workaround)
in Firmware Bugs
Posted
I posted an update, but I'm not sure it's going to fix this. This is probably a different problem. Ping me outside this thread, or start a new topic.