Lesson 02 - Wirenboard "Debug console and soft foe work"

Опубликовано: 21 Июнь 2026
на канале: Wirenboard SetPoint
14,483
185

Hello again dear colleagues! At today's video tutorial, we will consider the possibility of connecting to the controller via serial port, аs well

as connecting the controller itself to the local network via WiFi.

• Text: Connect to the serial port via WiFi.

• First, let's take a USB cable with a micro USB connector on the end. We connect this connector to the Debug Console of the controller and now we need to determine the device manager which of the virtual com-ports of the computer has assigned to our controller.

To do this, we type the «Device manager» in the search, open our Device manager in the "serial ports" section and there we see number of the serial connection, assigned to our controller. Serial port: COM8. In the future, when setting up the program input, we will use this value.

• Text: Download PUTTY

• When controller is connected to the serial port, we need to download a program what will display information on this serial port. To do this, type PUTTY in the search bar.

We select the site the program is located and go to the download page. Here we select the proper version we need to boot. 32-bit Windows - PUTTY-07, 64-bit - PUTTY-64. Start the download.

Install this program.

• Text: Connecting the PUTTY program

After the program is installed, let's launch it. Go to the main menu of the PUTTY program, launch ... In the settings window select the Port “Serial”.

As you remember, we set the virtual port COM8 and do not forget to change the “Speed”: 115200. After that, just click “Open” and the terminal window opens. After the terminal window has opened, we can turn on our controller.

We observe initial loading progress in the terminal window. And now we are waiting for the moment when the system prompts us to enter login, password, in order to carry out terminal commands. The program loaded quickly enough and now we need to type in the login field in small letters “root”. And the password is “wirenboard”, also in small letters.

That's all, we are in the command line interface. Now configure the WiFi interface. To do this, type “mcedit” and the path to the file in which these settings situated.

Open, find these three lines, substitute the “#” sign in order to comment it. But uncomment these three lines, so that you can substitute WiFi connection parameters.

In the first line of the WPA-SSID, we type the name, in my case it is “Keenetic-7861”, and in the second, we type in the password.

After we checked whether we entered everything correctly, press F10, confirm the save. And we can do a reboot.



After reboot we can check. In the settings of the router, you should find new device is connected.

Go into the list of devices and you see that among the connected ones, there is a WirenBoard controller. We look at address the router assigned to controller and in a new window we type this address in the address bar: 192.168.1.6.

That's all, now at this address 192.168.1.6 we can both get into the WEB interface and use other programs to connect the controller directly from the workstation.

Text: Connecting WINCSP

The next program that will be useful to us for working with the controller is a program for accessing files located in the Linux operating system of the controller.

In my case, it is WINCSP

We type in the search line WINCSP, go to their website WINCSP.net

In the download section, choose the latest version of this program and install it.

After installing the program, we launch it. To do this, in the main menu we find WINCSP. In the window that opens, he immediately offers to establish a connection ... For this, the transfer protocol is “SFTP”.

Next in the section “host name” type 192.168.1.6, port: 22. Username: “root”, password: “wirenboard”. After that, click "enter." And in the right pane, we see that we get into the file system of the WirenBoard controller. Pressing the “root” button, and then further through the folders we can find any file that interests us. This is the end, and in the next video, we will consider connecting the simplest devices to the controller I/O and writing scripts to manage it