Interesting take. The great misconception that Arduino has anything to do with Microcontrollers. All it is, is a build system with a SDK. It is just happenstance that the build system is used for Microcontrollers. There are better alternatives for the build systems.
Your whole comment contradicts itself but yea 👍🏽. Arduino is a bootload and ide for said bootload that is for ….. microcontrollers. You don’t need Arduino to for microcontrollers but you do need microcontrollers/socs for Arduino. This was stated in the video.
Yeah, you bet! I found this after a half hour of trying to find a concrete statement about the kind of languages used in microcontrollers and arduinos, and other clarifications. You had it all!! Subscribed right away. I can tell you’re putting a lot of work into these videos too, which is really cool. I’m starting my own called “I Wonder” to explore science topics. Wish me luck!
@@adamdabomb1113 Send a link and I would definitely be looking forward to your videos. Comments like this means so much, it also shows that this video has a nice "shelf life" cause it was one of my earlier video" all the best on the new channel, youtube can be a struggles but its important to first do it for yourself.
@@JustBarran Hmm right! Definitely still holds a lot of good info. I appreciate you asking about the channel! I'm going to be anonymous for a bit while discovering my style, but I'll be sure to send it later on! Thanks for the support!!
Actually got back my two pis this weeks so definitely some pi projects in the future, not really knowledgeable when it comes to the pis but once I learn enough I’ll definitely make a video
Nice video, what are your views on single-board computers ( such as Raspberry Pi) vs microcontrollers? Edit: Love the editing mainly, might be doing too much segmentation like the end the giveaway and the wrap up could have been one heading so it doesn't seem too choppy. Just like a preference thing on my end probably, don't know if anyone else found that weird.
Love the raspberry PI, love the ESp32 (SoC) even more, I think it depends on the application. A microcontroller is great for small projects so I would use them for led control or something that runs on battery, but with the taking off of the IoT SoCs and single-board computers are much easier to use to get your project off the ground. but they are not power efficient. I can't leave a raspberry Pi outside to run on a battery for 6 months, I would need a big battery. compared to a MCU
Great question, microcontrollers (most arduinos) are more task specific and self contained normally offering lower speed as a trade off for cost via a pi which is a a microprocessor (a more a less full blown linx computer) with some add microcontroller features like gpios and other serial busses. If you want to do a project to control lights then a standard Arduino would be better but if you want to do a project that requires on board high processing like image recognition or a monitor with a gui then a pi would be better. In most cause both can be used to do what the other can but depending on the application their would be trade offs of cost, level of code and time to finish between each product. Hope that helps
I'm not sure I agree with Arduino teaching people to code. If you spend time on the forums you'll find people attempting that ultimately get frustrated. The reason is, they are using C and a microcontroller. Not even that, it's C/C++ with all the ugly stuff hidden from you under a rather thin framework and pretty IDE. That's all well and good until things "don't" work. It is there that you will need to start learning what, exactly the compiler messages, which expect you know what you are doing, mean! C/C++ is not a nice language as it has ZERO forgiveness and zero fucks given. The arduino framework tries to protect you for a lot of it, generating canned errors where it can, saving you the main GCC compiler error. However that all impacts performance and... when things DO go wrong, the code you will experience is the Arduino framework code, which is not pretty or simple and not for beginners. As a vehicle to gain interest in coding, yes. Anyone who takes an interest in coding should, at least, do a few free online courses in normal "high level development" on a normal PC, or RPI, in a language like Python or C#. If you want to return to MCU dev later, the Arduino framework runs on many different controllers, but it is very limited and riddled with "forced conventions" and even peripheral modes/config. It (Standard Arduino) also badly lacks a proper debugger interface. The ability to view registers, memory and instructions and step, inspect, watch and run expressions is HUGELY important, especially if you don't need, want or have a UART terminal to "println" stuff too. That is a habit you need to get away from in favour of automated unit testing, debugger use and on systems with disc space, logs. This is where the less "noob friendly" eco-systems like STM32 and PIC come into play.
I agree with you but, I would say as someone who knows both sides like you it, Arduino is a great entry point and level of abstraction for persons who don’t need to dive deep in C for test/prototyping . No one who is going into programming professionally would be using Arduino for deployment but testing and prototyping sure. As well as those who doing embedded as a hobby don’t really need more than the tools provided by Arduino. Most people on those forums that trying to do their universality projects in Arduino are being advised by professors who don’t know better than the students in those aspects and that is why they are there. I agree if they plan to do more they should dive more into proper IDEs and understand Embedded C from a foundation point of view.
@@JustBarran I don't think we disagree. I just feel it needs to be mentioned that while Adruino lowers that first step to a very accessible level, the next step up from there has not been lowered, at least enough. Using myself as an example. My day job is JavaEE. My C is rusty (not a pun!). I have done arduino sketches quite a few times, usually just to drive some small hardware, but it's been a few years since I did any actual C beyond a "sketch". The first problem (and I see this in the newbies all the time), is when you want to use two different things. You have a tutorial on reading a temp sensor and a tutorial on displaying some text on an LCD, you want to put the two together. This results in the person merging everything from the two example sketches together. In my case this went pretty smoothly, but I have experience, working out when to call each examples setup() stuff and when and how to call BOTH of their loop() stuff in the right order. I know my brother really, really struggled and produced some of the most foul code I have seen. This usually leads to forum posts to get help and this is where the newbies will run face first into that second step. It will be suggested that they split the ino file up into modules to make it easier to read and deal with. Now this opens up the newbie to C and it's linker and managing memory between them, extern defs in headers, allocation in c files etc. That runs them into the differences in C and C++, especially if they use structs or object references between multiple files. All of that stuff gave me a few unwelcome reminders as a slap in the face. Especially the cpp memory allocation and header externs. The other one that threw me a curve ball was structs can be self initializing in C++ but not in C. For me it was just a matter of "Ding!" the memory kicking in as soon as I seen the solution on SO I was like, "Ahh, of course, DOH!". For a newbie hitting that stuff as their "second" step. God help them.
@@JustBarran On the future. Things do look brighter. The gap between MCUs and CPUs is narrowing. The price of powerful, large memory ARM Cortex MCUs is opening up the maker space to where languages like Python and maybe even Java become feasible on matchbox sized dev boards. The ESP32, for example, should run a Micro/Circuit python VM without issue. The RP2040 boards certainly can. This should move the space to a higher level with more management and less traps. The other improvement we are already seeing that can be canned in a way to favour newbies, is RTOS. A newbie friendly RTOS facade will remove most of the problems are the "hot looping, round robin" loop() functions and even the funky merged setups (to a degree).
@@1over137 Don't have a lot of love for Micro python as it is terribly slow. In my option Rust looks to be a better option. Rust is also not prefect. The joke is that all the fancy stuff that python is use for is accelerated with C/C++. All nicely wrapped in a API with a bow on top. Tensoflow is a big one that does this. There are also plenty of traps and pit falls with python, mainly understanding how the interpreter works. Found myself reaching for C every time I wanted to do something related to the IO on a RPI because python was so slow. Don't know about the RTOS since you are introducing resource locks, inter task communication and the concept of stack and heap but having the option to use one would be great. The ESP32 Arduino does have FreeRTOS available. Just no one uses it. I believe that horrid IDE is the core of the issue. Believe there is a new IDE that is being worked on. Integration will always be a problem for newbies regardless of language. Again back to the IDE that does not have basic tool to help you debug.
Paul Land in general terms it is , but in technical terms, the microcontroller is only the IC on the PCB. Arduino isn’t a microcontroller it’s a company that makes software and development boards some of which use microcontrollers.
about time, loving the memes, try and post more consistently plzzzz
MasterBarran I trying, I am my worst enemy
Such a great video!! Can't wait for a next one
Nicholas Singh thanks bro
Gonna watch this later. Favourite channel ever!
u watch it yet?
did you watch it yet?
Well done.
Lyndon Baptiste thanks 🙏
Interesting take. The great misconception that Arduino has anything to do with Microcontrollers. All it is, is a build system with a SDK. It is just happenstance that the build system is used for Microcontrollers. There are better alternatives for the build systems.
Your whole comment contradicts itself but yea 👍🏽. Arduino is a bootload and ide for said bootload that is for ….. microcontrollers. You don’t need Arduino to for microcontrollers but you do need microcontrollers/socs for Arduino. This was stated in the video.
@@JustBarran Not really a contradiction. You can build desktop application with the Arduino build system if you want.
That I didn’t know, interesting 🤔, I stand corrected
This was SO helpful. Thank you!!
I appreciated this comment so much thank you 😊
Yeah, you bet! I found this after a half hour of trying to find a concrete statement about the kind of languages used in microcontrollers and arduinos, and other clarifications. You had it all!! Subscribed right away. I can tell you’re putting a lot of work into these videos too, which is really cool. I’m starting my own called “I Wonder” to explore science topics. Wish me luck!
(My own channel, I mean)
@@adamdabomb1113 Send a link and I would definitely be looking forward to your videos. Comments like this means so much, it also shows that this video has a nice "shelf life" cause it was one of my earlier video" all the best on the new channel, youtube can be a struggles but its important to first do it for yourself.
@@JustBarran Hmm right! Definitely still holds a lot of good info. I appreciate you asking about the channel! I'm going to be anonymous for a bit while discovering my style, but I'll be sure to send it later on! Thanks for the support!!
Do your thing lil cuz 💯
thanks man
Really thank you.
Keep going.
Appreciated, glad it helped
Very Informative video, you should do one with the Raspberry Pi next!!
Actually got back my two pis this weeks so definitely some pi projects in the future, not really knowledgeable when it comes to the pis but once I learn enough I’ll definitely make a video
Nice video, what are your views on single-board computers ( such as Raspberry Pi) vs microcontrollers?
Edit: Love the editing mainly, might be doing too much segmentation like the end the giveaway and the wrap up could have been one heading so it doesn't seem too choppy. Just like a preference thing on my end probably, don't know if anyone else found that weird.
Love the raspberry PI, love the ESp32 (SoC) even more, I think it depends on the application. A microcontroller is great for small projects so I would use them for led control or something that runs on battery, but with the taking off of the IoT SoCs and single-board computers are much easier to use to get your project off the ground. but they are not power efficient. I can't leave a raspberry Pi outside to run on a battery for 6 months, I would need a big battery. compared to a MCU
Yea i understand, I started to rush the ending and I shifted things around, would try to make it cleaner in the next video
I'd like to see some projects please. Maybe even a "how to" vid or an example diy project on getting started with arduino
in the works
Love the italian part 😂😂
🥰 thanks
Just great! Keep it up!
thanks for the feedback Travis
Cool
thanks
Quality editing great video!!
Arch Angel thanks 😊
good work!
vishwarion thanks bro
Great vid! Very informative, great explanations!
I was expecting a sabotage
great vid man
thanks, bro, hope all is well with you, you gone off the grid
Hello. often program the microcontrollers. I see bit shift right or left using symbol ">>". why we use it. I am waiting for your response thank you.
But shifts are used for number of reasons, it a easy way to do Division and multiplication by two. Aka, >> 1, is a devide by 2, and
Thank you very much. I understood the explanation.
Very informative video Christian.
Partsman Electronics thanks, waiting for your next video
Good vid! Its informative but at the same time not information overload
thanks for the feedback Nicholas
Hey Barran, I am new to Iot but i want to start off exploring but confused between Raspberry pi and arduino
Great question, microcontrollers (most arduinos) are more task specific and self contained normally offering lower speed as a trade off for cost via a pi which is a a microprocessor (a more a less full blown linx computer) with some add microcontroller features like gpios and other serial busses. If you want to do a project to control lights then a standard Arduino would be better but if you want to do a project that requires on board high processing like image recognition or a monitor with a gui then a pi would be better. In most cause both can be used to do what the other can but depending on the application their would be trade offs of cost, level of code and time to finish between each product. Hope that helps
Also arduinos mostly use C code vs Pi you would more likely use Python
Shout out to Micro G Unit, greatest rap group
compiling words into fire since 2014
Great video very informative 🔥
Thanks a lot
Who is this sexy RUclipsr
who is this sexy commenter? also what you do you think about the memes
The Italian one kill me
@@14henrylover ahhaha yea that one I add this morning
I'm not sure I agree with Arduino teaching people to code. If you spend time on the forums you'll find people attempting that ultimately get frustrated. The reason is, they are using C and a microcontroller. Not even that, it's C/C++ with all the ugly stuff hidden from you under a rather thin framework and pretty IDE. That's all well and good until things "don't" work. It is there that you will need to start learning what, exactly the compiler messages, which expect you know what you are doing, mean! C/C++ is not a nice language as it has ZERO forgiveness and zero fucks given. The arduino framework tries to protect you for a lot of it, generating canned errors where it can, saving you the main GCC compiler error. However that all impacts performance and... when things DO go wrong, the code you will experience is the Arduino framework code, which is not pretty or simple and not for beginners.
As a vehicle to gain interest in coding, yes. Anyone who takes an interest in coding should, at least, do a few free online courses in normal "high level development" on a normal PC, or RPI, in a language like Python or C#.
If you want to return to MCU dev later, the Arduino framework runs on many different controllers, but it is very limited and riddled with "forced conventions" and even peripheral modes/config.
It (Standard Arduino) also badly lacks a proper debugger interface. The ability to view registers, memory and instructions and step, inspect, watch and run expressions is HUGELY important, especially if you don't need, want or have a UART terminal to "println" stuff too. That is a habit you need to get away from in favour of automated unit testing, debugger use and on systems with disc space, logs. This is where the less "noob friendly" eco-systems like STM32 and PIC come into play.
I agree with you but, I would say as someone who knows both sides like you it, Arduino is a great entry point and level of abstraction for persons who don’t need to dive deep in C for test/prototyping . No one who is going into programming professionally would be using Arduino for deployment but testing and prototyping sure. As well as those who doing embedded as a hobby don’t really need more than the tools provided by Arduino. Most people on those forums that trying to do their universality projects in Arduino are being advised by professors who don’t know better than the students in those aspects and that is why they are there. I agree if they plan to do more they should dive more into proper IDEs and understand Embedded C from a foundation point of view.
@@JustBarran I don't think we disagree. I just feel it needs to be mentioned that while Adruino lowers that first step to a very accessible level, the next step up from there has not been lowered, at least enough.
Using myself as an example. My day job is JavaEE. My C is rusty (not a pun!). I have done arduino sketches quite a few times, usually just to drive some small hardware, but it's been a few years since I did any actual C beyond a "sketch".
The first problem (and I see this in the newbies all the time), is when you want to use two different things. You have a tutorial on reading a temp sensor and a tutorial on displaying some text on an LCD, you want to put the two together.
This results in the person merging everything from the two example sketches together. In my case this went pretty smoothly, but I have experience, working out when to call each examples setup() stuff and when and how to call BOTH of their loop() stuff in the right order. I know my brother really, really struggled and produced some of the most foul code I have seen.
This usually leads to forum posts to get help and this is where the newbies will run face first into that second step.
It will be suggested that they split the ino file up into modules to make it easier to read and deal with.
Now this opens up the newbie to C and it's linker and managing memory between them, extern defs in headers, allocation in c files etc.
That runs them into the differences in C and C++, especially if they use structs or object references between multiple files.
All of that stuff gave me a few unwelcome reminders as a slap in the face. Especially the cpp memory allocation and header externs. The other one that threw me a curve ball was structs can be self initializing in C++ but not in C.
For me it was just a matter of "Ding!" the memory kicking in as soon as I seen the solution on SO I was like, "Ahh, of course, DOH!". For a newbie hitting that stuff as their "second" step. God help them.
@@JustBarran On the future. Things do look brighter. The gap between MCUs and CPUs is narrowing. The price of powerful, large memory ARM Cortex MCUs is opening up the maker space to where languages like Python and maybe even Java become feasible on matchbox sized dev boards.
The ESP32, for example, should run a Micro/Circuit python VM without issue. The RP2040 boards certainly can.
This should move the space to a higher level with more management and less traps.
The other improvement we are already seeing that can be canned in a way to favour newbies, is RTOS.
A newbie friendly RTOS facade will remove most of the problems are the "hot looping, round robin" loop() functions and even the funky merged setups (to a degree).
@@1over137 Don't have a lot of love for Micro python as it is terribly slow. In my option Rust looks to be a better option. Rust is also not prefect. The joke is that all the fancy stuff that python is use for is accelerated with C/C++. All nicely wrapped in a API with a bow on top. Tensoflow is a big one that does this. There are also plenty of traps and pit falls with python, mainly understanding how the interpreter works. Found myself reaching for C every time I wanted to do something related to the IO on a RPI because python was so slow.
Don't know about the RTOS since you are introducing resource locks, inter task communication and the concept of stack and heap but having the option to use one would be great. The ESP32 Arduino does have FreeRTOS available. Just no one uses it.
I believe that horrid IDE is the core of the issue. Believe there is a new IDE that is being worked on.
Integration will always be a problem for newbies regardless of language. Again back to the IDE that does not have basic tool to help you debug.
Errrr Arduino IS a microcontroller !!!!!!!!
Paul Land in general terms it is , but in technical terms, the microcontroller is only the IC on the PCB. Arduino isn’t a microcontroller it’s a company that makes software and development boards some of which use microcontrollers.