• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 527 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.

IWRL1432BOOST: mmWave Configuration Failure [Error code: -3110 Subsystem: 0] when Running Industrial_Visualizer.exe

JAEHOON KIM
Intellectual 445 points
Part Number: IWRL1432BOOST


Tool/software:

Dear [TI Support Team],

I am currently working with the TI mmWave sensor and modifying the configuration parameters to extend the maximum range and adjust the range resolution. However, I encountered an issue when running Industrial_Visualizer.exe with the modified configuration file.

Background

I started with the TI-provided configuration file high_accuracy_demo_fast_update_xwrl14xx.cfg, which has the following settings:

  • Maximum Range: 9.993 meters
  • Range Resolution: 0.049 meters

To extend the range and improve the resolution, I used the TI mmWave Sensing Estimator (v2.4.0) to generate a new configuration file. The modified settings are:

  • Maximum Range: 31.228 meters
  • Range Resolution: 0.038 meters

The main changes in the configuration file are:

  • chirpComnCfg: Changed from 8 0 0 512 0 45 0 to 8 0 0 2048 1 175 0
  • chirpTimingCfg: Changed from 6 23 0 75 77 to 6 23 0 24 76

All other parameters remained the same.

Issue

After applying the new configuration file, I attempted to run Industrial_Visualizer.exe, but the following error occurred: Error: mmWave Config failed [Error code: -3110 Subsystem: 0]

Questions

  1. What does Error Code -3110 (Subsystem: 0) indicate in this context?
  2. Could the changes in chirpComnCfg or chirpTimingCfg be causing the issue?
  3. Are there any additional constraints or dependencies when modifying these parameters?
  4. What steps should I take to debug or resolve this configuration error?

I would appreciate any guidance regarding this issue. Please let me know if further information is required.

Best regards,

Relevant Log Output

INFO [gui_core.py:274] Data COM Port found: COM24
INFO [gui_core.py:265] CLI COM Port found: COM23
INFO [gui_parser.py:300] Connected (one port) with baud rate 115200
b'channelCfg 1 1 0\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>chirpComnCfg 8 0 0 2048 0 175 0\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>chirpTimingCfg 6 23 0 24 76\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>frameCfg 1 0 200 1 100 0\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>guiMonitor 2 1 0 0 0 1 0 0 0 0 0\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>zoomCfg 16384 1 3\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>sigProcChainCfg 32 2 1 0 4 4 0 15 \n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>cfarCfg 2 8 4 3 0 12.0 0 0.5 0 1 1 1\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>aoaFovCfg -60 60 -40 40\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>rangeSelCfg 0.0 10.0\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>clutterRemoval 0\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>compRangeBiasAndRxChanPhase 0.0 1.0 0.0 -1.0 0.0 1.0 0.0 -1.0 0.0 1.0 0.0 -1.0 0.0\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>adcDataSource 0 C:/ti/mmwave_lp_sdk/examples/datapath/common/testBench/major_motion/adc_data_0001_CtestAdc6Ant.bin\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>adcLogging 0\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>lowPowerCfg 1\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>factoryCalibCfg 1 0 40 0 0x1ff000\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>baudRate 1250000\n'
b'\n'
b'\xf9'
b''
b'sensorStart 0 0 0 0\n'
b'\n'
b'Error: mmWave Config failed [Error code: -3110 Subsystem: 0]\n'
b'Done\r\n'
ERROR [gui_parser.py:189] ERROR: No data detected on COM Port, read timed out
ERROR [gui_parser.py:190] Be sure that the device is in the proper SOP mode after flashing with the correct binary, and that the cfg you are sending is valid
ERROR [gui_parser.py:189] ERROR: No data detected on COM Port, read timed out
ERROR [gui_parser.py:190] Be sure that the device is in the proper SOP mode after flashing with the correct binary, and that the cfg you are sending is valid

  • 0
    TI__Genius 12160 points

    Hi

    Thanks for your query. Please allow us a couple of days to respond

    Regards 

  • 0
    TI__Expert 4450 points

    Hello,

    The level sensing demo doesn't support 2048 ADC samples as our Hardware Accelerator can only perform a maximum of 1K point FFT.

    Hence, with the configuration you are using, the maximum samples you could provide is 1024 samples. You can use sensing estimator to arrive at a valid configuration with 1024 ADC samples and try running the demo again.

    Regards,

    Sharan

  • 0 in reply to Sharan S S
    Intellectual 445 points

    Hello,

    We encountered a -3110 error while modifying the settings below. After adjusting certain parameters, the system operated normally. However, we would like to understand the exact reason behind this issue.

    1. Configuration Changes and Error Occurrence

    We initially changed the 4th parameter (ADC sample count) of chirpComnCfg from 2048 to 1024, but the -3110 error persisted.
    Upon checking the firmware, we found that the -3110 error is related to frameCfg settings.

    • Before change: chirpComnCfg 8 0 0 2048 0 175 0
    • After change: chirpComnCfg 8 0 0 1024 0 175 0
    • Error occurred: -3110

    2. Additional Changes and Resolution

    We then modified the 3rd parameter (burstPeriodicity) of frameCfg from 800 to 200, and the -3110 error no longer occurred, allowing the system to function correctly.

    • Before change: frameCfg 1 0 800 1 100 0
    • After change: frameCfg 1 0 200 1 100 0
    • Error resolved

    3. Inquiry

    We would like to understand why adjusting burstPeriodicity was necessary when changing the ADC sample count in chirpComnCfg.
    Specifically, we would like to know why the error occurred when burstPeriodicity was set to 800 but disappeared when reduced to 200.

    Thank you for your support.

    Best regards

  • 0 in reply to JAEHOON KIM
    TI__Expert 4450 points

    Hi,

    Let me replicate the issue from my side. Is the config same as the one you had attached in the thread, apart from modification in frameCfg?

    Regards

  • 0 in reply to Sharan S S
    Intellectual 445 points

    There was an error in my question.

    The third parameter of frameCfg was not changed from 800 to 200.

    Instead, changing it from 200 to 800 resulted in normal operation.

    Before change: frameCfg 1 0 200 1 100 0
    After change: frameCfg 1 0 800 1 100 0

    Below is a properly functioning CFG file. However, if the third parameter of frameCfg is changed back from 800 to 200, an error occurs.

    % ***************************************************************
    % LevelSensing: Chirp configuration and Processing chain are
    % designed for high accuracy level sensing.
    % ***************************************************************
    channelCfg 1 1 0
    chirpComnCfg 8 0 0 1024 0 175 0
    chirpTimingCfg 6 23 0 24 76
    frameCfg 1 0 800 1 100 0
    guiMonitor 2 1 0 0 0 1 0 0 0 0 0
    zoomCfg 16384 1 3
    sigProcChainCfg 32 2 1 0 4 4 0 15
    cfarCfg 2 8 4 3 0 12.0 0 0.5 0 1 1 1
    aoaFovCfg -60 60 -40 40
    rangeSelCfg 0.0 10.0
    clutterRemoval 0
    compRangeBiasAndRxChanPhase 0.0 1.0 0.0 -1.0 0.0 1.0 0.0 -1.0 0.0 1.0 0.0 -1.0 0.0
    adcDataSource 0 C:/ti/mmwave_lp_sdk/examples/datapath/common/testBench/major_motion/adc_data_0001_CtestAdc6Ant.bin
    adcLogging 0
    lowPowerCfg 1
    factoryCalibCfg 1 0 40 0 0x1ff000
    baudRate 1250000
    sensorStart 0 0 0 0

  • +1 in reply to JAEHOON KIM
    TI__Expert 4450 points

    Hi,

    Burst periodicity should be greater than ((rampEndTime + chirpIdleTime) * numChirpsInBurst)) + 115us;

    115us is the minimum inter burst idle time. 

    Regards,

    Sharan

  • 0 in reply to Sharan S S
    Intellectual 445 points

    Understood.

    Thank you for your response.