AWR2944: runtime calibration (onetime calibration)

Hi Joseph,

I will need to check on this query within the team. I will update you on this in my next response. 

Thanks,

Pradipta.

Hi,

Please find my comments below.

Q) I'm trying to enable runtime calibration using the option of onetime calibration. i noticed that when i'm calling it by 25 msec periodicity it works fine, but if make it higher periodicity it doesn't work (1 sec for example).

Comment) Can you let me know in which parameter you are setting this 25 ms or 1sec. Is the CALIB_MON_TIME_UNIT? If so, then 1 sec is not a valid value for this filed.

Q)  what is the use of CALIB_MON_TIME_UNIT in case i'm using onetime calibration configuration not the periodic calibration? as i understood it only used if i'm configuring periodic runtime calibration, but i noticed in the manual that it may be used in AWR_CAL_MON_TIMING_FAIL_REPORT_AE_SB for onetime runtime calibration also.

Comment) CALIB_MON_TIME _UNIT is used a s a time unit for both calibration and monitoring operations. Even though you may not use any of the two operations still you will need to fill a valid value in this filed as per the ICD document. 

Q) according to the manual, the default of CALIB_MON_TIME_UNIT is 100, does it mean 100 msec?

Comment) One LSB for this field is defined as "duration of one frame". If for example your frame duration is 20 ms then the default value will mean 100 * 20 ms.

Q) and how could i know that the calibration is not done due to lack of idle time?, is CALIBRATION_ERROR_FLAG in AWR_RUN_TIME_CALIB_SUMMARY_REPORT_AE_SB if failed then the reason may be lack of idle time? or it only be shown in AWR_CAL_MON_TIMING_FAIL_REPORT_AE_SB?

Comment) We should check the AWR_CAL_MON_TIMING_FAIL_REPORT_AE_SB to find out any issues related to timing failures.

Thanks,

Pradipta.

 Can you let me know in which parameter you are setting this 25 ms or 1sec. Is the CALIB_MON_TIME_UNIT? If so, then 1 sec is not a valid value for this filed.

-> i'm not setting CALIB_MON_TIME_UNIT, as i'm using runtime calibration by onetime calibration not periodic calibration, but calling it periodically.

Hi Joseph,

Can you let me know

1) How many frames are being used in a single cycle. What is value of the CALIB_MON_TIME_UNIT being used. 

2) When exactly is the API call made. During framing or idle time?

3) Why are you not using periodic calibration and using one time calibration periodically. What is the rationale behind this? 

4) IS only 1sec causing an issue. Like values like 2sec or 1.5 sec are they also leading to issues. 

Thanks,

Pradipta.

Hello Pradipta,

1- we trigger the frame every 25 mse, CALIB_MON_TIME_UNIT  is left by it's default value which is 100
2- The API is calles after each frame, the frame is triggered every 25 msec and it takes around 13 msec.
3- i do need to use the periodic calibration but it didn't work for me, only one time calibration is working 
4- i didn't check. only 25 msec periodicity -> working fine, 1sec periodicity -> doesn't work, periodic calibration with periodicity 1 and CALIB_MON_TIME_UNIT as default -> doesn't work

Hi,

Please find my comments below.

1) CALIB_MON_TIME_UNIT should have a value between 40 ms to 250 ms as per the ICD document. If you see in your case it is 25 msec * 100 which exceeds this value. So, an incorrect value is being used here. Please use a value so that it is in range.

2) Can you please clarify what is consuming 13 msec 

3) Please set the CALIB_MON_TIME_UNIT and CALIB_PERIODICITY values as valid values and the periodic callibration will work for you.

4) As per above.

Thanks,

Pradipta.

Hello Pradipta,

we trigger the frame manually periodically, w didn't trigger it periodically automatically,
so the periodic runtime calibration is only working when CALIB_MON_TIME_UNIT = 1.

so i need to make onetime calibration working with me.

after enabling onetime runtime calibration, i can see in AWR_RUN_TIME_CALIB_SUMMARY_REPORT_AE_SB event that CALIBRATION_ERROR_FLAG are set, which means that the corresponding flags are passing, CALIBRATION_UPDATE_STATUS are not set and TEMPERATURE are constant.

also there is no timing failure events in AWR_CAL_MON_TIMING_FAIL_REPORT_AE_SB.

i test the onetime calibration by pointing hot air on the sensor to see the temperature change and the flags are set, but they are not.

the temperature is changing and the flags are set only when the frames are stopped. 

Thank you

Hello Pradipta,

Now onetime calibration is working under some conditions.

first i should call it just before triggering the frame.

secondly, i should put some delay between triggering runtime calibration and triggering the frame (10 usec) unless the frame stopped triggering after a while.

my question now, i don't want to call it directly before triggering the frame as i want triggering the frame in sharp time, nothing called before it beside the 10 usec delay, i tried to trigger the calibration in the callback functions at the beginning or ending of the frame but the sensor stuck.

1- where can i call the triggering of the runtime calibration ( i don't want to call it directly before triggering the frame )?

2- if the only way to call it before triggering the frame, what the timing constrain between calling the calibration and triggering the frame?

Thank you

 

Hello Pradipta,

Kind reminder