Robotics University

Home Automation | Onboarding Home Assistant (Create Account)

noreply@blogger.com (Taufiq D.S. Suyadhi) — Thu, 09 May 2019 13:42:00 +0000

robotics-university.com | On my previous article, I have written about how to Home Assistant installation. On this article, I will continue my explanation about onboarding Home Assistant before use it to awaken your own home automation project. So, continue to read this article!

Step 1: Create Account on Home Assistant

In order you can work with Home Assistant, you have to create your account there. Type your name, Username, and Password in the available field, then press “Create Account” button (see figure 1).

Figure 1. Create your account on Home Assistant sign-up page

Step 2: Determine Your Home Name & Detect Its Location

Next, give your home name on the available blank field, then click “Detect” button to set your location, time zone, and unit system. Your time zone and unit system will set based on your location automatically (See figure 2 and figure 3).

Figure 2. Determine your home name and detect its location

Figure 3. Your home location, time zone, and unit system information

After that, click “Next” button and on the next page, you will see some devices that it has discovered on your network. Don’t be worry if on your screen there is no showed any devices, but just “More” button as shown below (Its means that your Home Assistant account is in initial using). You can manually add your needed devices later (See figure 4).

Figure 4. Home Assistant account has created

Click “Finish” button to finished your Home Assistant account setting.

Step 3: Home Assistant Configuration

Once you click the “Finish” button (On the previous step), you will see your Home Assistant user interface (See figure 5).

Figure 5. Your Home Assistant user interface (Default view)

On your Home Assistant user interface, click “Configuration” option to open Home Assistant configuration page (See figure 6).

Figure 6. Home Assistant configuration page

On the Home Assistant configuration page, you will see some menu that have function to configure your home automation user interface features (See figure 6).

Step 4: Add “Integrations” on Your Home Assistant User Interface

The early step to awaken home automation user interface is add and setup the needed integration.

Figure 7. Integration page (Add integration)

To do so, click + button on the right-lower corner of integration page (See figure 7).

Figure 8. Click a new integration - Blink (for example)

Then select one integration that you need. For example, select Blink integration (See figure 8).

Figure 9. A new integration, in progress prepared (for example)

Wait for a moment, when the new integration, in progress prepared (See figure 9).

Figure 10. Setup the new integration - Blink (for example)

After the integration preparation has finished, then set the new integration parameters needed up. The setup parameters of one integration with one another integration, may be different.

Until this point, you have finished to onboarding your Home Assistant. Continue some steps, so you can get started awaken fully your own home automation projects.

Source:

[1] https://www.home-assistant.io/

[2] https://www.home-assistant.io/getting-started/

Home Automation | How to Install Home Assistant on Windows 10 Computer

noreply@blogger.com (Taufiq D.S. Suyadhi) — Tue, 07 May 2019 00:02:00 +0000

robotics-university.com | Hello my friends, hope you always in good condition. Today I will continue talking about Internet of Things (IoT) or in proper is Home Automation. Two topic that is the most popular talked by peoples on the last several years.

Today, I will talk about Home Assistant, Open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server [1].

In order you can use it, you have to install it on your Raspberry Pi single board computer (SBC) or on your computer local server. But on this article, I will give you guide to install Home Assistant on the local server of Windows 10 computer.

Step 1: Visit the Home Assistant Official Website

First, visit the Home Assistant official website (https://www.home-assistant.io/), then select “Get Started” menu to get the installation guidance (See figure 1 and figure 2).

Figure 1. The Home Assistant official website front-page

Figure 2. Installation guide of Home Assistant

Read the guidance and follow the Home Assistant installation steps there. But unfortunately, there is available installation guide on Raspberry Pi SBC only. If you have Raspberry Pi, follow the guidance. But if you don’t have and want to install Home Assistant on Windows 10 computer, please continue reading this article.

Step 2: Download and Install the Latest Version of Python

For your information: To install Home Assistant on Raspberry Pi SBC or Windows 10 computer, installed Python on your devices are needed. Python on Raspberry Pi is ready to use in default, but on Windows 10 computer isn't, so for your Windows 10 computer, you have to install Python first before installing Home Assistant.

Get the latest Python installer file from the Python official website by click this link, here (See figure 3). Save it into a folder/directory in your computer.

Figure 3. Python download page

To start install Python on your computer, just double-click the execute (exe) file, see figure 4.

Figure 4. Python installer file (exe) on a file storage directory

If an installation section window as displayed on figure 5 opened, before you click “Install Now” option, don’t forget to check on “Add Python x.x to PATH”

Figure 5. Python installation section window

After you have clicked “Install Now” option, the Python installation will run (See figure 5). Wait until the process complete (See figure 6 and figure 7).

Figure 6. Python installation is in progress

Figure 7. Python installation was complete

If the installation process has been completed (See figure 7), press “Close” button as the end of the Python installation step.

Step 3: Install Home Assistant Using Command Prompt Window

To install Home Assistant on a Widows 10 computer, it can do with aided by command prompt window (See figure 8).

Figure 8. Step to open Command prompt windows

Type “cmd” into the search box of your Windows 10 computer then press enter key or you can use shortcut-key, Windows key + R, then press enter key. The opened command prompt window shown on figure 9.

Figure 9. Command Prompt windows

A. Command to install Home Assistant

To get started install Home Assistant on your windows computer, type the command below:

pip3 install homeassistant

Before you press enter key of your keyboard, make sure that your computer connects with internet network.

Figure 10. The Home Assistant installation is on process

Once you press enter key on keyboard, the Home Assistant installation process will run (See figure 10).

Figure 11. The Home Assistant installation process has done

After a while, the installation process will be end (See figure 11)

B. Command to check Home Assistant package information

To make sure that Home Assistant has installed on your Windos 10 computer, you can check it. Type this command below to do so:

pip3 show homeassistant

Figure 12. The Home Assistant package information

Once you type the command above and then press enter key, on command prompt window will show package information of installed Home Assistant on your computer (See figure 12).

C. Command to open Home Assistant User Interface (UI)

Next, in order you can create an account on Home Assistant, you have to open the web-based user interface (UI). To do so, type the command below, then press enter key on your keyboard.

hass --open-ui

Figure 13. Command to install Home Assistant user interface (UI)

Once you press enter key, on your internet browse will open Home Assistant web-based user interface (Sign-up page) automatically (See figure 14).

Figure 14. Home Assistant web-based user interface (Sign-up page)

Looks at on the Home Assistant web-based user interface! “127.0.0.1“ is my computer IP address. Your computer IP address may be different (see figure 14).

Note:
When you run hass --open-ui command to open Home Assistant web-based user interface (UI), but there is error occur, type this command below:

C:\Users\admin\appdata\local\programs\python\python38-32\python.exe -m homeassistant (Change “admin” with your computer username) or type enough python -m homeassistant

After that if Home Assistant web-based user interface (See figure 14) not open automatically, open it with type on your internet browser one of the web-page URL below manually:

URL 1 = http://homeassistant.local:8123
URL 2 = http://homeassistant:8123 (for older version windows)
URL 3 = http://X.X.X.X:8123 (replace X.X.X.X with your computer IP address)

If there is no error occur again, the Home Assistant web-based user interface will open for you.

Yeah … great!

If you have reached on this point, its means that Home Assistant has installed on your Windows 10 computer now. Congratulation!

Next, you have to create account on Home Assistant web-based user interface (Onboarding) before you awaken your own home automation projects.

Sources

[1] https://www.home-assistant.io/

[2] https://www.home-assistant.io/getting-started/

Internet of Things | Monitoring Sensor and Controlling LED on Ubidots Dashboard Using MQTT Protocol

noreply@blogger.com (Taufiq D.S. Suyadhi) — Sun, 05 May 2019 03:25:00 +0000

robotics-university.com | Hello my friends, on my previous article, I have explained about MQTT protocol. On this article, I will try to give you an example of MQTT protocol use in a simple Internet of Things (IoT) project.

Today, I will guide you to know: The first, how to publish sensor data to IoT cloud platform, then monitor the real-time sensing data on the cloud platform dashboard. The second, how to subscribe (receive) instruction from IoT cloud platform dashboard. For the protocol, I use MQTT protocol. For this project, I use Ubidots cloud IoT platform (www.ubidots.com). To know the details, continue read this article and follow all of the steps for your practice.

Project Description

On this project, we will try to publish Hall-effect sensor (that built-in on ESP32 board) data and control internal LED of ESP32 board on Ubidots dashboard. Figure 1 is the block diagram of the project system.

Figure 1. Project block diagram

Hardware Needs

ESP32 DevKit V1 board (Include internal LED and Hall sensor)
USB cable
Jumper cables

Software Needs

Arduino IDE
Arduino IDE - Serial monitor
Library (PubSubClient, WiFi)

Step 1: Create Account on Ubidots Website

Ubidots provide free cloud storage for everyone that want to try built an IoT project for learning or prototyping purpose. To get started create an Ubidots account, visit the Ubidots official website (www.ubidots.com), then click “Get Started for Free” button.

Figure 2. Ubidots official website

After you press “Get Started for Free” button, you will ask to choose two optional Ubidots account, i.e. “For educational or Personal use” (free account) and “For Business.” For this project, just select the free account option (Se figure 3).

Figure 3. Ubidots for Educational/Personal and for Business

Figure 4. Sign up (create account) page of Ubidots official website

Next, input your username, email, and password. Then press “Sign up for free” button and your account will be created and ready to use.

For your information, on the sign-up page, you will know about the Ubidots free account features (See figure 4), i.e.

3 forever free devices.
200+ open source device libraries and tutorials.
Real-time dashboard with 30+ types of widget (and the tools to code your own!).
If-Then triggers with Email, SMS, Telegram, Voice call, Webhooks, or Slack notifications.

For learning or prototyping purpose, perhaps the features of Ubidots cloud platform has been enough. For business or real IoT/Smart Home project, we have to upgrade it to Industrial account version of Ubidots.

Step 2: Login to Ubidots Account

If your account has created successfully, next, login (Sign in) on Ubidots website using that account. See figure 5, figure 6, and figure 7.

Figure 5. Login button on Ubidots IoT clouds platform

Figure 6. Sign in page of Ubidots IoT clouds platform

Figure 7. Ubidots IoT clouds platform page display after login

Step 3: Create Project Device

The early step to make a dashboard on Ubidot IoT cloud platform. You have to create your project device first. Select “Devices” menu, then choose “Devices” option until Ubidots device page opened for you. See figure 8 and figure 9.

Figure 8. Select “Devices” menu

Figure 9. “Devices” page - Create new device

Next, press “Create Device” button on the device page (See figure 9). After that, on the right-side of device page, will open “Add New Device” section. Click “Blank Device.” See figure 10

Figure 10. “Blank Device” button

Figure 11. Type your device name

Then type your device name, so the device label will be generated automatically (See figure 11). Click check button to save your device name and label.

Figure 12. A new device has created

After that, on the device page will be created a new device on the device list (See figure 12).

Step 4: Create Device Variable(s)

After you create your project device, next, you have to create one or more variable that has correlation with your device. For example, on this project you will use ESP32 board and its internal Hall-sensor and LED. So on this case, your ESP32 board is your device, while the internal Hall-sensor and LED are your device variables.

Figure 13. Open device page and create device variable(s)

Click your device name (See figure 13) to open device page and create device variables. Figure 14 show the Ubidots device page.

Figure 14. Device page

Click “Add Variable” button to get started create a new device variable (See figure 14). Once you press the “Add Variable” button, there will show two option of variables, i.e. Raw and Synthetic. Select “Raw” if your variable is for non-arithmetic purpose (No need mathematical formula), on the other hand, if your variable is for arithmetic purpose, you should select “Synthetic.” Because a synthetic variable needs mathematical formula/expression. On this project, we will create non-arithmetic variable, so, select “Raw” type variable (See figure 15)

Figure 15. Variable type (Raw and Synthetic)

After you select “Raw” variable, a new variable box will created on device page (See fiure 16).

Figure 16. Created variable box

Click the variable box to open the variable page (See figure 16) and set the variable parameters (See figure 17).

Figure 17. Parameters setting of a variable

If you have finished on set a variable parameter, click “Back-arrow” to back to device page (See figure 17). A new ready variable has created there (See figure 18).

Figure 18. A new ready variable has created

If you want to add a new variable again, you can add it by click “Add Variable” again and do the same steps on this step (Step 4).

Figure 19. Device variables on this project (Hall sensor & LED)

For this project, we need two variables for one device (ESP32 board), i.e., “Hall Sensor on ESP32” and “LED on ESP32” (See figure 19).

Step 5: Get Your Device Label and Token

To get your device label and token, open your device page and get your both of them on the left-side. See figure 20.

Figure 20. Device token

From figure 20 we know that:

Device label = esp32-iot-board

Device token = BBFF-RPeLfc5xxxxxw7SyyyyyyLlRlxxxxx

Step 6: Get the Variables (API) Label

To get the variables (API) label, open the variable page by click the related variable box (See figure 20) and get your variable (API) label on the left-side of the variable page of each variable (See figure 21 and figure 22).

Figure 21. Hall Sensor - Variable page

Figure 22. LED - Variable page

From figure 21 and figure 22, we know that:

The Hall-sensor’s variable (API) label = hall-sensor-esp32

The LED’s variable (API) label = led-on-esp32

Note for Step 5 and Step 6:

Your Ubidots token, device label, and variable (API) label will be use on your program to make your device (ESP32) can be connected with Ubidots IoT cloud platform, publish sensor data on it, and subscribe command from its dashboard (See Program 1).

Step 7: Create the Project Dashboard and Add the Widget

After your device and its variables ready, next you have to create your project dashboard and its widget. To get started create a new dashboard, click “Data” menu, then select “Dashboards” option (See figure 23). So dashboard page opened for you (See figure 24).

Figure 23. Step to open Dashboards page

Figure 24. Opened Dashboards page

On the dashboard page, click “Add new Dashboard” button. After that, on the right-side of dashboard page, will open “Add New Dashboard” section. Set your dashboard parameters (See figure 25).

Figure 25. New Dashboards parameters setting

If you have finished to set the new dashboard parameters, then click check button to save your setting (See figure 25), so a new dashboard page created for you (See figure 26).

Figure 26. A new Dashboards has created

A dashboard is a graphical user interface (GUI). In order the user can monitor sensor data or control an actuator from the dashboard, so it has to equipped with features or widget (Gauge, switch, clock, double-axis graph, slider, thermometer, scatter, text, tank, battery, and more) to make user can do that.

To get started add a new widget on your dashboard, click “Add new Widget” button (See figure 26). So, on the right-side of your dashboard page, will open “Add new Widget” section or widget list (See figure 27).

Figure 27. Widget list and add “Gauge” widget

Select one or more widget that needed by your system project on the widget list (See figure 27). For this project, you need “Gauge”, so, click Gauge widget. After you click the Gauge widget on the widget list, on the right-side of your dashboard page will open “Gauge” parameter section. On there, determine the widget behavior (Static/Dynamic) and its variable (See figure 28).

This Gauge widget has function to display the Hall-sensor measurement data that published by ESP32 board, so, you have to determine the match variable for this widget.

Figure 28. “Add variable” button

Click the “Add Variables” button (See figure 28), then select the match variable, i.e. “Hall Sensor on ESP32” variable, and confirm your selection by click the green check button (See figure 29).

Figure 29. Select the match variable for your Gauge widget (Hall sensor on ESP32)

If you have selected the match variable, the variable will show on the Gauge widget parameter section (See figure 30).

Figure 30. Gauge widget parameter section

After you have selected the variable, then next set the others parameters with follow the table 1 below.

Table 1. Gauge (Hall sensor) widget parameters setting

Don’t forget to click the green check button to save your Gauge widget parameters setting (See figure 30).

Figure 31. A new widget has created (Hall sensor widget)

Figure 31 inform that Gauge widget (for Hall-sensor) hasn’t been found data, because still on initial condition. The figure also informs that if you want to add a new widget again, press the plus (+) button on the top right corner of your dashboard page.

Figure 32. Add new widget (Switch widget)

For the second widget, you need “Switch” widget, because this widget has function as a switch to control an internal Light Emitting Diode (LED) of ESP32 board.

Figure 33. Select the match variable for your widget (LED on ESP32)

Select switch widget (see figure 32), then determine “LED on ESP32” variable (See figure 33), and set its parameters with follow table 2. Click the green check button to save your widget parameters setting (See figure 34).

Figure 34. Switch widget parameter section

Table 2. Switch (LED on ESP32) widget parameters setting

Figure 35. The two widgets (Hall sensor & LED switch) of this dashboard has created

Finally, your Dashboard has created. The dashboard contains with two widgets, i.e. Gauge widget to display the real-time Hall-sensor sensing data and Switch widget to control internal LED of ESP32 board.

Step 8: Hardware (Device) Installation

The hardware of this project is ESP32 IoT board only. The Hall-sensor and LED have integrated on it. To program this board, you just make connection between this board and your computer/laptop via each USB port.

Figure 36. ESP32 board with internal Hall-sensor & LED

Step 9: Code Building & Uploading

After you have finished create your Dashboard on Ubidots IoT clouds platform, next, build the program (code/firmware) for your Hall-sensor device gateway (ESP32 IoT board) in order it can publish Hall sensor data to IoT clouds platform (Ubidots) and control the internal LED of ESP32 board. Type “Program 1” below in the Arduino IDE or actually copy and paste 😊

Program 1:

When you type your code, don’t forget to edit “Program 1” on the WiFi parameters, Ubidots device parameters, and also on the Ubidots device and variables label sections (See figure 37).

Figure 37. WiFi-Device parameters & Device-Variable label section

Tabel 3. Edit points on program 1

* Please refer Step 5 and Step 6 above.

If you have finished on your program typing and editing, next, compile/verify and upload your program to your ESP32 board. Then test it.

Step 10: Hardware/Device Testing

To test your sensor device hardware, open Serial Monitor that available on your Arduino IDE. Select “Tools” menu, the choose “Serial Monitor” option (See figure 38).

Figure 38. Step to open Arduino IDE serial Monitor

Once you click the “Serial Monitor” option, Serial monitor window will be open (See figure 39). In order you can see some information about your project there, select the baud rate value on the baud rate drop-down (in this case, the baud rate is 115200) and also press “Enable (EN)” button on your ESP32 board.

Figure 39. Hardware testing - WiFi connection and Published sensor data

If there is no error occur, on the serial monitor will display some information as shown on figure 39, i.e.:

Connected WiFi.
WiFi IP address.
Device connection information with Ubidots IoT cloud platform.
Published Hall sensor data.
Info if your system “Publishing data to Ubidots cloud.”

Step 11: Monitoring Hall-Sensor Data & Control LED on/from Ubidots Dashboard

The last step is testing the whole project performance, i.e. Monitoring the Hall-sensor data and control LED on/from Ubdots dashboard.

To make sure that the Hall-sensor data on the Ubidots dashboard and on the actual sensing place (Record on Arduino IDE Serial monitor) have the same value, its better if you compare the data by see the Hall-sensor data side by side. Either on Ubidots dashboard or on Serial Monitor. See figure 40.

Figure 40. Monitoring Hall-sensor data on Ubidots dashboard & Serial Monitor (Compare)

Then to control LED from Ubidot dashboard, try to click the switch widget and see the LED on your ESP32 board, if it light-ON or light-OFF when the switch widget clicked, its means that you have been successful publish command/instruction from Ubidots dashboard (IoT cloud platform) to your device (ESP32 board).

Figure 41. Realtime monitoring Hall sensor & control LED on Ubidots dashboard

Figure 41, showed the real-time monitoring of Hall-sensor data (Hall effect) on Ubidots dashboard and switch widget to control LED.

If you have reached on this point, congratulation!

Its means that you have published Hall-sensor data (also control the internal LED of ESP32 board) to Ubidots IoT cloud platform using MQTT protocol successfully.

Publish DHT22 Sensor Data to Adafruit IO IoT Cloud Platform Using MQTT Protocol

noreply@blogger.com (Taufiq D.S. Suyadhi) — Fri, 03 May 2019 23:21:00 +0000

robotics-university.com | Hello my friends, on my previous article, I have explained about MQTT protocol. Today, I will guide you to know how to publish sensor data to Internet of Things (IoT) cloud platform using MQTT protocol and then monitoring the real-time sensing data on the IoT cloud latform dashboard. For this project, I use Adafruit IO cloud platform (www.io.adafruit.com). To know the details, read this article completely and follow the steps for your practice.

Project Description

On this project, we will build a temperature and humidity wireless sensor device that built with DHT22 sensor module and ESP32 IoT board, so, it has ability to publish the detected temperature and humidity sensing data wirelessly when it placed on an internet network (WiFi).

Figure 1. Project block diagram

The project block diagram as shown on figure 1. On this project, there is a temperature and humidity sensor (DHT22) and ESP32 IoT board that will have function as the system gateway to publish sensing data to Adafruit IO clouds. The real-time sensing data can be accessed by smartphone or computer that has access to login into the Adafruit IO dashboard.

Hardware Needs

DHT22 - Temperature & Humidity sensor module
ESP32 DevKit V1 board
USB cable
Jumper cables

Software Needs

Arduino IDE
Arduino IDE - Serial monitor
Library (SimpleDHT, Adafruit_mqtt, WiFi)

Step 1: Create Account on Adafruit IO Website

Adafruit provide free cloud storage for everyone who want to try built an IoT project for learning or prototyping purpose. To get started create an account, visit the Adafruit official website (www.io.adafruit.com), then click “Get Started for Free” button on the right-top corner and then follow the sign-up steps and requirements. See figure 2 and figure 3!

Figure 2. Adafruit IO official website

Figure 3. Sign up (create account) page of Adafruit IO official website

Step 2: Login to Adafruit IO Account

If your account has created successfully, next, please login (Sign in) on Adafruit IO website using that account.

Figure 4. Sign in on Adafruit IO official website

Figure 5. Sign in page of Adafruit IO official website

After login, we will know that Adafruit IO free account has some limitation.

Figure 6. Adafruit IO free account limitations

For a free account, Adafruit IO has limitation as follow (See table 1):

Table 1. Adafruit IO free account limitation

With that limitation, for learning or prototyping purpose, perhaps the limit feature of Adafruit IO clouds platform has been enough. But for business or real IoT or Home automation project, we have to upgrade it to IO+ version of Adafruit IO (See figure 6 or figure 7).

Step 3: Create Project “Feeds”

The next step is get started to create project dashboard. But before it, you have to create the project “Feeds.” What is Feed? Feed is a variable on Adafruit IO clouds that have function to store data that published by a device (in this case, sensor gateway, i.e. ESP32 board) of a system in data publish operation.

Figure 7. Select “Feeds” menu

To create project Feed, on the top menu, click “IO” menu, then “Feeds” menu. See figure 7!

Figure 8. View All project “Feeds”

After that, “Feeds” page will be open (See figure 8), then click “View all” to open a list of Feeds that has created, if there are another feeds has created before. But if there are no available feeds, it’s means, the feed that will you create is the first feed. To get started create a feed, click “Action” drop-down option, then select “Create a New Feed” (See figure 9).

Figure 9. Create new project “Feeds”

Type your feed name (in this case, Temperature) in the name field, then click “Create” button (See figure 10). The maximum length of the feed name is 128 characters only.

Figure 10. Create feed - named “Temperature”

After “Create” button clicked, on the feed list will be created “Temperature” feed. See figure 11.

Figure 11. A feed named “Temperature” has created

Do the same steps, to create the other feed for this project (Humidity feed). See figure 12 and figure 13.

Figure 12. Create feed - named “Humidity”

Figure 13. A feed named “Humidity” has created

Step 4: Create Project “Dashboard”

After you have created feeds for this project, the next step is creating Dashboard. Dashboard is a web-based user interface (UI) page on your Adafruit IO account that make you can monitor data from sensor device (subscribe) or control actuators that installed on the sensor device (publish) from your smartphone or computer.

Figure 14. Select “Dashboards” menu

To get started create Dashboard, on the top menu, click “IO” menu, then “Dashboards” menu. See figure 14!

Figure 15. View All project “Dashboards”

After that, “Dashboards” page will be open (See figure 15), then click “View all” to open a list of Dashboard that has created, if there are another Dashboard has created before. But if there are no available Dashboards, it’s means, the dashboard that will you create is the first dashboard. To get started create a dashboard, click “Action” drop-down option, then select “Create a New Dashboard” (See figure 16).

Figure 16. Create new project “Dashboards”

Type your Dashboard name (in this case, Temperature & Humidity Monitor) in the name field, then click “Create” button (See figure 17).

Figure 17. Create dashboard - named “Temperature & Humidity Monitor”

After “Create” button clicked, on the Dashboards list will be created “Temperature & Humidity Monitor” dashboard. See figure 18.

Figure 18. A new dashboard has created

Step 5: Open the Created Dashboard

If your dashboard has created, to open it, just click the dashboard name. See figure 19!

Figure 19. Open the dashboard

After your new dashboard opened, there is no available control or monitor block yet (See figure 20), so, you have to create it with follow your project system needs. On this case, you need two monitor blocks to show the real-time sensing data of DHT22 sensor, i.e. Temperature and humidity sensor data.

Figure 20. Adafruit IO Dashboard opened (Temperature & Humidity Monitor)

Step 6: Create New (Control/Monitor) Block on the Dashboard

To get started create a new block, just click “Create a new block (+)” button. See figure 21.

Figure 21. Button to create a new block

After you press the “Create a new block (+)” button, a block option window will open for you, So, you can select a new block (Control or monitor) that match with your project. See figure 22!

Figure 22. Block options window

Step 7: Create Block to Monitor Temperature Data on the Dashboard

For this project, select “Gauge” block to monitor temperature data.

Figure 23. Select Gauge block for Temperature monitoring

After you select Gauge block, you need to choose a feed that you want its data will displayed on the Gauge block that has you selected before. So, choose “Temperature” feed! See figure 24.

Figure 24. Choose the match feed for Temperature block (Feed = Temperature)

After you have chosen the match feed for the Gauge block, then click “Next step” button (See figure 24), So, “Block setting” window will opened (See figure 25).

Figure 25. Temperature block setting

Set the Gauge block parameter with follow the figure 25, after complete, then click “Create block.”

Figure 26. Gauge block to monitor temperature data has created on the Dashboard

If you are success, you will see Gauge block to monitor temperature sensing data has created on the Dashboard.

Step 8: Create Block to Monitor Humidity on the Dashboard

With the same steps on the Step 6 and Step 7, create a new block for humidity data monitoring.

Open “block options window” by press “Create a new block” button, see figure 21 and figure 22.
Select Gauge block for Humidity monitoring. See figure 23.
Choose the match feed for Humidity block. See figure 27.
Set the humidity Gauge block parameters, then click “Create block.” See figure 28.
Gauge block to monitor humidity data has created on the Dashboard. See figure 29.

Figure 27. Choose the match feed for Humidity block (Feed = Humidity)

Figure 28. Humidity block setting

Figure 29. Gauge block to monitor humidity data has created on the Dashboard

Step 9: Dashboard Layout Editing

If you want to edit the blocks layout on your dashboard, you can do so with follow the steps below.

Figure 30. Edit Dashboard layout button

Click “Edit Dashboard layout” button so on each corner of the Gauge block will available “Corner blue marking,” that signed that you can click and drag the block to move it to another place that you want on the dashboard.

Figure 31. Blue marking on each block

For example, you want the Humidity gauge block placed on the right-side of the Temperature gauge block, so you can click the Humidity gauge block and drag to move to the right-side of the Temperature gauge block. Then click “Save layout change” button to save your new blocks layout (See figure 32 and figure 33).

Figure 32. Save the new layout setting

Figure 33. The new layout setting has saved

Step 10: Take Your Adafruit IO Username & Active Key

Click “Adafruit IO key” if you want to know your Adafruit IO username and active key. See figure 34 and figure 35.

Figure 34. Adafruit IO Key link

Figure 35. Your Adafruit IO Key information window

Your Adafruit IO key will be use on your program to make your device (Wireless sensor) can be connected with Adafruit IO IoT cloud platform and publish sensor data on it.

Step 11: Hardware (Device) Installation

For this project, the interface wiring between DHT22 with ESP32 IoT board is as follow the figure 36 below.

Figure 36. The interfacing between DHT22 with ESP32 IoT board

That is so simple interfacing, because you need three jumper-cable only. One for positive power supply (+3V3), one for negative power supply or GND, and one for sensor data output (in this case, I use the D15 pin).

Step 12: Code Build & Upload Program

After you have finished create your Dashboard on Adafruit IO IoT clouds platform, and make Interfacing between DHT22 sensor module with ESP32 IoT board, next, build the program (code/firmware) for your sensor device gateway (ESP32 IoT board) in order it can publish temperature and humidity sensor data (DHT22) to Adafruit IO IoT clouds platform. Type “Program 1” below in the Arduino IDE or actually copy and paste 😊

Program 1:

When you type your code, don’t forget to edit “Program 1” on “WiFi parameters” and “Adafruit IO setup” sections (See figure 37).

Figure 37. WiFi parameters & Adafruit IO setup section

On the WiFi parameters section, edit WLAN SSID name and its password. Change characters "TYPE_YOUR_WIFI_SSID_HERE", with the SSID name of your WiFi that you use for this project. Then change characters "TYPE_YOUR_WIFI_PASSWORD_HERE", with your WiFi password.

Then, on the Adafruit IO setup section. With refer Step 9 (Take your Adafruit IO username & Key) above. Change characters "TYPE_YOUR_ADAFRUIT_IO_USERNAME_HERE", with your Adafruit IO username and "TYPE_YOUR_ADAFRUIT_IO_KEY_HERE", with your Adafruit IO active key (See "Step 10" or figure 35 above).

If you have finished on your program typing and editing, next, compile/verify and upload your program to your ESP32 board. Then test it.

Step 13: Hardware/Device Testing

To test your sensor device hardware, open your Arduino IDE, the open Serial Monitor that has availabled in Arduino IDE. Select “Tools” menu, the choose “Serial Monitor” option (See figure 38).

Figure 38. Step to open Arduino IDE serial Monitor

Once you click the “Serial Monitor” option, Serial monitor window will be open (See figure 39). Then select the baud rate value on the baud rate drop-down (in this case, the baud rate is 115200).

Figure 39. Serial monitor

If there is no error occur, on the serial monitor will displayed some information, i.e.:

Connected WiFi SSID.
WiFi IP address.
Device connection information with Adafruit IO cloud platform.
Published sensor data (Temperature & Humidity).

Step 14: Monitoring DHT22 Sensor Data on Adafruit IO Dashboard

The last step is monitoring the DHT22 sensor data on Adafruit IO dashboard. To make sure that the DHT22 sensor data on the Adafruit IO dashboard and on the actual measurement place (Record on Arduino IDE Serial monitor window) have the same value, its better if you compare the data by see the DHT22 sensor data side by side. Either on Adafruit IO dashboard or on Serial Monitor. See figure 40.

Figure 40. DHT22 sensor data on Adafruit IO dashboard Vs on Serial Monitor

Figure 41. Realtime monitoring of DHT22 sensor data on Adafruit IO dashboard

Figure 41, showed the real-time monitoring of DHT22 sensor data (Temperature & Humidity) on Adafruit IO dashboard.

If you reach this point, congratulation!

Its means that you have published DHT22 sensor data (Temperature and Humidity) to Adafruit IO IoT cloud platform using MQTT protocol successfully.

ABU Robocon 2019 Mongolia

noreply@blogger.com (Robotics University) — Fri, 03 May 2019 06:58:00 +0000

robotics-university.com | The mission of ABU Robocon 2019 Ulaanbaatar is to delivery information fast by using a relay messenger system - the Urtuu, which was first innovated in the world by the nomadic Mongolians. For exchanging information in a long distance, Mongolians had been using the Urtuu system as a messenger for rest (feeding, replacing a horse, etc.) and in some cases, rely to another messenger. By using the Urtuu system, a messenger was able to travel in distance of 400 kilometers per day. At present day, we are going through massive and abrupt development of exchanging and sharing knowledge and information. This Urtuu system was an important invention that opened a new door for us to exchange and share the knowledge in regardless of space. Based on this concept, ABU Robocon 2019 Ulaanbaatar is designed to promote the idea of "Sharing the knowledge."

The official website:

http://aburobocon2019.mnb.mn/en

The theme rule of ABU ROBOCON 2019:

Download here!

Robocon 2019 Theme & Rules video:

SimpleLink MSP432 - enhanced Universal Serial Communication Interface (eUSCI) - UART Mode

noreply@blogger.com (Taufiq D.S. Suyadhi) — Thu, 25 Apr 2019 07:16:00 +0000

robotics-university.com | In order you can using MSP432P401R microcontroller chip to build your own embedded systems application, you have to know about the detail features of this microcontroller chip and how to use its. On today article, I will try to explain for you about one communication feature of the SimpleLink MSP432P401R microcontroller chip, i.e. Enhanced Universal Serial Communication Interface (eUSCI) - UART Mode. Understanding the serial communication feature of this microcontroller chip is an important thing for you when you will build embedded systems application which need make serial communication (UART mode) between your system hardware with an external device via TXD and RXD communication line.

Quote the explanation of eUSCI (UART Mode) on MSP432P401R microcontroller from its technical reference manual document, there are mentioned that the enhanced universal serial communication interface A (eUSCI_A) supports multiple serial communication modes with one hardware module.

The eUSCI modules are used for serial data communication. The eUSCI module supports synchronous communication protocols such as SPI (3-pin or 4-pin) and I2C, and asynchronous communication protocols such as UART, enhanced UART with automatic baud-rate detection, and IrDA (Infrared Data Association).

The eUSCI_An module provides support for SPI (3-pin or 4-pin), UART, enhanced UART, and IrDA.
The eUSCI_Bn module provides support for SPI (3-pin or 4-pin) and I2C.
The MSP432P401x MCUs offer up to four eUSCI_A and four eUSCI_B modules.

On this article, the explanation will discuss the operation of the asynchronous UART mode only. For the another eUSCI mode (SPI and I2C mode), I will discuss on the separate articles on this website.

1. eUSCI_A Overview

The eUSCI_A module supports two serial communication modes:

UART mode
SPI mode

2. eUSCI_A Introduction (UART Mode)

In asynchronous mode, the eUSCI_Ax modules connect the device to an external system through two external pins, UCAxRXD and UCAxTXD. UART mode is selected when the UCSYNC bit is cleared. UART mode features include:

7-bit or 8-bit data with odd, even, or no parity
Independent transmit and receive shift registers
Separate transmit and receive buffer registers
LSB-first or MSB-first data transmit and receive
Built-in idle-line and address-bit communication protocols for multiprocessor systems
Programmable baud rate with modulation for fractional baud-rate support
Status flags for error detection and suppression
Status flags for address detection
Independent interrupt capability for receive, transmit, start bit received, and transmit complete

Figure 1 shows the eUSCI_Ax block diagram when configured for UART mode.

Figure 1. eUSCI_Ax Block Diagram - UART Mode (UCSYNC = 0)

3. eUSCI_A UART Registers

From the MSP432P401R microcontroller technical reference manual document (Page 922-932), you will get information about the eUSCI_A - UART register. Below are the registers which will involve when you configure the eUSCI_A - UART mode of MSP432P401 microcontroller:

CAxCTLW0 (eUSCI_Ax Control Word Register 0)
CAxCTLW1 (eUSCI_Ax Control Word Register 1)
UCAxBRW (eUSCI_Ax Baud Rate Control Word) Register
UCAxMCTLW (eUSCI_Ax Modulation Control Word) Register
UCAxSTATW (eUSCI_Ax Status) Register
UCAxRXBUF (eUSCI_Ax Receive Buffer) Register
UCAxTXBUF (eUSCI_Ax Transmit Buffer) Register
UCAxABCTL (eUSCI_Ax Auto Baud Rate Control) Register
UCAxIRCTL (eUSCI_Ax IrDA Control Word) Register
UCAxIE (eUSCI_Ax Interrupt Enable) Register
UCAxIFG (eUSCI_Ax Interrupt Flag Register)
UCAxIV (eUSCI_Ax Interrupt Vector) Register

Note X = The UART number (0, 1, or 2)

For more information about the registers detail, you can read the SimpleLink MSP432P401R microcontroller datasheet, click here!

4. eUSCI_A Operation (UART Mode)

The eUSCI_A (UART Mode) are configured with user software. The setup and operation of the eUSCI_A (UART Mode) are discussed in the following sections. From the SimpleLink MSP432P4xx Technical Reference Manual, the recommended operation steps to Initialize or reconfigure the eUSCI_A module (UART mode) can be explain as follow:

Step 1: Set UCSWRST with software (UCSWRST = 1).

Step 2: Initialize all eUSCI_A registers when UCSWRST = 1.

Step 3: Configure UART ports (UART line, i.e. UCAxTXD and UCAxRXD).

Step 4: When you have finished reconfigure the UART registers, clear UCSWRST with software (UCSWRST = 0)

Step 5: Enable interrupts with UCRXIE or UCTXIE (This is optional).

Below is the example code in UART2 initialization:

Program 1: UART2 initialization code

Below are the “Program 1” detail explanation.

EUSCI_A2->CTLW0 |= 1; // UCSWRST = 1, UART on reset mode

The first line instruction of UART2_init function block will make the UART stay on Reset mode, so we can configure/modify the others eUSCI_A UART registers before use it on this mode.

The eUSCI_A can be reset by a hard-reset or by software-reset (Set the UCSWRST bit to high logic, 1). After a hard/soft reset, the UCSWRST bit is automatically set, keeping the eUSCI_A in a reset condition. On this reset condition, the UCTXIFG bit will be set automatically and resets the UCRXIE, UCTXIE, UCRXIFG, UCRXERR, UCBRK, UCPE, UCOE, UCFE, UCSTOE, and UCBTOE bits. The configuring and reconfiguring of the eUSCI_A module should be done when UCSWRST is set to avoid unpredictable behavior.

EUSCI_A2->BRW = 26; //3,000,000/115200 = 26 (N= Required division factor)

UCA2BRW is a register that have function to control the UART serial communication baud rate. From the program information, we know that the UART system clock frequency is 3 MHz (equivalent with 3.000.000 Hz) and the expected UART baud rate is 115200, so this instruction will give 26 as the UCBR2 bit value on UCA2BRW register (N = 3.000.000/115200). The 26 is the baud rate N division factor. To get division factor value (N), the formula as follow:

N = Division factor

fBRCLK = UART system clock frequency

Baud rate = The expected UART Baud rate value

EUSCI_A2->MCTLW = 1; //Because N>16 so UCOS16 = 1 / Enable oversampling

This instruction will make the UCOS16 bit condition of the MCTLW register become high-logic (1). Because of the division factor (N) of the UART systems clock frequency is bigger than 16, based on the SimpleLink MSP432P401R Technical reference (Page 915), this condition recommended to use the oversampling baud-rate generation mode.

EUSCI_A2->CTLW0 = 0x0081; // 1 stop bit, no parity, SMCLK, 8-bit data

This instruction is an example method in 16-bit register addressing. This instruction function is to set the UART specification with reconfigure the CTLW0 register.

Figure 2. UCAxCTLW0 Register

0x0081 is a 16-bit hexadecimal number. To make easy to understand how to address the UCAxCTLW0 register, we should convert this hexadecimal number to 16-bit binary number, so it will be:

0x0081 = 0b 0000-0000-1000-0001

Note:

The far-right bit is the least significant bit (LSB), vice versa the far-left bit is the most significant bit (MSB)

With the binary number, we can know the UART specification from the addressed bits of the UCAxCTLW0 register by saw the table 1 below (See the configuration on “Value” column).

Tabel 1. UCAxCTLW0 register reconfiguration

From table 1 above, we know the UART specification as follow:

Bit parity : No parity

Character length : 8-bit data

Stop bit : 1 stop bit

UART mode : Synchronous

Baud rate source clock (BRCLK) : SMCLK

P3->SEL0 |= 0x0C; // Configure P3.2(RXD) and P3.3(TXD) as UART line
P3->SEL1 &= ~0x0C;

This instruction will set the P3.2 and P3.3 as the serial communication (UART mode) line. So to build a serial communication with MSP432P401R microcontroller, the external hardware must be connected to that pins.

EUSCI_A2->CTLW0 &= ~1; // UCSWRST = 0, UART out of reset mode

This instruction will make the UART out of reset mode, so we can’t configure/modify the others eUSCI_A UART registers again.

Source:

[1] SimpleLink MSP432 P401R datasheet

[2] SimpleLinkMSP432P4xx - Technical Reference Manual

SimpleLink MSP432P401R Microcontroller Interfacing with 16x2 LCD

noreply@blogger.com (Taufiq D.S. Suyadhi) — Mon, 22 Apr 2019 17:21:00 +0000

robotics-university.com | Hello friends, today I invite you to learn embedded systems using SimpleLink MSP432 development kit form Texas Instruments (TI). On this article, I will make a guidance to make interfacing between 16x2 characters liquid crystal display (LCD) with MSP432P401R microcontroller chip that embedded on SimpleLink MSP432 development kit. For the software, still using Code Composer Studio IDE software. Okey ... let’s continue read this article and practiced by follow the guidance on this project, hopefully this article useful for you.

1. Project Materials

To build this project, we have to has the project materials. Below I write-down the needs hardware and software in order you can make this project realized.

A. Hardware needs

(1) SimpleLink MSP432P401R development kit (32-bit ARM Cortex-M4F) from TI.

(2) Data cable (USB type-A to Micro USB type-B).

(3) Computer/Laptop.

(4) Hitachi HD44780 - 16x2 LCD module (or compatible). See figure 1.

Figure 1. Hitachi HD44780 LCD (or compatible)

B. Software needs

(1) Code Composer (CoCo) Studio

Download the latest version of CoCo Studio (v9.3.0) here!, then install it to your computer.

(2) LCD16x2_MSP43x library

LCD16x2_MSP43x (Include lcd16x2_msp43x.h and lcd16x2_msp43x.c) is a couple-library file which can make you easy to develop an embedded systems project using LCD HD44780 and MSP432P401R microcontroller chip. This library authorized by Haroldo Amaral (agaelema@globo.com). He has been shared this library on Github for free. Download this library here!

2. Hardware Interface

To start the project, at the first, you have to make your SimpleLink MSP432 development kit connect to Hitachi HD44780 16x2 LCD module (or compatible). To make a connection, you have to know about Hitachi HD44780 16x2 LCD module pin configuration, see figure 2 first.

Figure 2. LCD 16x2 character - pin configuration

On this project, we will control the texts display on the 16x2 LCD with just using 4-bit data line, i.e. D4, D5, D6, and D7. On the other hands, on SimpleLink MSP432P401R development kit, we will use PORT-4 (P4) for the interfacing line. Below are the detail connection descriptions, see table 1.

Tabel 1. MSP432 microcontroller & 16x2 LCD pins connection description

With follow the pins connection description on table 1 above, start to connect every single pins on MSP432 microcontroller pins and 16x2 LCD pins using jumper cable.

Figure 3. SimpleLink MSP432 development kit interfacing with 16x2 LCD

For your information, on this project I use 16x2 LCD module from CH electronics (www.circuits-home.com), the wiring-visualization as shown on figure 4 below.

Figure 4. The wiring-visualization - MSP432P401R interfacing with 16x2 LCD module

3. Getting Started to New Project Building

STEP 1: Install The Hardware

Install your SimpleLink MSP432 development kit with your 16x2 LCD module with follow the guidance on Section 2 (Hardware Interface) above.

STEP 2: Create New Project

To create a new project on Code Composer Studio, you can read my previous article about “How to Create New Project & Hardware Connection Verify On Coco Studio” here!

Figure 5. A new project which has been created (lcd_16x2_b)

STEP 3: Download LCD16x2_MSP43x Library From Github

Download lcd16x2_msp43x library from Github. I have shared the download link above (See section 1.B, Project Materials)

Figure 6. lcd16x2_msp43x library download page

Save the library in a folder/directory of your computer and extract the zip file (LCD16x2_MSP43x-master.zip) to get the lcd16x2_msp43x.h and lcd16x2_msp43x.c files.

STEP 4: Add LCD16x2_MSP43x Library Into The Project

In order the lcd16x2_msp43x library file can be include on building/compilation process, you have to add the lcd16x2_msp43x.h and lcd16x2_msp43x.c files into the project package. To do so, please follow the steps below.

Figure 7. Add lcd16x2_msp43x library files into the project

Right-click the project package on the “Project Explorer,” then select “Add Files” option (See figure 7). Then browse and open folder/directory where you have store lcd16x2_msp43x library files (lcd16x2_msp43x.h and lcd16x2_msp43x.c) before (when you follow the library download steps above). If the library files have been found, select the lcd16x2_msp43x.h and lcd16x2_msp43x.c file, then click “Open” button to start add it into the project package (See figure 8).

Figure 8. Select the lcd16x2_msp43x.h and lcd16x2_msp43x.c files

If after you push “Open” button and “File Operation” windows opened, just select “Copy files” radio-button then push “OK” button to continue the adding files process (See figure 9).

Figure 9. File operation windows

If the adding files process run properly, on project explorer, you will see the lcd16x2_msp43x.h and lcd16x2_msp43x.c file has been added on the lcd_16x2_b project package (See figure 10).

Figure 10. lcd16x2_msp43x library files has added into the project

STEP 5: Modify The LCD16x2_MSP43x Library

Next, double-click lcd16x2_msp43x.h file to open it. The default lcd16x2_msp43x.h file as shown on figure 11.

Figure 11. The default lcd16x2_msp43x.h file

To make the lcd16x2_msp43x library can use to control the 16x2 LCD module, you have to do some modification in that. First, change the "msp430.h" microcontroller header to become "msp432.h" Second, set the LCD pins corresponding with your actual LCD pins connection to the MSP432P401R microcontroller pins. On this project, I use PORT-4, following the pins configuration in Table 1 and figure 3 above (See figure 12).

Figure 12. The modified lcd16x2_msp43x.h file

After you have been finished to modify the lcd16x2_msp43x.h file, then save the changed (Save All).

STEP 6: Create Program On Code Composer Studio Program Editor

On this project, we will create a main program to show two sentences on the LCD display, i.e. “Hi Taufiq!” on the first-row and “How are you?” on the second-row. Write the program below on the CCS IDE program editor (See Program 1).

Program 1: main.c

STEP 7: Build The Project

If you have been finished create your program, next, you have to “build” or compile that program, in order your program can be sent to the target microcontroller chip and configure its function as your expectation. To know the program building steps, you can read my previous article about “HowTo Build Project On Code Composer Studio” here!

STEP 8: Debug or Load The Project/Program

On Code Composer Studio, after a project has built successfully, there are two method to send the program-output to the microcontroller chip, i.e. Debug the program and Load the program. To know the program debugging or loading steps, you can read my previous article about “How To Debug and Load Project Using Code Composer Studio” here!

STEP 9: Ensure The Project Working As Your Expectation

To ensure that the built program has downloaded into the target microcontroller chip properly, please observe the project hardware. Is the LED behaviour has been as your expectation? If yes, that is sign that the built program has downloaded well.

Figure 13. Project result (MSP432 - LCD)

Recommended articles:

[1] Create New Project

[2] Build The Project

[3] Debug or Load The Project/Program

[4] Getting Started MSP432 Mircrocontroller Programming Using Code Composer Studio

Getting Started MSP432 Mircrocontroller Programming Using Code Composer Studio

noreply@blogger.com (Taufiq D.S. Suyadhi) — Sun, 21 Apr 2019 07:56:00 +0000

robotics-university.com | Hello friends, today I invite you to learn about one of popular 32-bit microcontroller chip from Texas Instruments (TI). On this article, I will make a guidance to get started MSP432 microcontroller chip programming using Code Composer Studio IDE software. This software has provided by Texas Instruments for its microcontroller chips user. On this project, I use MSP432P401R (MSP‑EXP432P401R) series microcontroller chip that was embeded on SimpleLink LaunchPad development kit (See figure 1). For your information, MSP432 is a microcontroller with ARM Cortex-M4F architecture that produced by TI. Okey ... let’s continue read this article and practiced by follow the guidance on this project, in order you can build your own MSP432 project at home.

1. Project Materials

To build this project, we have to has the project materials. Below I write-down the needs hardware and software in order you can make this project realized.

A. Hardware needs

(1) SimpleLink MSP432P401R development kit (32-bit ARM Cortex-M4F) from TI.

(2) Data cable (USB type-A to Micro USB type-B).

(3) Computer/Laptop.

Figure 1. SimpleLink MSP432 (MSP432P401R) development kit

B. Software needs

(1) Code Composer (CoCo) Studio.

Code Composer Studio or CCS for short is a suite of development tools including an editor, project management system, compiler, debugger, profiling and visualization tools.

The latest version of CoCo Studio 9.3.0 available to download here!

For your information, there is no license fee associated with Code Composer Studio. Users are free to download and install Code Composer Studio without having to purchase a license. The license terms for Code Composer Studio are shown at installation and available afterwards in the/doc folder.

2. The Interface of SimpleLink MSP432 Development Kit with Computer & LED

To start the project, at the first, you have to make your computer connect to the SimpleLink MSP432 development kit via USB port and connect the MSP432P401R microcontroller I/O pins with two light emitting diode (LED) components on PORT-5 (P5.2 and P5.4). See figure 2.

Figure 2. The interfacing of SimpleLink MSP432 development kit with computer

3. The Installation of the Needed Software

If you have downloaded Code Composer Studio installer file, then save it on your computer hard-disk, and you want to use it to build an embedded systems project, you have to install it first on your computer.

To get started install the Code Composer (Coco) Studio on your computer, open the directory/folder where have you save the zip package file of Coco Studio installer (Offline) that you have downloaded before, then extract it.

Figure 3. Code Composer Studio installer file

Next, open the extracted folder of the Coco Studio. To start install, double-click the Coco Studio exe file and then follow every single step of Coco Studio installation process until the process complete (See figure 3).

4. Getting Started to New Project Building

After you have installed all of the needed software on part-3 and connect your SimpleLink MSP432 development kit to computer with follow the figure 2 above, now it’s time to getting started build your first embedded systems project.

STEP 1: Create New Project

To create a new project on Code Composer Studio platform, you can read my previous article about “How to Create New Project & Hardware Connection Verify On Coco Studio” here!

STEP 2: Create Program On Code Composer Studio Program Editor

On this first project, we will create a program to control two LED (Ligth Emitting Diode) which installed on P5.2 and P5.4 of SimpleLink MSP432 development kit. Write the program below on the CCS IDE program editor (See Program 1).

Program 1: main.c

This program will make LED components which installed on P5.2 pin dan P5.4 pin light up alternately with different delay value.

STEP 6: Build The Project

STEP 7: Debug or Load The Project/Program

STEP 8: Ensure The Project Result As Your Expectation

Recommended articles:

[1] Create New Project

[2] Build The Project

[3] Debug or Load The Project/Program

[4] SimpleLink MSP432P401R Microcontroller Interfacing with 16x2 LCD

Digital Input-Output (I/O) of MSP432P401R Microcontroller

noreply@blogger.com (Taufiq D.S. Suyadhi) — Sat, 20 Apr 2019 07:55:00 +0000

robotics-university.com | In order you can using MSP432P401R microcontroller chip to build your own embedded systems application, you have to know about the detail features of this microcontroller chip and how to use its. On today article, I will try to explain for you about one important feature of the SimpleLink MSP432P401R microcontroller chip, i.e. Digital Input/Output (I/O). Understanding the I/O feature of this microcontroller chip is an important thing for you, without that, an embedded systems application using this microcontroller chip will not create properly and running well.

Quote the explanation of MSP432P401R microcontroller digital I/O from its technical reference manual document (Pages 677), the digital I/O features include:

Independently programmable individual I/Os
Any combination of input or output
Individually configurable interrupts for ports (available for certain ports only)
Independent input and output data registers
Individually configurable pullup or pulldown resistors
Wake-up capability from ultra-low-power modes (available for certain ports only)
Individually configurable high drive I/Os (available for certain I/Os only)

Devices within the family may have up to eleven digital I/O ports implemented (P1 to P10 and PJ). Most ports contain eight I/O lines; however, some ports may contain less (see the device-specific data sheet for ports available). Each I/O line is individually configurable for input or output direction, and each can be individually read or written. Each I/O line is individually configurable for pullup or pulldown resistors.

Certain ports have interrupt and wake-up capability from ultra-low-power modes (see device-specific data sheet for ports with interrupt and wake-up capability). Each interrupt can be individually enabled and configured to provide an interrupt on a rising or falling edge of an input signal. All interrupts are fed into an encoded interrupt vector register, allowing the application to determine which pin of a port has generated the event.

Individual ports can be accessed as byte-wide ports or can be combined into half-word-wide ports. Port pairs P1 and P2, P3 and P4, P5 and P6, P7 and P8, and so on, are associated with the names PA, PB, PC, PD, and so on, respectively. All port registers are handled in this manner with this naming convention. The main exception are the interrupt vector registers, for example, interrupts for ports P1 and P2 must be handled through P1IV and P2IV, PAIV does not exist.

When writing to port PA with half-word operations, all 16 bits are written to the port. When writing to the lower byte of port PA using byte operations, the upper byte remains unchanged. Similarly, writing to the upper byte of port PA using byte instructions leaves the lower byte unchanged. When writing to a port that contains fewer than the maximum number of bits possible, the unused bits are don't care. Ports PB, PC, PD, PE, and PF behave similarly.

Reading port PA using half-word operations causes all 16 bits to be transferred to the destination. Reading the lower or upper byte of port PA (P1 or P2) and storing to memory using byte operations causes only the lower or upper byte to be transferred to the destination, respectively. When reading from ports that contain fewer than the maximum bits possible, unused bits are read as zeros (similarly for port PJ).

1. MSP432P401R Microcontroller - I/O Pins Mapping

Figure 1 and figure 2 show for you the Simplelink MSP432P401 microcontroller I/O pins mapping on the SimpleLink MSP432 development kit.

Figure 1. Simplelink MSP432P401 I/O pins mapping (1)

Figure 2. Simplelink MSP432P401 I/O pins mapping (2)

2. MSP432P401R Microcontroller - Digital I/O Registers

From the MSP432P401R microcontroller digital I/O technical reference manual document (Page 676-699), you will get information about the twelve digital I/O register.

Figure 3. MSP432P401 microcontroller - Digital I/O registers

The registers which will involved when you configure the digital I/O of MSP432P401 microcontroller:

1. PxIV (Port X Interrupt Vector) Register

2. PxIN (Port X Input) Register

3. PxOUT (Port X Output) Register

4. PxDIR (Port X Direction) Register

5. PxREN (Port X Pullup or Pulldown Resistor Enable) Register

6. PxDS (Port X Drive Strength Selection) Register

7. PxSEL0 (Port X Function Selection) Register 0

8. PxSEL1 (Port X Function Selection) Register 1

9. PxSELC (Port X Complement) Selection

10. PxIES (Port X Interrupt Edge Select) Register

11. PxIE (Port X Interrupt Enable) Register

12. PxIFG (Port X Interrupt Flag) Register

Note X = 1, 2, 3, 4, 5, 6, 7, 8, 9 or 10

3. MSP432P401R Microcontroller - Digital I/O Operation

The digital I/O are configured with user software. The setup and operation of the digital I/O are discussed in the following sections.

3.1 Input Registers (PxIN)

Each bit in each PxIN register reflects the value of the input signal at the corresponding I/O pin when the pin is configured as I/O function. These registers are read only.

• Bit = 0: Input is low

• Bit = 1: Input is high

3.2 Output Registers (PxOUT)

Each bit in each PxOUT register is the value to be output on the corresponding I/O pin when the pin is configured as I/O function, output direction.

• Bit = 0: Output is low

• Bit = 1: Output is high

If the pin is configured as I/O function, input direction and the pullup or pulldown resistor are enabled; the corresponding bit in the PxOUT register selects pullup or pulldown.

• Bit = 0: Pin is pulled down

• Bit = 1: Pin is pulled up

3.3 Direction Registers (PxDIR)

Each bit in each PxDIR register selects the direction of the corresponding I/O pin when it is configured for I/O function. PxDIR register also in most of the cases controls the direction of the I/O when it is configured for peripheral functions. PxDIR bits for I/O pins that are selected for peripheral functions must be set as required by the peripheral functions. For certain secondary functions like eUSCI, the I/O direction is controlled by the secondary function itself and not by the PxDIR register. Refer to device-specific data sheet for more details.

• Bit = 0: Port pin is switched to input direction

• Bit = 1: Port pin is switched to output direction

3.4 Pullup or Pulldown Resistor Enable Registers (PxREN)

Each bit in each PxREN register enables or disables the pullup or pulldown resistor of the corresponding I/O pin. The corresponding bit in the PxOUT register selects if the pin contains a pullup or pulldown.

• Bit = 0: Pullup or pulldown resistor disabled

• Bit = 1: Pullup or pulldown resistor enabled

Table 1 summarizes the use of PxDIR, PxREN, and PxOUT for proper I/O configuration.

Table 1. I/O configuration

3.5 Output Drive Strength Selection Registers (PxDS)

There are two type of I/Os available. One with regular drive strength and the other with high drive strength. Most of the I/Os have regular drive strength while some selected I/Os have high drive strength. See device-specific data sheet for the I/Os with high drive strength. PxDS register is used to select the drive strength of the high drive strength I/Os.

• Bit = 0: High drive strength I/Os are configured for regular drive strength

• Bit = 1: High drive strength I/Os are configured for high drive strength

PxDS register does not have any effect on the I/Os with only regular drive strength.

3.6 Function Select Registers (PxSEL0, PxSEL1)

Port pins are often multiplexed with other peripheral module functions. See the device-specific data sheet to determine pin functions. Each port pin uses two bits to select the pin function – I/O port or one of the three possible peripheral module function. Table 2 shows how to select the various module functions. Each PxSEL bit is used to select the pin function – I/O port or peripheral module function

Table 2. I/O function selection

Setting the PxSEL1 or PxSEL0 bits to a module function does not automatically set the pin direction. Other peripheral module functions may require the PxDIR bits to be configured according to the direction needed for the module function. See the pin schematics in the device-specific data sheet.

When a port pin is selected as an input to peripheral modules, the input signal to those peripheral modules is a latched representation of the signal at the device pin. While PxSEL1 and PxSEL0 is other than 00, the internal input signal follows the signal at the pin for all connected modules. However, if PxSEL1 and PxSEL0 = 00, the input to the peripherals maintain the value of the input signal at the device pin before the PxSEL1 and PxSEL0 bits were reset.

3.7 Port Interrupts

3.7.1 Interrupt Vector (PxIV) & Interrupt Flag (PxIFG) Register

All Px interrupt flags for a particular port are prioritized, with PxIFG.0 being the highest, and combined to source a single interrupt vector. The highest priority enabled interrupt generates a number in the PxIV register. This number can be evaluated or added to the program counter to automatically enter the appropriate software routine. Disabled Px interrupts do not affect the PxIV value. The PxIV registers are half-word access only.

Each PxIFG bit is the interrupt flag for its corresponding I/O pin, and the flag is set when the selected input signal edge occurs at the pin. All PxIFG interrupt flags request an interrupt when their corresponding PxIE bit is set. Software can also set each PxIFG flag, providing a way to generate a software-initiated interrupt.

• Bit = 0: No interrupt is pending

• Bit = 1: An interrupt is pending

Only transitions, not static levels, cause interrupts. If any PxIFG flag becomes set during a Px interrupt service routine or after Px interrupt service routine execution is completed, the set PxIFG flag generates another interrupt. This ensures that each transition is acknowledged.

Any access (read or write) of the PxIV register automatically resets the highest pending interrupt flag. If another interrupt flag is set, another interrupt is immediately generated after servicing the initial interrupt.

For example, assume that P1IFG.0 has the highest priority. If the P1IFG.0 and P1IFG.2 flags are set when the interrupt service routine accesses the P1IV register, P1IFG.0 is reset automatically. After the completion of P1IFG.0 interrupt service routine, the P1IFG.2 generates another interrupt.

3.7.2 Interrupt Edge Select Registers (PxIES)

Each PxIES bit selects the interrupt edge for the corresponding I/O pin.

• Bit = 0: Respective PxIFG flag is set on a low-to-high transition

• Bit = 1: Respective PxIFG flag is set on a high-to-low transition

Writing to PxIES for each corresponding I/O can result in setting the corresponding interrupt flags.

Table 3. Writing to PxIES

3.7.3 Interrupt Enable Registers (PxIE)

Each PxIE bit enables the associated PxIFG interrupt flag.

• Bit = 0: The interrupt is disabled

• Bit = 1: The interrupt is enabled

4. How To Configure The Digital I/O Using C Program

Configure Px as output

P3->DIR = 0xFF;       // Configure all of P3 pins as output

P3->OUT = 0x00;       // All of P3 pins output is low

P4->SEL1 &= ~2;       // configure P4.1 as general-purpose I/O

P4->SEL0 &= ~2;

P4->DIR |= 2;         // P4.1 set as output pin

P5->SEL1 &= ~0x10;    // configure P5.4 as primary-module I/O

P5->SEL0 |= 0x10;

P5->DIR |= 0x10;      // P5.4 set as output pin

P6->SEL1 &= ~0x14;      // configure P6.2 & P6.4 as general-purpose I/O

P6->SEL0 &= ~0x14;

P6->DIR |= 0x14;        // P6.2 & P6.4 set as output pin

Configure Px as input

P1->DIR = 0x00;       // Configure all of P1 pins as input

P1->OUT = 0xFF;       // All of P1 input is pulled Up

P5->SEL1 &= ~2;       // configure P5.1 as general-purpose I/O

P5->SEL0 &= ~2;

P5->DIR &= ~2;       // P5.1 set as input pin

P7->SEL1 &= ~0x10;    // configure P7.4 as primary-module I/O

P7->SEL0 |= 0x10;

P7->DIR &= ~0x10;    // P7.4 set as input pins

P9->SEL1 &= ~0x14;      // configure P9.2 & P9.4 as general-purpose I/O

P9->SEL0 &= ~0x14;
P9->DIR &= ~0x14;      // P9.2 & P9.4 set as input pins

Source:

[1] SimpleLink MSP432P401R datasheet

[2] SimpleLink MSP432P4xx - Technical Reference Manual

Beginner User of SimpleLink MSP432P401R Development Kit

noreply@blogger.com (Taufiq D.S. Suyadhi) — Fri, 19 Apr 2019 10:25:00 +0000

robotics-university.com | Hello my friends, if you are a beginner in using SimpleLink MSP432P401R development kit, may be, you can follow my simple tips in order you can use that development kit properly. If you want to try my tips, please follow the steps below.

Step 1: Buy your own SimpleLink MSP432P401R development kit

To get your own SimpleLink MSP432P401R development kit, you can buy it from Texas Instruments (TI) official website (Click here!) or buy from online-shop which sell embedded systems products on your country.

If you have gotten your own SimpleLink MSP432P401R development kit, before you start to use your new development kit, it is better if you read the development kit User's Guide (Download here!) carefully.

Step 2: Download & install Code Composer (CoCo) Studio

Code Composer (CoCo) Studio is an integrated development environment (IDE) software from TI, you can download and use it freely from TI official website. Below is the Code Composer (CoCo) Studio download link:

Code Composer (CoCo) Studio installer, Download here!
Code Composer (CoCo) Studio User Guide for SimpleLink MSP432, Download here!

Step 3: Download & install CoCo Studio support software - SimpleLink MSP432 SDK

MSP432 Software Development Kit (SDK) is a comprehensive software package that enables engineers to quickly develop highly functional applications on Texas Instruments MSP432™ microcontrollers (MCUs). The MSP432 SDK is comprised of multiple compatible software components including RTOS, drivers, and middleware as well as examples of how to use these components together. In addition, examples are provided to demonstrate the use of each functional area and each supported device and as a starting point for your own projects. Download MSP432 SDK on the link below:

MSP432 Software Development Kit (SDK), Download here!

Step 4: Download & install CoCo Studio support software - MSP432Ware & MSP432 DriverLib

MSP432Ware is a collection of code examples, datasheets and other design resources for all MSP432 devices delivered in a convenient package, while MSP432 DriverLib (Driver Library) is a collection of high level API (Application Programming Interface) that speed up software development for MSP432. The MSP432 Driver Library package includes API documentaion and examples to help you get started. Driver library (DriverLib) is one of the main components of MSP432Ware.

MSP432Ware (3.50.00.02 version), Download here!
MSP432 Driver Library (3.21.00.05 version), Download here!

Step 5: Getting Started to make a project Using SimpleLink MSP432 and Code Composer Studio

Follow my guidance to get started to make a project Using SimpleLink MSP432 and Code Composer Studio, Click here!

SimpleLink SDK Plugin

noreply@blogger.com (Taufiq D.S. Suyadhi) — Thu, 18 Apr 2019 07:25:00 +0000

robotics-university.com | From the Texas Instrument (TI) official website, there was mention that SimpleLink SDK Plugins (referred simply to as "plugins" from here forward) are power software packages that are designed to extend the base functionality of one or more SimpleLink SDKs. Plugins provide use case application functionalities that are outside the scope of each platform SDK's base functionality. These plugins provide developers with a way to enhance support of their SDK to better match their application's individual needs. This SimpleLink Academy module is made to deep dive into the definition of an SDK Plugin as well as give users a couple of specific examples of plugin usage.

SimpleLink SDK Plugin Concept

Plugins are intended to extend functionality of each individual SimpleLink SDK to include specialized use-cases. These specialized use cases can range anywhere from adding wireless functionality to extending a platform SDK's example base.

While all of the plugins have the same basic structure and look-and-feel of an SDK, they are not meant as standalone applications and rely heavily on components from the base platform SDK. The SimpleLink MSP432 Sensors and Actuator Interface Library (SAIL) Plugin, for example, relies heavily on the TI-Drivers, RTOS kernels, DriverLib, and various other components from the platform SDK. A high level block diagram of these dependencies can be seen in the image below:

Figure 1. SDK plugin concept (SAIL plugin as example)

It is important to note that each plugin contains all of the necessary components to function fully alongside the platform SDK. Plugins do not install inside of the SDK itself, but rather in a folder next to the SDK. This is to simplify the maintenance model as well as provide customers with a organic experience for updating and switching between plugin versions.

SimpleLink SDK Plugin From Texas Instruments

SimpleLink software development kit (SDK) plug-in for HomeKit, Click here!
Sensor and Actuator Plug-ins for SimpleLink MCU SDK, Click here!
Bluetooth plug-in for the SimpleLink MSP432 SDK, Click here!
SIMPLELINK-SDK-WIFI-PLUGIN, Click here!
SimpleLink SDK Near Field Communication (NFC) Plugin, Click here!

SimpleLink SDK Plugin Detail Information

For more detail information about SimpleLink SDK Plugin, please visit this page!

MSP432Ware & MSP432 Driver Library (DriverLib)

noreply@blogger.com (Taufiq D.S. Suyadhi) — Wed, 17 Apr 2019 04:12:00 +0000

robotics-university.com | Beside SimpleLink MSP432 SDK, Texas Instruments (TI) also provide the other useful support software that also make you easy and faster when build an embedded systems project using MSP432 microcontroller and Code Composer Studio IDE from TI. They call that software with MSP432Ware and MSP432 Driver Library (DriverLib).

MSP432Ware

1. What is MSP432Ware?

MSP432Ware is a collection of code examples, datasheets and other design resources for all MSP432 devices delivered in a convenient package.

2. MSP432Ware Installation or Upgrade

There are two methods to install MSP432Ware:

A. Installing via the Code Composer Studio (CCS) App Center

If you have CCS 6.0 or later you can install MSP432Ware via the CCS App Center.

1. Open up CCS

2. Click “View->CCS App Center”

3. Click the checkbox next to MSP432Ware

4. Then click “Install Software” in the top left corner of the app center.

5. Let CCS restart and discover the software. You can now use TI Resource Explorer within CCS

B. Installing via the Standalone Installer

If CCS is not your primary IDE or want an offline installer on hand you can download the standalone installer.

1. Download the standalone MSP432Ware installer from download link section below.

2. Double click to run the installer, the default installation path is discoverable by CCS

3. Run CCS and let it discover the MSP432Ware installation. You can now use TI Resource Explorer within CCS.

MSP432 Driver Library (DriverLib)

1. What is MSP432 Driver Library?

MSP432 Driver Library is a collection of high level API (Application Programming Interface) that speed up software development for MSP432. The MSP432 Driver Library package includes API documentaion and examples to help you get started. Driver library (DriverLib) is one of the main components of MSP432Ware.

Download Link of MSP432Ware & MSP432 DriverLib

MSP432Ware (3.50.00.02 version), Download here!
MSP432 Driver Library (3.21.00.05 version), Download here!

Questions & Answer of MSP432Ware & MSP432 DriverLib

1. How do I use MSP432 Driver Library?

MSP432 Driver Library is available as a standalone BSD released package. To use the library simply download and unzip the package below. Please read the included user's guide to learn about adding driver library to a new or existing project.

MSP432 Driver Library is also released as a component of MSP432Ware. You can import and run examples from driver library from the TI Resouce Explorer GUI within the Code Composer Studio (CCS) window when you have MSP432Ware installed. For more information about MSP432Ware check the table below for a link to the latest version.

2. What is the difference between MSP432Ware and Driver Library?

MSP432Ware is a collection of MSP432 software and tools. One of the main components of MSP432Ware is Driver Library (DriverLib).

3. Why are there multiple driverlib folders within MSP432Ware?

MSP432Ware contains many different software libraries and projects. Some of these components depend on a specific version of Driver Library. Each component ships the version of Driver Library they tested with to ensure that all software works for you out of the box.

4. Can I have multiple versions of MSP432Ware installed?

Yes! MSP432Ware installations can exist alongside each other. You should only see the latest installed version within the TI Resource Explorer window of Code Composer Studio however.

5. How can I get support for MSP432Ware?

Feel free to use the TI E2E forum to ask anything MSP432Ware related.

Source:

[1] MSP432Ware

[2] MSP432 Driver Library

SimpleLink MSP432 Software Development Kit (SDK)

noreply@blogger.com (Taufiq D.S. Suyadhi) — Tue, 16 Apr 2019 02:37:00 +0000

robotics-university.com | To make easy and faster when you (A hobbyist or an engineer) build an embedded systems project using MSP432 microcontroller and Code Composer Studio IDE from Texas Instruments (TI), TI engineer provide a useful support software. They call the software with SimpleLink MSP432 Software Development Kit (SDK).

On today article, I will try to explain for you about that SimpleLink MSP432 SDK. I quote explanation about SDK from TI official website. There explained that the MSP432 SDK is a comprehensive software package that enables engineers to quickly develop highly functional applications on Texas Instruments MSP432™ microcontrollers (MCUs). The MSP432 SDK is comprised of multiple compatible software components including RTOS, drivers, and middleware as well as examples of how to use these components together. In addition, examples are provided to demonstrate the use of each functional area and each supported device and as a starting point for your own projects.

Figure 1. Simplelink MSP432 SDK block diagram (MSP432P4)

FEATURES OF MSP432 SDK

Flexible programming paradigms from bare metal to high-level APIs support the complete product lifecycle.
Jumpstart development with a rich set of application examples, clear documentation, getting started guides, training videos, and 24/7 online support.
Low cost of ownership with royalty-free software and rigorous testing of all software offerings, a predictable release cadence, and simplified upgrades compliant with published APIs.

WHAT'S INCLUDED ON MSP432 SDK?

TI-RTOS kernel: RTOS kernel developed by Texas Instruments with advanced power management capabilities
POSIX implementation of RTOS kernel: Portability across TI-RTOS and 3rd-party POSIX-compliant RTOSes including a pre-validated implementation of freeRTOS
TI Drivers: High-level abstraction layer with thread-safe APIs that operate across TI-RTOS and freeRTOS
Ethernet connectivity stacks: TCP/IP using NDK and lwIP, mbedTLS
USB stack for USB Full-speed/High-speed, Device/Host/OTG
Driver Library: Hardware peripheral software APIs that abstract away the intricacy of the device's hardware registers
Graphics Library: Create graphical user interfaces for MSP432 MCU-based systems incorporating a graphical display including the display driver layer, specific to the display in use; and the graphics primitives layer, which draws points, lines, rectangles, circles, text, and bitmap images. Image Reformer Tool: Image size and color depth manipulation utility used in Graphics Library
IQMathLib: A collection of highly optimized and high-precision mathematical functions for C programmers to seamlessly port a floating-point algorithm into fixed-point code on MSP432 microcontroller devices
Wide-ranging demo suite: Showcases several software libraries included in the SDK
Documentation: Comprehensive documentation and examples for each software components including software API Guides and User's Guides
Migration Guide from MSP432Ware: Guide provided in the SDK as well as on TI Cloud Resource Explorer

Download SimpleLink MSP432 SDK Installer

To download the SimpleLink MSP432 SDK installer file, for version 3.40.01.02 you can download here!

How To Install SimpleLink MSP432 SDK?

1. SimpleLink MSP432 SDK Installation using offline installer

After you have downloaded the SimpleLink MSP432 SDK installer file on the link above and save it on a directory/folder of your computer, double-click the exe file and then follow all of the installation steps until finished (See figure 2).

Figure 2. Install SimpleLink MSP432 SDK (Offline)

2. SimpleLink MSP432 SDK Installation from TI Resource Explorer (Online)

SimpleLink MSP432 SDK installation can be done online, i.e. using the TI Resource Explorer feature which has integrated on the Code Composer Studio IDE software. To do so, make sure that your computer has connected to the internet network (Online).

To get started install the SimpleLink MSP432 SDK via TI Resource Explorer, open the TI Resource Explorer, click “View” on the menu-bar, then select “Resource Explorer” option. Or you can also easy to do that by click the “Resource Explorer” on the “Getting Started” page (See figure 3). One you click the “Resource Explorer” option or button, the TI Resource Explorer welcome page will be opened for you (See figure 4).

Figure 3. TI Resource Explorer opening steps

Figure 4. TI Resource Explorer welcome page

Next, connect your SimpleLink MSP432 development kit to your computer. First, type your board/device name on the available blank field (See figure 4). Type “MSP432,” then there will appear drop-down of some TI board type. Select “MSP432P401R - Red 2” (See figure 5), then push the “DETECT MY BOARD” button on the TI Resource Explorer welcome page (See figure 6)

Figure 5. TI Board type drop-down

Once you push the “DETECT MY BOARD” button, the “DETECT MY BOARD” button changed as shown on figure 7 and It's sign that the MSP432P401R development kit has connected to the computer.

Figure 6. The “DETECT MY BOARD” button

Figure 7. The MSP432P401R development board has connected

Next, to get started install the SimpleLink MSP432P4 SDK. Click on “Software” root of TI Resource Explorer, then click on “SimpleLink MSP432P4 SDK” root, and push “Install” button on the up-right corner of TI Resource Explorer (See figure 8).

Figure 8. Steps to install SimpleLink MSP432P4 SDK

Once you push the “Install” button, the SimpleLink MSP432P4 SDK installation process will be started.

Figure 9. SimpleLink MSP432P4 SDK install confirmation

During the process, If the SimpleLink MSP432P4 SDK install confirmation windows opened, just click “Next” button (See figure 9), then wait the installation process until finished.

Source:

[1] SimpleLink MSP432 Software Development Kit (SDK)

How To Debug and Load Project Using Code Composer Studio

noreply@blogger.com (Taufiq D.S. Suyadhi) — Sat, 06 Apr 2019 15:45:00 +0000

robotics-university.com | Hello friends, if you build your embedded systems project using Texas Instruments microcontroller chips and Code Composer Studio IDE software, when you want to send your program-output into the target microcontroller chips, you have two options to choosen, i.e. Debug and Load. Have you known the difference and the equation between them? If haven’t yet, below I show you the method how to debug and load project using Code Composer Studio, then I also show you the comparisons between both of them.

1. PROJECT DEBUGGING

When using Code Composer Studio, debug means you load program-output to the target microcontroller chip and at the same time you can analyze or optimize your embedded systems project using project optimizer features. In order you can understand my explanation, please try debug a project. To debug a project, select “Run” menu then “Debug” on the Code Composer Studio menu-bar or press shortcut-key F11 (See figure 1).

Figure 1. Step to debug the project/program

Once you press “Run” menu then select “Debug (F11)” option on Code Composer Studio, the debug page feature (Analyze and Optimize feature) will be opened (See figure 2), among others Memory allocation tab, Optimizer assistant tab, Stack usage tab, and etc.

Figure 2. Code Composer Studio Debug feature page

And at the same time, the program-output sent to the target microcontroller chip (MSP432P401R). To see the hardware behavior and knowing the project result, push reset button on the SimpleLink MSP432 development kit.

2. PROGRAM LOADING

When using Code Composer Studio, load means you load program-output to the target microcontroller chip, after that you can see the hardware behavior and knowing the project result. To load a program (Load program to the target microcontroller chip only), select “Run” menu then “Load” and select “Select Program to Load” option on the Code Composer Studio menu-bar (See figure 3).

Figure 3. Step to load the program-output (1)

Then click “Browse” button to browse the program-output (See figure 4).

Figure 4. Step to load the program-output (2) - Browse the program-output

Open your related project folder (led_1 is my project folder), select the program-output (a program with “out” extension), next, press “Open” button (see figure 5), then press “OK” button (See figure 6).

Figure 5. Step to load the program-output (3) - Select the program-output (out file)

Figure 6. Step to load the program-output (4) - The selected program-output

Once you press “OK” button (see figure 6), the load program-output process will run and finally show Code Composer Studio Load feature page (See figure 7). See the hardware behavior to knowing the project result.

Figure 7. Code Composer Studio Load feature page

3. THE COMPARISONS BETWEEN DEBUG & LOAD

From the explanation above, we know about the different and the equation between Debug and Load. Below is Table 1 which give us knowledge about the Debug and Load comparisons.

Table 1. The Debug & Load Comparisons

After you know the different and the equation between Debug and Load, now it is depend on your needs to debug or to load. If you only want to send your program to the target microcontroller chip, use Load. But if you want to send your program to the target microcontroller chip and at the same time you also want to analyze or optimize your embedded systems project, use debug.

How To Build Project On Code Composer Studio

noreply@blogger.com (Taufiq D.S. Suyadhi) — Fri, 05 Apr 2019 15:24:00 +0000

robotics-university.com | Hello friends, when you have been finished to design your program on Code Composer Studio IDE software program editor, in order you can apply your program-output on the target microcontroller chip, you have to build (compile) it first. My today article will explain to you about how to build a project/program on Code Composer Studio. So, let’s continue reading and practice.

To build your program, just click “Project” menu on the Code Composer Studio and then select “Build Project” option (See figure 1). Once you click the “Build Project” option, the program building will run.

Figure 1. Build the created project

If the project building process run successfully, on the Code Composer Studio console section will generate notification that “ Build Finished” as we can see on the figure 2.

Figure 2. Project build status on Code Composer Studio console section

How To Create New Project and Hardware Connection Verify On Code Composer Studio

noreply@blogger.com (Taufiq D.S. Suyadhi) — Thu, 04 Apr 2019 14:57:00 +0000

robotics-university.com | Hello friends, when you getting started build your embedded systems project using Texas Instruments microcontroller chips and Code Composer Studio IDE software, it is important to know how to create new project and verify your hardware connection with your computer. My today article will explain to you about that. So, let’s continue reading and practice.

STEP 1: Open Code Composer Studio

To open the Code Composer Studio, double-click the shortcut (See figure 1) on your computer desktop or launch it from your computer “Start Menu.”

Figure 1. Code Composer Studio IDE shortcut

Figure 2. Opening display of Code Composer Studio IDE (v9.3.0)

STEP 2: Select A Directory As The Project Workspace

After you launch the Code Composer Studio shortcut, an “Eclipse Launcher: Select a directory as workspace” will opened (See figure 3). You need to determine a folder or directory as your project storage.

Figure 3. Eclipse Launcher: Select a directory as workspace window

Select your own workspace folder by push the Browse button. After you have selected your workspace folder, don’t check “Use this as the default and do not ask again” option, in order you can save another project file on the different folder/directory that you wanted. Then click the Launch button to go to the next steps (See figure 4).

Figure 4. Select your own workspace folder/directory

After you click Launch button, the Code Composer Studio main page will be opened (See figure 5).

Figure 5. Code Composer Studio main page

STEP 3: Create New Project

To create a new project on Code Composer Studio platform, select File-menu, then select New >> CSS Project (See figure 6).

Figure 6. Create new project

After that, a “New CCS Project” windows will be open for you. There, you have to set your project setting. See figure 7 and set your project setting with follow the project setting on that figure.

Figure 7. New Code Composer Studio (CCS) project setting

STEP 4: Verify Your Hardware Connection

Before you terminate (Finish) the new CCS project setting, it is better if you make sure that your MSP432 development kit has already connected with your computer. You can do it by click the “Verify” button on the right-side of connection section (See figure 7). For the connection status, once you push the “Verify” button, a “Verify Connection” windows will be opened (See figure 8). If the connection status “Succeeded,” it is sign that your MSP432 development kit has been connected with your computer. So, you can continue to go the next steps.

Figure 8. Development kit connection verification status

After you verify the connection of your MSP432 development kit with your computer and it is succeeded, next, push “Finish” button on the “Verify Connection” windows and on the “New CCS Project” windows (See figure 7 and figure 8). At the same time, a New CCS project has created (See figure 9).

Figure 9. New CCS project has created

LabVIEW and EPSON Robotics Library (DigiMetrix)

noreply@blogger.com (Taufiq D.S. Suyadhi) — Wed, 03 Apr 2019 04:08:00 +0000

robotics-university.com | Hello my friends, as usual, I hope all of you always in good condition. Today, I will talk about EPSON Robotics Library (toolkit) for LabVIEW. Have you been known about EPSON Robotics Library? If haven’t yet, lets follow my explanation about that.

A. What is EPSON Robotics Library (DigiMetrix) ?

EPSON Robotics Library is a LabVIEW toolkit that make us can control EPSON robot using LabVIEW graphical programming language. This toolkit developed by DigiMetrix. On their official website they give an overview about this toolkit.

With the Epson library, you can easily integrate robotics into new types of systems and applications for automated test, laboratory automation, and flexible manufacturing – eliminating complex robotics programming expertise. The library features easy-to-use native LabVIEW VIs for controlling and commanding robots directly from a graphical development environment. With this library, you can program a single LabVIEW application that integrates all aspects of machine control and automation from part-handling and robot control to advanced measurements, inspection, machine vision and HMI. Using this approach, you do not need to learn specialized robotics programming software, which means you can achieve higher performance and better results in less time.
The entire application is developed in NI’s powerful LabVIEW Graphical Design Environment. It can be downloaded for execution to various Windows or LabVIEW Real-Time targets like smart cameras, NI CompactRIO, and NI PXI platforms to achieve industry-proven speed and reliability.
3D factory simulation from Visual Components allows you to start your project even without real robots and continue with offline programming, collision detection and pass planning to be prepared for deploying to real-world setup!

B. Download EPSON Robotics Library for LabVIEW

To get EPSON Robotics Library package, we can download it from this link below:

http://www.ni.com/gate/gb/GB_EVALTLKTEPSON/US

Figure 1. Download EPSON Robotics Library

C. EPSON Robotics Library on VIPM 2019

If you have installed virtual instrument package amanager (VIPM) 2019 to support your LabVIEW software. There is already available EPSON Robotics Libary (toolkit) on the package/toolkit list, so we just install it if we want to start working with it. See figure 2!

Figure 2. EPSON Robotics Libary (DigiMetrix) on VIPM 2019 toolkit list

If you see figure 2 above, on the VIPM 2019 toolkit list available two EPSON Robotics Library, i.e. one developed by ImagingLab and one developed by DigiMetrix. But on this article, I just talk about EPSON Robotics Library that developed by DigiMetrix.

Note:

From the DigiMetrix “DM_EpRL_Controller_setup_manual.pdf” document file, if on VIPM toolkit list has been installed the two EPSON Robotics Library, we are recomended to uninstall the EPSON Robotics Library by ImagingLab.

D. Install EPSON Robotics Library for LabVIEW

To start EPSON Robotics Library installation, first open the VIPM software with administrative privileges. To do so, right-click on VI Package Manager launcher (shortcut) and select Run As Administrator. See figure 3!

Figure 3. Run VIPM as Administrator

If EPSON Robotics Library has been available on the VIPM 2019 toolkit list, to install, there is two method option that you can choose. The first method, select EPSON Robotics Library on the VIPM 2019 toolkit list and then click “Install” button on the VIPM 2019 toolbar. See figure 4!

Figure 4. Step to start EPSON Robotics Libary installation (1)

For the second method, you just right-click the EPSON Robotics Library on the VIPM 2019 toolkit list and then click “Install” option to start the installation. See figure 5!

Figure 5. Step to start EPSON Robotics Libary installation (2)

After that, a “Package Action Confirmation” window will open. Click “Contrinue” button. See figure 6!

Figure 6. Package action confirmation

If “VIPM Package License Agreement” window appear, click “Yes, I accept these license Agreement (s) Install Packages” button. See figure 7!

Figure 7. VIPM - Package License Agreement

After you have accepted the license agreement, the installation process will open LabVIEW Front Panel to synchronize the EPSON Robotics Library license. See figure 8!

Figure 8. EPSON Robotics Library license synchronize

Figure 9. EPSON Robotics Library installation in progress

The installation process will continue until a “Last Action Result” window appear. The “Last Action Result” window inform that the EPSON Robotics Library package and its license has been installed successfuly with no error. See figure 9 and figure 10!

Figure 10. EPSON Rrobotics Library installation has been finished with no errors

Figure 11. EPSON Rrobotics Library has been installed on VIPM and ready to use

On the “Last Action Result” window, click “Finish” button, next on the VIPM toolkit list will show that the EPSON Rrobotics Library has been installed on VIPM and ready to use. See figure 11!

E. Introduce to EPSON Robotics Library Control & Function Palette

Figure 12 until figure 16 show to us the EPSON Robotics Library control and function palette. Availabled function of EPSON Robotics Library are Main function, Motion function, Input/Output function, Application function, and Advanced function.

Figure 12. Main function

Figure 13. Motion function

Figure 14. In/Out function

Figure 15. Application function

Figure 16. Advanced function

F. LabVIEW Graphical Program Examples Using EPSON Robotics Library

On DigiMetrix official website, there is displayed LabVIEW graphical code example for us. So we can use it to start learn LabVIEW graphical program using EPSON Robotics Library to control EPSON robot. See figure 17 to figure 19!

Figure 17. Code example-1

Figure 18. Code example-2

Figure 19. Code example-3

G. Vision Robot Guidance for EPSON SCARA Robot Powered by NI LabVIEW

Source:

[1] Epson Robotics Library - DigiMetrix

Code Composer (CoCo) Studio

noreply@blogger.com (Taufiq D.S. Suyadhi) — Wed, 03 Apr 2019 03:48:00 +0000

robotics-university.com | Hello my friends, I hope you are always in good condition. Now, on this article, I will give information about an integrated development environment (IDE) software that provided by Texas Instruments (TI). The IDE that I mean is Code Composer Studio or sometime I call it with CoCo Studio. Figure 1 show us the CoCo Studio opening display.

Figure 1. Code Composer Studio - Opening display

Figure 2. Code Composer Studio - main page

What Can We Do with Code Composer Studio?

Once you open the Code Composer Studio, you can do all of activities below:

I. Preparation – Learning before working

1. Learn how to use Coco Studio to get started build an embedded systems project by browse and read project example, training, and documentations.

Figure 3. Resource Explorer feature

2. Learn how to perform various tasks from video tips

Figure 4. Video tips feature

II. Getting Started to Develop an Embedded Systems Project

1. Install additional tools (For instance: SimpleLink SDK, MSP432Ware, FreeRTOS, etc.) after knowing the function if it applied to a special project from Resource Explorer and Video tips.

Figure 5. Install additional tools

2. Create new project or import existing example project from Resource Explorer

Figure 6. Create a new project

Figure 7. Import existing project

3. Write your program on the text-editor.

Figure 8. Write program on the text-editor

4. Build/Compile your program when it is finish created.

Figure 9. Step to build/compile program

5. Debug your program to know if your program still has errors or not.

Figure 10. Step to debug program

6. Load your program to the microcontroller chip.

Figure 11. Step to load program to the microcontroller chip

III. Access Technical Support Forum

If there are some difficulties when you working with Code Composer Studio, you can try to get the solution by ask about your problem to the support forum (E2E forums) or by read topics discussion on that forum which has related with your problem, in order your problem solved.

Figure 12. Support forum feature

IV. Trace the Energy consumption of your embedded systems

EnergyTrace software for MSP430 MCUs, MSP432 MCUs, CC13xx wireless MCUs and CC26xx wireless MCUs is an energy-based code analysis tool that measures and displays the energy profile of an application and helps optimize it for ultra-low-power consumption.

Figure 13. Energy Trace technology feature

V. Using Analysis and Optimization Tools

CCS includes several productivity tools and views to help you analyze and optimize your application. Some of these are described below.

1. ULP (Ultra-Low Power) Advisor (for MSP430 MCU)

ULP Advisor is a static code analysis tool that scans source code against a thorough set of low-power coding rules to help squeeze every last nano amp out of your application. ULP Advisor is enabled by default for MSP430 projects and can be enabled for ARM projects. The analysis runs as part of the build. Any notifications and remarks to highlight areas of code that can be further optimized will be displayed in the Advice view.

Figure 14. Advice tab - Power ULP Advice (for MSP430 MCU)

Selecting an item in the Advice view will open detailed information on the rule that triggered the advice as well as example code that shows how to improve the application for better power usage. It is then up to the developer to either act on the advice or leave their application as-is.

Figure 15. Detail information of an item on the Advice tab

2. Optimizer Assistant

Optimizer Assistant is a static code analysis tool that scans source code and provides advice on how the code could be changed to improve performance. In addition it can also help with determining the ideal set of build options for obtaining the best optimization while staying within code size constraints. The initial analysis of the source code takes place automatically during the build and any advice will display in the Advice view. Selecting an item in the Advice view will open up a window providing more information on how the code may be improved.

Figure 16. Advice tab - Optimization advice

To determine the ideal set of build options for your project, select the Optimizer Assistant from the View menu. Click on Start Analysis to begin the analysis.

Figure 17. Optimizer assistant

3. Code Generation Tools XML Processing Utilities

This is a package of command line utilities used to process the XML files that come from the TI code generation tools. Use it to do things like build a spreadsheet that details the size of all the sections, or figure out how much of the memory map is taken up by specific libraries.

4. Memory Allocation view

The Memory Allocation View in Code Composer Studio provides a graphical representation of how much memory is consumed by your application. To open the view go to the CCS menu View and select Memory Allocation. By default, the view shows the memory used relative to the total available memory for the project that is active in the Project Explorer view. You can expand each memory region to see how much memory each individual section or sub-section is using.

Figure 18. Memory Allocation tab

5. Stack Usage View

The Stack Usage View in Code Composer Studio (available in CCS 6.2 and higher) provides a static view of stack usage for your application. The information is generated on project build and displayed as a function call tree with stack usages for each function in a horizontal bar graph. To open the view go to the CCS menu View and select Stack Usage.

Figure 19. Stack usage tab

The view shows Exclusive Size and Inclusive Size by function. The Exclusive Size is the amount of stack required by that function, ignoring any functions it may call. The Inclusive Size is the amount of stack required by that function, plus the amount of stack required by all the functions called by that function, applied recursively. So, if f1 calls f2, which calls f3, which calls f4, and so on, the amount of stack required by each of those functions is added in for the Inclusive Size.

The size values shown in the view are in bytes. The color shading indicates whether you are close to the limit of available stack space (shown as yellow) or not (shown as green). To avoid hitting the limit, you could free up some stack usage or increase the system stack size.

Source:

[1] Code Composer Studio IDE for MSP Microcontroller

[2] EnergyTrace Technology

[3] Analysis and Optimization Tools

SimpleLink MSP432P401R Development Kit

noreply@blogger.com (Taufiq D.S. Suyadhi) — Mon, 01 Apr 2019 06:58:00 +0000

robotics-university.com | Hello my friends, on this article, I will give an overview about one of the popular microcontroller minimum systems/development kit/evaluation board which manufactured by Texas Instruments (TI). The product I mean is SimpleLink MSP432P401R Development kit, please see figure 1 to know the visualization and figure 2 to know the top-view layout.

According to the user guide document of this development kit [2], The SimpleLink™ MSP432P401R LaunchPad™ development kit enables you to develop high-performance applications that benefit from low-power operation. It features the MSP432P401R – which includes a 48MHz ARM Cortex-M4F, 80uA/MHz active power and 660nA RTC operation, SAR Precision ADC with 16-bit performance and AES256 accelerator.

All pins of the MSP-EXP432P401R device are fanned out for easy access. These pins make it easy to plug in 20-pin and 40-pin BoosterPack modules that add additional functionality including Bluetooth low energy, Wi-Fi wireless connectivity, and more.

The out-of-box provided with the MSP-EXP432P401R LaunchPad kit features a graphical user-interface that enables the user to type in the desired beats per minute of an RGB LED, and select from over 16 million color options. See how simple it is to get started, with the MSP432 Quick Start Guide.

You can browse all documentation online with TI Resource Explorer and start development with SimpleLink MSP432 software development kit (SDK) and related SDK plugins, which make it easy to add Bluetooth low energy or Wi-Fi when adding a SimpleLink wireless BoosterPack. Other professional development environments are also available, such as TI's online CCS Cloud IDE, Eclipse-based Code Composer Studio, IAR Embedded Workbench, and Keil uVision.

This LaunchPad kit includes an on-board emulator with EnergyTrace+ Technology, which means you can program and debug your projects without the need for additional tools, while also measuring total system energy consumption.

Figure 1. SimpleLink MSP432P401R development kit

SimpleLink MSP432P401R Development Kit Features

Low-power, high performance MSP432P401R MCU

48MHz 32-bit ARM Cortex M4F with Floating Point Unit and DSP acceleration
Power consumption: 80uA/MHz active and 660nA RTC standby operation
Digital: Advanced Encryption Standard (AES256) Accelerator, CRC, DMA, HW MPY32
Memory: 256KB Flash, 64KB RAM
Timers: 4 x16-bit, and 2 x 32-bit
Communication: Up to 4 I2C, 8 SPI, 4 UART

40 pin BoosterPack Connector, and support for 20 pin BoosterPacks
Onboard XDS-110ET emulator featuring EnergyTrace+ Technology
2 buttons and 2 LEDs for User Interaction
Back-channel UART via USB to PC

Figure 2. SimpleLink MSP432P401R development kit (Top-view layout)

SimpleLink MSP432P401R Development Support Software

To getting started to develop an embedded systems project or prototype using SimpleLink MSP432P401R development kit, TI has provided an integrated development environment (IDE) that you can use for free. The IDE name is Code Composer Studio for MSP microcontroller. To download and get more information about this IDE, please visit the website page below:

http://www.ti.com/tool/CCSTUDIO-MSP

And to get the latest version of this IDE, please visit this page below:

http://www.ti.com/tool/download/CCSTUDIO

Sources:

[1] SimpleLink MSP432P401R high-precision ADC LaunchPad Development Kit

[2] MSP432P401R SimpleLink Microcontroller Development Kit – User Guide

[3] Code Composer Studio IDE for MSP Microcontrollers

[4] MSP432P401R Microcontroller Datashet

MSP430 LaunchPad Development Kit

noreply@blogger.com (Taufiq D.S. Suyadhi) — Wed, 27 Mar 2019 04:21:00 +0000

robotics-university.com | Hello my friends, on this article, I will give an overview about one of the popular microcontroller minimum systems/development kit/evaluation board which manufactured by Texas Instruments (TI). The product I mean is MSP430 LaunchPad Development kit, please see figure 1 to know the visualization and figure 2 to know the top-view layout.

According to the user guide document of this development kit [2], the MSP430 LaunchPad Development kit is an inexpensive and simple development kit for the MSP430G2xx Value Line series of microcontrollers. It is an easy way to start developing on the MSP430 MCUs with on-board emulation for programming and debugging as well as buttons and LEDs for a simple user interface.

Rapid prototyping is simplified by the 20-pin BoosterPack™ plug-in module headers which support a wide range of available BoosterPack plug-in modules. You can quickly add features like wireless connectivity, graphical displays, environmental sensing, and much more. You can either design your own BoosterPack plug-in module or choose among many already available from TI and third-party developers.

The LaunchPad development kit features an integrated DIP target socket that supports up to 20 pins, allowing MSP430 Value Line devices to be plugged into the LaunchPad development kit. The MSPEXP430G2 LaunchPad development kit comes with an MSP430G2553 MCU by default. The MSP430G2553 MCU has the most memory available of the compatible Value Line devices. The MSP430G2553 16-bit MCU has 16KB of flash, 512 bytes of RAM, up to 16-MHz CPU speed, a 10-bit ADC, capacitive-touch enabled I/Os, universal serial communication interface, and more – plenty to get you started in your development.

Figure 1. MSP430 LaunchPad development kit

MSP430 LaunchPad Development Kit Features

USB debugging and programming interface featuring a driverless installation and application UARTserial communication with up to 9600 Baud.
Supports MSP430G2xx2, MSP430G2xx3, and MSP430F20xx devices in PDIP14 or PDIP20 packages.
Two general-purpose digital I/O pins connected to green and red LEDs for visual feedback
Two push button for user feedback and device reset
Easily accessible device pins for debugging purposes or as socket for adding customized extension boards.
High-quality 20-pin DIP socket for an easy plug-in or removal of the target device

Figure 2. MSP430 LaunchPad development kit (Top-view layout)

MSP430 LaunchPad Development Support Software

To getting started to develop an embedded systems project or prototype using MSP430 LaunchPad development kit, TI has provided an integrated development environment (IDE) that you can use for free. The IDE name is Code Composer Studio for MSP microcontroller. To download and get more information about this IDE, please visit the website page below:

http://www.ti.com/tool/CCSTUDIO-MSP

And to get the latest version of this IDE, please visit this page below:

http://www.ti.com/tool/download/CCSTUDIO

Key Documents

Below is some documents that useful for you to getting started using MSP430 LaunchPad development kit:

1. MSP-EXP430G2 Software Examples (Rev. F)

2. MSP-EXP430G2 LaunchPad Development Kit User's Guide (Rev. G)

3. MSP-EXP430G2 Hardware Design Files (Rev. C)

Source:

[1] MSP430G2 LaunchPad Development kit

[2] MSP-EXP430G2 LaunchPad™ Development Kit - User Guide

[3] Code Composer Studio IDE for MSP Microcontrollers

Texas Instruments Microcontroller

noreply@blogger.com (Taufiq D.S. Suyadhi) — Sun, 24 Mar 2019 18:20:00 +0000

robotics-university.com | Texas Instruments (TI) is one of the big semiconductor company in the world. TI’s semiconductor products are so many kinds of special function chips like Amplifiers, Audio, Clocks & timing, Data converters, Interface, Isolation, Logic, Microcontrollers, Motor drivers, Power management, Processors, RF & microwave, Sensors, Space & harsh environment, Switches & multiplexers, Wireless connectivity, and more. TI’s technologies are at work in every type of electronic system in markets that include Industrial, Automotive, Personal electronics, Communications equipment, and Enterprise systems

TI’s Microcontroller

Microcontroller become one of the TI products, for this line product, TI provide a portfolio of low-power, high-performance microcontrollers (MCUs) with wired and wireless options. Supported by a common RTOS software platform, the consumers have access to a robust development ecosystem that includes LaunchPad Development Kits. TI offer the right mix of silicon, software and development tools to differentiate and get your product to market faster.

The Types of TI’s Microcontroller Products

1. SimpleLink MCU

The broadest portfolio of wired and wireless Arm Cortex-M based MCUs with the lowest power, advanced security and best-in-class analog integration.

2. MSP430 MCU

TI’s MSP430 microcontroller (MCU) portfolio offers a wide variety of 16-bit MCUs with ultra-low-power and integrated analog and digital peripherals for sensing and measurement applications.

3. C2000 MCU

C2000 real-time controllers are a portfolio of high-performance microcontrollers that are purpose-built to control power electronics and provide advanced digital signal processing in industrial and automotive applications. In over 20 years at the forefront of the analog to digital control revolution, C2000 MCUs have evolved to provide precision sensing, powerful processing, and premium actuation to enable engineers to create the world’s most efficient power control systems.

TI’s Microcontroller Embedded Systems Design Tools

To give support for the consumers, TI provide so meaning-full tools to design and develop theirs embedded systems prototype or projects. The tools are 1) Hardware kits boards, 2) Code Composer Studio IDE, and 3) Software Development Kits (SDK).

1. Hardware Kits Boards

TI cross-compatible portfolio of modular evaluation and development hardware pair perfectly with scalable online and offline software to help you get your products to market faster. From affordable microcontroller hardware development kits (LaunchPads™) to 80+ functional plug-in modules (BoosterPacks™), we have the hardware you need to get your embedded development project off the ground.

Figure 1. SimpleLink MSP432P401R development board (for example)

Starting from evaluation to prototyping to development and optimization, the SimpleLink™ platform offers simple yet powerful hardware and software tools that enable you to ramp up quickly based on your customer needs. You only need to learn one unified, consistent development platform regardless of the SimpleLink MCU you’re using.

2. Code Composer Studio IDE

TI robust development environment, centered on Code Composer Studio™ IDE, is built with your convenience and ease-of-use in mind. You need to get to market fast, iterate faster, and scale your innovations quickly and seamlessly across diverse families of equipments. From our unique cloud environment of easy resource exploration and browser-based development tools to advanced debugging on your desktop, our development tools enable your journey from discovery to production.

Figure 2. Code Composer Studio IDE

3. Software Development Kits (SDK).

TI Software Development Kits (SDKs) provide all needed components to start embedded systems development, are fully tested and integrated, and release quarterly. Get to market faster with our operating systems, middleware/frameworks and stacks, application examples, demos, documentation and training--all packaged together for your convenience.

What's an SDK?

Application software consists of simple software commands that you want the hardware to do, typically C or ASM code. Development tools like IDEs, compilers, and debug probe allow you to create that application code for a given evaluation or development board. SDKs, though, are intended to solve bigger problems. Operating systems, peripheral drivers, hardware abstraction, protocols, and libraries all need to work together seamlessly--that's why our kits include all of these necessities and come fully tested and integrated.

Source:

[1] 16-bit and 32-bit microcontrollers

[2] SimpleLink MCUs

[3] MSP430 ultra-low-power sensing & measurement MCUs

[4] C2000 32-bit microcontrollers

[5] Embedded development hardware kits & boards

[6] Code Composer Studio IDE & development tools

[7] Embedded development software

HC-08 Module - Bluetooth Low Energy V4.0

noreply@blogger.com (Taufiq D.S. Suyadhi) — Thu, 07 Mar 2019 09:36:00 +0000

robotics-university.com | Hello friends, talking about wireless communication with Bluetooth technology, there is one useful Bluetooth module which can be use. The Bluetooth module that I mean is HC-08 (Bluetooth Low Energy V4.0) module (See figure 1). On today article, I will give an overview about that module. In general, this module used by embedded systems developer or hobbist to make wireless application with apply Bluetooth low energy (BLE) V4.0 technology.

Figure 1. HC-08 (Bluetooth Low Energy V4.0) module

HC-08 (BLE V4.0) Module Introduction

Quote from the HC-08 module, there are mention that HC-08 Bluetooth UART communication module is a new generation of Bluetooth specification V4.0 BLE Bluetooth protocol based on the transmission module. Wireless working frequency is 2.4GHz ISM, modulation is GFSK. The maximum transmit power module 4dBm, the receiving sensitivity is -93dBm, and iphone4s can achieve 80 meters of super long-distance communication under open environment.

The module uses the stamp hole encapsulation, can patch welding, module size is 26.9mm * 13mm * 2.2mm, very convenient to the customer within the embedded application system.

The module uses the CC2540 chip, the configuration of the 256K Byte space, supports AT command, the user can according to need to change role and the serial baud rate, equipment name and other parameters, the use of flexible.

Figure 2. CC2540 chip on the HC-08 (BLE V4.0) module main processor

HC-08 (BLE V4.0) Module Dimension

The dimension of HC-08 (BLE V4.0) module hardware are shows as on the figure 3 below.

Figure 3. HC-08 (BLE V4.0) module - dimension

HC-08 (BLE V4.0) Module Pins Description

In order you can use this HC-08 (BLE V4.0) module, you have to know the pins description, so you will get this Bluetooth module work as your expectation. See figure 4.

Figure 4. HC-08 (BLE V4.0) module - pin description

From figure 3 above, we know that HC-08 (BLE V4.0) module has 30 pins and also equipped with on board PCB antenna. Pin specific definitions are listed in the following table:

Table 1. HC-08 (BLE V4.0) module - pin description

For the detail information about HC-08 (BLE V4.0) module pin description, you can download and read its document support (User Manual) from the link which available on the “Source” section of this article.

In the using, HC-08 module placed on the top of an adapter, so the pins that used for interfacing become six pins only, i.e. TXD, RXD, GND, VCC, and two additional pins of the adapter, i.e. State and Key. See figure 4 for the detail.

Figure 5. HC-08 (BLE V4.0) module pin description on the top of its adapter

HC-08 (BLE V4.0) Module AT Commands

For the operation, the HC-08 (BLE V4.0) module parameters have to set using AT command. AT commands are instructions used to control and configure a modem or bluetooth module functionalities. AT is the abbreviation of ATtention. Every command line starts with "AT" or "at". That's why that commands are called with AT commands. Below is the AT commands list to configure the function of HC-08 (BLE V4.0) module.

Table 2. AT commands list for HC-08 (BLE V4.0) module configuration

For the detail information about HC-08 (BLE V4.0) module AT command, you can download and read its document support (User Manual) from the link which available on the “Source” section of this article.

Source

[1] HC-08 (BLEV4.0) module user manual

[2] Bluetooth Low Energy

LabVIEW and LINX Toolkit

noreply@blogger.com (Taufiq D.S. Suyadhi) — Sat, 12 Jan 2019 09:20:00 +0000

robotics-university.com | Hello my friends, as usual, I hope all of you always in good condition. Today, I will talk about LINK toolkit for LabVIEW. Have you been known about LINX toolkit? If haven’t, lets follow my explanation about that.

A. What is LINX?

From the National Instrument official website they said that LINX is:

LINX is an open source project by Digilent and is designed to make it easy to develop embedded applications using LabVIEW. LINX includes VIs for over 30 of the most common embedded sensors as well as hardware agnostic APIs for accessing peripherals like digital I/O, analog I/O, PWM, I2C, SPI, and UART.

Whether you’re remotely controlling a chipKIT or Arduino over USB/Serial, Ethernet or Wi-Fi, or deploying VIs to run on BeagleBone Black or Raspberry Pi 2/3, LINX and LabVIEW make it easy visualize the data you’re working with, debug your code, and create advanced embedded applications faster than ever before.

And for additional information, they also said that LINX is:

Digilent LINX is the successor of LabVIEW Interface for Arduino (LIFA). Both packages are from the same software author who recommends migrating to LINX. LINX is designed to be a more generic hardware abstraction layer for embedded devices, rather than designed for just one specific microcontroller platform.

My Notes:

From the information above, I will take a note that LINX toolkit can support for chipKIT, Arduino, BeagleBone, Raspberry Pi, and more. Click here to know supported devices by LINX.

B. Download Digilent LINX for LabVIEW

To get LINX toolkit package, we can download it from this link below:

http://www.ni.com/gate/gb/GB_EVALTLKTLINXLVH/US

To start download LINX toolkit (vip) file, just click on “Download from FTP” link (see figure 1) and then a page that contains with list of LINX toolkit file download in some version will opened (See figure 2). Select the latest version and click the link to start the downloading process.

Figure 1. LINX toolkit download page and link

Figure 2. LINX toolkit download page and link

Figure 3. Determine a directory to save the LINX toolkit (vip) file

C. Install Digilent LINX for LabVIEW (Offline)

After the download process is complete, now it’s time to install the LINX toolkit package on VIPM. To install it, please follow my guidance to offline install a LabVIEW toolkit package on my previous article here.

D. Download & Install Digilent LINX for LabVIEW (Online)

Beside offline installation, we can also install the LINX toolkit package with online mode, it mean, we need internet connection to do the installation process. To online download and install LINX toolkit on VIPM, follow the steps below:

1. Connect our computer with internet.

2. Make sure you have been installed VIPM on your computer.

3. Visit this link - http://www.ni.com/gate/gb/GB_EVALTLKTLINXLVH/US and click “Download Toolkit” button. See figure 4

Figure 4. Download button to download & install LINK toolkit (online)

Figure 5. Install button to download & install LINK on VIPM

After we press the “Download Toolkit” button, then VIPM software will automatically opened and an installation page as display on Figure 5 will open. To start download and install LINX toolkit, just click the “Install” button and the download/install process will start to run.

Figure 6. LINK toolkit package has been installed successfully on VIPM

Figure 7. LINK toolkit package has been installed successfully on VIPM

If the installation process has been completed (See Figure 6), so on the VIPM package list will display a LabVIEW icon on the left-side of the “Digilent LINX” toolkit. See figure 7!

E. Introduce to LINX Control & Function Palette

Figure 8, show to us the LINX toolkit function palette.

Figure 8. LINK toolkit palette

Source:

[1] LINX by Digilent/LabVIEW MakerHub

[2] How To Download Digilent LINX For LabVIEW?

[3] Download LINX - LabVIEW MakerHub

[4] LabVIEW and Virtual Instrument Package Manager (VIPM)

[5] Download and Install LabVIEW Interface for Arduino (LIFA) toolkit

LabVIEW Interface for Arduino (LIFA) Toolkit Replaced By LINX Toolkit

noreply@blogger.com (Taufiq D.S. Suyadhi) — Fri, 11 Jan 2019 09:56:00 +0000

robotics-university.com | Hello my friends, with this article I want to say to you that LabVIEW Interface for Arduino (LIFA) toolkit has been replaced by LINX toolkit. You can found the official information from National Instrument by visit this page:

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019SBnSAM&l=en-ID

On that page, they said that:

“The package LabVIEW Interface for Arduino (LIFA) has been replaced with LINX. It is highly recommended to migrate to LINX as there will be no further development for LIFA. See How To Download Digilent LINX For LabVIEW? for more information.”

But don’t worry, National Instrument is still give support if you want to use LIFA toolkit, although it will no update again:

“LabVIEW Interface for Arduino (LIFA) is a third-party Add-On for LabVIEW. National Instruments gives support for it through the www.ni.com/arduino Discussion Forum. This forum is constantly monitored by Arduino/LabVIEW users. You can also find documents, examples, and share knowledge there.”

LabVIEW-Arduino - Getting Started Using LIFA Toolkit

noreply@blogger.com (Taufiq D.S. Suyadhi) — Thu, 10 Jan 2019 09:13:00 +0000

robotics-university.com | Hello my friends, hope all of you always in good condition. Today, I will guide you to build the first LabVIEW application project that implement LabVIEW Interface for Arduino (LIFA) toolkit that we had been installed on Virtual Intrument Package Manager (VIPM). I have explained about the steps on my previoous article, please click here!

A. Hardware - Arduino & LED Circuits

Below is the circuits of a Light Emitting Diode (LED) component that connected on the fourth pin of Arduino Uno board. See figure 1!

Figure 1. Arduino Uno & LED circuits

In order we can control the LED, connect the Arduino board via USB port to a computer (PC/Laptop) that LabVIEW and LIFA toolkit has been installed on that. See figure 2!

Figure 2. LabVIEW, LIFA, and Arduino Uno board

B. Program Descriptions

For this project, we have to create a LabVIEW graphical program that has purpose to control LED (ON/OFF) condition. If a Light Emitting Diode (LED) component that connect to a selected Arduino pin (in this project I use fourth pin. See figure 1) set to one (HIGH logic) using "Digital Write Pin" LIFA object, the LED on that pin will light up (ON condition), vice-versa, if selected Arduino pin set to zero (LOW logic), the LED will in OFF condition.

C. Text-based Program

If we create a text-based program to control LED (ON/OFF) condition with follow the program description on B point above. The program is as shown on the figure 3 below. I type that code on Arduino IDE software.

Figure 3. Arduino text-based program typed on Arduino IDE

The program will make the LED on the Arduino fourth pin in light up (ON condition) when the LED variable equal to one (HIGH logic), vice-versa, the LED will in OFF condition when the LED variable equal to zero (LOW logic).

D. Graphical Program on LabVIEW Block Diagram

If we want to control the LED (ON/OFF) condition using LabVIEW, We can’t using text-based programming, but we have to create a graphical program. With follow the program description on B point above, we can create graphical program as shown on the figure 4 below (See figure 4). The graphical program on figure 4 represented text-based program on figure 3. So if we run the both program, they will have same output, i.e. output signal to control LED (ON/OFF) condition.

Figure 4. LabVIEW graphical program using LIFA toolkit

Table 1. Used LIFA object

If we see on figure 4, that graphical program using four LIFA objects, i.e. “Init” object, “Set Digital Pin Mode” object, “Write Digital Pin” object, and “Close” object (See Table 1). In order, we can create a complete and right LabVIEW graphical program, we have to know the descriptions of each LIFA object that used. To do that, we can see the object description of each “Context Help” window.

Context Help

If you want to know the description of an object which you want to use it when create a LabVIEW graphical program, you can use “Show Context Help” option to do that. To start use the option, on Block Diagram window, click Help menu, then select “Show Context Help” option or you can use shortcut key “Ctrl + H.” See figure 5!

Figure 5. Step to Show Context Help

After you select “Show Context Help” option, then left-click an object to open a “Context Help” window of the object. Once you click an object, the descriptions of the clicked object will show on its context help window. On this example, the descriptions of “Init” object, “Set Digital Pin Mode” object, “Write Digital Pin” object, and “Close” object shown on Figure 6, Figure 7, Figure 8, and Figure 9.

Figure 6. Click “Init” object to open its context help window

Figure 7. Click “Set Digital Pin Mode” object to open its context help window

Figure 8. Click “Digital Write Pin” object to open its context help window

Figure 9. Click “Close” object to open its context help window

Create Your Own LabVIEW Graphical Program

To start create your own LabVIEW graphical program, you can follow my example LabVIEW graphical program on Figure 4. For your information, when create a LabVIEW graphical program using LIFA toolkit, we have to start the program with “Init” object (Init.vi) and with “Close” object (Close.vi) for the ending.

E. Graphical User Interface on LabVIEW Front Panel

Figure 10, show to us a Graphic User Interface (GUI) application that automatically created on LabVIEW Front Panel window when we create graphical program on LabVIEW Block Diagram window.

Figure 10. GUI to control LED (ON/OFF) condition

The main part of the GUI on Figure 10, is a “STOP” button and a “Numeric Control.” Stop button use to stop program looping (on this example, While Loop), in order the program stop running. While “Numeric Control” use to set the pin-value (0 logic or 1 logic) of “Digital Write Pin” object.

F. LabVIEW Project - Complete

Figure 11, show to us an image of a complete LabVIEW project using LIFA toolkit package. There are displayed the Project Explorer window, the Front Panel window, and the Block Diagram window.

Figure 11. LabVIEW project - GUI on Front Panel & Graphical Program on Block Diagram

G. Run the Graphical Program

To start running our LabVIEW application that we have created, click on “Run” button (See figure 12), either “Run” button on Front Panel tool-bar or “Run” button on Block Diagram tool-bar.

Figure 12. Click “Run” button to start running LabVIEW application

Then see on the Arduino board, the LED on fourth-pin will be in ON condition if on the Numeric Control, we set the value is one (1, High logic) and will be in OFF condition if we set the value is zero (0, Low logic). See figure 12.

________________________________

Note:

If you face errors when you follow my guidance to create LabVIEW project using LIFA toolkit, I recommend you to read article entitled “LabVIEW Interface for Arduino Error 5002: Unable to EstablishConnection”