Normal people make their requirements based on what they want to do, not what they want to use

But if you changed compilers and messed with opcodes, that almost certainly means you're stuck with the processor you did that for and the language that compiler is made for...

@steve933 you should be good to go now. Let me know.

@TMX I'm looking into it!

una volta che ne colleghi uno come ad esempio in questo link dove viene usato proprio un motorino come il tuo ripeti le stesse cose utilizzando altri tre mosfet e altri tre pin pwm di arduino e sei a posto.

Ah sorry about the emoticons, I'll stop with them.

@septillion I have such specific requirements because it's a project I've been really thinking about for a long time now, I actually had even more specific requirements but lightened up on them when I posted here. For example I did modify a compiler locally on my computer to produce a custom opcode range with features added and others removed specifically tailored for my alarm clock that I was going to look into possibly ordering one day in the future from a manufacture. The custom processor with custom opcodes was more realistically based on an existing processor, just very stripped down, and after studying how other companies order custom processors that strip them down or add new features.

Also I did plan to have actual cartridges instead of an SDCard but I was trying to lighten up the requirements before posting on here (Details below)

I am very competent in C++, it was my 2nd programming language I learned and one one that I chose to really move to advance level before eventually deciding to move to other languages

@PaulRB I'm sorry, this is my first project so perhaps I should have gone a different route for it, in software I'm used to planning everything out in detail before implementing it but hardware I suppose is completely different then.

I find the old cartridge stuff from before I was born so absolutely fascinating for the different gaming devices, the idea that the console, whatever it is, would run some initial boot stuff and then transfer control over to a cartridge. I would love that in a simple alarm clock, the idea that you can just load an "Alarm Clock" ROM onto an sdcard to simulate a cartridge and insert it into an alarm clock to run it but in reality it would just be a generic device with an old retro LCD and simple buzzer sound but the freedom to make an "Alarm Clock" however you want in a device with such capability or even to make something completely different from an alarm clock absolutely intrigues me.

I never knew about not being able to run code off the SDCard, I knew that people designed custom cartridges for existing gaming systems both old and new such as the DSI that has an SDCard adaptation cartridge which code runs off of but perhaps I'm misunderstanding this for the Arduino.

@ChrisTenone I am very interested in older hardware before I was born so I guess I kind of live in that world a bit too much. Also is ROM not the same as EEPROM or is EEPROM easier to alter than older ROM styles. That would make sense though for modern computers I would imagine.

So your suggestion would be to pick a random Arduino board and just have fun and learn hardware getting used to the waters first doing random examples or tinkering in code before jumping in to a more complex project.

Thank you for everyones help so far

        currentState = stoprobot;      //Nächste Bewegung - Bewege zu...

After stopping the robot what do you want it to do ?  I assume that it should move forward as you are calling the forward() function so the next state should be FORWARD.