It is also widely used to program raspberry PI’s and it is on the verge to become available on our small microcontrollers. Has the time come to leave the arduino ide and go on time for a closer look gritty? Youtubers here is the guy, with the Swiss accent, with a new episode and fresh ideas around sensors and microcontrollers. If we trust this Stack, Overflow post Python is a growing language and Adafruit invests a ton of money into their dialect of micro Python. A typical makers perspective is he currently uses. Arduino wants to have fun with programming, but also wants to know about trends. After this video, you should be able to have a solid opinion. First thing. I hope we will not continue religious wars. I firmly believe there is no right or wrong programming language. Everybody can choose and be happy with his favorite by the way, if you know Python, you can skip small parts of the video. Maybe you are interested in how Adafruit implemented the programming interface to these small boards. It is quite interesting, in my opinion, I will cover these three topics and compare them with the current Arduino IDE environment, the language itself, parts of the hardware and programming interface, libraries, documentation and community fun for me means challenges, but not too much hassle, and this is Why I use a de fruits implementation tools and ports for this comparison to make it clear from the beginning, I bought the port’s myself and never had any contact with either fruit up till now, let’s start with the languages.
There are two significant differences between Python and C the language used in the arduino ide. If you look at the code, python looks more like an english text and c used in the arduino ide looks more cryptic. Python often is considered to be a higher level, lang and C, a language closer to the machine. The second big difference is on how these two languages are translated into executable binary commands, which are understandable by our microcontrollers. The sketch in the Arduino IDE is stored on our PC and it uses a compiler which also runs on our PC. Every time we hit upload, it takes some time to create a binary file which then is uploaded by a serial connection to the microcontroller. The flash memory of the MCU is completely overwritten every time we upload new code. As we all know, this takes time, especially if we forgot to choose a high speed for serial micro Python, on the other hand, runs on the microcontroller itself, not on the PC. It has to be installed before we can start and it stays there as soon as we change our code micro Python takes it, translate it into a bytecode and stores it in RAM also on the MCU micro Python then executes this bytecode from RAM. This is why the size of RAM is far more critical for micro Python than for C. Does all of that make a difference. Yes, a big difference. Micro Python behaves very much like an interpreter language.
You properly work with the board. We also need software on our PC. Adafruit recommends mu. I hope I pronounced it right for that purpose by the way mu is free, open source and also be used for other processes and is also written in Python. Mu has a code selection and a serial monitor in one window, similar to the Arduino IDE. To get you an impression on the two languages, I use a standard blink program, we all know the C code, it consists of a setup and a loop part in setup. We define the pin mode and in the loop we write to this pin and wait for a period. How does that code locate Python? We first have to import some libraries that we can use the hardware of the board. Then, as without you we’ll know, we define the pin and the pin mode here called direction. There is no setup or loop. This wild statement creates a indefinite loop and we do not have any curly braces Python reads the code as we would read a text. All intended code belongs to the while loop. We also need for statements in the loop one thing we do not need in Python. The declaration of variables in C we first have to declare a variable as int, float, etc. Python does not require this step. This might be easier for beginners. For me, there is no significant difference between these two examples. I can live with both for a beginner.
It might be a little more comfortable without the curly braces. In my opinion, there are more important differences, as we will see later. The name of the code is code, dot py, because this is the code circuit. Python starts after boot. As soon as we press save the LED starts to blink much much faster than without we know if we change the timing and press safe again, it is immediately applied cool. If we want the debug message, we enter a print statement and hit safe and it immediately shows in serial monitor extremely cool. All this is possible because of this small disk, which is created by the feather Express port move, only saves the file on the disk and python on the board restarts with a new sketch. As soon as it is changed. The libraries and everything else stays on the MCU for the whole project. We cannot discuss micro python without mentioning ripple. This is the abbreviation of read eval print. This is the normal user interface for micro, python and with other boards. We would have started with this ripple because they do not offer a disk on these ports. The code is uploaded to the board using ripple we get to rebel if we press control C and we get back to program execution by pressing control D in ripple, we work directly with the board and can, as shown before, directly execute commands. For example, we can import the board’s library and then display all available pins with a command tear port for sure this is faster than the Arduino programming cycle, where we always have to compile and upload whole coat.
One of the worst chapters of C in the arduino ide, especially for beginners, is string. Handling dealing with strings is hard for non programmers like me, especially if you have to deal with libraries which are written by real programmers and where pointers come into play. String handling was not important in the old days when we wrote code to manage pings, but today, with all the user interfaces and the connectivity we more and more have to deal with strings even when we call web services and decode the answer. For me, this is definitely easier in Python. It does more or less what you expect similar to the string type in Arduino let’s be T equals one two, three, four, five, six, seven, eight nine. If we want a substring, we only write this command. If we want to find the number three, the command is like that. We can combine the two and type this command which returns 1, because 3 does not appear in position 4 to 8 let’s, take a more complicated string and define T equals gear port. We can print it without Sprint, F, conversions, and if we print t5, we get a surprising result. Python did not store the pins as a string. It saved it as a list interesting. Of course, there are much more differences and details to be mentioned, for example, also that python has a garbage collector, which frees unused memory, but this is stuff for other channels and maybe even for another video on this channel.
The next big thing is libraries, a big plus for the arduino platform, because we find a library for most of our devices. Quite a few of the well known libraries come from Adafruit and they did an excellent job in porting. Many of those libraries to circuit Python. For the moment, I do not know if micro Python libraries are compatible with circuit Python, but you also find a lot of libraries for micro Python, but still Arduino is ahead and you have to check for the needed libraries before you start your project by the way On the Express sports, you can load all available Adafruit libraries, including all example, files on the board and keep it there for the whole project. There is enough space available like that. You do not lose any time to search for or upload if you need a new library in your code. What about documentation and support the documentation of circuit Python and its hardware is excellent. It only took me a few minutes to get everything up and running when I started, I downloaded the wrong initial file for my board and just got a disk space of 50k. This gave me the opportunity to test the support. I went to Adafruit a skort channel and got help in less than five minutes. This channel seems to be very active with lots of users summarized the decision of Adafruit to use this m.d processors with native USB support increases the usability of Python on micro processors, especially for beginners, and it raises the comfort and development speed for the rest of us.
The most significant difference between circuit Python and the Arduino IDE is the fact that Python behaves like an interpreter language. People in my age might be reminded at our beginnings with basic, just without the go to statement and without line numbers. Python is considered to be a higher level language than C, which means that it has some powerful commands which have to be explicitly programmed in C. On the other hand, circlet Python needs more resources and runs slower than C, especially Ram can become an issue. This is why I would not run it on an esp8266. I would start with an ESB 32 with PS run. A version of micro Python exists which can use PS Ram. The code structure in both languages is very similar. Micro Python reminds me more of English C looks more like code. Arduino has much more available. Libraries Arduino IDE supports many ports, especially the esp8266 and the ESP 32 circuit python. For the moment, melee runs on a de fruits hardware. They ported it to the esp8266 and planned to port it. On the Nordic, NRF 52 platform may be expressive. Looks at these Sam D chips and adds a USB interface to their ESP 32 chips as well, who knows micro, Python is also ported to a few other platforms. The documentation of circuit Python is proper, and the support on this court was good for me. The main reason for starting this endeavor was the announcement that Adafruit wants to port circuit Python.
On the Nordic platform, viewers know that I am disappointed about the ble performance of the ESP 32 with the arduino ide. I will closely monitor the development of this branch, as these nordic chips are very good on ble and I’m still interested in this technology. Most probably, this was not the last time you heard of micro Python on this channel. What is your experience with micro or circlet Python? Do you use it and on which platform, or do you have plans to use it in the future? I hope this video was useful, or at least interesting for you. If true, please consider supporting the channel to secure its future existence, you find the links in the description.
arduino python Video
arduino python news
Posted on Friday September 06, 2019The Top Programming Languages 2019 IEEE SpectrumPython remains the big kahuna, but specialist languages hold their own. … Continue Reading »
Posted on Tuesday September 10, 2019Training in Arduino basics for students The HinduThe Innovation Hub of the Regional Science Centre, Kozhikode, is organising a three-day workshop titled “Arduino for school students”, from September 13 to … … Continue Reading »
Posted on Saturday August 24, 2019WiringPi – Deprecated iProgrammerOpen source is wonderful – except when it isn’t. The latest mini-disaster, let’s not get carried away, is that the creator and maintainer of wiringPi has given up, … … Continue Reading »
arduino python Social