SetState MixedSpherical
Set the orbit state of a satellite or missile using mixed spherical coordinates
Syntax
SetState <VehObjectPath> MixedSpherical {Propagator} {NoProp | {TimeInterval}} <StepSize> {CoordSystem} "<OrbitEpoch>" <Longitude> <GeodeticLatitude> <Altitude> <HorizontalFlightPathAngle> <FlightPathAzimuth> <Velocity> ["<CoordEpoch>"]
Related commands
Description
The SetState MixedSpherical command sets the orbit state of the specified satellite or missile and propagates the orbit over the specified time period. The propagated ephemeris data is spaced by the <StepSize> parameter.
The SetState MixedSpherical command is valid for Satellite and Missile only.
| Parameter | Description |
|---|---|
| {Propagator} | This parameter is case sensitive and the Propagator name must match the format used in the Satellite's Orbit page or Missile's Trajectory page under Basic properties. Valid values for Satellite are TwoBody, J2Perturbation, J4Perturbation, HPOP, and LOP. Valid values for Missile are TwoBody and HPOP. |
| {NoProp | {TimeInterval}} | Enter NoProp to set the state of the vehicle but not propagate it. Enter {TimeInterval} to define the beginning and end of the satellite's time period for propagation. For valid {TimeInterval} values, see Time Options. |
| <StepSize> | Enter this in seconds; it must be greater than or equal to 0.001 seconds.
If LOP propagator is selected, the <StepSize> must be greater than or equal to one day (86164.09 seconds). |
| {CoordSystem} | Enter any coordinate system supported by the vehicle's central body. All central bodies support Fixed, Inertial, J2000, ICRF, and TrueOfDate. TrueOfEpoch, TEMEOfDate, TEMEOfEpoch, MeanOfDate, MeanOfEpoch, B1950, AlignmentAtEpoch, ITRF2020, ITRF2014, ITRF2008, ITRF2005, and ITRF2000 are supported when the central body is Earth. MeanEarth, PrincipalAxes_440, PrincipalAxes_430, PrincipalAxes_421, etc. are supported when the central body is Moon. |
| "<OrbitEpoch>" | For valid "<OrbitEpoch>" values, see Time Options. |
| <Longitude> | Enter this in degrees. |
| <GeodeticLatitude> | Enter this in degrees. |
| <Altitude> | Enter this in Connect distance units. |
| <HorizontalFlightPathAngle> | Enter this in degrees. |
| <FlightPathAzimuth> | Enter this in degrees. |
| <Velocity> | Enter this in Connect distance units over Connect time units. |
| ["<CoordEpoch>"] | This parameter is only applicable, and is required, for {CoordSystem} based on an epoch, such as MeanOfEpoch, TrueOfEpoch, TEMEOfEpoch, and AlignmentAtEpoch.
For valid "<CoordEpoch>" values, see Time Options. |
This command doesn't accept values of less than -180 degrees for orbital elements.
Propagator-specific parameters stored with the vehicle instance aren't affected. For example, when STK receives the SetState MixedSpherical command with HPOP specified for {Propagator}, STK uses the existing HPOP force model data. If you create a vehicle and modify the force model, or load a vehicle with a modified force model, that data isn't modified by this command. If you create a new vehicle via the Connect New Command, STK uses the default force model data.
The STK orbit propagator doesn't completely validate the correctness of the complete orbit state specified. This means that Connect may return a positive acknowledgment even when STK cannot display the orbit track. Connect performs the same validation that occurs from the entry of state data via the user interface.
Examples
To set the path for the ERS1 satellite using Mixed Spherical coordinates and propagate the orbit:
To set the state for Missile1 using MixedSpherical coordinates and the TwoBody propagator:
To set the state for TestSat34 using MixedSpherical coordinates and the J4Perturbation propagator:
Return message
Group membership
This command belongs to the following group(s):
Version
10.1