jason

I'm really sorry for the delay, I had family in town and thought I could slip this in during my free time. Turns out they didn't give me any free time. I'll try and get this in over this coming weekend. I'm sorry for the delay everyone.

I do have an API written in C. I will post this in the near future when I clean it up. This is a great idea though.

I would love to have an application launcher in flirc, and I'll be looking into figuring out how to do this after the 1.0 release. The hard part is, making it work across platform. = (

Thanks Matt for pointing me to this thread. I've got to say, I was really puzzled reading the problem. And even more so as I kept reading each reply. But I've got to hand it to SirDrexI, I think this might be it. That's the only difference I can think of, and I do send the keys simultaneously. You might have nailed it. This should be fairly easy to try, and I'm going to post a beta firmware image this weekend for you guys to test. I'm sorry for the delay, I can't quite figure out how to get notified of 'all new created threads'. I'll post an update here when that image get's created, so make sure you're following this thread to get notified.

You beat me to it. No problem, and I'm happy that did the trick. Sorry this was such a pain, I'll make the cli a little easier to use in this respect.

Here are all the definitions Modifiers work as follows: #define MOD_CTRL_LEFT (1<<0) #define MOD_SHIFT_LEFT (1<<1) Left Control stands for 1 shifted left 0 times. So that's: 0000 0001 Left Shift stands for 1 shifted left 1 times, Which is: 0000 0010 If you want to do Left Ctrl+ Left Shift + a, then do the following: Logical OR of both Left Ctrl+Left Shift: 0000 0011 The result is 3. So, flirc record 3 4 Where 4 stands for HID_a It's not very intuitive for anyone who doesn't have much experience programming, or in engineering. So the GUI is very useful. Maybe a website accessible via your smartphone or PC will spit out the equivalent api strings for you? Hope that makes sense and thank you Chris for pointing me to this thread. /* HID #Defines */ #define HID_a 4 #define HID_b 5 #define HID_c 6 #define HID_d 7 #define HID_e 8 #define HID_f 9 #define HID_g 10 #define HID_h 11 #define HID_i 12 #define HID_j 13 #define HID_k 14 #define HID_l 15 #define HID_m 16 #define HID_n 17 #define HID_o 18 #define HID_p 19 #define HID_q 20 #define HID_r 21 #define HID_s 22 #define HID_t 23 #define HID_u 24 #define HID_v 25 #define HID_w 26 #define HID_x 27 #define HID_y 28 #define HID_z 29 #define HID_1 30 #define HID_excl 30 #define HID_2 31 #define HID_address 31 #define HID_3 32 #define HID_pound 32 #define HID_4 33 #define HID_dollar 33 #define HID_5 34 #define HID_percent 34 #define HID_6 35 #define HID_carrot 35 #define HID_7 36 #define HID_amp 36 #define HID_8 37 #define HID_star 37 #define HID_9 38 #define HID_paren_right 38 #define HID_0 39 #define HID_paren_left 39 #define HID_return 40 #define HID_escape 41 #define HID_delete 76 #define HID_backspace 42 #define HID_tab 43 #define HID_space 44 #define HID_minus 45 #define HID_underscore 45 #define HID_equal 46 #define HID_plus 46 #define HID_brack_right 47 #define HID_curly_right 47 #define HID_brack_left 48 #define HID_curly_left 48 #define HID_back_slash 49 #define HID_pipe 49 #define HID_semi_colon 51 #define HID_colon 51 #define HID_apostrophe 52 #define HID_quote 52 #define HID_back_tick 53 #define HID_tilde 53 #define HID_comma 54 #define HID_less_than 54 #define HID_period 55 #define HID_greater_than 55 #define HID_fw_slash 56 #define HID_questionmark 56 #define HID_F1 58 #define HID_F2 59 #define HID_F3 60 #define HID_F4 61 #define HID_F5 62 #define HID_F6 63 #define HID_F7 64 #define HID_F8 65 #define HID_F9 66 #define HID_F10 67 #define HID_F11 68 #define HID_F12 69 #define HID_print_scr 70 #define HID_scroll 71 #define HID_pause 72 #define HID_insert 73 #define HID_home 74 #define HID_pageup 75 #define HID_end 77 #define HID_pagedown 78 #define HID_right 79 #define HID_left 80 #define HID_down 81 #define HID_up 82 #define HID_enter 88 #define HID_shift (1<<1) #define MOD_CTRL_LEFT (1<<0) #define MOD_SHIFT_LEFT (1<<1) #define MOD_ALT_LEFT (1<<2) #define MOD_COMMAND_LEFT (1<<3) #define MOD_CTRL_RIGHT (1<<4) #define MOD_SHIFT_RIGHT (1<<5) #define MOD_ALT_RIGHT (1<<6) #define MOD_COMMAND_RIGHT (1<<7) #define HID_EJECT (1<<7) #define HID_VOL_DOWN (1<<6) #define HID_VOL_UP (1<<5) #define HID_MUTE (1<<4) #define HID_PLAY_PAUSE (1<<3) #define HID_STOP (1<<2) #define HID_PREV_TRACK (1<<1) #define HID_NEXT_TRACK (1<<0) [/CODE]

1. That would actually be pretty difficult. Since all the 'keys' seen are keyboard presses, I'd have to develop something special. However, it would certainly be an invaluable debug tool, so yes. 2. Yeah, eventually, It'll get there. We're talking how to make this more social friendly. 3. I'm working fairly hard on wake. Period and comma should actually be there. Try: flirc record . flirc record , 4) It's planned, I'm going to have something coherent to read like a Sensitive <-----> Least Sensitive scale. I want to apologize, I've fallen behind in development. For those who don't know, it's really just me putting in all the time and work, and I have a full time job on top of this. But in the next coming weeks, things will certainly pick up again as I'm pushing very hard to ensure this happens.

While I certainly wont rule out that the unit is defective, I believe I may know the cause. Flirc may be recording a signal seen from your room lighting, or even television. When this happens, a good trick would be to open up the GUI, and press the delete command. The next key 'seen' by flirc will be deleted. That way, if an erroneous signal was recorded as 'some' key, you will un link it. Let me know if that does the trick.

I'm glad you got it working but unfulfilled not solving the problem should it still exist. :( Could you perhaps post a picture of the remote that didn't work? Thanks so much Henry.

Something doesn't sound right, and I certainly can't leave you having to sit next to the receiver. Try updating the firmware to the latest and stable release, clearing the config, and starting over. http://blog.flirc.tv/?page_id=46

With the flirc in your machine, try an lsmod. Compare them on both machines and see if a there are any different usb/hid drivers loaded. It's possible that an an update, something new got loaded. Was your system recently updated?

Is there another PC you can test this on? Another remote? Just trying to take one thing out of the equation. Let me know.

This is actually all really good feedback. It will be a matter of hooking up my debugger and trying to figure out why a key is sent when an unknown signal is detected. The hard part....time... = (

Sorry, I dropped the ball, wondering how things were going? You still seeing this issue?

Thanks Chris, yes, please keep me posted. I've actually been looking at this quite a bit to see what the cause is.

Your device certainly has many records, however, it shouldn't be full. It's about half way. I can presume it's a software bug, but I'll try to confirm. Which remote are you using?

thanks so much for your really detailed posts. I'll get to these. One note, with the sensitivity, you have to plug-unplug your flirc. I should have a print out but I didn't really make that official yet as I will be fine tuning this and adding support via the gui. Thanks again.

It's actually pretty complicated. I appear to the host as a USB keyboard, but my firmware and how I send keys to the computer is entirely up to me. But that's not the problem, the problem is the remote control. When you press a button on your remote, your remote blinks an LED sending a 'packet' across your room. Each packet is sent around 100ms apart from the next, but that 100ms really depends on your remote. Some are 100ms, the harmony is configurable to seconds. So here is the problem. When you press the button on the remote, the remote sends packets (plural) to flirc. When you hold your button down on your remote, your remote sends 'packets' to flirc. There is absolutely no difference from flirc's point of view. I have to determine if you've just pressed the button on your remote, or if you are holding it down. If you press the button rapidly, you may just end up looking like you are pressing the button down to me. And the worst part is, each remote control is different. So I have to come up with a generic way that will work with everything. So that's the problem, I'm not sure if that's what you asked, but I'm referring to this as 'sticky' buttons. I'll narrow this down and come up with a really smart way of making this rock solid. The issue with the new firmware is that I made a mistake somewhere in the USB protocol and windows does not see my 'terminate' character, which is interpreted as the user has stopped pressing the key all together. I'm going to narrow this down really soon.

Try experimenting with that delay, between 100ms - 200ms. Yes, 200ms will limit you to about 5 button presses a second, and if you click faster than every 200ms, the second press would be ignored. Every remote works differently, and I had to make an assumption that no person would really press a button faster than 6 times a second. ~166ms. I believe I gave it wiggle room and stuck it around 140 ms. Try playing with it, I'm sure you will find a happy spot. Let me know.

Yes, there should be a configuration in your harmony software to change a delay for successive button presses. I actually haven't found this myself (nor have I really looked), but others on the forum have mentioned this. Maybe someone will chime in, or if you do find it, could you post back a screenshot or where it is? I'm sure this would help a lot of people. Just increase that delay to 200ms. Thanks for the good feedback, and let me know.

Pretty curios to know what the original default remote protocol was. I want to perfect this guy, and it's been quite the challenge to make it work across all the flavors of remotes....but I'm going to fucking do it. :)

Nope, they don't have to be programmable. Any other remote should work fine. You can even cycle through DVD/AUX/TV to get different remotes as those are most likely set as different devices. I'm not quite sure yet. If you give another remote a shot, that might narrow it down. If you run through the GUI minimalist view two times, do you get, "button already exists" error? Or can you record the same button a couple times. The "GO" button needs to disappear on the other windows, it only works on the minimalist window. I will update that in the next release.

Not really sure what could be going on. Do you have any other remote you could try? Let's see if it's a problem with Flirc, or an issue with remote/compatibility. Perhaps the batteries in the remote are on their way out?

Thanks for the followup, I'm going to get this resolved in a firmware update.

duk @ Neal Does the special wake command from flirc work? I haven't gotten much feedback regarding that release. Yes, the commandline will still show the wake command, and you will be able to successfully record to that command, however the firmware wont officially support this in v1.0. Here are my plans: I'm overwhelmed working out logistics right now. Programming, assembly, packaging take up most of my time and I'm working a lot right now to make this less intrusive to my day so I can continue with development on the GUI and firmware. The repeat firmware will be deployed soon. Once that is done, I will work on the 1.0 release of the GUI, then this will have my full attention as it's one of the last remaining puzzle pieces. Of course stay tuned to the blog or twitter feed where I will be announcing all these releases as well as any new beta firmware images to try. Thanks Neal.