In esp-idf v5.2.1 the rmt driver has been modified and some examples are provided in the SDK.
In ir_nec_transceiver example I modified the example to send a nec ir with address 0 and command 0
const ir_nec_scan_code_t scan_code = {
.address = 0x0,
.command = 0x0,
};
The nec_encoder do not seem to work as intended.
NEC protocol is supposed to send address !address command !command (! = complement)
Leading pulse is ok, but no complements are in the stream.
With this version of rmt driver, it seems not possible to just send an array of raw data. We must implement an encoder which is useless for raw data.
Please add the possibility of using a transmit function that do not use an encoder.
new rmt driver and ir_nec_transceiver examples not generating proper NEC signals
Re: new rmt driver and ir_nec_transceiver examples not generating proper NEC signals
I agree that a simple 'send' option should be added, together with simple ways of registering one's own interrupts.
A lot of times it's much simpler and faster for the user to directly generate rmt_item32_t instead of writing a encoder. Not to mention registering custom interrupts could be much more efficient.
A lot of times it's much simpler and faster for the user to directly generate rmt_item32_t instead of writing a encoder. Not to mention registering custom interrupts could be much more efficient.
Who is online
Users browsing this forum: kaxx1975, Majestic-12 [Bot] and 228 guests