December 6, 20178 yr comment_14608 I have URC remote that's configured to keep sending commands while the button is pressed. I can see signal getting transmitted. And, similar config works with all my other devices - receiver, tivo, etc. It doesn't work for Flirc. I have both, old and new, configured to Nvidia Shield and Fire TV. Both only react one time and not repeating. I've tried 2 different code sets on URC - AUX 001 and, I think, 022. Neither will repeat. Any ideas? BTW, new model doesn't have inter-key delay in firmware. Report
December 6, 20178 yr comment_14609 Can you fire up the GUI, go to device log, enable ir debugging, and press and hold the button down in question? Save and post that text file here. Report
December 6, 20178 yr Author comment_14612 As you have no doubt suspected, it was only sending repeat command on repeat keypress. It turns out in URC it's a function of code set rather than remote itself. Found a code set that doesn't do it and it works now. Thanks. It would be nice if firmware natively support repeat command but I can see how that could be different for selected code set and isn't easily done on your side. For the record, used AUX 689 if anybody's having same issue. Report
December 6, 20178 yr comment_14613 @TVAddict it's a matter of the IR protocol used by specific setup code (or code set). Different protocols have different rules regarding the signal repeat. Some use a full frame repeat where the same frame is being repeated all the time, others use different start frame and then some repeat pattern (like the NEC1/NEC2 ditto frame). Flirc should work properly with any protocol using full frame repeat, if the repeated frame is the same as the starting frame (this isn't always the case). It also has support for NEC1/NEC2 repeat. It would be helpful if you could do what @jason has asked about anyway. If you can, go back to your previous setup on the remote, enable IR logging in Flirc and post here your log files. We will analyse the signals and there's a chance that a support for that protocol could be added in the future. Report
December 7, 20178 yr comment_14617 Yes, we're very interested in seeing this. If we could trouble you to follow up with a log, we'd be extremely grateful. Thanks for the help and the follow-up. Report
December 7, 20178 yr Author comment_14619 Here you go. This is from URC AUX 001 code set, which was suggested as working in another URC related thread. Thanks for you help, guys. :e:20324 0,8960,4370,598,466,571,467,575,462,576,462,576,462,576,460,576,462,576,462,574,462,573,463,580,455,576,462,576,1574,602,462,575,1570,602,462,576,1574,597,1575,599,460,576,460,575,1574,598,1574,597,462,576,462,575 :e:60 :e:96 :e:97 :e:96 :e:97 :e:96 :e:97 :e:96 :e:97 :e:97 :e:97 :e:97 :e:97 :e:97 :e:97 :e:97 :e:97 :e:97 :e:12481 0,8957,4369,598,466,576,462,575,462,576,462,575,462,576,462,576,462,575,462,602,436,602,436,601,436,576,462,602,1548,597,462,576,1574,602,462,601,1544,601,462,576,462,601,1548,602,1569,597,1574,602,462,575,462,576 :e:60 :e:96 :e:97 :e:96 :e:97 :e:96 :e:97 :e:96 :e:97 :e:96 :e:97 :e:96 :e:97 :e:96 Report
December 7, 20178 yr comment_14621 Do you know what device is the AUX 001 code for? The manufacturer and maybe model? Do you have some code set book or list for your remote? From what I can see this seems to be some variant of the NEC protocol, but it's too short (NEC1 has 32 bits of information, this one only carries 24 bits). Report
December 9, 20178 yr Author comment_14628 Unfortunately, no. When you go by code number, it just pulls up command set but not device/manufacturer. And to find it you need to click through every available manufacturer and model. They're not organized or sorted. Sorry. Report
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.