AWR6843AOPEVM:

Hi,

1. Will get back to you
2. Most of our automotive demos are configured such that these vibrations are not a major issue, but I can look at this further if necessary.
3. This FOV is determined by the antenna package, there should be documentation on this on the product pages for the awr6843 device if you want to redesign it.
4. This is a bit of a complex question, but in most demos there is a calibration structure that is passed in during the open/start process. 

5. Depends on the calibration settings. We pass in a configuration file to most of our demos over CLI at startup to config many different parameters, you can view these in the SDK User's Guide section called "Configuration file format". We also support saving calibration results into non-volatile memory and restoring them later, this is called Save and Restore. You could also extrapolate these to add your own configuration if necessary.
6. This heating is specific to the AOP variants of the devices, so if it becomes an issue for your application than you may want to look at the other package instead of the AOP.

Let me know if there are any other questions.

Best Regards,
Alec

Hi Alec, 

Thank you for your support.

below, my comments:

1. Will get back to you

We will wait for your response, it will be really helpful.

2. Most of our automotive demos are configured such that these vibrations are not a major issue, but I can look at this further if necessary.

Honestly, based on the results that we have realized we need to go deeper in vibration compensation.

We also noticed, that the EVM supports an acceloremeter (Not Mounted), is it used for vibration control? and is there an SDK that support it?

3. This FOV is determined by the antenna package, there should be documentation on this on the product pages for the awr6843 device if you want to redesign it.

Got it, thank you.

4. This is a bit of a complex question, but in most demos there is a calibration structure that is passed in during the open/start process. 

Got it, thank you.

5. Depends on the calibration settings. We pass in a configuration file to most of our demos over CLI at startup to config many different parameters, you can view these in the SDK User's Guide section called "Configuration file format". We also support saving calibration results into non-volatile memory and restoring them later, this is called Save and Restore. You could also extrapolate these to add your own configuration if necessary.

We have already verify the Configuration File Format, we need to run the calibration as an independent function of the open/start process.

For example, if the passenger change, we need to re-run the calibration without restarting the system.

6. This heating is specific to the AOP variants of the devices, so if it becomes an issue for your application than you may want to look at the other package instead of the AOP.

Got it, thank you.

1. Did you base this application off of one of our demos? If so, which one?
2. I have not personally encountered a situation where this has been an issue. I will investigate with other members of my team, but I do not believe an accelerometer would be a viable option considering how slight the vibrations would be.
5. If you are trying to trigger this calibration from an EXTERNAL system, then I would recommend referencing our CLI commands and adding your own commands to trigger this.
6. Check out the following document https://www.ti.com/lit/an/swra672/swra672.pdf

1. Did you base this application off of one of our demos? If so, which one?

Yes we are using the Vital Sign Lab demo.

2. I have not personally encountered a situation where this has been an issue. I will investigate with other members of my team, but I do not believe an accelerometer would be a viable option considering how slight the vibrations would be.

We will wait for your response, it will be really helpful.

5. If you are trying to trigger this calibration from an EXTERNAL system, then I would recommend referencing our CLI commands and adding your own commands to trigger this.

Honestly, we have tested with the CLI commands and we have not reach our goals.

Could you please specify more.

6. Check out the following document https://www.ti.com/lit/an/swra672/swra672.pdf

Got it, thank you.

We also need to run the Occupancy detection & Occupancy detection + Vital signs labs on our EVM but it did not work and it noted that those labs are siupported only by the AWR6843ISk.

Does the AOP version supports those labs ?

If yes, is there any procedure?

Else, is there any equivalent of those labs for our model?

Hi,

I'm not sure offhand how much this specific lab's functionality would be affected by the antenna pattern, but I believe the vital signs demo for 68xx in the Industrial Toolbox supports all of the antenna patterns.

Best Regards,
Alec

2. I have not personally encountered a situation where this has been an issue. I will investigate with other members of my team, but I do not believe an accelerometer would be a viable option considering how slight the vibrations would be.

We will wait for your response, it will be really helpful.

5. If you are trying to trigger this calibration from an EXTERNAL system, then I would recommend referencing our CLI commands and adding your own commands to trigger this.

Honestly, we have tested with the CLI commands and we have not reach our goals.

Could you please specify more.