IWR1443: TX channel select problem in single input single output mode

Xiushan:

Can you please copy and paste your .cfg file into a reply, so that I can see how you configured the device.

Best regards,

Connor Desmond

parameters work well：

sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 8 1 0
adcCfg 2 1
adcbufCfg 0 1 0 1
profileCfg 0 77 7 7 130.05 0 0 27.96 1 512 4195 0 0 36
profileCfg 1 77.199997 7 7 130.05 0 0 27.690001 1 512 4195 0 0 42
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 2 1 0 0 0 0 1
frameCfg 1 2 4 1 4 1 0
calibDcRangeSig 0 -5 5 32
guiMonitor 1 1 0 0 0 1
RangeLimitCfg 0 0.0 8.0
sensorStart

parameters can not work：

sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 8 2 0
adcCfg 2 1
adcbufCfg 0 1 0 1
profileCfg 0 77 7 7 130.05 0 0 27.96 1 512 4195 0 0 36
profileCfg 1 77.199997 7 7 130.05 0 0 27.690001 1 512 4195 0 0 42
chirpCfg 0 0 0 0 0 0 0 2
chirpCfg 1 2 1 0 0 0 0 2
frameCfg 1 2 4 1 4 1 0
calibDcRangeSig 0 -5 5 32
guiMonitor 1 1 0 0 0 1
RangeLimitCfg 0 0.0 8.0
sensorStart

HI, 

Your second chirpCfg and frameCfg looks strange to me.  It should be 

chirpCfg 0 0 0 0 0 0 0 2

chirpCfg 1 1 1 0 0 0 0 2

frameCfg 0 1 4 1 4 1 0

meaning from chirp1 to chirp1, you are using profileID 1 and enable TX2, from chirp0~ chirp0, you are using profileID 0 and enable TX2 only.

And your frameCfg means it uses both two chirps (chirp 0 ~ chirp1).   Let me know if this is what you meant.

You can go through SDK users guide to get to know the field of each CLI command like chirpCfg and frameCfg.

Best,

Zigang 

Thanks for your advice.

In fact, profileID 0 (chirpCfg 0 0 0 0 0 0 0 2) is not really used. We use only profileID 1 (chirpCfg 1 2 1 0 0 0 0 2). And the only difference between the first and second set of parameters is the TX channel. The first set of parameters work well, so is it correct to use the second set of parameters if we only want to change TX1 to TX2? We also tried to use TX3 that way, and iwr1443 worked well.

Xiushan:

With the procedure that you detailed above were you able to get TX2 to be your sole transmission antenna?

Best regards,

Connor Desmond

Nope. I checked the code(downloaded as a demo using iwr1443) thoroughly and found that TX2 is treated as AntElev(antanna elevation?) while TX1 & TX3 as AntAzim(antanna azimuth?). What is the difference between AntElev and AntAzim?

Xiushan:

If you look at the antenna notice that the middle transmission antenna (TX2) is slightly higher than then the side antennas (TX1 and TX3). It appears that TX2 might not be able to be used in isolation, but I will need to verify this and see what the reason is and share it with you. AntElev stands for Antenna Elevation and Antenna Azimuth. If you are thinking in spherical coordinate system Azimuth is the the phi and Elevation is theta. TX2 gives the ability to have 3D point clouds instead of just 2D point clouds. Here is a link to spherical coordinate system if you need a visual:

https://en.wikipedia.org/wiki/Spherical_coordinate_system

I will get an answer to this and share back with you. In the mean time can you share with me why you have to use TX2.

Best regards,

Connor Desmond

Thanks a lot for the information. Actually we have no particular use of TX2. We just tried every combination of TXn and RXn to check out whether it can be used in single in single out mode.

Xiushan:

I am still in the process of getting an answer for using TX2 as the single transmission antenna. I will get back to you when I have an answer.

Best regards,

Connor Desmond

Xiushan:

Can you please try the following configuration:

profileCfg 0 77.199997 7 7 130.05 0 0 27.690001 1 512 4195 0 0 42
chirpCfg 0 1 0 0 0 0 0 2
frameCfg 0 1 4 1 4 1 0

Let me know if this works.

Best regards,

Connor Desmond

Thanks for your advice, but still can't work. It seems using TX2 alone is forbidden by the sample code we use. We tried to modify the code manually and TX2 can be used.

Xiushan:

Can you please provide the source of the sample code that you are using as well as the modification that you made to make TX2 be used.

Best,

Connor Desmond