Blacknight Space blog

Modeling Comets & Asteroids

alex@blacknightspace.com (Alex Ridgeway) — Wed, 03 Jun 2026 18:46:09 GMT

STK-Modeling Comets and Asteroids Using NASA Ephemeris Data

In this tutorial, we will create specific Ephemeris Data for the Comet Nishimura which passed through our solar system in the Fall of 2023. We will use NASA’s Horizon tool to generate specific Ephemeris Data for this comet and Implement that Data into STK. There are several tools and external links required to replicate the example Scenario. Importing a Custom .obj model is not required to view the STK functions demonstrated in this tutorial, so these steps will be optional.

Resources:

Building the Ephemeris Data:

We are going to build a Custom .txt file using NASA’s Horizon System Planner. To do this we must first set the correct parameters.

Go to Horizons System (nasa.gov) to access the Horizon’s Web Application.

First set the 1 Ephemeris type to Vector Table.

Set the 2 Target Body: to the official name of the Comet, enter “C/2023 E1 (ATLAS)”.

Set the 3 Coordinate Center: to be geodetic by using method ‘Specifying Coordinates’.

Set the 4 Time Specifications: to be start time of 2023-09-01 and the stop time of 2023-10-1 with a step of 6 hours.

Set the 5 Table Settings: by clicking [Edit] to configure the Vector Table Settings. Ensure that your settings are the same as the ones pictured below:

Once you complete these steps, your Ephemeris Data settings should look like this:

Click [Generate Ephemeris] Data and save it to an easily accessible location. Now we will begin to implement this data into STK to view Comet Nishimura’s Path.

Note: You can press Save/Load Settings, to save the settings for reuse.

Integrating with STK

You will need the STK JPLHorizonsEphmeris.ZIP file from the AGI Website. It can be found at the bottom of this page: Knowledge: Downloading and Using Ephemerides for Comets, Asteroids, Small Bodies, and Interplanetary Spacecraft (site.com)

After you have downloaded and unzipped it, bring the .xml file into the STK Plugins Folder. This is the default directory for it: C:/Program Files/AGI/STK 12/Plugins

Next, we will open Command Prompt or a Windows PowerShell as an Administrator.

We will run the following command (replace the Install Location with the proper one correct to your download):

regsvr32 InstallLocation JPLHorizonsFileReader.wsc

Configuring the Scenario

Create a new STK Scenario within the period specified while creating the Ephemeris Data. For this example, use 1 Sept 2023 until 1 Oct 2023.

Then use the Insert STK Objects tool to add two Central Bodies and a Satellite.

Within the Properties->Basic->Definitions Tab on the Central Bodies set one of them to the Earth and the Other to the Sun. Ensure Auto Rename is checked:

Click [OK] to save your changes.

After Renaming the Satellite to Comet_Nishimura, it should look like this:

Open the Properties->Basic->Orbit page for Comet Nishimura

Change the Propagator to STK External. Then change the Ephemeris Type to JPL Horizons Ephemeris Reader. Next, select the file you generate from NASA’s Horizon tool earlier. It should look like the following:

Click OK to save your changes and close the Satellite Properties.

Configuring the Window

Maximize the 3D Graphics Window and Open the Globe Manager:

Disable the Moon in the 3D Graphics Window to declutter the Scenario:

After that, configure the Settings for the Central Body Objects.

In each, go to Properties-> 3D Graphics-> Attributes and ensure only the following are selected:

Click OK to save your changes. After that open, the 3D Graphics Window Properties->Details and enable Label Declutter:

Then, in the 3D Graphics Window Properties-> Advanced Section, turn the max viewing distance up to 1e^20km:

Click [OK] to save your changes.

Now Configure your window by clicking on Comet Nishimura and selecting Zoom-to. Then you can start your scenario to see its Path in the given Ephemeris.

You now have a Satellite Object that has used NASA’s Ephemeris Data to represent the path of a Comet that passed through our Solar System. You can stop there, or if you want to you can continue to the optional steps to change the Satellites model.

Changing the Object Model (Optional)

The “Comet Nishimura” has the default Satellite object model in the 3D Graphics View, which is not ideal for 3D graphics window when zoomed in.

An example celestial object model that you can use, is one from Sketchfab, located here: Asteroid 3d Model.

Note: This is not Comet Nishimura but an example 3D model of a celestial object.

Additionally, when downloading 3D Models, they might not be in the correct format for STK to ingest. The Asteroid model is available as an *.OBJ model. We will need to convert the .obj file to a file STK recognizes. The easiest way to do this is with Blender, a free 3D modeling software, which can be downloaded for Windows here: Download — blender.org

Once you have downloaded and unzipped the model you wish to use, and installed Blender, you can begin to modify your .obj file into a .glb file that STK can use.

Open a new Blender Scenario and Import your wavefront .obj file:

Then we will add the necessary textures to the Object. Select the Test_planet on the right side of the Blender Window and select the Materials Window.

Then select the yellow dot and select the Image Texture option:

Next, select the Open option and CTRL-click all the options provided in the download of the Asteroid object from Sketchfab:

Then export your model for use in STK as a .glb file:

Return to your STK Scenario and Select Comet Nishimura Properties -> 3D Graphics ->Model and change the model to the custom one we compiled in Blender:

Click [OK] to save your changes.

Now select the 3D Graphics window and Zoom-to your Comet Nishimura:

Next Steps:

Now you are ready to use NASA’s Horizon tool to generate Ephemeris data and implement that data into an STK Scenario to show accurate paths of Comets and Asteroids in our solar system. These can be used for a variety of applications and purposes to gather data or simply figure out when to look outside to observe the next celestial object’s close approach.

If you have any further questions or need assistance, we are here to help! Our dedicated Tec-Support team is ready to provide prompt and personalized assistance tailored to your needs. We look forward to assisting you and ensuring a positive experience.

Thanks,

Blacknight Space Team

Troubleshooting a Corrupted Scenario in STK

alex@blacknightspace.com (Alex Ridgeway) — Wed, 03 Jun 2026 18:42:05 GMT

How do I trouble shoot a potentially corrupted scenario in STK?

Try to identify the specific problem within the scenario. Generally, there is a root cause with multiple things failing then STK crashes, but all issues can be traced back to one cause. Sometimes STK is looking for a file, that now doesn’t exist. Sometimes, two scenarios are writing to the same file. Sometimes, STK topped out the machine when running analysis and caused a crash, which caused corruption in a file it was writing at the time of the crash. Sometimes, STK simply crashes for some other reason and now the scenario is corrupt. We have luck in recovering a corrupted scenario but there is no guarantee that we can fix a problem. Check the Tips using STK below.

Here are things to check about your scenario that crashes STK

Identify when does the crash occurs.

Does the crash happen at startup?
- This could indicate a graphics issue, as crashing at start up can mean that STK could not render the scenario, so it crashes.
Does the crash happen when running analysis right after startup?
- This could indicate a problem with an object like a satellite, aircraft or vehicle. STK will repropagate objects first, before doing anything else. So if there was an error in the propagator, which causes a crash, then an object is the issue.
- This could indicate a problem with an object like coverage, comm systems or volumetric, which generally recalculate right after start up?
Does this crash happen when recalculating an analysis object?
- This is a problem with the analysis object like coverage or comm systems. Check what objects are used in that analysis and if those objects are valid, which could be the root cause. Remove or recreate the analysis.
Figure out if there is a specific time when the error occurs, does this correspond with an object being added or a change being made?

Check if you were saving a scenario to the same folder, Scenario1_v1 Scenario2_v2…

This has caused corruption in the past because STK saves the scenario to that folder but the first and second version CAN modify the other files like Satellite1.sa. STK does not save copies of Scenario2_v2_Satellite1.sa, it only saves Satellite1.sa.
Instead of saving the scenario with a different name, simply Save the Scenario like normal, then use Windows Explorer, create a copy of the FULL Folder, and call it *_backup. This way you backup your scenarios AND all of your objects.

Confirm STK is using the right graphics card, and that your drivers are up to date.

First, check your graphics card drivers are up to date. If not, update your graphics card drivers.
Once you've confirmed your drivers are up to date, in STK, navigate to Help -> Graphics Card Info
Under OpenGL Information, you should see the brand name of your graphics card shown to indicate that the graphics card is being used.
For example, in the image below, the Graphics Card Info report shows that there is a NVIDIA graphics card available, but instead, STK is using the Intel XE Graphics. This is not correct.

If STK is not using the correct graphics card, such as in the image above, follow the instructions in the following blog to configure STK to use your graphics card: AGI: Make STK Look Beautiful Using Your Fancy Graphics Card

Check the Error Messages from C:\Users {UserNameORUsername\OneDrive}\Documents\STK 12\Config\Logs

There are some nominal warnings, so be sure to review any errors or messages that may have been sent right before the crash.
Error Messages could indicate a problem with a specific object or analysis. Please see if it says where the problem lies.
Missing External Files, for STK Scenarios, there are many things that can be added to your scenario. STK pulls in data from many different places, and you can also tell STK to pull in data from other sources. STK has features to look for moved files upon scenario load. Moving files that STK relies on is not a good practice.

Try on another machine. If the error occurs on both machines, then the scenario has issues.

Retrieve the minidump diagnostic file (When all other items are checked)

Set the environment variable AGI_GENERATE_MINIDUMP = 1.
Reproduce the crash.
A dump file will be created in %TEMP% in a subfolder called AGI-STK12Application.
The %TEMP% directory is usually C:\Users\username\AppData\Local\Temp. If yours is not located there, you can paste %TEMP% into your browser file path to find it.

How to uncorrupt a corrupted scenario?

Create a copy of your full scenario folder and save in a new place. Use that for the following troubleshooting steps.
- VDFs should not be used as they are fully packed scenarios and cannot be broken apart.
First see if there is an issue with the objects in your scenario.
- Create a new scenario and import an object file, one at a time.
- Each time you load an object, see if there is an error in the message viewer.
- Each time, see if the object loads as you expect.
- IF you are back to a fully built scenario, forget about your old scenario and carry on with this one.
If all of the objects load in the new scenario but you still want your original scenario.
- You can compare a default scenario vs. the corrupted scenario file, *.sc.
- Create a default scenario, then save it.
- Open a tool like ExamDiff.
  - ExamDiff compares to files.
  - If you cannot install another program, open two Notepad++ or open two Notepads, side by side. Visually inspect these.
Compare the potentially corrupted scenario file and the default scenario.
- The scenario properties should be similar.
- Check for any setting in the bad scenario that could be causing a problem.
- *Not recommended, but if you identify a problem in the scenario file, you can copy sections from the default scenario and add them into your scenario file. Then try to re-load into STK.
If all else fails, please send the full scenario folder to support@lsas-tec.com and we can help troubleshoot further.

If you have any further questions or need assistance, we are here to help! Our dedicated Tec-Support team is ready to provide prompt and personalized assistance tailored to your needs.

Thanks,

Blacknight Space Team

STK: Lunar Resources

alex@blacknightspace.com (Alex Ridgeway) — Tue, 02 Jun 2026 23:01:41 GMT

Where are the Lunar Mission resources?

STK: Lunar Mission resources:

With the upcoming Artemis mission, it's time to focus on lunar exploration once again. If you're planning a lunar mission, STK provides the perfect platform for modeling and simulation to support your mission from start to finish.

To get started with lunar mission planning, you can watch our YouTube tutorial on the Astrogator segment called "Earth to Moon." This segment offers a practical foundation for designing a lunar mission, considering launch dates, parking orbit altitudes, and lunar orbits.

AGI: STK Tip: Quickly Design a Moon Mission

For a more detailed understanding of translunar injection targeting, you can find an Astrogator tutorial on b-plane targeting for lunar missions.

Moon Mission Using B-Plane Targeting

Beyond reaching the Moon, STK offers capabilities for lunar terrain analysis. You can explore the lunar surface because STK has the ability to import lunar terrain data. This allows for improved visualization and analysis of lunar landing missions or sensing missions. You can refer to our YouTube video on importing lunar terrain data.

Importing Lunar Terrain - AGI Geeks 15 - YouTube

By combining lunar terrain data with STK's objects and reports, you can create accurate representations of line-of-sight access, revisit time, lighting times, and communication capabilities on the lunar surface. With the resources provided, you can create detailed lunar mission scenarios that encompass various subsystems and gain novel insights.

STK makes planning and executing a lunar mission more achievable than ever before.

Thanks,

Blacknight Space Team

LaunchPad's Training Platform

alex@blacknightspace.com (Alex Ridgeway) — Tue, 02 Jun 2026 22:50:34 GMT

LaunchPad's Training Platform delivers interactive, software-connected training designed to help users become proficient with STK and ODTK through hands-on learning, guided exercises, and graded evaluations. Unlike traditional training that relies on videos and reading alone, LaunchPad places users directly inside the software, where they learn by doing.

Whether you're new to the space domain, building mission analysis skills, or becoming an orbit determination expert, LaunchPad provides a structured path from beginner to certified practitioner.

Why use the Training Platform in LaunchPad?

Interactive training connected directly to STK and ODTK
Learn through real-world exercises and scenarios
Self-paced training available anytime, anywhere
Progress tracking and mastery-based learning
Graded evaluations and certification exams
STK and ODTK professional certifications

Demonstrate Skills. Earn Certification.

LaunchPad certifications validate real skills—not just course completion.

Every certification includes practical exercises and graded evaluations performed inside STK or ODTK. Users must demonstrate proficiency by completing hands-on tasks and passing assessment criteria.

STK L1 Certification
STK L2 Certification
ODTK L1 Certification
Additional Certifications coming soon!

Certifications provide organizations with a measurable way to track workforce development and software proficiency.

Available Courses on the Space Domain

Intro to Space

Foundation Course | 4 Lessons | Graded

New to the space domain? Intro to Space builds the conceptual foundation required for success with STK, ODTK, and space mission analysis.

Topics Covered

Orbital mechanics fundamentals
Orbit types and usages
Propagation and Perturbations
Spacecraft Maneuvering
Interactive exercises and evaluations

Advanced Space Concepts

Expert Course | 4 Lessons | Graded

Built for engineers and analysts performing real mission planning and operational analysis.

Topics Covered

Ground tracks
Launch analysis
Ground tasking
Rendezvous planning
Proximity operations

Available Courses on the STK

STK Essentials

Core Course | 3 Lessons | STK Certified

The foundational STK course designed to build confidence and proficiency with the industry's leading mission engineering software.

Topics Covered

STK interface and workflow
Object creation and management
Reports and graphs
Access calculations
Air and space analysis fundamentals

Certification: STK L1 Certification.

STK for Air

Advanced Course | 3 Lessons | STK Master Certified

Learn how STK is used to model and analyze aviation operations.

Topics Covered

Aircraft mission planning
Sensor modeling
Radar analysis
RF interference
Missile analysis
Aviator flight performance
Formation flying and aerial refueling

Certification: STK L2 Master Certification for Air (Coming Soon...)

STK for Space

Advanced Course | 5 Lessons | STK Master Certified

Advanced training focused on satellite operations, mission planning, and space analysis.

Topics Covered

LEO, MEO, and GEO mission analysis
Satellite databases
Connect commands
Advanced visualization
Space-focused premium capabilities

Certification: STK L2 Master Certification for Space.

Available Courses on the STK

ODTK Essentials

Specialized Course | 5 Lessons | ODTK Certified

The definitive introduction to orbit determination and operational flight dynamics.

Topics Covered

Orbit determination fundamentals
Initial Orbit Determination (IOD)
Batch Least Squares
Extended Kalman Filter
Smoother processing
Maneuver estimation
Operational OD workflows

Certification: ODTK Essentials Certification.

Recommended Learning Paths

New to Space User

Intro to Space → STK Essentials → STK for Space

Air Domain Analyst

STK Essentials → STK for Air

Space Domain Analyst

STK Essentials → STK for Space → Advanced Space

Orbit Determination Analyst

ODTK Essentials

Enterprise Training

LaunchPad helps organizations standardize training, accelerate onboarding, and measure workforce proficiency across teams.

Benefits for Organizations

Faster onboarding of new personnel
Consistent training across teams
Certification tracking and reporting
Reduced training costs
Self-paced learning for distributed organizations
Custom training content available
Expert-led training options available

Ready to Launch?

Request Access, Schedule a Demo, or Learn More please contact support@blacknightspace.com

Python with STK: 03 Computing Access

Drew Latta — Tue, 02 Jun 2026 14:55:13 GMT

STK-Python Compute Access

STK has various tools that can be integrated for automation and streamlining mission planning processes. Python is one of these tools. Python can be used with built-in STK tools to calculate the access a sensor has over a given area during a specified period. This tutorial works with either the STK-Python Basic Aircraft or STK-Python Basic Satellite training.

Resources

STK 12.8 or newer
STK Python API
Python Capable Code Editor (ex-PyCharm Community Edition)

Creating the Coverage Definition Tool and Figure of Merit

First, we must create and define a Coverage Definition Object. If you are attempting to compute access for the satellite, use the following code to create a Global Coverage Definition:

coverage = scenario.Children.New(AgESTKObjectType.eCoverageDefinition, 'GlobalCov')

coverage.Grid.BoundsType = AgECvBounds.eBoundsGlobal

covGrid = coverage.Grid

Res = covGrid.Resolution

Res.LatLon = 6 # deg

Or, if you are attempting to compute access for the aircraft, use the following code. First, we must define the target region:

areaTarget = root.CurrentScenario.Children.New(AgESTKObjectType.eAreaTarget, 'TargetRegion')

root.BeginUpdate()

areaTarget.AreaType = AgEAreaType.ePattern

patterns = areaTarget.AreaTypeData

patterns.Add(37.26134, 116.63154)

patterns.Add(34.26336, 116.63154)

patterns.Add(34.26336, 121.71344)

patterns.Add(37.26134, 121.71344)

root.EndUpdate()

areaTarget.AutoCentroid = True

Then we create the Coverage Definition Object for the aircraft scenario:

coverage = scenario.Children.New(AgESTKObjectType.eCoverageDefinition, 'RegionCov')

coverage.Grid.BoundsType = AgECvBounds.eBoundsCustomRegions

covGrid = coverage.Grid

bounds = covGrid.Bounds

bounds.AreaTargets.Add('AreaTarget/TargetRegion')

Res = covGrid.Resolution

Res.LatLon = .5 # deg

After that, we must create and define our Figure of Merit. This will be the same for either scenario:

fom = coverage.Children.New(AgESTKObjectType.eFigureOfMerit, 'SimpleCoverage')

fom.SetDefinitionType(AgEFmDefinitionType.eFmSimpleCoverage)

Assigning the Sensor as an Access Tool

We will then use Connect commands to assign our Sensor as an access tool for the Coverage Definition Object. In the case of the Satellite, input the following:

root.ExecuteCommand("Cov */CoverageDefinition/GlobalCov Asset */Satellite/ClimateWatch/Sensor/Monitor Assign")

root.ExecuteCommand("Cov */CoverageDefinition/GlobalCov Asset */Satellite/ClimateWatch/Sensor/Monitor Activate")

In the case of the Aircraft, input the following:

root.ExecuteCommand("Cov */CoverageDefinition/RegionCov Asset */Aircraft/UAV/Sensor/Monitor Assign")

root.ExecuteCommand("Cov */CoverageDefinition/RegionCov Asset */Aircraft/UAV/Sensor/Monitor Activate")

Computing Access and Displaying Data

Next, we will compute access with the following code:

coverage.ComputeAccesses()

Finally, we will generate a report that shows the Percent Satisfied of the Coverage Region over the time interval:

root.ExecuteCommand("ReportCreate */CoverageDefinition/GlobalCov/FigureOfMerit/SimpleCoverage Style \"Percent Satisfied\" Type Display")

Note that you’ll have to change the name of the Coverage Definition Object to RegionCov for the aircraft scenario.

Next Steps

With a running instance of STK, you can run this code from your preferred Python code editor to Compute Access and generate a Percent Satisfied Report for either the Aircraft or Satellite Scenarios we created earlier. These parameters can be expanded, and the type of graph can be adjust to gather the data that you need for your mission.

If you have any further questions or need assistance, we are here to help! Our dedicated Tec-Support team is ready to provide prompt and personalized assistance tailored to your needs.

Thanks,

Blacknight Space Team

Getting Started: STK Connect Commands

Drew Latta — Fri, 29 May 2026 18:50:23 GMT

Why should I learn about Connect Commands?

When it comes to automating tasks in STK, Connect Commands stand out as an invaluable tool available to any STK Rocket Scientist! Whether you're conducting access reports for thousands of satellites with your ground sensor or loading satellites with updated databases daily using specific search filters, automation streamlines these processes. With tasks often becoming repetitive, STK Connect Commands offer the initial, straightforward step to mastering automation within STK. Moreover, the reasons for automating or integrating STK are numerous and diverse, ranging from needing specific calculation parameters like the cross-sectional area of a tumbling spacecraft to optimizing data collection schedules for ground stations. STK's rich API set enables the use of its powerful analytical engine within custom projects, facilitating tasks such as designing guidance laws for interceptor systems and conducting real-time and post-processing analysis.

STK Connect Commands represent the first step towards learning automation in STK. Indeed, even if you will use STK Object Model API, you will be able to execute Connect Commands with your script. In fact, most of the new STK features that come with the newest versions are often first implemented within Connect Commands before having their own Object Model definitions.

How can I get started with Connect commands directly in STK?

A great way to learn connect commands and test them is to use them directly inside of STK, without any implementation of any sort. You can use a simple tool called the HTML viewer in order to type in Connect command and execute them inside of your STK running instance. If you are a beginner with Connect command, this is a great way to understand their syntax and get familiar with how they affect your STK session.

Where can I find the Connect Commands Library?

The Connect Commands Library can be found in the STK Help at this address.

The library can be viewed in different ways. You can search for Connect Commands with different filters, which the most important are:

Alphabetical Listing of Connect Commands: The Alphabetical listing includes all Connect commands, regardless of their groupings.
Object Tools: Object tools manipulate and display data related to individual objects separately from their properties. They include functions like calculating access between objects, creating reports and graphs, determining vehicle or sensor swath, and generating a Walker constellation.
Application Options: There are several Connect commands available to control application options.
Astrogator related Connect Commands: Astrogator's Connect relationship diverges from other STK objects. This page covers the general structure and syntax of Astrogator Connect commands, while detailed commands and attributes are found in the table of contents of this help section.
Aviator related Connect Commands: Configure all procedures, calculate any changes made to the aircraft object, or implement all changes across STK.
2D Graphics Window Commands: Connect commands are available to control the display of objects and the view in the 2D Graphics window.
2D Object Graphics Commands: Commands that allow you to control the 2D Graphics properties of an object.
3D Visualization Window Commands: Commands that enable you to configure and operate the 3D visualization window.
STK Desktop Only Commands: Commands available only when running STK Desktop.
Added or changed commands: Commands changes that come with each new version of STK.

What is a Connect Command typical synthax?

Single commands sent to Connect use the following format:

<CommandName> <ObjectPath> [<CommandData>]

Where:

<CommandName>: is the name of a particular command (e.g., Load).
<ObjectPath>: The STK instance (e.g., Scenario/stkDemo/Satellite/Shuttle) to which the <CommandName> directs action.
[<CommandData>] <CommandData> fields modify a <CommandName> and may or may not be required. Please refer to the format of the individual commands for additional information.

Important Notes:

Although the <CommandName> field isn't case sensitive, the <ObjectPath> is. <CommandData> may or may not be case sensitive.
Multiple commands can be sent to Connect in one transaction by separating them with semicolons (;).
<CommandData> fields modify a <CommandName> and may or may not be required. Please refer to the format of the individual commands for additional information.

You can find more information about Connect Commands Syntax here.

Connect Wildcard

In complex projects, initial stages often involve experimentation, where the first part is built without full details for subsequent phases. Sometimes, significant changes lead to a crossroads: starting anew or revising existing work. This dilemma is common when constructing scenarios in STK.

A common example to such situation would be this one: you developed a scenario with a large satellite constellation, each with an onboard sensor initially set with default properties due to unknown specifications. As details emerged, you sought to edit sensor properties efficiently. While manually editing each sensor via the Properties Browser seemed tedious, it wasn't the sole option. STK offers various methods to modify groups of objects efficiently. Among them:

Multi-select:
- With this method you can select multiple objects in the Object Browser and open the Properties Browser to edit properties for all the selected objects at once. In some cases, you can simultaneously edit some, but not all, properties on a given properties page. In this case, the customer wanted to make all the sensors targeted at a facility object. Unfortunately, adding objects to the Assigned Targets list was not available.
Copy and paste:
- With this approach, you create one version of the object as you want it, then use the copy and paste functions within the Object Browser to add duplicates of the object to the scenario. When pasting, the object’s name will be appended with an incrementing number. This approach could have worked for the customer, but would have required removing the old sensors and then renaming all the new sensors as they were inserted.
Wildcard Connect:
- Although you do may not have strong programming background, the ideal solution in such cases is using automation and therefore using Connect. The wildcard character (*) can be used in Connect Commands.
- With the wildcard, you can apply a single Connect command to a group of objects in a scenario by pattern matching against their names. You can, for example, apply the command to all satellites that begin with "GPS", or you can apply it to all facilities, or to all sensors attached to all satellites.

How to use the Connect wildcard

The wildcard character (*) can be used in an <InstanceName> in a Connect <ObjectPath>. The wildcard can only be used in the <ObjectPath> for which the command is being sent, it can not be used in an <ObjectPath> (or <TruncatedPath>) that is one of the command parameters, except where explicitly stated in a command's documentation.

The wildcard character can not be used in any <ObjectClass> name.

If the wildcard is used in a command returns data, the returned data for each object represented by the path, will be separated with a keyword, MDATA@DataLength@, where DataLength is the number of characters in the returned data for that object.

The wildcard should not be used with commands that write to a file. Only one file will be written and it will contain the data for the last path found.

When a command is entered using a wildcard in the <ObjectPath>, the path is expanded into all possible instances and the command is called for each instance. If any of the commands Nack, then a Nack will be returned, even though some commands may have completed successfully. To have the command ignore Nacks and continue processing use the ConControl / WildcardIgnoreNacksOn command.

Some examples follow:

*/Satellite/GPS*

The command with this path will affect all Satellites whose name begins with "GPS".

Scenario/stkDemo/Satellite/espSat/Sensor/*Test

The command with this path will affect all Sensors, on the Satellite espSat, whose name ends with "Test"

Scenario/stkDemo/Satellite/Sat*/Sensor/*

The command with this path will affect all Sensors on all Satellites whose name begins with "Sat".

*/Satellite/*/Sensor/*

The command with this path will affect all Sensors on all Satellites.

Chains */Constellation/ConstObj Add Place/*

The command adds all Place objects in the scenario to a Constellation object.

Chains */Constellation/ConstObj Add Place/*/Transmitter/*

The command adds all Transmitters on a Place object to a Constellation.

Connect Command Example

A simple connect command example for creating a new satellite on the current opened scenario's central body would be:

New / */Satellite MySatellite

Let's dig in this example and understand the structure behind this command.

The structure of a Connect Command is : <CommandName> <ObjectPath> [<CommandData>].

So our command name is New. If we look in the Alphabetical Listing of Connect Commands we will find that the command called "New" creates a new scenario or add a new object to the current scenario, and it will give us the following syntax rule:

New <ApplicationPath> <ClassPath> <NewObjectName> {NewOptions}

In our command, the <ApplicationPath> is the path to the instance of the current Application. The format for this is /Application/<AppName>where <AppName> is the Application name, e.g. STK, ODTK, etc...
- Since only one Application can be opened at a time, our <ApplicationPath> can be abbreviated by /.
<ClassPath> specifies the full class path of the object to be created.
- For instance, to add the satellite to the current scenario, the <ClassPath> is: */Satellite. We are using a wildcard because we don't need to specify the full path that resides behind the Satellite Class. It is a useful shortcut.
<NewObjectName> is simply the name of your Object.
- MySatellite
{NewOptions} is an optional argument and its possible argument differs for each type of Connect Command. The New Connect Command has three possible {NewOptions}:
- NoDefault: If specified, the object is created using hard coded defaults and does not load the object default file.
- Ignore: If specified, duplicates will be discarded without generating errors.
- CentralBody <CBName>: Create the new object on the specified Central Body. Using this option will set the default Central Body used for subsequent New commands.
- For example, Earth is the default central body for an object. If you wanted to specify that your new facility has to be located on Mars while not loading the default object file, you would use the following command:
  - New / */Facility MyFacility CentralBody Mars NoDefault

You can easily find any information for a specific command and its parameters, syntax and special options in the Connect Command Library. Links displayed earlier in this article can lead you to the part of the library that you are most interested in. Each command listed in the library has a large description and explanation on the use of the command, as well as example commands.

How can I test commands directly in STK with the STK Web Browser?

STK has an embedded tool present natively called the Web Browser. It can help you to in turn open a natively present GUI that interacts with your current STK scenario and send and test Connect Commands through it.

In order to open the Web Browser, please select the View tab, and in the dropdown menu select Web Browser:

Once you click on the Web Browser, you should have a new window open with a search bar at the top and the web address of AGI Support loaded in. Near this search bar, you should be able to see a Folder Icon. Click on it:

Once you click on the Folder Icon, your File Explorer will be opened to select which file you want to open with the Web Browser. Make sure you are in the STK Branch (1), then click on the Example HTML Utilities folder (2) and double-click on the STK Automation folder (3):

Then select the Send a Connect Command folder:

Finally, double-click on the .htm file to open it in the STK Web Browser:

Here is the interface that should now be available inside of your STK Window:

Let's try our satellite example command!

You can now notice the new object in your component browser, but our satellite is not propagated so it is not visible in 3D yet. It just exists as a satellite object:

Let's use a more complicated command called "SetState" with the SGP4 propagator which you can find at this address.

Here, we will propagate our specific MySatellite satellite object (<SatObjectPath> is */Satellite/MySatellite) using the SGP4 propagator for the whole scenario duration interval (UseScenarioInterval {TimeInterval} argument of which you can find documentation on this page under the DATE/TIME OPTIONS title). We will use a 60 seconds <StepSize> parameter, and the NORAD number of the ISS (25544) for the <SSCNumber> parameter. Our TLESource parameter will be defined with the option Automatic. Which means it will be directly sourced from the default way, in our case, AGI Online Servers:

Example Connect Commands: ISS Ground Track Scenario

Here is a quick example of connect commands that actually builds the following items:
- ISS-like orbit: 420 km, 51.6° inclination (matches the real ISS)
- 3 ground stations at KSC, Baikonur, and Kourou/Guiana — the three primary ISS crew transport launch sites
- Each station has a wide-cone sensor (85° half-angle ≈ 5° elevation cutoff) auto-pointed at ISS
- Access windows computed for all 3 sites over 24 hours
- Access timing reports pop up for each station

# ── 1. CREATE SCENARIO ────────────────────────────────────────────────────
New / Scenario ISS_Tracker
SetAnalysisTimePeriod * "Today" "+24 hours"
Animate * Reset

# ── 2. ISS-LIKE LOW EARTH ORBIT ───────────────────────────────────────────
New / */Satellite ISS
OrbitWizard */Satellite/ISS Circular Inclination 51.6 Altitude 420000 RAAN 0
Graphics */Satellite/ISS Show On
VO */Satellite/ISS Pass3D OrbitLead OnePass OrbitTrail Full

# ── 3. GROUND STATIONS ────────────────────────────────────────────────────
New / */Facility KSC
SetPosition */Facility/KSC Geodetic 28.573 -80.649 0.0

New / */Facility Baikonur
SetPosition */Facility/Baikonur Geodetic 45.92 63.34 0.0

New / */Facility Guiana
SetPosition */Facility/Guiana Geodetic 5.236 -52.769 0.0

# ── 4. TRACKING SENSORS (5° elevation mask = 85° half-angle) ──────────────
New / */Facility/KSC/Sensor KSC_Tracker
Define */Facility/KSC/Sensor/KSC_Tracker SimpleCone 85.0
Point */Facility/KSC/Sensor/KSC_Tracker Targeted Tracking Satellite/ISS

New / */Facility/Baikonur/Sensor Baikonur_Tracker
Define */Facility/Baikonur/Sensor/Baikonur_Tracker SimpleCone 85.0
Point */Facility/Baikonur/Sensor/Baikonur_Tracker Targeted Tracking Satellite/ISS

New / */Facility/Guiana/Sensor Guiana_Tracker
Define */Facility/Guiana/Sensor/Guiana_Tracker SimpleCone 85.0
Point */Facility/Guiana/Sensor/Guiana_Tracker Targeted Tracking Satellite/ISS

# ── 5. COMPUTE ACCESS ─────────────────────────────────────────────────────
Access */Facility/KSC/Sensor/KSC_Tracker */Satellite/ISS
Access */Facility/Baikonur/Sensor/Baikonur_Tracker */Satellite/ISS
Access */Facility/Guiana/Sensor/Guiana_Tracker */Satellite/ISS

# ── 6. GENERATE REPORTS ───────────────────────────────────────────────────
ReportCreate */Facility/KSC/Sensor/KSC_Tracker Type Display Style "Access" AccessObject */Satellite/ISS
ReportCreate */Facility/Baikonur/Sensor/Baikonur_Tracker Type Display Style "Access" AccessObject */Satellite/ISS
ReportCreate */Facility/Guiana/Sensor/Guiana_Tracker Type Display Style "Access" AccessObject */Satellite/ISS

Conclusion

With the knowledge of Connect Commands at your disposal, you're ready to embark on experimentation within the STK GUI! Delve into the STK Connect Command Library, exploring new commands and honing your syntax skills. Additionally, leverage the HTML Utility as a straightforward automation tool for various STK tasks, from access calculations to EOIR. As you become proficient with Connect Commands, consider advancing to the Object Model API to develop more intricate automation scripts using languages like Python, C++, C#, Java, Visual Basic, Matlab, and beyond. Your journey into STK automation is just beginning!

Useful Links

Thanks,

Blacknight Space Team

SOLIS: Target Orbiting Objects

Drew Latta — Fri, 29 May 2026 18:50:22 GMT

SOLIS can add fidelity to mission models by providing realistic satellite attitude profiles and maneuvers. With SOLIS, it is possible to model camera and antenna pointing and slews between ground targets, planes and other satellites. When SOLIS runs in STK, all of its behaviors are running on fully functional flight software, which is fed simulated sensor data and outputs simulated actuator commands, with SOLIS's Onboard Dynamic Simulation System (ODySSy) being used to close the loop between actuator behavior and sensor input. To learn more about SOLIS on ASI's website, click here.

In order to accurately point, MAX - the flight software running inside SOLIS - must have an accurate understanding of its own position. This is a challenge discussed in our SOLIS Ephemeris Management article. In real-world operation, MAX must propagate its own orbit to understand its position in space. MAX can define four different types of targets, with the Ballistic target type making it possible to model and track the relative position between two orbiting satellites.

The Slew Limits & Targets subtab of the Mode Controller page of SOLIS is used to define targets. Modes are then used to define the target type and the pointing/alignment vector. For example, the default TargetTrack mode (mode #9 on the Modes subtab) is configured to slew the satellite's [0, 0, 1] alignment vector to point in the direction of the SpotTarget target type.

The Target Types:

First, we will briefly discuss all four target definitions, then discuss how to use the Ballistic Target to point at another satellite. For more information on the target definitions, click here.

1: Spot Target

Used for stationary ground targets, this target definition uses a target's latitude, longitude and altitude on the central body the satellite is orbiting to generate a pointing vector from the satellite's position to the target position for slews. When the A Spot Target definition comes prebuilt in any SOLIS scenario for use in the Target Planner, a useful tool covered in the introductory SOLIS Tutorial.

2: Scan Path

Used for targeting swaths of the ground, this target definition is like the Spot, but allows the satellite to sweep from one point on the earth to another, rather than targeting a stationary point.

3: Scheduled Path

For targeting planes, ships and other earth-based moving objects, this target type allows the satellite to track a moving object on or above the surface of the earth.

4: Ballistic

To target other satellites that are moving relative to your own satellite, MAX uses the Ballistic target definition. To point at an orbiting satellite, MAX must predict its path by propagating its orbit. The Ballistic target definition takes the initial state, or ephemeris, of a target satellite and propagates it the same way it propagates its own orbit. MAX uses a relatively simple propagator, so for tracking over a long period of time, or for tracking a maneuvering target, this ephemeris may need to be updated with a new entry to maintain pointing accuracy. It is also possible to add ephemeris tables for these ballistic targets to ensure accurate tracking if the target satellite is maneuvering or being tracked over a long period of time.

How to Use the Ballistic Target Definition to Track a Satellite:

Note: This tutorial assumes a working knowledge of STK and will require an understanding of the STK GUI to follow along. New STK Users may consider taking the Level 1 STK Certification Training to familiarize themselves with STK.

Configuring Ballistic Targeting:

To illustrate ballistic tracking, we used the Insert STK Objects tool to create a satellite in STK and named it "Target." The orbital parameters of the target satellite are arbitrary; MAX can track any object that is orbiting the same central body as itself.

If your scenario does not already have a SOLIS-modeled satellite, one can be created now with the Insert STK Objects tool. For this tutorial, we use the SOLIS default configuration, adding a sensor object to the STK satellite object to demonstrate pointing. We used a default conic sensor, left the default sensor pointing in the +Z direction, and narrowed the cone half angle to two degrees.

In order to propagate the orbit of the Target satellite, MAX will need to know the target's ephemeris in the CBI reference frame. For any STK satellite, this can be obtained with the report and graph manager. Right click the Target satellite in the object browser on the left and select the Report and Graph Manager. In the installed styles, select the "Inertial Position Velocity" report type.

Generate the "Inertial Position Velocity" report. This report provides the position and velocity of the Target satellite in the CBI frame. For one of the data points, take note of the time value, the position values, and the velocity values. For longer SOLIS scenarios, or targets that are maneuvering, users can choose a point in time that is nearer to the time of target tracking. In this demonstration, we simply record the first data point.

To open the SOLIS_Sat's SOLIS page, right click SOLIS_Sat in the object browser on the left and select SOLIS from the drop-down menu. Navigate to the Mode Controller page, then the Slew Limits & Targets page, and add a new ballistic target definition by clicking the green plus button below the slew and target definitions. This ballistic target will give MAX the Target satellite's initial state so that MAX can propagate the orbit and predict Target's position moving forward.

To configure the target definition to track the Target satellite, set the following values:

Name: BallisticTarget

Type: Ballistic

Epoch (UTC): The time noted from the Inertial Position Velocity report of the Target satellite.

Position (CBI): The position noted from the Inertial Position and Velocity report of the Target satellite.

Velocity (CBI): The velocity noted from the Inertial Position and Velocity report for the Target satellite.

Based on the Inertial Position Velocity report generated in our scenario, we had the following values:

Now that we have defined the target, we will define a targeting mode that references this ballistic target. For this demo we will copy the TargetTrack mode and modify it into a ballistic track. This mode was copied for convenience as its alignment vector is oriented in the same direction as the SOLIS satellite's camera. If your sensor points in a different direction, simply configure the Body Align: vector to the direction of the sensor. Select the TargetTrack mode and click the copy button at the top of the page.

This will create a new mode called "TargetTrack_Copy". Rename this mode to "BallisticTrackMode", and then at the bottom, set Align Target: to "BallisticTarget." When activated, this mode will point the satellite's Body Align: vector toward the Target satellite.

To demonstrate this new ballistic tracking mode, we will now go to the Mission Sequence Definition page, open the Sequence Editor and add a new target sequence by clicking the green plus button. Save this sequence with the name "TrackTarget."

Next, click the green plus button near the top of the page next to Spacecraft Command and add a single command to the mission sequence: "SlewTo Tracking" (located in Mode Control). Change the TRACKMODE option to BallisticTrackMode - the mode created in the previous steps - and save the sequence.

Last, test the ballistic tracking sequence! Go to the Sequence Selection subtab, select the TrackTarget sequence you just created, add it to the execution list, and click Accept All Changes at the top. Now, when SOLIS is run, MAX will run the sequence just created. Run the SOLIS scenario by clicking the green button at the top left.

When running SOLIS, users should see their satellite tracking the Target! You can add as many tracking targets as you would like by creating new modes, or updating the ephemeris to that of a different satellite while MAX is running via direct commanding (EPH_ADD_BALLISTICTGT_ENTRY). Note that for longer scenarios, the target's ephemeris may need to be updated to maintain accurate tracking.

You now know how to configure ballistic tracking in SOLIS! Ballistic tracking sequences can be used to simulate imaging of a target satellite, data downlink to a GEO relay satellite, or any other ballistic tracking in STK. In the Sequence Selection page, add and reorder as many sequences as desired to simulate a full satellite mission, slewing back and forth between communication relays, sun pointing, ground stations and more. There is a great deal of additional configuration and customization that can be done in SOLIS, and fully configuring the satellite in SOLIS will add fidelity to a mission model. We recommend following the SOLIS introductory tutorial available here, which provides a full walkthrough of satellite SOLIS configuration. Users can also explore the example SOLIS scenarios that come pre-built with the SOLIS install to see what kind of modeling is possible in SOLIS.

If you have any further questions or need assistance, we are here to help! Our dedicated Tec-Support team is ready to provide prompt and personalized assistance tailored to your needs.

Thanks,

Blacknight Space Team

Network License Setup

Drew Latta — Fri, 29 May 2026 18:50:21 GMT

Introduction

If your organization uses ANSYS products across multiple workstations, a network (floating/concurrent) license setup is often the most efficient way to get maximum value. This blog explains how to configure the ANSYS License Manager to serve licenses over your internal network, so client machines can check out licenses from the server, share them, and you avoid “one-machine per license” lockdown.

Note: While we'll guide you through the License Manager Setup, it's not within our scope to configure your VPN, firewall rules, subnets or LAN connectivity. These are network-infrastructure tasks that your IT or network provider must handle. Without proper internal connectivity between clients and license server, the network licensing model cannot function.

Step-by-Step Guide: Setting Up a Network License Server

1. Choose and prepare your license server machine

Select a dedicated machine (Windows or Linux) that will host the License Manager.
Ensure it has a fixed hostname or IP address that client machines will reference.
Make sure you have administrator (Windows) or root (Linux) access.
Ensure the server has access to the license file once generated and can host the licensing service. The license files format are *.lic. If you have not received a license and you have active entitlements, you can follow step 3.

2. Download & install the ANSYS License Manager

On the server, download the “ANSYS License Manager” installer from the ANSYS Customer Portal / licensing site customer.ansys.com or at www.agi.com/download
On Windows: Run the Setup, follow installation wizard.
- Ansys Windows Install Guide
On Linux: Extract the installer, run ./INSTALL, or for silent install use -silent -LM etc.
- Ansys Linux Install Guide
After installation, you’ll have the License Management Center UI (web interface) to manage the license manager. Ansys License Management Guide

3. (If you have a License, skip this) Generate the license file

Log into your ANSYS Licensing Portal and activate the entitlement for your HostID (server’s MAC address or Disk Serial) to generate the license file. Ansys Optics
Download the resulting license file (.lic or similar).
In the License Management Center on your server choose “Add a license file” and install it.

4. Configure the License Manager for shared access (network)

Within the License Manager, configure static ports or ensure the default port is open (1055 for ANSYS FlexNet) so clients can connect.
Ensure the server is set to “shared access” so that licenses may be checked out by multiple client machines.
If you plan redundancy, triad servers or fallback, you can configure multiple servers in client settings.

5. Configure network / firewall / client access

Ensure client systems can reliably communicate with the license server—whether through proper firewall configuration, VPN, or routed network setup—so they can resolve the server and access the required license ports (e.g., TCP 1055).
To verify, a simple test is a good first check to confirm network connectivity between the client and the license server. Here’s a simple verification step you can include:From the client machine, open a PowerShell and run:Windows PowerShell:Test-NetConnection <ServerName or IP> -Port 1055
If that command returns TcpTestSucceeded : True, then the client can reach the license service itself.

As noted above: support cannot configure your network infrastructure (VPN, firewall, LAN segmentation) — that is up to your network provider/IT team.

6. Configure client machines

On each client workstation, launch the ANSYS Client Licensing Settings utility (or equivalent) and:
- Enable Client Licensing.
- Enter the port and hostname of the license server (e.g., 1055 and licenseserver.domain.com ).
- Click “Test” to verify connectivity. (Green check is present to verify the connection)
- Save settings and start STK/ODTK products.
If you have multiple license servers/fallback, you can list more than one in client settings.

7. Verify license server status & usage

On the license server, open the License Management Center → Diagnostics → “Display FlexNet License Status” to view current checked-out features.
Verify that clients can open ANSYS products and check out licenses.
Monitor usage and ensure license availability meets your concurrency needs.

Useful Resources & Official Documentation

ANSYS License Manager installation guide (Windows) — [Installation guide Windows] Ansys Optics
ANSYS License Manager installation guide (Linux) — [Installation guide Linux] Ansys Optics
Configuring the license manager for shared access – [Shared access article] Ansys Optics
Client licensing settings utility – [Client settings guide] Ansys Optics+1
FlexNet licensing overview & system requirements – [FlexNet overview] SimuTech
ANSYS licensing portal & resources – [Licensing resources] Ansys

Why a License Server Needs More Than "Internet Connected"

A machine simply being connected to the Internet does not guarantee it can act as a network license server. The client workstations must be able to directly reach the server machine (by hostname or IP) on the correct port(s). Ansys Optics+3SimuTech+3Ansys Optics+3
The product manager (FlexNet/ANSYS) checks out licenses from the server and expects network-visibility—not just “internet access.” SimuTech
Therefore, you must ensure internal connectivity (same LAN or routed subnet/VPN) and open relevant ports. External support (e.g., cloud/Internet only) may not suffice unless configured as a dedicated network license cloud service.

Frequently Asked Questions (FAQs)

Q: Can client machines just connect via the Internet to the license server?

A: No — simply being Internet-connected is not enough. The client must be able to reach the server on the internal network (or VPN) with the correct port and hostname. Without that internal network visibility, the license checkout will fail.

Q: What is the default port number for ANSYS License Manager?

A: The default port is 1055 for the ANSYS license server vendor daemon. If you did not change it during setup, use 1055. Ansys Optics+1

Q: What if I don’t want a license server — can I license each workstation individually?

A: Yes — ANSYS supports node-locked or individual licenses for single machines. But in that case, each workstation uses its own license and you lose the benefit of sharing and concurrency.

Q: Can the license server run in the cloud or on remote machines?

A: Yes, technically it can. But you must ensure network connectivity (routing/firewall/VPN) so that client machines can reliably reach the server. Also performance and licensing policies may apply. For many organisations, staying on the internal LAN is simpler.

Q: Who sets up the VPN/firewall/subnet so clients can see the server?

A: That falls under your organization’s network/IT administration. External support (like software vendor support) will not set up your VPN, firewall rules or LAN segmentation. Make sure your network infrastructure is configured appropriately.

Q: How many concurrent users can I have?

A: That depends on how many licenses (increments) you purchased and how you configured the license file. On the server you can monitor how many are checked out and adjust your policy.

Q: What happens if the license server goes down?

A: Client workstations will not be able to check out new licenses. Some clients support borrowing licenses temporarily (where allowed) to minimize the risk of downtime. Other use a backup server to maintain 100% availability. The license server does not need to be a powerful machine but needs to have minimal downtime to maintain license availability.

Q: Can I restrict which users or machines can use certain features?

A: Yes — using an 'options file' you can define INCLUDE/EXCLUDE rules, reserve licenses, limit borrow hours, etc. Ansys Optics

Final Note

Setting up a network license server for ANSYS software is a powerful way to maximize usage and share resources. It requires coordinated efforts between your licensing/team, server setup, client configuration and your internal network infrastructure. Remember: While this guide covers the License Manager setup and client configuration, you must involve your network/IT team to ensure firewall rules, VPN/subnet connectivity and hostname resolution are in place — without that, the shared license model will not work.

If you follow the steps above, verify connectivity and monitor usage, you should be ready to deploy network licensing with confidence.

How to Request a License

Drew Latta — Fri, 29 May 2026 18:50:21 GMT

Here is an overview of how to get a license and the subsequent installs. If you have any questions not answered by this document, please do not hesitate to submit a support ticket to Blacknight support.

Export Control process
Understanding License Types
Submit Licensing Information to Blacknight
Sending of Product Installs and Product Licenses

Export Control: Blacknight Technology and Partner Technology is export controlled by the US Government. In order to be given access to our technology, we must know about your company/organization, we must understand your needs and your potential usage of the technology, among other items as request. Blacknight can help determine what type of export control licenses are required for you to access our technology. Due to complexity with certain Export Control groups, please allow time for the team to analyze your requests. Once the export control process is complete, we can continue with the process of getting you access to our technology.

Understanding License Types: There are many different types and durations of the licenses. The sales team can provide more information about the license structure and offer a license solution that best suits your needs.

Blacknight can provide different time constraints on the licenses. Blacknight offers Permanent/ “Paid-Up” licenses which allow these premium products to be used forever at the current version. To maintain the latest version and technical support, annual Software Maintenance is required. We also offer Lease licenses which allow the products to be used for a limited period of time while using the latest version. Lease licenses have a duration of 1 year usually. We also offer evaluations licenses for prospective customers, in order to trial the software, usually lasting for 15 to 30 days.

Blacknight offers different types of licenses from Networked Licenses, Node-locked License, to Web Licensing.

Node-locked licenses are product licenses that are tied/locked to an individual workstation. There are different ways to add these licenses to a workstation, but all require information about the workstation from the user.

Network licenses are licenses hosted by a license server. These licenses are tied/locked to an individual server, but the licenses can be hosted to anyone on that same network. Users who have access to the license server can get a license for the technology on their workstation. Network Licenses require the License Management Center to be installed on a server. The client users can set their local Licensing Client Setting application to point the license server. The License Server can also be installed locally to serve the licenses only to the current machine, acting as a Server and Client.

Ansys Web Licensing is a cloud-hosted licensing solution that allows users to access Ansys software without a local license server. Licenses are assigned through the Ansys Licensing Portal and authenticated using the user's Ansys account, simplifying deployment and license management. To request access, the Blacknight team will assign licenses to your Ansys Account and assign the Ansys products you need access to. Once approved, your account will be assigned the appropriate web license entitlements and you'll receive instructions to sign in and activate access. This is only available for Ansys Products.

Company Name	Available Products	Available License Types
Ansys	STK/Pro, STK/Premium-Space, STK/Premium-Air, STK/Enterprise, ODTK, ODSSA STK/Scheduler, STK/SOLIS ModelCenter	Network, Web, and Node-locked (Equivalent)*
COMSPOC	SEG, SOTA	Node-locked
Blacknight Space	LaunchPad, OrbitLens	Node-locked**

*Ansys products are provided as network licenses and web-licensing. To make a node-locked equivalent license, the Ansys License Management Center can be installed locally to serve the Ansys licenses only to the current machine, acting as a Server and Client which essentially is a Node-locked license.

**Blacknight products are provided as Node-locked licenses. However, other flexible licensing approaches are possible, please ask our team for more information.

Submitting License Information to Blacknight: In order to receive a license for any of our products, please provide the necessary information to make the licensing process quick and efficient.

For Ansys Web License, Blacknight can perform all necessary actions. Simply submit the request through your Account Manager.

For Ansys Network Licenses, Blacknight requires the running the following instructions on the Server that will be hosting the licenses.

On the target machine (license server machine), open Command Prompt (cmd.exe) and run the following commands.
- vol
- hostname
Record and Send the information to Blacknight support.
- Server Disk ID (or Volume Serial Number)
- Host Name (Server Name).
Note: If Host Name is sensitive, ChangeMe123 is acceptable as the license file can be modified directly in a notepad. Disk Serial ID is required, the Disk Serial ID cannot be modified.

For Blacknight Licenses, Blacknight requires the running the following instructions on the User's Machine.

On the target machine (user machines), open Command Prompt (cmd.exe) and run the following commands separately.
- vol
Record and Send the information to Blacknight support.
- Disk ID Number

For SEG and SOTA Licenses, Blacknight requires the running the following instructions on the User's Machine.

On the target machine (user machines), open Windows PowerShell application.
In PowerShell, send the following command to get UUID.
- Get-CimInstance -ClassName Win32_ComputerSystemProduct | Select-Object UUID

Record and Send the information to Blacknight support.
- UUID (is only for SEG and SOTA)

Product Install Instructions and Licenses Sent:

Once the licenses have been generated and approved. The install instructions will be sent. Please follow the instructions received.

Note: Product Licenses and Installs might come from Blacknight, AGI or COMSPOC depending on the Export Control procedures. Blacknight will do our best to make the license and install process as seamless as possible.

Please let us know what we can do to expedite the process for you.

STK Pro, Premium & Enterprise

Drew Latta — Fri, 29 May 2026 18:50:20 GMT

Legacy Product Mapping: in STK 12.3, Ansys bundled the STK capabilities into four products with 3 additional specialized modules. These new products include STK Pro, STK Premium Space/Air and STK Enterprise. Here is the mapping from the legacy license names to current license bundles.

STK Systems Tool Kit Family

The STK product line is structured in tiers, with each tier including the capabilities of the tiers below it.

STK Pro (Baseline)

STK Pro provides the core modeling, visualization, and analysis environment used for aerospace, defense, and space mission engineering.

Visualization

Advanced 2D and 3D visualization

Modeling

Customizable and interoperable models
- Sensors
- Communications
- Radar Systems
- Optical Sensors

Analysis

Line of Sight
Multi-Hop Links
Complex Links
Geometry
Time
Spatial Analysis

STK Premium (Air or Space)

Includes all STK Pro capabilities

Adds advanced analysis and domain-specific capabilities for either Air or Space applications.

Customers select either the Premium Air or Premium Space capability set depending on their mission requirements.

Premium Capabilities for Both Air and Space

Advanced Electro-Optical / Infrared (EO/IR) analysis
Specific and limited real-time data feeds

Air Specific Capabilities

Aircraft performance profiles for highly accurate flight profiles (Aviator)
Performance profiles for:
- Missiles
- Hypersonic vehicles
- Rotorcraft

Space Specifc Capabilities

Spacecraft trajectory design (Astrogator)
Space environment models
Conjunction assessment
Trajectory design for spacecraft in all orbital regimes

STK Enterprise

Includes all STK Premium and STK Pro capabilities

Enterprise Capabilities

Test and evaluation-specific capabilities focused on aircraft testing
Behavior Engine
- Supports applications in Cameo and SysML

There are license dependencies STK and Specialized Modules/Plugins.

License	Dependency
STK Pro	None: This is the baseline capabilities
STK Premium	None: STK Premium includes STK Pro capabilities
STK Enterprise	None: STK Enterprise includes STK Pro, STK Premium Air and Space capabilities
STK Scheduler	STK Pro
STK SOLIS	STK Pro
MTK	STK Pro
ODTK	None: This is the baseline capabilities
ODSSA	ODTK

Note: A more detailed and up-to-date list can be found on the Ansys website.

Knowledge: What License Dependencies are There for STK Modules, ODTK, SSA products, and Components Libraries? (site.com)

Thanks,

Blacknight Space Team