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.

IWRL1432BOOST: IWRL1432 boost

Part Number: IWRL1432BOOST
Other Parts Discussed in Thread: IWRL1432

Tool/software:

we are making use of iwrl1432 and we are interested to read out the level sensing data via external controller is there any option that data can be fetched from UART,SPI any other protocol

we prefer UART if any other thing supports let us know 

If it supports UART we can directly guide the level sensing data to any serial monitor if it works

  • Hello, 

    We provide an example level sensing application that already outputs the level sensing data via UART. Please refer to the user guide here. Typically when running the demo the visualizer is used for connecting to the device and viewing the data but you can also configure the device and stream the output data directly from a serial monitor software such as tera term or putty, etc... You just need to ensure that you connect to the correct com ports and appropriate baud rate. 

    Best regards,

    Josh

  • Hello Josh Dye,

        i checked the output in Visualizer, what are the configurations we  have to do to get the data via UART to check in serial monitor like TERA TERM/PUTTY.
    can you tell the Baud Rate and other thing will get a final output data or the raw data so that we should convert it

    1. Our requirement  is for only one object we don't need multiple object 

    2. Can we directly tap the data at IWRL1432BGAMFQ1 pin L12 and j11 pins 

    3. If we tap can give us any sample data how it looks like

    Thanks

  • Hello, 

    The baud rate for the 1432 level sensing demo is 115200 (this can be found in the level_sensing.syscfg file). The processed radar data (level sensing info in this case) is output as a binary stream of UART data so viewing in the serial terminal window it will not be readable. The data will need to be decoded and parsed to be used. The level sensing demo user guide documents how the output data for that demo is structured. 

    1. Our requirement  is for only one object we don't need multiple object 

    Can you please elaborate what you mean here? Are you referring to the multi-peak detection feature of the level sensing demo. 

    2. Can we directly tap the data at IWRL1432BGAMFQ1 pin L12 and j11 pins 

    Currently the data is being output via RS232_TX (E10). Actually for all xWRLx432 demos the sensor configuration and data output happens on the same UART port (UARTB/RS232_). If you wanted to change the data to output via UARTA (L12) then you must make changes in the demo code (syscfg file) and add the UART instance. You will also need to modify the mmwDemo_TransmitProcessedOutputTask (level_sensing.c) to output the data over UARTA instead of UARTB.

    Best Regards,

    Josh

  • 1. One object Means we need only level sensing data ie height of the only one object it detects we don't need multiple objects to be detected 

    2. OK understood so the data in uart can be easily readable on UARTB ok now I need some reference link or document so that how can we parse the UART data to a meaningful one

    3. If we open uart/data port only these prints are available no other logs is there how would i get other logs like this even though i have added debug logs refer attached image 

    logs
    xWRL1432 MMW Demo 05.05.00.00
    ******************************************
    mmwDemo:/

    3. Is there any settings to be done on the board to get logs on uart ?

    Thanks 

  • Hi, 

    One object Means we need only level sensing data ie height of the only one object it detects we don't need multiple objects to be detected 

    Understood. The number of zoom measurements can be configured in the cfg file sent to the device. 

    zoomCfg 16384 1 3

    2. OK understood so the data in uart can be easily readable on UARTB ok now I need some reference link or document so that how can we parse the UART data to a meaningful one

    Data is output in TLV format (Type Length Value). Described here: https://dev.ti.com/tirex/local?id=Understanding_UART_Data_Output_Format&packageId=radar_toolbox 

    For an example of how the data is decoded and parsed on the PC using python you can refer to the code of the industrial visualizer in the radar toolbox. The relevant files containing the parsing code are gui_parser.py, parseFrame.py and parseTLV.py. 

    3. If we open uart/data port only these prints are available no other logs is there how would i get other logs like this even though i have added debug logs refer attached image 

    I believe the logs you are referring to are the CLI console messages. You can use the CLI_write() function for this. DebugP_log will only show messages in the debug console in CCS when running the demo in debug mode. 

    Best regards,

    Josh

  • Hi Thanks for reply 
    1. For getting logs in UART my point is we are getting the logs after every start 
    xWRL1432 MMW Demo 05.05.00.00
    ******************************************
    mmwDemo

    2. Using CLI write we are getting but if we use the same func in main .c or somewhere in the code  we are not getting those how would i get logs in srial port by using CLI write or any other func so that we can see some kind of logs in the serial port so that we can have some understanding of code flow

  • Hello, 

    Using CLI write we are getting but if we use the same func in main .c or somewhere in the code  we are not getting those

    You may need to ensure the required header file is included at the top of the file where you are trying to use CLI_write. For example "#include "mmw_cli.h"". 

    Regards,

    Josh