• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 703 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

IWR6843ISK: FCC Certification using mmWave Visualizer and a proper config file...

Thomas Grounds
Prodigy 90 points
Part Number: IWR6843ISK

We are getting a product ready for FCC testing which integrates the IWR6843ISK board as part of the end-product.   We understand we can use the mmWave Visualizer for the testing (we cannot use LUA commands with the carrier card because it won't fit in the product for testing).  However, we're trying to setup a .cfg file with SDK 3.6 that will allow us to emulate the LUA commands.  We think (for instance) that the following would be used for the FCC 300MHz test portion of the configuration:

sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 7 0
adcCfg 2 1
adcbufCfg -1 0 1 1 1
lowPower 0 0
%profileCfg 0 60 7 3 24 0 0 166 1 256 12500 0 0 158
profileCfg 0 61.1 2 3.4 18 0 0 16.693 1 128 10000 0 131072 30
%chirpCfg 0 0 0 0 0 0 0 1
%chirpCfg 1 1 0 0 0 0 0 4
%chirpCfg 2 2 0 0 0 0 0 2
chirpCfg 0 0 0 0 0 1 0 1
chirpCfg 1 1 0 0 0 1 0 1
chirpCfg 2 2 0 0 0 1 0 1
%frameCfg 0 2 32 0 100 1 0
frameCfg 0 2 32 0 100 1 0
%frameCfg 0 2 16 128 0 1 0
guiMonitor -1 1 1 1 0 0 1
cfarCfg -1 0 2 8 4 3 0 15.0 0
cfarCfg -1 1 0 4 2 3 1 15.0 0
multiObjBeamForming -1 1 0.5
calibDcRangeSig -1 0 -5
compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
measureRangeBiasAndRxChanPhase 0 1. 0.2
aoaFovCfg -1 -90 90 -90 90
cfarFovCfg -1 0 0.25 9.0
cfarFovCfg -1 1 -20.16 20.16
extendedMaxVelocity -1 0
CQRxSatMonitor 0 3 4 63 0
CQSigImgMonitor 0 127 4
analogMonitor 0 0
lvdsStreamCfg -1 0 0 0
bpmCfg -1 0 0 0
calibData 0 0 0
sensorStart 0 0

It would be helpful to know if this configuration for the mmWave Demo Visualizer will work for the 300MHz band test of the IWR6843ISK board for FCC compliance, or if we should use something different entirely.
Thanks.  TomG.

  • 0
    TI__Mastermind 19920 points

    Hello.

    We are discussing this internally and will get back to you next week.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 90 points

    Thank you.  We appreciate it.  -TomG.

  • 0 in reply to Thomas Grounds
    TI__Mastermind 37805 points

    Hi Tom,

    Can you see if the FCC section of our Area Scanner doc helps? It should be a decent starting point for this.

    https://dev.ti.com/tirex/explore/node?a=VLyFKFf__4.12.1&node=A__AONFBQevesFfseDnZda2rw__com.ti.mmwave_industrial_toolbox__VLyFKFf__4.12.1

    Best,

    Nate

  • 0 in reply to Nathan Block
    Prodigy 90 points

    Hi Nathan,

    The link provides some sample profileCfg settings for Full Power/Full Bandwidth, Low Power/Full Bandwidth, and Full Power/Low Bandwidth configurations for FCC testing - which is helpful.  Our selection would seem to be the Full Power/Low Bandwidth for our particular application.  This seems though to be significantly different than the recommended LUA similar commands found in https://www.ti.com/lit/an/spracp3c/spracp3c.pdf on page 13.  Any idea why the frequency settings are different for instance, or is this just a minor variance due to the 300MHz test bandwidth for the FCC:

    %profileCfg 0 61 100 2    69 0 0 7          1 256 4000  0  0          30 %Full Power/Low Bandwidth - recommended for long range FCC testing
    profileCfg    0 61.1 2  3.4 18 0 0 16.693 1 128 10000 0 131072 30 %based on LUA 300 MHz test recommendations

    We will take a look at the back-off change for the setup to verify that it makes sense.

    Can we get confirmation on the chirpCfg and frameCfg settings as well in our proposed config file?  The data-path configuration for the DSP setup is fairly extensive, and we're trying to fully configure the front-end (so the processes will start properly configured) with some gui response on the back-end to the visualizer so we can see that the DSP/Ramp Generator/Synth is at least running continuously.  As I'm sure you know, FCC testing is expensive, and we want to be as prepared beforehand as possible.  Thanks, -TomG.

  • 0 in reply to Thomas Grounds
    Prodigy 90 points

    For instance, from the LUA configuration commands found in TIRegComplianceGuide.pdf (page 13), they recommend the following for FCC testing at 300MHz: Bandwidth Operating Frequency Range Review 300 MHz 61-61.5 GHz ar1.ProfileConfig(0, 61.1, 2, 3.4, 18, 0, 0, 0, 0, 0, 0, 16.693, 1, 128, 10000, 0, 131072, 30) ar1.ChirpConfig(0, 0, 0, 0, 0, 0, 0, 1, 0, 1) ar1.FrameConfig(0, 0, 0, 128, 16 , 0, 1).  The ProfileConfig for the 300MHz system has a start frequency of 61.1GHz, a freqSlopeConst of 16.693MHz/us, and a second corner frequency setting of 131072, whereas the suggested start frequency in the command you suggested is 61GHz, with a freqSlopeConst of 7MHz/us and no corner filtering settings at all.  The freqSlopeConst can't be set to zero, but why wouldn't it be set to 1?  There seems to be some conflicting information about what to set this to from my standpoint, as well as questions about why certain settings were suggested.  Any explanation or support would be appreciated.  We just want to be sure we're prepared when we show up for the FCC testing.  Best Regards, -TomG.

  • 0 in reply to Thomas Grounds
    Prodigy 90 points

    After reviewing the link again, I caught the power and bandwidth calculations at the bottom, so that helps with the 300MHz test settings on the profileCfg.  The chirp and frame settings seem fairly straight-forward as well.  I will review the other two FCC test parameters to see if the LUA settings match up as well.  Thanks.  -TomG.