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.

DCA1000EVM: DCA1000EVM stops streaming data after 2mts

Part Number: DCA1000EVM
Other Parts Discussed in Thread: IWR1642BOOST

Hi, 

I am trying to capture IQ data using DCA1000EVM and IWR1642BOOST. For this, I used OOB Demo and CLI tools provided. I used UDP functions provided in MATLAB to read data.  After around 1.5 -2mts  the transmission from DCA stops  (the first LED on the corner of the DCA  board stops blinking, it's always high.  No data received on the host.- checked in wireshark)

FrameRate is 1hz and Packet Delay is 100 us. "captureStopMode" is set as infinite"

When check in wireshark, looks like somehow the DCA is getting a STOP command packet. I am not sure how is this command getting send, I didnt invoke stop_record at this point. 

Is there an implicit condition this can happen?

Thanks 

Gayatri

  • Hello Gayatri,

    Are you using mmWaveStudio or StudioCLI for this project? If possible I would like to see the configuration you are using to start the sensor so that I can have more details.

    Best Regards,

    Pedrhom

  • Hi 

    I am using StudioCLI. 

    json file 

    {
    "DCA1000Config": {
    "dataLoggingMode": "raw",
    "dataTransferMode": "LVDSCapture",
    "dataCaptureMode": "ethernetStream",
    "lvdsMode": 2,
    "dataFormatMode": 3,
    "packetDelay_us": 100,
    "ethernetConfig": {
    "DCA1000IPAddress": "192.168.33.180",
    "DCA1000ConfigPort": 4096,
    "DCA1000DataPort": 4098
    },
    "ethernetConfigUpdate": {
    "systemIPAddress": "192.168.33.30",
    "DCA1000IPAddress": "192.168.33.180",
    "DCA1000MACAddress": "12.34.56.78.90.12",
    "DCA1000ConfigPort": 4096,
    "DCA1000DataPort": 4098
    },
    "captureConfig": {
    "fileBasePath": "C:\\mySavedData\\Parse22\\88",
    "filePrefix": "datacard_record",
    "maxRecFileSize_MB": 1024,
    "sequenceNumberEnable": 1,
    "captureStopMode": "infinite",
    "bytesToCapture": 1025,
    "durationToCapture_ms": 1000,
    "framesToCapture": 5
    },
    "dataFormatConfig": {
    "MSBToggle": 0,
    "reorderEnable": 1,
    "laneFmtMap": 0,
    "dataPortConfig": [
    {
    "portIdx": 0,
    "dataType": "complex"
    },
    {
    "portIdx": 1,
    "dataType": "complex"
    },
    {
    "portIdx": 2,
    "dataType": "complex"
    },
    {
    "portIdx": 3,
    "dataType": "complex"
    },
    {
    "portIdx": 4,
    "dataType": "complex"
    }
    ]
    }
    }
    }
    Config file : 
    sensorStop
    flushCfg
    dfeDataOutputMode 1
    channelCfg 15 5 0
    adcCfg 2 1
    adcbufCfg -1 0 1 1 1
    profileCfg 0 60 596 7 28.51 0 0 37.5 1 256 12499 0 0 158
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 4
    frameCfg 0 1 16 0 100 1 0
    lowPower 0 0
    guiMonitor -1 1 1 0 0 0 0
    cfarCfg -1 0 2 8 4 3 0 15 1
    cfarCfg -1 1 0 4 2 3 1 15 1
    multiObjBeamForming -1 1 0.5
    clutterRemoval -1 0
    calibDcRangeSig -1 0 -5 8 256
    extendedMaxVelocity -1 0
    bpmCfg -1 0 0 1
    lvdsStreamCfg -1 0 1 0
    compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
    measureRangeBiasAndRxChanPhase 0 1.5 0.2
    CQRxSatMonitor 0 3 4 63 0
    CQSigImgMonitor 0 127 4
    analogMonitor 0 0
    aoaFovCfg -1 -90 90 -90 90
    cfarFovCfg -1 0 0 39.99
    cfarFovCfg -1 1 -1 1.00
    calibData 0 0 0
    sensorStart
    Regards
    Gayatri
  • Hello Gayatri,

    Did you make that JSON file based off of an example one? Did you see the one provided as an example within the StudioCLI tool's profile folder? There are also JSON files within the mmWaveStudio's JSONSampleFiles folder. I see several potential issues and your JSON file seems very different than the example ones. You are saying it is only going on for like 2 minutes correct? Some of your parameters under "captureConfig" might be causing an issue

    Best Regards,

    Pedrhom Nafisi

  • I used the json file in mmwave SDK user guide.  From the datasheet available at "mmwave_studio_02_01_01_00/mmWaveStudio/ReferenceCode/DCA1000/Docs/TI_DCA1000EVM_CLI_Software_UserGuide.pdf" 

    I understand when captureStopMode is set to infinite, other params in captureConfig shouldn't take effect 

    I am able to stream data continuously if I just use "file writing ". If I try to open a udpport to same port in parallel, only then after 2mts stop command is send. I am trying to understand why is this stop command being sent. 

    Thanks

  • Hello,

    Please give me a few days to look into this as this does not seem to be normal, but we also do not normally use anything outside of mmWaveStudio and Studio CLI for standard raw data collection to file.

    Best Regards,

    Pedrhom

  • Hi, 

    Just wanted to check if you had chance to look into above issue. 

    Regards

    Gayatri

  • Hello Gayatri,

    I want to let you know that I have not forgotten about this thread, this just is not an issue we have seen before so it has admittedly been hard to pinpoint a specific reason this could be occurring. We are looking into your JSON file more closely and hopefully will have at the very least more questions for you soon.

    Best Regards,

    Pedrhom