{"id":25923,"date":"2020-03-18T08:43:56","date_gmt":"2020-03-18T08:43:56","guid":{"rendered":"https:\/\/3dwork.io\/configura-y-actualiza-tu-impresora-3d-utilizando-visual-studio-code-y-platform-io\/"},"modified":"2020-10-17T11:02:07","modified_gmt":"2020-10-17T11:02:07","slug":"visual-studio-code-and-platform-io","status":"publish","type":"post","link":"https:\/\/3dwork.io\/en\/visual-studio-code-and-platform-io\/","title":{"rendered":"Configure and update your 3D printer using Visual Studio Code and Platform.io"},"content":{"rendered":"

I recently had to upgrade a 32bit board (MKS Robin Nano<\/strong><\/a> de MakerBase) to install a Marlin firmware, specifically version 2.0.1. I usually use sublime and the arduino IDE, but this time I set about doing it with Visual Studio Code<\/strong><\/a> and its great extension Platform.io IDE<\/strong><\/a>.<\/p>\n

I had previously heard of it on our Telegram channel<\/a><\/strong>, but had never had the chance to use it. And it certainly seemed like a great way to edit and compile Marlin files.<\/p>\n

So I leave you here a short and quick guide on how to start using it. I hope as always that it can be of use to you.<\/p>\n

[toc]<\/p>\n

 <\/p>\n

Visual Studio Code<\/h2>\n

\"Configure<\/p>\n

Visual Studio Code<\/strong> is a fabulous freeware editor of very light and powerful code. It is oriented to programming languages \u200b\u200bof all kinds (JS, TypeScript, C ++, C #, Python, PHP, etc.). In addition, it includes numerous functions such as code debugging, syntax highlighting, intelligent code completion, refactoring, and much more.<\/p>\n

It is available on the 3 most important platforms that currently exist: Windows (7, 8 and 10), Linux (.deb .rpm and .tar.gz formats), and of course Mac (macOS 10.10+).<\/p>\n

It is not my role, nor that of this mini-guide, to explain all the bonanzas of this great code editor in depth. However, if you want to know more about it and obtain all the information about it, do not hesitate to visit the page official website of the project at this link<\/a><\/strong>.<\/p>\n

Well, the first thing you should do is install this software. Here is the download link for each and every available platform: Download Visual Studio Code<\/strong><\/a><\/p>\n

 <\/p>\n

Installing the PlatformIO IDE extension<\/h2>\n

\"-<\/p>\n

Once we have correctly installed Visual Studio Code<\/strong>, we will run the program and look in the left sidebar for an icon with a kind of Puzzle (as you can see in the image above)<\/p>\n

With this we will access the section where Extensions<\/strong> are administered. There we will go to the search box, enter the name “PlatformIO IDE<\/strong>” and wait for it to appear in the list. Then we will select it and press the “Install<\/strong>” button to begin the installation process.<\/p>\n

The installation time will depend on your computer and the operating system you have. It will take a little while, so be patient and wait for it to finish completely. Once finished, the software itself will notify you with a message in the lower right part “PlatformIO IDE has been successfully installed! Please reload window<\/strong>“.<\/p>\n

In case you don’t have Python installed, Visual Studio Code will ask you to install it, as it is completely necessary for this extension. You should see a message like this “PlatformIO: Can not find working Python 2.7 or 3.5+ Interpreter. Please install the latest Python 3 and restart VSCode<\/strong>“. And it will offer you the possibility of downloading it by pressing a button, click on it, download the software and install it.<\/p>\n

 <\/p>\n

Uploading our Marlin Firmware<\/h2>\n

\"Actualiza<\/p>\n

With Visual Studio Code <\/strong> and the Platform.io IDE <\/strong> extension fully installed and functional, we can start messing with our Marlin firmware. To do this we will start the application, and in the upper part we will look for a tab called PIO Home <\/strong> (just to the right of the Welcome<\/strong>).<\/p>\n

If we click on this tab, PlatformIO <\/strong> will welcome us and show us several quick access buttons (Quick Access<\/strong>). Among them we will find one that says “Open Project<\/strong>” and we will click on it to search for our project, which in this case will be a Marlin firmware to edit and \/ or compile.<\/p>\n

Remember to have unzipped the Marlin firmware, in case it was just downloaded, since what we are going to select here is the containing folder, and not the project file as we did with the official Arduino compiler (Arduino IDE).<\/p>\n

 <\/p>\n

Setting up our project<\/h2>\n

\"Actualiza<\/p>\n

Now comes the time to configure our Marlin firmware for the mechanics of our printer, and with the options that we obviously want.<\/p>\n

To do this, we encourage you to read our article Complete guide: Configure Marlin 2.0.x from scratch and not die trying<\/a><\/strong>, which I wrote a few weeks ago and which will be of great help if you have no previous experience compiling Marlin.<\/p>\n

If you already have the firmware configured to your liking (and that of the demanding printer), it only remains to select the microprocessor on which we are going to work, which can be 8-bit or 32-bit. To do this, inside the Marlin project folder, we will find and edit a file called “platformio.ini<\/strong>“.<\/p>\n

In this file we will indicate what type of microprocessor our electronics has, so the compiler can prepare the firmware to work on it without any problem. For this we will look for the following lines:<\/p>\n

\r\n[platformio]\r\nsrc_dir      = Marlin\r\nboards_dir   = buildroot\/share\/PlatformIO\/boards\r\ndefault_envs = megaatmega2560\r\ninclude_dir  = Marlin\r\n<\/pre>\n
 <\/p>\n
Where default_envs<\/strong> appears, you must indicate the microcontroller of your electronics. In this particular case, I have an MKS Gen v1.4 from Makerbase, and that is why the value “megaatmega2560” is configured.<\/p>\n
You should discover what microcontroller use your electronic board for fill it in default_envs<\/strong>. Otherwise it will show you an error during the compilation process.<\/p>\n
I leave here a list with some of the most common microprocessors and the value to indicate in that variable. There are more, so check the “platformio.ini<\/strong>” file if yours doesn’t appear here.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
MICROCONTROLLER<\/strong><\/span><\/td>\nENV_DEFAULT<\/strong><\/span><\/td>\n<\/tr>\n
Arduino Mega 2560 (8-bit)<\/td>\nmegaatmega2560<\/td>\n<\/tr>\n
Arduino Mega 1280 (32-bit)<\/td>\nmegaatmega1280<\/td>\n<\/tr>\n
Arduino Due<\/td>\nDUE<\/td>\n<\/tr>\n
SKR v1.4
\nRe-ARM Board
\nMKS SBASE 1.3<\/td>\n		LPC1768<\/td>\n<\/tr>\n
SKR v1.4 Turbo
\nPanucatt Azteeg X5
\nSmoothieboard 4x<\/td>\n		LPC1769<\/span><\/td>\n<\/tr>\n
MKS Robin<\/td>\nmks_robin<\/span><\/td>\n<\/tr>\n
MKS Robin Nano<\/td>\nmks_robin_nano<\/span><\/td>\n<\/tr>\n
RAMBO (8-bit)<\/td>\nrambo<\/td>\n<\/tr>\n
Melzi y clones<\/td>\nmelzi<\/td>\n<\/tr>\n
Sanguinololu (ATmega644p)<\/td>\nsanguino_atmega644p<\/td>\n<\/tr>\n
Sanguinololu (ATmega1284p)<\/td>\nsanguino_atmega1284p<\/td>\n<\/tr>\n
FYSETC S6 (STM32F446)<\/td>\nFYSETC_S6<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
Compiling and uploading the firmware to our printer<\/h2>\n
\"Actualiza<\/p>\n
And finally, we come to the simplest part of the article, compiling and uploading our custom firmware to the 3D printer. So let’s get to it!<\/p>\n
 <\/p>\n
8-bit electronics<\/h3>\n
In 8-bit plates we must click on the icon of the “martian” or “dragonfly” (I have no idea what the hell it is). This is in an icon bar on our left, and is positioned below the icon that we used previously to install the “PlatformIO IDE<\/strong>” extension.<\/p>\n
\"-Once we have clicked, another bar (somewhat wider) will appear on its right with the different compiler options. In the PROJECT TASKS<\/strong> section, we will press the “Build<\/strong>” option to compile the firmware.<\/p>\n
The compiler will start working, and we will only have to wait for it to finish. On my Windows 10 computer with an i7 (1st generation) microprocessor it usually takes just over a minute. Needless to say, if we have something wrongly configured, the compiler and Marlin’s “SanityCheck.h<\/strong>” will give us a compilation error and exhaustive information about the problem.<\/p>\n
Finally, if we want to upload the compiled firmware to our printer, we will press the “Upload<\/strong>” option. Remember to have plugged your board into the computer via USB, otherwise you will not be able to connect and finish the process.<\/p>\n
 <\/p>\n
32-bit electronics<\/h3>\n
For 32-bit boards, we will follow the same process to compile. Click on the “martian”, and then on the option “Build<\/strong>” in the same way that we did in the 8 bits.<\/p>\n
But in this case we will not use the “Upload<\/strong>” option to upload the file to the board, since normally in 32-bit electronics the generated file (Firmware) is usually copied to an SD Card. Then you insert the SD Card in its corresponding slot and after feeding the board, it will detect a new firmware and update itself automatically during the power-on process.<\/p>\n
For this to happen, we will copy our generated firmware to the card, and we will find it in the following path of our Marlin project: \\.pio\\build\\mks_robin_nano\\firmware.bin<\/strong><\/p>\n
 <\/p>\n
 <\/p>\n
And well, this is it for now. I don’t want to get too long since I promised you that it was only a mini-guide on how to use Visual Studio Code and Platform.io. As always, if you have any questions, do not hesitate to join our Telegram channel<\/a><\/strong>.<\/p>\n
 <\/p>\n
If you wish, you can find other interesting articles in 3DWork at the following links:<\/p>\n