Other Parts Discussed in Thread: IWR6843
<Edited out as per user request>
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.
HI, there:
If you follow the SDK OOB demo structure, you can issue a sensorStop, reprogramming the txPhaseShifter in the profileCfg and issue sensor restart after that (sensorStart 0), will that be acceptable?
Best,
Zigang
Zigang,
It is too slow to start/stop sensor several times during interframe time. Any other way to achieve change Tx phase in the run time?
Regards
Andre
Hi, Andre:
I will need to consult with the design team and get back to you later.
Best,
Zigang
Zigang,
Any update?
1. If stop/start sensor is mandatory, how long will BBS take from stop to start sensor?
2. Any config parameters need to be reinitialized in between stop and start sensor?
Does designer have any recommendation to implement bean steering function?
Regards
Andre
Hi, Andre:
Sorry for the late reply. Most of the team members, including me, were gone for the vacation at the end of last year. I have not received any reply from the design team. I have just sent a reminder to the team and will update you as soon as I get some answers.
Best,
Zigang
HI, there:
I get some good news for you. For iwr6843 device, we can make TX phase shifter change without stop and restart the sensor. The user need to use API
rlRfSetPhaseShiftConfig to program the per chirp TX phase shifter. There is some Doyxgen documentation at:
file:///C:/ti/mmwave_sdk_03_05_00_04/packages/ti/control/mmwavelink/docs/doxygen/html/group___sensor.html#gaf9450d508e0fa2857f8f9cb6b5004ecc
best,
Zigang
Hi Zigang,
Looks good to me.
Is there any example code and data flow chart about this API?
Cause the description about the argument is too rough to understand how to use this API.
For example.
If I need to steering three times of Tx beam(-20°,0°,20°) in one frame .
How should I setting the argument about "rlRfSetPhaseShiftConfig".
BR
Thanks
Frank
Hi, there:
If you click on the data structure "
rlRfPhaseShiftCfg_t |
, it will lead you to the details located at:
file:///C:/ti/mmwave_sdk_03_05_00_04/packages/ti/control/mmwavelink/docs/doxygen/html/structrl_rf_phase_shift_cfg__t.html
I was told that there is an example code at:
mmwave_automotive_toolbox_#_#_#\labs\lab0011_mrr_beamsteering\src
Please search in following for “rlRfSetPhaseShiftConfig” and
Cfg_TxPhaseShiftInitParams() is used to init the structure in common\cfg.c
Best,
Zigang
Hi Zigang,
We had implement the API "rlRfSetPhaseShiftConfig".
It seems works about modifying the tx-phase dynamically but still has some problem to be solved.
When we use this API to modify the tx-phase dynamically, it still spends the period of one frame time what we define in system every time we call this API.
It doesn't match our data flow chart.
What we want is collecting the raw data by different tx-phase in "one frame" show as below.
Is there any suggestion about that?
Could we modify the period of one frame time dynamically without re-start sensor too?
BR
Thanks
Frank
Hi, Frank:
Let me first align with your design goal: Do you mean you want to apply different phase per chirp? instead of per frame?
If so, you can use per-chip phase shifter to program different phase to different chirp. But if you need to program a new set of per-chip phase shifter, it probably will still wait to next frame to apply the new phase shifter.
Is that sound a good plan to you?
Best,
Zigang
Hi Zigang,
Sorry for late reply.
What we need is call the phase shifter API "rlRfSetPhaseShiftConfig" three times in one frame.(Show as below)
If this API must to wait for the next frame for a new phase setting.
How should we control the period of frame time dynamically?
Maybe the first few frames we can set short frame time just for data collection and the last frame set the long frame time for algorithm.
BR
Thanks
HI, BR:
you can define 3 subframes, and each with different frame period, and each with different TX phase shifter. But the current SDK out of box demo does not allocate different radar cube memory for each subframe, so you will have to process the radar cube after each subframe, and maybe create some global variable to save the end results and then jointly process them together after the last subframe.
Let me know if it makes sense to you.
Best,
Zigang
Hi Zigang,
I tried what you suggest to build up the multi sub-frame to satisfy the dynamic frame time.
It worked about the frame time problem but still has some problem on Tx phase shift.
I set three initial tx phase to each sub-frame by "Cfg_ProfileCfgInitParams" (NUM_PROFILES = 3)
but in the last, it only provide one tx phase what we first set in "Cfg_ProfileCfgInitParams" (PROFILE_DBF_FIRSTBEAM_TXPHASESHIFTER_VAL"), we observed it by RF pattern measure.
Why can not to set initial Tx phase to each sub-frame by setting "Cfg_ProfileCfgInitParams"?
Is it must to use this API "rlRfSetPhaseShiftConfig " what you suggest before to change tx phase dynamically for each sub-frame?
BR
Thanks
Frank
Hi Zigang,
I tried what you suggest to build up the multi sub-frame to satisfy the dynamic frame time.
It worked about the frame time problem but still has some problem on Tx phase shift.
I set three initial tx phase to each sub-frame by "Cfg_ProfileCfgInitParams" (NUM_PROFILES = 3)
but in the last, it only provide one tx phase what we first set in "Cfg_ProfileCfgInitParams" (PROFILE_DBF_FIRSTBEAM_TXPHASESHIFTER_VAL"), we observed it by RF pattern measure.
Why can not to set initial Tx phase to each sub-frame by setting "Cfg_ProfileCfgInitParams"?
Is it must to use this API "rlRfSetPhaseShiftConfig " what you suggest before to change tx phase dynamically for each sub-frame?
BR
Thanks
Frank
HI, Frank:
It sounds like although three profile are defined here, but only one profile configuration is used. Is it from the out-of-box demo code?
Best,
Zigang