Search found 776 matches
- Thu Apr 29, 2021 10:54 pm
- Forum: IR Protocols & Codes
- Topic: Gap between Sony triplets
- Replies: 1
- Views: 3846
Re: Gap between Sony triplets
It seems the 45 mSecs is correct for 20 bit SONY as well. $40:2400,600,1200,600,1200,600,1200,600,1200,600,1200,600,1200,600,600,600,600,600,1200,600,600,600,1200,600,1200,600,1200,600,600,600,600,600,600,600,1200,600,1200,600,1200,600,1200,10133,2400,600,1200,600,1200,600,1200,600,1200,600,1200,600...
- Wed Apr 28, 2021 9:06 pm
- Forum: IR Protocols & Codes
- Topic: Resolved: Code Burst with LearnIR
- Replies: 3
- Views: 4014
Re: Code Burst with LearnIR
Thanks for the info Joe. Here is the summary for reference: The SONY protocol must be sent in 3 bursts otherwise it will be ignored. (There may be a small number of exceptions) So even the shortest of presses will always generate 3 bursts. The shorter Pronto capture is likely a bug on that other dev...
- Wed Apr 28, 2021 12:06 pm
- Forum: IR Protocols & Codes
- Topic: Resolved: Code Burst with LearnIR
- Replies: 3
- Views: 4014
Re: Code Burst with LearnIR
Sorry to hear you are having issues... 1. When recording signals make sure to hold the remote about 1m(1 yard) away from the LearnIR and point the remote directly at it. 2. Please email me (to info@....) - a copy of the signals in LIR format and also the RAW format of say 3 different signals - also ...
- Wed Mar 17, 2021 7:00 pm
- Forum: Community
- Topic: Using a Pi for transmitting IR signals
- Replies: 8
- Views: 12522
- Tue Feb 02, 2021 10:37 pm
- Forum: Support Requests
- Topic: 100% repro -- AnalysIR null dereference
- Replies: 5
- Views: 9131
Re: 100% repro -- AnalysIR null dereference
If possible, it'd be great (if not technically difficult) to avoid resetting the device type away from the user-configured device type. I can't tell you how many times I've scratched my head, wondering what I was doing wrong, only to find the device type got reset. It's been a lot. (Then again, may...
- Sat Jan 30, 2021 4:30 pm
- Forum: Support Requests
- Topic: 100% repro -- AnalysIR null dereference
- Replies: 5
- Views: 9131
Re: 100% repro -- AnalysIR null dereference
UPDATE: It proved pretty straightforward to resolve. We will include the fix in a future AnalysIR application update. In the meantime the following workaround should do: When this error is encountered, type a 'space' character into the Button column, instead of totally deleting the contents. Alterna...
- Sat Jan 30, 2021 4:11 pm
- Forum: Support Requests
- Topic: 100% repro -- AnalysIR null dereference
- Replies: 5
- Views: 9131
Re: 100% repro -- AnalysIR null dereference
Hi Henry Sure is an unusual use case, which was never considered until now... renaming the same signal & then un-naming it etc :) I tried it with another source device and the same thing happened. I will send some time over the next few days tracking it down. (I suspect it will be easy to resolv...
- Thu Jan 28, 2021 12:20 pm
- Forum: Support Requests
- Topic: error "Value was either too large or too small for a UInt32"
- Replies: 2
- Views: 5871
Re: error "Value was either too large or too small for a UInt32"
It looks like an application error as opposed to a LearnIR device error. I will email you the V2 application to see if it is better. The signal you posted decodes fine for me on AnalysIR. When recording signals I suggest you only press the remote briefly (vs holding down for a long time and keep the...
- Sat Jan 23, 2021 2:16 pm
- Forum: Community
- Topic: Constant current IR LED circuit
- Replies: 26
- Views: 48542
Re: Constant current IR LED circuit
Thanks for the update!
- Sun Jan 10, 2021 4:48 pm
- Forum: Community
- Topic: Constant current IR LED circuit
- Replies: 26
- Views: 48542
Re: Constant current IR LED circuit
First thing to check is if you have the x1 and x10 setting correct on your scope & pobes????