Antenna Array Workshop HFSS
Antenna Array Workshop HFSS
5G Applications
(2)
Snap1
Snap2
2
Slave The Master and Slave boundaries force a periodicity in the fields corresponding
to the periodicity of the array. It does this by mapping the fields from the
Master boundary to the corresponding Slave boundary. These fields are
identical to each other with the exception of a potential phase shift. This phase
shift is what will be used to enforce the progressive phase delay across the array
that steers the beam.
Master and Slave boundaries use UV coordinate systems to determine the field
mapping. Since Master/Slave pairs are defined on opposite sides of the unit cell,
1 the slave’s UV coordinate system should be a simple linear translation of the
Master master’s UV coordinate system. If done correctly, the distance between each
boundary’s UV coordinate system should correspond to the distance and
direction of the next adjacent element in the array.
UV coordinate systems are defined by selecting two points. The first point
corresponds to the coordinate system’s origin. The second point defines the U
axis’ direction.
The phase delay between Master / Slave boundary pairs is defined on the Slave
boundary’s Phase Delay Tab. It can be defined as a phase delay or in terms of
the array’s scan angle. If the array’s scan angle is chosen, HFSS will determine
the appropriate phase delay to properly steer the beam.
UV Co-ordinate
System
(2)
(1)
(1)
1
Master
(1)
(2)
(2)
2
Slave 2
1
Slave 1
1
Master 1 2
Master 2
Note: The UnitCell design should have2 pairs of Master / Slave boundaries totaling 4 boundaries all together. Each pair should be
defined on opposite sides of the unit cell. Each boundary pair should have UV coordinate systems defined on them in such a way that
the U-axes point in the same direction and the V-axes point in the same direction. The only difference being a linear translation of their
origins across the unit cell.
In addition, each slave boundary should use the Scan Angle method for defining the phase delay between the fields on the Master and
Slave boundaries. This scan angle should be controlled by two variables; Phi_Scan and Theta_Scan.
Note: The radiated waves from the array will be terminated in the Floquet Modes defined by the Floquet Port Setup. Each Floquet Mode
is a plane wave supported by the periodic structure. They also correspond to the different beams an array might support. They come in
two polarizations; Transverse Electric (TE) and Transverse Magnetic (TM). Assuming the Floquet Port is parallel to the XY plane, TE modes
are +/- Phi polarized waves and TM modes are Theta polarized wave. The dominant modes are the TE 00 and TM00 modes which
correspond to the phi and theta polarized components of the array’s main beam. All other mode indexes correspond to various grating
lobes.
The energy associated with any mode not defined in the Floquet Port will be short circuited back into the model so its important to
include all propagating mode. However, which modes propagate depends on the angle the array is scanned. The Mode’s Calculator was
added to make choosing the appropriate modes easier. It will search a scan volume defined by Theta and Phi angles and report the
modes with the smallest attenuation constant over that scan volume. Make sure any mode not included in the port experiences at least
50dB of attenuation as it propagates from the element to the port. That way it has little chance to affect the predicted performance. The
attenuation is calculated in dB/length so the total attenuation can be computed by multiplying the calculated attenuation by the unit cell
height (27.10dB/length)*1.8cm = 50dB of attenuation for mode 3, 4, 5, 6. All modes listed above mode 3 have 0dB/length of attenuation
so they must be included.
Its important to note that the height of the Unit Cell impacts how many modes need to be included in the Floquet Port Setup. Non-
propagating modes can be removed from the setup by choosing a height large enough to make sure they experience the recommended
attenuation for elimination.
Note: The active impedance of an array changes as the array is scanned in different directions. Since the scan angle is fixed through
the Theta_Scan and Phi_Scan variables used in the Slave Boundaries, the unit cell model needs to be simulated explicitly at different
scan angles to capture the element’s behavior for each of these conditions.
The easiest way to perform the analysis over the scan volume is to use the Optimetrics License to create a Parametric Sweep of the
Theta_Scan and Phi_Scan variables. The parametric sweep created here scans the array from boresight out to 60. This is determined
by the Definitions Tab which swept the Theta_Scan variable from 0deg to 60deg. The Phi_Scan is set for 0deg and 90deg, this
parametric sweep corresponding to the array scanning along the XZ plane and YZ plane.
This example assumes that the computer running the analysis has 4 cores and there are 4 DSO licenses
available.
If the computer running this sweep does not contain 4 cores or you do not have 4 DSO licenses you will
need to reduce the number of Tasks and Cores appropriately. If you have more cores and licenses available
you can further speed up the analysis by adding more tasks.
Note: The Embedded (Active) Element Pattern can be extracted from the radiation patterns just plotted by
taking the one point on each curve corresponding to the scan angle used to produce that curve. For instance,
the Embedded Element Pattern for the angle (theta, phi) = (15deg, 90deg) would correspond to the (theta, phi) =
(15deg, 90deg) point on the RealizedGainTotal curve associated with Theta_Scan = 15deg and Phi_Scan = 90deg.
All the other points on the curve would be discarded. The points that are part of the Embedded Element Pattern
are highlighted with blue boxes in the above data table.
Note: Scan_CS is a relative coordinate system parameterized so the z-axis always points in the scan direction defined by
Theta_Scan and Phi_Scan. You can visibly verify this in the 3D Modeler by switching to the Scan_CS coordinate system,
changing the value for Theta_Scan to 60deg and observing where the z-axis points.
Note: This pattern can then be used to predict a finite array’s pattern through the method of pattern
multiplication.
𝐸𝐹𝑖𝑛𝑖𝑡𝑒 𝐴𝑟𝑟𝑎𝑦 = 𝐸𝐸𝑚𝑏𝑒𝑑𝑑𝑒𝑑 𝐸𝑙𝑒𝑚𝑒𝑛𝑡 ⋅ 𝐴𝑟𝑟𝑎𝑦𝐹𝑎𝑐𝑡𝑜𝑟
To fill in the rest of the pattern additional simulations would need to be performed at different scan angles.
• Rename Design
− In the Project Manager window, select: SqPatch_Unitcell (DrivenModal)
• Right-click and select the menu item: Edit > Rename
− Rename design to: SqPatch_DDM
− In the Project Manager window, minimize the Unit Cell design and expand
the Finite Array design
Note: We don’t want to invalidate the solution of the unit cell simulation because we will
want to use the mesh from this solution to solve the finite array design. By copy/pasting
the unit cell design to create the finite array design, we are ensuring that the unit cell used
to build the finite array is geometrically-equivalent to the one used in the unit cell
simulation --- in other words, we can safely use the same mesh in both designs.
In the finite array simulation, padding elements border the entire array. These are not visible to the user. When comparing
the finite array DDM results to an explicitly drawn array of the same configuration, one must remember to include the air
padding buffer around the model as shown below.
• Radiation Setup
− In the Project Manager Window, right-click on Radiation and select Insert
Far Field Setup >> Infinite Sphere…
• Name: 3D
• Phi
• Start: 0deg
• Stop: 360deg
• Step: 1deg
• Theta
• Start: -180deg
• Stop: 180deg
• Step: 1deg
− Select OK
• Realized Gain dB
− In the Project Manager Window, right-click on Results and select Create
Far Field Report >> 3D Polar Plot
− In the Context field, select 3D from the Geometry drop-down menu
− Under Trace Tab:
• Category: Realized Gain
• Quantity: Realzied GainTotal
• Function: dB
− Select New Report
− Select Close
− Click under Results on Realized Gain Plot 1
− In the Properties window change Name: “3D Realized Gain Beam
Steered”