Two force model plugin points are provided for the customization of the accelerations used in the propagation of the satellite trajectory. One point is provided as an HPOP plugin and the other as an SRP Reflectance Model. Typical uses of the force model plugin are to implement satellite specific solar pressure, drag and lift models.
Plugins may be written in a number of languages, including Perl, VB script, C++, C# and Visual Basic.NET.
NOTE: For plugins written in Perl, ODTK requires Perl version 5.6.1 or later.
The Plugin attribute has the following sub-attributes:
|Force Model Plugin Options|
|Use||Set to true to use the Plugin model.|
|PluginID||Select the desired plugin from the dropdown list.|
|PluginConfig||When you set the PluginID and click Apply in the Object Properties window, one or more sub-attributes will appear, allowing you to configure parameters that depend on the selected plugin.|
Follow the table of contents to ODTK Plugins for further information.
From the command line, you must register each assembly using
RegAsm.exe. To do this, you need
certain DLLs to be present on your computer. These can be obtained
by building a plugin (the build process produces these DLLs from
AGI-supplied DLLs located in the bin directory of the install).
These DLLs are named
Interop.Agi.<name>.dll. If you cannot do a
build to produce these DLLs, you can obtain them from AGI customer
support at www.agi.com.
cd to the directory where the DLLs are
present. Then execute the following lines:
[DIR]\RegAsm.exe /codebase Agi.As.Hpop.FrcMdl.Srp.Plugin.CSharp.Examples.dll
where [DIR] is the directory where
RegAsm.exe is located, possibly
Note: A warning about possible interference of the assembly name with other assemblies will be displayed. In deciding whether to proceed despite this warning, bear in mind that the assembly name begins with "Agi.", which should minimize the chance of interference. If in doubt, however, please check with your system administrator or contact AGI technical support.
From the command line, register each WSC file using
cd in to the
directory where the
.wsc file is located. Then
Note that an additional registration step is required for your component to show up as being selectable in the UI. This registration associates your plugin with a plugin category. There is a sample registration file in each of the CodeSamples\...\WSC folders that shows how to register for a particular plugin point.
Regsvr32.exe requires administrator rights in order to register a plugin. Once registered, it's available to all users on that machine (provided that the actual file location on the disk does not change). It's sometimes difficult to find a system administrator to register the plugin though. In this case we have provided a VBScript utility "register_wsc_hkcu.vbs" located in your install under <INSTALL DIR>\CodeSamples\Extend (where <INSTALL DIR> is typically C:\Program Files\AGI\ODTK 6 (32-bit Windows) or C:\Program Files (x86)\AGI\ODTK 6 (64-bit Windows)). The utility will register a Windows Script Component to the HKEY_CURRENT_USER area of the Windows registry rather than HKEY_LOCAL_MACHINE. To run the utility, open up a command prompt and change directories to the location of the utility. Then enter
cscript register_wsc_hkcu.vbs "Your WSC Name.wsc"
replacing "Your WSC Name.wsc" with the actual full path to the location of your Windows Script Component (WSC) file. The utility will parse your WSC file and make the appropriate entries into the Windows registry. This utility must be run for each user on the machine if they want to use that plugin.