This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSP432P401R: The sum of many parts, dissecting the Vibration Condition Monitoring (TIDA-01575)

Part Number: MSP432P401R

The sum of many parts, dissecting the Vibration Condition Monitoring (TIDA-01575)

Vibration Condition Monitoring (VCM) is a very specific solution to a very specific challenge in motor diagnostics.  And while it might be easy to pass over or disregard such a solution based upon the title, the different software components of this design – the parts – can be reused for a wide range of applications.  Here is a list of the different parts found in TIDA-01575.

(1)    SimpleLink SDK, Pluggin Integration

One of the more powerful features of the SimpleLink SDK is the ability to ‘pluggin’ different software components to support wired communication channels such as Ethernet or wireless communications such as BLE, WIFI, ZigBee, or TI 15.4.  While the integration is in the context of VCM, the pluggin is ‘agnostic’ to the application.

(2)    Power Management: power constraints for entering/exiting deepsleep (LPM3)

The ability to set and release constraints is how the application can manage low power modes in the context of TIDrivers.  The example in this design not only shows the use and application of the associated APIs but creates a specific callback associated with the entering and exiting of deep sleep.

(3)    TI Drivers, RTOS: How to create a Hwi Object

This application uses the watch dog peripheral to periodically wake the device from deepsleep to perform the adc measurements across the three axis of the accelerometer.  There is no TIDriver for the watch dog peripheral so a hardware interrupt (HWI) object  needs to be created.  This example can be reused in different applications and be expanded to other peripherals, even peripherals to which drivers already exist.

(4)    FFT analysis and type conversion with the CMSIS DSP Library

This is not the first example which utilizes the CMSIS DSP library, which is now part of the SimpleLink SDK; however, it is an example in the context of an RTOS.  Specific to this application are the conversion of the fixed point ADC conversion to a floating point representation as well as FFT analysis of the ADC conversion result. 

(5)    Data Acquisition, Configuration for multiple samples across multiple channels

A commonly asked question is how to use the ADC to sample several different channels.  In this design the ADCBuf TIDriver is used to measure three channels (3-axis accelerometer) 1024 times and store the results in the arrays sampleBufferX,Y, and Z.

Although you may not be designing a VCM application, hopefully you will find a number of these ‘parts’ helpful in your design. 

Cheers,

Chris

**Attention** This is a public forum