I would need to know a lot more info, to answer your question - as I do not know what system your are referring to....etc.
Search found 653 matches
- Wed Mar 17, 2021 7:00 pm
- Forum: Community
- Topic: Using a Pi for transmitting IR signals
- Replies: 8
- Views: 2330
- Tue Feb 02, 2021 10:37 pm
- Forum: Support Requests
- Topic: 100% repro -- AnalysIR null dereference
- Replies: 5
- Views: 372
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: 372
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: 372
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 resolve). ...
- 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: 186
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: 12
- Views: 26948
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: 12
- Views: 26948
Re: Constant current IR LED circuit
First thing to check is if you have the x1 and x10 setting correct on your scope & pobes????
- Mon Jan 04, 2021 12:48 am
- Forum: IR Protocols & Codes
- Topic: Reverse engineering Sanyo AC rcs-3pss4e remote
- Replies: 6
- Views: 2864
Re: Reverse engineering Sanyo AC rcs-3pss4e remote
I can confirm that this 'Broadlink' formatted signal decodes as SANYO152AC in AnalysIR & can be imported in this format. (152 data bits) e.g. Row: 1 Hex: 020028017623187FC40000EDC020000000008E Binary: 00000010 00000000 00101000 00000001 01110110 00100011 00011000 01111111 11000100 00000000 00000000 ...
- Sat Dec 05, 2020 11:39 pm
- Forum: Support Requests
- Topic: "'TIMER_ENABLE_PWM' was not declared in this scope"
- Replies: 12
- Views: 1015
Re: "'TIMER_ENABLE_PWM' was not declared in this scope"
Ok
Best thing to do is to email me all of the files from your KontroLIR directory & I will try it out here. (Might take a day or 2).
send to info@A?????IR.com
Best thing to do is to email me all of the files from your KontroLIR directory & I will try it out here. (Might take a day or 2).
send to info@A?????IR.com
- Sat Dec 05, 2020 10:18 pm
- Forum: Support Requests
- Topic: "'TIMER_ENABLE_PWM' was not declared in this scope"
- Replies: 12
- Views: 1015
Re: "'TIMER_ENABLE_PWM' was not declared in this scope"
...forget to mention...
When making changes to the library, restart the IDE to ensure the new version of IRremote is used
When making changes to the library, restart the IDE to ensure the new version of IRremote is used