IWR6843AOP

Hello,

A few things to note. Our demos specifically for detecting cars are optimized for longer distance, so they don't support the AOP device as, and will require code changes. They both are made to use the ISK antenna / EVM. What kind of distance are you needing to detect cars at? The AOP device will be somewhat limited in max distance due to the antenna pattern.

If you are trying to detect parked vehicles, then the Parking Garage Sensor lab is the best to start with.

If you are trying to detect moving cars, then the Traffic Monitoring Demo is the best to start.

Both of those use the IWR6843ISK. It seems in the previous question you want to detect parked cars with the AOP. In that case, you can use the Area Scanner Demo. This is very similar to the parking garage sensor demo, but it supports the AOP antenna configuration.

Regards,

Jackson

Within 5m i want to detect moving the car and what is the difference between MSS and DSS?

Which files I should look at if I choose traffic monitoring demo to change for AOP device?

Hello, if you just want to detect cars within a short distance, and use the AOP device, using the area scanner lab is probably best. You can ignore the static objects if you chose. It will be tuned for a shorter distance. You can see the CFG parameters from the parking garage sensor lab (which has the same embedded SW mostly) to see how to modify the chirp parameters for cars. Switching to the AOP antenna is difficult as it requires a new angle estimation procedure that is not included in the traffic monitoring demo.

Regards,

Jackson

I checked the cfg file of parking garage sensor and area scanner. I could not find any difference in it. Could you tell me which parameters to check for detecting cars?

This depends on how you want to 'detect' cars. If you want to track them as they are moving, you will want to modify the gating parameters of the tracking configuration. Please see the following document. 3D_people_counting_tracker_layer_tuning_guide.pdf

If you are using the static object detection, you will want to modify the parameters for the static config. Please see the following document.
https://dev.ti.com/tirex/explore/node?a=VLyFKFf__4.10.1&node=ANeAbdL5iuCGKCHkfAqZgw__VLyFKFf__4.10.1&r=VLyFKFf__4.1.0 

Regards,

Jackson

If i use the area scanner lab code and change the configuration files according to the pdf file for detecting cars for AOP device. Is this sufficient to moving detect cars using AOP device? or anything else i should also handle?

I'm trying to change the cfg file by checking the traffic monitoring 3d file into the area scanner aop file.

In tracking commands, for stateParam and trackingCfg, the parameters defined or not the same. Either one parameter is more or less in one of them and I'm getting errors while i run the gui of the area scanner.

Also I'm referring to the 3D_people_counting_tracker_layer_tuning_guide.pdf document for configuring and understanding the parameters.

Could you help me if the number of parameters are constrained in AOP deivce?

Hello,

The difference is not in the AOP device, but in the SW in those demos. They use different versions of the tracker and the command structure is a little different. The documentation should apply well to the traffic monitoring demo, but less so to the Area Scanner demo. To understand the exact parameters needed, it will be best to go look in the code to see which params are needed. The file to check is mmw_cli.c at the following path.

C:\ti\mmwave_industrial_toolbox_4_10_1\labs\Area_Scanner\src\68xx\mss

There is also a similar file in the traffic monitoring demo.

Regards,

Jackson

I have attached the screenshot of mmw_cli.c file which i referred to, it looks same but I'm not sure how are the parameters are more inside the cfg files.

The cfg files also i have attached which I'm referring to where i see the parameters are not same.

Could you please tell me how to resolve this and also if I'm referring to correct files?

Hello,

I think the help strings are not accurate in all these demos.If you go to the command handler function for those CLI commands (e.g. MmwDemo_CLITrackingCfg), it will show you the difference in how each of those are being used. The variable assignments will look something like the below image.

Those functions will be in the tracker_utils.c source file, which is linked to at the top of the mmw_cli.c file.

Regards,

Jackson

Thank you, i figured out for the Stateparam how to fix but not for trackingcfg.

I can directly change the files of area_scanner_68xx_mss lab project code for AOP right?

When i build the system, it's showing for ISK, I'm bit confused here, if we have project files for AOP or not?

I'm unable to find AOP folder for .c and .h files. i can only see mss and dss folder which are executing for ISK i think

Thank you, got it

If i just change the code file of the config by adding the parameters, is that sufficient? The gui did not work when i updated the parameters. Are there anything else which needs to be taken care also?

If you have changed the format of the CFG file, you will need to change the format of the CFG parser in the GUI files. If you just changed the values, there should be no issue. The demos may not be compatible with other GUIs however, so if you change which GUI you are using, you will need to check the CFG parser to ensure compatibility.

Were there any errors in the GUI console? you may need to run the .exe from the CMD console so that the errors stay if you close the program. Or if you run from matlab source the errors will show there.

Sorry, it did not resolve my issue by mistake it happened.

Yes, you are right. I have attached both the files. I have changed the values and have commented few of the traffic monitoring parameters inside the area scanner since it is not working in the GUI when i execute. It says something like it cannot read the values (I don't remember exactly the error, once I reproduce it, i will post it).

Please let me know which other files I need to consider?

4645.area_scanner_68xx_AOP.cfg

area_scanner_68xx_demo_aop.txt

I have attached the bin file but renamed as .txt since i could not upload it. But could you let me know where should i change the GUI files when new parameters are added in the cfg file?

I have changed the defineCLICommands.m file for GUI, other than this file any other file should be taken care?

Thanks Harish,

I will look at this later today and get back to you with some suggestions early next week.

Regards,

Jackson

This type of error I get when i increased the number of parameters in StateParam and edited one of the gui file as mentioned above. Should I take care any other files?

Hello,

It looks like the .bin file you sent does not boot fully. Are you using the default AOP bin for area scanner, or have you modified the source code?

Also, that error means that the sensor crashed after sending the CFG. This is very unlikely to be caused by the values in stateParam, more likely there was a code change that causes this. 

I don't see anything in the CFG file you sent that shouldn't work with the area scanner demo, however the values in gatingParam and maxAccelration are very large and will probably cause detection issues. Also, you have modified your boundary box to be very large. There is no problem with this, just note that the AOP device will not get any detections at the far values you have.

Regards,

Jackson

I have again attached the .bin file which has some code modifications in it adding the extra parameter whcih is needed for the StateParam as the initial step I have done. The build is successful and also i can dump the code into the hardware using this file.

The values in the cfg file, I have taken it from Traffic monitoring as an initial step to just get started, later fine tuning the values is the thought process. Since, I'm unable to execute it successfully, I'm stuck at this point. Even the COM ports, don't detect properly and they are sporadic sometimes. Could you help me how to proceed further?

6471.area_scanner_68xx_demo_aop.txt

For hardware issues: I have a thread here:https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1088208/iwr6843aop-iwr6843aop

Hi Harish,

Please make sure you are following all the steps in the user's guide correctly when rebuilding the project, as this binary does not start up. It seems the changes you have made stop the program from booting correctly. Did you change anything besides the CLI file? Did you build the DSS image before building the MSS image? Did you select AOP for both builds?

Regards,

Jackson

Also, if you are just trying to use longer range detection with the AOP and area scanner, please try the following CFG file with the default area_scanner binary file for AOP.

area_scanner_68xx_AOP_longRange.cfg

The antenna pattern of the AOP device may not work well for detection longer than 20m or so, maybe less depending on the object.

Regards,

Jackson

I have also changed tracker_utils.c since the parameters had to be changed for StateParam. I changed the configuration in properties and made the AOP device active: I had compiled only MSS and did not touch DSS folder at all. Is this the issue?
Should I compile first DSS and later MSS?

I need to detect from a distance of 5m onwards. I should check only gatingParam for detecting the car from a distance?