• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 424 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.

AWR1642BOOST: Driver vital sign monitoring GUI

Swapan Jain
Prodigy 190 points
Part Number: AWR1642BOOST
Other Parts Discussed in Thread: AWR1642

After flashing the prebuilt binary into my awr 1642, I  powered off and removed the sop2 jumper to bring it into the functional mode.

Then I installed the XDS emulation package and tried to run the GUI as mentioned in the getting started document. The GUI starts , but every value there is static and is zero.The GUI is not updating.

The below are the logs on starting up the GUI. Need help in sorting this out.

QT version = 5.8.0
QMetaObject::connectSlotsByName: No matching signal for on_buttonBox_accepted()
Serial Port Found
Data Port Number is "COM8"
User Port Number is "COM9"
Data port succesfully Open
User port succesfully Open
QWindowsWindow::setGeometry: Unable to set geometry 1349x817+8+31 on QWidgetWindow/'MainWindowWindow'. Resulting geometry: 1349x749+8+31 (frame: 8, 31, 8, 8, custom margin: 0, 0, 0, 0, minimum size: 1347x706, maximum size: 16777215x16777215).
QWindowsWindow::setGeometry: Unable to set geometry 1373x817+8+31 on QWidgetWindow/'MainWindowWindow'. Resulting geometry: 1373x749+8+31 (frame: 8, 31, 8, 8, custom margin: 0, 0, 0, 0, minimum size: 1373x740, maximum size: 16777215x16777215).
QMetaObject::connectSlotsByName: No matching signal for on_buttonBox_accepted()
"COM9"
Configuration File Path is %s/n "E:/tiAutomotiveToolbox/mmwave_automotive_toolbox_3_1_0__win/mmwave_automotive_toolbox_3_1_0/labs/incabinsensing/driver_vital_signs/vitalSigns_host/gui/profiles/profile_2d_VitalSigns_20fps_Front.cfg"
"sensorStop"
"flushCfg"
"dfeDataOutputMode 1"
"channelCfg 15 3 0"
"adcCfg 2 1"
"adcbufCfg -1 0 0 1 0"
"profileCfg 0 77 7 6 57 0 0 70 1 100 2000 0 0 40"
"chirpCfg 0 0 0 0 0 0 0 1"
"frameCfg 0 0 2 0 50 1 0"
"lowPower 0 0"
"guiMonitor 0 0 0 0 1"
"vitalSignsCfg 0.3 0.9 256 512 4 0.1 0.05 100000 300000"
"motionDetection 1 20 2.0 0"
"sensorStart"
""
"sensorStop"
"flushCfg"
"dfeDataOutputMode 1"
"channelCfg 15 3 0"
"adcCfg 2 1"
"adcbufCfg -1 0 0 1 0"
"profileCfg 0 77 7 6 57 0 0 70 1 100 2000 0 0 40"
"chirpCfg 0 0 0 0 0 0 0 1"
"frameCfg 0 0 2 0 50 1 0"
"lowPower 0 0"
"guiMonitor 0 0 0 0 1"
"vitalSignsCfg 0.3 0.9 256 512 4 0.1 0.05 100000 300000"
0.3
0.9
4
"motionDetection 1 20 2.0 0"
"sensorStart"
""
Chirp Duration in us is : 50
Chirp Bandwidth in kHz is : 3500
Maximum Range in Meters is : 4.28571
Range-FFT size is : 128
Range-Bin size is : 0.0334821
Range-Bin Start Index is : 8
Range-Bin End Index is : 26
Total Payload size from the UART is : 220
Padding Factor is : 7
Total Payload size from the UART is : 224

Thanks

Swapan

  • 0
    TI__Guru 69960 points

    Hello Swapan,

    Could you confirm if you are able to run default mmw demo from mmwave SDK on the same board and from same PC?

    And default driver vital sign demo binary should work with AWR1642 without any error. Please follow the user guide and pre-requisite this demo requires.

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    Prodigy 190 points

    Hi,

    I am able to run the demo on a different machine which has the recommended sdk version on the same board. But I cannot run it on my machine.

    I will change the sdk version on my machine and get back to you.

    Thanks

    Swapan Jain