• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 917 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

$core_v2_language.Truncate($relatedThread.Subject, 120, "...")

AWR1642BOOST: Human vital signs lab not gathering data

Michael van der Veldt
Prodigy 170 points
Part Number: AWR1642BOOST
Other Parts Discussed in Thread: AWR1642, IWR1642, , IWR1642BOOST

After flashing the binary in mmwave_automotive_toolbox_2_4_7\labs\lab0001-driver-vital-signs\vitalSigns_target\pre-built-Binaries\vitalSigns_16xx.bin
and running the executable in mmwave_automotive_toolbox_2_4_7\labs\lab0001-driver-vital-signs\vitalSigns_host\gui_exe\VitalSignsRadar_Demo.exe
I am getting no data outputting on the GUI

Here's the code showing on the command window

QT version = 5.9.1
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 2970x1998+14+58 on QWidgetWindow/'MainWindowWindow'. Resulting geometry: 2970x1959+14+58 (frame: 13, 58, 13, 13, custom margin: 0, 0, 0, 0, minimum size: 1347x741, maximum size: 16777215x16777215).
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()
"COM9"
Configuration File Path is %s/n "C:/Users/School/Downloads/mmwave_automotive_toolbox_2_4_7/labs/lab0001-driver-vital-signs/vitalSigns_host/profiles/xwr1642_profile_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 200 4000 0 0 48"
"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"
"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 200 4000 0 0 48"
"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 : 3500
Maximum Range in Meters is : 8.57143
Range-FFT size is : 256
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 : 260
Padding Factor is : 9
Total Payload size from the UART is : 288
QMetaObject::connectSlotsByName: No matching signal for on_buttonBox_accepted()

  • 0
    TI__Mastermind 24955 points
    Michael,

    Please ensure that you are using an ES 2.0 AWR1642 device with this lab. ES 1.0 AWR1642 devices are not compatible with this release and this is the message that is seen when this is the case.

    Please search on this forum to understand how to determine which version of silicon your AWR1642 device is. This type of question has addressed several times in the past.

    Regards,
    Kyle
  • 0 in reply to Kyle Cousino
    Prodigy 170 points

    I'm fairly certain we have the ES 2.0 AWR1642 device. I was unable to find a definite way to check on the forums. Referencing this thread: \e2e.ti.com/.../699519

    lettering on my chip reads:

    IWR1642

    QG

    822E3Y9

    502AC       ABL     G1

    The 502 AC leads me to believe that I have the ES2.0 but I lack an "A" after "AWR1642A".  

  • 0 in reply to Michael van der Veldt
    TI__Mastermind 24955 points
    Michael,

    You in fact do not have an AWR1642 device, you have an IWR1642 device. There is a known issue with the vital signs lab where it works successfully on AWR1642BOOST but not on IWR1642BOOST. The issue will be addressed in a future release of the automotive toolbox. It does state in the release notes that the current vital signs lab is only for AWR1642.

    Regards,
    Kyle
  • 0 in reply to Kyle Cousino
    Prodigy 170 points
    AWR1642ABIGABLQ1
    AWR1642ABIGABLRQ1

    If I were to order one of these, which would be better for the lab?
  • 0 in reply to Michael van der Veldt
    TI__Mastermind 24955 points
    Michael,

    You can use the AWR1642BOOST which you can find here: www.ti.com/.../AWR1642BOOST

    The only different between the two parts variants that you listed above is that one comes on a tray while the other comes on a reel.

    You would need to check to see if the ball outs for the IWR1642 and AWR1642 are compatible if you are trying to desolder the IWR1642 chip and replace it with the AWR1642. You can compare the design files for both the AWR1642BOOST and IWR1642BOOST, which are both available to download from ti.com.

    Regards,
    Kyle