new rmt driver and ir_nec_transceiver examples not generating proper NEC signals
Posted: Sun Mar 24, 2024 5:50 pm
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.
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.