# General QuestionSatellite STS payloads setup

#### gattispilot

Not sure if this is the right place,
So looking at Shuttle fleet payloads. So the satellites are made from 4 parts.
 PAM-1:STS_PAYLOADS\PAM STATUS Orbiting Earth ATTACHED 0:0,STS-5 PRPLEVEL 0:1.000 END STAR-48B1:STS_PAYLOADS\EQUIP STATUS Orbiting Earth ATTACHED 0:0,PAM-1 END STAR-30B1:STS_PAYLOADS\STAR STATUS Orbiting Earth ATTACHED 0:0,STAR-48B1 END SBS-3:STS_PAYLOADS\HS-376 STATUS Orbiting Earth ATTACHED 0:0,STAR-30B1 PRPLEVEL 0:1.000 CONFIGURATION 1 CURRENT_PAYLOAD 0 END 

But then looking at the cfg of each 4 only one shows a mesh the equip which shows the PAM
 ; === Configuration file for vessel class STS-PAM === ClassName = PAM Mass = 236 ;124KG EMPTY STAR-48B SHORT: MASS 102KG EQUIPMENT MASS PropellantResource1 = 2000 ;STS LOAD FUEL Size = 10 MaxAttitudeThrust = 0 ISP = 2802 MaxMainThrust = 67170 TouchdownPoints = 0 -0.882 -2.027 -.882 .882 -2.027 .882 .882 -2.027 CrossSections = 1.77 1.80 1.37 Inertia = 0.22 0.22 0.22 MEngineRef1 = 0 0 -1.5 CameraOffset = 0 1.2 -0.15 ; === Attachment specs === BEGIN_ATTACHMENT C 0 0 0 0 0 1 0 1 0 XS ;TO STAR-48B P 0 0 0 0 0 -1 0 1 0 XS ;TO SPIN TABLE END_ATTACHMENT 

 ; === Configuration file for vessel class Satellite === ClassName = EQUIP MeshName = sts_payloads\pam-d Mass = 1124 Size = 10 PropellantResource1 = 10 MaxAttitudeThrust = 1 MaxMainThrust = 1 AttRefZ00 = 0.65 0 -0.2 AttRefZ01 = -0.65 0 -0.2 ISP = 10000 EnableFocus = FALSE ; === Attachment specs === BEGIN_ATTACHMENT P 0 0 0 0 0 -1 0 1 0 XS ; TO PAM-D C 0 0 0 0 0 1 0 1 0 XS ; TO SATELLITE END_ATTACHMENT 

 ; === Configuration file for vessel class Satellite === ClassName = STAR Mass = 32 EnableFocus = FALSE Size = 10 ; === Attachment specs === BEGIN_ATTACHMENT P 0 0 0 0 0 -1 0 1 0 XS ; TO PAM-D C 0 0 0 0 0 1 0 1 0 XS ; TO SATELLITE END_ATTACHMENT 

 ; === Configuration file for vessel class NASA ASE PAM === ClassName = HS-376 Module = Spacecraft3 ; === Attachment specs === BEGIN_ATTACHMENT P 0 0 -2.28 0 0 -1 0 1 0 XS ; TO PAM EQUIPMENT P 0 0 -1.13 0 0 1 0 1 0 XS ; TO STINGER C 0 0 1.13 0 0 1 0 1 0 XS ; TO A-FRAME C 0 0.17 -2.95 0 0 1 0 1 0 XS ; TO STINGER END_ATTACHMENT 

So we show the PAM mesh but the Satellite is HS-376. It has the module as Spacecraft3. But I can not find a HS-376 ini in spacecraft.

Here is another satellit different name but same class:
 PALAPA-B1:STS_PAYLOADS\HS-376 STATUS Orbiting Earth RPOS 5864152.29 3044501.76 962955.07 RVEL 480.717 -3162.462 7039.959 AROT 72.82 -61.32 172.08 VROT 0.07 -0.00 -0.00 ATTACHED 0:0,STAR-30B1 AFCMODE 7 PRPLEVEL 0:1.000000 NAVFREQ 0 0 RCS 1 CTRL_SURFACE 1 CONFIGURATION 1 CURRENT_PAYLOAD 0 SEQ 0 -2 0.000000 SEQ 1 -2 0.000000 END 

This has animation sequences. But what tells to show the satellite mesh?
Seems like it should just be 2 vessels PAM and Satellite

Last edited:

#### Gargantua2024

##### The Desktop Orbinaut
This arrangement was from the old O2006 where they were supposed to be operated by Pylon MFD (based on the documentation from STS Payloads addon). The HS-376 satellites were coded as SC3/4 vessels.

To simplify operations, I converted the PAM-D launched satellites into VesselBuilders in a way that the satellites automatically jettison from their kick motors once the fuel of those boosters were depleted. The files were included in my Launch Sounds for the Space Shuttle addon (Flights 1-10.zip)

#### gattispilot

Thanks. OK that explains that. But I wonder where the satellite mesh was coded. It looks like it is the Anik mesh.

I may redo them even more. It looks like that HS-376 satellite expands. Because there does not seem to be a sc3/4 ini that tells which mesh and animation

#### Gargantua2024

##### The Desktop Orbinaut
There are six identical HS-376 meshes on the STS Payloads addon, of which their only differences are their textures:
• Anik.msh
• Arabsat.msh
• Aussat-2006c.msh
• Morelos.msh
• Palapa.msh
• Westar.msh

#### gattispilot

Thanks. But what determines the mesh.

#### Gargantua2024

##### The Desktop Orbinaut
It looks like that HS-376 satellite expands. Because there does not seem to be a sc3/4 ini that tells which mesh and animation
The name of the HS-376 satellite in the scenario (example: Anik-C2) is also the sc3/4 ini file of the satellite

#### gattispilot

Yes. But I could not find a Hs-376.ini

#### Donamy

Donator
Beta Tester
The mesh should be in the .ini

#### Marg

##### Active member
In current STS release there is something like:
in scenario, so satellite is not spacecraft3/4 vessel, as HS-376.cfg is ordinary cfg file with no animation support.
If there would be scenario line:
SBS-4:spacecraft\spacecraft3
then SBS-4.ini is required with all info (like in cfg + animations).

#### gattispilot

In current STS release there is something like:
in scenario, so satellite is not spacecraft3/4 vessel, as HS-376.cfg is ordinary cfg file with no animation support.
If there would be scenario line:
SBS-4:spacecraft\spacecraft3
then SBS-4.ini is required with all info (like in cfg + animations).
Yes. But like sts 5 PAM-1:STS_PAYLOADS\PAM STATUS Orbiting Earth ATTACHED 0:0,STS-5 PRPLEVEL 0:1.000 END STAR-48B1:STS_PAYLOADS\EQUIP STATUS Orbiting Earth ATTACHED 0:0,PAM-1 END STAR-30B1:STS_PAYLOADS\STAR STATUS Orbiting Earth ATTACHED 0:0,STAR-48B1 END SBS-3:STS_PAYLOADS\HS-376 STATUS Orbiting Earth ATTACHED 0:0,STAR-30B1 PRPLEVEL 0:1.000 CONFIGURATION 1 CURRENT_PAYLOAD 0 END 

There is no ini for HS-376 but there is the SBS-3

So in the real world there would just be the PAM (Payload Assist Module) and the Satellite. The PAm would the be rocket that moves it into orbit.

#### Gargantua2024

##### The Desktop Orbinaut
That's because SBS-3 is the HS-376's ini file itself. Here are all other ini files for the HS-376 class satellites:
• Anik-C1.ini
• Anik-C2.ini
• Anik-C3.ini
• Anik-D2.ini
• Aussat-1.ini
• Aussat-2.ini
• Morelos-A.ini
• Morelos-B.ini
• Palapa-B1.ini
• Palapa-B2.ini
• Palapa-B2-R.ini
• SBS-3.ini
• SBS-4.ini
• Telstar-3C.ini
• Telstar-3D.ini
• Westar-VI.ini
• Westar-VI-R.ini
The list below are also listed in scenarios as HS-376 class satellites, but are built on different models:

(Spacebus-100 class)
• Arabsat-1B.ini
(I-1000 class)
• INSAT-1B.ini
Remember that the satellites above are coded as SC3/4 vessels, so their name in the scenario is what define the mesh rendered

Last edited:

#### Gargantua2024

##### The Desktop Orbinaut
So in the real world there would just be the PAM (Payload Assist Module) and the Satellite. The PAm would the be rocket that moves it into orbit.
Yep. The PAM-D kick motor is the upper stage used by the Shuttles to send these satellites into geostationary transfer orbits since the satellites were relatively light. Heavier satellites used the IUS and TOS (in the case of ACTS) instead

#### Gargantua2024

##### The Desktop Orbinaut
In current STS release there is something like:
in scenario, so satellite is not spacecraft3/4 vessel, as HS-376.cfg is ordinary cfg file with no animation support.
If there would be scenario line:
SBS-4:spacecraft\spacecraft3
then SBS-4.ini is required with all info (like in cfg + animations).
The Module defined in the HS-376.cfg is SC3...Here are the parameters coded on the cfg file below:
Code:
; === Configuration file for vessel class NASA ASE PAM ===
ClassName = HS-376
Module = Spacecraft3

#### gattispilot

Thanks. So ideally in the scenario it show SBs-3 as spacecraft3/4 rather than HS-376.

It looked like the HS 376 extend:

#### Gargantua2024

##### The Desktop Orbinaut
Thanks. So ideally in the scenario it show SBs-3 as spacecraft3/4 rather than HS-376.
Exactly!
It looked like the HS 376 extend:
Yep. In the scenarios, the HS-376 satellites extend by pressing LShift+Key 1, and rotate by pressing LShift+Key 7

#### gattispilot

Thanks. Yes I see that in the cfg. I may need to make dll of them. So all you need to do is add a PAM and attach the satellite. Like I did for sts 49. Where the Thruster launch the sat and spun. Stop the spinning for nav purposes and restart the steering.,....

On the hs 376. So looking at the mesh the bottom seems solid. It would seem the kick motor thruster would be there. And the bottom extends down?

Or the whole assembly extends up when in orbit as the kick motor would burn the inside of the bottom unit

Might make another version without antenna as one shuttle mission repairs her.

Last edited:

#### Marg

##### Active member
The Module defined in the HS-376.cfg is SC3...Here are the parameters coded on the cfg file below:
Code:
; === Configuration file for vessel class NASA ASE PAM ===
ClassName = HS-376
Module = Spacecraft3
Yes, I just realized that spacecraft3 module can be defined\referenced inside .cfg file also...

#### gattispilot

It is just confusing with the HS-376 cfg with nothing because the real satelite is a different name.
I am thinking about doing dlls for the PAm and satellites.
And ase with inside structure:

#### gattispilot

Now we get this:

According to this:

it looks like the pam and satellite drift for 45 minutes and then the pam rocket engages. I like the when the PAM is out of fuel separate. I have a timer so after 45 minutes the thruster will fire or you can manually fire