IWR6843AOPEVM: How to realize duty=10% with frame-time =33[ms] with gesture_recognition demo by IWR6843AOPEVM

matusan

Guru 10235 points

Part Number: IWR6843AOPEVM

Hello, TI Experts,

I have additional question from the below E2E-thread.

https://e2e.ti.com/support/sensors/f/1023/p/935692/3464425#3464425

We continue to investigate how to realize duty=10% with gesture_recognition demo by IWR6843AOPEVM.

We need to realize this gesture demo with the frame-time =33[ms] to passes the FCC Waiver Order DA 18-1308

(equivalent Japanese certification) as we said below E2E-thread including DA-18-1308A1.pdf.

https://e2e.ti.com/support/sensors/f/1023/t/934330

https://docs.fcc.gov/public/attachments/DA-18-1308A1.pdf

So we need to modify "cli.c" like below to meet duty=10% in frame-time=33[ms];

"frameCfg 0 1 16 0 33 1 0 "

->The duty seems to be calculated about 10% (= ((71+34)+(82+34))*16/33000).

But this gesture demo doesn't work properly.

Question:

- Could you tell us the recommended way to realize duty=10% with frame-time =33[ms] to passes the FCC?

- Are there any successful way of the gesture demo code modification including "*.c and *.h" with "frameCfg 0 1 16 0 33 1 0 "?

We would also appreciate if you check the behavior with your EVM and tell us successful way.

Best regards,

over 5 years ago

0 Vaibhav Mahimkar over 5 years ago

TI__Mastermind 23725 points

Hello,

We can help you confirm the computation formula for duty cycle. Typically On time is Chirp period * Number of chirps.

Chirp would have to be designed to meet the application sensing needs along with regulation needs. For Gesture application this would typically be velocity and range resolution close enough to what the existing chirp design uses.

Alternately it would be worth checking if the exiting chirp can be used with reduced transmit power to meet the local regulation requirements.

Hope that helps.

Thank you.

Vaibhav

0 matusan over 5 years ago in reply to Vaibhav Mahimkar

Guru 10235 points

Hi,

Thank you very much for your kindness.

I really appreciate your help.

We would like to know "How to realize duty=10% with frame-time =33[ms] with gesture_recognition demo".

But this gesture demo doesn't work properly by changing to "frameCfg 0 1 16 0 33 1 0 " in cli.c.

(It seems to be stopped in about 10 seconds after gesture demo running.)

Questions:

- Do you have same experience with your IWR6843AOPEVM by changing to "frameCfg 0 1 16 0 33 1 0 " in cli.c?

- Could you tell us how to modify the gesture demo code such as "*.c and *.h" with "frameCfg 0 1 16 0 33 1 0 "?

Best regards,

0 matusan over 5 years ago in reply to matusan

Guru 10235 points

Hi,

Thank you very much for your kindness.

I really appreciate your help.

Do you have any update?

I would appreciate if you tell us about the progress on this.

Best regards,

0 Charles Oladimeji over 5 years ago in reply to matusan

TI__Mastermind 33805 points

Hi,

Still looking into this to provide some useful information.

The gesture demo requires a bit more fine tuning. Using a new chirp will mean you'll need to collect the raw data with gestures and generate data to fine tune the application

Regards,

Charles O

0 matusan over 5 years ago in reply to Charles Oladimeji

Guru 10235 points

Hi,

Thank you very much for sending us your situation.

Please tell us if you find some useful information to realize duty=10% with frame-time =33[ms] with gesture_recognition demo.

Best regards,

0 Nitin Sakhuja over 5 years ago in reply to matusan

TI__Mastermind 30405 points

Hi Matusan,

Changing the number of chirps from 256 (i.e. 128 x 2) to 32 (i.e. 16 x 2) will reduce the gesture recognition performance and we have not evaluated whether/how it will perform. The gesture demo is provided as-is as a proof of concept but we do not support custom modifications to it.

IWR6843ISK-ODS: Implementation of twirl gesture

You mentioned that the demo stops after 10 minutes. If you are able to get the desired gesture performance within this time, you can try to debug the cause of failure by running the demo in CCS mode as explained in the demo user guide and look for and errors on the CCS console as well as the call stack when the demo stopped.

Regards

-Nitin

0 matusan over 4 years ago in reply to Nitin Sakhuja

Guru 10235 points

Hi,

Thank you very much for your kindness.

I really appreciate your help.

I'd like to continue to check the behavior from your advice.

Best regards,

Sensors

Sensors forum

IWR6843AOPEVM: How to realize duty=10% with frame-time =33[ms] with gesture_recognition demo by IWR6843AOPEVM