GoForSmoke:
perkunas:
2)Halfway through the program I found it impossible to multithread and multitask, something you want to do after your 1st blinky.
Oh sure you can write a state machine, or some other trick but that's not true multitasking, confusing totally impractical.Yet another modern PC programmer who does not understand state machines. No surprise there.
What Mike said, you need multiple cores to do "true multitasking". Which is possible with Arduino when you add MCU's... I'd go for SPI or I2C bus and some extra 1-wire bus comms as needed but the real question is why for a task like yours? Organized and written properly it should be well within the capabilities of an Arduino.
No, you don't need multiple cores to do "true multitasking". You just need enough memory to allow each thread to run in its own stack frame, and something to do the switching. There are various thread models that use cooperative threads.
That assumes you are in control of all of the software, and don't use pre-written libraries that use delays. For example as say the Morse code library and the IR library both do, and which I want to marry together (I have a camera shutter release, that wants to fire off a message in Morse code, but I want to be able to stop the beeping if I get a button press, either a direct button or a button with an IR transmitter). Yes, I eventually will take the source to both, and rewrite them to use state machines, but it would have been a lot simpler if I didn't have to write everything from scratch, and I can just use the libraries as is. Both state machines and threads are tools in the toolbox. Sometimes one is better than the other.