• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 4052 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Starterware/AWR1642: Starting up the device without sending config from the visualizer

Amol Vagad
Intellectual 445 points
Part Number: AWR1642
Other Parts Discussed in Thread: MMWAVE-SDK, IWR1642

Tool/software: Starterware

Hi all,

We are working wit the AWR1642 and reading the data from the UART port. However, one thing which we observed that the radar does not start unless we send config from the visualizer. When we do not send the config we cannot see any data received by the UART port. Is there any way we could enable the radar without using the visualizer using our C++ program that reads from the UART port ?? 

Thanks.  

  • 0
    TI__Mastermind 22155 points

    Hello Amol,

    In the current MMWAVE-SDK offering we only have the demo applications that need the configuration to be sent to the device either from the command line(Capture Demo) or through the visualizer (mmw Demo) .

    Using the existing demo application as reference you can develop your own application with the configurations you need .

    Thanks,

    Raghu

    ----------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.

    ----------------------------------------------------------------------------------------------------------

  • 0
    Prodigy 140 points

    Hi Amol.

    You can save needed cfg files from demo visualizer and send them using your code when you start the sensor.

    Here's python code for it (with pyserial library):

    import serial

CLIport = serial.Serial('/dev/ttyACM0', 115200)

config = [line.rstrip('\r\n') for line in open(path+'/profile1.cfg')]
for i in config:
    CLIport.write(i+'\n')
    time.sleep(0.01)

    Notice that /dev/ttyACM0 is the path to iwr config port in Linux. Also notice the time.sleep() command adter writing to port, this is necessary to prevent overlapping of commands sent.
    I think you can now easily implement that in C/C++.
    It is also worth mentioning that sending only sensorStart command won't work - you have to set all configuration parameters prior to starting the sensor after poweroff.

  • 0 in reply to Dmitry Frolov
    Intellectual 445 points
    Hi Dmitry,

    The solution you suggested works perfectly . But even for that to work we need to set up the configuration using visualizer at least once per boot sequence. Is there a way to do it without using it at all?

    Thanks
  • 0 in reply to Amol Vagad
    Prodigy 140 points

    Hi Amol,

    Why do you need to use visualizer once per boot sequence. Please make it clear, I don`t fully understand. Trying different configrations?
    Once you have saved .cfg file on your computer, you can then just send it with your code to IWR without using Demo Vizualizer. You can save several files with desirable configurations.
    You can change sensor parameters directly using command line interface, then I suggest you see mmWave SDK user's guide, where all command are documented. However, as I discovered during my work with IWR1642 the demo code in it will not support all possible chirp configurations

    If you want to play with different configs and receive UART data with your code, I suggest the following trick:
    You open data port firstly with your code. Then it wiil be occupied and when you start Demo Vizualiser it will only connect to CLI port. You wiil be able to change configs via Vizualiser, and receive data with your code.