I have created a NEC infrared component that can either decode data on the signal pin of VS1838B type of component.
The reason being Amazon UK sells 6 receivers for less than £5.
Plus the receiver and remotes are supplied in Arduino and ESP32 Kits ,e.g. by ELEGOO.
TX transmits the 38KHz required that is supplied to an IR LED
Installing the NEC_IR Component
Place the attached component (NEC_IR.fcpx) into a folder, e.g. "Flowcode Custom Components".
In Flowcode: File > Global Settings > Locations tab > add that folder path under "Look for components in..." (add a semicolon suffix to include subfolders).
File > Reload.
Component Libraries > right-click "NEC IR TX/RX 38KHz" > Details, to confirm it's loaded from the right folder. You'll find it under Comms > Wireless, or by searching "RX".
Wiring & Setup
PWM1's output pin (drives the TX IR LED) and the pin you select for your IOC interrupt (reads the RX receiver module) must be different physical pins — never the same one.
Add an Interrupt icon to your flowchart, then double-click it to open its properties. Set Interrupt on to IOC, then click Create New Macro. In the pin list that appears, select the physical pin your receiver module is wired to (this is the IOC pin), then click OK. Click Edit Macro to open the new interrupt macro that was just created for you.
In that newly created macro, add a call to NEC_IR1::ProcessEdge(Mode) so it runs on every edge (Mode: 1=Address, 2=Command, 3=both packed as Address256+Command).
Back on the Interrupt icon's Properties dialog, set Trigger on change to Both Edges — not rising or falling only. NEC decoding needs to see both, since a mark and a space are told apart by which way the signal just transitioned.
Set the component's RX Pin property to exactly the same pin you selected as the IOC pin above. These are two separate settings that must match: the Interrupt icon controls which pin wakes your ISR; RX Pin controls which pin ProcessEdge() itself reads to tell a mark from a space. Getting this wrong can silently fail to decode, or "accidentally" appear to work — don't rely on that.
Call NEC_IR1::Initialise() once at startup, before transmitting or receiving.
If driving the TX LED through an inverting stage (e.g. a PNP transistor), tick the "Invert Output (PNP driver)" property under Transmit Options.
Tested on Arduino MEGA (AVR) and BL0011 Eblocks 2 (PIC)
Martin (mnfisher) also added a NEC decoder here
The funny thing is he posted it as the same time I announced I was creating a NED component.
So there are now two to use.
Attached is an Example project I was using for testing.
If course you can use LDC/GLCD or any other method instead of UART.
If you want to create a remote receiver, you can use the Command, then use the switch command.
If you are using more than 1 remote, then the Address should be different so use address as well.
Br Jorgen
EDIT: Short week In your examble, I change the device to an Arduino Uno an add an I2C display and toggle the Uart, but get error in compiling. I see that it is something to do with the timer, I also try to change to other, what have I forgotten, have I to start with a new project wih an arduino
Looks good - an idea (and I probably should test this works first) - rather than the user 'busy waiting' on data_ready (in my code's case) - or calling ProcessEdge and checking the value...
Would it be possible to setup a pin interrupt - that fires on new data ready. Then the main program can go about it's business and only handle IR if the user presses a button?
Then, of course, we want to use the RMT hardware on the esp32 to receive the signal
Thanks Jorgen & Martin.
@Jorgen.
Thanks for checking on the UNO.
There is a bug within the component.
I will get the component updated and will also attach updated UNO project that should work.
Note button number will not be shown it will need converting.
Are you using ELEGOO remote?
@Martin.
It kind of does work like that as the IOC is used to trigger ProcessEdge and that is only when button is pressed.
So the rest of the program is allowed to carry on with the rest of the code.
It would be nice for the ProcessEdge to be automatically triggered by an IOC you don't have to add, which is what you are asking, but thats in the future.
Not quite what I'm after, but i see what you mean. I'd like a 'new code' interrupt that occurs once for a new message or repeat received. The IOC interrupt is called multiple times per transmission - so the user must still decide if they need to handle the message?
Even the single interrupt doesn't quite answer all the problems - repeat comes very quickly after a code - something like skip track would need some extra logic to avoid whizzing through a CD?
Hi Jorgen, Yes I am.
I have fixed the bugs and added new functions:
IsDataDetected() Used with a decision branch (True is data detected) don't need to keep printing data until data is received.
ClearDataDetected() Used to clear isDataDetected()
IsRepeat(). Value is 1 is a button is being held down.
Component update can be found on my initial post.
I have modified your project with the new functions
In the likely event our remotes don't share the same codes, disable the switch command and enable the calculation command.
Press button 0 and note the value.
Repeat until button 9.
Edit the switch command with correct values for all the buttons.
Enable swich command and disable calculation command.
I’ve made a few small changes to the program, including adding an output that I can turn on with 0 (22) and turn off with 1 (12), just for testing purposes. Now I have to remote everything
In your examble, I change the device to an Arduino Uno an add an I2C display and toggle the Uart, but get error in compiling. I see that it is something to do with the timer, I also try to change to other, what have I forgotten, have I to start with a new project wih an arduino