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.

AWR1843BOOST: How to Restart the RF sensor of AWR1843boost

Part Number: AWR1843BOOST
Other Parts Discussed in Thread: AWR1843

Hello Team,

The post is regarding an issue that we are facing while trying to restart the sensor using SW api during runtime in AWR1843 Boost.

 

The activity involves following steps:

  1. We initialize and set the RF configuration settings in CLI task. which starts the Radar transmission and reception.
  2. We have integrated a counter for starting and stopping the radar sensor during runtime.
  3. At the end of the 5sec of counter, the sensor is stopped using the command: MmwDemo_CLISensorStop(). This command stops the RF transmission.
  4. Now at the end of 10sec of counter, since we have not reset the controller, we skip the reconfiguration of sensor and in order to restart the sensor, we provide the following command:MmwDemo_CLISensorStart(1,’0’).{Reference:mmwave sdk documentation,attached}.

 

However, the RF transmission never restarts without power reset of controller.

   

Tell me if my step is correct or Not. If not give me the correct step for this or please provide me example code if available.

Thank,

Miit Prajapati.

  • Hi Miit,

    Did you try to check the same experiment directly from the UART cli?

    Here's what you can try - 

    1. Flash the OOB demo from the SDK 

    2. Connect to the UART com port via Tera Term or similar tool

    3. Use a config file from the demo folder to configure the sensor for the first time

    4. Start the sensor

    5. Stop the sensor and wait for whatever time you want

    6. Start the sensor with "sensorStart 0" command 

    Let me know your observation on this experiment.

    Thanks,
    Anirban

  • Hello Anirban,

    Thanks for replying.

    As per you mentioned the steps via UART, I already tried and it's works.

    But i want to Stop and start the Sensor for the diagnostic purpose at runtime, if the diagnostic value will increase and crossing the limit threshold which i set  then only Sensor should stop and controller will continuously monitoring the diagnostic value. If the value will comes down to the limit threshold, then sensor will start using already provided configuration.

    In above paragraph i mentioned the requirements which i want, By using command : MmwDemo_CLISensorStop() the sensor is stoping. But i facing the issue while starting the sensor. 

    kindly give me the solution on that or if any example code is available for the same, Please provide me.

    Thanks 

    Miit prajapati.

  • Hi Miit,

    According to your statement, I understood that you are expecting monitoring reports even after the sensor is stop.

    This idea is not correct Miit, the monitoring chirps are sent in inter-frame duration and monitoring is done only during inter-frame idle time. So, you should not expect continuous monitoring even after the sensor is stopped. 

    As sensor is stopped, the device is not getting any monitoring data so it will not be able to verify if the value becomes lower than your threshold.

    Thanks,
    Anirban

  • Hi Anirban,

    We have the hardcoded the configurations and intend to stop the sensor during hazardous conditions such as over temperature(we are self designing this diagnostic detection feature), and would like to restart the sensor (without rebooting the controller), once the temperature falls below the safe limits.

  • Hi Miit,

    The basic idea behind this monitoring is as I said earlier if you stop the sensor the monitoring will also stops and you have to start the sensor manually from the terminal or by hard-coding. 

    What you can do is based on monitoring result you can send some sort of warning to the application level so the end user can understand and maybe stop the sensor.

    Once the sensor is stopped after some time, the end user should start the sensor manually.

    Thanks,
    Anirban 

  • Hi,

    I cannot understand the monitoring that you are talking of. What we are doing is as follows:

    1 We are sensing certain parameters like controller temperature and supply voltage over GPADC pins.

    2.And if one of these parameters exceeds a predefined threshold value, we are calling MmwDemo_CLISensorStop() function to stop the sensor to stop transmitting RF signals.

    3.Then we wait for the parameter(temperature or supply voltage )to go below the threshold.

    4.Once the SW identifies that that the input ADC value for temperature or voltage is within safe limits, we call :MmwDemo_CLISensorStart(1,"sensor start 0’).

    But now the sensor doesn't start transmitting RF signal,unless we do the power reset. 

    We want to understand if the MmwDemo_CLISensorStart(1,"sensor start 0’) is a correct hard coded sensor starting command?

  • Hi Miit,

    How are you confirming the sensor is not transmitting RF signals? Are you facing any specific type of error?

    Thanks,
    Anirban

  • Hello Anirban,

    I Logged the data which comes from EVM at runtime and as i mentioned in above threads at the end of the 5second of counter sensor should stop.

    When sensor was stop, no data was come out from EVM.

  • Hi Miit,

    Clarifying my question

    After the threshold was hit, the sensor is stopped and once the values are below threshold (you're expecting the sensor to be start again) how are you confirming that the device is not transmitting RF signals? Any specific type of issue you faced?

    You can always use our CCS tool to connect the device when it is stuck and load symbols to check where exactly is it stuck.

    Thanks,
    Anirban

  • Hello Anirban,

    1.We are using SPI for Data logging.

    2.We used CCS tool for debugging, But debugger is stop when data is not coming.

    It will very helpful for us. If we get the proper guidance session for this.

    Thanks,

    Miit 

  • Hello Miit,

    Apologies for a late reply.

    As you mentioned that you're measuring supply voltage and temperature over GPADC, after the first threshold hit have you tried re-configuring the GPADC module when trying to restart the sensor?

    Regards,
    Anirban