Rei Vilo

Thank you Sir for recommending node-red. That is very interesting.
In about an hour, I was able to figure out how to:
Install node-red Connect it to my mosquitto server Install the node-red dashboard Configure node-red to display live data from one mqtt channel Nice!
Now I have to program my datalogger to gather and report data. \o/ yay

@zeke Why not give Node-RED a try?
I’m very happy with Node-RED. It provides a GUI IDE, supports natively a variety of formats / protocols like JSON and MQTT, and features its own dashboard. It is expandable with additional nodes, for example to  interface with an SQL database.
See my reviews and projects at 
https://embeddedcomputing.weebly.com/iot-with-node-red.html,  https://embeddedcomputing.weebly.com/sensortag-to-blynk-using-node-red.html and  https://embeddedcomputing.weebly.com/isup2c-smartnode-smart-device.html.  To get this...

... you just need that...

In case you need to stock up on MSP430 dev boards, it's MSP430 week in the TI store.
http://www.ti.com/store/featured/msp430week18.html

 

Well, it had been way too long since I worked on this project so decided to get busy this week.
I just finished assembling four prototypes and now I am debugging the hardware. 
I still have to write some device drivers and design a rudimentary operating system for it.
At this time, I am planning on having the datalogger report its results over the serial port. Another program will be waiting for the results to come in. I want to store them in some sort of database then display them in some sort of dashboard. 
I want to keep the overall complexity of the system low because I am afraid of not completing the project. I am the customer.
You may be asking "Why?" 
Because I want to keep my skills up and I want to force myself to learn new things.
Feel free to ask questions.
 

Maybe we can ask @bluehash to make this a sticky thread with the appropriate subject name?

Wire.begin(ADXAddress);  configures the TM4C129 as an I²C slave, not an I²C master.
Please refer to http://energia.nu/reference/wire/wire_begin/

Wire.begin(ADXAddress);  configures the TM4C129 as an I²C slave, not an I²C master.
Please refer to http://energia.nu/reference/wire/wire_begin/

For the boards supporting EMT, try the Galaxia library.
Which board are you targeting? Which library are you referring to? About posting a question and porting libraries from Arduino to Energia, see
 
 
 

LaunchPad and BoosterPack Pins Maps Find the pins map at LaunchPads and BoosterPacks Pins Maps, Energia website and BoosterPack Checker.

Check the usual suspects:
Is the I²C bus initialised? Wire.begin(); Does the I²C device run at 3.3V? Otherwise, use a logic-level converter.
Are pull-ups installed? Try 10, 4.7 or 2.2 kΩ for the SDA and SCL lines.
In case the LaunchPad provides multiple I²C ports, is the correct port selected? Try 
Wire.setModule(0); // or other port number Wire.begin(); Still nothing? Use a logic analyser to trace the signals on the I²C port.

(To be continued...)

Following Rei's advice, I'm using embedXcode.
It works very nicely, great work Rei.

Some topics come aver and over again. Here are the most frequent questions.
Wouldn't be nice to have all of them in one single place?
Listed questions:
Netiquette for Newbies What Information to Provide When Asking for Help I²C Check-List  Porting an Arduino library to Energia Use Pins Number instead of Pins Names with Energia Add a New Board to Energia LaunchPad and BoosterPack Pins Maps Boards Supporting the Galaxia Library  
 
Netiquette for Newbies  What Information to Provide When Asking for Help  I²C Check-List  Porting an Arduino library to Energia  

Some topics come aver and over again. Here are the most frequent questions.
Wouldn't be nice to have all of them in one single place?
Listed questions:
Netiquette for Newbies What Information to Provide When Asking for Help I²C Check-List  Porting an Arduino library to Energia Use Pins Number instead of Pins Names with Energia Add a New Board to Energia LaunchPad and BoosterPack Pins Maps Boards Supporting the Galaxia Library  
 
Netiquette for Newbies  What Information to Provide When Asking for Help  I²C Check-List  Porting an Arduino library to Energia  

Some topics come aver and over again. Here are the most frequent questions.
Wouldn't be nice to have all of them in one single place?
Listed questions:
Netiquette for Newbies What Information to Provide When Asking for Help I²C Check-List  Porting an Arduino library to Energia Use Pins Number instead of Pins Names with Energia Add a New Board to Energia LaunchPad and BoosterPack Pins Maps Boards Supporting the Galaxia Library  
 
Netiquette for Newbies  What Information to Provide When Asking for Help  I²C Check-List  Porting an Arduino library to Energia  

The iMeter BoosterPack features the INA226, an iteration of the INA219 I've been using in various projects like the I²C Voltage-Current-Power INA219 Sensor and the Volt-Amp-Watt-Meter for Grove.

Compared to the INA219, the INA226 operates on the same I²C bus but can now perform the measures on the high- or low-side, when the INA219 could only measure on the high-side.
 

The library for Energia was then easy to develop thanks to the prior experience with the INA219. 

I tested the iMeter BoosterPack on a MSP430FR4133 LaunchPad and a MSP430FR6989 LaunchPad with the built-in segmented LCD, leveraging the alpha-numeric LCD to display the units and the buttons to select the different measures (V, A, W) and toggle between units (V, mV). 

 
References
INA219 Review INA226 BoosterPack full review Library for Energia

The iMeter BoosterPack features the INA226, an iteration of the INA219 I've been using in various projects like the I²C Voltage-Current-Power INA219 Sensor and the Volt-Amp-Watt-Meter for Grove.

Compared to the INA219, the INA226 operates on the same I²C bus but can now perform the measures on the high- or low-side, when the INA219 could only measure on the high-side.
 

The library for Energia was then easy to develop thanks to the prior experience with the INA219. 

I tested the iMeter BoosterPack on a MSP430FR4133 LaunchPad and a MSP430FR6989 LaunchPad with the built-in segmented LCD, leveraging the alpha-numeric LCD to display the units and the buttons to select the different measures (V, A, W) and toggle between units (V, mV). 

 
References
INA219 Review INA226 BoosterPack full review Library for Energia

The iMeter BoosterPack features the INA226, an iteration of the INA219 I've been using in various projects like the I²C Voltage-Current-Power INA219 Sensor and the Volt-Amp-Watt-Meter for Grove.

Compared to the INA219, the INA226 operates on the same I²C bus but can now perform the measures on the high- or low-side, when the INA219 could only measure on the high-side.
 

The library for Energia was then easy to develop thanks to the prior experience with the INA219. 

I tested the iMeter BoosterPack on a MSP430FR4133 LaunchPad and a MSP430FR6989 LaunchPad with the built-in segmented LCD, leveraging the alpha-numeric LCD to display the units and the buttons to select the different measures (V, A, W) and toggle between units (V, mV). 

 
References
INA219 Review INA226 BoosterPack full review Library for Energia

Shouldn’t there be a special badge on 43oh for earning 430 reputation points?
Well, congrats to my dear friend @Fmilburn for having crossed that line of 43oh awesomeness 

For production, I'm using Energia for rapid prototyping. If some parts need to go faster, then I use the DriverLib on ROM, and eventually the registers for further optimisation (I get useful help from this very forum on how to use HWREG). However, the more optimised the code is for speed , the less portable the code is across MCUs. 
As a matter of facts, most prototypes are "good enough" even for final product. The killer feature of C++ (and thus Energia) is OOP, making maintenance really easy. That's how I've built the LCD_screen Library Suite for the screens supported by the LaunchPads. Adding a new screen only requires defining a couple of functions.
Now, there is no secret: different programming methods just move the difficulty from one part to another. It is always interesting to compare different solutions, so students can weight the pros and the cons of each of them (e.g. One Example, Three Environments), and discover that previous analysis is key, whatever the solution.
I did the same with RTOS: I completed the Real-Time Bluetooth Networks: Shape the World — MOOC edX UTAustinX UT.RTBN.12.01x MOOC and built the kernel of an RTOS from scratch. Now, I'm very happy to use TI-RTOS or Energia MT directly, with the ease of RTOS elements packaged as objects with the Galaxia library for Energia MT.

For production, I'm using Energia for rapid prototyping. If some parts need to go faster, then I use the DriverLib on ROM, and eventually the registers for further optimisation (I get useful help from this very forum on how to use HWREG). However, the more optimised the code is for speed , the less portable the code is across MCUs. 
As a matter of facts, most prototypes are "good enough" even for final product. The killer feature of C++ (and thus Energia) is OOP, making maintenance really easy. That's how I've built the LCD_screen Library Suite for the screens supported by the LaunchPads. Adding a new screen only requires defining a couple of functions.
Now, there is no secret: different programming methods just move the difficulty from one part to another. It is always interesting to compare different solutions, so students can weight the pros and the cons of each of them (e.g. One Example, Three Environments), and discover that previous analysis is key, whatever the solution.
I did the same with RTOS: I completed the Real-Time Bluetooth Networks: Shape the World — MOOC edX UTAustinX UT.RTBN.12.01x MOOC and built the kernel of an RTOS from scratch. Now, I'm very happy to use TI-RTOS or Energia MT directly, with the ease of RTOS elements packaged as objects with the Galaxia library for Energia MT.

I completed the MOOC Embedded Systems: Shape The World — MOOC edX UTAustinX UT.6.02x and learnt how to define an analog input "the real way".
Real way // Declare analog input PE2/A1 SYSCTL_RCGC2_R |= 0x00000010; GPIO_PORTE_DIR_R &= ~0b00000100; GPIO_PORTE_AFSEL_R |= 0b00000100; GPIO_PORTE_DEN_R &= ~ 0b00000100; GPIO_PORTE_AMSEL_R |= 0b00000100; SYSCTL_RCGC0_R |= 0x00010000; SYSCTL_RCGC0_R &= ~0x00000300; ADC0_SSPRI_R = 0x0123; ADC0_ACTSS_R &= ~0x0008; ADC0_EMUX_R &= ~0xf000; ADC0_SSMUX3_R &= ~0x000f; ADC0_SSMUX3_R += 1; ADC0_SSCTL3_R = 0x0006; ADC0_ACTSS_R |= 0x0008; // Read value form PE2/A1 ADC0_PSSI_R = 0x0008; while ((ADC0_RIS_R & 0x08) == 0); result = ADC0_SSFIFO3_R & 0xfff; ADC0_ISC_R = 0x0008; Energia way pinMode(A1, INPUT); uint16_t value = analogRead(A1); It is interesting the first time, but laziness made me use the Energia way the times after. Remember laziness is how developers survive :).

I completed the MOOC Embedded Systems: Shape The World — MOOC edX UTAustinX UT.6.02x and learnt how to define an analog input "the real way".
Real way // Declare analog input PE2/A1 SYSCTL_RCGC2_R |= 0x00000010; GPIO_PORTE_DIR_R &= ~0b00000100; GPIO_PORTE_AFSEL_R |= 0b00000100; GPIO_PORTE_DEN_R &= ~ 0b00000100; GPIO_PORTE_AMSEL_R |= 0b00000100; SYSCTL_RCGC0_R |= 0x00010000; SYSCTL_RCGC0_R &= ~0x00000300; ADC0_SSPRI_R = 0x0123; ADC0_ACTSS_R &= ~0x0008; ADC0_EMUX_R &= ~0xf000; ADC0_SSMUX3_R &= ~0x000f; ADC0_SSMUX3_R += 1; ADC0_SSCTL3_R = 0x0006; ADC0_ACTSS_R |= 0x0008; // Read value form PE2/A1 ADC0_PSSI_R = 0x0008; while ((ADC0_RIS_R & 0x08) == 0); result = ADC0_SSFIFO3_R & 0xfff; ADC0_ISC_R = 0x0008; Energia way pinMode(A1, INPUT); uint16_t value = analogRead(A1); It is interesting the first time, but laziness made me use the Energia way the times after. Remember laziness is how developers survive :).

Both CCS Cloud and CCS standard support Energia.

Hello Everyone,
I would like to wish all of our members and visitors a wonderful new year. Thank you for contributing and answering posts. 
Keep posting and wish you all the best.

@agaelema Have a look at my project of Low Power Weather Station.
The LCD library designed for the MSP430FR4133 and MPS430FR6989 shouldn't be difficult to port to the MSP432P111.