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.

AWR6843ISK: Vital Signs demo hang-up

Part Number: AWR6843ISK
Other Parts Discussed in Thread: MMWAVEICBOOST, IWR6843AOP, IWR6843ISK

Hi E2E,

Our customer encounters hang up in using the vital signs demo, even though the flash has been loaded and completed successfully. What causes the problem?

The customer has changed the cable and also reconnect the board but it doesn't work. 

QT version =  5.9.1
QMetaObject::connectSlotsByName: No matching signal for on_buttonBox_accepted()
Serial Port Found
Data Port Number is "COM5"
User Port Number is "COM5"
Data port succesfully Open
User port did not Open
QMetaObject::connectSlotsByName: No matching signal for on_buttonBox_accepted()
Configuration File Name Read from the GUI is %s/n "xwr1642_profile_VitalSigns_20fps_Back.cfg"
QMetaObject::connectSlotsByName: No matching signal for on_buttonBox_accepted()
""
Configuration File Path is %s/n "C:/ti/mmwave_industrial_toolbox_4_7_0/labs/vital_signs/68xx_vital_signs/gui/profiles/xwr1642_profile_VitalSigns_20fps_Front.cfg"
"sensorStop"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"flushCfg"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"dfeDataOutputMode 1"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"channelCfg 15 3 0"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"adcCfg 2 1"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"adcbufCfg -1 0 0 1 0"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"profileCfg 0 60.25 7 6 57 0 0 65 1 200 4000 0 0 40"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"chirpCfg 0 0 0 0 0 0 0 1"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"frameCfg 0 0 2 0 50 1 0"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"lowPower 0 1"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"guiMonitor 0 0 0 0 1"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"calibDcRangeSig -1 0 0 0 0"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"vitalSignsCfg 0.3 0.9 256 512 4 0.1 0.05 100000 300000"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"motionDetection 1 20 2.0 0"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"sensorStart"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"sensorStop"
"flushCfg"
"dfeDataOutputMode 1"
"channelCfg 15 3 0"
"adcCfg 2 1"
"adcbufCfg -1 0 0 1 0"
"profileCfg 0 60.25 7 6 57 0 0 65 1 200 4000 0 0 40"
"chirpCfg 0 0 0 0 0 0 0 1"
"frameCfg 0 0 2 0 50 1 0"
"lowPower 0 1"
"guiMonitor 0 0 0 0 1"
"calibDcRangeSig -1 0 0 0 0"
"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 :  3250
Maximum Range in Meters is : 9.23077
Range-FFT size is : 256
Range-Bin size is : 0.0360577
Range-Bin Start Index is : 8
Range-Bin End Index is : 24
Total Payload size from the UART is : 252
Padding Factor is : 8
Total Payload size from the UART is : 256
QMetaObject::connectSlotsByName: No matching signal for on_buttonBox_accepted()
Configuration File Name Read from the GUI is %s/n "xwr1642_profile_VitalSigns_20fps_Back.cfg"
QMetaObject::connectSlotsByName: No matching signal for on_buttonBox_accepted()
""
Configuration File Path is %s/n "C:/ti/mmwave_industrial_toolbox_4_7_0/labs/vital_signs/68xx_vital_signs/gui/profiles/xwr1642_profile_VitalSigns_20fps_Front.cfg"
"sensorStop"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"flushCfg"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"dfeDataOutputMode 1"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"channelCfg 15 3 0"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"adcCfg 2 1"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"adcbufCfg -1 0 0 1 0"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"profileCfg 0 60.25 7 6 57 0 0 65 1 200 4000 0 0 40"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"chirpCfg 0 0 0 0 0 0 0 1"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"frameCfg 0 0 2 0 50 1 0"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"lowPower 0 1"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"guiMonitor 0 0 0 0 1"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"calibDcRangeSig -1 0 0 0 0"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"vitalSignsCfg 0.3 0.9 256 512 4 0.1 0.05 100000 300000"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"motionDetection 1 20 2.0 0"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"sensorStart"
QIODevice::write (QSerialPort): device not open
QIODevice::write (QSerialPort): device not open
"sensorStop"
"flushCfg"
"dfeDataOutputMode 1"
"channelCfg 15 3 0"
"adcCfg 2 1"
"adcbufCfg -1 0 0 1 0"
"profileCfg 0 60.25 7 6 57 0 0 65 1 200 4000 0 0 40"
"chirpCfg 0 0 0 0 0 0 0 1"
"frameCfg 0 0 2 0 50 1 0"
"lowPower 0 1"
"guiMonitor 0 0 0 0 1"
"calibDcRangeSig -1 0 0 0 0"
"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 :  3250
Maximum Range in Meters is : 9.23077
Range-FFT size is : 256
Range-Bin size is : 0.0360577
Range-Bin Start Index is : 8
Range-Bin End Index is : 24
Total Payload size from the UART is : 252
Padding Factor is : 8
Total Payload size from the UART is : 256

Your help is appreciated.

Regards,
Carlo

  • Hello

    Can you please make sure  you are able to the run the out of box demo for this device /board.

    That will ensure your setup  is working and then issues specific to this demo can be handled.

    Thank you

    Vaibhav

  • Hello Vaibhav,

    The customer use at the same time the occupancy and vital signs detection and it work well. They encounter this problem in this demo only.

    Regards,
    Carlo

  • Hello Mr. thanks for your support and we are also facing the same issue. I am attaching the screenshot of the issue for you reference.

    We are able to the run the out of box demo for this device/board for your information.

    Lab:- 68xx_vital_signs.

    Hardware used:- IWR6843AOP EVM paired with MMWAVEICBOOST board.

    The above image is the screenshot of the issue which we have facing for the past 5 days. kindly do the needful and help us with the issue.

    Mr. can you kindly update the status on the issue whether the issue still persists or have you fixed it. 

    Thanks and Regards

    K. Dinesh Krishna (6566937)

  • Hi Carlo

    It seems user has selected COM5 for both UART and DATA ports. Please make sure user has selected each port appropriately.

    Regards,

    AG

  • Hi AG,

    I seem to be facing the same problem where the the demo is automatically choosing both the com ports as the same port and I am unable to manually configure this in the GUI as the com ports are already opened in the demo (automatically upon GUI startup). Would it be possible for you to re - iterate the fix for this?

    I am using an IWR6843ISK ES2.0 for this and followed the steps mentioned in the user guide.

    Thanks & Regards,

    Kaushik Gowda

  • Hi Kaushik

    You should be using MMWAVEICBOOST for this.

    For more support please open up a new thread.

    Regards,

    AG