jason
-
Posts
4,023 -
Joined
-
Last visited
-
Days Won
259
Posts posted by jason
-
-
Update: Last night, I decided to take my universal remote out of the loop. I dug out my old Xbox remote, but had the same problems. I even opened up a second flirc with the same result. I then decided to try my Roku remote. Everything seemed to work with the Roku remote and my universal remote mimicking the Roku remote. It appears that flirc has some incompatibilities with certain IR protocols. flirc could not tell the difference between some of the Xbox directional buttons. The Xbox uses the RCA protocol while the Roku uses the NEC1 protocol. I also had problem with the MCE protocol.
Update 2: A little search of the forums confirms that both the Xbox and MCE remotes do not play nice with flirc. No worries, I can tell my JP1 remote to mimic a different remote entirely. I am off to search for a well supported remote/protocol.
-Tom
Yes, you found out before I was able to get back to you. They use non-standard frequencies and it messes with flirc a bit. I have it on my todo to fix this.
Try samsung or panasonic profiles. Those work great.
-
No problem, appreciate you understanding. It's been pretty tough.
Which version of the GUI are you on? You on the latest?
-
I mentioned this in a few places, but don't like to because it doesn't excuse much, but it's just me here. I do everything, support, development, sales, packaging, testing, assembly, you name it. It's literally enough jobs for 2 people full time, and I do it outside a full time job. I may miss an occasional post, which I did, and I really apologize. One way to get a hold of me is by going to that contact support site, it goes directly to my email and is managed by zendesk so I don't lose track.
That's a problem that is due to a bad driver. Give this a try: https://flirc.zendesk.com/hc/en-us/articles/200712548-Using-the-ZADIG-Utility
I apologize I missed your post.
-
So pictures are more important than a buggy Flirc () ... I think i should post that on Amazon ... -.-
I mentioned this in a few places, but don't like to because it doesn't excuse much, but it's just me here. I do everything, support, development, sales, packaging, testing, assembly, you name it. It's literally enough jobs for 2 people full time, and I do it outside a full time job. I may miss an occasional post, which I did, and I really apologize. One way to get a hold of me is by going to that contact support site, it goes directly to my email and is managed by zendesk so I don't lose track. I'll respond about what your specific problem is in your thread.
-
Yes they would, and yes you just need to use different profiles.
-
I added a second 2 foot USB extension cable and ran my flirc out the back of my cabinet and it is now perched atop my center channel speaker. It's been chilling out up there for a week now and i haven't had a single issue of multiple key presses! I'd prefer to have it inside behind the glass, but i don't have any spare material to use as a filter.
Any chance I could you post a picture of your cabinet?
-
Glad it finally worked, not sure why it took so many attempts but it shouldn't be an issue any more. Sorry for the trouble.
-
How about trying to install the libusb driver?
-
Try this:
https://flirc.zendesk.com/hc/en-us/articles/200712548-Using-the-ZADIG-Utility
** EDIT **
you have an old driver, the installer doesn't do a good job of replacing the old driver, and I don't know why. Following the instructions, you'll force the update of the driver, and everything should be good. The -16.-16 is because that request to the device doesn't work because the old winusb driver is restricting commands.
-
In the advanced menu, disable 'built-in profiles'
-
1
-
-
That's a really interesting find.
Try the same command with sudo
-
It's not too bad. Here is what I would recommend to help out. Use an sftp application, on the mac, it's transmit/cyber duck. There are plenty for windows.
What this will do for you, is look like an FTP browser but connect over SSH. You'll want to connect to your raspberry pi on port 22. Use the default raspberry pi login and password for your distribution. root/openelec
Then, browse to the location of the xml file. Looks like it's here: /storage/.xbmc/userdata/
(found on this website: http://wiki.xbmc.org/?title=HOW-TO:Modify_keyboard.xml)
Then, with that application, you could double click it, and open with a text editor, or drag it to your computer, edit it, and then send it back.
That should make things easier. Let me know.
-
Yes, it's definitely the keymap file in XBMC. I tried to use the most common keys, but often, the keymap on the distribution, xbmc, openelec, etc, will be different. You need to ssh into the box and locate that xml file.
-
Thanks Chris. Yes, just a one man show. I have a number of things I'm working on to get me more free time.
-
-
I'll take it back, no questions asked. It's just me here.
-
Here is your configuration:
flirc_util version v1.2.2 [v1.2.2-13-gc107673+]
Firmware: v2.3
Settings:
sleep detection: Disabled
noise canceler: Disabled
inter-key delay: 6
state: 0
builtin profiles: Enable
Memory Info:
keys recorded: 72
keys remaining: 97
memory used: 74%
Recorded Keys:
Index hash key
----- --------- ---
0 77E20A13 F4
1 37A6D1B2 F4
2 7BA80BB8 F3
3 3B8C8611 F3
4 5A47BC68 tab
5 1A2B37C2 tab
6 19B7D2BA F7
7 D98A955E F7
8 F8B6D2BA F6
9 B88A955E F6
10 F897EE73 wake
11 B86BB117 wake
12 F83CF522 F5
13 3869327F F5
14 BBEA3188 F2
15 FB06B72E F2
16 99F746C3 c
17 D923841F c
18 B8FA34A3 i
19 F82672FF i
20 DA2637C2 F1
21 1A43BC68 F1
22 193DF522 u
23 5969327F u
24 99D7C620 return
25 D903047D return
26 3872835E return
27 789EC0BA return
28 FCFFB1D3 backspace
29 3C0CC3B1 backspace
30 D9A29BD0 p
31 19CFD82C p
32 193FF0D2 f
33 596B2D2F f
34 DAA47327 r
35 1AC1F8CD r
36 376775D7 space
37 77A3AE37 space
38 782DB499 x
39 B859F1F5 x
40 77233EEF up
41 B75F774F up
42 B8D9A083 down
43 F805DEDF down
44 D9731B23 up
45 19A0587F up
46 9AA9CA85 down
47 DAC54F2C down
48 FBADCA85 left
49 3BCA4F2C left
50 DAADCA85 right
51 1ACA4F2C right
52 16DDD665 1
53 561910C6 1
54 77E1D665 2
55 B71D10C6 2
56 56E1D665 3
57 961D10C6 3
58 F781E965 4
59 37BE22C6 4
60 3898E222 5
61 78C41F7F 5
62 B7F5E865 6
63 F73122C6 6
64 96F5E865 7
65 D63122C6 7
66 774226B5 8
67 B77E5F15 8
68 B838F522 9
69 F864327F 9
70 55760237 0
71 95C27B8A 0
So I would pay attention to the doubles. You have double:
return
Down
Up
I don't know if this was intentional, or if noise was recorded. If not, delete those. Have you tried enabling the noise canceler?
-
do you guys have sleep detect enabled in the GUI?
Also, make sure you haven't recorded any noise. use the commandline, flirc_util settings. Look for duplicates. Delete all duplicates and re-record those keys.
When receiving a signal, flirc will send a character to the machine. Regardless of the state of the machine. Sleep detect tells flirc to check if the computer is sleeping. If it is sleeping, do not send any keys unless it's the 'wake-up' command.
Further, if you don't have sleep detect, and have recorded erroneous noise, then the machine will see noise as a false signal, and send a command to the computer.
** EDIT **
TLDR; enable sleep detect in the gui
-
I'm not familiar with XMP, can you give me a pointer to a remote?
-
try changing your interkey delay to 3 in the advanced section of the gui
-
Can you post the configuration?
-
Yes it's possible with either the GUI and the command line. It's under the file menu in the GUI.
-
No update yet guys, I'm working on my test fixture. I'm spending way to much time testing, I need to hand this off to give me the time to work on firmware.
-
In advanced, disable built in profiles.
Could not upgrade firmware. Contact support.
in Firmware Bugs
Posted
Sorry, missed your first reply. Any chance we can set up a team viewer session?