FlightGear wiki - User contributions [en]

Sukhoi Su-15/info

2022-08-29T21:08:50Z

Vitos:

<includeonly>{{infobox aircraft
| name = {{LangSwitch
| en = Sukhoi Su-15
| ru = Су-15
}}
| aircraft = Su-15
| image = Su-15-Exterior.png
| image2 = Su-15-Interior.png
| image3 = Su-15-Panel.png
| type = Fighter aircraft/Interceptor aircraft/Military aircraft/Supersonic aircraft/Jet fighter
| config = Delta-wing aircraft
| propulsion = Twinjet
| manufacturer = Sukhoi
| author1 = {{usr|Vitos|Victor Slavutinsky}}
| author2 =
| author3 =
| author4 =
| author5 =
| author6 =
| author7 =
| author8 =
| devel-team =
| fdm = JSBsim
| fgname = Su-15
| status-fdm =
| status-systems =
| status-cockpit =
| status-model =
| ready =
| forumtid = 25993
| navbar = 1
| license = GetToFlyOnly
| download = http://autopsi.info/Su-15/Su-15.zip
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[Sukhoi Su-15]].
[[Category:Aircraft infobox documentation]]
</noinclude>

Vostok-1

2020-06-25T12:43:44Z

Vitos: /* Developer's message */

{{:{{PAGENAME}}/info}}
{{SpaceFlight}}

[[Image:Spacetripready.png|link=FlightGear_space_program]]

Vostok-1 was the first manned spaceflight in history, done by Yuri Gagarin in 1961. The launch vehicle was a Vostok-K rocket carrying the Vostok-3KA capsule.

While the historical space mission was under fully automatic control and Gagarin ejected from the capsule at an altitude of 7 km and parachuted to the ground, the simulation in Flightgear has to be flown manually and lands the capsule itself via parachutes. To that aim, an extra control panel to manage the various stages of the rocket which is not present in the real capsule has been added at the right side of the cockpit.

== Characteristics of the Vostok-K carrier ==

The Vostok-K is a three stage rocket. All three stages are powered by RP-1 (a kerosene-like rocket propellant) and liquid oxygene. It works partially with a parallel-burn concept.

The first stage consists of four boosters with a total thrust of 3,883.4 kN. They ignite in parallel with the second stage with a thrust of 912 kN.

The boosters have a burn time of about 118 seconds and are jettisoned when empty. In the later stages of the booster burn, the rocket can reach accelerations in excess of 4 g (the structural limit) and the engines need to be throttled back.

The second stage has a burn duration of 301 seconds and is also discarded when empty. Just as with the boosters, the acceleration may reach the structural limit towards the end of the burn as the tanks deplete.

The third stage has a much lower thrust of 54.5 kN leading to about 0.5 g acceleration. It is used to nudge the capsule into a stable orbit and has a burn duration of 365 seconds.

Control during ascent is provided by maneuvering thrusters rather than thrust vector control by gimbaling the main engines. As a result, Vostok's response to control input in powered flight is considerably less crisp than that of e.g. the Space Shuttle.

== Limits and damage ==

The modeling of Vostok includes structural limit checks. Upon ascent, the various parts of the rocket can break when overstressed either by too high dynamical pressure or g-forces. Often this leads to loss of control as the maneuver engines are not powerful enough to compensate for e.g. the loss of a booster and the resulting asymmetric thrust.

In addition, the pilot chute can tear off if deployed at too high dynamical pressure, just as the main chute and and the landing engine sensor.

For the detailed limits in all stages of the flight, please refer to the manual coming with the spacecraft.

== Automated launch ==

The spacecraft is equipped with a simple launch AP. This is (intentionally, to reflect the early spaceflight capabilities) made to be not precise and cannot be used for e.g. rendezvous targeting, but it can fly the capsule into a stable orbit. The target orbit can be specified in the menu, and the AP is capable of fully controlling the spacecraft right to third stage separation.

There is a one-way option provided to take over manually in case of an AP malfunction - note that controls can not be handed back to the autopilot.

== Simulation options ==

The simulation provides the options to make discarded stages simply vanish (easier on system resources) or to simulate them as they fall away or, in the case of third stage and TDU, orbit together with the spacecraft for a while.

For technical reasons, the option to simulate the drop of the boosters is really a startup option - the user selection will be autosaved and used upon next startup.

In addition, the simulation provides the option to automatically switch to the [[Earthview]] renderer when a certain altitude is reached and to switch back to the normal renderer when the spacecraft returns to Earth.

== Developer's message ==

Well, what can I say? You know what.

Real Vostok-1 was fully automated. The purpose of "Vostok-1" FG project, aside other things, is to give to You some understanding of spaceflight by giving to You full control from lift-off to landing. Perhaps there will be some automatic orbit and de-orbit in the future, but not now.

There are many things which would be realized. At now it's possible to "fly" around "Earth".

P.S. I could not and won't be responsible of what's going on with model after I had quit development of it, since of conflict instead of friendship, at 2011, when it was "now". As I made model GPL, whoever may do anything with it, and it's up to community, which conflicted with idea of spaceflight then, and suddenly changed it's mind with "Shuttle" model development next, if it not works way it should, not looks as it should, etc. Same with my "MiG-15" model. It's as really working thing may not work at news of some country, and it's not problem of people who made that thing, but of ones views of whom are cut short voluntary. Basically, I just don't care, as it useless with those.

If You mean some friendship, You may look at my "Su-15" model instead, which no-one with arguing/competitive/conflict mind having right, and, though, ability to put hands on.

Wish to You good flight,

Victor Slavutinsky, vitosnet@mail.ru.

== Gallery ==

Current:

<gallery mode="packed">
Vostok-launch01.jpg|Stage 1+2 ignited
Vostok-launch02.jpg|Stage 2 burn
Vostok-launch03.jpg|Stage 2 separation, stage 3 ignited
Vostok-launch04.jpg|The TDU in orbit
Vostok-glow03.jpg|The capsule glowing from atmospheric friction
Vostok-glow05.jpg|The charred capsule hanging underneath the braking parachute
</gallery>

Historic:

<gallery mode="packed">
Vostok_01.jpg|Stage 1+2 ignited
Vostok_02.jpg|Stage 2 burn
Vostok_03.jpg|Stage 3 burn
Vostok_04.jpg|The TDU in orbit
Vostok_05.jpg|TDU details
Vostok_06.jpg|entry configuration
File:SOTM_2019-05_Cosmonaut_by_legoboyvdlp.jpg
</gallery>

== External links ==
* [http://en.wikipedia.org/wiki/Vostok_1 Wikipedia]

[[ru:Vostok-1]]

Vostok-1

2020-06-25T12:43:03Z

Vitos: /* Developer's message */

{{:{{PAGENAME}}/info}}
{{SpaceFlight}}

[[Image:Spacetripready.png|link=FlightGear_space_program]]

Vostok-1 was the first manned spaceflight in history, done by Yuri Gagarin in 1961. The launch vehicle was a Vostok-K rocket carrying the Vostok-3KA capsule.

While the historical space mission was under fully automatic control and Gagarin ejected from the capsule at an altitude of 7 km and parachuted to the ground, the simulation in Flightgear has to be flown manually and lands the capsule itself via parachutes. To that aim, an extra control panel to manage the various stages of the rocket which is not present in the real capsule has been added at the right side of the cockpit.

== Characteristics of the Vostok-K carrier ==

The Vostok-K is a three stage rocket. All three stages are powered by RP-1 (a kerosene-like rocket propellant) and liquid oxygene. It works partially with a parallel-burn concept.

The first stage consists of four boosters with a total thrust of 3,883.4 kN. They ignite in parallel with the second stage with a thrust of 912 kN.

The boosters have a burn time of about 118 seconds and are jettisoned when empty. In the later stages of the booster burn, the rocket can reach accelerations in excess of 4 g (the structural limit) and the engines need to be throttled back.

The second stage has a burn duration of 301 seconds and is also discarded when empty. Just as with the boosters, the acceleration may reach the structural limit towards the end of the burn as the tanks deplete.

The third stage has a much lower thrust of 54.5 kN leading to about 0.5 g acceleration. It is used to nudge the capsule into a stable orbit and has a burn duration of 365 seconds.

Control during ascent is provided by maneuvering thrusters rather than thrust vector control by gimbaling the main engines. As a result, Vostok's response to control input in powered flight is considerably less crisp than that of e.g. the Space Shuttle.

== Limits and damage ==

The modeling of Vostok includes structural limit checks. Upon ascent, the various parts of the rocket can break when overstressed either by too high dynamical pressure or g-forces. Often this leads to loss of control as the maneuver engines are not powerful enough to compensate for e.g. the loss of a booster and the resulting asymmetric thrust.

In addition, the pilot chute can tear off if deployed at too high dynamical pressure, just as the main chute and and the landing engine sensor.

For the detailed limits in all stages of the flight, please refer to the manual coming with the spacecraft.

== Automated launch ==

The spacecraft is equipped with a simple launch AP. This is (intentionally, to reflect the early spaceflight capabilities) made to be not precise and cannot be used for e.g. rendezvous targeting, but it can fly the capsule into a stable orbit. The target orbit can be specified in the menu, and the AP is capable of fully controlling the spacecraft right to third stage separation.

There is a one-way option provided to take over manually in case of an AP malfunction - note that controls can not be handed back to the autopilot.

== Simulation options ==

The simulation provides the options to make discarded stages simply vanish (easier on system resources) or to simulate them as they fall away or, in the case of third stage and TDU, orbit together with the spacecraft for a while.

For technical reasons, the option to simulate the drop of the boosters is really a startup option - the user selection will be autosaved and used upon next startup.

In addition, the simulation provides the option to automatically switch to the [[Earthview]] renderer when a certain altitude is reached and to switch back to the normal renderer when the spacecraft returns to Earth.

== Developer's message ==

Well, what can I say? You know what.

Real Vostok-1 was fully automated. The purpose of "Vostok-1" FG project, aside other things, is to give to You some understanding of spaceflight by giving to You full control from lift-off to landing. Perhaps there will be some automatic orbit and de-orbit in the future, but not now.

There are many things which would be realized. At now it's possible to "fly" around "Earth".

P.S. I could not and won't be responsible of what's going on with model after I had quit development of it, since of conflict instead of friendship, at 2011, when it was "now". As I made model GPL, whoever may do anything with it, and it's up to community, which conflicted with idea of spaceflight then, and suddenly changed it's mind with "Shuttle" model development next, if it not works way it should, not looks as it should, etc. Same with my "MiG-15" model. It's as really working thing may not work at news of some country, and it's not problem of people who made that thing, but of ones, views of whom are cut short voluntary. Basically, I just don't care, as it useless with those.

If You mean some friendship, You may look at my "Su-15" model instead, which no-one with arguing/competitive/conflict mind having right, and, though, ability to put hands on.

Wish to You good flight,

Victor Slavutinsky, vitosnet@mail.ru.

== Gallery ==

Current:

<gallery mode="packed">
Vostok-launch01.jpg|Stage 1+2 ignited
Vostok-launch02.jpg|Stage 2 burn
Vostok-launch03.jpg|Stage 2 separation, stage 3 ignited
Vostok-launch04.jpg|The TDU in orbit
Vostok-glow03.jpg|The capsule glowing from atmospheric friction
Vostok-glow05.jpg|The charred capsule hanging underneath the braking parachute
</gallery>

Historic:

<gallery mode="packed">
Vostok_01.jpg|Stage 1+2 ignited
Vostok_02.jpg|Stage 2 burn
Vostok_03.jpg|Stage 3 burn
Vostok_04.jpg|The TDU in orbit
Vostok_05.jpg|TDU details
Vostok_06.jpg|entry configuration
File:SOTM_2019-05_Cosmonaut_by_legoboyvdlp.jpg
</gallery>

== External links ==
* [http://en.wikipedia.org/wiki/Vostok_1 Wikipedia]

[[ru:Vostok-1]]

Vostok-1

2020-06-25T12:42:42Z

Vitos: /* Developer's message */

{{:{{PAGENAME}}/info}}
{{SpaceFlight}}

[[Image:Spacetripready.png|link=FlightGear_space_program]]

Vostok-1 was the first manned spaceflight in history, done by Yuri Gagarin in 1961. The launch vehicle was a Vostok-K rocket carrying the Vostok-3KA capsule.

While the historical space mission was under fully automatic control and Gagarin ejected from the capsule at an altitude of 7 km and parachuted to the ground, the simulation in Flightgear has to be flown manually and lands the capsule itself via parachutes. To that aim, an extra control panel to manage the various stages of the rocket which is not present in the real capsule has been added at the right side of the cockpit.

== Characteristics of the Vostok-K carrier ==

The Vostok-K is a three stage rocket. All three stages are powered by RP-1 (a kerosene-like rocket propellant) and liquid oxygene. It works partially with a parallel-burn concept.

The first stage consists of four boosters with a total thrust of 3,883.4 kN. They ignite in parallel with the second stage with a thrust of 912 kN.

The boosters have a burn time of about 118 seconds and are jettisoned when empty. In the later stages of the booster burn, the rocket can reach accelerations in excess of 4 g (the structural limit) and the engines need to be throttled back.

The second stage has a burn duration of 301 seconds and is also discarded when empty. Just as with the boosters, the acceleration may reach the structural limit towards the end of the burn as the tanks deplete.

The third stage has a much lower thrust of 54.5 kN leading to about 0.5 g acceleration. It is used to nudge the capsule into a stable orbit and has a burn duration of 365 seconds.

Control during ascent is provided by maneuvering thrusters rather than thrust vector control by gimbaling the main engines. As a result, Vostok's response to control input in powered flight is considerably less crisp than that of e.g. the Space Shuttle.

== Limits and damage ==

The modeling of Vostok includes structural limit checks. Upon ascent, the various parts of the rocket can break when overstressed either by too high dynamical pressure or g-forces. Often this leads to loss of control as the maneuver engines are not powerful enough to compensate for e.g. the loss of a booster and the resulting asymmetric thrust.

In addition, the pilot chute can tear off if deployed at too high dynamical pressure, just as the main chute and and the landing engine sensor.

For the detailed limits in all stages of the flight, please refer to the manual coming with the spacecraft.

== Automated launch ==

The spacecraft is equipped with a simple launch AP. This is (intentionally, to reflect the early spaceflight capabilities) made to be not precise and cannot be used for e.g. rendezvous targeting, but it can fly the capsule into a stable orbit. The target orbit can be specified in the menu, and the AP is capable of fully controlling the spacecraft right to third stage separation.

There is a one-way option provided to take over manually in case of an AP malfunction - note that controls can not be handed back to the autopilot.

== Simulation options ==

The simulation provides the options to make discarded stages simply vanish (easier on system resources) or to simulate them as they fall away or, in the case of third stage and TDU, orbit together with the spacecraft for a while.

For technical reasons, the option to simulate the drop of the boosters is really a startup option - the user selection will be autosaved and used upon next startup.

In addition, the simulation provides the option to automatically switch to the [[Earthview]] renderer when a certain altitude is reached and to switch back to the normal renderer when the spacecraft returns to Earth.

== Developer's message ==

Well, what can I say? You know what.

Real Vostok-1 was fully automated. The purpose of "Vostok-1" FG project, aside other things, is to give to You some understanding of spaceflight by giving to You full control from lift-off to landing. Perhaps there will be some automatic orbit and de-orbit in the future, but not now.

There are many things which would be realized. At now it's possible to "fly" around "Earth".

P.S. I could not and won't be responsible of what's going on with model after I had quit development of it, since of conflict instead of friendship, at 2011, when it was "now". As I made model GPL, whoever may do anything with it, and it's up to community, which conflicted with idea of spaceflight then, and suddenly changed it's mind with "Shuttle" model development next, if it not works way it should, not looks as it should, etc. Same with my "MiG-15" model. It's as really working thing may not work at news of some country, and it's not problem of people who made that thing, but of ones, views of whom are cut short voluntary. Basically, I just don't care, as it useless with those.

If You mean some friendship, You may look at my "Su-15" model instead, which no-one with arguing/competitive/conflict mind having right, and, though, ability, to put hands on.

Wish to You good flight,

Victor Slavutinsky, vitosnet@mail.ru.

== Gallery ==

Current:

<gallery mode="packed">
Vostok-launch01.jpg|Stage 1+2 ignited
Vostok-launch02.jpg|Stage 2 burn
Vostok-launch03.jpg|Stage 2 separation, stage 3 ignited
Vostok-launch04.jpg|The TDU in orbit
Vostok-glow03.jpg|The capsule glowing from atmospheric friction
Vostok-glow05.jpg|The charred capsule hanging underneath the braking parachute
</gallery>

Historic:

<gallery mode="packed">
Vostok_01.jpg|Stage 1+2 ignited
Vostok_02.jpg|Stage 2 burn
Vostok_03.jpg|Stage 3 burn
Vostok_04.jpg|The TDU in orbit
Vostok_05.jpg|TDU details
Vostok_06.jpg|entry configuration
File:SOTM_2019-05_Cosmonaut_by_legoboyvdlp.jpg
</gallery>

== External links ==
* [http://en.wikipedia.org/wiki/Vostok_1 Wikipedia]

[[ru:Vostok-1]]

Vostok-1

2020-06-24T11:12:02Z

Vitos: /* Developer's message */

{{:{{PAGENAME}}/info}}
{{SpaceFlight}}

[[Image:Spacetripready.png|link=FlightGear_space_program]]

Vostok-1 was the first manned spaceflight in history, done by Yuri Gagarin in 1961. The launch vehicle was a Vostok-K rocket carrying the Vostok-3KA capsule.

While the historical space mission was under fully automatic control and Gagarin ejected from the capsule at an altitude of 7 km and parachuted to the ground, the simulation in Flightgear has to be flown manually and lands the capsule itself via parachutes. To that aim, an extra control panel to manage the various stages of the rocket which is not present in the real capsule has been added at the right side of the cockpit.

== Characteristics of the Vostok-K carrier ==

The Vostok-K is a three stage rocket. All three stages are powered by RP-1 (a kerosene-like rocket propellant) and liquid oxygene. It works partially with a parallel-burn concept.

The first stage consists of four boosters with a total thrust of 3,883.4 kN. They ignite in parallel with the second stage with a thrust of 912 kN.

The boosters have a burn time of about 118 seconds and are jettisoned when empty. In the later stages of the booster burn, the rocket can reach accelerations in excess of 4 g (the structural limit) and the engines need to be throttled back.

The second stage has a burn duration of 301 seconds and is also discarded when empty. Just as with the boosters, the acceleration may reach the structural limit towards the end of the burn as the tanks deplete.

The third stage has a much lower thrust of 54.5 kN leading to about 0.5 g acceleration. It is used to nudge the capsule into a stable orbit and has a burn duration of 365 seconds.

Control during ascent is provided by maneuvering thrusters rather than thrust vector control by gimbaling the main engines. As a result, Vostok's response to control input in powered flight is considerably less crisp than that of e.g. the Space Shuttle.

== Limits and damage ==

The modeling of Vostok includes structural limit checks. Upon ascent, the various parts of the rocket can break when overstressed either by too high dynamical pressure or g-forces. Often this leads to loss of control as the maneuver engines are not powerful enough to compensate for e.g. the loss of a booster and the resulting asymmetric thrust.

In addition, the pilot chute can tear off if deployed at too high dynamical pressure, just as the main chute and and the landing engine sensor.

For the detailed limits in all stages of the flight, please refer to the manual coming with the spacecraft.

== Automated launch ==

The spacecraft is equipped with a simple launch AP. This is (intentionally, to reflect the early spaceflight capabilities) made to be not precise and cannot be used for e.g. rendezvous targeting, but it can fly the capsule into a stable orbit. The target orbit can be specified in the menu, and the AP is capable of fully controlling the spacecraft right to third stage separation.

There is a one-way option provided to take over manually in case of an AP malfunction - note that controls can not be handed back to the autopilot.

== Simulation options ==

The simulation provides the options to make discarded stages simply vanish (easier on system resources) or to simulate them as they fall away or, in the case of third stage and TDU, orbit together with the spacecraft for a while.

For technical reasons, the option to simulate the drop of the boosters is really a startup option - the user selection will be autosaved and used upon next startup.

In addition, the simulation provides the option to automatically switch to the [[Earthview]] renderer when a certain altitude is reached and to switch back to the normal renderer when the spacecraft returns to Earth.

== Developer's message ==

Well, what can I say? You know what.

Real Vostok-1 was fully automated. The purpose of "Vostok-1" FG project, aside other things, is to give to You some understanding of spaceflight by giving to You full control from lift-off to landing. Perhaps there will be some automatic orbit and de-orbit in the future, but not now.

There are many things which would be realized. At now it's possible to "fly" around "Earth".

P.S. I could not and won't be responsible of what's going on with model after I had quit development of it since of conflict instead of friendship at 2011, when it was "now". As I made model GPL, whoever may do anything with it, and it's up to community which conflicted with idea of spaceflight then, and suddenly changed it's mind with "Shuttle" model development next, if it's not work way it should, not looks as it should, etc. Same with my "MiG-15" model. It's as really working thing may not work at news of some country, and it's not problem of people who made that thing, but of ones views of whom are cut short voluntary. Basically, I just don't care, as it useless with those.

If You mean some friendship, You may look at my "Su-15" model instead, which no-one with arguing/competitive/conflict mind having right to put hands on.

Wish to You good flight,

Victor Slavutinsky, vitosnet@mail.ru.

== Gallery ==

Current:

<gallery mode="packed">
Vostok-launch01.jpg|Stage 1+2 ignited
Vostok-launch02.jpg|Stage 2 burn
Vostok-launch03.jpg|Stage 2 separation, stage 3 ignited
Vostok-launch04.jpg|The TDU in orbit
Vostok-glow03.jpg|The capsule glowing from atmospheric friction
Vostok-glow05.jpg|The charred capsule hanging underneath the braking parachute
</gallery>

Historic:

<gallery mode="packed">
Vostok_01.jpg|Stage 1+2 ignited
Vostok_02.jpg|Stage 2 burn
Vostok_03.jpg|Stage 3 burn
Vostok_04.jpg|The TDU in orbit
Vostok_05.jpg|TDU details
Vostok_06.jpg|entry configuration
File:SOTM_2019-05_Cosmonaut_by_legoboyvdlp.jpg
</gallery>

== External links ==
* [http://en.wikipedia.org/wiki/Vostok_1 Wikipedia]

[[ru:Vostok-1]]

Vostok-1

2020-06-24T11:11:41Z

Vitos: /* Developer's message */

{{:{{PAGENAME}}/info}}
{{SpaceFlight}}

[[Image:Spacetripready.png|link=FlightGear_space_program]]

Vostok-1 was the first manned spaceflight in history, done by Yuri Gagarin in 1961. The launch vehicle was a Vostok-K rocket carrying the Vostok-3KA capsule.

While the historical space mission was under fully automatic control and Gagarin ejected from the capsule at an altitude of 7 km and parachuted to the ground, the simulation in Flightgear has to be flown manually and lands the capsule itself via parachutes. To that aim, an extra control panel to manage the various stages of the rocket which is not present in the real capsule has been added at the right side of the cockpit.

== Characteristics of the Vostok-K carrier ==

The Vostok-K is a three stage rocket. All three stages are powered by RP-1 (a kerosene-like rocket propellant) and liquid oxygene. It works partially with a parallel-burn concept.

The first stage consists of four boosters with a total thrust of 3,883.4 kN. They ignite in parallel with the second stage with a thrust of 912 kN.

The boosters have a burn time of about 118 seconds and are jettisoned when empty. In the later stages of the booster burn, the rocket can reach accelerations in excess of 4 g (the structural limit) and the engines need to be throttled back.

The second stage has a burn duration of 301 seconds and is also discarded when empty. Just as with the boosters, the acceleration may reach the structural limit towards the end of the burn as the tanks deplete.

The third stage has a much lower thrust of 54.5 kN leading to about 0.5 g acceleration. It is used to nudge the capsule into a stable orbit and has a burn duration of 365 seconds.

Control during ascent is provided by maneuvering thrusters rather than thrust vector control by gimbaling the main engines. As a result, Vostok's response to control input in powered flight is considerably less crisp than that of e.g. the Space Shuttle.

== Limits and damage ==

The modeling of Vostok includes structural limit checks. Upon ascent, the various parts of the rocket can break when overstressed either by too high dynamical pressure or g-forces. Often this leads to loss of control as the maneuver engines are not powerful enough to compensate for e.g. the loss of a booster and the resulting asymmetric thrust.

In addition, the pilot chute can tear off if deployed at too high dynamical pressure, just as the main chute and and the landing engine sensor.

For the detailed limits in all stages of the flight, please refer to the manual coming with the spacecraft.

== Automated launch ==

The spacecraft is equipped with a simple launch AP. This is (intentionally, to reflect the early spaceflight capabilities) made to be not precise and cannot be used for e.g. rendezvous targeting, but it can fly the capsule into a stable orbit. The target orbit can be specified in the menu, and the AP is capable of fully controlling the spacecraft right to third stage separation.

There is a one-way option provided to take over manually in case of an AP malfunction - note that controls can not be handed back to the autopilot.

== Simulation options ==

The simulation provides the options to make discarded stages simply vanish (easier on system resources) or to simulate them as they fall away or, in the case of third stage and TDU, orbit together with the spacecraft for a while.

For technical reasons, the option to simulate the drop of the boosters is really a startup option - the user selection will be autosaved and used upon next startup.

In addition, the simulation provides the option to automatically switch to the [[Earthview]] renderer when a certain altitude is reached and to switch back to the normal renderer when the spacecraft returns to Earth.

== Developer's message ==

Well, what can I say? You know what.

Real Vostok-1 was fully automated. The purpose of "Vostok-1" FG project, aside other things, is to give to You some understanding of spaceflight by giving to You full control from lift-off to landing. Perhaps there will be some automatic orbit and de-orbit in the future, but not now.

There are many things which would be realized. At now it's possible to "fly" around "Earth".

P.S. I could not and won't be responsible of what's going on with model after I had quit development of it since of conflict instead of friendship at 2011, when it was "now". As I made model GPL, whoever may do anything with it, and it's up to community which conflicted with idea of spaceflight then, and suddenly changed it's mind with "Shuttle" model development next, if it's not work way it should, not looks as it should, etc. Same with my "MiG-15" model. It's as really working thing may not work at news of some country, and it's not problem of people who made that thing, but of ones views of whom are cut short voluntary. Basically, I just don't care, as it useless with those people.

If You mean some friendship, You may look at my "Su-15" model instead, which no-one with arguing/competitive/conflict mind having right to put hands on.

Wish to You good flight,

Victor Slavutinsky, vitosnet@mail.ru.

== Gallery ==

Current:

<gallery mode="packed">
Vostok-launch01.jpg|Stage 1+2 ignited
Vostok-launch02.jpg|Stage 2 burn
Vostok-launch03.jpg|Stage 2 separation, stage 3 ignited
Vostok-launch04.jpg|The TDU in orbit
Vostok-glow03.jpg|The capsule glowing from atmospheric friction
Vostok-glow05.jpg|The charred capsule hanging underneath the braking parachute
</gallery>

Historic:

<gallery mode="packed">
Vostok_01.jpg|Stage 1+2 ignited
Vostok_02.jpg|Stage 2 burn
Vostok_03.jpg|Stage 3 burn
Vostok_04.jpg|The TDU in orbit
Vostok_05.jpg|TDU details
Vostok_06.jpg|entry configuration
File:SOTM_2019-05_Cosmonaut_by_legoboyvdlp.jpg
</gallery>

== External links ==
* [http://en.wikipedia.org/wiki/Vostok_1 Wikipedia]

[[ru:Vostok-1]]

Vostok-1

2020-06-24T11:04:17Z

Vitos: /* Developer's message */

{{:{{PAGENAME}}/info}}
{{SpaceFlight}}

[[Image:Spacetripready.png|link=FlightGear_space_program]]

Vostok-1 was the first manned spaceflight in history, done by Yuri Gagarin in 1961. The launch vehicle was a Vostok-K rocket carrying the Vostok-3KA capsule.

While the historical space mission was under fully automatic control and Gagarin ejected from the capsule at an altitude of 7 km and parachuted to the ground, the simulation in Flightgear has to be flown manually and lands the capsule itself via parachutes. To that aim, an extra control panel to manage the various stages of the rocket which is not present in the real capsule has been added at the right side of the cockpit.

== Characteristics of the Vostok-K carrier ==

The Vostok-K is a three stage rocket. All three stages are powered by RP-1 (a kerosene-like rocket propellant) and liquid oxygene. It works partially with a parallel-burn concept.

The first stage consists of four boosters with a total thrust of 3,883.4 kN. They ignite in parallel with the second stage with a thrust of 912 kN.

The boosters have a burn time of about 118 seconds and are jettisoned when empty. In the later stages of the booster burn, the rocket can reach accelerations in excess of 4 g (the structural limit) and the engines need to be throttled back.

The second stage has a burn duration of 301 seconds and is also discarded when empty. Just as with the boosters, the acceleration may reach the structural limit towards the end of the burn as the tanks deplete.

The third stage has a much lower thrust of 54.5 kN leading to about 0.5 g acceleration. It is used to nudge the capsule into a stable orbit and has a burn duration of 365 seconds.

Control during ascent is provided by maneuvering thrusters rather than thrust vector control by gimbaling the main engines. As a result, Vostok's response to control input in powered flight is considerably less crisp than that of e.g. the Space Shuttle.

== Limits and damage ==

The modeling of Vostok includes structural limit checks. Upon ascent, the various parts of the rocket can break when overstressed either by too high dynamical pressure or g-forces. Often this leads to loss of control as the maneuver engines are not powerful enough to compensate for e.g. the loss of a booster and the resulting asymmetric thrust.

In addition, the pilot chute can tear off if deployed at too high dynamical pressure, just as the main chute and and the landing engine sensor.

For the detailed limits in all stages of the flight, please refer to the manual coming with the spacecraft.

== Automated launch ==

The spacecraft is equipped with a simple launch AP. This is (intentionally, to reflect the early spaceflight capabilities) made to be not precise and cannot be used for e.g. rendezvous targeting, but it can fly the capsule into a stable orbit. The target orbit can be specified in the menu, and the AP is capable of fully controlling the spacecraft right to third stage separation.

There is a one-way option provided to take over manually in case of an AP malfunction - note that controls can not be handed back to the autopilot.

== Simulation options ==

The simulation provides the options to make discarded stages simply vanish (easier on system resources) or to simulate them as they fall away or, in the case of third stage and TDU, orbit together with the spacecraft for a while.

For technical reasons, the option to simulate the drop of the boosters is really a startup option - the user selection will be autosaved and used upon next startup.

In addition, the simulation provides the option to automatically switch to the [[Earthview]] renderer when a certain altitude is reached and to switch back to the normal renderer when the spacecraft returns to Earth.

== Developer's message ==

Well, what can I say? You know what.

Real Vostok-1 was fully automated. The purpose of "Vostok-1" FG project, aside other things, is to give to You some understanding of spaceflight by giving to You full control from lift-off to landing. Perhaps there will be some automatic orbit and de-orbit in the future, but not now.

There are many things which would be realized. At now it's possible to "fly" around "Earth".

P.S. I could not and won't be responsible of what's going on with model after I had quit development of it since of conflict instead of friendship at 2011, when it was "now". As I made model GPL, whoever may do anything with it, and it's up to community which conflicted with idea of spaceflight then, and suddenly changed it's mind with "Shuttle" model development next, if it's not work way it should, not looks as it should, etc. Same with my "MiG-15" model. It's as really working thing may not work at news of some country, and it's not problem of people who made that thing. Basically, I just don't care, as it useless with those people.

If You mean some friendship, You may look at my "Su-15" model instead, which no-one with arguing/competitive/conflict mind having right to put hands on.

Wish to You good flight,

Victor Slavutinsky, vitosnet@mail.ru.

== Gallery ==

Current:

<gallery mode="packed">
Vostok-launch01.jpg|Stage 1+2 ignited
Vostok-launch02.jpg|Stage 2 burn
Vostok-launch03.jpg|Stage 2 separation, stage 3 ignited
Vostok-launch04.jpg|The TDU in orbit
Vostok-glow03.jpg|The capsule glowing from atmospheric friction
Vostok-glow05.jpg|The charred capsule hanging underneath the braking parachute
</gallery>

Historic:

<gallery mode="packed">
Vostok_01.jpg|Stage 1+2 ignited
Vostok_02.jpg|Stage 2 burn
Vostok_03.jpg|Stage 3 burn
Vostok_04.jpg|The TDU in orbit
Vostok_05.jpg|TDU details
Vostok_06.jpg|entry configuration
File:SOTM_2019-05_Cosmonaut_by_legoboyvdlp.jpg
</gallery>

== External links ==
* [http://en.wikipedia.org/wiki/Vostok_1 Wikipedia]

[[ru:Vostok-1]]

Vostok-1

2020-06-24T10:53:31Z

Vitos: /* Developer's message */

{{:{{PAGENAME}}/info}}
{{SpaceFlight}}

[[Image:Spacetripready.png|link=FlightGear_space_program]]

Vostok-1 was the first manned spaceflight in history, done by Yuri Gagarin in 1961. The launch vehicle was a Vostok-K rocket carrying the Vostok-3KA capsule.

While the historical space mission was under fully automatic control and Gagarin ejected from the capsule at an altitude of 7 km and parachuted to the ground, the simulation in Flightgear has to be flown manually and lands the capsule itself via parachutes. To that aim, an extra control panel to manage the various stages of the rocket which is not present in the real capsule has been added at the right side of the cockpit.

== Characteristics of the Vostok-K carrier ==

The Vostok-K is a three stage rocket. All three stages are powered by RP-1 (a kerosene-like rocket propellant) and liquid oxygene. It works partially with a parallel-burn concept.

The first stage consists of four boosters with a total thrust of 3,883.4 kN. They ignite in parallel with the second stage with a thrust of 912 kN.

The boosters have a burn time of about 118 seconds and are jettisoned when empty. In the later stages of the booster burn, the rocket can reach accelerations in excess of 4 g (the structural limit) and the engines need to be throttled back.

The second stage has a burn duration of 301 seconds and is also discarded when empty. Just as with the boosters, the acceleration may reach the structural limit towards the end of the burn as the tanks deplete.

The third stage has a much lower thrust of 54.5 kN leading to about 0.5 g acceleration. It is used to nudge the capsule into a stable orbit and has a burn duration of 365 seconds.

Control during ascent is provided by maneuvering thrusters rather than thrust vector control by gimbaling the main engines. As a result, Vostok's response to control input in powered flight is considerably less crisp than that of e.g. the Space Shuttle.

== Limits and damage ==

The modeling of Vostok includes structural limit checks. Upon ascent, the various parts of the rocket can break when overstressed either by too high dynamical pressure or g-forces. Often this leads to loss of control as the maneuver engines are not powerful enough to compensate for e.g. the loss of a booster and the resulting asymmetric thrust.

In addition, the pilot chute can tear off if deployed at too high dynamical pressure, just as the main chute and and the landing engine sensor.

For the detailed limits in all stages of the flight, please refer to the manual coming with the spacecraft.

== Automated launch ==

The spacecraft is equipped with a simple launch AP. This is (intentionally, to reflect the early spaceflight capabilities) made to be not precise and cannot be used for e.g. rendezvous targeting, but it can fly the capsule into a stable orbit. The target orbit can be specified in the menu, and the AP is capable of fully controlling the spacecraft right to third stage separation.

There is a one-way option provided to take over manually in case of an AP malfunction - note that controls can not be handed back to the autopilot.

== Simulation options ==

The simulation provides the options to make discarded stages simply vanish (easier on system resources) or to simulate them as they fall away or, in the case of third stage and TDU, orbit together with the spacecraft for a while.

For technical reasons, the option to simulate the drop of the boosters is really a startup option - the user selection will be autosaved and used upon next startup.

In addition, the simulation provides the option to automatically switch to the [[Earthview]] renderer when a certain altitude is reached and to switch back to the normal renderer when the spacecraft returns to Earth.

== Developer's message ==

Well, what can I say? You know what.

Real Vostok-1 was fully automated. The purpose of "Vostok-1" FG project, aside other things, is to give to You some understanding of spaceflight by giving to You full control from lift-off to landing. Perhaps there will be some automatic orbit and de-orbit in the future, but not now.

There are many things which would be realized. At now it's possible to "fly" around "Earth".

P.S. I could not and won't be responsible of what's going on with model after I had quit development of it since of conflict instead of friendship at 2011, when it was "now". As I made model GPL, whoever may do anything with it, and it's up to community which conflicted with idea of spaceflight then, and suddenly changed it's mind with "Shuttle" model development next, if it's not work way it should, not looks as it should, etc. Same with my "MiG-15" model. It's as really working thing may not work at news of some country, and it's not problem of people who made that thing.

If You mean some friendship, You may look at my "Su-15" model instead, which no-one with arguing/competitive/conflict mind having right to put hands on.

Wish to You good flight,

Victor Slavutinsky, vitosnet@mail.ru.

== Gallery ==

Current:

<gallery mode="packed">
Vostok-launch01.jpg|Stage 1+2 ignited
Vostok-launch02.jpg|Stage 2 burn
Vostok-launch03.jpg|Stage 2 separation, stage 3 ignited
Vostok-launch04.jpg|The TDU in orbit
Vostok-glow03.jpg|The capsule glowing from atmospheric friction
Vostok-glow05.jpg|The charred capsule hanging underneath the braking parachute
</gallery>

Historic:

<gallery mode="packed">
Vostok_01.jpg|Stage 1+2 ignited
Vostok_02.jpg|Stage 2 burn
Vostok_03.jpg|Stage 3 burn
Vostok_04.jpg|The TDU in orbit
Vostok_05.jpg|TDU details
Vostok_06.jpg|entry configuration
File:SOTM_2019-05_Cosmonaut_by_legoboyvdlp.jpg
</gallery>

== External links ==
* [http://en.wikipedia.org/wiki/Vostok_1 Wikipedia]

[[ru:Vostok-1]]

Vostok-1

2020-06-24T10:52:51Z

Vitos: /* Developer's message */

{{:{{PAGENAME}}/info}}
{{SpaceFlight}}

[[Image:Spacetripready.png|link=FlightGear_space_program]]

Vostok-1 was the first manned spaceflight in history, done by Yuri Gagarin in 1961. The launch vehicle was a Vostok-K rocket carrying the Vostok-3KA capsule.

While the historical space mission was under fully automatic control and Gagarin ejected from the capsule at an altitude of 7 km and parachuted to the ground, the simulation in Flightgear has to be flown manually and lands the capsule itself via parachutes. To that aim, an extra control panel to manage the various stages of the rocket which is not present in the real capsule has been added at the right side of the cockpit.

== Characteristics of the Vostok-K carrier ==

The Vostok-K is a three stage rocket. All three stages are powered by RP-1 (a kerosene-like rocket propellant) and liquid oxygene. It works partially with a parallel-burn concept.

The first stage consists of four boosters with a total thrust of 3,883.4 kN. They ignite in parallel with the second stage with a thrust of 912 kN.

The boosters have a burn time of about 118 seconds and are jettisoned when empty. In the later stages of the booster burn, the rocket can reach accelerations in excess of 4 g (the structural limit) and the engines need to be throttled back.

The second stage has a burn duration of 301 seconds and is also discarded when empty. Just as with the boosters, the acceleration may reach the structural limit towards the end of the burn as the tanks deplete.

The third stage has a much lower thrust of 54.5 kN leading to about 0.5 g acceleration. It is used to nudge the capsule into a stable orbit and has a burn duration of 365 seconds.

Control during ascent is provided by maneuvering thrusters rather than thrust vector control by gimbaling the main engines. As a result, Vostok's response to control input in powered flight is considerably less crisp than that of e.g. the Space Shuttle.

== Limits and damage ==

The modeling of Vostok includes structural limit checks. Upon ascent, the various parts of the rocket can break when overstressed either by too high dynamical pressure or g-forces. Often this leads to loss of control as the maneuver engines are not powerful enough to compensate for e.g. the loss of a booster and the resulting asymmetric thrust.

In addition, the pilot chute can tear off if deployed at too high dynamical pressure, just as the main chute and and the landing engine sensor.

For the detailed limits in all stages of the flight, please refer to the manual coming with the spacecraft.

== Automated launch ==

The spacecraft is equipped with a simple launch AP. This is (intentionally, to reflect the early spaceflight capabilities) made to be not precise and cannot be used for e.g. rendezvous targeting, but it can fly the capsule into a stable orbit. The target orbit can be specified in the menu, and the AP is capable of fully controlling the spacecraft right to third stage separation.

There is a one-way option provided to take over manually in case of an AP malfunction - note that controls can not be handed back to the autopilot.

== Simulation options ==

The simulation provides the options to make discarded stages simply vanish (easier on system resources) or to simulate them as they fall away or, in the case of third stage and TDU, orbit together with the spacecraft for a while.

For technical reasons, the option to simulate the drop of the boosters is really a startup option - the user selection will be autosaved and used upon next startup.

In addition, the simulation provides the option to automatically switch to the [[Earthview]] renderer when a certain altitude is reached and to switch back to the normal renderer when the spacecraft returns to Earth.

== Developer's message ==

Well, what can I say? You know what.

Real Vostok-1 was fully automated. The purpose of "Vostok-1" FG project, aside other things, is to give to You some understanding of spaceflight by giving to You full control from lift-off to landing. Perhaps there will be some automatic orbit and de-orbit in the future, but not now.

There are many things which would be realized. At now it's possible to "fly" around "Earth".

P.S. I could not and won't be responsible of what's going on with model after I had quit development of it since of conflict instead of friendship at 2011, when it was "now". As I made model GPL, whoever may do anything with it, and it's up to community which conflicted with idea of spaceflight then, and suddenly changed it's mind with "Shuttle" model development next, if it's not work way it should, not looks as it should, etc. Same with my "MiG-15" model. It's as really working thing would not work at news of some country, and it's not problem of people who made that thing.

If You mean some friendship, You may look at my "Su-15" model instead, which no-one with arguing/competitive/conflict mind having right to put hands on.

Wish to You good flight,

Victor Slavutinsky, vitosnet@mail.ru.

== Gallery ==

Current:

<gallery mode="packed">
Vostok-launch01.jpg|Stage 1+2 ignited
Vostok-launch02.jpg|Stage 2 burn
Vostok-launch03.jpg|Stage 2 separation, stage 3 ignited
Vostok-launch04.jpg|The TDU in orbit
Vostok-glow03.jpg|The capsule glowing from atmospheric friction
Vostok-glow05.jpg|The charred capsule hanging underneath the braking parachute
</gallery>

Historic:

<gallery mode="packed">
Vostok_01.jpg|Stage 1+2 ignited
Vostok_02.jpg|Stage 2 burn
Vostok_03.jpg|Stage 3 burn
Vostok_04.jpg|The TDU in orbit
Vostok_05.jpg|TDU details
Vostok_06.jpg|entry configuration
File:SOTM_2019-05_Cosmonaut_by_legoboyvdlp.jpg
</gallery>

== External links ==
* [http://en.wikipedia.org/wiki/Vostok_1 Wikipedia]

[[ru:Vostok-1]]

Vostok-1

2020-06-24T10:44:18Z

Vitos: /* Developer's message */

{{:{{PAGENAME}}/info}}
{{SpaceFlight}}

[[Image:Spacetripready.png|link=FlightGear_space_program]]

Vostok-1 was the first manned spaceflight in history, done by Yuri Gagarin in 1961. The launch vehicle was a Vostok-K rocket carrying the Vostok-3KA capsule.

While the historical space mission was under fully automatic control and Gagarin ejected from the capsule at an altitude of 7 km and parachuted to the ground, the simulation in Flightgear has to be flown manually and lands the capsule itself via parachutes. To that aim, an extra control panel to manage the various stages of the rocket which is not present in the real capsule has been added at the right side of the cockpit.

== Characteristics of the Vostok-K carrier ==

The Vostok-K is a three stage rocket. All three stages are powered by RP-1 (a kerosene-like rocket propellant) and liquid oxygene. It works partially with a parallel-burn concept.

The first stage consists of four boosters with a total thrust of 3,883.4 kN. They ignite in parallel with the second stage with a thrust of 912 kN.

The boosters have a burn time of about 118 seconds and are jettisoned when empty. In the later stages of the booster burn, the rocket can reach accelerations in excess of 4 g (the structural limit) and the engines need to be throttled back.

The second stage has a burn duration of 301 seconds and is also discarded when empty. Just as with the boosters, the acceleration may reach the structural limit towards the end of the burn as the tanks deplete.

The third stage has a much lower thrust of 54.5 kN leading to about 0.5 g acceleration. It is used to nudge the capsule into a stable orbit and has a burn duration of 365 seconds.

Control during ascent is provided by maneuvering thrusters rather than thrust vector control by gimbaling the main engines. As a result, Vostok's response to control input in powered flight is considerably less crisp than that of e.g. the Space Shuttle.

== Limits and damage ==

The modeling of Vostok includes structural limit checks. Upon ascent, the various parts of the rocket can break when overstressed either by too high dynamical pressure or g-forces. Often this leads to loss of control as the maneuver engines are not powerful enough to compensate for e.g. the loss of a booster and the resulting asymmetric thrust.

In addition, the pilot chute can tear off if deployed at too high dynamical pressure, just as the main chute and and the landing engine sensor.

For the detailed limits in all stages of the flight, please refer to the manual coming with the spacecraft.

== Automated launch ==

The spacecraft is equipped with a simple launch AP. This is (intentionally, to reflect the early spaceflight capabilities) made to be not precise and cannot be used for e.g. rendezvous targeting, but it can fly the capsule into a stable orbit. The target orbit can be specified in the menu, and the AP is capable of fully controlling the spacecraft right to third stage separation.

There is a one-way option provided to take over manually in case of an AP malfunction - note that controls can not be handed back to the autopilot.

== Simulation options ==

The simulation provides the options to make discarded stages simply vanish (easier on system resources) or to simulate them as they fall away or, in the case of third stage and TDU, orbit together with the spacecraft for a while.

For technical reasons, the option to simulate the drop of the boosters is really a startup option - the user selection will be autosaved and used upon next startup.

In addition, the simulation provides the option to automatically switch to the [[Earthview]] renderer when a certain altitude is reached and to switch back to the normal renderer when the spacecraft returns to Earth.

== Developer's message ==

Well, what can I say? You know what.

Real Vostok-1 was fully automated. The purpose of "Vostok-1" FG project, aside other things, is to give to You some understanding of spaceflight by giving to You full control from lift-off to landing. Perhaps there will be some automatic orbit and de-orbit in the future, but not now.

There are many things which would be realized. At now it's possible to "fly" around "Earth".

P.S. I could not and won't be responsible of what's going on with model after I had quit development of it since of conflict instead of friendship at 2011, when it was "now". As I made model GPL, whoever may do anything with it, and it's up to community which conflicted with idea of spaceflight then, and suddenly changed it's mind with Shuttle development next, if it's not work way it should, not looks as it should, etc. Same with my MiG-15 model. It's as really working thing would not work at news of some country, and it's not problem of people who made that thing.

If You mean some friendship, You may look at my Su-15 model instead, which no-one with arguing/competitive/conflict mind having right to put hands on.

Wish to You good flight,

Victor Slavutinsky, vitosnet@mail.ru.

== Gallery ==

Current:

<gallery mode="packed">
Vostok-launch01.jpg|Stage 1+2 ignited
Vostok-launch02.jpg|Stage 2 burn
Vostok-launch03.jpg|Stage 2 separation, stage 3 ignited
Vostok-launch04.jpg|The TDU in orbit
Vostok-glow03.jpg|The capsule glowing from atmospheric friction
Vostok-glow05.jpg|The charred capsule hanging underneath the braking parachute
</gallery>

Historic:

<gallery mode="packed">
Vostok_01.jpg|Stage 1+2 ignited
Vostok_02.jpg|Stage 2 burn
Vostok_03.jpg|Stage 3 burn
Vostok_04.jpg|The TDU in orbit
Vostok_05.jpg|TDU details
Vostok_06.jpg|entry configuration
File:SOTM_2019-05_Cosmonaut_by_legoboyvdlp.jpg
</gallery>

== External links ==
* [http://en.wikipedia.org/wiki/Vostok_1 Wikipedia]

[[ru:Vostok-1]]

Vostok-1

2020-06-24T10:35:10Z

Vitos: /* Developer's message */

{{:{{PAGENAME}}/info}}
{{SpaceFlight}}

[[Image:Spacetripready.png|link=FlightGear_space_program]]

Vostok-1 was the first manned spaceflight in history, done by Yuri Gagarin in 1961. The launch vehicle was a Vostok-K rocket carrying the Vostok-3KA capsule.

While the historical space mission was under fully automatic control and Gagarin ejected from the capsule at an altitude of 7 km and parachuted to the ground, the simulation in Flightgear has to be flown manually and lands the capsule itself via parachutes. To that aim, an extra control panel to manage the various stages of the rocket which is not present in the real capsule has been added at the right side of the cockpit.

== Characteristics of the Vostok-K carrier ==

The Vostok-K is a three stage rocket. All three stages are powered by RP-1 (a kerosene-like rocket propellant) and liquid oxygene. It works partially with a parallel-burn concept.

The first stage consists of four boosters with a total thrust of 3,883.4 kN. They ignite in parallel with the second stage with a thrust of 912 kN.

The boosters have a burn time of about 118 seconds and are jettisoned when empty. In the later stages of the booster burn, the rocket can reach accelerations in excess of 4 g (the structural limit) and the engines need to be throttled back.

The second stage has a burn duration of 301 seconds and is also discarded when empty. Just as with the boosters, the acceleration may reach the structural limit towards the end of the burn as the tanks deplete.

The third stage has a much lower thrust of 54.5 kN leading to about 0.5 g acceleration. It is used to nudge the capsule into a stable orbit and has a burn duration of 365 seconds.

Control during ascent is provided by maneuvering thrusters rather than thrust vector control by gimbaling the main engines. As a result, Vostok's response to control input in powered flight is considerably less crisp than that of e.g. the Space Shuttle.

== Limits and damage ==

The modeling of Vostok includes structural limit checks. Upon ascent, the various parts of the rocket can break when overstressed either by too high dynamical pressure or g-forces. Often this leads to loss of control as the maneuver engines are not powerful enough to compensate for e.g. the loss of a booster and the resulting asymmetric thrust.

In addition, the pilot chute can tear off if deployed at too high dynamical pressure, just as the main chute and and the landing engine sensor.

For the detailed limits in all stages of the flight, please refer to the manual coming with the spacecraft.

== Automated launch ==

The spacecraft is equipped with a simple launch AP. This is (intentionally, to reflect the early spaceflight capabilities) made to be not precise and cannot be used for e.g. rendezvous targeting, but it can fly the capsule into a stable orbit. The target orbit can be specified in the menu, and the AP is capable of fully controlling the spacecraft right to third stage separation.

There is a one-way option provided to take over manually in case of an AP malfunction - note that controls can not be handed back to the autopilot.

== Simulation options ==

The simulation provides the options to make discarded stages simply vanish (easier on system resources) or to simulate them as they fall away or, in the case of third stage and TDU, orbit together with the spacecraft for a while.

For technical reasons, the option to simulate the drop of the boosters is really a startup option - the user selection will be autosaved and used upon next startup.

In addition, the simulation provides the option to automatically switch to the [[Earthview]] renderer when a certain altitude is reached and to switch back to the normal renderer when the spacecraft returns to Earth.

== Developer's message ==

Well, what can I say? You know what.

Real Vostok-1 was fully automated. The purpose of "Vostok-1" FG project, aside other things, is to give to You some understanding of spaceflight by giving to You full control from lift-off to landing. Perhaps there will be some automatic orbit and de-orbit in the future, but not now.

There are many things which would be realized. At now it's possible to "fly" around "Earth".

P.S. I could not and won't be responsible of what's going on with model after I had quit development of it since of conflict instead of friendship at 2011, when it was "now". As I made model GPL, whoever may do anything with it, and it's up to community which conflicted with idea of spaceflight then, and suddenly changed it's mind with Shuttle development next, if it's not work way it should, not looks as it should, etc. Same with my MiG-15 model. If You mean some friendship, You may look at my Su-15 model instead, which no-one with arguing/competitive/conflict mind having right to put hands on.

Wish to You good flight,

Victor Slavutinsky, vitosnet@mail.ru.

== Gallery ==

Current:

<gallery mode="packed">
Vostok-launch01.jpg|Stage 1+2 ignited
Vostok-launch02.jpg|Stage 2 burn
Vostok-launch03.jpg|Stage 2 separation, stage 3 ignited
Vostok-launch04.jpg|The TDU in orbit
Vostok-glow03.jpg|The capsule glowing from atmospheric friction
Vostok-glow05.jpg|The charred capsule hanging underneath the braking parachute
</gallery>

Historic:

<gallery mode="packed">
Vostok_01.jpg|Stage 1+2 ignited
Vostok_02.jpg|Stage 2 burn
Vostok_03.jpg|Stage 3 burn
Vostok_04.jpg|The TDU in orbit
Vostok_05.jpg|TDU details
Vostok_06.jpg|entry configuration
File:SOTM_2019-05_Cosmonaut_by_legoboyvdlp.jpg
</gallery>

== External links ==
* [http://en.wikipedia.org/wiki/Vostok_1 Wikipedia]

[[ru:Vostok-1]]

Vostok-1

2020-06-24T10:33:59Z

Vitos: /* Developer's message */

{{:{{PAGENAME}}/info}}
{{SpaceFlight}}

[[Image:Spacetripready.png|link=FlightGear_space_program]]

Vostok-1 was the first manned spaceflight in history, done by Yuri Gagarin in 1961. The launch vehicle was a Vostok-K rocket carrying the Vostok-3KA capsule.

While the historical space mission was under fully automatic control and Gagarin ejected from the capsule at an altitude of 7 km and parachuted to the ground, the simulation in Flightgear has to be flown manually and lands the capsule itself via parachutes. To that aim, an extra control panel to manage the various stages of the rocket which is not present in the real capsule has been added at the right side of the cockpit.

== Characteristics of the Vostok-K carrier ==

The Vostok-K is a three stage rocket. All three stages are powered by RP-1 (a kerosene-like rocket propellant) and liquid oxygene. It works partially with a parallel-burn concept.

The first stage consists of four boosters with a total thrust of 3,883.4 kN. They ignite in parallel with the second stage with a thrust of 912 kN.

The boosters have a burn time of about 118 seconds and are jettisoned when empty. In the later stages of the booster burn, the rocket can reach accelerations in excess of 4 g (the structural limit) and the engines need to be throttled back.

The second stage has a burn duration of 301 seconds and is also discarded when empty. Just as with the boosters, the acceleration may reach the structural limit towards the end of the burn as the tanks deplete.

The third stage has a much lower thrust of 54.5 kN leading to about 0.5 g acceleration. It is used to nudge the capsule into a stable orbit and has a burn duration of 365 seconds.

Control during ascent is provided by maneuvering thrusters rather than thrust vector control by gimbaling the main engines. As a result, Vostok's response to control input in powered flight is considerably less crisp than that of e.g. the Space Shuttle.

== Limits and damage ==

The modeling of Vostok includes structural limit checks. Upon ascent, the various parts of the rocket can break when overstressed either by too high dynamical pressure or g-forces. Often this leads to loss of control as the maneuver engines are not powerful enough to compensate for e.g. the loss of a booster and the resulting asymmetric thrust.

In addition, the pilot chute can tear off if deployed at too high dynamical pressure, just as the main chute and and the landing engine sensor.

For the detailed limits in all stages of the flight, please refer to the manual coming with the spacecraft.

== Automated launch ==

The spacecraft is equipped with a simple launch AP. This is (intentionally, to reflect the early spaceflight capabilities) made to be not precise and cannot be used for e.g. rendezvous targeting, but it can fly the capsule into a stable orbit. The target orbit can be specified in the menu, and the AP is capable of fully controlling the spacecraft right to third stage separation.

There is a one-way option provided to take over manually in case of an AP malfunction - note that controls can not be handed back to the autopilot.

== Simulation options ==

The simulation provides the options to make discarded stages simply vanish (easier on system resources) or to simulate them as they fall away or, in the case of third stage and TDU, orbit together with the spacecraft for a while.

For technical reasons, the option to simulate the drop of the boosters is really a startup option - the user selection will be autosaved and used upon next startup.

In addition, the simulation provides the option to automatically switch to the [[Earthview]] renderer when a certain altitude is reached and to switch back to the normal renderer when the spacecraft returns to Earth.

== Developer's message ==

Well, what can I say? You know what.

Real Vostok-1 was fully automated. The purpose of "Vostok-1" FG project, aside other things, is to give to You some understanding of spaceflight by giving to You full control from lift-off to landing. Perhaps there will be some automatic orbit and de-orbit in the future, but not now.

There are many things which would be realized. At now it's possible to "fly" around "Earth".

P.S. I could not and won't be responsible of what's going on with model after I had quit development of it since of conflict instead of friendship at 2011, when it was "now". As I made model GPL, whoever may do anything with it, and it's up to community which conflicted with idea of spaceflight then, and suddenly changed it's mind with Shuttle development next, if it's not work way it should, not looks as it should, etc. Same with my MiG-15 model. If You mean some friendship, You may look at my Su-15 model instead, which no-one with arguing mind having right to put hands on.

Wish to You good flight,

Victor Slavutinsky, vitosnet@mail.ru.

== Gallery ==

Current:

<gallery mode="packed">
Vostok-launch01.jpg|Stage 1+2 ignited
Vostok-launch02.jpg|Stage 2 burn
Vostok-launch03.jpg|Stage 2 separation, stage 3 ignited
Vostok-launch04.jpg|The TDU in orbit
Vostok-glow03.jpg|The capsule glowing from atmospheric friction
Vostok-glow05.jpg|The charred capsule hanging underneath the braking parachute
</gallery>

Historic:

<gallery mode="packed">
Vostok_01.jpg|Stage 1+2 ignited
Vostok_02.jpg|Stage 2 burn
Vostok_03.jpg|Stage 3 burn
Vostok_04.jpg|The TDU in orbit
Vostok_05.jpg|TDU details
Vostok_06.jpg|entry configuration
File:SOTM_2019-05_Cosmonaut_by_legoboyvdlp.jpg
</gallery>

== External links ==
* [http://en.wikipedia.org/wiki/Vostok_1 Wikipedia]

[[ru:Vostok-1]]

Vostok-1

2020-06-24T10:33:36Z

Vitos: /* Developer's message */

{{:{{PAGENAME}}/info}}
{{SpaceFlight}}

[[Image:Spacetripready.png|link=FlightGear_space_program]]

Vostok-1 was the first manned spaceflight in history, done by Yuri Gagarin in 1961. The launch vehicle was a Vostok-K rocket carrying the Vostok-3KA capsule.

While the historical space mission was under fully automatic control and Gagarin ejected from the capsule at an altitude of 7 km and parachuted to the ground, the simulation in Flightgear has to be flown manually and lands the capsule itself via parachutes. To that aim, an extra control panel to manage the various stages of the rocket which is not present in the real capsule has been added at the right side of the cockpit.

== Characteristics of the Vostok-K carrier ==

The Vostok-K is a three stage rocket. All three stages are powered by RP-1 (a kerosene-like rocket propellant) and liquid oxygene. It works partially with a parallel-burn concept.

The first stage consists of four boosters with a total thrust of 3,883.4 kN. They ignite in parallel with the second stage with a thrust of 912 kN.

The boosters have a burn time of about 118 seconds and are jettisoned when empty. In the later stages of the booster burn, the rocket can reach accelerations in excess of 4 g (the structural limit) and the engines need to be throttled back.

The second stage has a burn duration of 301 seconds and is also discarded when empty. Just as with the boosters, the acceleration may reach the structural limit towards the end of the burn as the tanks deplete.

The third stage has a much lower thrust of 54.5 kN leading to about 0.5 g acceleration. It is used to nudge the capsule into a stable orbit and has a burn duration of 365 seconds.

Control during ascent is provided by maneuvering thrusters rather than thrust vector control by gimbaling the main engines. As a result, Vostok's response to control input in powered flight is considerably less crisp than that of e.g. the Space Shuttle.

== Limits and damage ==

The modeling of Vostok includes structural limit checks. Upon ascent, the various parts of the rocket can break when overstressed either by too high dynamical pressure or g-forces. Often this leads to loss of control as the maneuver engines are not powerful enough to compensate for e.g. the loss of a booster and the resulting asymmetric thrust.

In addition, the pilot chute can tear off if deployed at too high dynamical pressure, just as the main chute and and the landing engine sensor.

For the detailed limits in all stages of the flight, please refer to the manual coming with the spacecraft.

== Automated launch ==

The spacecraft is equipped with a simple launch AP. This is (intentionally, to reflect the early spaceflight capabilities) made to be not precise and cannot be used for e.g. rendezvous targeting, but it can fly the capsule into a stable orbit. The target orbit can be specified in the menu, and the AP is capable of fully controlling the spacecraft right to third stage separation.

There is a one-way option provided to take over manually in case of an AP malfunction - note that controls can not be handed back to the autopilot.

== Simulation options ==

The simulation provides the options to make discarded stages simply vanish (easier on system resources) or to simulate them as they fall away or, in the case of third stage and TDU, orbit together with the spacecraft for a while.

For technical reasons, the option to simulate the drop of the boosters is really a startup option - the user selection will be autosaved and used upon next startup.

In addition, the simulation provides the option to automatically switch to the [[Earthview]] renderer when a certain altitude is reached and to switch back to the normal renderer when the spacecraft returns to Earth.

== Developer's message ==

Well, what can I say? You know what.

Real Vostok-1 was fully automated. The purpose of "Vostok-1" FG project, aside other things, is to give to You some understanding of spaceflight by giving to You full control from lift-off to landing. Perhaps there will be some automatic orbit and de-orbit in the future, but not now.

There are many things which would be realized. At now it's possible to "fly" around "Earth".

P.S. I could not and won't be responsible of what's going on with model after I had quit development of it since of conflict instead of friendship at 2011, when it was "now". As I made model GPL, whoever may do anything with it, and it's up to community which conflicted with idea of spaceflight then, and suddenly changed it's mind with Shuttle development next, if it's not work way it should, not looks as it should, etc. Same with my MiG-15 model. If You mean some friendship, You may look at my Su-15 model instead, which no-one with arguing mind had right to put hands on.

Wish to You good flight,

Victor Slavutinsky, vitosnet@mail.ru.

== Gallery ==

Current:

<gallery mode="packed">
Vostok-launch01.jpg|Stage 1+2 ignited
Vostok-launch02.jpg|Stage 2 burn
Vostok-launch03.jpg|Stage 2 separation, stage 3 ignited
Vostok-launch04.jpg|The TDU in orbit
Vostok-glow03.jpg|The capsule glowing from atmospheric friction
Vostok-glow05.jpg|The charred capsule hanging underneath the braking parachute
</gallery>

Historic:

<gallery mode="packed">
Vostok_01.jpg|Stage 1+2 ignited
Vostok_02.jpg|Stage 2 burn
Vostok_03.jpg|Stage 3 burn
Vostok_04.jpg|The TDU in orbit
Vostok_05.jpg|TDU details
Vostok_06.jpg|entry configuration
File:SOTM_2019-05_Cosmonaut_by_legoboyvdlp.jpg
</gallery>

== External links ==
* [http://en.wikipedia.org/wiki/Vostok_1 Wikipedia]

[[ru:Vostok-1]]

Vostok-1

2020-06-24T10:29:35Z

Vitos: /* Developer's message */

{{:{{PAGENAME}}/info}}
{{SpaceFlight}}

[[Image:Spacetripready.png|link=FlightGear_space_program]]

Vostok-1 was the first manned spaceflight in history, done by Yuri Gagarin in 1961. The launch vehicle was a Vostok-K rocket carrying the Vostok-3KA capsule.

While the historical space mission was under fully automatic control and Gagarin ejected from the capsule at an altitude of 7 km and parachuted to the ground, the simulation in Flightgear has to be flown manually and lands the capsule itself via parachutes. To that aim, an extra control panel to manage the various stages of the rocket which is not present in the real capsule has been added at the right side of the cockpit.

== Characteristics of the Vostok-K carrier ==

The Vostok-K is a three stage rocket. All three stages are powered by RP-1 (a kerosene-like rocket propellant) and liquid oxygene. It works partially with a parallel-burn concept.

The first stage consists of four boosters with a total thrust of 3,883.4 kN. They ignite in parallel with the second stage with a thrust of 912 kN.

The boosters have a burn time of about 118 seconds and are jettisoned when empty. In the later stages of the booster burn, the rocket can reach accelerations in excess of 4 g (the structural limit) and the engines need to be throttled back.

The second stage has a burn duration of 301 seconds and is also discarded when empty. Just as with the boosters, the acceleration may reach the structural limit towards the end of the burn as the tanks deplete.

The third stage has a much lower thrust of 54.5 kN leading to about 0.5 g acceleration. It is used to nudge the capsule into a stable orbit and has a burn duration of 365 seconds.

Control during ascent is provided by maneuvering thrusters rather than thrust vector control by gimbaling the main engines. As a result, Vostok's response to control input in powered flight is considerably less crisp than that of e.g. the Space Shuttle.

== Limits and damage ==

The modeling of Vostok includes structural limit checks. Upon ascent, the various parts of the rocket can break when overstressed either by too high dynamical pressure or g-forces. Often this leads to loss of control as the maneuver engines are not powerful enough to compensate for e.g. the loss of a booster and the resulting asymmetric thrust.

In addition, the pilot chute can tear off if deployed at too high dynamical pressure, just as the main chute and and the landing engine sensor.

For the detailed limits in all stages of the flight, please refer to the manual coming with the spacecraft.

== Automated launch ==

The spacecraft is equipped with a simple launch AP. This is (intentionally, to reflect the early spaceflight capabilities) made to be not precise and cannot be used for e.g. rendezvous targeting, but it can fly the capsule into a stable orbit. The target orbit can be specified in the menu, and the AP is capable of fully controlling the spacecraft right to third stage separation.

There is a one-way option provided to take over manually in case of an AP malfunction - note that controls can not be handed back to the autopilot.

== Simulation options ==

The simulation provides the options to make discarded stages simply vanish (easier on system resources) or to simulate them as they fall away or, in the case of third stage and TDU, orbit together with the spacecraft for a while.

For technical reasons, the option to simulate the drop of the boosters is really a startup option - the user selection will be autosaved and used upon next startup.

In addition, the simulation provides the option to automatically switch to the [[Earthview]] renderer when a certain altitude is reached and to switch back to the normal renderer when the spacecraft returns to Earth.

== Developer's message ==

Well, what can I say? You know what.

Real Vostok-1 was fully automated. The purpose of "Vostok-1" FG project, aside other things, is to give to You some understanding of spaceflight by giving to You full control from lift-off to landing. Perhaps there will be some automatic orbit and de-orbit in the future, but not now.

There are many things which would be realized. At now it's possible to "fly" around "Earth".

P.S. I could not and won't be responsible of what's going on with model after I had quit development of it since of conflict instead of friendship at 2011, when it was "now". As I made model GPL, whoever may do anything with it, and it's up to community which conflicted with idea of spaceflight then, and suddenly changed it's mind with Shuttle development next, if it's not work way it should, not looks as it should, etc. Same with my MiG-15 model. If You mean some friendship, You may look at my Su-15 model instead.

Wish to You good flight,

Victor Slavutinsky, vitosnet@mail.ru.

== Gallery ==

Current:

<gallery mode="packed">
Vostok-launch01.jpg|Stage 1+2 ignited
Vostok-launch02.jpg|Stage 2 burn
Vostok-launch03.jpg|Stage 2 separation, stage 3 ignited
Vostok-launch04.jpg|The TDU in orbit
Vostok-glow03.jpg|The capsule glowing from atmospheric friction
Vostok-glow05.jpg|The charred capsule hanging underneath the braking parachute
</gallery>

Historic:

<gallery mode="packed">
Vostok_01.jpg|Stage 1+2 ignited
Vostok_02.jpg|Stage 2 burn
Vostok_03.jpg|Stage 3 burn
Vostok_04.jpg|The TDU in orbit
Vostok_05.jpg|TDU details
Vostok_06.jpg|entry configuration
File:SOTM_2019-05_Cosmonaut_by_legoboyvdlp.jpg
</gallery>

== External links ==
* [http://en.wikipedia.org/wiki/Vostok_1 Wikipedia]

[[ru:Vostok-1]]

Vostok-1

2020-06-24T10:26:54Z

Vitos: /* Developer's message */

{{:{{PAGENAME}}/info}}
{{SpaceFlight}}

[[Image:Spacetripready.png|link=FlightGear_space_program]]

Vostok-1 was the first manned spaceflight in history, done by Yuri Gagarin in 1961. The launch vehicle was a Vostok-K rocket carrying the Vostok-3KA capsule.

While the historical space mission was under fully automatic control and Gagarin ejected from the capsule at an altitude of 7 km and parachuted to the ground, the simulation in Flightgear has to be flown manually and lands the capsule itself via parachutes. To that aim, an extra control panel to manage the various stages of the rocket which is not present in the real capsule has been added at the right side of the cockpit.

== Characteristics of the Vostok-K carrier ==

The Vostok-K is a three stage rocket. All three stages are powered by RP-1 (a kerosene-like rocket propellant) and liquid oxygene. It works partially with a parallel-burn concept.

The first stage consists of four boosters with a total thrust of 3,883.4 kN. They ignite in parallel with the second stage with a thrust of 912 kN.

The boosters have a burn time of about 118 seconds and are jettisoned when empty. In the later stages of the booster burn, the rocket can reach accelerations in excess of 4 g (the structural limit) and the engines need to be throttled back.

The second stage has a burn duration of 301 seconds and is also discarded when empty. Just as with the boosters, the acceleration may reach the structural limit towards the end of the burn as the tanks deplete.

The third stage has a much lower thrust of 54.5 kN leading to about 0.5 g acceleration. It is used to nudge the capsule into a stable orbit and has a burn duration of 365 seconds.

Control during ascent is provided by maneuvering thrusters rather than thrust vector control by gimbaling the main engines. As a result, Vostok's response to control input in powered flight is considerably less crisp than that of e.g. the Space Shuttle.

== Limits and damage ==

The modeling of Vostok includes structural limit checks. Upon ascent, the various parts of the rocket can break when overstressed either by too high dynamical pressure or g-forces. Often this leads to loss of control as the maneuver engines are not powerful enough to compensate for e.g. the loss of a booster and the resulting asymmetric thrust.

In addition, the pilot chute can tear off if deployed at too high dynamical pressure, just as the main chute and and the landing engine sensor.

For the detailed limits in all stages of the flight, please refer to the manual coming with the spacecraft.

== Automated launch ==

The spacecraft is equipped with a simple launch AP. This is (intentionally, to reflect the early spaceflight capabilities) made to be not precise and cannot be used for e.g. rendezvous targeting, but it can fly the capsule into a stable orbit. The target orbit can be specified in the menu, and the AP is capable of fully controlling the spacecraft right to third stage separation.

There is a one-way option provided to take over manually in case of an AP malfunction - note that controls can not be handed back to the autopilot.

== Simulation options ==

The simulation provides the options to make discarded stages simply vanish (easier on system resources) or to simulate them as they fall away or, in the case of third stage and TDU, orbit together with the spacecraft for a while.

For technical reasons, the option to simulate the drop of the boosters is really a startup option - the user selection will be autosaved and used upon next startup.

In addition, the simulation provides the option to automatically switch to the [[Earthview]] renderer when a certain altitude is reached and to switch back to the normal renderer when the spacecraft returns to Earth.

== Developer's message ==

Well, what can I say? You know what.

Real Vostok-1 was fully automated. The purpose of "Vostok-1" FG project, aside other things, is to give to You some understanding of spaceflight by giving to You full control from lift-off to landing. Perhaps there will be some automatic orbit and de-orbit in the future, but not now.

There are many things which would be realized. At now it's possible to "fly" around "Earth".

P.S. I could not and won't be responsible of what's going on with model after I had quit development of it since of conflict instead of friendship at 2011, when it was "now". As I made model GPL, whoever may do anything with it, and it's up to community which conflicted with idea of spaceflight then, if it's not work way it should, not looks as it should, etc. Same with my MiG-15 model. If You mean some friendship, You may look at my Su-15 model instead.

Wish to You good flight,

Victor Slavutinsky, vitosnet@mail.ru.

== Gallery ==

Current:

<gallery mode="packed">
Vostok-launch01.jpg|Stage 1+2 ignited
Vostok-launch02.jpg|Stage 2 burn
Vostok-launch03.jpg|Stage 2 separation, stage 3 ignited
Vostok-launch04.jpg|The TDU in orbit
Vostok-glow03.jpg|The capsule glowing from atmospheric friction
Vostok-glow05.jpg|The charred capsule hanging underneath the braking parachute
</gallery>

Historic:

<gallery mode="packed">
Vostok_01.jpg|Stage 1+2 ignited
Vostok_02.jpg|Stage 2 burn
Vostok_03.jpg|Stage 3 burn
Vostok_04.jpg|The TDU in orbit
Vostok_05.jpg|TDU details
Vostok_06.jpg|entry configuration
File:SOTM_2019-05_Cosmonaut_by_legoboyvdlp.jpg
</gallery>

== External links ==
* [http://en.wikipedia.org/wiki/Vostok_1 Wikipedia]

[[ru:Vostok-1]]

Vostok-1

2020-06-24T10:24:50Z

Vitos: /* Developer's message */

{{:{{PAGENAME}}/info}}
{{SpaceFlight}}

[[Image:Spacetripready.png|link=FlightGear_space_program]]

Vostok-1 was the first manned spaceflight in history, done by Yuri Gagarin in 1961. The launch vehicle was a Vostok-K rocket carrying the Vostok-3KA capsule.

While the historical space mission was under fully automatic control and Gagarin ejected from the capsule at an altitude of 7 km and parachuted to the ground, the simulation in Flightgear has to be flown manually and lands the capsule itself via parachutes. To that aim, an extra control panel to manage the various stages of the rocket which is not present in the real capsule has been added at the right side of the cockpit.

== Characteristics of the Vostok-K carrier ==

The Vostok-K is a three stage rocket. All three stages are powered by RP-1 (a kerosene-like rocket propellant) and liquid oxygene. It works partially with a parallel-burn concept.

The first stage consists of four boosters with a total thrust of 3,883.4 kN. They ignite in parallel with the second stage with a thrust of 912 kN.

The boosters have a burn time of about 118 seconds and are jettisoned when empty. In the later stages of the booster burn, the rocket can reach accelerations in excess of 4 g (the structural limit) and the engines need to be throttled back.

The second stage has a burn duration of 301 seconds and is also discarded when empty. Just as with the boosters, the acceleration may reach the structural limit towards the end of the burn as the tanks deplete.

The third stage has a much lower thrust of 54.5 kN leading to about 0.5 g acceleration. It is used to nudge the capsule into a stable orbit and has a burn duration of 365 seconds.

Control during ascent is provided by maneuvering thrusters rather than thrust vector control by gimbaling the main engines. As a result, Vostok's response to control input in powered flight is considerably less crisp than that of e.g. the Space Shuttle.

== Limits and damage ==

The modeling of Vostok includes structural limit checks. Upon ascent, the various parts of the rocket can break when overstressed either by too high dynamical pressure or g-forces. Often this leads to loss of control as the maneuver engines are not powerful enough to compensate for e.g. the loss of a booster and the resulting asymmetric thrust.

In addition, the pilot chute can tear off if deployed at too high dynamical pressure, just as the main chute and and the landing engine sensor.

For the detailed limits in all stages of the flight, please refer to the manual coming with the spacecraft.

== Automated launch ==

The spacecraft is equipped with a simple launch AP. This is (intentionally, to reflect the early spaceflight capabilities) made to be not precise and cannot be used for e.g. rendezvous targeting, but it can fly the capsule into a stable orbit. The target orbit can be specified in the menu, and the AP is capable of fully controlling the spacecraft right to third stage separation.

There is a one-way option provided to take over manually in case of an AP malfunction - note that controls can not be handed back to the autopilot.

== Simulation options ==

The simulation provides the options to make discarded stages simply vanish (easier on system resources) or to simulate them as they fall away or, in the case of third stage and TDU, orbit together with the spacecraft for a while.

For technical reasons, the option to simulate the drop of the boosters is really a startup option - the user selection will be autosaved and used upon next startup.

In addition, the simulation provides the option to automatically switch to the [[Earthview]] renderer when a certain altitude is reached and to switch back to the normal renderer when the spacecraft returns to Earth.

== Developer's message ==

Well, what can I say? You know what.

Real Vostok-1 was fully automated. The purpose of "Vostok-1" FG project, aside other things, is to give to You some understanding of spaceflight by giving to You full control from lift-off to landing. Perhaps there will be some automatic orbit and de-orbit in the future, but not now.

There are many things which would be realized. At now it's possible to "fly" around "Earth".

P.S. I could not and won't be responsible of what's going on with model after I had quit development of it since of conflict instead of friendship at 2011, when it was "now". As I made model GPL, whoever may do anything with it, and it's up to community which conflicted with idea of spaceflight then, if it's not work way it should, not looks as it should, etc. If You mean some friendship, You may look at my Su-15 model instead.

Wish to You good flight,

Victor Slavutinsky, vitosnet@mail.ru.

== Gallery ==

Current:

<gallery mode="packed">
Vostok-launch01.jpg|Stage 1+2 ignited
Vostok-launch02.jpg|Stage 2 burn
Vostok-launch03.jpg|Stage 2 separation, stage 3 ignited
Vostok-launch04.jpg|The TDU in orbit
Vostok-glow03.jpg|The capsule glowing from atmospheric friction
Vostok-glow05.jpg|The charred capsule hanging underneath the braking parachute
</gallery>

Historic:

<gallery mode="packed">
Vostok_01.jpg|Stage 1+2 ignited
Vostok_02.jpg|Stage 2 burn
Vostok_03.jpg|Stage 3 burn
Vostok_04.jpg|The TDU in orbit
Vostok_05.jpg|TDU details
Vostok_06.jpg|entry configuration
File:SOTM_2019-05_Cosmonaut_by_legoboyvdlp.jpg
</gallery>

== External links ==
* [http://en.wikipedia.org/wiki/Vostok_1 Wikipedia]

[[ru:Vostok-1]]

Vostok-1

2020-06-24T10:23:06Z

Vitos: /* Developer's message */

{{:{{PAGENAME}}/info}}
{{SpaceFlight}}

[[Image:Spacetripready.png|link=FlightGear_space_program]]

Vostok-1 was the first manned spaceflight in history, done by Yuri Gagarin in 1961. The launch vehicle was a Vostok-K rocket carrying the Vostok-3KA capsule.

While the historical space mission was under fully automatic control and Gagarin ejected from the capsule at an altitude of 7 km and parachuted to the ground, the simulation in Flightgear has to be flown manually and lands the capsule itself via parachutes. To that aim, an extra control panel to manage the various stages of the rocket which is not present in the real capsule has been added at the right side of the cockpit.

== Characteristics of the Vostok-K carrier ==

The Vostok-K is a three stage rocket. All three stages are powered by RP-1 (a kerosene-like rocket propellant) and liquid oxygene. It works partially with a parallel-burn concept.

The first stage consists of four boosters with a total thrust of 3,883.4 kN. They ignite in parallel with the second stage with a thrust of 912 kN.

The boosters have a burn time of about 118 seconds and are jettisoned when empty. In the later stages of the booster burn, the rocket can reach accelerations in excess of 4 g (the structural limit) and the engines need to be throttled back.

The second stage has a burn duration of 301 seconds and is also discarded when empty. Just as with the boosters, the acceleration may reach the structural limit towards the end of the burn as the tanks deplete.

The third stage has a much lower thrust of 54.5 kN leading to about 0.5 g acceleration. It is used to nudge the capsule into a stable orbit and has a burn duration of 365 seconds.

Control during ascent is provided by maneuvering thrusters rather than thrust vector control by gimbaling the main engines. As a result, Vostok's response to control input in powered flight is considerably less crisp than that of e.g. the Space Shuttle.

== Limits and damage ==

The modeling of Vostok includes structural limit checks. Upon ascent, the various parts of the rocket can break when overstressed either by too high dynamical pressure or g-forces. Often this leads to loss of control as the maneuver engines are not powerful enough to compensate for e.g. the loss of a booster and the resulting asymmetric thrust.

In addition, the pilot chute can tear off if deployed at too high dynamical pressure, just as the main chute and and the landing engine sensor.

For the detailed limits in all stages of the flight, please refer to the manual coming with the spacecraft.

== Automated launch ==

The spacecraft is equipped with a simple launch AP. This is (intentionally, to reflect the early spaceflight capabilities) made to be not precise and cannot be used for e.g. rendezvous targeting, but it can fly the capsule into a stable orbit. The target orbit can be specified in the menu, and the AP is capable of fully controlling the spacecraft right to third stage separation.

There is a one-way option provided to take over manually in case of an AP malfunction - note that controls can not be handed back to the autopilot.

== Simulation options ==

The simulation provides the options to make discarded stages simply vanish (easier on system resources) or to simulate them as they fall away or, in the case of third stage and TDU, orbit together with the spacecraft for a while.

For technical reasons, the option to simulate the drop of the boosters is really a startup option - the user selection will be autosaved and used upon next startup.

In addition, the simulation provides the option to automatically switch to the [[Earthview]] renderer when a certain altitude is reached and to switch back to the normal renderer when the spacecraft returns to Earth.

== Developer's message ==

Well, what can I say? You know what.

Real Vostok-1 was fully automated. The purpose of "Vostok-1" FG project, aside other things, is to give to You some understanding of spaceflight by giving to You full control from lift-off to landing. Perhaps there will be some automatic orbit and de-orbit in the future, but not now.

There are many things which would be realized. At now it's possible to "fly" around "Earth".

P.S. I could not and won't be responsible of what's going on with model after I had quit development of it since of conflict instead of friendship at 2011, when it was "now". As I made model GPL, it's up to community which conflicted with idea of spaceflight then, if it's not work way it should, not looks as it should, etc. If You mean some friendship, You may look at my Su-15 model instead.

Wish to You good flight,

Victor Slavutinsky, vitosnet@mail.ru.

== Gallery ==

Current:

<gallery mode="packed">
Vostok-launch01.jpg|Stage 1+2 ignited
Vostok-launch02.jpg|Stage 2 burn
Vostok-launch03.jpg|Stage 2 separation, stage 3 ignited
Vostok-launch04.jpg|The TDU in orbit
Vostok-glow03.jpg|The capsule glowing from atmospheric friction
Vostok-glow05.jpg|The charred capsule hanging underneath the braking parachute
</gallery>

Historic:

<gallery mode="packed">
Vostok_01.jpg|Stage 1+2 ignited
Vostok_02.jpg|Stage 2 burn
Vostok_03.jpg|Stage 3 burn
Vostok_04.jpg|The TDU in orbit
Vostok_05.jpg|TDU details
Vostok_06.jpg|entry configuration
File:SOTM_2019-05_Cosmonaut_by_legoboyvdlp.jpg
</gallery>

== External links ==
* [http://en.wikipedia.org/wiki/Vostok_1 Wikipedia]

[[ru:Vostok-1]]

Sukhoi Su-15

2020-06-14T06:28:52Z

Vitos: /* Features */

{{:{{PAGENAME}}/info}}

'''Su-15''' - semi-automated Mach 2, 20 km interceptor with missiles armament.

== About ==

The Sukhoi Su-15 (NATO reporting name "'''Flagon'''") was the second semi-automated interceptor on the planet, the first being its predecessor, the Sukhoi Su-9, and for its time this was quite advanced. It worked in tandem with ground radar, receiving calculated direction data via a encoded radio link, but also had its own radar with a working distance of 30 km (16 nm), which was huge at time. It was first aircraft ever able to catch a target at both head-on and following courses, at a speed of Mach 2 at an altitude of approximately 20 km (66,000 ft.), and target speeds of Mach 3 at approximately 25 km (82,000 ft.). In fact, with all that equipment, it was first ever aircraft in which the pilot was more of an operator than pilot — the plane could intercept a target by itself in both ground-guided and radar-guided modes.

But its effectiveness was bought at a high price. Being a heavy plane with small wings, it has an extremely high landing speed of 350 km/h, similar to the Space Shuttle and {{wikipedia|Buran|noicon=1}}, both of which are spaceplanes(!). It was also unstable at those kind of speeds, while oversonic yaw maneuvering was limited by its side intakes, a first for Soviet aircraft. Fuel consumption was similar to a rocket, and enormously high by modern standards — it got through 8 tonnes of kerosene in a normal 15-minute, Mach 2 interception flight.

Regular pilot training - happily Su-15 was not used at real targets often - cost the same amount of money as making cosmonaut out of him and sending him at space; common 200 flight hours per year turned into monstrous 1000tonnes of fuel, while weight of whole R-7 rocket was 280tonnes only. At modern prices such training would cost 1million of, heh, money per year - really, not less, so expenses of usage was comparable with cost of plane itself for sure.

Interception of 2Mach target, including radar selection, friend-or-foe semiautomatic recognition, missile guidance head lock, so on, could occur at head-on course only, since other way Su could not reach it; so relative approaching speed was up to 4Mach, and all process had to be pressed in 30seconds, without second chance. 3Mach demanded even faster reaction - but it should be made without any mistake, since a target would be the bomber with thermonuclear bombs. In addition, return at 1 tonne of leftover fuel was a normal part of interception flights.

Summing all that, needed piloting class was high - so high that at most units of anti-aircraft warfare, which was armed with Su-15, cadet who flew it first time alone received a cake from colleagues; it was not tradition common with other units. Other prove - only pilots of Tu-128, flying even more heavy interceptors for hours, had greater incomes in whole air forces.

Even with such qualified pilots, area of plane usage was quite narrow. Not maneuverable, without place for regular gyro sight at cockpit, it has standard armament of two heavy missiles only - typical second generation interceptor, with sole target as heavy high altitude bomber; first series was completely useless against low-speed low-altitude targets. Some of limitations was overpassed at later modifications, but fact that Su-15 as whole was used for quarter of century, and, with modifications, was produced 1300 times, is mostly prove that there is nothing more constant than temporary than evidence of its versatility.

Fact is representative more that, instead of other former Soviet fighters as MiG-21, not one flew in private hands after retiring. It's just too hard, too demanding, to be common fun. Once it was case three Su crashed in a row, in just 15minutes, due to foggy conditions and guiding system absence at receiving port. All three pilots was high-rank - so to use it alone, without ground automatics, would be risky even at future times with its artificially advanced humans. Heh. At fact, pilots respected plane, some of them even liked it, but, seems to be, not one really loved it, way this was with some other types. Well, it's hard to love something that do at its own better than under Your control.

I made model of it mostly as part of personal investigation of Yury Gagarin life and death circumstances - as Alexey Leonov, friend of Gagarin and man who made first ever EVA, said that Su was involved in second. So exactness of model is as high as possible; with conditions in which documentation of it is not at public domain yet.

Also, it was test of ability to make mostly JSBSim realistic model, which could run standalone with all systems, each switch, by minimal fixes and changes; of course it was some additional social test of community, etc.

== Features ==
[[File:Su-15-3D-Quality.jpg|thumb|Example of "Su-15" 3D model quality.]]
[[File:MPClash.png|thumb|MPClash protocol working example.]]
[[File:Su-15-Panair Front.png|thumb|Su-15 PanAir model]]
[[File:Su-15-ALS.png|thumb|Example of Su-15 model ALS shadow, reflection, and instrumentation light.]]
[[File:Su-15-ALS-Lights.png|thumb|Example of external ALS lights of "Su-15" model.]]
* Detailed 3D external model and virtual cockpit based on real photos
* Exact textures with special Soviet fonts
* Sounds from real sources
* Common FDM generated by Datcom with fuselage form modeling
* Advanced FDM polished by [[Panair|Boeing Panair]] panel code program.
* Further polishing of FDM with [[XFLR5]]
* Each surface, gears, tanks, missiles inclusive, have its own forces and moments calculated
* Blowing flaps with realistic effect on pitch
* Braking chute
* Engines based on graphs from real MiG-21 documentation, since it has same one, with possibility of overheating and fire
* Extinguishing system, and ability to land at one engine
* Intakes calculated realtime, with engines cutoff at resurfacing or aerodynamic shadowing mistakes
* Electrical, hydraulic, pneumatic, other systems with flows calculation via JSBSim, which means tens of milliseconds exactness, and wide specter of possible malfunctions on usage mistakes. More than 1Mb of xml code.
* Disturbed instrumentation with lags, which also calculated via JSBsim, and depended on Pitot tubes
* Pitot tubes with possibility of freezing and heaters which could burn out
* Oxygen system used by pilot and engines airstart, with possibility of pilot knockout on exhaust
* Breakable gears, blowing flaps, canopy
* Chain reactions of malfunctions caused by some minor mistakes of pilot
* Manually tuned radicompass working with NDB beacons
* "Asure" radioline commands directions to MP targets or runways
* Autopilot working from stop to stop, including takeoff, passing to beacon, MP target following, interception, landing
* Stabilization and antiskid automation
* Braking chute
* Droppable external tanks with moments and drags
* Radar working at MP targets, based on real Su-15 work movie and real data; as real one, can not see targets below model or behind mountain
* Infrared R-8P and halfactive radar R-8R missiles working at MP targets, based on real data
* Guidance heads of missiles calculated realtime, means it can lose target that making an antimissile maneuvers
* FDM of missiles calculated via JSBSim, means these could lose stability on turns. Instead of other FG missiles, these are calculated as standard JSBSim models, by data sets made by Datcom, plus own stability automation is calculated. Basically, exactness is just same as of plane model itself. Comparison with Yasim/JSBSim models quality matching is relevant here. 100Kb of xml code per missile.
* Basic version with missiles and some systems calculated by Nasal. A bit rough, still missiles works with real calculation of forces and alpha/beta, so maneuvering one slows realistically faster than one flying straight, and would not catch maneuverable target, while heavy bomber should not be an question - it's most realistic missiles at FG still. For old PCs, 7..10fps at Athlon 64X2 4000+, GeForce GTS 450, 2Gb Ram.
* Custom MPClash protocol, allowing missiles dogfight training trough MP, including missile launched by other player visibility, radar irradiation warner, lamps for own missiles catches and for catches of other pilot. At now "Su-15" model is sole one at FG having such abilities. Others can shoot in the air only, since they do not see missiles of each other, and not affected by it in any way, excluding MP messages spam; while protocol could be expanded easily with other missiles types, already existed ones inclusive. To change catch lamp to some breakage calculator is matter of day; so at now "Su-15" model is single one at FG which can shoot down model of other player really. A bit aggressive, still not one else deals with others in any way.
* Exact Russian/English PDF documentation with screenshots for any important action
* Some [[ALS_technical_notes|ALS]] candies - external and internal shadows, canopy glass reflection, red instrumentation light, reheat exhaust, etc.
* GetToFlyOnly license above all that, means You can fly model personally for free, but got to ask me for any other usage. Since some miscomprehendings with FG community, started with "MiG-15" model at 2010, went quite far with "Vostok-1" model at 2011, and not solved with that one and MPClash GPL proposition yet. Lone work for free is possible, it's called "hobby". Common work without own authority is possible, it's often called just "work". Both simultaneously, plus without respect - not. And missiles of "Su" is aimed at people thinking other way. Let's see if these will work.

== Tutorial videos ==

Startup:

{{#ev:youtube|QY3VCHgHCjg}}

Automatic takeoff:

{{#ev:youtube|eRvlWUuXGkg}}

Manual takeoff:

{{#ev:youtube|JvTQzWfcp3A}}

Autopilot beacon following:

{{#ev:youtube|oSKRm5UxQ20}}

Autopilot port following:

{{#ev:youtube|huf06SzYNVw}}

Automatic convoy:

{{#ev:youtube|3nbyZKuf6WQ}}

Automatic and manual interception:

{{#ev:youtube|y-fzJV0AOOA}}

Airstart at altitude cutoff:

{{#ev:youtube|yKCZ7DRYelI}}

Automatic landing:

{{#ev:youtube|bF9GK1PwtUo}}

Manual landing:

{{#ev:youtube|vdI2qFbOGA0}}

== Model performance ==
* Maximum speed: Mach 2.05
* Maximum speed without reheat: Mach 1.5
* Practical ceiling: 18 km
* Dynamic hop ceiling: 23 km
* Maximum flight duration: 3 hours
* Maximum flight duration with reheat: 30 min
* Takeoff speed: 400 km/h
* Landing speed with blowing flaps: 325 km/h
* Stall speed: 300 km/h
* Minimal runway length: 1,500 m
* Radar range: 40 km
* Radar selection range: 30 km
* Medium missiles working range: 10 km

== Model author ==
Victor Slavutinsky, vitosnet <at> mail <dot> ru.

== External links ==
* {{wikipedia|Su-15|Wikipedia}}
* [http://www.airwar.ru/enc/fighter/su15.html Airwar.ru]

{{Sukhoi}}

[[Category:Military aircraft]]

Sukhoi Su-15

2020-06-14T06:26:51Z

Vitos: /* Features */

{{:{{PAGENAME}}/info}}

'''Su-15''' - semi-automated Mach 2, 20 km interceptor with missiles armament.

== About ==

The Sukhoi Su-15 (NATO reporting name "'''Flagon'''") was the second semi-automated interceptor on the planet, the first being its predecessor, the Sukhoi Su-9, and for its time this was quite advanced. It worked in tandem with ground radar, receiving calculated direction data via a encoded radio link, but also had its own radar with a working distance of 30 km (16 nm), which was huge at time. It was first aircraft ever able to catch a target at both head-on and following courses, at a speed of Mach 2 at an altitude of approximately 20 km (66,000 ft.), and target speeds of Mach 3 at approximately 25 km (82,000 ft.). In fact, with all that equipment, it was first ever aircraft in which the pilot was more of an operator than pilot — the plane could intercept a target by itself in both ground-guided and radar-guided modes.

But its effectiveness was bought at a high price. Being a heavy plane with small wings, it has an extremely high landing speed of 350 km/h, similar to the Space Shuttle and {{wikipedia|Buran|noicon=1}}, both of which are spaceplanes(!). It was also unstable at those kind of speeds, while oversonic yaw maneuvering was limited by its side intakes, a first for Soviet aircraft. Fuel consumption was similar to a rocket, and enormously high by modern standards — it got through 8 tonnes of kerosene in a normal 15-minute, Mach 2 interception flight.

Regular pilot training - happily Su-15 was not used at real targets often - cost the same amount of money as making cosmonaut out of him and sending him at space; common 200 flight hours per year turned into monstrous 1000tonnes of fuel, while weight of whole R-7 rocket was 280tonnes only. At modern prices such training would cost 1million of, heh, money per year - really, not less, so expenses of usage was comparable with cost of plane itself for sure.

Interception of 2Mach target, including radar selection, friend-or-foe semiautomatic recognition, missile guidance head lock, so on, could occur at head-on course only, since other way Su could not reach it; so relative approaching speed was up to 4Mach, and all process had to be pressed in 30seconds, without second chance. 3Mach demanded even faster reaction - but it should be made without any mistake, since a target would be the bomber with thermonuclear bombs. In addition, return at 1 tonne of leftover fuel was a normal part of interception flights.

Summing all that, needed piloting class was high - so high that at most units of anti-aircraft warfare, which was armed with Su-15, cadet who flew it first time alone received a cake from colleagues; it was not tradition common with other units. Other prove - only pilots of Tu-128, flying even more heavy interceptors for hours, had greater incomes in whole air forces.

Even with such qualified pilots, area of plane usage was quite narrow. Not maneuverable, without place for regular gyro sight at cockpit, it has standard armament of two heavy missiles only - typical second generation interceptor, with sole target as heavy high altitude bomber; first series was completely useless against low-speed low-altitude targets. Some of limitations was overpassed at later modifications, but fact that Su-15 as whole was used for quarter of century, and, with modifications, was produced 1300 times, is mostly prove that there is nothing more constant than temporary than evidence of its versatility.

Fact is representative more that, instead of other former Soviet fighters as MiG-21, not one flew in private hands after retiring. It's just too hard, too demanding, to be common fun. Once it was case three Su crashed in a row, in just 15minutes, due to foggy conditions and guiding system absence at receiving port. All three pilots was high-rank - so to use it alone, without ground automatics, would be risky even at future times with its artificially advanced humans. Heh. At fact, pilots respected plane, some of them even liked it, but, seems to be, not one really loved it, way this was with some other types. Well, it's hard to love something that do at its own better than under Your control.

I made model of it mostly as part of personal investigation of Yury Gagarin life and death circumstances - as Alexey Leonov, friend of Gagarin and man who made first ever EVA, said that Su was involved in second. So exactness of model is as high as possible; with conditions in which documentation of it is not at public domain yet.

Also, it was test of ability to make mostly JSBSim realistic model, which could run standalone with all systems, each switch, by minimal fixes and changes; of course it was some additional social test of community, etc.

== Features ==
[[File:Su-15-3D-Quality.jpg|thumb|Example of "Su-15" 3D model quality.]]
[[File:MPClash.png|thumb|MPClash protocol working example.]]
[[File:Su-15-Panair Front.png|thumb|Su-15 PanAir model]]
[[File:Su-15-ALS.png|thumb|Example of Su-15 model ALS shadow, reflection, and instrumentation light.]]
[[File:Su-15-ALS-Lights.png|thumb|Example of external ALS lights of "Su-15" model.]]
* Detailed 3D external model and virtual cockpit based on real photos
* Exact textures with special Soviet fonts
* Sounds from real sources
* Common FDM generated by Datcom with fuselage form modeling
* Advanced FDM polished by [[Panair|Boeing Panair]] panel code program.
* Further polishing of FDM with [[XFLR5]]
* Each surface, gears, tanks, missiles inclusive, have its own forces and moments calculated
* Blowing flaps with realistic effect on pitch
* Braking chute
* Engines based on graphs from real MiG-21 documentation, since it has same one, with possibility of overheating and fire
* Extinguishing system, and ability to land at one engine
* Intakes calculated realtime, with engines cutoff at resurfacing or aerodynamic shadowing mistakes
* Electrical, hydraulic, pneumatic, other systems with flows calculation via JSBSim, which means tens of milliseconds exactness, and wide specter of possible malfunctions on usage mistakes. More than 1Mb of xml code.
* Disturbed instrumentation with lags, which also calculated via JSBsim, and depended on Pitot tubes
* Pitot tubes with possibility of freezing and heaters which could burn out
* Oxygen system used by pilot and engines airstart, with possibility of pilot knockout on exhaust
* Breakable gears, blowing flaps, canopy
* Chain reactions of malfunctions caused by some minor mistakes of pilot
* Manually tuned radicompass working with NDB beacons
* "Asure" radioline commands directions to MP targets or runways
* Autopilot working from stop to stop, including takeoff, passing to beacon, MP target following, interception, landing
* Stabilization and antiskid automation
* Braking chute
* Droppable external tanks with moments and drags
* Radar working at MP targets, based on real Su-15 work movie and real data; as real one, can not see targets below model or behind mountain
* Infrared R-8P and halfactive radar R-8R missiles working at MP targets, based on real data
* Guidance heads of missiles calculated realtime, means it can lose target that making an antimissile maneuvers
* FDM of missiles calculated via JSBSim, means these could lose stability on turns. Instead of other FG missiles, these are calculated as standard JSBSim models, by data sets made by Datcom, plus own stability automation is calculated. Basically, exactness is just same as of plane model itself. Comparison with Yasim/JSBSim models quality matching is relevant here. 100Kb of xml code per missile.
* Basic version with missiles and some systems calculated by Nasal. A bit rough, still missiles works with real calculation of forces and alpha/beta, so maneuvering one slows realistically faster than one flying straight, and would not catch maneuverable target, while heavy bomber should not be an question - it's most realistic missiles at FG still. For old PCs, 7..10fps at Athlon 64X2 4000+, GeForce GTS 450, 2Gb Ram.
* Custom MPClash protocol, allowing missiles dogfight training trough MP, including missile launched by other player visibility, radar irradiation warner, lamps for own missiles catches and for catches of other pilot. At now "Su-15" model is sole one at FG having such abilities. Others can shoot in the air only, since they do not see missiles of each other, and not affected by it in any way, excluding MP messages spam; while protocol could be expanded easily with other missiles types, already existed ones inclusive. To change catch lamp to some breakage calculator is matter of day; so at now "Su-15" model is single one at FG which can shoot down model of other player really. A bit aggressive, still not one else deals with others in any way.
* Exact Russian/English PDF documentation with screenshots for any important action
* Some [[ALS_technical_notes|ALS]] candies - external and internal shadows, canopy glass reflection, red instrumentation light, reheat exhaust, etc.
* GetToFlyOnly license above all that, means You can fly model personally for free, but got to ask me for any other usage. Since some miscomprehendings with FG community, started with MiG-15 model at 2010, went quite far with Vostok-1 model at 2011, and was not solved with that one yet. Lone work for free is possible, it's called "hobby". Common work without own authority is possible, it's often called just "work". Both simultaneously, plus without respect - not. And missiles of "Su" is aimed at people thinking other way. Let's see if these will work.

== Tutorial videos ==

Startup:

{{#ev:youtube|QY3VCHgHCjg}}

Automatic takeoff:

{{#ev:youtube|eRvlWUuXGkg}}

Manual takeoff:

{{#ev:youtube|JvTQzWfcp3A}}

Autopilot beacon following:

{{#ev:youtube|oSKRm5UxQ20}}

Autopilot port following:

{{#ev:youtube|huf06SzYNVw}}

Automatic convoy:

{{#ev:youtube|3nbyZKuf6WQ}}

Automatic and manual interception:

{{#ev:youtube|y-fzJV0AOOA}}

Airstart at altitude cutoff:

{{#ev:youtube|yKCZ7DRYelI}}

Automatic landing:

{{#ev:youtube|bF9GK1PwtUo}}

Manual landing:

{{#ev:youtube|vdI2qFbOGA0}}

== Model performance ==
* Maximum speed: Mach 2.05
* Maximum speed without reheat: Mach 1.5
* Practical ceiling: 18 km
* Dynamic hop ceiling: 23 km
* Maximum flight duration: 3 hours
* Maximum flight duration with reheat: 30 min
* Takeoff speed: 400 km/h
* Landing speed with blowing flaps: 325 km/h
* Stall speed: 300 km/h
* Minimal runway length: 1,500 m
* Radar range: 40 km
* Radar selection range: 30 km
* Medium missiles working range: 10 km

== Model author ==
Victor Slavutinsky, vitosnet <at> mail <dot> ru.

== External links ==
* {{wikipedia|Su-15|Wikipedia}}
* [http://www.airwar.ru/enc/fighter/su15.html Airwar.ru]

{{Sukhoi}}

[[Category:Military aircraft]]

Sukhoi Su-15

2016-11-29T14:25:43Z

Vitos: /* Features */

{{:{{PAGENAME}}/info}}

'''Su-15''' - semi-automated Mach 2, 20 km interceptor with missiles armament.

== About ==

The Sukhoi Su-15 (NATO reporting name "'''Flagon'''") was the second semi-automated interceptor on the planet, the first being its predecessor, the Sukhoi Su-9, and for its time this was quite advanced. It worked in tandem with ground radar, receiving calculated direction data via a encoded radio link, but also had its own radar with a working distance of 30 km (16 nm), which was huge at time. It was first aircraft ever able to catch a target at both head-on and following courses, at a speed of Mach 2 at an altitude of approximately 20 km (66,000 ft.), and target speeds of Mach 3 at approximately 25 km (82,000 ft.). In fact, with all that equipment, it was first ever aircraft in which the pilot was more of an operator than pilot — the plane could intercept a target by itself in both ground-guided and radar-guided modes.

But its effectiveness was bought at a high price. Being a heavy plane with small wings, it has an extremely high landing speed of 350 km/h, similar to the Space Shuttle and {{wikipedia|Buran|noicon=1}}, both of which are spaceplanes(!). It was also unstable at those kind of speeds, while oversonic yaw maneuvering was limited by its side intakes, a first for Soviet aircraft. Fuel consumption was similar to a rocket, and enormously high by modern standards — it got through 8 tonnes of kerosene in a normal 15-minute, Mach 2 interception flight.

Regular pilot training - happily Su-15 was not used at real targets often - cost the same amount of money as making cosmonaut out of him and sending him at space; common 200 flight hours per year turned into monstrous 1000tonnes of fuel, while weight of whole R-7 rocket was 280tonnes only. At modern prices such training would cost 1million of, heh, money per year - really, not less, so expenses of usage was comparable with cost of plane itself for sure.

Interception of 2Mach target, including radar selection, friend-or-foe semiautomatic recognition, missile guidance head lock, so on, could occur at head-on course only, since other way Su could not reach it; so relative approaching speed was up to 4Mach, and all process had to be pressed in 30seconds, without second chance. 3Mach demanded even faster reaction - but it should be made without any mistake, since a target would be the bomber with thermonuclear bombs. In addition, return at 1 tonne of leftover fuel was a normal part of interception flights.

Summing all that, needed piloting class was high - so high that at most units of anti-aircraft warfare, which was armed with Su-15, cadet who flew it first time alone received a cake from colleagues; it was not tradition common with other units. Other prove - only pilots of Tu-128, flying even more heavy interceptors for hours, had greater incomes in whole air forces.

Even with such qualified pilots, area of plane usage was quite narrow. Not maneuverable, without place for regular gyro sight at cockpit, it has standard armament of two heavy missiles only - typical second generation interceptor, with sole target as heavy high altitude bomber; first series was completely useless against low-speed low-altitude targets. Some of limitations was overpassed at later modifications, but fact that Su-15 as whole was used for quarter of century, and, with modifications, was produced 1300 times, is mostly prove that there is nothing more constant than temporary than evidence of its versatility.

Fact is representative more that, instead of other former Soviet fighters as MiG-21, not one flew in private hands after retiring. It's just too hard, too demanding, to be common fun. Once it was case three Su crashed in a row, in just 15minutes, due to foggy conditions and guiding system absence at receiving port. All three pilots was high-rank - so to use it alone, without ground automatics, would be risky even at future times with its artificially advanced humans. Heh. At fact, pilots respected plane, some of them even liked it, but, seems to be, not one really loved it, way this was with some other types. Well, it's hard to love something that do at its own better than under Your control.

I made model of it mostly as part of personal investigation of Yury Gagarin life and death circumstances - as Alexey Leonov, friend of Gagarin and man who made first ever EVA, said that Su was involved in second. So exactness of model is as high as possible; with conditions in which documentation of it is not at public domain yet.

Also, it was test of ability to make mostly JSBSim realistic model, which could run standalone with all systems, each switch, by minimal fixes and changes; of course it was some additional social test of community, etc.

== Features ==
[[File:Su-15-3D-Quality.jpg|thumb|Example of "Su-15" 3D model quality.]]
[[File:MPClash.png|thumb|MPClash protocol working example.]]
[[File:Su-15-Panair Front.png|thumb|Su-15 PanAir model]]
[[File:Su-15-ALS.png|thumb|Example of Su-15 model ALS shadow, reflection, and instrumentation light.]]
[[File:Su-15-ALS-Lights.png|thumb|Example of external ALS lights of "Su-15" model.]]
* Detailed 3D external model and virtual cockpit based on real photos
* Exact textures with special Soviet fonts
* Sounds from real sources
* Common FDM generated by Datcom with fuselage form modeling
* Advanced FDM polished by [[Panair|Boeing Panair]] panel code program.
* Further polishing of FDM with [[XFLR5]]
* Each surface, gears, tanks, missiles inclusive, have its own forces and moments calculated
* Blowing flaps with realistic effect on pitch
* Braking chute
* Engines based on graphs from real MiG-21 documentation, since it has same one, with possibility of overheating and fire
* Extinguishing system, and ability to land at one engine
* Intakes calculated realtime, with engines cutoff at resurfacing or aerodynamic shadowing mistakes
* Electrical, hydraulic, pneumatic, other systems with flows calculation via JSBSim, which means tens of milliseconds exactness, and wide specter of possible malfunctions on usage mistakes. More than 1Mb of xml code.
* Disturbed instrumentation with lags, which also calculated via JSBsim, and depended on Pitot tubes
* Pitot tubes with possibility of freezing and heaters which could burn out
* Oxygen system used by pilot and engines airstart, with possibility of pilot knockout on exhaust
* Breakable gears, blowing flaps, canopy
* Chain reactions of malfunctions caused by some minor mistakes of pilot
* Manually tuned radicompass working with NDB beacons
* "Asure" radioline commands directions to MP targets or runways
* Autopilot working from stop to stop, including takeoff, passing to beacon, MP target following, interception, landing
* Stabilization and antiskid automation
* Braking chute
* Droppable external tanks with moments and drags
* Radar working at MP targets, based on real Su-15 work movie and real data; as real one, can not see targets below model or behind mountain
* Infrared R-8P and halfactive radar R-8R missiles working at MP targets, based on real data
* Guidance heads of missiles calculated realtime, means it can lose target that making an antimissile maneuvers
* FDM of missiles calculated via JSBSim, means these could lose stability on turns. Instead of other FG missiles, these are calculated as standard JSBSim models, by data sets made by Datcom, plus own stability automation is calculated. Basically, exactness is just same as of plane model itself. Comparison with Yasim/JSBSim models quality matching is relevant here. 100Kb of xml code per missile.
* Basic version with missiles and some systems calculated by Nasal. A bit rough, still missiles works with real calculation of forces and alpha/beta, so maneuvering one slows realistically faster than one flying straight, and would not catch maneuverable target, while heavy bomber should not be an question - it's most realistic missiles at FG still. For old PCs, 7..10fps at Athlon 64X2 4000+, GeForce GTS 450, 2Gb Ram.
* Custom MPClash protocol, allowing missiles dogfight training trough MP, including missile launched by other player visibility, radar irradiation warner, lamps for own missiles catches and for catches of other pilot. At now "Su-15" model is sole one at FG having such abilities. Others can shoot in the air only, since they do not see missiles of each other, and not affected by it in any way, excluding MP messages spam; while protocol could be expanded easily with other missiles types, already existed ones inclusive. To change catch lamp to some breakage calculator is matter of day; so at now "Su-15" model is single one at FG which can shoot down model of other player really. A bit aggressive, still not one else deals with others in any way.
* Exact Russian/English PDF documentation with screenshots for any important action
* Some [[ALS_technical_notes|ALS]] candies - external and internal shadows, canopy glass reflection, red instrumentation light, reheat exhaust, etc.
* GetToFlyOnly license above all that, means You can fly model personally for free, but got to ask me for any other usage. Since some miscomprehendings with FG community. Lone work for free is possible, it's called "hobby". Common work without own authority is possible, it's often called just "work". Both simultaneously, plus without respect - not. And missiles of "Su" is aimed at people thinking other way. Let's see if these will work.

== Tutorial videos ==

Startup:

{{#ev:youtube|QY3VCHgHCjg}}

Automatic takeoff:

{{#ev:youtube|eRvlWUuXGkg}}

Manual takeoff:

{{#ev:youtube|JvTQzWfcp3A}}

Autopilot beacon following:

{{#ev:youtube|oSKRm5UxQ20}}

Autopilot port following:

{{#ev:youtube|huf06SzYNVw}}

Automatic convoy:

{{#ev:youtube|3nbyZKuf6WQ}}

Automatic and manual interception:

{{#ev:youtube|y-fzJV0AOOA}}

Airstart at altitude cutoff:

{{#ev:youtube|yKCZ7DRYelI}}

Automatic landing:

{{#ev:youtube|bF9GK1PwtUo}}

Manual landing:

{{#ev:youtube|vdI2qFbOGA0}}

== Model performance ==
* Maximum speed: Mach 2.05
* Maximum speed without reheat: Mach 1.5
* Practical ceiling: 18 km
* Dynamic hop ceiling: 23 km
* Maximum flight duration: 3 hours
* Maximum flight duration with reheat: 30 min
* Takeoff speed: 400 km/h
* Landing speed with blowing flaps: 325 km/h
* Stall speed: 300 km/h
* Minimal runway length: 1,500 m
* Radar range: 40 km
* Radar selection range: 30 km
* Medium missiles working range: 10 km

== Model author ==
Victor Slavutinsky, vitosnet <at> mail <dot> ru.

== External links ==
* {{wikipedia|Su-15|Wikipedia}}
* [http://www.airwar.ru/enc/fighter/su15.html Airwar.ru]

{{Sukhoi}}

[[Category:Military aircraft]]

File:Su-15-ALS-Lights.png

2016-11-29T14:23:21Z

Vitos: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Example of external ALS lights of "Su-15" model.}}
|date=2016-11-29
|source={{own}}
|author=[[User:Vitos|Vitos]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

Sukhoi Su-15

2016-11-26T16:24:43Z

Vitos: /* Features */

{{:{{PAGENAME}}/info}}

'''Su-15''' - semi-automated Mach 2, 20 km interceptor with missiles armament.

== About ==

The Sukhoi Su-15 (NATO reporting name "'''Flagon'''") was the second semi-automated interceptor on the planet, the first being its predecessor, the Sukhoi Su-9, and for its time this was quite advanced. It worked in tandem with ground radar, receiving calculated direction data via a encoded radio link, but also had its own radar with a working distance of 30 km (16 nm), which was huge at time. It was first aircraft ever able to catch a target at both head-on and following courses, at a speed of Mach 2 at an altitude of approximately 20 km (66,000 ft.), and target speeds of Mach 3 at approximately 25 km (82,000 ft.). In fact, with all that equipment, it was first ever aircraft in which the pilot was more of an operator than pilot — the plane could intercept a target by itself in both ground-guided and radar-guided modes.

But its effectiveness was bought at a high price. Being a heavy plane with small wings, it has an extremely high landing speed of 350 km/h, similar to the Space Shuttle and {{wikipedia|Buran|noicon=1}}, both of which are spaceplanes(!). It was also unstable at those kind of speeds, while oversonic yaw maneuvering was limited by its side intakes, a first for Soviet aircraft. Fuel consumption was similar to a rocket, and enormously high by modern standards — it got through 8 tonnes of kerosene in a normal 15-minute, Mach 2 interception flight.

Regular pilot training - happily Su-15 was not used at real targets often - cost the same amount of money as making cosmonaut out of him and sending him at space; common 200 flight hours per year turned into monstrous 1000tonnes of fuel, while weight of whole R-7 rocket was 280tonnes only. At modern prices such training would cost 1million of, heh, money per year - really, not less, so expenses of usage was comparable with cost of plane itself for sure.

Interception of 2Mach target, including radar selection, friend-or-foe semiautomatic recognition, missile guidance head lock, so on, could occur at head-on course only, since other way Su could not reach it; so relative approaching speed was up to 4Mach, and all process had to be pressed in 30seconds, without second chance. 3Mach demanded even faster reaction - but it should be made without any mistake, since a target would be the bomber with thermonuclear bombs. In addition, return at 1 tonne of leftover fuel was a normal part of interception flights.

Summing all that, needed piloting class was high - so high that at most units of anti-aircraft warfare, which was armed with Su-15, cadet who flew it first time alone received a cake from colleagues; it was not tradition common with other units. Other prove - only pilots of Tu-128, flying even more heavy interceptors for hours, had greater incomes in whole air forces.

Even with such qualified pilots, area of plane usage was quite narrow. Not maneuverable, without place for regular gyro sight at cockpit, it has standard armament of two heavy missiles only - typical second generation interceptor, with sole target as heavy high altitude bomber; first series was completely useless against low-speed low-altitude targets. Some of limitations was overpassed at later modifications, but fact that Su-15 as whole was used for quarter of century, and, with modifications, was produced 1300 times, is mostly prove that there is nothing more constant than temporary than evidence of its versatility.

Fact is representative more that, instead of other former Soviet fighters as MiG-21, not one flew in private hands after retiring. It's just too hard, too demanding, to be common fun. Once it was case three Su crashed in a row, in just 15minutes, due to foggy conditions and guiding system absence at receiving port. All three pilots was high-rank - so to use it alone, without ground automatics, would be risky even at future times with its artificially advanced humans. Heh. At fact, pilots respected plane, some of them even liked it, but, seems to be, not one really loved it, way this was with some other types. Well, it's hard to love something that do at its own better than under Your control.

I made model of it mostly as part of personal investigation of Yury Gagarin life and death circumstances - as Alexey Leonov, friend of Gagarin and man who made first ever EVA, said that Su was involved in second. So exactness of model is as high as possible; with conditions in which documentation of it is not at public domain yet.

Also, it was test of ability to make mostly JSBSim realistic model, which could run standalone with all systems, each switch, by minimal fixes and changes; of course it was some additional social test of community, etc.

== Features ==
* Detailed 3D external model and virtual cockpit based on real photos
[[File:Su-15-3D-Quality.jpg|thumb|Example of "Su-15" 3D model quality.]]
* Exact textures with special Soviet fonts
* Sounds from real sources
* Common FDM generated by Datcom with fuselage form modeling
* Advanced FDM polished by [[Panair|Boeing Panair]] panel code program.
[[File:Su-15-Panair Front.png|thumb|Su-15 PanAir model]]
* Further polishing of FDM with [[XFLR5]]
* Each surface, gears, tanks, missiles inclusive, have its own forces and moments calculated
* Blowing flaps with realistic effect on pitch
* Braking chute
* Engines based on graphs from real MiG-21 documentation, since it has same one, with possibility of overheating and fire
* Extinguishing system, and ability to land at one engine
* Intakes calculated realtime, with engines cutoff at resurfacing or aerodynamic shadowing mistakes
* Electrical, hydraulic, pneumatic, other systems with flows calculation via JSBSim, which means tens of milliseconds exactness, and wide specter of possible malfunctions on usage mistakes. More than 1Mb of xml code.
* Disturbed instrumentation with lags, which also calculated via JSBsim, and depended on Pitot tubes
* Pitot tubes with possibility of freezing and heaters which could burn out
* Oxygen system used by pilot and engines airstart, with possibility of pilot knockout on exhaust
* Breakable gears, blowing flaps, canopy
* Chain reactions of malfunctions caused by some minor mistakes of pilot
* Manually tuned radicompass working with NDB beacons
* "Asure" radioline commands directions to MP targets or runways
* Autopilot working from stop to stop, including takeoff, passing to beacon, MP target following, interception, landing
* Stabilization and antiskid automation
* Braking chute
* Droppable external tanks with moments and drags
* Radar working at MP targets, based on real Su-15 work movie and real data; as real one, can not see targets below model or behind mountain
* Infrared R-8P and halfactive radar R-8R missiles working at MP targets, based on real data
* Guidance heads of missiles calculated realtime, means it can lose target that making an antimissile maneuvers
* FDM of missiles calculated via JSBSim, means these could lose stability on turns. Instead of other FG missiles, these are calculated as standard JSBSim models, by data sets made by Datcom, plus own stability automation is calculated. Basically, exactness is just same as of plane model itself. Comparison with Yasim/JSBSim models quality matching is relevant here. 100Kb of xml code per missile.
* Basic version with missiles and some systems calculated by Nasal. A bit rough, still missiles works with real calculation of forces and alpha/beta, so maneuvering one slows realistically faster than one flying straight, and would not catch maneuverable target, while heavy bomber should not be an question - it's most realistic missiles at FG still. For old PCs, 7..10fps at Athlon 64X2 4000+, GeForce GTS 450, 2Gb Ram.
* Custom MPClash protocol, allowing missiles dogfight training trough MP, including missile launched by other player visibility, radar irradiation warner, lamps for own missiles catches and for catches of other pilot. At now "Su-15" model is sole one at FG having such abilities. Others can shoot in the air only, since they do not see missiles of each other, and not affected by it in any way, excluding MP messages spam; while protocol could be expanded easily with other missiles types, already existed ones inclusive. To change catch lamp to some breakage calculator is matter of day; so at now "Su-15" model is single one at FG which can shoot down model of other player really. A bit aggressive, still not one else deals with others in any way.
[[File:MPClash.png|thumb|MPClash protocol working example.]]
* Exact Russian/English PDF documentation with screenshots for any important action
* Some [[ALS_technical_notes|ALS]] candies - external and internal shadows, canopy glass reflection, red instrumentation light, reheat exhaust, etc.
[[File:Su-15-ALS.png|thumb|Example of Su-15 model ALS shadow, reflection, and instrumentation light.]]
* GetToFlyOnly license above all that, means You can fly model personally for free, but got to ask me for any other usage. Since some miscomprehendings with FG community. Lone work for free is possible, it's called "hobby". Common work without own authority is possible, it's often called just "work". Both simultaneously, plus without respect - not. And missiles of "Su" is aimed at people thinking other way. Let's see if these will work.

== Tutorial videos ==

Startup:

{{#ev:youtube|QY3VCHgHCjg}}

Automatic takeoff:

{{#ev:youtube|eRvlWUuXGkg}}

Manual takeoff:

{{#ev:youtube|JvTQzWfcp3A}}

Autopilot beacon following:

{{#ev:youtube|oSKRm5UxQ20}}

Autopilot port following:

{{#ev:youtube|huf06SzYNVw}}

Automatic convoy:

{{#ev:youtube|3nbyZKuf6WQ}}

Automatic and manual interception:

{{#ev:youtube|y-fzJV0AOOA}}

Airstart at altitude cutoff:

{{#ev:youtube|yKCZ7DRYelI}}

Automatic landing:

{{#ev:youtube|bF9GK1PwtUo}}

Manual landing:

{{#ev:youtube|vdI2qFbOGA0}}

== Model performance ==
* Maximum speed: Mach 2.05
* Maximum speed without reheat: Mach 1.5
* Practical ceiling: 18 km
* Dynamic hop ceiling: 23 km
* Maximum flight duration: 3 hours
* Maximum flight duration with reheat: 30 min
* Takeoff speed: 400 km/h
* Landing speed with blowing flaps: 325 km/h
* Stall speed: 300 km/h
* Minimal runway length: 1,500 m
* Radar range: 40 km
* Radar selection range: 30 km
* Medium missiles working range: 10 km

== Model author ==
Victor Slavutinsky, vitosnet <at> mail <dot> ru.

== External links ==
* {{wikipedia|Su-15|Wikipedia}}
* [http://www.airwar.ru/enc/fighter/su15.html Airwar.ru]

{{Sukhoi}}

[[Category:Military aircraft]]

Sukhoi Su-15

2016-11-26T16:22:08Z

Vitos: /* Features */

{{:{{PAGENAME}}/info}}

'''Su-15''' - semi-automated Mach 2, 20 km interceptor with missiles armament.

== About ==

The Sukhoi Su-15 (NATO reporting name "'''Flagon'''") was the second semi-automated interceptor on the planet, the first being its predecessor, the Sukhoi Su-9, and for its time this was quite advanced. It worked in tandem with ground radar, receiving calculated direction data via a encoded radio link, but also had its own radar with a working distance of 30 km (16 nm), which was huge at time. It was first aircraft ever able to catch a target at both head-on and following courses, at a speed of Mach 2 at an altitude of approximately 20 km (66,000 ft.), and target speeds of Mach 3 at approximately 25 km (82,000 ft.). In fact, with all that equipment, it was first ever aircraft in which the pilot was more of an operator than pilot — the plane could intercept a target by itself in both ground-guided and radar-guided modes.

But its effectiveness was bought at a high price. Being a heavy plane with small wings, it has an extremely high landing speed of 350 km/h, similar to the Space Shuttle and {{wikipedia|Buran|noicon=1}}, both of which are spaceplanes(!). It was also unstable at those kind of speeds, while oversonic yaw maneuvering was limited by its side intakes, a first for Soviet aircraft. Fuel consumption was similar to a rocket, and enormously high by modern standards — it got through 8 tonnes of kerosene in a normal 15-minute, Mach 2 interception flight.

Regular pilot training - happily Su-15 was not used at real targets often - cost the same amount of money as making cosmonaut out of him and sending him at space; common 200 flight hours per year turned into monstrous 1000tonnes of fuel, while weight of whole R-7 rocket was 280tonnes only. At modern prices such training would cost 1million of, heh, money per year - really, not less, so expenses of usage was comparable with cost of plane itself for sure.

Interception of 2Mach target, including radar selection, friend-or-foe semiautomatic recognition, missile guidance head lock, so on, could occur at head-on course only, since other way Su could not reach it; so relative approaching speed was up to 4Mach, and all process had to be pressed in 30seconds, without second chance. 3Mach demanded even faster reaction - but it should be made without any mistake, since a target would be the bomber with thermonuclear bombs. In addition, return at 1 tonne of leftover fuel was a normal part of interception flights.

Summing all that, needed piloting class was high - so high that at most units of anti-aircraft warfare, which was armed with Su-15, cadet who flew it first time alone received a cake from colleagues; it was not tradition common with other units. Other prove - only pilots of Tu-128, flying even more heavy interceptors for hours, had greater incomes in whole air forces.

Even with such qualified pilots, area of plane usage was quite narrow. Not maneuverable, without place for regular gyro sight at cockpit, it has standard armament of two heavy missiles only - typical second generation interceptor, with sole target as heavy high altitude bomber; first series was completely useless against low-speed low-altitude targets. Some of limitations was overpassed at later modifications, but fact that Su-15 as whole was used for quarter of century, and, with modifications, was produced 1300 times, is mostly prove that there is nothing more constant than temporary than evidence of its versatility.

Fact is representative more that, instead of other former Soviet fighters as MiG-21, not one flew in private hands after retiring. It's just too hard, too demanding, to be common fun. Once it was case three Su crashed in a row, in just 15minutes, due to foggy conditions and guiding system absence at receiving port. All three pilots was high-rank - so to use it alone, without ground automatics, would be risky even at future times with its artificially advanced humans. Heh. At fact, pilots respected plane, some of them even liked it, but, seems to be, not one really loved it, way this was with some other types. Well, it's hard to love something that do at its own better than under Your control.

I made model of it mostly as part of personal investigation of Yury Gagarin life and death circumstances - as Alexey Leonov, friend of Gagarin and man who made first ever EVA, said that Su was involved in second. So exactness of model is as high as possible; with conditions in which documentation of it is not at public domain yet.

Also, it was test of ability to make mostly JSBSim realistic model, which could run standalone with all systems, each switch, by minimal fixes and changes; of course it was some additional social test of community, etc.

== Features ==
* Detailed 3D external model and virtual cockpit based on real photos
[[File:Su-15-3D-Quality.jpg|thumb|Example of "Su-15" 3D model quality.]]
* Exact textures with special Soviet fonts
* Sounds from real sources
* Common FDM generated by Datcom with fuselage form modeling
* Advanced FDM polished by [[Panair|Boeing Panair]] panel code program.
[[File:Su-15-Panair Front.png|thumb|Su-15 PanAir model]]
* Further polishing of FDM with [[XFLR5]]
* Each surface, gears, tanks, missiles inclusive, have its own forces and moments calculated
* Blowing flaps with realistic effect on pitch
* Braking chute
* Engines based on graphs from real MiG-21 documentation, since it has same one, with possibility of overheating and fire
* Extinguishing system, and ability to land at one engine
* Intakes calculated realtime, with engines cutoff at resurfacing or aerodynamic shadowing mistakes
* Electrical, hydraulic, pneumatic, other systems with flows calculation via JSBSim, which means tens of milliseconds exactness, and wide specter of possible malfunctions on usage mistakes. More than 1Mb of xml code.
* Disturbed instrumentation with lags, which also calculated via JSBsim, and depended on Pitot tubes
* Pitot tubes with possibility of freezing and heaters which could burn out
* Oxygen system used by pilot and engines airstart with possibility of pilot knockout on exhaust
* Breakable gears, blowing flaps, canopy
* Chain reactions of malfunctions caused by some minor mistakes of pilot
* Manually tuned radicompass working with NDB beacons
* "Asure" radioline commands directions to MP targets or runways
* Autopilot working from stop to stop, including takeoff, passing to beacon, MP target following, interception, landing
* Stabilization and antiskid automation
* Braking chute
* Droppable external tanks with moments and drags
* Radar working at MP targets, based on real Su-15 work movie and real data; as real one, can not see targets below model or behind mountain
* Infrared R-8P and halfactive radar R-8R missiles working at MP targets, based on real data
* Guidance heads of missiles calculated realtime, means it can lose target that making an antimissile maneuvers
* FDM of missiles calculated via JSBSim, means these could lose stability on turns. Instead of other FG missiles, these are calculated as standard JSBSim models, by data sets made by Datcom, plus own stability automation is calculated. Basically, exactness is just same as of plane model itself. Comparison with Yasim/JSBSim models quality matching is relevant here. 100Kb of xml code per missile.
* Basic version with missiles and some systems calculated by Nasal. A bit rough, still missiles works with real calculation of forces and alpha/beta, so maneuvering one slows realistically faster than one flying straight, and would not catch maneuverable target, while heavy bomber should not be an question - it's most realistic missiles at FG still. For old PCs, 7..10fps at Athlon 64X2 4000+, GeForce GTS 450, 2Gb Ram.
* Custom MPClash protocol, allowing missiles dogfight training trough MP, including missile launched by other player visibility, radar irradiation warner, lamps for own missiles catches and for catches of other pilot. At now "Su-15" model is sole one at FG having such abilities. Others can shoot in the air only, since they do not see missiles of each other, and not affected by it in any way, excluding MP messages spam; while protocol could be expanded easily with other missiles types, already existed ones inclusive. To change catch lamp to some breakage calculator is matter of day; so at now "Su-15" model is single one at FG which can shoot down model of other player really. A bit aggressive, still not one else deals with others in any way.
[[File:MPClash.png|thumb|MPClash protocol working example.]]
* Exact Russian/English PDF documentation with screenshots for any important action
* Some [[ALS_technical_notes|ALS]] candies - external and internal shadows, canopy glass reflection, red instrumentation light, reheat exhaust, etc.
[[File:Su-15-ALS.png|thumb|Example of Su-15 model ALS shadow, reflection, and instrumentation light.]]
* GetToFlyOnly license above all that, means You can fly model personally for free, but got to ask me for any other usage. Since some miscomprehendings with FG community. Lone work for free is possible, it's called "hobby". Common work without own authority is possible, it's often called just "work". Both simultaneously, plus without respect - not. And missiles of "Su" is aimed at people thinking other way. Let's see if these will work.

== Tutorial videos ==

Startup:

{{#ev:youtube|QY3VCHgHCjg}}

Automatic takeoff:

{{#ev:youtube|eRvlWUuXGkg}}

Manual takeoff:

{{#ev:youtube|JvTQzWfcp3A}}

Autopilot beacon following:

{{#ev:youtube|oSKRm5UxQ20}}

Autopilot port following:

{{#ev:youtube|huf06SzYNVw}}

Automatic convoy:

{{#ev:youtube|3nbyZKuf6WQ}}

Automatic and manual interception:

{{#ev:youtube|y-fzJV0AOOA}}

Airstart at altitude cutoff:

{{#ev:youtube|yKCZ7DRYelI}}

Automatic landing:

{{#ev:youtube|bF9GK1PwtUo}}

Manual landing:

{{#ev:youtube|vdI2qFbOGA0}}

== Model performance ==
* Maximum speed: Mach 2.05
* Maximum speed without reheat: Mach 1.5
* Practical ceiling: 18 km
* Dynamic hop ceiling: 23 km
* Maximum flight duration: 3 hours
* Maximum flight duration with reheat: 30 min
* Takeoff speed: 400 km/h
* Landing speed with blowing flaps: 325 km/h
* Stall speed: 300 km/h
* Minimal runway length: 1,500 m
* Radar range: 40 km
* Radar selection range: 30 km
* Medium missiles working range: 10 km

== Model author ==
Victor Slavutinsky, vitosnet <at> mail <dot> ru.

== External links ==
* {{wikipedia|Su-15|Wikipedia}}
* [http://www.airwar.ru/enc/fighter/su15.html Airwar.ru]

{{Sukhoi}}

[[Category:Military aircraft]]

Sukhoi Su-15

2016-11-21T22:18:32Z

Vitos: /* Tutorial videos */

{{:{{PAGENAME}}/info}}

'''Su-15''' - semi-automated Mach 2, 20 km interceptor with missiles armament.

== About ==

The Sukhoi Su-15 (NATO reporting name "'''Flagon'''") was the second semi-automated interceptor on the planet, the first being its predecessor, the Sukhoi Su-9, and for its time this was quite advanced. It worked in tandem with ground radar, receiving calculated direction data via a encoded radio link, but also had its own radar with a working distance of 30 km (16 nm), which was huge at time. It was first aircraft ever able to catch a target at both head-on and following courses, at a speed of Mach 2 at an altitude of approximately 20 km (66,000 ft.), and target speeds of Mach 3 at approximately 25 km (82,000 ft.). In fact, with all that equipment, it was first ever aircraft in which the pilot was more of an operator than pilot — the plane could intercept a target by itself in both ground-guided and radar-guided modes.

But its effectiveness was bought at a high price. Being a heavy plane with small wings, it has an extremely high landing speed of 350 km/h, similar to the Space Shuttle and {{wikipedia|Buran|noicon=1}}, both of which are spaceplanes(!). It was also unstable at those kind of speeds, while oversonic yaw maneuvering was limited by its side intakes, a first for Soviet aircraft. Fuel consumption was similar to a rocket, and enormously high by modern standards — it got through 8 tonnes of kerosene in a normal 15-minute, Mach 2 interception flight.

Regular pilot training - happily Su-15 was not used at real targets often - cost the same amount of money as making cosmonaut out of him and sending him at space; common 200 flight hours per year turned into monstrous 1000tonnes of fuel, while weight of whole R-7 rocket was 280tonnes only. At modern prices such training would cost 1million of, heh, money per year - really, not less, so expenses of usage was comparable with cost of plane itself for sure.

Interception of 2Mach target, including radar selection, friend-or-foe semiautomatic recognition, missile guidance head lock, so on, could occur at head-on course only, since other way Su could not reach it; so relative approaching speed was up to 4Mach, and all process had to be pressed in 30seconds, without second chance. 3Mach demanded even faster reaction - but it should be made without any mistake, since a target would be the bomber with thermonuclear bombs. In addition, return at 1 tonne of leftover fuel was a normal part of interception flights.

Summing all that, needed piloting class was high - so high that at most units of anti-aircraft warfare, which was armed with Su-15, cadet who flew it first time alone received a cake from colleagues; it was not tradition common with other units. Other prove - only pilots of Tu-128, flying even more heavy interceptors for hours, had greater incomes in whole air forces.

Even with such qualified pilots, area of plane usage was quite narrow. Not maneuverable, without place for regular gyro sight at cockpit, it has standard armament of two heavy missiles only - typical second generation interceptor, with sole target as heavy high altitude bomber; first series was completely useless against low-speed low-altitude targets. Some of limitations was overpassed at later modifications, but fact that Su-15 as whole was used for quarter of century, and, with modifications, was produced 1300 times, is mostly prove that there is nothing more constant than temporary than evidence of its versatility.

Fact is representative more that, instead of other former Soviet fighters as MiG-21, not one flew in private hands after retiring. It's just too hard, too demanding, to be common fun. Once it was case three Su crashed in a row, in just 15minutes, due to foggy conditions and guiding system absence at receiving port. All three pilots was high-rank - so to use it alone, without ground automatics, would be risky even at future times with its artificially advanced humans. Heh. At fact, pilots respected plane, some of them even liked it, but, seems to be, not one really loved it, way this was with some other types. Well, it's hard to love something that do at its own better than under Your control.

I made model of it mostly as part of personal investigation of Yury Gagarin life and death circumstances - as Alexey Leonov, friend of Gagarin and man who made first ever EVA, said that Su was involved in second. So exactness of model is as high as possible; with conditions in which documentation of it is not at public domain yet.

Also, it was test of ability to make mostly JSBSim realistic model, which could run standalone with all systems, each switch, by minimal fixes and changes; of course it was some additional social test of community, etc.

== Features ==
* Detailed 3D external model and virtual cockpit based on real photos
[[File:Su-15-3D-Quality.jpg|thumb|Example of "Su-15" 3D model quality.]]
* Exact textures with special Soviet fonts
* Sounds from real sources
* Common FDM generated by Datcom with fuselage form modeling
* Advanced FDM polished by [[Panair|Boeing Panair]] panel code program.
[[File:Su-15-Panair Front.png|thumb|Su-15 PanAir model]]
* Further polishing of FDM with [[XFLR5]]
* Each surface, gears, tanks, missiles inclusive, have its own forces and moments calculated
* Blowing flaps with realistic effect on pitch
* Braking chute
* Engines based on graphs from real MiG-21 documentation, since it has same one, with possibility of overheating and fire
* Extinguishing system, and ability to land at one engine
* Intakes calculated realtime, with engines cutoff at resurfacing or aerodynamic shadowing mistakes
* Electrical, hydraulic, pneumatic, other systems with flows calculation via JSBSim, which means tens of milliseconds exactness, and wide specter of possible malfunctions on usage mistakes. More than 1Mb of xml code.
* Disturbed instrumentation with lags, which also calculated via JSBsim, and depended on Pitot tubes
* Pitot tubes with possibility of freezing and heaters which could burn out
* Breakable gears, blowing flaps, canopy
* Chain reactions of malfunctions caused by some minor mistakes of pilot
* Manually tuned radicompass working with NDB beacons
* "Asure" radioline commands directions to MP targets or runways
* Autopilot working from stop to stop, including takeoff, passing to beacon, MP target following, interception, landing
* Stabilization and antiskid automation
* Braking chute
* Droppable external tanks with moments and drags
* Radar working at MP targets, based on real Su-15 work movie and real data; as real one, can not see targets below model or behind mountain
* Infrared R-8P and halfactive radar R-8R missiles working at MP targets, based on real data
* Guidance heads of missiles calculated realtime, means it can lose target that making an antimissile maneuvers
* FDM of missiles calculated via JSBSim, means these could lose stability on turns. Instead of other FG missiles, these are calculated as standard JSBSim models, by data sets made by Datcom, plus own stability automation is calculated. Basically, exactness is just same as of plane model itself. Comparison with Yasim/JSBSim models quality matching is relevant here. 100Kb of xml code per missile.
* Basic version with missiles and some systems calculated by Nasal. A bit rough, still missiles works with real calculation of forces and alpha/beta, so maneuvering one slows realistically faster than one flying straight, and would not catch maneuverable target, while heavy bomber should not be an question - it's most realistic missiles at FG still. For old PCs, 7..10fps at Athlon 64X2 4000+, GeForce GTS 450, 2Gb Ram.
* Custom MPClash protocol, allowing missiles dogfight training trough MP, including missile launched by other player visibility, radar irradiation warner, lamps for own missiles catches and for catches of other pilot. At now "Su-15" model is sole one at FG having such abilities. Others can shoot in the air only, since they do not see missiles of each other, and not affected by it in any way, excluding MP messages spam; while protocol could be expanded easily with other missiles types, already existed ones inclusive. To change catch lamp to some breakage calculator is matter of day; so at now "Su-15" model is single one at FG which can shoot down model of other player really. A bit aggressive, still not one else deals with others in any way.
[[File:MPClash.png|thumb|MPClash protocol working example.]]
* Exact Russian/English PDF documentation with screenshots for any important action
* Some [[ALS_technical_notes|ALS]] candies - external and internal shadows, canopy glass reflection, red instrumentation light, reheat exhaust, etc.
[[File:Su-15-ALS.png|thumb|Example of Su-15 model ALS shadow, reflection, and instrumentation light.]]
* GetToFlyOnly license above all that, means You can fly model personally for free, but got to ask me for any other usage. Since some miscomprehendings with FG community. Lone work for free is possible, it's called "hobby". Common work without own authority is possible, it's often called just "work". Both simultaneously, plus without respect - not. And missiles of "Su" is aimed at people thinking other way. Let's see if these will work.

== Tutorial videos ==

Startup:

{{#ev:youtube|QY3VCHgHCjg}}

Automatic takeoff:

{{#ev:youtube|eRvlWUuXGkg}}

Manual takeoff:

{{#ev:youtube|JvTQzWfcp3A}}

Autopilot beacon following:

{{#ev:youtube|oSKRm5UxQ20}}

Autopilot port following:

{{#ev:youtube|huf06SzYNVw}}

Automatic convoy:

{{#ev:youtube|3nbyZKuf6WQ}}

Automatic and manual interception:

{{#ev:youtube|y-fzJV0AOOA}}

Airstart at altitude cutoff:

{{#ev:youtube|yKCZ7DRYelI}}

Automatic landing:

{{#ev:youtube|bF9GK1PwtUo}}

Manual landing:

{{#ev:youtube|vdI2qFbOGA0}}

== Model performance ==
* Maximum speed: Mach 2.05
* Maximum speed without reheat: Mach 1.5
* Practical ceiling: 18 km
* Dynamic hop ceiling: 23 km
* Maximum flight duration: 3 hours
* Maximum flight duration with reheat: 30 min
* Takeoff speed: 400 km/h
* Landing speed with blowing flaps: 325 km/h
* Stall speed: 300 km/h
* Minimal runway length: 1,500 m
* Radar range: 40 km
* Radar selection range: 30 km
* Medium missiles working range: 10 km

== Model author ==
Victor Slavutinsky, vitosnet <at> mail <dot> ru.

== External links ==
* {{wikipedia|Su-15|Wikipedia}}
* [http://www.airwar.ru/enc/fighter/su15.html Airwar.ru]

{{Sukhoi}}

[[Category:Military aircraft]]

Sukhoi Su-15

2016-11-21T22:17:03Z

Vitos: /* Tutorial videos */

{{:{{PAGENAME}}/info}}

'''Su-15''' - semi-automated Mach 2, 20 km interceptor with missiles armament.

== About ==

The Sukhoi Su-15 (NATO reporting name "'''Flagon'''") was the second semi-automated interceptor on the planet, the first being its predecessor, the Sukhoi Su-9, and for its time this was quite advanced. It worked in tandem with ground radar, receiving calculated direction data via a encoded radio link, but also had its own radar with a working distance of 30 km (16 nm), which was huge at time. It was first aircraft ever able to catch a target at both head-on and following courses, at a speed of Mach 2 at an altitude of approximately 20 km (66,000 ft.), and target speeds of Mach 3 at approximately 25 km (82,000 ft.). In fact, with all that equipment, it was first ever aircraft in which the pilot was more of an operator than pilot — the plane could intercept a target by itself in both ground-guided and radar-guided modes.

But its effectiveness was bought at a high price. Being a heavy plane with small wings, it has an extremely high landing speed of 350 km/h, similar to the Space Shuttle and {{wikipedia|Buran|noicon=1}}, both of which are spaceplanes(!). It was also unstable at those kind of speeds, while oversonic yaw maneuvering was limited by its side intakes, a first for Soviet aircraft. Fuel consumption was similar to a rocket, and enormously high by modern standards — it got through 8 tonnes of kerosene in a normal 15-minute, Mach 2 interception flight.

Regular pilot training - happily Su-15 was not used at real targets often - cost the same amount of money as making cosmonaut out of him and sending him at space; common 200 flight hours per year turned into monstrous 1000tonnes of fuel, while weight of whole R-7 rocket was 280tonnes only. At modern prices such training would cost 1million of, heh, money per year - really, not less, so expenses of usage was comparable with cost of plane itself for sure.

Interception of 2Mach target, including radar selection, friend-or-foe semiautomatic recognition, missile guidance head lock, so on, could occur at head-on course only, since other way Su could not reach it; so relative approaching speed was up to 4Mach, and all process had to be pressed in 30seconds, without second chance. 3Mach demanded even faster reaction - but it should be made without any mistake, since a target would be the bomber with thermonuclear bombs. In addition, return at 1 tonne of leftover fuel was a normal part of interception flights.

Summing all that, needed piloting class was high - so high that at most units of anti-aircraft warfare, which was armed with Su-15, cadet who flew it first time alone received a cake from colleagues; it was not tradition common with other units. Other prove - only pilots of Tu-128, flying even more heavy interceptors for hours, had greater incomes in whole air forces.

Even with such qualified pilots, area of plane usage was quite narrow. Not maneuverable, without place for regular gyro sight at cockpit, it has standard armament of two heavy missiles only - typical second generation interceptor, with sole target as heavy high altitude bomber; first series was completely useless against low-speed low-altitude targets. Some of limitations was overpassed at later modifications, but fact that Su-15 as whole was used for quarter of century, and, with modifications, was produced 1300 times, is mostly prove that there is nothing more constant than temporary than evidence of its versatility.

Fact is representative more that, instead of other former Soviet fighters as MiG-21, not one flew in private hands after retiring. It's just too hard, too demanding, to be common fun. Once it was case three Su crashed in a row, in just 15minutes, due to foggy conditions and guiding system absence at receiving port. All three pilots was high-rank - so to use it alone, without ground automatics, would be risky even at future times with its artificially advanced humans. Heh. At fact, pilots respected plane, some of them even liked it, but, seems to be, not one really loved it, way this was with some other types. Well, it's hard to love something that do at its own better than under Your control.

I made model of it mostly as part of personal investigation of Yury Gagarin life and death circumstances - as Alexey Leonov, friend of Gagarin and man who made first ever EVA, said that Su was involved in second. So exactness of model is as high as possible; with conditions in which documentation of it is not at public domain yet.

Also, it was test of ability to make mostly JSBSim realistic model, which could run standalone with all systems, each switch, by minimal fixes and changes; of course it was some additional social test of community, etc.

== Features ==
* Detailed 3D external model and virtual cockpit based on real photos
[[File:Su-15-3D-Quality.jpg|thumb|Example of "Su-15" 3D model quality.]]
* Exact textures with special Soviet fonts
* Sounds from real sources
* Common FDM generated by Datcom with fuselage form modeling
* Advanced FDM polished by [[Panair|Boeing Panair]] panel code program.
[[File:Su-15-Panair Front.png|thumb|Su-15 PanAir model]]
* Further polishing of FDM with [[XFLR5]]
* Each surface, gears, tanks, missiles inclusive, have its own forces and moments calculated
* Blowing flaps with realistic effect on pitch
* Braking chute
* Engines based on graphs from real MiG-21 documentation, since it has same one, with possibility of overheating and fire
* Extinguishing system, and ability to land at one engine
* Intakes calculated realtime, with engines cutoff at resurfacing or aerodynamic shadowing mistakes
* Electrical, hydraulic, pneumatic, other systems with flows calculation via JSBSim, which means tens of milliseconds exactness, and wide specter of possible malfunctions on usage mistakes. More than 1Mb of xml code.
* Disturbed instrumentation with lags, which also calculated via JSBsim, and depended on Pitot tubes
* Pitot tubes with possibility of freezing and heaters which could burn out
* Breakable gears, blowing flaps, canopy
* Chain reactions of malfunctions caused by some minor mistakes of pilot
* Manually tuned radicompass working with NDB beacons
* "Asure" radioline commands directions to MP targets or runways
* Autopilot working from stop to stop, including takeoff, passing to beacon, MP target following, interception, landing
* Stabilization and antiskid automation
* Braking chute
* Droppable external tanks with moments and drags
* Radar working at MP targets, based on real Su-15 work movie and real data; as real one, can not see targets below model or behind mountain
* Infrared R-8P and halfactive radar R-8R missiles working at MP targets, based on real data
* Guidance heads of missiles calculated realtime, means it can lose target that making an antimissile maneuvers
* FDM of missiles calculated via JSBSim, means these could lose stability on turns. Instead of other FG missiles, these are calculated as standard JSBSim models, by data sets made by Datcom, plus own stability automation is calculated. Basically, exactness is just same as of plane model itself. Comparison with Yasim/JSBSim models quality matching is relevant here. 100Kb of xml code per missile.
* Basic version with missiles and some systems calculated by Nasal. A bit rough, still missiles works with real calculation of forces and alpha/beta, so maneuvering one slows realistically faster than one flying straight, and would not catch maneuverable target, while heavy bomber should not be an question - it's most realistic missiles at FG still. For old PCs, 7..10fps at Athlon 64X2 4000+, GeForce GTS 450, 2Gb Ram.
* Custom MPClash protocol, allowing missiles dogfight training trough MP, including missile launched by other player visibility, radar irradiation warner, lamps for own missiles catches and for catches of other pilot. At now "Su-15" model is sole one at FG having such abilities. Others can shoot in the air only, since they do not see missiles of each other, and not affected by it in any way, excluding MP messages spam; while protocol could be expanded easily with other missiles types, already existed ones inclusive. To change catch lamp to some breakage calculator is matter of day; so at now "Su-15" model is single one at FG which can shoot down model of other player really. A bit aggressive, still not one else deals with others in any way.
[[File:MPClash.png|thumb|MPClash protocol working example.]]
* Exact Russian/English PDF documentation with screenshots for any important action
* Some [[ALS_technical_notes|ALS]] candies - external and internal shadows, canopy glass reflection, red instrumentation light, reheat exhaust, etc.
[[File:Su-15-ALS.png|thumb|Example of Su-15 model ALS shadow, reflection, and instrumentation light.]]
* GetToFlyOnly license above all that, means You can fly model personally for free, but got to ask me for any other usage. Since some miscomprehendings with FG community. Lone work for free is possible, it's called "hobby". Common work without own authority is possible, it's often called just "work". Both simultaneously, plus without respect - not. And missiles of "Su" is aimed at people thinking other way. Let's see if these will work.

== Tutorial videos ==

Startup:

{{#ev:youtube|QY3VCHgHCjg}}

Automatic takeoff:

{{#ev:youtube|eRvlWUuXGkg}}

Manual takeoff:

{{#ev:youtube|JvTQzWfcp3A}}

Autopilot beacon following:

{{#ev:youtube|oSKRm5UxQ20}}

Autopilot port following:

{{#ev:youtube|huf06SzYNVw}}

Automatic convoy:

{{#ev:youtube|3nbyZKuf6WQ}}

Automatic and manual interception:

{{#ev:youtube|y-fzJV0AOOA}}

Airstart at altitude cutoff:

{{#ev:youtube|jh-hzbG5FzI}}

Automatic landing:

{{#ev:youtube|bF9GK1PwtUo}}

Manual landing:

{{#ev:youtube|vdI2qFbOGA0}}

== Model performance ==
* Maximum speed: Mach 2.05
* Maximum speed without reheat: Mach 1.5
* Practical ceiling: 18 km
* Dynamic hop ceiling: 23 km
* Maximum flight duration: 3 hours
* Maximum flight duration with reheat: 30 min
* Takeoff speed: 400 km/h
* Landing speed with blowing flaps: 325 km/h
* Stall speed: 300 km/h
* Minimal runway length: 1,500 m
* Radar range: 40 km
* Radar selection range: 30 km
* Medium missiles working range: 10 km

== Model author ==
Victor Slavutinsky, vitosnet <at> mail <dot> ru.

== External links ==
* {{wikipedia|Su-15|Wikipedia}}
* [http://www.airwar.ru/enc/fighter/su15.html Airwar.ru]

{{Sukhoi}}

[[Category:Military aircraft]]

Sukhoi Su-15

2016-11-18T21:40:27Z

Vitos: /* Tutorial videos */

{{:{{PAGENAME}}/info}}

'''Su-15''' - semi-automated Mach 2, 20 km interceptor with missiles armament.

== About ==

The Sukhoi Su-15 (NATO reporting name "'''Flagon'''") was the second semi-automated interceptor on the planet, the first being its predecessor, the Sukhoi Su-9, and for its time this was quite advanced. It worked in tandem with ground radar, receiving calculated direction data via a encoded radio link, but also had its own radar with a working distance of 30 km (16 nm), which was huge at time. It was first aircraft ever able to catch a target at both head-on and following courses, at a speed of Mach 2 at an altitude of approximately 20 km (66,000 ft.), and target speeds of Mach 3 at approximately 25 km (82,000 ft.). In fact, with all that equipment, it was first ever aircraft in which the pilot was more of an operator than pilot — the plane could intercept a target by itself in both ground-guided and radar-guided modes.

But its effectiveness was bought at a high price. Being a heavy plane with small wings, it has an extremely high landing speed of 350 km/h, similar to the Space Shuttle and {{wikipedia|Buran|noicon=1}}, both of which are spaceplanes(!). It was also unstable at those kind of speeds, while oversonic yaw maneuvering was limited by its side intakes, a first for Soviet aircraft. Fuel consumption was similar to a rocket, and enormously high by modern standards — it got through 8 tonnes of kerosene in a normal 15-minute, Mach 2 interception flight.

Regular pilot training - happily Su-15 was not used at real targets often - cost the same amount of money as making cosmonaut out of him and sending him at space; common 200 flight hours per year turned into monstrous 1000tonnes of fuel, while weight of whole R-7 rocket was 280tonnes only. At modern prices such training would cost 1million of, heh, money per year - really, not less, so expenses of usage was comparable with cost of plane itself for sure.

Interception of 2Mach target, including radar selection, friend-or-foe semiautomatic recognition, missile guidance head lock, so on, could occur at head-on course only, since other way Su could not reach it; so relative approaching speed was up to 4Mach, and all process had to be pressed in 30seconds, without second chance. 3Mach demanded even faster reaction - but it should be made without any mistake, since a target would be the bomber with thermonuclear bombs. In addition, return at 1 tonne of leftover fuel was a normal part of interception flights.

Summing all that, needed piloting class was high - so high that at most units of anti-aircraft warfare, which was armed with Su-15, cadet who flew it first time alone received a cake from colleagues; it was not tradition common with other units. Other prove - only pilots of Tu-128, flying even more heavy interceptors for hours, had greater incomes in whole air forces.

Even with such qualified pilots, area of plane usage was quite narrow. Not maneuverable, without place for regular gyro sight at cockpit, it has standard armament of two heavy missiles only - typical second generation interceptor, with sole target as heavy high altitude bomber; first series was completely useless against low-speed low-altitude targets. Some of limitations was overpassed at later modifications, but fact that Su-15 as whole was used for quarter of century, and, with modifications, was produced 1300 times, is mostly prove that there is nothing more constant than temporary than evidence of its versatility.

Fact is representative more that, instead of other former Soviet fighters as MiG-21, not one flew in private hands after retiring. It's just too hard, too demanding, to be common fun. Once it was case three Su crashed in a row, in just 15minutes, due to foggy conditions and guiding system absence at receiving port. All three pilots was high-rank - so to use it alone, without ground automatics, would be risky even at future times with its artificially advanced humans. Heh. At fact, pilots respected plane, some of them even liked it, but, seems to be, not one really loved it, way this was with some other types. Well, it's hard to love something that do at its own better than under Your control.

I made model of it mostly as part of personal investigation of Yury Gagarin life and death circumstances - as Alexey Leonov, friend of Gagarin and man who made first ever EVA, said that Su was involved in second. So exactness of model is as high as possible; with conditions in which documentation of it is not at public domain yet.

Also, it was test of ability to make mostly JSBSim realistic model, which could run standalone with all systems, each switch, by minimal fixes and changes; of course it was some additional social test of community, etc.

== Features ==
* Detailed 3D external model and virtual cockpit based on real photos
[[File:Su-15-3D-Quality.jpg|thumb|Example of "Su-15" 3D model quality.]]
* Exact textures with special Soviet fonts
* Sounds from real sources
* Common FDM generated by Datcom with fuselage form modeling
* Advanced FDM polished by [[Panair|Boeing Panair]] panel code program.
[[File:Su-15-Panair Front.png|thumb|Su-15 PanAir model]]
* Further polishing of FDM with [[XFLR5]]
* Each surface, gears, tanks, missiles inclusive, have its own forces and moments calculated
* Blowing flaps with realistic effect on pitch
* Braking chute
* Engines based on graphs from real MiG-21 documentation, since it has same one, with possibility of overheating and fire
* Extinguishing system, and ability to land at one engine
* Intakes calculated realtime, with engines cutoff at resurfacing or aerodynamic shadowing mistakes
* Electrical, hydraulic, pneumatic, other systems with flows calculation via JSBSim, which means tens of milliseconds exactness, and wide specter of possible malfunctions on usage mistakes. More than 1Mb of xml code.
* Disturbed instrumentation with lags, which also calculated via JSBsim, and depended on Pitot tubes
* Pitot tubes with possibility of freezing and heaters which could burn out
* Breakable gears, blowing flaps, canopy
* Chain reactions of malfunctions caused by some minor mistakes of pilot
* Manually tuned radicompass working with NDB beacons
* "Asure" radioline commands directions to MP targets or runways
* Autopilot working from stop to stop, including takeoff, passing to beacon, MP target following, interception, landing
* Stabilization and antiskid automation
* Braking chute
* Droppable external tanks with moments and drags
* Radar working at MP targets, based on real Su-15 work movie and real data; as real one, can not see targets below model or behind mountain
* Infrared R-8P and halfactive radar R-8R missiles working at MP targets, based on real data
* Guidance heads of missiles calculated realtime, means it can lose target that making an antimissile maneuvers
* FDM of missiles calculated via JSBSim, means these could lose stability on turns. Instead of other FG missiles, these are calculated as standard JSBSim models, by data sets made by Datcom, plus own stability automation is calculated. Basically, exactness is just same as of plane model itself. Comparison with Yasim/JSBSim models quality matching is relevant here. 100Kb of xml code per missile.
* Basic version with missiles and some systems calculated by Nasal. A bit rough, still missiles works with real calculation of forces and alpha/beta, so maneuvering one slows realistically faster than one flying straight, and would not catch maneuverable target, while heavy bomber should not be an question - it's most realistic missiles at FG still. For old PCs, 7..10fps at Athlon 64X2 4000+, GeForce GTS 450, 2Gb Ram.
* Custom MPClash protocol, allowing missiles dogfight training trough MP, including missile launched by other player visibility, radar irradiation warner, lamps for own missiles catches and for catches of other pilot. At now "Su-15" model is sole one at FG having such abilities. Others can shoot in the air only, since they do not see missiles of each other, and not affected by it in any way, excluding MP messages spam; while protocol could be expanded easily with other missiles types, already existed ones inclusive. To change catch lamp to some breakage calculator is matter of day; so at now "Su-15" model is single one at FG which can shoot down model of other player really. A bit aggressive, still not one else deals with others in any way.
[[File:MPClash.png|thumb|MPClash protocol working example.]]
* Exact Russian/English PDF documentation with screenshots for any important action
* Some [[ALS_technical_notes|ALS]] candies - external and internal shadows, canopy glass reflection, red instrumentation light, reheat exhaust, etc.
[[File:Su-15-ALS.png|thumb|Example of Su-15 model ALS shadow, reflection, and instrumentation light.]]
* GetToFlyOnly license above all that, means You can fly model personally for free, but got to ask me for any other usage. Since some miscomprehendings with FG community. Lone work for free is possible, it's called "hobby". Common work without own authority is possible, it's often called just "work". Both simultaneously, plus without respect - not. And missiles of "Su" is aimed at people thinking other way. Let's see if these will work.

== Tutorial videos ==

Startup:

{{#ev:youtube|QY3VCHgHCjg}}

Automatic takeoff:

{{#ev:youtube|eRvlWUuXGkg}}

Manual takeoff:

{{#ev:youtube|JvTQzWfcp3A}}

Autopilot beacon following:

{{#ev:youtube|oSKRm5UxQ20}}

Autopilot port following:

{{#ev:youtube|huf06SzYNVw}}

Automatic convoy:

{{#ev:youtube|3nbyZKuf6WQ}}

Automatic and manual interception:

{{#ev:youtube|y-fzJV0AOOA}}

Automatic landing:

{{#ev:youtube|bF9GK1PwtUo}}

Manual landing:

{{#ev:youtube|vdI2qFbOGA0}}

== Model performance ==
* Maximum speed: Mach 2.05
* Maximum speed without reheat: Mach 1.5
* Practical ceiling: 18 km
* Dynamic hop ceiling: 23 km
* Maximum flight duration: 3 hours
* Maximum flight duration with reheat: 30 min
* Takeoff speed: 400 km/h
* Landing speed with blowing flaps: 325 km/h
* Stall speed: 300 km/h
* Minimal runway length: 1,500 m
* Radar range: 40 km
* Radar selection range: 30 km
* Medium missiles working range: 10 km

== Model author ==
Victor Slavutinsky, vitosnet <at> mail <dot> ru.

== External links ==
* {{wikipedia|Su-15|Wikipedia}}
* [http://www.airwar.ru/enc/fighter/su15.html Airwar.ru]

{{Sukhoi}}

[[Category:Military aircraft]]

Sukhoi Su-15

2016-11-16T23:11:41Z

Vitos:

{{:{{PAGENAME}}/info}}

'''Su-15''' - semi-automated Mach 2, 20 km interceptor with missiles armament.

== About ==

The Sukhoi Su-15 (NATO reporting name "'''Flagon'''") was the second semi-automated interceptor on the planet, the first being its predecessor, the Sukhoi Su-9, and for its time this was quite advanced. It worked in tandem with ground radar, receiving calculated direction data via a encoded radio link, but also had its own radar with a working distance of 30 km (16 nm), which was huge at time. It was first aircraft ever able to catch a target at both head-on and following courses, at a speed of Mach 2 at an altitude of approximately 20 km (66,000 ft.), and target speeds of Mach 3 at approximately 25 km (82,000 ft.). In fact, with all that equipment, it was first ever aircraft in which the pilot was more of an operator than pilot — the plane could intercept a target by itself in both ground-guided and radar-guided modes.

But its effectiveness was bought at a high price. Being a heavy plane with small wings, it has an extremely high landing speed of 350 km/h, similar to the Space Shuttle and {{wikipedia|Buran|noicon=1}}, both of which are spaceplanes(!). It was also unstable at those kind of speeds, while oversonic yaw maneuvering was limited by its side intakes, a first for Soviet aircraft. Fuel consumption was similar to a rocket, and enormously high by modern standards — it got through 8 tonnes of kerosene in a normal 15-minute, Mach 2 interception flight.

Regular pilot training - happily Su-15 was not used at real targets often - cost the same amount of money as making cosmonaut out of him and sending him at space; common 200 flight hours per year turned into monstrous 1000tonnes of fuel, while weight of whole R-7 rocket was 280tonnes only. At modern prices such training would cost 1million of, heh, money per year - really, not less, so expenses of usage was comparable with cost of plane itself for sure.

Interception of 2Mach target, including radar selection, friend-or-foe semiautomatic recognition, missile guidance head lock, so on, could occur at head-on course only, since other way Su could not reach it; so relative approaching speed was up to 4Mach, and all process had to be pressed in 30seconds, without second chance. 3Mach demanded even faster reaction - but it should be made without any mistake, since a target would be the bomber with thermonuclear bombs. In addition, return at 1 tonne of leftover fuel was a normal part of interception flights.

Summing all that, needed piloting class was high - so high that at most units of anti-aircraft warfare, which was armed with Su-15, cadet who flew it first time alone received a cake from colleagues; it was not tradition common with other units. Other prove - only pilots of Tu-128, flying even more heavy interceptors for hours, had greater incomes in whole air forces.

Even with such qualified pilots, area of plane usage was quite narrow. Not maneuverable, without place for regular gyro sight at cockpit, it has standard armament of two heavy missiles only - typical second generation interceptor, with sole target as heavy high altitude bomber; first series was completely useless against low-speed low-altitude targets. Some of limitations was overpassed at later modifications, but fact that Su-15 as whole was used for quarter of century, and, with modifications, was produced 1300 times, is mostly prove that there is nothing more constant than temporary than evidence of its versatility.

Fact is representative more that, instead of other former Soviet fighters as MiG-21, not one flew in private hands after retiring. It's just too hard, too demanding, to be common fun. Once it was case three Su crashed in a row, in just 15minutes, due to foggy conditions and guiding system absence at receiving port. All three pilots was high-rank - so to use it alone, without ground automatics, would be risky even at future times with its artificially advanced humans. Heh. At fact, pilots respected plane, some of them even liked it, but, seems to be, not one really loved it, way this was with some other types. Well, it's hard to love something that do at its own better than under Your control.

I made model of it mostly as part of personal investigation of Yury Gagarin life and death circumstances - as Alexey Leonov, friend of Gagarin and man who made first ever EVA, said that Su was involved in second. So exactness of model is as high as possible; with conditions in which documentation of it is not at public domain yet.

Also, it was test of ability to make mostly JSBSim realistic model, which could run standalone with all systems, each switch, by minimal fixes and changes; of course it was some additional social test of community, etc.

== Features ==
* Detailed 3D external model and virtual cockpit based on real photos
[[File:Su-15-3D-Quality.jpg|thumb|Example of "Su-15" 3D model quality.]]
* Exact textures with special Soviet fonts
* Sounds from real sources
* Common FDM generated by Datcom with fuselage form modeling
* Advanced FDM polished by [[Panair|Boeing Panair]] panel code program.
[[File:Su-15-Panair Front.png|thumb|Su-15 PanAir model]]
* Further polishing of FDM with [[XFLR5]]
* Each surface, gears, tanks, missiles inclusive, have its own forces and moments calculated
* Blowing flaps with realistic effect on pitch
* Braking chute
* Engines based on graphs from real MiG-21 documentation, since it has same one, with possibility of overheating and fire
* Extinguishing system, and ability to land at one engine
* Intakes calculated realtime, with engines cutoff at resurfacing or aerodynamic shadowing mistakes
* Electrical, hydraulic, pneumatic, other systems with flows calculation via JSBSim, which means tens of milliseconds exactness, and wide specter of possible malfunctions on usage mistakes. More than 1Mb of xml code.
* Disturbed instrumentation with lags, which also calculated via JSBsim, and depended on Pitot tubes
* Pitot tubes with possibility of freezing and heaters which could burn out
* Breakable gears, blowing flaps, canopy
* Chain reactions of malfunctions caused by some minor mistakes of pilot
* Manually tuned radicompass working with NDB beacons
* "Asure" radioline commands directions to MP targets or runways
* Autopilot working from stop to stop, including takeoff, passing to beacon, MP target following, interception, landing
* Stabilization and antiskid automation
* Braking chute
* Droppable external tanks with moments and drags
* Radar working at MP targets, based on real Su-15 work movie and real data; as real one, can not see targets below model or behind mountain
* Infrared R-8P and halfactive radar R-8R missiles working at MP targets, based on real data
* Guidance heads of missiles calculated realtime, means it can lose target that making an antimissile maneuvers
* FDM of missiles calculated via JSBSim, means these could lose stability on turns. Instead of other FG missiles, these are calculated as standard JSBSim models, by data sets made by Datcom, plus own stability automation is calculated. Basically, exactness is just same as of plane model itself. Comparison with Yasim/JSBSim models quality matching is relevant here. 100Kb of xml code per missile.
* Basic version with missiles and some systems calculated by Nasal. A bit rough, still missiles works with real calculation of forces and alpha/beta, so maneuvering one slows realistically faster than one flying straight, and would not catch maneuverable target, while heavy bomber should not be an question - it's most realistic missiles at FG still. For old PCs, 7..10fps at Athlon 64X2 4000+, GeForce GTS 450, 2Gb Ram.
* Custom MPClash protocol, allowing missiles dogfight training trough MP, including missile launched by other player visibility, radar irradiation warner, lamps for own missiles catches and for catches of other pilot. At now "Su-15" model is sole one at FG having such abilities. Others can shoot in the air only, since they do not see missiles of each other, and not affected by it in any way, excluding MP messages spam; while protocol could be expanded easily with other missiles types, already existed ones inclusive. To change catch lamp to some breakage calculator is matter of day; so at now "Su-15" model is single one at FG which can shoot down model of other player really. A bit aggressive, still not one else deals with others in any way.
[[File:MPClash.png|thumb|MPClash protocol working example.]]
* Exact Russian/English PDF documentation with screenshots for any important action
* Some [[ALS_technical_notes|ALS]] candies - external and internal shadows, canopy glass reflection, red instrumentation light, reheat exhaust, etc.
[[File:Su-15-ALS.png|thumb|Example of Su-15 model ALS shadow, reflection, and instrumentation light.]]
* GetToFlyOnly license above all that, means You can fly model personally for free, but got to ask me for any other usage. Since some miscomprehendings with FG community. Lone work for free is possible, it's called "hobby". Common work without own authority is possible, it's often called just "work". Both simultaneously, plus without respect - not. And missiles of "Su" is aimed at people thinking other way. Let's see if these will work.

== Tutorial videos ==

Startup:

{{#ev:youtube|QY3VCHgHCjg}}

Automatic takeoff:

{{#ev:youtube|eRvlWUuXGkg}}

Manual takeoff:

{{#ev:youtube|JvTQzWfcp3A}}

Autopilot beacon following:

{{#ev:youtube|oSKRm5UxQ20}}

Autopilot port following:

{{#ev:youtube|huf06SzYNVw}}

Automatic landing:

{{#ev:youtube|bF9GK1PwtUo}}

Manual landing:

{{#ev:youtube|vdI2qFbOGA0}}

== Model performance ==
* Maximum speed: Mach 2.05
* Maximum speed without reheat: Mach 1.5
* Practical ceiling: 18 km
* Dynamic hop ceiling: 23 km
* Maximum flight duration: 3 hours
* Maximum flight duration with reheat: 30 min
* Takeoff speed: 400 km/h
* Landing speed with blowing flaps: 325 km/h
* Stall speed: 300 km/h
* Minimal runway length: 1,500 m
* Radar range: 40 km
* Radar selection range: 30 km
* Medium missiles working range: 10 km

== Model author ==
Victor Slavutinsky, vitosnet <at> mail <dot> ru.

== External links ==
* {{wikipedia|Su-15|Wikipedia}}
* [http://www.airwar.ru/enc/fighter/su15.html Airwar.ru]

{{Sukhoi}}

[[Category:Military aircraft]]

Sukhoi Su-15

2016-11-08T13:12:57Z

Vitos: /* Features */

{{:{{PAGENAME}}/info}}

'''Su-15''' - semi-automated Mach 2, 20 km interceptor with missiles armament.

== About ==

The Sukhoi Su-15 (NATO reporting name "'''Flagon'''") was the second semi-automated interceptor on the planet, the first being its predecessor, the Sukhoi Su-9, and for its time this was quite advanced. It worked in tandem with ground radar, receiving calculated direction data via a encoded radio link, but also had its own radar with a working distance of 30 km (16 nm), which was huge at time. It was first aircraft ever able to catch a target at both head-on and following courses, at a speed of Mach 2 at an altitude of approximately 20 km (66,000 ft.), and target speeds of Mach 3 at approximately 25 km (82,000 ft.). In fact, with all that equipment, it was first ever aircraft in which the pilot was more of an operator than pilot — the plane could intercept a target by itself in both ground-guided and radar-guided modes.

But its effectiveness was bought at a high price. Being a heavy plane with small wings, it has an extremely high landing speed of 350 km/h, similar to the Space Shuttle and {{wikipedia|Buran|noicon=1}}, both of which are spaceplanes(!). It was also unstable at those kind of speeds, while oversonic yaw maneuvering was limited by its side intakes, a first for Soviet aircraft. Fuel consumption was similar to a rocket, and enormously high by modern standards — it got through 8 tonnes of kerosene in a normal 15-minute, Mach 2 interception flight.

Regular pilot training - happily Su-15 was not used at real targets often - cost the same amount of money as making cosmonaut out of him and sending him at space; common 200 flight hours per year turned into monstrous 1000tonnes of fuel, while weight of whole R-7 rocket was 280tonnes only. At modern prices such training would cost 1million of, heh, money per year - really, not less, so expenses of usage was comparable with cost of plane itself for sure.

Interception of 2Mach target, including radar selection, friend-or-foe semiautomatic recognition, missile guidance head lock, so on, could occur at head-on course only, since other way Su could not reach it; so relative approaching speed was up to 4Mach, and all process had to be pressed in 30seconds, without second chance. 3Mach demanded even faster reaction - but it should be made without any mistake, since a target would be the bomber with thermonuclear bombs. In addition, return at 1 tonne of leftover fuel was a normal part of interception flights.

Summing all that, needed piloting class was high - so high that at most units of anti-aircraft warfare, which was armed with Su-15, cadet who flew it first time alone received a cake from colleagues; it was not tradition common with other units. Other prove - only pilots of Tu-128, flying even more heavy interceptors for hours, had greater incomes in whole air forces.

Even with such qualified pilots, area of plane usage was quite narrow. Not maneuverable, without place for regular gyro sight at cockpit, it has standard armament of two heavy missiles only - typical second generation interceptor, with sole target as heavy high altitude bomber; first series was completely useless against low-speed low-altitude targets. Some of limitations was overpassed at later modifications, but fact that Su-15 as whole was used for quarter of century, and, with modifications, was produced 1300 times, is mostly prove that there is nothing more constant than temporary than evidence of its versatility.

Fact is representative more that, instead of other former Soviet fighters as MiG-21, not one flew in private hands after retiring. It's just too hard, too demanding, to be common fun. Once it was case three Su crashed in a row, in just 15minutes, due to foggy conditions and guiding system absence at receiving port. All three pilots was high-rank - so to use it alone, without ground automatics, would be risky even at future times with its artificially advanced humans. Heh. At fact, pilots respected plane, some of them even liked it, but, seems to be, not one really loved it, way this was with some other types. Well, it's hard to love something that do at its own better than under Your control.

I made model of it mostly as part of personal investigation of Yury Gagarin life and death circumstances - as Alexey Leonov, friend of Gagarin and man who made first ever EVA, said that Su was involved in second. So exactness of model is as high as possible; with conditions in which documentation of it is not at public domain yet.

Also, it was test of ability to make mostly JSBSim realistic model, which could run standalone with all systems, each switch, by minimal fixes and changes; of course it was some additional social test of community, etc.

== Features ==
* Detailed 3D external model and virtual cockpit based on real photos
[[File:Su-15-3D-Quality.jpg|thumb|Example of "Su-15" 3D model quality.]]
* Exact textures with special Soviet fonts
* Sounds from real sources
* Common FDM generated by Datcom with fuselage form modeling
* Advanced FDM polished by [[Panair|Boeing Panair]] panel code program.
[[File:Su-15-Panair Front.png|thumb|Su-15 PanAir model]]
* Further polishing of FDM with [[XFLR5]]
* Each surface, gears, tanks, missiles inclusive, have its own forces and moments calculated
* Blowing flaps with realistic effect on pitch
* Braking chute
* Engines based on graphs from real MiG-21 documentation, since it has same one, with possibility of overheating and fire
* Extinguishing system, and ability to land at one engine
* Intakes calculated realtime, with engines cutoff at resurfacing or aerodynamic shadowing mistakes
* Electrical, hydraulic, pneumatic, other systems with flows calculation via JSBSim, which means tens of milliseconds exactness, and wide specter of possible malfunctions on usage mistakes. More than 1Mb of xml code.
* Disturbed instrumentation with lags, which also calculated via JSBsim, and depended on Pitot tubes
* Pitot tubes with possibility of freezing and heaters which could burn out
* Breakable gears, blowing flaps, canopy
* Chain reactions of malfunctions caused by some minor mistakes of pilot
* Manually tuned radicompass working with NDB beacons
* "Asure" radioline commands directions to MP targets or runways
* Autopilot working from stop to stop, including takeoff, passing to beacon, MP target following, interception, landing
* Stabilization and antiskid automation
* Braking chute
* Droppable external tanks with moments and drags
* Radar working at MP targets, based on real Su-15 work movie and real data; as real one, can not see targets below model or behind mountain
* Infrared R-8P and halfactive radar R-8R missiles working at MP targets, based on real data
* Guidance heads of missiles calculated realtime, means it can lose target that making an antimissile maneuvers
* FDM of missiles calculated via JSBSim, means these could lose stability on turns. Instead of other FG missiles, these are calculated as standard JSBSim models, by data sets made by Datcom, plus own stability automation is calculated. Basically, exactness is just same as of plane model itself. Comparison with Yasim/JSBSim models quality matching is relevant here. 100Kb of xml code per missile.
* Basic version with missiles and some systems calculated by Nasal. A bit rough, still missiles works with real calculation of forces and alpha/beta, so maneuvering one slows realistically faster than one flying straight, and would not catch maneuverable target, while heavy bomber should not be an question - it's most realistic missiles at FG still. For old PCs, 7..10fps at Athlon 64X2 4000+, GeForce GTS 450, 2Gb Ram.
* Custom MPClash protocol, allowing missiles dogfight training trough MP, including missile launched by other player visibility, radar irradiation warner, lamps for own missiles catches and for catches of other pilot. At now "Su-15" model is sole one at FG having such abilities. Others can shoot in the air only, since they do not see missiles of each other, and not affected by it in any way, excluding MP messages spam; while protocol could be expanded easily with other missiles types, already existed ones inclusive. To change catch lamp to some breakage calculator is matter of day; so at now "Su-15" model is single one at FG which can shoot down model of other player really. A bit aggressive, still not one else deals with others in any way.
[[File:MPClash.png|thumb|MPClash protocol working example.]]
* Exact Russian/English PDF documentation with screenshots for any important action
* Some [[ALS_technical_notes|ALS]] candies - external and internal shadows, canopy glass reflection, red instrumentation light, reheat exhaust, etc.
[[File:Su-15-ALS.png|thumb|Example of Su-15 model ALS shadow, reflection, and instrumentation light.]]
* GetToFlyOnly license above all that, means You can fly model personally for free, but got to ask me for any other usage. Since some miscomprehendings with FG community. Lone work for free is possible, it's called "hobby". Common work without own authority is possible, it's often called just "work". Both simultaneously, plus without respect - not. And missiles of "Su" is aimed at people thinking other way. Let's see if these will work.

== Model performance ==
* Maximum speed: Mach 2.05
* Maximum speed without reheat: Mach 1.5
* Practical ceiling: 18 km
* Dynamic hop ceiling: 23 km
* Maximum flight duration: 3 hours
* Maximum flight duration with reheat: 30 min
* Takeoff speed: 400 km/h
* Landing speed with blowing flaps: 325 km/h
* Stall speed: 300 km/h
* Minimal runway length: 1,500 m
* Radar range: 40 km
* Radar selection range: 30 km
* Medium missiles working range: 10 km

== Model author ==
Victor Slavutinsky, vitosnet <at> mail <dot> ru.

== External links ==
* {{wikipedia|Su-15|Wikipedia}}
* [http://www.airwar.ru/enc/fighter/su15.html Airwar.ru]

{{Sukhoi}}

[[Category:Military aircraft]]

File:Su-15-ALS.png

2016-11-08T13:11:59Z

Vitos: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Example of Su-15 model ALS shadow, reflection, and instrumentation light.}}
|date=2016-11-08
|source={{own}}
|author=[[User:Vitos|Vitos]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

Sukhoi Su-15

2016-11-08T13:09:26Z

Vitos: /* Features */

{{:{{PAGENAME}}/info}}

'''Su-15''' - semi-automated Mach 2, 20 km interceptor with missiles armament.

== About ==

The Sukhoi Su-15 (NATO reporting name "'''Flagon'''") was the second semi-automated interceptor on the planet, the first being its predecessor, the Sukhoi Su-9, and for its time this was quite advanced. It worked in tandem with ground radar, receiving calculated direction data via a encoded radio link, but also had its own radar with a working distance of 30 km (16 nm), which was huge at time. It was first aircraft ever able to catch a target at both head-on and following courses, at a speed of Mach 2 at an altitude of approximately 20 km (66,000 ft.), and target speeds of Mach 3 at approximately 25 km (82,000 ft.). In fact, with all that equipment, it was first ever aircraft in which the pilot was more of an operator than pilot — the plane could intercept a target by itself in both ground-guided and radar-guided modes.

But its effectiveness was bought at a high price. Being a heavy plane with small wings, it has an extremely high landing speed of 350 km/h, similar to the Space Shuttle and {{wikipedia|Buran|noicon=1}}, both of which are spaceplanes(!). It was also unstable at those kind of speeds, while oversonic yaw maneuvering was limited by its side intakes, a first for Soviet aircraft. Fuel consumption was similar to a rocket, and enormously high by modern standards — it got through 8 tonnes of kerosene in a normal 15-minute, Mach 2 interception flight.

Regular pilot training - happily Su-15 was not used at real targets often - cost the same amount of money as making cosmonaut out of him and sending him at space; common 200 flight hours per year turned into monstrous 1000tonnes of fuel, while weight of whole R-7 rocket was 280tonnes only. At modern prices such training would cost 1million of, heh, money per year - really, not less, so expenses of usage was comparable with cost of plane itself for sure.

Interception of 2Mach target, including radar selection, friend-or-foe semiautomatic recognition, missile guidance head lock, so on, could occur at head-on course only, since other way Su could not reach it; so relative approaching speed was up to 4Mach, and all process had to be pressed in 30seconds, without second chance. 3Mach demanded even faster reaction - but it should be made without any mistake, since a target would be the bomber with thermonuclear bombs. In addition, return at 1 tonne of leftover fuel was a normal part of interception flights.

Summing all that, needed piloting class was high - so high that at most units of anti-aircraft warfare, which was armed with Su-15, cadet who flew it first time alone received a cake from colleagues; it was not tradition common with other units. Other prove - only pilots of Tu-128, flying even more heavy interceptors for hours, had greater incomes in whole air forces.

Even with such qualified pilots, area of plane usage was quite narrow. Not maneuverable, without place for regular gyro sight at cockpit, it has standard armament of two heavy missiles only - typical second generation interceptor, with sole target as heavy high altitude bomber; first series was completely useless against low-speed low-altitude targets. Some of limitations was overpassed at later modifications, but fact that Su-15 as whole was used for quarter of century, and, with modifications, was produced 1300 times, is mostly prove that there is nothing more constant than temporary than evidence of its versatility.

Fact is representative more that, instead of other former Soviet fighters as MiG-21, not one flew in private hands after retiring. It's just too hard, too demanding, to be common fun. Once it was case three Su crashed in a row, in just 15minutes, due to foggy conditions and guiding system absence at receiving port. All three pilots was high-rank - so to use it alone, without ground automatics, would be risky even at future times with its artificially advanced humans. Heh. At fact, pilots respected plane, some of them even liked it, but, seems to be, not one really loved it, way this was with some other types. Well, it's hard to love something that do at its own better than under Your control.

I made model of it mostly as part of personal investigation of Yury Gagarin life and death circumstances - as Alexey Leonov, friend of Gagarin and man who made first ever EVA, said that Su was involved in second. So exactness of model is as high as possible; with conditions in which documentation of it is not at public domain yet.

Also, it was test of ability to make mostly JSBSim realistic model, which could run standalone with all systems, each switch, by minimal fixes and changes; of course it was some additional social test of community, etc.

== Features ==
* Detailed 3D external model and virtual cockpit based on real photos
[[File:Su-15-3D-Quality.jpg|thumb|Example of "Su-15" 3D model quality.]]
* Exact textures with special Soviet fonts
* Sounds from real sources
* Common FDM generated by Datcom with fuselage form modeling
* Advanced FDM polished by [[Panair|Boeing Panair]] panel code program.
[[File:Su-15-Panair Front.png|thumb|Su-15 PanAir model]]
* Further polishing of FDM with [[XFLR5]]
* Each surface, gears, tanks, missiles inclusive, have its own forces and moments calculated
* Blowing flaps with realistic effect on pitch
* Braking chute
* Engines based on graphs from real MiG-21 documentation, since it has same one, with possibility of overheating and fire
* Extinguishing system, and ability to land at one engine
* Intakes calculated realtime, with engines cutoff at resurfacing or aerodynamic shadowing mistakes
* Electrical, hydraulic, pneumatic, other systems with flows calculation via JSBSim, which means tens of milliseconds exactness, and wide specter of possible malfunctions on usage mistakes. More than 1Mb of xml code.
* Disturbed instrumentation with lags, which also calculated via JSBsim, and depended on Pitot tubes
* Pitot tubes with possibility of freezing and heaters which could burn out
* Breakable gears, blowing flaps, canopy
* Chain reactions of malfunctions caused by some minor mistakes of pilot
* Manually tuned radicompass working with NDB beacons
* "Asure" radioline commands directions to MP targets or runways
* Autopilot working from stop to stop, including takeoff, passing to beacon, MP target following, interception, landing
* Stabilization and antiskid automation
* Braking chute
* Droppable external tanks with moments and drags
* Radar working at MP targets, based on real Su-15 work movie and real data; as real one, can not see targets below model or behind mountain
* Infrared R-8P and halfactive radar R-8R missiles working at MP targets, based on real data
* Guidance heads of missiles calculated realtime, means it can lose target that making an antimissile maneuvers
* FDM of missiles calculated via JSBSim, means these could lose stability on turns. Instead of other FG missiles, these are calculated as standard JSBSim models, by data sets made by Datcom, plus own stability automation is calculated. Basically, exactness is just same as of plane model itself. Comparison with Yasim/JSBSim models quality matching is relevant here. 100Kb of xml code per missile.
* Basic version with missiles and some systems calculated by Nasal. A bit rough, still missiles works with real calculation of forces and alpha/beta, so maneuvering one slows realistically faster than one flying straight, and would not catch maneuverable target, while heavy bomber should not be an question - it's most realistic missiles at FG still. For old PCs, 7..10fps at Athlon 64X2 4000+, GeForce GTS 450, 2Gb Ram.
* Custom MPClash protocol, allowing missiles dogfight training trough MP, including missile launched by other player visibility, radar irradiation warner, lamps for own missiles catches and for catches of other pilot. At now "Su-15" model is sole one at FG having such abilities. Others can shoot in the air only, since they do not see missiles of each other, and not affected by it in any way, excluding MP messages spam; while protocol could be expanded easily with other missiles types, already existed ones inclusive. To change catch lamp to some breakage calculator is matter of day; so at now "Su-15" model is single one at FG which can shoot down model of other player really. A bit aggressive, still not one else deals with others in any way.
[[File:MPClash.png|thumb|MPClash protocol working example.]]
* Exact Russian/English PDF documentation with screenshots for any important action
* Some [[ALS_technical_notes|ALS]] candies - external and internal shadows, canopy glass reflection, red instrumentation light, reheat exhaust, etc.
* GetToFlyOnly license above all that, means You can fly model personally for free, but got to ask me for any other usage. Since some miscomprehendings with FG community. Lone work for free is possible, it's called "hobby". Common work without own authority is possible, it's often called just "work". Both simultaneously, plus without respect - not. And missiles of "Su" is aimed at people thinking other way. Let's see if these will work.

== Model performance ==
* Maximum speed: Mach 2.05
* Maximum speed without reheat: Mach 1.5
* Practical ceiling: 18 km
* Dynamic hop ceiling: 23 km
* Maximum flight duration: 3 hours
* Maximum flight duration with reheat: 30 min
* Takeoff speed: 400 km/h
* Landing speed with blowing flaps: 325 km/h
* Stall speed: 300 km/h
* Minimal runway length: 1,500 m
* Radar range: 40 km
* Radar selection range: 30 km
* Medium missiles working range: 10 km

== Model author ==
Victor Slavutinsky, vitosnet <at> mail <dot> ru.

== External links ==
* {{wikipedia|Su-15|Wikipedia}}
* [http://www.airwar.ru/enc/fighter/su15.html Airwar.ru]

{{Sukhoi}}

[[Category:Military aircraft]]

File:Su-15-Interior.png

2016-11-07T22:41:23Z

Vitos: Vitos uploaded a new version of File:Su-15-Interior.png

=={{int:filedesc}}==
{{Information
|description={{en|1=Interior of Su-15 model}}
|date=2016-08-30
|source={{own}}
|author=[[User:Vitos|Vitos]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

Sukhoi Su-15

2016-11-07T22:38:34Z

Vitos: /* Features */

{{:{{PAGENAME}}/info}}

'''Su-15''' - semi-automated Mach 2, 20 km interceptor with missiles armament.

== About ==

The Sukhoi Su-15 (NATO reporting name "'''Flagon'''") was the second semi-automated interceptor on the planet, the first being its predecessor, the Sukhoi Su-9, and for its time this was quite advanced. It worked in tandem with ground radar, receiving calculated direction data via a encoded radio link, but also had its own radar with a working distance of 30 km (16 nm), which was huge at time. It was first aircraft ever able to catch a target at both head-on and following courses, at a speed of Mach 2 at an altitude of approximately 20 km (66,000 ft.), and target speeds of Mach 3 at approximately 25 km (82,000 ft.). In fact, with all that equipment, it was first ever aircraft in which the pilot was more of an operator than pilot — the plane could intercept a target by itself in both ground-guided and radar-guided modes.

But its effectiveness was bought at a high price. Being a heavy plane with small wings, it has an extremely high landing speed of 350 km/h, similar to the Space Shuttle and {{wikipedia|Buran|noicon=1}}, both of which are spaceplanes(!). It was also unstable at those kind of speeds, while oversonic yaw maneuvering was limited by its side intakes, a first for Soviet aircraft. Fuel consumption was similar to a rocket, and enormously high by modern standards — it got through 8 tonnes of kerosene in a normal 15-minute, Mach 2 interception flight.

Regular pilot training - happily Su-15 was not used at real targets often - cost the same amount of money as making cosmonaut out of him and sending him at space; common 200 flight hours per year turned into monstrous 1000tonnes of fuel, while weight of whole R-7 rocket was 280tonnes only. At modern prices such training would cost 1million of, heh, money per year - really, not less, so expenses of usage was comparable with cost of plane itself for sure.

Interception of 2Mach target, including radar selection, friend-or-foe semiautomatic recognition, missile guidance head lock, so on, could occur at head-on course only, since other way Su could not reach it; so relative approaching speed was up to 4Mach, and all process had to be pressed in 30seconds, without second chance. 3Mach demanded even faster reaction - but it should be made without any mistake, since a target would be the bomber with thermonuclear bombs. In addition, return at 1 tonne of leftover fuel was a normal part of interception flights.

Summing all that, needed piloting class was high - so high that at most units of anti-aircraft warfare, which was armed with Su-15, cadet who flew it first time alone received a cake from colleagues; it was not tradition common with other units. Other prove - only pilots of Tu-128, flying even more heavy interceptors for hours, had greater incomes in whole air forces.

Even with such qualified pilots, area of plane usage was quite narrow. Not maneuverable, without place for regular gyro sight at cockpit, it has standard armament of two heavy missiles only - typical second generation interceptor, with sole target as heavy high altitude bomber; first series was completely useless against low-speed low-altitude targets. Some of limitations was overpassed at later modifications, but fact that Su-15 as whole was used for quarter of century, and, with modifications, was produced 1300 times, is mostly prove that there is nothing more constant than temporary than evidence of its versatility.

Fact is representative more that, instead of other former Soviet fighters as MiG-21, not one flew in private hands after retiring. It's just too hard, too demanding, to be common fun. Once it was case three Su crashed in a row, in just 15minutes, due to foggy conditions and guiding system absence at receiving port. All three pilots was high-rank - so to use it alone, without ground automatics, would be risky even at future times with its artificially advanced humans. Heh. At fact, pilots respected plane, some of them even liked it, but, seems to be, not one really loved it, way this was with some other types. Well, it's hard to love something that do at its own better than under Your control.

I made model of it mostly as part of personal investigation of Yury Gagarin life and death circumstances - as Alexey Leonov, friend of Gagarin and man who made first ever EVA, said that Su was involved in second. So exactness of model is as high as possible; with conditions in which documentation of it is not at public domain yet.

Also, it was test of ability to make mostly JSBSim realistic model, which could run standalone with all systems, each switch, by minimal fixes and changes; of course it was some additional social test of community, etc.

== Features ==
* Detailed 3D external model and virtual cockpit based on real photos
[[File:Su-15-3D-Quality.jpg|thumb|Example of "Su-15" 3D model quality.]]
* Exact textures with special Soviet fonts
* Sounds from real sources
* Common FDM generated by Datcom with fuselage form modeling
* Advanced FDM polished by [[Panair|Boeing Panair]] panel code program. Since tests are ongoing still, only nasal version is affected.
[[File:Su-15-Panair Front.png|thumb|Su-15 PanAir model]]
* Further polishing of FDM with [[XFLR5]]
* Each surface, gears, tanks, missiles inclusive, have its own forces and moments calculated
* Blowing flaps with realistic effect on pitch
* Braking chute
* Engines based on graphs from real MiG-21 documentation, since it has same one, with possibility of overheating and fire
* Extinguishing system, and ability to land at one engine
* Intakes calculated realtime, with engines cutoff at resurfacing or aerodynamic shadowing mistakes
* Electrical, hydraulic, pneumatic, other systems with flows calculation via JSBSim, which means tens of milliseconds exactness, and wide specter of possible malfunctions on usage mistakes. More than 1Mb of xml code.
* Disturbed instrumentation with lags, which also calculated via JSBsim, and depended on Pitot tubes
* Pitot tubes with possibility of freezing and heaters which could burn out
* Breakable gears, blowing flaps, canopy
* Chain reactions of malfunctions caused by some minor mistakes of pilot
* Manually tuned radicompass working with NDB beacons
* "Asure" radioline commands directions to MP targets or runways
* Autopilot working from stop to stop, including takeoff, passing to beacon, MP target following, interception, landing
* Stabilization and antiskid automation
* Braking chute
* Droppable external tanks with moments and drags
* Radar working at MP targets, based on real Su-15 work movie and real data; as real one, can not see targets below model or behind mountain
* Infrared R-8P and halfactive radar R-8R missiles working at MP targets, based on real data
* Guidance heads of missiles calculated realtime, means it can lose target that making an antimissile maneuvers
* FDM of missiles calculated via JSBSim, means these could lose stability on turns. Instead of other FG missiles, these are calculated as standard JSBSim models, by data sets made by Datcom, plus own stability automation is calculated. Basically, exactness is just same as of plane model itself. Comparison with Yasim/JSBSim models quality matching is relevant here. 100Kb of xml code per missile.
* Version with missiles and some systems calculated by Nasal. A bit rough, for example flight of missiles may not to look good somewhere, since errors at FG interpolation. Still these works with real calculation of forces and alpha/beta, so maneuvering missile slows realistically faster than one flying straight, and would not catch maneuverable target, while heavy bomber should not be an question - it's most realistic missiles at FG still. For old PCs, 7..10fps at Athlon 64X2 4000+, GeForce GTS 450, 2Gb Ram.
* Custom MPClash protocol, allowing missiles dogfight training trough MP, including missile launched by other player visibility, radar irradiation warner, lamps for own missiles catches and for catches of other pilot. At now "Su-15" model is sole one at FG having such abilities. Others can shoot in the air only, since they do not see missiles of each other, and not affected by it in any way, excluding MP messages spam; while protocol could be expanded easily with other missiles types, already existed ones inclusive. To change catch lamp to some breakage calculator is matter of day; so at now "Su-15" model is single one at FG which can shoot down model of other player really. A bit aggressive, still not one else deals with others in any way.
[[File:MPClash.png|thumb|MPClash protocol working example.]]
* Exact Russian/English PDF documentation with screenshots for any important action
* Some [[ALS_technical_notes|ALS]] candies - external and internal shadows, canopy glass reflection, red instrumentation light, reheat exhaust, etc.
* GetToFlyOnly license above all that, means You can fly model personally for free, but got to ask me for any other usage. Since some miscomprehendings with FG community. Lone work for free is possible, it's called "hobby". Common work without own authority is possible, it's often called just "work". Both simultaneously, plus without respect - not. And missiles of "Su" is aimed at people thinking other way. Let's see if these will work.

== Model performance ==
* Maximum speed: Mach 2.05
* Maximum speed without reheat: Mach 1.5
* Practical ceiling: 18 km
* Dynamic hop ceiling: 23 km
* Maximum flight duration: 3 hours
* Maximum flight duration with reheat: 30 min
* Takeoff speed: 400 km/h
* Landing speed with blowing flaps: 325 km/h
* Stall speed: 300 km/h
* Minimal runway length: 1,500 m
* Radar range: 40 km
* Radar selection range: 30 km
* Medium missiles working range: 10 km

== Model author ==
Victor Slavutinsky, vitosnet <at> mail <dot> ru.

== External links ==
* {{wikipedia|Su-15|Wikipedia}}
* [http://www.airwar.ru/enc/fighter/su15.html Airwar.ru]

{{Sukhoi}}

[[Category:Military aircraft]]

Sukhoi Su-15

2016-11-07T22:37:45Z

Vitos: /* Features */

{{:{{PAGENAME}}/info}}

'''Su-15''' - semi-automated Mach 2, 20 km interceptor with missiles armament.

== About ==

The Sukhoi Su-15 (NATO reporting name "'''Flagon'''") was the second semi-automated interceptor on the planet, the first being its predecessor, the Sukhoi Su-9, and for its time this was quite advanced. It worked in tandem with ground radar, receiving calculated direction data via a encoded radio link, but also had its own radar with a working distance of 30 km (16 nm), which was huge at time. It was first aircraft ever able to catch a target at both head-on and following courses, at a speed of Mach 2 at an altitude of approximately 20 km (66,000 ft.), and target speeds of Mach 3 at approximately 25 km (82,000 ft.). In fact, with all that equipment, it was first ever aircraft in which the pilot was more of an operator than pilot — the plane could intercept a target by itself in both ground-guided and radar-guided modes.

But its effectiveness was bought at a high price. Being a heavy plane with small wings, it has an extremely high landing speed of 350 km/h, similar to the Space Shuttle and {{wikipedia|Buran|noicon=1}}, both of which are spaceplanes(!). It was also unstable at those kind of speeds, while oversonic yaw maneuvering was limited by its side intakes, a first for Soviet aircraft. Fuel consumption was similar to a rocket, and enormously high by modern standards — it got through 8 tonnes of kerosene in a normal 15-minute, Mach 2 interception flight.

Regular pilot training - happily Su-15 was not used at real targets often - cost the same amount of money as making cosmonaut out of him and sending him at space; common 200 flight hours per year turned into monstrous 1000tonnes of fuel, while weight of whole R-7 rocket was 280tonnes only. At modern prices such training would cost 1million of, heh, money per year - really, not less, so expenses of usage was comparable with cost of plane itself for sure.

Interception of 2Mach target, including radar selection, friend-or-foe semiautomatic recognition, missile guidance head lock, so on, could occur at head-on course only, since other way Su could not reach it; so relative approaching speed was up to 4Mach, and all process had to be pressed in 30seconds, without second chance. 3Mach demanded even faster reaction - but it should be made without any mistake, since a target would be the bomber with thermonuclear bombs. In addition, return at 1 tonne of leftover fuel was a normal part of interception flights.

Summing all that, needed piloting class was high - so high that at most units of anti-aircraft warfare, which was armed with Su-15, cadet who flew it first time alone received a cake from colleagues; it was not tradition common with other units. Other prove - only pilots of Tu-128, flying even more heavy interceptors for hours, had greater incomes in whole air forces.

Even with such qualified pilots, area of plane usage was quite narrow. Not maneuverable, without place for regular gyro sight at cockpit, it has standard armament of two heavy missiles only - typical second generation interceptor, with sole target as heavy high altitude bomber; first series was completely useless against low-speed low-altitude targets. Some of limitations was overpassed at later modifications, but fact that Su-15 as whole was used for quarter of century, and, with modifications, was produced 1300 times, is mostly prove that there is nothing more constant than temporary than evidence of its versatility.

Fact is representative more that, instead of other former Soviet fighters as MiG-21, not one flew in private hands after retiring. It's just too hard, too demanding, to be common fun. Once it was case three Su crashed in a row, in just 15minutes, due to foggy conditions and guiding system absence at receiving port. All three pilots was high-rank - so to use it alone, without ground automatics, would be risky even at future times with its artificially advanced humans. Heh. At fact, pilots respected plane, some of them even liked it, but, seems to be, not one really loved it, way this was with some other types. Well, it's hard to love something that do at its own better than under Your control.

I made model of it mostly as part of personal investigation of Yury Gagarin life and death circumstances - as Alexey Leonov, friend of Gagarin and man who made first ever EVA, said that Su was involved in second. So exactness of model is as high as possible; with conditions in which documentation of it is not at public domain yet.

Also, it was test of ability to make mostly JSBSim realistic model, which could run standalone with all systems, each switch, by minimal fixes and changes; of course it was some additional social test of community, etc.

== Features ==
* Detailed 3D external model and virtual cockpit based on real photos
[[File:Su-15-3D-Quality.jpg|thumb|Example of "Su-15" 3D model quality.]]
* Exact textures with special Soviet fonts
* Sounds from real sources
* Common FDM generated by Datcom with fuselage form modeling
* Advanced FDM polished by [[Panair|Boeing Panair]] panel code program. Since tests are ongoing still, only nasal version is affected.
[[File:Su-15-Panair Front.png|thumb|Su-15 PanAir model]]
* Further polishing of FDM with [[XFLR5]]
* Each surface, gears, tanks, missiles inclusive, have its own forces and moments calculated
* Blowing flaps with realistic effect on pitch
* Braking chute
* Engines based on graphs from real MiG-21 documentation, since it has same one, with possibility of overheating and fire
* Extinguishing system, and ability to land at one engine
* Intakes calculated realtime, with engines cutoff at resurfacing or aerodynamic shadowing mistakes
* Electrical, hydraulic, pneumatic, other systems with flows calculation via JSBSim, which means tens of milliseconds exactness, and wide specter of possible malfunctions on usage mistakes. More than 1Mb of xml code.
* Disturbed instrumentation with lags, which also calculated via JSBsim, and depended on Pitot tubes
* Pitot tubes with possibility of freezing and heaters which could burn out
* Breakable gears, blowing flaps, canopy
* Chain reactions of malfunctions caused by some minor mistakes of pilot
* Manually tuned radicompass working with NDB beacons
* "Asure" radioline commands directions to MP targets or runways
* Autopilot working from stop to stop, including takeoff, passing to beacon, MP target following, interception, landing
* Stabilization and antiskid automation
* Braking chute
* Droppable external tanks with moments and drags
* Radar working at MP targets, based on real Su-15 work movie and real data; as real one, can not see targets below model or behind mountain
* Infrared R-8P and halfactive radar R-8R missiles working at MP targets, based on real data
* Guidance heads of missiles calculated realtime, means it can lose target that making an antimissile maneuvers
* FDM of missiles calculated via JSBSim, means these could lose stability on turns. Instead of other FG missiles, these are calculated as standard JSBSim models, by data sets made by Datcom, plus own stability automation is calculated. Basically, exactness is just same as of plane model itself. Comparison with Yasim/JSBSim models quality matching is relevant here. 100Kb of xml code per missile.
* Version with missiles and some systems calculated by Nasal. A bit rough, for example flight of missiles may not to look good somewhere, since errors at FG interpolation. Still these works with real calculation of forces and alpha/beta, so maneuvering missile slows realistically faster than one flying straight, and would not catch maneuverable target, while heavy bomber should not be an question - it's most realistic missiles at FG still. For old PCs, 7..10fps at Athlon 64X2 4000+, GeForce GTS 450, 2Gb Ram.
* Custom MPClash protocol, allowing missiles dogfight training trough MP, including missile launched by other player visibility, radar irradiation warner, lamps for own missiles catches and for catches of other pilot. At now "Su-15" model is sole one at FG having such abilities. Others can shoot in the air only, since they do not see missiles of each other, and not affected by it in any way, excluding MP messages spam; while protocol could be expanded easily with other missiles types, already existed ones inclusive. To change catch lamp to some breakage calculator is matter of day; so at now "Su-15" model is single one at FG which can shoot down model of other player really. A bit aggressive, still not one else deals with others in any way.
[[File:MPClash.png|thumb|MPClash protocol working example.]]
* Exact Russian/English PDF documentation with screenshots for any important action
* Some [[ALS_technical_notes|ALS]] candies - external and internal shadows, canopy glass reflection, reheat exhaust, etc.
* GetToFlyOnly license above all that, means You can fly model personally for free, but got to ask me for any other usage. Since some miscomprehendings with FG community. Lone work for free is possible, it's called "hobby". Common work without own authority is possible, it's often called just "work". Both simultaneously, plus without respect - not. And missiles of "Su" is aimed at people thinking other way. Let's see if these will work.

== Model performance ==
* Maximum speed: Mach 2.05
* Maximum speed without reheat: Mach 1.5
* Practical ceiling: 18 km
* Dynamic hop ceiling: 23 km
* Maximum flight duration: 3 hours
* Maximum flight duration with reheat: 30 min
* Takeoff speed: 400 km/h
* Landing speed with blowing flaps: 325 km/h
* Stall speed: 300 km/h
* Minimal runway length: 1,500 m
* Radar range: 40 km
* Radar selection range: 30 km
* Medium missiles working range: 10 km

== Model author ==
Victor Slavutinsky, vitosnet <at> mail <dot> ru.

== External links ==
* {{wikipedia|Su-15|Wikipedia}}
* [http://www.airwar.ru/enc/fighter/su15.html Airwar.ru]

{{Sukhoi}}

[[Category:Military aircraft]]

Sukhoi Su-15/info

2016-11-07T22:34:17Z

Vitos:

<includeonly>{{infobox aircraft
| name = {{LangSwitch
| en = Sukhoi Su-15
| ru = Су-15
}}
| aircraft = Su-15
| image = Su-15-Exterior.png
| image2 = Su-15-Interior.png
| image3 = Su-15-Panel.png
| type = Fighter aircraft/Interceptor aircraft/Military aircraft/Supersonic aircraft/Jet fighter
| config = Delta-wing aircraft
| propulsion = Twinjet
| manufacturer = Sukhoi
| author1 = {{usr|Vitos|Victor Slavutinsky}}
| author2 =
| author3 =
| author4 =
| author5 =
| author6 =
| author7 =
| author8 =
| devel-team =
| fdm = JSBsim
| fgname = Su-15
| status-fdm =
| status-systems =
| status-cockpit =
| status-model =
| ready =
| forumtid = 25993
| navbar = 1
| license = GetToFlyOnly
| download = http://www.autopsi.info/Su-15/Su-15.zip
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[Sukhoi Su-15]].
[[Category:Aircraft infobox documentation]]
</noinclude>

Howto:Make full spherical panorama

2016-11-07T21:53:01Z

Vitos: /* Taking the required screenshots */

{{Note|Also see [[FlightGear WorldTerrain SkyBox Server]] for a FlightGear-based approach to procedurally create cubemap textures using FlightGear itself.}}
In this [[:Category:Howto|howto]] I will explain how to make full spherical panorama in [[FlightGear]]. To see many examples of spherical panorama, take a look at this forum thread: http://forum.flightgear.org/viewtopic.php?f=19&t=7713. The semi-automated process is useful for everyone that wants to contribute to the flightgear wiki by adding one of this panorama to each aircraft's page in order to display the cockpit. Here is an example of what can be achieved:

[[File:C172p-cockpit-pano.jpg|480px|thumb|center|A full spherical panorama of the 3d cessna c172p cockpit]]

=== The tools ===
In order to take panorama in flightgear you need:
* of course [[Flightgear]]
* a panorama stitching tool. I suggest to use [http://hugin.sourceforge.net Hugin]: it's free and very powerful.

=== The automatic process ===
To make the process easier I've created a [[Nasal scripting language|nasal]] script that capture automagically the required screenshots. This script can be binded to a keyboard key. Also I've created a standard Hugin file to assemble this screenshots into a full spherical panorama.
To get rid of the popup window telling you that the screenshots was saved, you can follow this guidance: http://forum.flightgear.org/viewtopic.php?f=17&t=13810#p140388

==== Taking the required screenshots ====
The easier way is to bind the following nasal script to a keyboard key (The {{key press|F3}} key that is used by default to take screenshots). To do this, open the file keyboard.xml that you can find in the fgdata folder with a text editor and look for the following section:

<syntaxhighlight lang="xml">
<key n="259">
<name>F3</name>
<desc>Capture screen</desc>
<binding>
<command>nasal</command>
<script>
var success = fgcommand("screen-capture");
var path = getprop("/sim/paths/screenshot-last");
if (success)
gui.popupTip("Screenshot written to '" ~ path ~ "'");
else
gui.popupTip("Error writing screenshot '" ~ path ~ "'");
</script>
</binding>
<mod-shift>
<desc>Load panel</desc>
<binding>
<command>panel-load</command>
</binding>
</mod-shift>
</key>
</syntaxhighlight>

Now substitute the [[Nasal scripting language|nasal]] code between the <script> tags with this:

<syntaxhighlight lang="nasal">
var tick_time=3;

menubarvalue=getprop("/sim/menubar/visibility");
znearvalue=("sim/rendering/camera-group/znear");
fovvalue=getprop("/sim/current-view/field-of-view");
freezemvalue=getprop("/sim/freeze/master");
freezecvalue=getprop("/sim/freeze/clock");
headingvalue=getprop("/sim/current-view/heading-offset-deg");
pitchvalue=getprop("/sim/current-view/pitch-offset-deg");

setprop("/sim/menubar/visibility", 'false');
setprop("/sim/rendering/camera-group/znear",0.03);
setprop("/sim/current-view/field-of-view", 120);
setprop("/sim/freeze/master",'true');
setprop("/sim/freeze/clock",'true');

var rotatescreen = func(heading_deg, pitch_deg)
{
setprop("/sim/current-view/goal-heading-offset-deg", heading_deg);
setprop("/sim/current-view/heading-offset-deg", heading_deg);
setprop("/sim/current-view/goal-pitch-offset-deg", pitch_deg);
setprop("/sim/current-view/pitch-offset-deg", pitch_deg);
}

var takescreen = func(heading_deg, pitch_deg)
{
print ("taking screen with heading= ", heading_deg, " and pitch= ", pitch_deg);
var success = fgcommand("screen-capture");
if (success)
{
print ("screen taken with heading= ", heading_deg, " and pitch= ", pitch_deg);
}
else
{
print("screen not taken");
}
}

var scr_ticks = func()
{
i=getprop("/sim/screenshots/i");
j=getprop("/sim/screenshots/j");
k=getprop("/sim/screenshots/k");
if (i==0)
{
pitch_deg=-45;
}
else
{
pitch_deg=45;
}
heading_deg=j*(-90);
if (k==0)
{
rotatescreen(heading_deg, pitch_deg);
setprop("/sim/screenshots/k", 1);
settimer(scr_ticks, tick_time, tick_time);
}
else if (k==1)
{
print("testing");
takescreen(heading_deg, pitch_deg);
setprop("/sim/screenshots/k", 0);
if (j!=3)
{
j=j+1;
setprop("/sim/screenshots/j", j);
settimer(scr_ticks, tick_time, tick_time);
}
else
{
if (i==0)
{
i=i+1;
setprop("/sim/screenshots/i", i);
j=0;
setprop("/sim/screenshots/j", j);
settimer(scr_ticks, tick_time, tick_time);
}
else
{
setprop("/sim/screenshots/k", 2);
settimer(scr_ticks, tick_time, tick_time);
}
}
}
else
{
setprop("/sim/menubar/visibility", menubarvalue);
setprop("/sim/current-view/field-of-view", fovvalue);
setprop("/sim/current-view/heading-offset-deg", headingvalue);
setprop("/sim/current-view/pitch-offset-deg", pitchvalue);
setprop("/sim/freeze/master", freezemvalue);
setprop("/sim/freeze/clock", freezecvalue);
}
}

setprop("/sim/screenshots/i", 0);
setprop("/sim/screenshots/j", 0);
setprop("/sim/screenshots/k", 0);
scr_ticks();
</syntaxhighlight>

Also, You would want to comment out next strings at gui.nas file

<syntaxhighlight lang="nasal">
if (success) {
popupTip("Screenshot written to '" ~ path ~ "'", 3);
} else {
popupTip("Error writing screenshot '" ~ path ~ "'", 600, button);
}
</syntaxhighlight>

by #, to stop that message mess with view.

Now you are ready to start Flightgear but in order to use efficiently this script and the provided Hugin file you need to set the video format to 4/3 (800x600, 1024x768, 1200x900, 1600x1200...). When in the game press the {{key press|F3}} key and wait. You will see the camera changing heading and pitch automatically. When the required screenshots are taken, the original view is restored. Now exit flightgear, look for saved screenshots in png format and follow the next step.

==== Stitching the panorama with Hugin ====
Copy all the eight screenshots in a new folder named as you want. Open this folder and create in it a new text file called panorama.pto. Open this file and copy the following lines in it:

# hugin project file
#hugin_ptoversion 2
p f2 w3000 h1500 v360 E0 R0 n"TIFF_m c:LZW r:CROP"
m g1 i0 f0 m2 p0.00784314

# image lines
#-hugin cropFactor=1
i w800 h600 f0 v120 Ra0 Rb0 Rc0 Rd0 Re0 Eev0 Er1 Eb1 r0 p-45 y0 TrX0 TrY0 TrZ0 j0 a0 b0 c0 d0 e0 g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 Vm5 u10 n"fgfs-screen-001.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y90 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-002.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y180 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-003.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y270 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-004.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y0 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-005.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y90 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-006.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y180 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-007.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y270 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-008.png"

# specify variables that should be optimized
v r1
v p1
v y1
v r2
v p2
v y2
v r3
v p3
v y3
v r4
v p4
v y4
v r5
v p5
v y5
v r6
v p6
v y6
v r7
v p7
v y7
v

# control points

#hugin_optimizeReferenceImage 0
#hugin_blender enblend
#hugin_remapper nona
#hugin_enblendOptions
#hugin_enfuseOptions
#hugin_hdrmergeOptions -m avg -c
#hugin_outputLDRBlended true
#hugin_outputLDRLayers false
#hugin_outputLDRExposureRemapped false
#hugin_outputLDRExposureLayers false
#hugin_outputLDRExposureBlended false
#hugin_outputLDRExposureLayersFused false
#hugin_outputHDRBlended false
#hugin_outputHDRLayers false
#hugin_outputHDRStacks false
#hugin_outputLayersCompression LZW
#hugin_outputImageType jpg
#hugin_outputImageTypeCompression LZW
#hugin_outputJPEGQuality 100
#hugin_outputImageTypeHDR exr
#hugin_outputImageTypeHDRCompression LZW

Save the file and open it with [http://hugin.sourceforge.net Hugin]. In Hugin go to the "stitching" tab and press the "Stitch Now" button. You will be asked where to save the resulting image. Select a path and press ok. When Hugin terminates the stitching process you are done. Browse to where you told Hugin to save the panorama, and take a look at the image to check if something went wrong.

[[Category:Howto|Make full spherical panorama]]

XFLR5

2016-10-24T09:45:59Z

Vitos: /* Step eight: Controlled surfaces */

<br />
== Polishing FDM with XFLR5 ==

My next attempt to make aerodynamics of [[Su-15]] model realistic more was with [http://www.xflr5.com/xflr5.htm XFLR5]. That Open Source program is included at most of Linux distributions, to install it is not so big deal, and some of developers used it already. Again, let's go calculation process step by step to figure out what it can do.

== First step: Defining profiles ==

Most easy way is to define profiles of surefaces manually, at "File/Direct Foil Design".

[[File:XFLR5 Profiles.jpg|thumb|XFLR5 wing profiles edit window]]

First clone it from default one, then name it, then adjust common thickness by "Scale Camber and Thickness" dropdown menu. Then look at points of profile at "Edit Foil Coordinates". Don't edit these manually, but compare thickness of profile at 0.1 of chord at XFLR5 and Blender, or where You have it, and then use "Set L.E. Radius" to adjust thickness of beginning of wing.

At now program does not allow to import profile points, it can export it only. Anyway, by experience, to achieve needed result is question of minutes. Note that if You mean some flaps or rudder calculations then You need to create profile with turned flap also here, and then to make additional one, with false flap, beginning at same place, but rotated at zero angle - that one will be used for better exactness of calculations later.

At my Fedora with Cinnamon, latest XFLR5 sometimes stops to react at mouse with additional popup windows. So, maybe, knowing of some Tab/Shift-Tab and Space/Esc keyboard magic would be useful to You.

== Second step: Defining surfaces ==

Save project and switch to "Wing and Plane Design". You would want to set metrics at "Options/Units" to feets and lbs prior, as JSBSim uses these - I did not do that, since my initial model was at meters, but preferred to recalculate output later at Libre Office Calc.

So, use "Plane/Define New Plane". Here You go to "Main Wing/Define".

[[File:XFLR5 WIng Profile.jpg|thumb|XFLR5 Su-15 wing model]]
[[File:XFLR5 Elevator.jpg|thumb|XFLR5 Su-15 model solid elevator variant]]

Look at presented screen to figure out what to do. You may notice next things, actually taken ideologically from program manual:

* Wing starts at zero point.
* It has six parts, two for root with false flap, two for aileron, with flap, and two for tip, with false flap. Second ones at all cases have 1 panel at Y - that way program comprehends structure and can calculate effects of flap-nonflap surfaces joint.
* Each part is defined by things as chord at X, distance from zero axle at Y, offset and so.
* Number of panels is not so big, 8x8 at greater case - by experience I do know that greater takes much more time but don't affect results much.

Save anything and then set wing offsets at main edit window.

Then You do define elevator.

Note that same distributions are set at that screen and previous one, length and number of panels at Y axis are just same for root part of thing and for elevator. That is highly recommended by manual; if length of elevator at Your model is not that same as distance to aileron of wing at Y, and with other similar cases, divide both wing and elevator accordingly, to make it fit panel to panel at Y axis.

Save result, set offsets, then set tail at fin edit window.

== Step third: Defining body ==

[[File:XFLR5 Body.jpg|thumb|XFLR5 body edit window]]

You can use XFLR5 as primitive 3D editor and define body spline by spline. As I had other one already, I preferred other way, and made a Blender exporter plugin. So, make body as half of cylinder at Blender, with 0..positive y's, divided up to ~30 cuts at Y and Z, starting with cone and ending with cone, export it from Blender and import it with "Other/Import Body Definition from text file" at body edition window. Quite easy.

== Step fourth: Defining plane inertia ==

[[File:XFLR5 Inertia.jpg|thumb|XFLR5 inertia edit window]]

Just a bit tricky, and You can omit that step, defining weight and Center of Gravity position at analysis window directly instead - if You do know it. I did, anyway, that option was tested.

I knew more or less exact weights of wing, tail, elevator and empty body from documentation, and set these at "Plane Inertia" window. Then I set additional weights to body - two engines at its positions, as I did knew exact weight of engine also.

And then, since I knew point where CG got to be, I took one tonne from weight of body and defined additional mass there, then shifted it to nose until CG went to needed position - seems to be that Su have really heavy radar there. At Your case You could do same, knowing that CG could not be after main gears, and should be at ~third of median chord of wing.

That's it. If You need some Ixx or so then You can take it from here and, if Your XFLR5 model was made at ft/lbs units, put these values directly at needed place of JSBSim FDM xml model file; at case it was made in meters and kilograms, multiply it with 0.453592 prior.

Also, I would add, better to make such calculations with plane defined a bit other way, with surfaces starts not at zero point inside fuselage, but a bit off it, as at one of examples presented with pack below. Then inertia moments are correct more.

== Step fifth: Calculation ==

OK, everything is set.

[[File:XFLR5 Model Aileron Rudder.jpg|thumb|XFLR5 Su-15 model with ailerons and rudder shifted]]

Open "Analysis/Define an Analysis", choose "Type 1 (Fixed Speed)", with speed of 100m/s at first panel, "Ring Vortex (VLM2)" without other options at second - again, some Ctrl-Tab magic could be useful. Do not use "Viscous" and "Tilt. Geom" options - as I can remember, one of these produces wrong values, while other is error making.

Set name for analysis, press OK, then select it above main window. At side panel set alpha angles, from -45deg to 45 for example, with step of 5deg, and press "Analyze" button. At my old PC it calculated such case for some minutes - two maybe, not more than five for sure.

== Step sixth: Data mining ==

Go to "Polars/Current Polar/Export" and export results to text file. Open it at gedit and change multiply spaces to one by Ctrl-H, " " to " ". Then copy text and paste it to Calc.

[[File:XFLR5 Cl.jpg|thumb|XFLR5 and Datcom lift coefficient comparison]]
[[File:XFLR5 Cd.jpg|thumb|XFLR5 and Datcom drag coefficient comparison]]
[[File:XFLR5 Cm.jpg|thumb|XFLR5 and Datcom pitch moment coefficient comparison]]

First of all, if You calculated at m/kg units, multiply lift coefficient, CL, to
0.453592/(0.3048^2)
to convert it to feet/lbs; same with drag, CD. As of pitch, CM, since it multiplies at chord in calculations, and goes with inversion, conversion coefficient is
-0.453592/0.3048

Then look at presented graphs. Since it was said at manual that effects of both wing going trough body and wing starting a bit offside it are unknown, I made two models - one with wing going trough, and one with wing starting offside, then compared results of these two with Datcom results.

Seems to be that lift coefficient is better with wing going trough at smaller absolute alphas values; angles near to critical angle of attack is better with wing starting offside. With negative critical angle it's some median between two variants. Resulting integral CL, combining two initial variants that way, is quite near to Datcom results.

For both CD and CM, drag and moment, variant without holes is better. Drag at zero alpha is too small anyway, set it to half of CD at 5deg manually.

== Step seventh: Higher Machs ==

[[File:Datcom Cd Mach Correction.jpg|thumb|Datcom made drag coefficient due to Mach number correction]]

Unfortunately, current version of XFLR5 seems to not care about speed at all. It produces quite same results at VLM2 method for 100m/s and 200m/s. Panel method, which You could set at "Define Analysis (Advance Users)" - don't forget to switch default "Viscous" option off, as it makes errors instead of values - seems to produce a bit different results, but, again, these are not changing with velocity.

So I made next rough approximation, taken from Datcom data analysis: up to 1Mach CL is more or less same, then it starts to drop, and goes to half of initial values at 2.5Mach. Same with CM. As of drag, it drops to 0.9 to 0.9Mach, jumps to 1.5 at 1.1Mach, and drops to 1 to 2.5Mach.

It's quite rough; anyway, just to add additional tables to functions of coefficients, as at this example, and it would make difference with Datcom model not so notable.

<nowiki><table></nowiki>
<independentVar lookup="row">velocities/mach</independentVar>
<tableData>
0.3000 1.0000
0.4000 1.0112
0.5000 1.0112
0.9000 0.9888
1.1000 0.9775
1.5000 0.8315
2.0000 0.6404
2.5000 0.5281
</tableData>
<nowiki></table></nowiki>

== Step eight: Controlled surfaces ==

[[File:XFLR5 Standalone Elevator.jpg|thumb|XFLR5 Su-15 cut rotated elevator variant]]
[[File:XFLR5 Elevator Cl to Cm.jpg|thumb|XFLR5 elevator moment coefficient converted from elevator lift coefficient]]

Again, it's a bit tricky, since method seems to be not so accurate at moments. At first, You need to calculate change of lift coefficient due to surface shift - of aileron, or, as at example, of fully rotated elevator.

I set internal offsets of it to put axle at zero, then external to make it stay at correct position, then just set its "Tilt Angle" to needed values to rotate it. Secondly, You need to multiply result at
distance_from_axle_to_center_of_gravity/wing_chord
or some span if that was set as multiplier of that coefficient at xml file. At least on resulted graphs difference at CM caused by elevator shift was lower than CM itself, while CM calculated out of CL was greater at needed angles, and model with that variant was controllable, while with pure CM changes - not.

== Step nine: Experiments ==

As I saw at web, some people do not import some body into XFLR5, but do define it as thick profile at core part of wing. Seems to be that approach produces more or less correct results too. You may try it, while I prefer to make conclusions instead.

== Resume ==

Easy and fast tool for beginners. If You made Your first JSBSim model, especially subsonic one, and do want to step further from initial [[Aeromatic]] made coefficients, that's what You need exactly - it would give You needed results in day or two.

But, making better picture, it calculates more, say, scientific results than Datcom, and some additional steps are needed to make output of it more or less exact with subsonics; at oversonics I went 2.5Mach without reheat at resulted "Su-15" model. Though it was not made for this at all, and would evolve, but at now I would recommend some other approaches to mature developers.

== External links ==
[http://www.xflr5.com/xflr5.htm XFLR5]

[https://sourceforge.net/projects/xflr5/files/Guidelines.pdf/download XFLR5 manual]

[http://autopsi.info/Su-15/Su-15-XFLR5-Tests.zip Su-15 XFLR5 Pack], including Blender export script, .ac, .txt, and .xfl examples

== Author ==

Victor Slavutinsky, vitosnet at mail dot ru

[[Category:Aerodynamic Tools]]

XFLR5

2016-10-24T09:42:05Z

Vitos: /* Step sixth: Data mining */

<br />
== Polishing FDM with XFLR5 ==

My next attempt to make aerodynamics of [[Su-15]] model realistic more was with [http://www.xflr5.com/xflr5.htm XFLR5]. That Open Source program is included at most of Linux distributions, to install it is not so big deal, and some of developers used it already. Again, let's go calculation process step by step to figure out what it can do.

== First step: Defining profiles ==

Most easy way is to define profiles of surefaces manually, at "File/Direct Foil Design".

[[File:XFLR5 Profiles.jpg|thumb|XFLR5 wing profiles edit window]]

First clone it from default one, then name it, then adjust common thickness by "Scale Camber and Thickness" dropdown menu. Then look at points of profile at "Edit Foil Coordinates". Don't edit these manually, but compare thickness of profile at 0.1 of chord at XFLR5 and Blender, or where You have it, and then use "Set L.E. Radius" to adjust thickness of beginning of wing.

At now program does not allow to import profile points, it can export it only. Anyway, by experience, to achieve needed result is question of minutes. Note that if You mean some flaps or rudder calculations then You need to create profile with turned flap also here, and then to make additional one, with false flap, beginning at same place, but rotated at zero angle - that one will be used for better exactness of calculations later.

At my Fedora with Cinnamon, latest XFLR5 sometimes stops to react at mouse with additional popup windows. So, maybe, knowing of some Tab/Shift-Tab and Space/Esc keyboard magic would be useful to You.

== Second step: Defining surfaces ==

Save project and switch to "Wing and Plane Design". You would want to set metrics at "Options/Units" to feets and lbs prior, as JSBSim uses these - I did not do that, since my initial model was at meters, but preferred to recalculate output later at Libre Office Calc.

So, use "Plane/Define New Plane". Here You go to "Main Wing/Define".

[[File:XFLR5 WIng Profile.jpg|thumb|XFLR5 Su-15 wing model]]
[[File:XFLR5 Elevator.jpg|thumb|XFLR5 Su-15 model solid elevator variant]]

Look at presented screen to figure out what to do. You may notice next things, actually taken ideologically from program manual:

* Wing starts at zero point.
* It has six parts, two for root with false flap, two for aileron, with flap, and two for tip, with false flap. Second ones at all cases have 1 panel at Y - that way program comprehends structure and can calculate effects of flap-nonflap surfaces joint.
* Each part is defined by things as chord at X, distance from zero axle at Y, offset and so.
* Number of panels is not so big, 8x8 at greater case - by experience I do know that greater takes much more time but don't affect results much.

Save anything and then set wing offsets at main edit window.

Then You do define elevator.

Note that same distributions are set at that screen and previous one, length and number of panels at Y axis are just same for root part of thing and for elevator. That is highly recommended by manual; if length of elevator at Your model is not that same as distance to aileron of wing at Y, and with other similar cases, divide both wing and elevator accordingly, to make it fit panel to panel at Y axis.

Save result, set offsets, then set tail at fin edit window.

== Step third: Defining body ==

[[File:XFLR5 Body.jpg|thumb|XFLR5 body edit window]]

You can use XFLR5 as primitive 3D editor and define body spline by spline. As I had other one already, I preferred other way, and made a Blender exporter plugin. So, make body as half of cylinder at Blender, with 0..positive y's, divided up to ~30 cuts at Y and Z, starting with cone and ending with cone, export it from Blender and import it with "Other/Import Body Definition from text file" at body edition window. Quite easy.

== Step fourth: Defining plane inertia ==

[[File:XFLR5 Inertia.jpg|thumb|XFLR5 inertia edit window]]

Just a bit tricky, and You can omit that step, defining weight and Center of Gravity position at analysis window directly instead - if You do know it. I did, anyway, that option was tested.

I knew more or less exact weights of wing, tail, elevator and empty body from documentation, and set these at "Plane Inertia" window. Then I set additional weights to body - two engines at its positions, as I did knew exact weight of engine also.

And then, since I knew point where CG got to be, I took one tonne from weight of body and defined additional mass there, then shifted it to nose until CG went to needed position - seems to be that Su have really heavy radar there. At Your case You could do same, knowing that CG could not be after main gears, and should be at ~third of median chord of wing.

That's it. If You need some Ixx or so then You can take it from here and, if Your XFLR5 model was made at ft/lbs units, put these values directly at needed place of JSBSim FDM xml model file; at case it was made in meters and kilograms, multiply it with 0.453592 prior.

Also, I would add, better to make such calculations with plane defined a bit other way, with surfaces starts not at zero point inside fuselage, but a bit off it, as at one of examples presented with pack below. Then inertia moments are correct more.

== Step fifth: Calculation ==

OK, everything is set.

[[File:XFLR5 Model Aileron Rudder.jpg|thumb|XFLR5 Su-15 model with ailerons and rudder shifted]]

Open "Analysis/Define an Analysis", choose "Type 1 (Fixed Speed)", with speed of 100m/s at first panel, "Ring Vortex (VLM2)" without other options at second - again, some Ctrl-Tab magic could be useful. Do not use "Viscous" and "Tilt. Geom" options - as I can remember, one of these produces wrong values, while other is error making.

Set name for analysis, press OK, then select it above main window. At side panel set alpha angles, from -45deg to 45 for example, with step of 5deg, and press "Analyze" button. At my old PC it calculated such case for some minutes - two maybe, not more than five for sure.

== Step sixth: Data mining ==

Go to "Polars/Current Polar/Export" and export results to text file. Open it at gedit and change multiply spaces to one by Ctrl-H, " " to " ". Then copy text and paste it to Calc.

[[File:XFLR5 Cl.jpg|thumb|XFLR5 and Datcom lift coefficient comparison]]
[[File:XFLR5 Cd.jpg|thumb|XFLR5 and Datcom drag coefficient comparison]]
[[File:XFLR5 Cm.jpg|thumb|XFLR5 and Datcom pitch moment coefficient comparison]]

First of all, if You calculated at m/kg units, multiply lift coefficient, CL, to
0.453592/(0.3048^2)
to convert it to feet/lbs; same with drag, CD. As of pitch, CM, since it multiplies at chord in calculations, and goes with inversion, conversion coefficient is
-0.453592/0.3048

Then look at presented graphs. Since it was said at manual that effects of both wing going trough body and wing starting a bit offside it are unknown, I made two models - one with wing going trough, and one with wing starting offside, then compared results of these two with Datcom results.

Seems to be that lift coefficient is better with wing going trough at smaller absolute alphas values; angles near to critical angle of attack is better with wing starting offside. With negative critical angle it's some median between two variants. Resulting integral CL, combining two initial variants that way, is quite near to Datcom results.

For both CD and CM, drag and moment, variant without holes is better. Drag at zero alpha is too small anyway, set it to half of CD at 5deg manually.

== Step seventh: Higher Machs ==

[[File:Datcom Cd Mach Correction.jpg|thumb|Datcom made drag coefficient due to Mach number correction]]

Unfortunately, current version of XFLR5 seems to not care about speed at all. It produces quite same results at VLM2 method for 100m/s and 200m/s. Panel method, which You could set at "Define Analysis (Advance Users)" - don't forget to switch default "Viscous" option off, as it makes errors instead of values - seems to produce a bit different results, but, again, these are not changing with velocity.

So I made next rough approximation, taken from Datcom data analysis: up to 1Mach CL is more or less same, then it starts to drop, and goes to half of initial values at 2.5Mach. Same with CM. As of drag, it drops to 0.9 to 0.9Mach, jumps to 1.5 at 1.1Mach, and drops to 1 to 2.5Mach.

It's quite rough; anyway, just to add additional tables to functions of coefficients, as at this example, and it would make difference with Datcom model not so notable.

<nowiki><table></nowiki>
<independentVar lookup="row">velocities/mach</independentVar>
<tableData>
0.3000 1.0000
0.4000 1.0112
0.5000 1.0112
0.9000 0.9888
1.1000 0.9775
1.5000 0.8315
2.0000 0.6404
2.5000 0.5281
</tableData>
<nowiki></table></nowiki>

== Step eight: Controlled surfaces ==

[[File:XFLR5 Standalone Elevator.jpg|thumb|XFLR5 Su-15 cut rotated elevator variant]]
[[File:XFLR5 Elevator Cl to Cm.jpg|thumb|XFLR5 elevator moment coefficient converted from elevator lift coefficient]]

Again, it's a bit tricky, since method seems to be not so accurate at moments. At first, You need to calculate change of lift coefficient due to surface shift - of aileron, or, as at example, of fully rotated elevator.

I set internal offsets of it to put axle at zero, then external to make it stay at correct position, then just set its "Tilt Angle" to needed values to rotate it. Secondly, You need to multiply result at distance_from_axle_to_center_of_mass/wing_chord, or some span if that was set as multiplier of that coefficient at xml file. At least on resulted graphs difference at CM caused by elevator shift was lower than CM itself, while CM calculated of CL was greater at needed angles, and model with that variant is controllable, while with pure CM - not.

== Step nine: Experiments ==

As I saw at web, some people do not import some body into XFLR5, but do define it as thick profile at core part of wing. Seems to be that approach produces more or less correct results too. You may try it, while I prefer to make conclusions instead.

== Resume ==

Easy and fast tool for beginners. If You made Your first JSBSim model, especially subsonic one, and do want to step further from initial [[Aeromatic]] made coefficients, that's what You need exactly - it would give You needed results in day or two.

But, making better picture, it calculates more, say, scientific results than Datcom, and some additional steps are needed to make output of it more or less exact with subsonics; at oversonics I went 2.5Mach without reheat at resulted "Su-15" model. Though it was not made for this at all, and would evolve, but at now I would recommend some other approaches to mature developers.

== External links ==
[http://www.xflr5.com/xflr5.htm XFLR5]

[https://sourceforge.net/projects/xflr5/files/Guidelines.pdf/download XFLR5 manual]

[http://autopsi.info/Su-15/Su-15-XFLR5-Tests.zip Su-15 XFLR5 Pack], including Blender export script, .ac, .txt, and .xfl examples

== Author ==

Victor Slavutinsky, vitosnet at mail dot ru

[[Category:Aerodynamic Tools]]

XFLR5

2016-10-24T09:40:22Z

Vitos: /* Step fourth: Defining plane inertia */

<br />
== Polishing FDM with XFLR5 ==

My next attempt to make aerodynamics of [[Su-15]] model realistic more was with [http://www.xflr5.com/xflr5.htm XFLR5]. That Open Source program is included at most of Linux distributions, to install it is not so big deal, and some of developers used it already. Again, let's go calculation process step by step to figure out what it can do.

== First step: Defining profiles ==

Most easy way is to define profiles of surefaces manually, at "File/Direct Foil Design".

[[File:XFLR5 Profiles.jpg|thumb|XFLR5 wing profiles edit window]]

First clone it from default one, then name it, then adjust common thickness by "Scale Camber and Thickness" dropdown menu. Then look at points of profile at "Edit Foil Coordinates". Don't edit these manually, but compare thickness of profile at 0.1 of chord at XFLR5 and Blender, or where You have it, and then use "Set L.E. Radius" to adjust thickness of beginning of wing.

At now program does not allow to import profile points, it can export it only. Anyway, by experience, to achieve needed result is question of minutes. Note that if You mean some flaps or rudder calculations then You need to create profile with turned flap also here, and then to make additional one, with false flap, beginning at same place, but rotated at zero angle - that one will be used for better exactness of calculations later.

At my Fedora with Cinnamon, latest XFLR5 sometimes stops to react at mouse with additional popup windows. So, maybe, knowing of some Tab/Shift-Tab and Space/Esc keyboard magic would be useful to You.

== Second step: Defining surfaces ==

Save project and switch to "Wing and Plane Design". You would want to set metrics at "Options/Units" to feets and lbs prior, as JSBSim uses these - I did not do that, since my initial model was at meters, but preferred to recalculate output later at Libre Office Calc.

So, use "Plane/Define New Plane". Here You go to "Main Wing/Define".

[[File:XFLR5 WIng Profile.jpg|thumb|XFLR5 Su-15 wing model]]
[[File:XFLR5 Elevator.jpg|thumb|XFLR5 Su-15 model solid elevator variant]]

Look at presented screen to figure out what to do. You may notice next things, actually taken ideologically from program manual:

* Wing starts at zero point.
* It has six parts, two for root with false flap, two for aileron, with flap, and two for tip, with false flap. Second ones at all cases have 1 panel at Y - that way program comprehends structure and can calculate effects of flap-nonflap surfaces joint.
* Each part is defined by things as chord at X, distance from zero axle at Y, offset and so.
* Number of panels is not so big, 8x8 at greater case - by experience I do know that greater takes much more time but don't affect results much.

Save anything and then set wing offsets at main edit window.

Then You do define elevator.

Note that same distributions are set at that screen and previous one, length and number of panels at Y axis are just same for root part of thing and for elevator. That is highly recommended by manual; if length of elevator at Your model is not that same as distance to aileron of wing at Y, and with other similar cases, divide both wing and elevator accordingly, to make it fit panel to panel at Y axis.

Save result, set offsets, then set tail at fin edit window.

== Step third: Defining body ==

[[File:XFLR5 Body.jpg|thumb|XFLR5 body edit window]]

You can use XFLR5 as primitive 3D editor and define body spline by spline. As I had other one already, I preferred other way, and made a Blender exporter plugin. So, make body as half of cylinder at Blender, with 0..positive y's, divided up to ~30 cuts at Y and Z, starting with cone and ending with cone, export it from Blender and import it with "Other/Import Body Definition from text file" at body edition window. Quite easy.

== Step fourth: Defining plane inertia ==

[[File:XFLR5 Inertia.jpg|thumb|XFLR5 inertia edit window]]

Just a bit tricky, and You can omit that step, defining weight and Center of Gravity position at analysis window directly instead - if You do know it. I did, anyway, that option was tested.

I knew more or less exact weights of wing, tail, elevator and empty body from documentation, and set these at "Plane Inertia" window. Then I set additional weights to body - two engines at its positions, as I did knew exact weight of engine also.

And then, since I knew point where CG got to be, I took one tonne from weight of body and defined additional mass there, then shifted it to nose until CG went to needed position - seems to be that Su have really heavy radar there. At Your case You could do same, knowing that CG could not be after main gears, and should be at ~third of median chord of wing.

That's it. If You need some Ixx or so then You can take it from here and, if Your XFLR5 model was made at ft/lbs units, put these values directly at needed place of JSBSim FDM xml model file; at case it was made in meters and kilograms, multiply it with 0.453592 prior.

Also, I would add, better to make such calculations with plane defined a bit other way, with surfaces starts not at zero point inside fuselage, but a bit off it, as at one of examples presented with pack below. Then inertia moments are correct more.

== Step fifth: Calculation ==

OK, everything is set.

[[File:XFLR5 Model Aileron Rudder.jpg|thumb|XFLR5 Su-15 model with ailerons and rudder shifted]]

Open "Analysis/Define an Analysis", choose "Type 1 (Fixed Speed)", with speed of 100m/s at first panel, "Ring Vortex (VLM2)" without other options at second - again, some Ctrl-Tab magic could be useful. Do not use "Viscous" and "Tilt. Geom" options - as I can remember, one of these produces wrong values, while other is error making.

Set name for analysis, press OK, then select it above main window. At side panel set alpha angles, from -45deg to 45 for example, with step of 5deg, and press "Analyze" button. At my old PC it calculated such case for some minutes - two maybe, not more than five for sure.

== Step sixth: Data mining ==

Go to "Polars/Current Polar/Export" and export results to text file. Open it at gedit and change multiply spaces to one by Ctrl-H, " " to " ". Then copy text and paste it to Calc.

[[File:XFLR5 Cl.jpg|thumb|XFLR5 and Datcom lift coefficient comparison]]
[[File:XFLR5 Cd.jpg|thumb|XFLR5 and Datcom drag coefficient comparison]]
[[File:XFLR5 Cm.jpg|thumb|XFLR5 and Datcom pitch moment coefficient comparison]]

First of all, if You calculated at m/kg units, multiply lift coefficient, CL, to
:0.453592/(0.3048^2)
to convert it to feet/lbs; same with drag, CD. As of pitch, CM, since it multiplies at chord in calculations, and goes with inversion, conversion coefficient is
:-0.453592/0.3048

Then look at presented graphs. Since it was said at manual that effects of both wing going trough body and wing starting a bit offside it are unknown, I made two models - one with wing going trough, and one with wing starting offside, then compared results of these two with Datcom results.

Seems to be that lift coefficient is better with wing going trough at smaller absolute alphas values; angles near to critical angle of attack is better with wing starting offside. With negative critical angle it's some median between two variants. Resulting integral CL, combining two initial variants that way, is quite near to Datcom results.

For both CD and CM, drag and moment, variant without holes is better. Drag at zero alpha is too small anyway, set it to half of CD at 5deg manually.

== Step seventh: Higher Machs ==

[[File:Datcom Cd Mach Correction.jpg|thumb|Datcom made drag coefficient due to Mach number correction]]

Unfortunately, current version of XFLR5 seems to not care about speed at all. It produces quite same results at VLM2 method for 100m/s and 200m/s. Panel method, which You could set at "Define Analysis (Advance Users)" - don't forget to switch default "Viscous" option off, as it makes errors instead of values - seems to produce a bit different results, but, again, these are not changing with velocity.

So I made next rough approximation, taken from Datcom data analysis: up to 1Mach CL is more or less same, then it starts to drop, and goes to half of initial values at 2.5Mach. Same with CM. As of drag, it drops to 0.9 to 0.9Mach, jumps to 1.5 at 1.1Mach, and drops to 1 to 2.5Mach.

It's quite rough; anyway, just to add additional tables to functions of coefficients, as at this example, and it would make difference with Datcom model not so notable.

<nowiki><table></nowiki>
<independentVar lookup="row">velocities/mach</independentVar>
<tableData>
0.3000 1.0000
0.4000 1.0112
0.5000 1.0112
0.9000 0.9888
1.1000 0.9775
1.5000 0.8315
2.0000 0.6404
2.5000 0.5281
</tableData>
<nowiki></table></nowiki>

== Step eight: Controlled surfaces ==

[[File:XFLR5 Standalone Elevator.jpg|thumb|XFLR5 Su-15 cut rotated elevator variant]]
[[File:XFLR5 Elevator Cl to Cm.jpg|thumb|XFLR5 elevator moment coefficient converted from elevator lift coefficient]]

Again, it's a bit tricky, since method seems to be not so accurate at moments. At first, You need to calculate change of lift coefficient due to surface shift - of aileron, or, as at example, of fully rotated elevator.

I set internal offsets of it to put axle at zero, then external to make it stay at correct position, then just set its "Tilt Angle" to needed values to rotate it. Secondly, You need to multiply result at distance_from_axle_to_center_of_mass/wing_chord, or some span if that was set as multiplier of that coefficient at xml file. At least on resulted graphs difference at CM caused by elevator shift was lower than CM itself, while CM calculated of CL was greater at needed angles, and model with that variant is controllable, while with pure CM - not.

== Step nine: Experiments ==

As I saw at web, some people do not import some body into XFLR5, but do define it as thick profile at core part of wing. Seems to be that approach produces more or less correct results too. You may try it, while I prefer to make conclusions instead.

== Resume ==

Easy and fast tool for beginners. If You made Your first JSBSim model, especially subsonic one, and do want to step further from initial [[Aeromatic]] made coefficients, that's what You need exactly - it would give You needed results in day or two.

But, making better picture, it calculates more, say, scientific results than Datcom, and some additional steps are needed to make output of it more or less exact with subsonics; at oversonics I went 2.5Mach without reheat at resulted "Su-15" model. Though it was not made for this at all, and would evolve, but at now I would recommend some other approaches to mature developers.

== External links ==
[http://www.xflr5.com/xflr5.htm XFLR5]

[https://sourceforge.net/projects/xflr5/files/Guidelines.pdf/download XFLR5 manual]

[http://autopsi.info/Su-15/Su-15-XFLR5-Tests.zip Su-15 XFLR5 Pack], including Blender export script, .ac, .txt, and .xfl examples

== Author ==

Victor Slavutinsky, vitosnet at mail dot ru

[[Category:Aerodynamic Tools]]

XFLR5

2016-10-24T09:30:10Z

Vitos: /* Step third: Defining body */

<br />
== Polishing FDM with XFLR5 ==

My next attempt to make aerodynamics of [[Su-15]] model realistic more was with [http://www.xflr5.com/xflr5.htm XFLR5]. That Open Source program is included at most of Linux distributions, to install it is not so big deal, and some of developers used it already. Again, let's go calculation process step by step to figure out what it can do.

== First step: Defining profiles ==

Most easy way is to define profiles of surefaces manually, at "File/Direct Foil Design".

[[File:XFLR5 Profiles.jpg|thumb|XFLR5 wing profiles edit window]]

First clone it from default one, then name it, then adjust common thickness by "Scale Camber and Thickness" dropdown menu. Then look at points of profile at "Edit Foil Coordinates". Don't edit these manually, but compare thickness of profile at 0.1 of chord at XFLR5 and Blender, or where You have it, and then use "Set L.E. Radius" to adjust thickness of beginning of wing.

At now program does not allow to import profile points, it can export it only. Anyway, by experience, to achieve needed result is question of minutes. Note that if You mean some flaps or rudder calculations then You need to create profile with turned flap also here, and then to make additional one, with false flap, beginning at same place, but rotated at zero angle - that one will be used for better exactness of calculations later.

At my Fedora with Cinnamon, latest XFLR5 sometimes stops to react at mouse with additional popup windows. So, maybe, knowing of some Tab/Shift-Tab and Space/Esc keyboard magic would be useful to You.

== Second step: Defining surfaces ==

Save project and switch to "Wing and Plane Design". You would want to set metrics at "Options/Units" to feets and lbs prior, as JSBSim uses these - I did not do that, since my initial model was at meters, but preferred to recalculate output later at Libre Office Calc.

So, use "Plane/Define New Plane". Here You go to "Main Wing/Define".

[[File:XFLR5 WIng Profile.jpg|thumb|XFLR5 Su-15 wing model]]
[[File:XFLR5 Elevator.jpg|thumb|XFLR5 Su-15 model solid elevator variant]]

Look at presented screen to figure out what to do. You may notice next things, actually taken ideologically from program manual:

* Wing starts at zero point.
* It has six parts, two for root with false flap, two for aileron, with flap, and two for tip, with false flap. Second ones at all cases have 1 panel at Y - that way program comprehends structure and can calculate effects of flap-nonflap surfaces joint.
* Each part is defined by things as chord at X, distance from zero axle at Y, offset and so.
* Number of panels is not so big, 8x8 at greater case - by experience I do know that greater takes much more time but don't affect results much.

Save anything and then set wing offsets at main edit window.

Then You do define elevator.

Note that same distributions are set at that screen and previous one, length and number of panels at Y axis are just same for root part of thing and for elevator. That is highly recommended by manual; if length of elevator at Your model is not that same as distance to aileron of wing at Y, and with other similar cases, divide both wing and elevator accordingly, to make it fit panel to panel at Y axis.

Save result, set offsets, then set tail at fin edit window.

== Step third: Defining body ==

[[File:XFLR5 Body.jpg|thumb|XFLR5 body edit window]]

You can use XFLR5 as primitive 3D editor and define body spline by spline. As I had other one already, I preferred other way, and made a Blender exporter plugin. So, make body as half of cylinder at Blender, with 0..positive y's, divided up to ~30 cuts at Y and Z, starting with cone and ending with cone, export it from Blender and import it with "Other/Import Body Definition from text file" at body edition window. Quite easy.

== Step fourth: Defining plane inertia ==

[[File:XFLR5 Inertia.jpg|thumb|XFLR5 inertia edit window]]

Just a bit tricky, and You can omit that step, defining weight and Center of Mass position at analysis window directly instead - if You do know it. I did, anyway, that option was tested.

I knew more or less exact weights of wing, tail, elevator and empty body from documentation, and set these at "Plane Inertia" window. Then I set additional weights to body - two engines at its positions, as I did knew exact weight of engine also.

And then, since I knew point where Center of Mass got to be, I took one tonne from weight of body and defined additional mass there, then shifted it to nose until Center of Mass went to needed position - seems to be that Su have really heavy radar there. At Your case You could do same, knowing that Center of Mass could not be after main gears, and should be at ~third of median chord of wing.

That's it. If You need some Ixx or so then You can take it from here and, if Your XFLR5 model was made at ft/lbs units, put these values directly at needed place of JSBSim FDM xml model file; at case it was made in meters and kilograms, multiply it with 0.453592 prior.

Also, I would add, better to make such calculations with plane defined a bit other way, with surfaces starts not at zero point inside fuselage, but a bit off it, as at one of examples presented with pack below. Then inertia moments are correct more.

== Step fifth: Calculation ==

OK, everything is set.

[[File:XFLR5 Model Aileron Rudder.jpg|thumb|XFLR5 Su-15 model with ailerons and rudder shifted]]

Open "Analysis/Define an Analysis", choose "Type 1 (Fixed Speed)", with speed of 100m/s at first panel, "Ring Vortex (VLM2)" without other options at second - again, some Ctrl-Tab magic could be useful. Do not use "Viscous" and "Tilt. Geom" options - as I can remember, one of these produces wrong values, while other is error making.

Set name for analysis, press OK, then select it above main window. At side panel set alpha angles, from -45deg to 45 for example, with step of 5deg, and press "Analyze" button. At my old PC it calculated such case for some minutes - two maybe, not more than five for sure.

== Step sixth: Data mining ==

Go to "Polars/Current Polar/Export" and export results to text file. Open it at gedit and change multiply spaces to one by Ctrl-H, " " to " ". Then copy text and paste it to Calc.

[[File:XFLR5 Cl.jpg|thumb|XFLR5 and Datcom lift coefficient comparison]]
[[File:XFLR5 Cd.jpg|thumb|XFLR5 and Datcom drag coefficient comparison]]
[[File:XFLR5 Cm.jpg|thumb|XFLR5 and Datcom pitch moment coefficient comparison]]

First of all, if You calculated at m/kg units, multiply lift coefficient, CL, to
:0.453592/(0.3048^2)
to convert it to feet/lbs; same with drag, CD. As of pitch, CM, since it multiplies at chord in calculations, and goes with inversion, conversion coefficient is
:-0.453592/0.3048

Then look at presented graphs. Since it was said at manual that effects of both wing going trough body and wing starting a bit offside it are unknown, I made two models - one with wing going trough, and one with wing starting offside, then compared results of these two with Datcom results.

Seems to be that lift coefficient is better with wing going trough at smaller absolute alphas values; angles near to critical angle of attack is better with wing starting offside. With negative critical angle it's some median between two variants. Resulting integral CL, combining two initial variants that way, is quite near to Datcom results.

For both CD and CM, drag and moment, variant without holes is better. Drag at zero alpha is too small anyway, set it to half of CD at 5deg manually.

== Step seventh: Higher Machs ==

[[File:Datcom Cd Mach Correction.jpg|thumb|Datcom made drag coefficient due to Mach number correction]]

Unfortunately, current version of XFLR5 seems to not care about speed at all. It produces quite same results at VLM2 method for 100m/s and 200m/s. Panel method, which You could set at "Define Analysis (Advance Users)" - don't forget to switch default "Viscous" option off, as it makes errors instead of values - seems to produce a bit different results, but, again, these are not changing with velocity.

So I made next rough approximation, taken from Datcom data analysis: up to 1Mach CL is more or less same, then it starts to drop, and goes to half of initial values at 2.5Mach. Same with CM. As of drag, it drops to 0.9 to 0.9Mach, jumps to 1.5 at 1.1Mach, and drops to 1 to 2.5Mach.

It's quite rough; anyway, just to add additional tables to functions of coefficients, as at this example, and it would make difference with Datcom model not so notable.

<nowiki><table></nowiki>
<independentVar lookup="row">velocities/mach</independentVar>
<tableData>
0.3000 1.0000
0.4000 1.0112
0.5000 1.0112
0.9000 0.9888
1.1000 0.9775
1.5000 0.8315
2.0000 0.6404
2.5000 0.5281
</tableData>
<nowiki></table></nowiki>

== Step eight: Controlled surfaces ==

[[File:XFLR5 Standalone Elevator.jpg|thumb|XFLR5 Su-15 cut rotated elevator variant]]
[[File:XFLR5 Elevator Cl to Cm.jpg|thumb|XFLR5 elevator moment coefficient converted from elevator lift coefficient]]

Again, it's a bit tricky, since method seems to be not so accurate at moments. At first, You need to calculate change of lift coefficient due to surface shift - of aileron, or, as at example, of fully rotated elevator.

I set internal offsets of it to put axle at zero, then external to make it stay at correct position, then just set its "Tilt Angle" to needed values to rotate it. Secondly, You need to multiply result at distance_from_axle_to_center_of_mass/wing_chord, or some span if that was set as multiplier of that coefficient at xml file. At least on resulted graphs difference at CM caused by elevator shift was lower than CM itself, while CM calculated of CL was greater at needed angles, and model with that variant is controllable, while with pure CM - not.

== Step nine: Experiments ==

As I saw at web, some people do not import some body into XFLR5, but do define it as thick profile at core part of wing. Seems to be that approach produces more or less correct results too. You may try it, while I prefer to make conclusions instead.

== Resume ==

Easy and fast tool for beginners. If You made Your first JSBSim model, especially subsonic one, and do want to step further from initial [[Aeromatic]] made coefficients, that's what You need exactly - it would give You needed results in day or two.

But, making better picture, it calculates more, say, scientific results than Datcom, and some additional steps are needed to make output of it more or less exact with subsonics; at oversonics I went 2.5Mach without reheat at resulted "Su-15" model. Though it was not made for this at all, and would evolve, but at now I would recommend some other approaches to mature developers.

== External links ==
[http://www.xflr5.com/xflr5.htm XFLR5]

[https://sourceforge.net/projects/xflr5/files/Guidelines.pdf/download XFLR5 manual]

[http://autopsi.info/Su-15/Su-15-XFLR5-Tests.zip Su-15 XFLR5 Pack], including Blender export script, .ac, .txt, and .xfl examples

== Author ==

Victor Slavutinsky, vitosnet at mail dot ru

[[Category:Aerodynamic Tools]]

XFLR5

2016-10-24T09:29:29Z

Vitos: /* Second step: Defining surfaces */

<br />
== Polishing FDM with XFLR5 ==

My next attempt to make aerodynamics of [[Su-15]] model realistic more was with [http://www.xflr5.com/xflr5.htm XFLR5]. That Open Source program is included at most of Linux distributions, to install it is not so big deal, and some of developers used it already. Again, let's go calculation process step by step to figure out what it can do.

== First step: Defining profiles ==

Most easy way is to define profiles of surefaces manually, at "File/Direct Foil Design".

[[File:XFLR5 Profiles.jpg|thumb|XFLR5 wing profiles edit window]]

First clone it from default one, then name it, then adjust common thickness by "Scale Camber and Thickness" dropdown menu. Then look at points of profile at "Edit Foil Coordinates". Don't edit these manually, but compare thickness of profile at 0.1 of chord at XFLR5 and Blender, or where You have it, and then use "Set L.E. Radius" to adjust thickness of beginning of wing.

At now program does not allow to import profile points, it can export it only. Anyway, by experience, to achieve needed result is question of minutes. Note that if You mean some flaps or rudder calculations then You need to create profile with turned flap also here, and then to make additional one, with false flap, beginning at same place, but rotated at zero angle - that one will be used for better exactness of calculations later.

At my Fedora with Cinnamon, latest XFLR5 sometimes stops to react at mouse with additional popup windows. So, maybe, knowing of some Tab/Shift-Tab and Space/Esc keyboard magic would be useful to You.

== Second step: Defining surfaces ==

Save project and switch to "Wing and Plane Design". You would want to set metrics at "Options/Units" to feets and lbs prior, as JSBSim uses these - I did not do that, since my initial model was at meters, but preferred to recalculate output later at Libre Office Calc.

So, use "Plane/Define New Plane". Here You go to "Main Wing/Define".

[[File:XFLR5 WIng Profile.jpg|thumb|XFLR5 Su-15 wing model]]
[[File:XFLR5 Elevator.jpg|thumb|XFLR5 Su-15 model solid elevator variant]]

Look at presented screen to figure out what to do. You may notice next things, actually taken ideologically from program manual:

* Wing starts at zero point.
* It has six parts, two for root with false flap, two for aileron, with flap, and two for tip, with false flap. Second ones at all cases have 1 panel at Y - that way program comprehends structure and can calculate effects of flap-nonflap surfaces joint.
* Each part is defined by things as chord at X, distance from zero axle at Y, offset and so.
* Number of panels is not so big, 8x8 at greater case - by experience I do know that greater takes much more time but don't affect results much.

Save anything and then set wing offsets at main edit window.

Then You do define elevator.

Note that same distributions are set at that screen and previous one, length and number of panels at Y axis are just same for root part of thing and for elevator. That is highly recommended by manual; if length of elevator at Your model is not that same as distance to aileron of wing at Y, and with other similar cases, divide both wing and elevator accordingly, to make it fit panel to panel at Y axis.

Save result, set offsets, then set tail at fin edit window.

== Step third: Defining body ==

[[File:XFLR5 Body.jpg|thumb|XFLR5 body edit window]]

You can use XFLR5 as primitive 3D editor and define body spline by spline. As I already had other one, I preferred other way, and made a Blender exporter plugin. So, make body as half of cylinder at Blender, with 0..positive y's, divided up to ~30 cuts at Y and Z, starting with cone and ending with cone, export it from Blender and import it with "Other/Import Body Definition from text file" at body edition window. Quite easy.

== Step fourth: Defining plane inertia ==

[[File:XFLR5 Inertia.jpg|thumb|XFLR5 inertia edit window]]

Just a bit tricky, and You can omit that step, defining weight and Center of Mass position at analysis window directly instead - if You do know it. I did, anyway, that option was tested.

I knew more or less exact weights of wing, tail, elevator and empty body from documentation, and set these at "Plane Inertia" window. Then I set additional weights to body - two engines at its positions, as I did knew exact weight of engine also.

And then, since I knew point where Center of Mass got to be, I took one tonne from weight of body and defined additional mass there, then shifted it to nose until Center of Mass went to needed position - seems to be that Su have really heavy radar there. At Your case You could do same, knowing that Center of Mass could not be after main gears, and should be at ~third of median chord of wing.

That's it. If You need some Ixx or so then You can take it from here and, if Your XFLR5 model was made at ft/lbs units, put these values directly at needed place of JSBSim FDM xml model file; at case it was made in meters and kilograms, multiply it with 0.453592 prior.

Also, I would add, better to make such calculations with plane defined a bit other way, with surfaces starts not at zero point inside fuselage, but a bit off it, as at one of examples presented with pack below. Then inertia moments are correct more.

== Step fifth: Calculation ==

OK, everything is set.

[[File:XFLR5 Model Aileron Rudder.jpg|thumb|XFLR5 Su-15 model with ailerons and rudder shifted]]

Open "Analysis/Define an Analysis", choose "Type 1 (Fixed Speed)", with speed of 100m/s at first panel, "Ring Vortex (VLM2)" without other options at second - again, some Ctrl-Tab magic could be useful. Do not use "Viscous" and "Tilt. Geom" options - as I can remember, one of these produces wrong values, while other is error making.

Set name for analysis, press OK, then select it above main window. At side panel set alpha angles, from -45deg to 45 for example, with step of 5deg, and press "Analyze" button. At my old PC it calculated such case for some minutes - two maybe, not more than five for sure.

== Step sixth: Data mining ==

Go to "Polars/Current Polar/Export" and export results to text file. Open it at gedit and change multiply spaces to one by Ctrl-H, " " to " ". Then copy text and paste it to Calc.

[[File:XFLR5 Cl.jpg|thumb|XFLR5 and Datcom lift coefficient comparison]]
[[File:XFLR5 Cd.jpg|thumb|XFLR5 and Datcom drag coefficient comparison]]
[[File:XFLR5 Cm.jpg|thumb|XFLR5 and Datcom pitch moment coefficient comparison]]

First of all, if You calculated at m/kg units, multiply lift coefficient, CL, to
:0.453592/(0.3048^2)
to convert it to feet/lbs; same with drag, CD. As of pitch, CM, since it multiplies at chord in calculations, and goes with inversion, conversion coefficient is
:-0.453592/0.3048

Then look at presented graphs. Since it was said at manual that effects of both wing going trough body and wing starting a bit offside it are unknown, I made two models - one with wing going trough, and one with wing starting offside, then compared results of these two with Datcom results.

Seems to be that lift coefficient is better with wing going trough at smaller absolute alphas values; angles near to critical angle of attack is better with wing starting offside. With negative critical angle it's some median between two variants. Resulting integral CL, combining two initial variants that way, is quite near to Datcom results.

For both CD and CM, drag and moment, variant without holes is better. Drag at zero alpha is too small anyway, set it to half of CD at 5deg manually.

== Step seventh: Higher Machs ==

[[File:Datcom Cd Mach Correction.jpg|thumb|Datcom made drag coefficient due to Mach number correction]]

Unfortunately, current version of XFLR5 seems to not care about speed at all. It produces quite same results at VLM2 method for 100m/s and 200m/s. Panel method, which You could set at "Define Analysis (Advance Users)" - don't forget to switch default "Viscous" option off, as it makes errors instead of values - seems to produce a bit different results, but, again, these are not changing with velocity.

So I made next rough approximation, taken from Datcom data analysis: up to 1Mach CL is more or less same, then it starts to drop, and goes to half of initial values at 2.5Mach. Same with CM. As of drag, it drops to 0.9 to 0.9Mach, jumps to 1.5 at 1.1Mach, and drops to 1 to 2.5Mach.

It's quite rough; anyway, just to add additional tables to functions of coefficients, as at this example, and it would make difference with Datcom model not so notable.

<nowiki><table></nowiki>
<independentVar lookup="row">velocities/mach</independentVar>
<tableData>
0.3000 1.0000
0.4000 1.0112
0.5000 1.0112
0.9000 0.9888
1.1000 0.9775
1.5000 0.8315
2.0000 0.6404
2.5000 0.5281
</tableData>
<nowiki></table></nowiki>

== Step eight: Controlled surfaces ==

[[File:XFLR5 Standalone Elevator.jpg|thumb|XFLR5 Su-15 cut rotated elevator variant]]
[[File:XFLR5 Elevator Cl to Cm.jpg|thumb|XFLR5 elevator moment coefficient converted from elevator lift coefficient]]

Again, it's a bit tricky, since method seems to be not so accurate at moments. At first, You need to calculate change of lift coefficient due to surface shift - of aileron, or, as at example, of fully rotated elevator.

I set internal offsets of it to put axle at zero, then external to make it stay at correct position, then just set its "Tilt Angle" to needed values to rotate it. Secondly, You need to multiply result at distance_from_axle_to_center_of_mass/wing_chord, or some span if that was set as multiplier of that coefficient at xml file. At least on resulted graphs difference at CM caused by elevator shift was lower than CM itself, while CM calculated of CL was greater at needed angles, and model with that variant is controllable, while with pure CM - not.

== Step nine: Experiments ==

As I saw at web, some people do not import some body into XFLR5, but do define it as thick profile at core part of wing. Seems to be that approach produces more or less correct results too. You may try it, while I prefer to make conclusions instead.

== Resume ==

Easy and fast tool for beginners. If You made Your first JSBSim model, especially subsonic one, and do want to step further from initial [[Aeromatic]] made coefficients, that's what You need exactly - it would give You needed results in day or two.

But, making better picture, it calculates more, say, scientific results than Datcom, and some additional steps are needed to make output of it more or less exact with subsonics; at oversonics I went 2.5Mach without reheat at resulted "Su-15" model. Though it was not made for this at all, and would evolve, but at now I would recommend some other approaches to mature developers.

== External links ==
[http://www.xflr5.com/xflr5.htm XFLR5]

[https://sourceforge.net/projects/xflr5/files/Guidelines.pdf/download XFLR5 manual]

[http://autopsi.info/Su-15/Su-15-XFLR5-Tests.zip Su-15 XFLR5 Pack], including Blender export script, .ac, .txt, and .xfl examples

== Author ==

Victor Slavutinsky, vitosnet at mail dot ru

[[Category:Aerodynamic Tools]]

XFLR5

2016-10-24T09:28:39Z

Vitos: /* Second step: Defining surfaces */

<br />
== Polishing FDM with XFLR5 ==

My next attempt to make aerodynamics of [[Su-15]] model realistic more was with [http://www.xflr5.com/xflr5.htm XFLR5]. That Open Source program is included at most of Linux distributions, to install it is not so big deal, and some of developers used it already. Again, let's go calculation process step by step to figure out what it can do.

== First step: Defining profiles ==

Most easy way is to define profiles of surefaces manually, at "File/Direct Foil Design".

[[File:XFLR5 Profiles.jpg|thumb|XFLR5 wing profiles edit window]]

First clone it from default one, then name it, then adjust common thickness by "Scale Camber and Thickness" dropdown menu. Then look at points of profile at "Edit Foil Coordinates". Don't edit these manually, but compare thickness of profile at 0.1 of chord at XFLR5 and Blender, or where You have it, and then use "Set L.E. Radius" to adjust thickness of beginning of wing.

At now program does not allow to import profile points, it can export it only. Anyway, by experience, to achieve needed result is question of minutes. Note that if You mean some flaps or rudder calculations then You need to create profile with turned flap also here, and then to make additional one, with false flap, beginning at same place, but rotated at zero angle - that one will be used for better exactness of calculations later.

At my Fedora with Cinnamon, latest XFLR5 sometimes stops to react at mouse with additional popup windows. So, maybe, knowing of some Tab/Shift-Tab and Space/Esc keyboard magic would be useful to You.

== Second step: Defining surfaces ==

Save project and switch to "Wing and Plane Design". You would want to set metrics at "Options/Units" to feets and lbs prior, as JSBSim uses these - I did not do that, since my initial model was at meters, but preferred to recalculate output later at Libre Office Calc.

So, use "Plane/Define New Plane". Here You go to "Main Wing/Define".

[[File:XFLR5 WIng Profile.jpg|thumb|XFLR5 Su-15 wing model]]
[[File:XFLR5 Elevator.jpg|thumb|XFLR5 Su-15 model solid elevator variant]]

Look at presented screen to figure out what to do. You may notice next things, actually taken ideologically from program manual:

* Wing starts at zero point.
* It has six parts, two for root with false flap, two for aileron, with flap, and two for tip, with false flap. Second ones at all cases have 1 panel at Y - that way program comprehends structure and can calculate effects of flap-nonflap surfaces joint.
* Each part is defined by things as chord at X, distance from zero axle at Y, offset and so.
* Number of panels is not so big, 8x8 at greater case - by experience I do know that greater takes much more time but don't affect results much.

Save anything and then set wing offsets at main edit window.

Then You do define elevator.

Note that same distributions are set at screen, length and number of panels at Y axis are just same for root part of thing and elevator. That is highly recommended by manual; if length of elevator at Your model is not that same as distance to aileron of wing at Y, and with other similar cases, divide both wing and elevator accordingly, to make it fit panel to panel at Y axis.

Save result, set offsets, then set tail at fin edit window.

== Step third: Defining body ==

[[File:XFLR5 Body.jpg|thumb|XFLR5 body edit window]]

You can use XFLR5 as primitive 3D editor and define body spline by spline. As I already had other one, I preferred other way, and made a Blender exporter plugin. So, make body as half of cylinder at Blender, with 0..positive y's, divided up to ~30 cuts at Y and Z, starting with cone and ending with cone, export it from Blender and import it with "Other/Import Body Definition from text file" at body edition window. Quite easy.

== Step fourth: Defining plane inertia ==

[[File:XFLR5 Inertia.jpg|thumb|XFLR5 inertia edit window]]

Just a bit tricky, and You can omit that step, defining weight and Center of Mass position at analysis window directly instead - if You do know it. I did, anyway, that option was tested.

I knew more or less exact weights of wing, tail, elevator and empty body from documentation, and set these at "Plane Inertia" window. Then I set additional weights to body - two engines at its positions, as I did knew exact weight of engine also.

And then, since I knew point where Center of Mass got to be, I took one tonne from weight of body and defined additional mass there, then shifted it to nose until Center of Mass went to needed position - seems to be that Su have really heavy radar there. At Your case You could do same, knowing that Center of Mass could not be after main gears, and should be at ~third of median chord of wing.

That's it. If You need some Ixx or so then You can take it from here and, if Your XFLR5 model was made at ft/lbs units, put these values directly at needed place of JSBSim FDM xml model file; at case it was made in meters and kilograms, multiply it with 0.453592 prior.

Also, I would add, better to make such calculations with plane defined a bit other way, with surfaces starts not at zero point inside fuselage, but a bit off it, as at one of examples presented with pack below. Then inertia moments are correct more.

== Step fifth: Calculation ==

OK, everything is set.

[[File:XFLR5 Model Aileron Rudder.jpg|thumb|XFLR5 Su-15 model with ailerons and rudder shifted]]

Open "Analysis/Define an Analysis", choose "Type 1 (Fixed Speed)", with speed of 100m/s at first panel, "Ring Vortex (VLM2)" without other options at second - again, some Ctrl-Tab magic could be useful. Do not use "Viscous" and "Tilt. Geom" options - as I can remember, one of these produces wrong values, while other is error making.

Set name for analysis, press OK, then select it above main window. At side panel set alpha angles, from -45deg to 45 for example, with step of 5deg, and press "Analyze" button. At my old PC it calculated such case for some minutes - two maybe, not more than five for sure.

== Step sixth: Data mining ==

Go to "Polars/Current Polar/Export" and export results to text file. Open it at gedit and change multiply spaces to one by Ctrl-H, " " to " ". Then copy text and paste it to Calc.

[[File:XFLR5 Cl.jpg|thumb|XFLR5 and Datcom lift coefficient comparison]]
[[File:XFLR5 Cd.jpg|thumb|XFLR5 and Datcom drag coefficient comparison]]
[[File:XFLR5 Cm.jpg|thumb|XFLR5 and Datcom pitch moment coefficient comparison]]

First of all, if You calculated at m/kg units, multiply lift coefficient, CL, to
:0.453592/(0.3048^2)
to convert it to feet/lbs; same with drag, CD. As of pitch, CM, since it multiplies at chord in calculations, and goes with inversion, conversion coefficient is
:-0.453592/0.3048

Then look at presented graphs. Since it was said at manual that effects of both wing going trough body and wing starting a bit offside it are unknown, I made two models - one with wing going trough, and one with wing starting offside, then compared results of these two with Datcom results.

Seems to be that lift coefficient is better with wing going trough at smaller absolute alphas values; angles near to critical angle of attack is better with wing starting offside. With negative critical angle it's some median between two variants. Resulting integral CL, combining two initial variants that way, is quite near to Datcom results.

For both CD and CM, drag and moment, variant without holes is better. Drag at zero alpha is too small anyway, set it to half of CD at 5deg manually.

== Step seventh: Higher Machs ==

[[File:Datcom Cd Mach Correction.jpg|thumb|Datcom made drag coefficient due to Mach number correction]]

Unfortunately, current version of XFLR5 seems to not care about speed at all. It produces quite same results at VLM2 method for 100m/s and 200m/s. Panel method, which You could set at "Define Analysis (Advance Users)" - don't forget to switch default "Viscous" option off, as it makes errors instead of values - seems to produce a bit different results, but, again, these are not changing with velocity.

So I made next rough approximation, taken from Datcom data analysis: up to 1Mach CL is more or less same, then it starts to drop, and goes to half of initial values at 2.5Mach. Same with CM. As of drag, it drops to 0.9 to 0.9Mach, jumps to 1.5 at 1.1Mach, and drops to 1 to 2.5Mach.

It's quite rough; anyway, just to add additional tables to functions of coefficients, as at this example, and it would make difference with Datcom model not so notable.

<nowiki><table></nowiki>
<independentVar lookup="row">velocities/mach</independentVar>
<tableData>
0.3000 1.0000
0.4000 1.0112
0.5000 1.0112
0.9000 0.9888
1.1000 0.9775
1.5000 0.8315
2.0000 0.6404
2.5000 0.5281
</tableData>
<nowiki></table></nowiki>

== Step eight: Controlled surfaces ==

[[File:XFLR5 Standalone Elevator.jpg|thumb|XFLR5 Su-15 cut rotated elevator variant]]
[[File:XFLR5 Elevator Cl to Cm.jpg|thumb|XFLR5 elevator moment coefficient converted from elevator lift coefficient]]

Again, it's a bit tricky, since method seems to be not so accurate at moments. At first, You need to calculate change of lift coefficient due to surface shift - of aileron, or, as at example, of fully rotated elevator.

I set internal offsets of it to put axle at zero, then external to make it stay at correct position, then just set its "Tilt Angle" to needed values to rotate it. Secondly, You need to multiply result at distance_from_axle_to_center_of_mass/wing_chord, or some span if that was set as multiplier of that coefficient at xml file. At least on resulted graphs difference at CM caused by elevator shift was lower than CM itself, while CM calculated of CL was greater at needed angles, and model with that variant is controllable, while with pure CM - not.

== Step nine: Experiments ==

As I saw at web, some people do not import some body into XFLR5, but do define it as thick profile at core part of wing. Seems to be that approach produces more or less correct results too. You may try it, while I prefer to make conclusions instead.

== Resume ==

Easy and fast tool for beginners. If You made Your first JSBSim model, especially subsonic one, and do want to step further from initial [[Aeromatic]] made coefficients, that's what You need exactly - it would give You needed results in day or two.

But, making better picture, it calculates more, say, scientific results than Datcom, and some additional steps are needed to make output of it more or less exact with subsonics; at oversonics I went 2.5Mach without reheat at resulted "Su-15" model. Though it was not made for this at all, and would evolve, but at now I would recommend some other approaches to mature developers.

== External links ==
[http://www.xflr5.com/xflr5.htm XFLR5]

[https://sourceforge.net/projects/xflr5/files/Guidelines.pdf/download XFLR5 manual]

[http://autopsi.info/Su-15/Su-15-XFLR5-Tests.zip Su-15 XFLR5 Pack], including Blender export script, .ac, .txt, and .xfl examples

== Author ==

Victor Slavutinsky, vitosnet at mail dot ru

[[Category:Aerodynamic Tools]]

XFLR5

2016-10-23T22:58:53Z

Vitos: /* Resume */

<br />
== Polishing FDM with XFLR5 ==

My next attempt to make aerodynamics of [[Su-15]] model realistic more was with [http://www.xflr5.com/xflr5.htm XFLR5]. That Open Source program is included at most of Linux distributions, to install it is not so big deal, and some of developers used it already. Again, let's go calculation process step by step to figure out what it can do.

== First step: Defining profiles ==

Most easy way is to define profiles of surefaces manually, at "File/Direct Foil Design".

[[File:XFLR5 Profiles.jpg|thumb|XFLR5 wing profiles edit window]]

First clone it from default one, then name it, then adjust common thickness by "Scale Camber and Thickness" dropdown menu. Then look at points of profile at "Edit Foil Coordinates". Don't edit these manually, but compare thickness of profile at 0.1 of chord at XFLR5 and Blender, or where You have it, and then use "Set L.E. Radius" to adjust thickness of beginning of wing.

At now program does not allow to import profile points, it can export it only. Anyway, by experience, to achieve needed result is question of minutes. Note that if You mean some flaps or rudder calculations then You need to create profile with turned flap also here, and then to make additional one, with false flap, beginning at same place, but rotated at zero angle - that one will be used for better exactness of calculations later.

At my Fedora with Cinnamon, latest XFLR5 sometimes stops to react at mouse with additional popup windows. So, maybe, knowing of some Tab/Shift-Tab and Space/Esc keyboard magic would be useful to You.

== Second step: Defining surfaces ==

Save project and switch to "Wing and Plane Design". You would want to set metrics at "Options/Units" to feets and lbs prior, as JSBSim uses these - I did not do that, since my initial model was at meters, but preferred to recalculate output later at Libre Office Calc.

So, use "Plane/Define New Plane". Here You go to "Main Wing/Define".

[[File:XFLR5 WIng Profile.jpg|thumb|XFLR5 Su-15 wing model]]
[[File:XFLR5 Elevator.jpg|thumb|XFLR5 Su-15 model solid elevator variant]]

Look at presented screen to figure out what to do. You may notice next things, actually taken ideologically from program manual:

* Wing starts at zero point.
* It has six parts, two for root with false flap, two for aileron, with flap, and two for tip, with false flap. Second ones at all cases have 1 panel at Y - that way program comprehends structure and can calculate effects of flap-nonflap surfaces joint.
* Each pat is defined by things as chord at X, distance from zero axle at Y, offset and so.
* Number of panels is not so big, 8x8 at greater case - by experience I do know that greater takes much more time but don't affect results much.

Save anything and then set wing offsets at main edit window.

Then You do define elevator.

Note that same distributions are set at screen, length and number of panels at Y axis are just same for root part of thing and elevator. That is highly recommended by manual; if length of elevator at Your model is not that same as distance to aileron of wing at Y, and with other similar cases, divide both wing and elevator accordingly, to make it fit panel to panel at Y axis.

Save result, set offsets, then set tail at fin edit window.

== Step third: Defining body ==

[[File:XFLR5 Body.jpg|thumb|XFLR5 body edit window]]

You can use XFLR5 as primitive 3D editor and define body spline by spline. As I already had other one, I preferred other way, and made a Blender exporter plugin. So, make body as half of cylinder at Blender, with 0..positive y's, divided up to ~30 cuts at Y and Z, starting with cone and ending with cone, export it from Blender and import it with "Other/Import Body Definition from text file" at body edition window. Quite easy.

== Step fourth: Defining plane inertia ==

[[File:XFLR5 Inertia.jpg|thumb|XFLR5 inertia edit window]]

Just a bit tricky, and You can omit that step, defining weight and Center of Mass position at analysis window directly instead - if You do know it. I did, anyway, that option was tested.

I knew more or less exact weights of wing, tail, elevator and empty body from documentation, and set these at "Plane Inertia" window. Then I set additional weights to body - two engines at its positions, as I did knew exact weight of engine also.

And then, since I knew point where Center of Mass got to be, I took one tonne from weight of body and defined additional mass there, then shifted it to nose until Center of Mass went to needed position - seems to be that Su have really heavy radar there. At Your case You could do same, knowing that Center of Mass could not be after main gears, and should be at ~third of median chord of wing.

That's it. If You need some Ixx or so then You can take it from here and, if Your XFLR5 model was made at ft/lbs units, put these values directly at needed place of JSBSim FDM xml model file; at case it was made in meters and kilograms, multiply it with 0.453592 prior.

Also, I would add, better to make such calculations with plane defined a bit other way, with surfaces starts not at zero point inside fuselage, but a bit off it, as at one of examples presented with pack below. Then inertia moments are correct more.

== Step fifth: Calculation ==

OK, everything is set.

[[File:XFLR5 Model Aileron Rudder.jpg|thumb|XFLR5 Su-15 model with ailerons and rudder shifted]]

Open "Analysis/Define an Analysis", choose "Type 1 (Fixed Speed)", with speed of 100m/s at first panel, "Ring Vortex (VLM2)" without other options at second - again, some Ctrl-Tab magic could be useful. Do not use "Viscous" and "Tilt. Geom" options - as I can remember, one of these produces wrong values, while other is error making.

Set name for analysis, press OK, then select it above main window. At side panel set alpha angles, from -45deg to 45 for example, with step of 5deg, and press "Analyze" button. At my old PC it calculated such case for some minutes - two maybe, not more than five for sure.

== Step sixth: Data mining ==

Go to "Polars/Current Polar/Export" and export results to text file. Open it at gedit and change multiply spaces to one by Ctrl-H, " " to " ". Then copy text and paste it to Calc.

[[File:XFLR5 Cl.jpg|thumb|XFLR5 and Datcom lift coefficient comparison]]
[[File:XFLR5 Cd.jpg|thumb|XFLR5 and Datcom drag coefficient comparison]]
[[File:XFLR5 Cm.jpg|thumb|XFLR5 and Datcom pitch moment coefficient comparison]]

First of all, if You calculated at m/kg units, multiply lift coefficient, CL, to
:0.453592/(0.3048^2)
to convert it to feet/lbs; same with drag, CD. As of pitch, CM, since it multiplies at chord in calculations, and goes with inversion, conversion coefficient is
:-0.453592/0.3048

Then look at presented graphs. Since it was said at manual that effects of both wing going trough body and wing starting a bit offside it are unknown, I made two models - one with wing going trough, and one with wing starting offside, then compared results of these two with Datcom results.

Seems to be that lift coefficient is better with wing going trough at smaller absolute alphas values; angles near to critical angle of attack is better with wing starting offside. With negative critical angle it's some median between two variants. Resulting integral CL, combining two initial variants that way, is quite near to Datcom results.

For both CD and CM, drag and moment, variant without holes is better. Drag at zero alpha is too small anyway, set it to half of CD at 5deg manually.

== Step seventh: Higher Machs ==

[[File:Datcom Cd Mach Correction.jpg|thumb|Datcom made drag coefficient due to Mach number correction]]

Unfortunately, current version of XFLR5 seems to not care about speed at all. It produces quite same results at VLM2 method for 100m/s and 200m/s. Panel method, which You could set at "Define Analysis (Advance Users)" - don't forget to switch default "Viscous" option off, as it makes errors instead of values - seems to produce a bit different results, but, again, these are not changing with velocity.

So I made next rough approximation, taken from Datcom data analysis: up to 1Mach CL is more or less same, then it starts to drop, and goes to half of initial values at 2.5Mach. Same with CM. As of drag, it drops to 0.9 to 0.9Mach, jumps to 1.5 at 1.1Mach, and drops to 1 to 2.5Mach.

It's quite rough; anyway, just to add additional tables to functions of coefficients, as at this example, and it would make difference with Datcom model not so notable.

<nowiki><table></nowiki>
<independentVar lookup="row">velocities/mach</independentVar>
<tableData>
0.3000 1.0000
0.4000 1.0112
0.5000 1.0112
0.9000 0.9888
1.1000 0.9775
1.5000 0.8315
2.0000 0.6404
2.5000 0.5281
</tableData>
<nowiki></table></nowiki>

== Step eight: Controlled surfaces ==

[[File:XFLR5 Standalone Elevator.jpg|thumb|XFLR5 Su-15 cut rotated elevator variant]]
[[File:XFLR5 Elevator Cl to Cm.jpg|thumb|XFLR5 elevator moment coefficient converted from elevator lift coefficient]]

Again, it's a bit tricky, since method seems to be not so accurate at moments. At first, You need to calculate change of lift coefficient due to surface shift - of aileron, or, as at example, of fully rotated elevator.

I set internal offsets of it to put axle at zero, then external to make it stay at correct position, then just set its "Tilt Angle" to needed values to rotate it. Secondly, You need to multiply result at distance_from_axle_to_center_of_mass/wing_chord, or some span if that was set as multiplier of that coefficient at xml file. At least on resulted graphs difference at CM caused by elevator shift was lower than CM itself, while CM calculated of CL was greater at needed angles, and model with that variant is controllable, while with pure CM - not.

== Step nine: Experiments ==

As I saw at web, some people do not import some body into XFLR5, but do define it as thick profile at core part of wing. Seems to be that approach produces more or less correct results too. You may try it, while I prefer to make conclusions instead.

== Resume ==

Easy and fast tool for beginners. If You made Your first JSBSim model, especially subsonic one, and do want to step further from initial [[Aeromatic]] made coefficients, that's what You need exactly - it would give You needed results in day or two.

But, making better picture, it calculates more, say, scientific results than Datcom, and some additional steps are needed to make output of it more or less exact with subsonics; at oversonics I went 2.5Mach without reheat at resulted "Su-15" model. Though it was not made for this at all, and would evolve, but at now I would recommend some other approaches to mature developers.

== External links ==
[http://www.xflr5.com/xflr5.htm XFLR5]

[https://sourceforge.net/projects/xflr5/files/Guidelines.pdf/download XFLR5 manual]

[http://autopsi.info/Su-15/Su-15-XFLR5-Tests.zip Su-15 XFLR5 Pack], including Blender export script, .ac, .txt, and .xfl examples

== Author ==

Victor Slavutinsky, vitosnet at mail dot ru

[[Category:Aerodynamic Tools]]

XFLR5

2016-10-23T22:57:19Z

Vitos: /* Step nine: Experiments */

<br />
== Polishing FDM with XFLR5 ==

My next attempt to make aerodynamics of [[Su-15]] model realistic more was with [http://www.xflr5.com/xflr5.htm XFLR5]. That Open Source program is included at most of Linux distributions, to install it is not so big deal, and some of developers used it already. Again, let's go calculation process step by step to figure out what it can do.

== First step: Defining profiles ==

Most easy way is to define profiles of surefaces manually, at "File/Direct Foil Design".

[[File:XFLR5 Profiles.jpg|thumb|XFLR5 wing profiles edit window]]

First clone it from default one, then name it, then adjust common thickness by "Scale Camber and Thickness" dropdown menu. Then look at points of profile at "Edit Foil Coordinates". Don't edit these manually, but compare thickness of profile at 0.1 of chord at XFLR5 and Blender, or where You have it, and then use "Set L.E. Radius" to adjust thickness of beginning of wing.

At now program does not allow to import profile points, it can export it only. Anyway, by experience, to achieve needed result is question of minutes. Note that if You mean some flaps or rudder calculations then You need to create profile with turned flap also here, and then to make additional one, with false flap, beginning at same place, but rotated at zero angle - that one will be used for better exactness of calculations later.

At my Fedora with Cinnamon, latest XFLR5 sometimes stops to react at mouse with additional popup windows. So, maybe, knowing of some Tab/Shift-Tab and Space/Esc keyboard magic would be useful to You.

== Second step: Defining surfaces ==

Save project and switch to "Wing and Plane Design". You would want to set metrics at "Options/Units" to feets and lbs prior, as JSBSim uses these - I did not do that, since my initial model was at meters, but preferred to recalculate output later at Libre Office Calc.

So, use "Plane/Define New Plane". Here You go to "Main Wing/Define".

[[File:XFLR5 WIng Profile.jpg|thumb|XFLR5 Su-15 wing model]]
[[File:XFLR5 Elevator.jpg|thumb|XFLR5 Su-15 model solid elevator variant]]

Look at presented screen to figure out what to do. You may notice next things, actually taken ideologically from program manual:

* Wing starts at zero point.
* It has six parts, two for root with false flap, two for aileron, with flap, and two for tip, with false flap. Second ones at all cases have 1 panel at Y - that way program comprehends structure and can calculate effects of flap-nonflap surfaces joint.
* Each pat is defined by things as chord at X, distance from zero axle at Y, offset and so.
* Number of panels is not so big, 8x8 at greater case - by experience I do know that greater takes much more time but don't affect results much.

Save anything and then set wing offsets at main edit window.

Then You do define elevator.

Note that same distributions are set at screen, length and number of panels at Y axis are just same for root part of thing and elevator. That is highly recommended by manual; if length of elevator at Your model is not that same as distance to aileron of wing at Y, and with other similar cases, divide both wing and elevator accordingly, to make it fit panel to panel at Y axis.

Save result, set offsets, then set tail at fin edit window.

== Step third: Defining body ==

[[File:XFLR5 Body.jpg|thumb|XFLR5 body edit window]]

You can use XFLR5 as primitive 3D editor and define body spline by spline. As I already had other one, I preferred other way, and made a Blender exporter plugin. So, make body as half of cylinder at Blender, with 0..positive y's, divided up to ~30 cuts at Y and Z, starting with cone and ending with cone, export it from Blender and import it with "Other/Import Body Definition from text file" at body edition window. Quite easy.

== Step fourth: Defining plane inertia ==

[[File:XFLR5 Inertia.jpg|thumb|XFLR5 inertia edit window]]

Just a bit tricky, and You can omit that step, defining weight and Center of Mass position at analysis window directly instead - if You do know it. I did, anyway, that option was tested.

I knew more or less exact weights of wing, tail, elevator and empty body from documentation, and set these at "Plane Inertia" window. Then I set additional weights to body - two engines at its positions, as I did knew exact weight of engine also.

And then, since I knew point where Center of Mass got to be, I took one tonne from weight of body and defined additional mass there, then shifted it to nose until Center of Mass went to needed position - seems to be that Su have really heavy radar there. At Your case You could do same, knowing that Center of Mass could not be after main gears, and should be at ~third of median chord of wing.

That's it. If You need some Ixx or so then You can take it from here and, if Your XFLR5 model was made at ft/lbs units, put these values directly at needed place of JSBSim FDM xml model file; at case it was made in meters and kilograms, multiply it with 0.453592 prior.

Also, I would add, better to make such calculations with plane defined a bit other way, with surfaces starts not at zero point inside fuselage, but a bit off it, as at one of examples presented with pack below. Then inertia moments are correct more.

== Step fifth: Calculation ==

OK, everything is set.

[[File:XFLR5 Model Aileron Rudder.jpg|thumb|XFLR5 Su-15 model with ailerons and rudder shifted]]

Open "Analysis/Define an Analysis", choose "Type 1 (Fixed Speed)", with speed of 100m/s at first panel, "Ring Vortex (VLM2)" without other options at second - again, some Ctrl-Tab magic could be useful. Do not use "Viscous" and "Tilt. Geom" options - as I can remember, one of these produces wrong values, while other is error making.

Set name for analysis, press OK, then select it above main window. At side panel set alpha angles, from -45deg to 45 for example, with step of 5deg, and press "Analyze" button. At my old PC it calculated such case for some minutes - two maybe, not more than five for sure.

== Step sixth: Data mining ==

Go to "Polars/Current Polar/Export" and export results to text file. Open it at gedit and change multiply spaces to one by Ctrl-H, " " to " ". Then copy text and paste it to Calc.

[[File:XFLR5 Cl.jpg|thumb|XFLR5 and Datcom lift coefficient comparison]]
[[File:XFLR5 Cd.jpg|thumb|XFLR5 and Datcom drag coefficient comparison]]
[[File:XFLR5 Cm.jpg|thumb|XFLR5 and Datcom pitch moment coefficient comparison]]

First of all, if You calculated at m/kg units, multiply lift coefficient, CL, to
:0.453592/(0.3048^2)
to convert it to feet/lbs; same with drag, CD. As of pitch, CM, since it multiplies at chord in calculations, and goes with inversion, conversion coefficient is
:-0.453592/0.3048

Then look at presented graphs. Since it was said at manual that effects of both wing going trough body and wing starting a bit offside it are unknown, I made two models - one with wing going trough, and one with wing starting offside, then compared results of these two with Datcom results.

Seems to be that lift coefficient is better with wing going trough at smaller absolute alphas values; angles near to critical angle of attack is better with wing starting offside. With negative critical angle it's some median between two variants. Resulting integral CL, combining two initial variants that way, is quite near to Datcom results.

For both CD and CM, drag and moment, variant without holes is better. Drag at zero alpha is too small anyway, set it to half of CD at 5deg manually.

== Step seventh: Higher Machs ==

[[File:Datcom Cd Mach Correction.jpg|thumb|Datcom made drag coefficient due to Mach number correction]]

Unfortunately, current version of XFLR5 seems to not care about speed at all. It produces quite same results at VLM2 method for 100m/s and 200m/s. Panel method, which You could set at "Define Analysis (Advance Users)" - don't forget to switch default "Viscous" option off, as it makes errors instead of values - seems to produce a bit different results, but, again, these are not changing with velocity.

So I made next rough approximation, taken from Datcom data analysis: up to 1Mach CL is more or less same, then it starts to drop, and goes to half of initial values at 2.5Mach. Same with CM. As of drag, it drops to 0.9 to 0.9Mach, jumps to 1.5 at 1.1Mach, and drops to 1 to 2.5Mach.

It's quite rough; anyway, just to add additional tables to functions of coefficients, as at this example, and it would make difference with Datcom model not so notable.

<nowiki><table></nowiki>
<independentVar lookup="row">velocities/mach</independentVar>
<tableData>
0.3000 1.0000
0.4000 1.0112
0.5000 1.0112
0.9000 0.9888
1.1000 0.9775
1.5000 0.8315
2.0000 0.6404
2.5000 0.5281
</tableData>
<nowiki></table></nowiki>

== Step eight: Controlled surfaces ==

[[File:XFLR5 Standalone Elevator.jpg|thumb|XFLR5 Su-15 cut rotated elevator variant]]
[[File:XFLR5 Elevator Cl to Cm.jpg|thumb|XFLR5 elevator moment coefficient converted from elevator lift coefficient]]

Again, it's a bit tricky, since method seems to be not so accurate at moments. At first, You need to calculate change of lift coefficient due to surface shift - of aileron, or, as at example, of fully rotated elevator.

I set internal offsets of it to put axle at zero, then external to make it stay at correct position, then just set its "Tilt Angle" to needed values to rotate it. Secondly, You need to multiply result at distance_from_axle_to_center_of_mass/wing_chord, or some span if that was set as multiplier of that coefficient at xml file. At least on resulted graphs difference at CM caused by elevator shift was lower than CM itself, while CM calculated of CL was greater at needed angles, and model with that variant is controllable, while with pure CM - not.

== Step nine: Experiments ==

As I saw at web, some people do not import some body into XFLR5, but do define it as thick profile at core part of wing. Seems to be that approach produces more or less correct results too. You may try it, while I prefer to make conclusions instead.

== Resume ==

Easy and fast tool for beginners. If You made Your first JSBSim model, especially subsonic one, and do want to step further from initial [[Aeromatic]] made coefficients, that's what You need exactly. But, making better picture, it calculates more, say, scientific results than Datcom, and some additional steps are needed to make output of it more or less exact with subsonics; at oversonics I went 2.5Mach without reheat at resulted "Su-15" model. Though it was not made for this at all, and would evolve, but at now I would recommend some other approaches to mature developers.

== External links ==
[http://www.xflr5.com/xflr5.htm XFLR5]

[https://sourceforge.net/projects/xflr5/files/Guidelines.pdf/download XFLR5 manual]

[http://autopsi.info/Su-15/Su-15-XFLR5-Tests.zip Su-15 XFLR5 Pack], including Blender export script, .ac, .txt, and .xfl examples

== Author ==

Victor Slavutinsky, vitosnet at mail dot ru

[[Category:Aerodynamic Tools]]

XFLR5

2016-10-23T22:50:48Z

Vitos: /* Resume */

<br />
== Polishing FDM with XFLR5 ==

My next attempt to make aerodynamics of [[Su-15]] model realistic more was with [http://www.xflr5.com/xflr5.htm XFLR5]. That Open Source program is included at most of Linux distributions, to install it is not so big deal, and some of developers used it already. Again, let's go calculation process step by step to figure out what it can do.

== First step: Defining profiles ==

Most easy way is to define profiles of surefaces manually, at "File/Direct Foil Design".

[[File:XFLR5 Profiles.jpg|thumb|XFLR5 wing profiles edit window]]

First clone it from default one, then name it, then adjust common thickness by "Scale Camber and Thickness" dropdown menu. Then look at points of profile at "Edit Foil Coordinates". Don't edit these manually, but compare thickness of profile at 0.1 of chord at XFLR5 and Blender, or where You have it, and then use "Set L.E. Radius" to adjust thickness of beginning of wing.

At now program does not allow to import profile points, it can export it only. Anyway, by experience, to achieve needed result is question of minutes. Note that if You mean some flaps or rudder calculations then You need to create profile with turned flap also here, and then to make additional one, with false flap, beginning at same place, but rotated at zero angle - that one will be used for better exactness of calculations later.

At my Fedora with Cinnamon, latest XFLR5 sometimes stops to react at mouse with additional popup windows. So, maybe, knowing of some Tab/Shift-Tab and Space/Esc keyboard magic would be useful to You.

== Second step: Defining surfaces ==

Save project and switch to "Wing and Plane Design". You would want to set metrics at "Options/Units" to feets and lbs prior, as JSBSim uses these - I did not do that, since my initial model was at meters, but preferred to recalculate output later at Libre Office Calc.

So, use "Plane/Define New Plane". Here You go to "Main Wing/Define".

[[File:XFLR5 WIng Profile.jpg|thumb|XFLR5 Su-15 wing model]]
[[File:XFLR5 Elevator.jpg|thumb|XFLR5 Su-15 model solid elevator variant]]

Look at presented screen to figure out what to do. You may notice next things, actually taken ideologically from program manual:

* Wing starts at zero point.
* It has six parts, two for root with false flap, two for aileron, with flap, and two for tip, with false flap. Second ones at all cases have 1 panel at Y - that way program comprehends structure and can calculate effects of flap-nonflap surfaces joint.
* Each pat is defined by things as chord at X, distance from zero axle at Y, offset and so.
* Number of panels is not so big, 8x8 at greater case - by experience I do know that greater takes much more time but don't affect results much.

Save anything and then set wing offsets at main edit window.

Then You do define elevator.

Note that same distributions are set at screen, length and number of panels at Y axis are just same for root part of thing and elevator. That is highly recommended by manual; if length of elevator at Your model is not that same as distance to aileron of wing at Y, and with other similar cases, divide both wing and elevator accordingly, to make it fit panel to panel at Y axis.

Save result, set offsets, then set tail at fin edit window.

== Step third: Defining body ==

[[File:XFLR5 Body.jpg|thumb|XFLR5 body edit window]]

You can use XFLR5 as primitive 3D editor and define body spline by spline. As I already had other one, I preferred other way, and made a Blender exporter plugin. So, make body as half of cylinder at Blender, with 0..positive y's, divided up to ~30 cuts at Y and Z, starting with cone and ending with cone, export it from Blender and import it with "Other/Import Body Definition from text file" at body edition window. Quite easy.

== Step fourth: Defining plane inertia ==

[[File:XFLR5 Inertia.jpg|thumb|XFLR5 inertia edit window]]

Just a bit tricky, and You can omit that step, defining weight and Center of Mass position at analysis window directly instead - if You do know it. I did, anyway, that option was tested.

I knew more or less exact weights of wing, tail, elevator and empty body from documentation, and set these at "Plane Inertia" window. Then I set additional weights to body - two engines at its positions, as I did knew exact weight of engine also.

And then, since I knew point where Center of Mass got to be, I took one tonne from weight of body and defined additional mass there, then shifted it to nose until Center of Mass went to needed position - seems to be that Su have really heavy radar there. At Your case You could do same, knowing that Center of Mass could not be after main gears, and should be at ~third of median chord of wing.

That's it. If You need some Ixx or so then You can take it from here and, if Your XFLR5 model was made at ft/lbs units, put these values directly at needed place of JSBSim FDM xml model file; at case it was made in meters and kilograms, multiply it with 0.453592 prior.

Also, I would add, better to make such calculations with plane defined a bit other way, with surfaces starts not at zero point inside fuselage, but a bit off it, as at one of examples presented with pack below. Then inertia moments are correct more.

== Step fifth: Calculation ==

OK, everything is set.

[[File:XFLR5 Model Aileron Rudder.jpg|thumb|XFLR5 Su-15 model with ailerons and rudder shifted]]

Open "Analysis/Define an Analysis", choose "Type 1 (Fixed Speed)", with speed of 100m/s at first panel, "Ring Vortex (VLM2)" without other options at second - again, some Ctrl-Tab magic could be useful. Do not use "Viscous" and "Tilt. Geom" options - as I can remember, one of these produces wrong values, while other is error making.

Set name for analysis, press OK, then select it above main window. At side panel set alpha angles, from -45deg to 45 for example, with step of 5deg, and press "Analyze" button. At my old PC it calculated such case for some minutes - two maybe, not more than five for sure.

== Step sixth: Data mining ==

Go to "Polars/Current Polar/Export" and export results to text file. Open it at gedit and change multiply spaces to one by Ctrl-H, " " to " ". Then copy text and paste it to Calc.

[[File:XFLR5 Cl.jpg|thumb|XFLR5 and Datcom lift coefficient comparison]]
[[File:XFLR5 Cd.jpg|thumb|XFLR5 and Datcom drag coefficient comparison]]
[[File:XFLR5 Cm.jpg|thumb|XFLR5 and Datcom pitch moment coefficient comparison]]

First of all, if You calculated at m/kg units, multiply lift coefficient, CL, to
:0.453592/(0.3048^2)
to convert it to feet/lbs; same with drag, CD. As of pitch, CM, since it multiplies at chord in calculations, and goes with inversion, conversion coefficient is
:-0.453592/0.3048

Then look at presented graphs. Since it was said at manual that effects of both wing going trough body and wing starting a bit offside it are unknown, I made two models - one with wing going trough, and one with wing starting offside, then compared results of these two with Datcom results.

Seems to be that lift coefficient is better with wing going trough at smaller absolute alphas values; angles near to critical angle of attack is better with wing starting offside. With negative critical angle it's some median between two variants. Resulting integral CL, combining two initial variants that way, is quite near to Datcom results.

For both CD and CM, drag and moment, variant without holes is better. Drag at zero alpha is too small anyway, set it to half of CD at 5deg manually.

== Step seventh: Higher Machs ==

[[File:Datcom Cd Mach Correction.jpg|thumb|Datcom made drag coefficient due to Mach number correction]]

Unfortunately, current version of XFLR5 seems to not care about speed at all. It produces quite same results at VLM2 method for 100m/s and 200m/s. Panel method, which You could set at "Define Analysis (Advance Users)" - don't forget to switch default "Viscous" option off, as it makes errors instead of values - seems to produce a bit different results, but, again, these are not changing with velocity.

So I made next rough approximation, taken from Datcom data analysis: up to 1Mach CL is more or less same, then it starts to drop, and goes to half of initial values at 2.5Mach. Same with CM. As of drag, it drops to 0.9 to 0.9Mach, jumps to 1.5 at 1.1Mach, and drops to 1 to 2.5Mach.

It's quite rough; anyway, just to add additional tables to functions of coefficients, as at this example, and it would make difference with Datcom model not so notable.

<nowiki><table></nowiki>
<independentVar lookup="row">velocities/mach</independentVar>
<tableData>
0.3000 1.0000
0.4000 1.0112
0.5000 1.0112
0.9000 0.9888
1.1000 0.9775
1.5000 0.8315
2.0000 0.6404
2.5000 0.5281
</tableData>
<nowiki></table></nowiki>

== Step eight: Controlled surfaces ==

[[File:XFLR5 Standalone Elevator.jpg|thumb|XFLR5 Su-15 cut rotated elevator variant]]
[[File:XFLR5 Elevator Cl to Cm.jpg|thumb|XFLR5 elevator moment coefficient converted from elevator lift coefficient]]

Again, it's a bit tricky, since method seems to be not so accurate at moments. At first, You need to calculate change of lift coefficient due to surface shift - of aileron, or, as at example, of fully rotated elevator.

I set internal offsets of it to put axle at zero, then external to make it stay at correct position, then just set its "Tilt Angle" to needed values to rotate it. Secondly, You need to multiply result at distance_from_axle_to_center_of_mass/wing_chord, or some span if that was set as multiplier of that coefficient at xml file. At least on resulted graphs difference at CM caused by elevator shift was lower than CM itself, while CM calculated of CL was greater at needed angles, and model with that variant is controllable, while with pure CM - not.

== Step nine: Experiments ==

As I saw at web, some people do not import some body into XFLR5, but do define it as thick profile at core part of wing. Seems to be that approach produces more or less exact results too. You may try it, while I prefer to make conclusions instead.

== Resume ==

Easy and fast tool for beginners. If You made Your first JSBSim model, especially subsonic one, and do want to step further from initial [[Aeromatic]] made coefficients, that's what You need exactly. But, making better picture, it calculates more, say, scientific results than Datcom, and some additional steps are needed to make output of it more or less exact with subsonics; at oversonics I went 2.5Mach without reheat at resulted "Su-15" model. Though it was not made for this at all, and would evolve, but at now I would recommend some other approaches to mature developers.

== External links ==
[http://www.xflr5.com/xflr5.htm XFLR5]

[https://sourceforge.net/projects/xflr5/files/Guidelines.pdf/download XFLR5 manual]

[http://autopsi.info/Su-15/Su-15-XFLR5-Tests.zip Su-15 XFLR5 Pack], including Blender export script, .ac, .txt, and .xfl examples

== Author ==

Victor Slavutinsky, vitosnet at mail dot ru

[[Category:Aerodynamic Tools]]

XFLR5

2016-10-23T22:46:08Z

Vitos: /* Step seventh: Higher Machs */

<br />
== Polishing FDM with XFLR5 ==

My next attempt to make aerodynamics of [[Su-15]] model realistic more was with [http://www.xflr5.com/xflr5.htm XFLR5]. That Open Source program is included at most of Linux distributions, to install it is not so big deal, and some of developers used it already. Again, let's go calculation process step by step to figure out what it can do.

== First step: Defining profiles ==

Most easy way is to define profiles of surefaces manually, at "File/Direct Foil Design".

[[File:XFLR5 Profiles.jpg|thumb|XFLR5 wing profiles edit window]]

First clone it from default one, then name it, then adjust common thickness by "Scale Camber and Thickness" dropdown menu. Then look at points of profile at "Edit Foil Coordinates". Don't edit these manually, but compare thickness of profile at 0.1 of chord at XFLR5 and Blender, or where You have it, and then use "Set L.E. Radius" to adjust thickness of beginning of wing.

At now program does not allow to import profile points, it can export it only. Anyway, by experience, to achieve needed result is question of minutes. Note that if You mean some flaps or rudder calculations then You need to create profile with turned flap also here, and then to make additional one, with false flap, beginning at same place, but rotated at zero angle - that one will be used for better exactness of calculations later.

At my Fedora with Cinnamon, latest XFLR5 sometimes stops to react at mouse with additional popup windows. So, maybe, knowing of some Tab/Shift-Tab and Space/Esc keyboard magic would be useful to You.

== Second step: Defining surfaces ==

Save project and switch to "Wing and Plane Design". You would want to set metrics at "Options/Units" to feets and lbs prior, as JSBSim uses these - I did not do that, since my initial model was at meters, but preferred to recalculate output later at Libre Office Calc.

So, use "Plane/Define New Plane". Here You go to "Main Wing/Define".

[[File:XFLR5 WIng Profile.jpg|thumb|XFLR5 Su-15 wing model]]
[[File:XFLR5 Elevator.jpg|thumb|XFLR5 Su-15 model solid elevator variant]]

Look at presented screen to figure out what to do. You may notice next things, actually taken ideologically from program manual:

* Wing starts at zero point.
* It has six parts, two for root with false flap, two for aileron, with flap, and two for tip, with false flap. Second ones at all cases have 1 panel at Y - that way program comprehends structure and can calculate effects of flap-nonflap surfaces joint.
* Each pat is defined by things as chord at X, distance from zero axle at Y, offset and so.
* Number of panels is not so big, 8x8 at greater case - by experience I do know that greater takes much more time but don't affect results much.

Save anything and then set wing offsets at main edit window.

Then You do define elevator.

Note that same distributions are set at screen, length and number of panels at Y axis are just same for root part of thing and elevator. That is highly recommended by manual; if length of elevator at Your model is not that same as distance to aileron of wing at Y, and with other similar cases, divide both wing and elevator accordingly, to make it fit panel to panel at Y axis.

Save result, set offsets, then set tail at fin edit window.

== Step third: Defining body ==

[[File:XFLR5 Body.jpg|thumb|XFLR5 body edit window]]

You can use XFLR5 as primitive 3D editor and define body spline by spline. As I already had other one, I preferred other way, and made a Blender exporter plugin. So, make body as half of cylinder at Blender, with 0..positive y's, divided up to ~30 cuts at Y and Z, starting with cone and ending with cone, export it from Blender and import it with "Other/Import Body Definition from text file" at body edition window. Quite easy.

== Step fourth: Defining plane inertia ==

[[File:XFLR5 Inertia.jpg|thumb|XFLR5 inertia edit window]]

Just a bit tricky, and You can omit that step, defining weight and Center of Mass position at analysis window directly instead - if You do know it. I did, anyway, that option was tested.

I knew more or less exact weights of wing, tail, elevator and empty body from documentation, and set these at "Plane Inertia" window. Then I set additional weights to body - two engines at its positions, as I did knew exact weight of engine also.

And then, since I knew point where Center of Mass got to be, I took one tonne from weight of body and defined additional mass there, then shifted it to nose until Center of Mass went to needed position - seems to be that Su have really heavy radar there. At Your case You could do same, knowing that Center of Mass could not be after main gears, and should be at ~third of median chord of wing.

That's it. If You need some Ixx or so then You can take it from here and, if Your XFLR5 model was made at ft/lbs units, put these values directly at needed place of JSBSim FDM xml model file; at case it was made in meters and kilograms, multiply it with 0.453592 prior.

Also, I would add, better to make such calculations with plane defined a bit other way, with surfaces starts not at zero point inside fuselage, but a bit off it, as at one of examples presented with pack below. Then inertia moments are correct more.

== Step fifth: Calculation ==

OK, everything is set.

[[File:XFLR5 Model Aileron Rudder.jpg|thumb|XFLR5 Su-15 model with ailerons and rudder shifted]]

Open "Analysis/Define an Analysis", choose "Type 1 (Fixed Speed)", with speed of 100m/s at first panel, "Ring Vortex (VLM2)" without other options at second - again, some Ctrl-Tab magic could be useful. Do not use "Viscous" and "Tilt. Geom" options - as I can remember, one of these produces wrong values, while other is error making.

Set name for analysis, press OK, then select it above main window. At side panel set alpha angles, from -45deg to 45 for example, with step of 5deg, and press "Analyze" button. At my old PC it calculated such case for some minutes - two maybe, not more than five for sure.

== Step sixth: Data mining ==

Go to "Polars/Current Polar/Export" and export results to text file. Open it at gedit and change multiply spaces to one by Ctrl-H, " " to " ". Then copy text and paste it to Calc.

[[File:XFLR5 Cl.jpg|thumb|XFLR5 and Datcom lift coefficient comparison]]
[[File:XFLR5 Cd.jpg|thumb|XFLR5 and Datcom drag coefficient comparison]]
[[File:XFLR5 Cm.jpg|thumb|XFLR5 and Datcom pitch moment coefficient comparison]]

First of all, if You calculated at m/kg units, multiply lift coefficient, CL, to
:0.453592/(0.3048^2)
to convert it to feet/lbs; same with drag, CD. As of pitch, CM, since it multiplies at chord in calculations, and goes with inversion, conversion coefficient is
:-0.453592/0.3048

Then look at presented graphs. Since it was said at manual that effects of both wing going trough body and wing starting a bit offside it are unknown, I made two models - one with wing going trough, and one with wing starting offside, then compared results of these two with Datcom results.

Seems to be that lift coefficient is better with wing going trough at smaller absolute alphas values; angles near to critical angle of attack is better with wing starting offside. With negative critical angle it's some median between two variants. Resulting integral CL, combining two initial variants that way, is quite near to Datcom results.

For both CD and CM, drag and moment, variant without holes is better. Drag at zero alpha is too small anyway, set it to half of CD at 5deg manually.

== Step seventh: Higher Machs ==

[[File:Datcom Cd Mach Correction.jpg|thumb|Datcom made drag coefficient due to Mach number correction]]

Unfortunately, current version of XFLR5 seems to not care about speed at all. It produces quite same results at VLM2 method for 100m/s and 200m/s. Panel method, which You could set at "Define Analysis (Advance Users)" - don't forget to switch default "Viscous" option off, as it makes errors instead of values - seems to produce a bit different results, but, again, these are not changing with velocity.

So I made next rough approximation, taken from Datcom data analysis: up to 1Mach CL is more or less same, then it starts to drop, and goes to half of initial values at 2.5Mach. Same with CM. As of drag, it drops to 0.9 to 0.9Mach, jumps to 1.5 at 1.1Mach, and drops to 1 to 2.5Mach.

It's quite rough; anyway, just to add additional tables to functions of coefficients, as at this example, and it would make difference with Datcom model not so notable.

<nowiki><table></nowiki>
<independentVar lookup="row">velocities/mach</independentVar>
<tableData>
0.3000 1.0000
0.4000 1.0112
0.5000 1.0112
0.9000 0.9888
1.1000 0.9775
1.5000 0.8315
2.0000 0.6404
2.5000 0.5281
</tableData>
<nowiki></table></nowiki>

== Step eight: Controlled surfaces ==

[[File:XFLR5 Standalone Elevator.jpg|thumb|XFLR5 Su-15 cut rotated elevator variant]]
[[File:XFLR5 Elevator Cl to Cm.jpg|thumb|XFLR5 elevator moment coefficient converted from elevator lift coefficient]]

Again, it's a bit tricky, since method seems to be not so accurate at moments. At first, You need to calculate change of lift coefficient due to surface shift - of aileron, or, as at example, of fully rotated elevator.

I set internal offsets of it to put axle at zero, then external to make it stay at correct position, then just set its "Tilt Angle" to needed values to rotate it. Secondly, You need to multiply result at distance_from_axle_to_center_of_mass/wing_chord, or some span if that was set as multiplier of that coefficient at xml file. At least on resulted graphs difference at CM caused by elevator shift was lower than CM itself, while CM calculated of CL was greater at needed angles, and model with that variant is controllable, while with pure CM - not.

== Step nine: Experiments ==

As I saw at web, some people do not import some body into XFLR5, but do define it as thick profile at core part of wing. Seems to be that approach produces more or less exact results too. You may try it, while I prefer to make conclusions instead.

== Resume ==

Easy and fast tool for beginners. If You made Your first JSBSim model, especially subsonic one, and do want to step further from initial [[Aeromatic]] made coefficients, that's what You need exactly. But, making better picture, it calculates more, say, scientific results than Datcom, and some additional steps are needed to make it more or less exact with subsonics; at oversonics I went 2.5Mach without reheat at resulted "Su-15" model. Though it was not made for this at all, and would evolve, but at now I would recommend some other approaches to mature developers.

== External links ==
[http://www.xflr5.com/xflr5.htm XFLR5]

[https://sourceforge.net/projects/xflr5/files/Guidelines.pdf/download XFLR5 manual]

[http://autopsi.info/Su-15/Su-15-XFLR5-Tests.zip Su-15 XFLR5 Pack], including Blender export script, .ac, .txt, and .xfl examples

== Author ==

Victor Slavutinsky, vitosnet at mail dot ru

[[Category:Aerodynamic Tools]]

XFLR5

2016-10-23T22:39:57Z

Vitos: /* Step seventh: Higher Machs */

<br />
== Polishing FDM with XFLR5 ==

My next attempt to make aerodynamics of [[Su-15]] model realistic more was with [http://www.xflr5.com/xflr5.htm XFLR5]. That Open Source program is included at most of Linux distributions, to install it is not so big deal, and some of developers used it already. Again, let's go calculation process step by step to figure out what it can do.

== First step: Defining profiles ==

Most easy way is to define profiles of surefaces manually, at "File/Direct Foil Design".

[[File:XFLR5 Profiles.jpg|thumb|XFLR5 wing profiles edit window]]

First clone it from default one, then name it, then adjust common thickness by "Scale Camber and Thickness" dropdown menu. Then look at points of profile at "Edit Foil Coordinates". Don't edit these manually, but compare thickness of profile at 0.1 of chord at XFLR5 and Blender, or where You have it, and then use "Set L.E. Radius" to adjust thickness of beginning of wing.

At now program does not allow to import profile points, it can export it only. Anyway, by experience, to achieve needed result is question of minutes. Note that if You mean some flaps or rudder calculations then You need to create profile with turned flap also here, and then to make additional one, with false flap, beginning at same place, but rotated at zero angle - that one will be used for better exactness of calculations later.

At my Fedora with Cinnamon, latest XFLR5 sometimes stops to react at mouse with additional popup windows. So, maybe, knowing of some Tab/Shift-Tab and Space/Esc keyboard magic would be useful to You.

== Second step: Defining surfaces ==

Save project and switch to "Wing and Plane Design". You would want to set metrics at "Options/Units" to feets and lbs prior, as JSBSim uses these - I did not do that, since my initial model was at meters, but preferred to recalculate output later at Libre Office Calc.

So, use "Plane/Define New Plane". Here You go to "Main Wing/Define".

[[File:XFLR5 WIng Profile.jpg|thumb|XFLR5 Su-15 wing model]]
[[File:XFLR5 Elevator.jpg|thumb|XFLR5 Su-15 model solid elevator variant]]

Look at presented screen to figure out what to do. You may notice next things, actually taken ideologically from program manual:

* Wing starts at zero point.
* It has six parts, two for root with false flap, two for aileron, with flap, and two for tip, with false flap. Second ones at all cases have 1 panel at Y - that way program comprehends structure and can calculate effects of flap-nonflap surfaces joint.
* Each pat is defined by things as chord at X, distance from zero axle at Y, offset and so.
* Number of panels is not so big, 8x8 at greater case - by experience I do know that greater takes much more time but don't affect results much.

Save anything and then set wing offsets at main edit window.

Then You do define elevator.

Note that same distributions are set at screen, length and number of panels at Y axis are just same for root part of thing and elevator. That is highly recommended by manual; if length of elevator at Your model is not that same as distance to aileron of wing at Y, and with other similar cases, divide both wing and elevator accordingly, to make it fit panel to panel at Y axis.

Save result, set offsets, then set tail at fin edit window.

== Step third: Defining body ==

[[File:XFLR5 Body.jpg|thumb|XFLR5 body edit window]]

You can use XFLR5 as primitive 3D editor and define body spline by spline. As I already had other one, I preferred other way, and made a Blender exporter plugin. So, make body as half of cylinder at Blender, with 0..positive y's, divided up to ~30 cuts at Y and Z, starting with cone and ending with cone, export it from Blender and import it with "Other/Import Body Definition from text file" at body edition window. Quite easy.

== Step fourth: Defining plane inertia ==

[[File:XFLR5 Inertia.jpg|thumb|XFLR5 inertia edit window]]

Just a bit tricky, and You can omit that step, defining weight and Center of Mass position at analysis window directly instead - if You do know it. I did, anyway, that option was tested.

I knew more or less exact weights of wing, tail, elevator and empty body from documentation, and set these at "Plane Inertia" window. Then I set additional weights to body - two engines at its positions, as I did knew exact weight of engine also.

And then, since I knew point where Center of Mass got to be, I took one tonne from weight of body and defined additional mass there, then shifted it to nose until Center of Mass went to needed position - seems to be that Su have really heavy radar there. At Your case You could do same, knowing that Center of Mass could not be after main gears, and should be at ~third of median chord of wing.

That's it. If You need some Ixx or so then You can take it from here and, if Your XFLR5 model was made at ft/lbs units, put these values directly at needed place of JSBSim FDM xml model file; at case it was made in meters and kilograms, multiply it with 0.453592 prior.

Also, I would add, better to make such calculations with plane defined a bit other way, with surfaces starts not at zero point inside fuselage, but a bit off it, as at one of examples presented with pack below. Then inertia moments are correct more.

== Step fifth: Calculation ==

OK, everything is set.

[[File:XFLR5 Model Aileron Rudder.jpg|thumb|XFLR5 Su-15 model with ailerons and rudder shifted]]

Open "Analysis/Define an Analysis", choose "Type 1 (Fixed Speed)", with speed of 100m/s at first panel, "Ring Vortex (VLM2)" without other options at second - again, some Ctrl-Tab magic could be useful. Do not use "Viscous" and "Tilt. Geom" options - as I can remember, one of these produces wrong values, while other is error making.

Set name for analysis, press OK, then select it above main window. At side panel set alpha angles, from -45deg to 45 for example, with step of 5deg, and press "Analyze" button. At my old PC it calculated such case for some minutes - two maybe, not more than five for sure.

== Step sixth: Data mining ==

Go to "Polars/Current Polar/Export" and export results to text file. Open it at gedit and change multiply spaces to one by Ctrl-H, " " to " ". Then copy text and paste it to Calc.

[[File:XFLR5 Cl.jpg|thumb|XFLR5 and Datcom lift coefficient comparison]]
[[File:XFLR5 Cd.jpg|thumb|XFLR5 and Datcom drag coefficient comparison]]
[[File:XFLR5 Cm.jpg|thumb|XFLR5 and Datcom pitch moment coefficient comparison]]

First of all, if You calculated at m/kg units, multiply lift coefficient, CL, to
:0.453592/(0.3048^2)
to convert it to feet/lbs; same with drag, CD. As of pitch, CM, since it multiplies at chord in calculations, and goes with inversion, conversion coefficient is
:-0.453592/0.3048

Then look at presented graphs. Since it was said at manual that effects of both wing going trough body and wing starting a bit offside it are unknown, I made two models - one with wing going trough, and one with wing starting offside, then compared results of these two with Datcom results.

Seems to be that lift coefficient is better with wing going trough at smaller absolute alphas values; angles near to critical angle of attack is better with wing starting offside. With negative critical angle it's some median between two variants. Resulting integral CL, combining two initial variants that way, is quite near to Datcom results.

For both CD and CM, drag and moment, variant without holes is better. Drag at zero alpha is too small anyway, set it to half of CD at 5deg manually.

== Step seventh: Higher Machs ==

Unfortunately, current version of XFLR5 seems to not care about speed at all. It produces quite same results at VLM2 method for 100m/s and 200m/s. Panel method, which You could set at "Define Analysis (Advance Users)" - don't forget to switch default "Viscous" option off, as it makes errors instead of values - seems to produce a bit different results, but, again, these are not changing with velocity.

So I made next rough approximation, taken from Datcom data analysis: up to 1Mach CL is more or less same, then it starts to drop, and goes to half of initial values at 2.5Mach. Same with CM. As of drag, it drops to 0.9 to 0.9Mach, jumps to 1.5 at 1.1Mach, and drops to 1 to 2.5Mach.

It's quite rough; anyway, just to add additional tables to functions of coefficients, as at this example, and it would make difference with Datcom model not so notable.

<nowiki><table></nowiki>
<independentVar lookup="row">velocities/mach</independentVar>
<tableData>
0.3000 1.0000
0.4000 1.0112
0.5000 1.0112
0.9000 0.9888
1.1000 0.9775
1.5000 0.8315
2.0000 0.6404
2.5000 0.5281
</tableData>
<nowiki></table></nowiki>

== Step eight: Controlled surfaces ==

[[File:XFLR5 Standalone Elevator.jpg|thumb|XFLR5 Su-15 cut rotated elevator variant]]
[[File:XFLR5 Elevator Cl to Cm.jpg|thumb|XFLR5 elevator moment coefficient converted from elevator lift coefficient]]

Again, it's a bit tricky, since method seems to be not so accurate at moments. At first, You need to calculate change of lift coefficient due to surface shift - of aileron, or, as at example, of fully rotated elevator.

I set internal offsets of it to put axle at zero, then external to make it stay at correct position, then just set its "Tilt Angle" to needed values to rotate it. Secondly, You need to multiply result at distance_from_axle_to_center_of_mass/wing_chord, or some span if that was set as multiplier of that coefficient at xml file. At least on resulted graphs difference at CM caused by elevator shift was lower than CM itself, while CM calculated of CL was greater at needed angles, and model with that variant is controllable, while with pure CM - not.

== Step nine: Experiments ==

As I saw at web, some people do not import some body into XFLR5, but do define it as thick profile at core part of wing. Seems to be that approach produces more or less exact results too. You may try it, while I prefer to make conclusions instead.

== Resume ==

Easy and fast tool for beginners. If You made Your first JSBSim model, especially subsonic one, and do want to step further from initial [[Aeromatic]] made coefficients, that's what You need exactly. But, making better picture, it calculates more, say, scientific results than Datcom, and some additional steps are needed to make it more or less exact with subsonics; at oversonics I went 2.5Mach without reheat at resulted "Su-15" model. Though it was not made for this at all, and would evolve, but at now I would recommend some other approaches to mature developers.

== External links ==
[http://www.xflr5.com/xflr5.htm XFLR5]

[https://sourceforge.net/projects/xflr5/files/Guidelines.pdf/download XFLR5 manual]

[http://autopsi.info/Su-15/Su-15-XFLR5-Tests.zip Su-15 XFLR5 Pack], including Blender export script, .ac, .txt, and .xfl examples

== Author ==

Victor Slavutinsky, vitosnet at mail dot ru

[[Category:Aerodynamic Tools]]

XFLR5

2016-10-23T22:38:30Z

Vitos: /* Step sixth: Data mining */

<br />
== Polishing FDM with XFLR5 ==

My next attempt to make aerodynamics of [[Su-15]] model realistic more was with [http://www.xflr5.com/xflr5.htm XFLR5]. That Open Source program is included at most of Linux distributions, to install it is not so big deal, and some of developers used it already. Again, let's go calculation process step by step to figure out what it can do.

== First step: Defining profiles ==

Most easy way is to define profiles of surefaces manually, at "File/Direct Foil Design".

[[File:XFLR5 Profiles.jpg|thumb|XFLR5 wing profiles edit window]]

First clone it from default one, then name it, then adjust common thickness by "Scale Camber and Thickness" dropdown menu. Then look at points of profile at "Edit Foil Coordinates". Don't edit these manually, but compare thickness of profile at 0.1 of chord at XFLR5 and Blender, or where You have it, and then use "Set L.E. Radius" to adjust thickness of beginning of wing.

At now program does not allow to import profile points, it can export it only. Anyway, by experience, to achieve needed result is question of minutes. Note that if You mean some flaps or rudder calculations then You need to create profile with turned flap also here, and then to make additional one, with false flap, beginning at same place, but rotated at zero angle - that one will be used for better exactness of calculations later.

At my Fedora with Cinnamon, latest XFLR5 sometimes stops to react at mouse with additional popup windows. So, maybe, knowing of some Tab/Shift-Tab and Space/Esc keyboard magic would be useful to You.

== Second step: Defining surfaces ==

Save project and switch to "Wing and Plane Design". You would want to set metrics at "Options/Units" to feets and lbs prior, as JSBSim uses these - I did not do that, since my initial model was at meters, but preferred to recalculate output later at Libre Office Calc.

So, use "Plane/Define New Plane". Here You go to "Main Wing/Define".

[[File:XFLR5 WIng Profile.jpg|thumb|XFLR5 Su-15 wing model]]
[[File:XFLR5 Elevator.jpg|thumb|XFLR5 Su-15 model solid elevator variant]]

Look at presented screen to figure out what to do. You may notice next things, actually taken ideologically from program manual:

* Wing starts at zero point.
* It has six parts, two for root with false flap, two for aileron, with flap, and two for tip, with false flap. Second ones at all cases have 1 panel at Y - that way program comprehends structure and can calculate effects of flap-nonflap surfaces joint.
* Each pat is defined by things as chord at X, distance from zero axle at Y, offset and so.
* Number of panels is not so big, 8x8 at greater case - by experience I do know that greater takes much more time but don't affect results much.

Save anything and then set wing offsets at main edit window.

Then You do define elevator.

Note that same distributions are set at screen, length and number of panels at Y axis are just same for root part of thing and elevator. That is highly recommended by manual; if length of elevator at Your model is not that same as distance to aileron of wing at Y, and with other similar cases, divide both wing and elevator accordingly, to make it fit panel to panel at Y axis.

Save result, set offsets, then set tail at fin edit window.

== Step third: Defining body ==

[[File:XFLR5 Body.jpg|thumb|XFLR5 body edit window]]

You can use XFLR5 as primitive 3D editor and define body spline by spline. As I already had other one, I preferred other way, and made a Blender exporter plugin. So, make body as half of cylinder at Blender, with 0..positive y's, divided up to ~30 cuts at Y and Z, starting with cone and ending with cone, export it from Blender and import it with "Other/Import Body Definition from text file" at body edition window. Quite easy.

== Step fourth: Defining plane inertia ==

[[File:XFLR5 Inertia.jpg|thumb|XFLR5 inertia edit window]]

Just a bit tricky, and You can omit that step, defining weight and Center of Mass position at analysis window directly instead - if You do know it. I did, anyway, that option was tested.

I knew more or less exact weights of wing, tail, elevator and empty body from documentation, and set these at "Plane Inertia" window. Then I set additional weights to body - two engines at its positions, as I did knew exact weight of engine also.

And then, since I knew point where Center of Mass got to be, I took one tonne from weight of body and defined additional mass there, then shifted it to nose until Center of Mass went to needed position - seems to be that Su have really heavy radar there. At Your case You could do same, knowing that Center of Mass could not be after main gears, and should be at ~third of median chord of wing.

That's it. If You need some Ixx or so then You can take it from here and, if Your XFLR5 model was made at ft/lbs units, put these values directly at needed place of JSBSim FDM xml model file; at case it was made in meters and kilograms, multiply it with 0.453592 prior.

Also, I would add, better to make such calculations with plane defined a bit other way, with surfaces starts not at zero point inside fuselage, but a bit off it, as at one of examples presented with pack below. Then inertia moments are correct more.

== Step fifth: Calculation ==

OK, everything is set.

[[File:XFLR5 Model Aileron Rudder.jpg|thumb|XFLR5 Su-15 model with ailerons and rudder shifted]]

Open "Analysis/Define an Analysis", choose "Type 1 (Fixed Speed)", with speed of 100m/s at first panel, "Ring Vortex (VLM2)" without other options at second - again, some Ctrl-Tab magic could be useful. Do not use "Viscous" and "Tilt. Geom" options - as I can remember, one of these produces wrong values, while other is error making.

Set name for analysis, press OK, then select it above main window. At side panel set alpha angles, from -45deg to 45 for example, with step of 5deg, and press "Analyze" button. At my old PC it calculated such case for some minutes - two maybe, not more than five for sure.

== Step sixth: Data mining ==

Go to "Polars/Current Polar/Export" and export results to text file. Open it at gedit and change multiply spaces to one by Ctrl-H, " " to " ". Then copy text and paste it to Calc.

[[File:XFLR5 Cl.jpg|thumb|XFLR5 and Datcom lift coefficient comparison]]
[[File:XFLR5 Cd.jpg|thumb|XFLR5 and Datcom drag coefficient comparison]]
[[File:XFLR5 Cm.jpg|thumb|XFLR5 and Datcom pitch moment coefficient comparison]]

First of all, if You calculated at m/kg units, multiply lift coefficient, CL, to
:0.453592/(0.3048^2)
to convert it to feet/lbs; same with drag, CD. As of pitch, CM, since it multiplies at chord in calculations, and goes with inversion, conversion coefficient is
:-0.453592/0.3048

Then look at presented graphs. Since it was said at manual that effects of both wing going trough body and wing starting a bit offside it are unknown, I made two models - one with wing going trough, and one with wing starting offside, then compared results of these two with Datcom results.

Seems to be that lift coefficient is better with wing going trough at smaller absolute alphas values; angles near to critical angle of attack is better with wing starting offside. With negative critical angle it's some median between two variants. Resulting integral CL, combining two initial variants that way, is quite near to Datcom results.

For both CD and CM, drag and moment, variant without holes is better. Drag at zero alpha is too small anyway, set it to half of CD at 5deg manually.

== Step seventh: Higher Machs ==

Unfortunately, current version of XFLR5 seems to not care about speed at all. It produces quite same results at VLM2 method for 100m/s and 200m/s. Panel method, which You could set at "Define Analysis (Advance Users)" - don't forget to switch default "Viscous" option off - seems to produce a bit different results, but, again, these are not changing with velocity.

So I made next rough approximation, taken from Datcom data analysis: up to 1Mach CL is more or less same, then it starts to drop, and goes to half of initial values at 2.5Mach. Same with CM. As of drag, it drops to 0.9 to 0.9Mach, jumps to 1.5 at 1.1Mach, and drops to 1 to 2.5Mach.

It's quite rough; anyway, just to add additional tables to functions of coefficients, as at this example, and it would make difference with Datcom model not so notable.

<nowiki><table></nowiki>
<independentVar lookup="row">velocities/mach</independentVar>
<tableData>
0.3000 1.0000
0.4000 1.0112
0.5000 1.0112
0.9000 0.9888
1.1000 0.9775
1.5000 0.8315
2.0000 0.6404
2.5000 0.5281
</tableData>
<nowiki></table></nowiki>

== Step eight: Controlled surfaces ==

[[File:XFLR5 Standalone Elevator.jpg|thumb|XFLR5 Su-15 cut rotated elevator variant]]
[[File:XFLR5 Elevator Cl to Cm.jpg|thumb|XFLR5 elevator moment coefficient converted from elevator lift coefficient]]

Again, it's a bit tricky, since method seems to be not so accurate at moments. At first, You need to calculate change of lift coefficient due to surface shift - of aileron, or, as at example, of fully rotated elevator.

I set internal offsets of it to put axle at zero, then external to make it stay at correct position, then just set its "Tilt Angle" to needed values to rotate it. Secondly, You need to multiply result at distance_from_axle_to_center_of_mass/wing_chord, or some span if that was set as multiplier of that coefficient at xml file. At least on resulted graphs difference at CM caused by elevator shift was lower than CM itself, while CM calculated of CL was greater at needed angles, and model with that variant is controllable, while with pure CM - not.

== Step nine: Experiments ==

As I saw at web, some people do not import some body into XFLR5, but do define it as thick profile at core part of wing. Seems to be that approach produces more or less exact results too. You may try it, while I prefer to make conclusions instead.

== Resume ==

Easy and fast tool for beginners. If You made Your first JSBSim model, especially subsonic one, and do want to step further from initial [[Aeromatic]] made coefficients, that's what You need exactly. But, making better picture, it calculates more, say, scientific results than Datcom, and some additional steps are needed to make it more or less exact with subsonics; at oversonics I went 2.5Mach without reheat at resulted "Su-15" model. Though it was not made for this at all, and would evolve, but at now I would recommend some other approaches to mature developers.

== External links ==
[http://www.xflr5.com/xflr5.htm XFLR5]

[https://sourceforge.net/projects/xflr5/files/Guidelines.pdf/download XFLR5 manual]

[http://autopsi.info/Su-15/Su-15-XFLR5-Tests.zip Su-15 XFLR5 Pack], including Blender export script, .ac, .txt, and .xfl examples

== Author ==

Victor Slavutinsky, vitosnet at mail dot ru

[[Category:Aerodynamic Tools]]

XFLR5

2016-10-23T22:37:51Z

Vitos: /* Step sixth: Data mining */

<br />
== Polishing FDM with XFLR5 ==

My next attempt to make aerodynamics of [[Su-15]] model realistic more was with [http://www.xflr5.com/xflr5.htm XFLR5]. That Open Source program is included at most of Linux distributions, to install it is not so big deal, and some of developers used it already. Again, let's go calculation process step by step to figure out what it can do.

== First step: Defining profiles ==

Most easy way is to define profiles of surefaces manually, at "File/Direct Foil Design".

[[File:XFLR5 Profiles.jpg|thumb|XFLR5 wing profiles edit window]]

First clone it from default one, then name it, then adjust common thickness by "Scale Camber and Thickness" dropdown menu. Then look at points of profile at "Edit Foil Coordinates". Don't edit these manually, but compare thickness of profile at 0.1 of chord at XFLR5 and Blender, or where You have it, and then use "Set L.E. Radius" to adjust thickness of beginning of wing.

At now program does not allow to import profile points, it can export it only. Anyway, by experience, to achieve needed result is question of minutes. Note that if You mean some flaps or rudder calculations then You need to create profile with turned flap also here, and then to make additional one, with false flap, beginning at same place, but rotated at zero angle - that one will be used for better exactness of calculations later.

At my Fedora with Cinnamon, latest XFLR5 sometimes stops to react at mouse with additional popup windows. So, maybe, knowing of some Tab/Shift-Tab and Space/Esc keyboard magic would be useful to You.

== Second step: Defining surfaces ==

Save project and switch to "Wing and Plane Design". You would want to set metrics at "Options/Units" to feets and lbs prior, as JSBSim uses these - I did not do that, since my initial model was at meters, but preferred to recalculate output later at Libre Office Calc.

So, use "Plane/Define New Plane". Here You go to "Main Wing/Define".

[[File:XFLR5 WIng Profile.jpg|thumb|XFLR5 Su-15 wing model]]
[[File:XFLR5 Elevator.jpg|thumb|XFLR5 Su-15 model solid elevator variant]]

Look at presented screen to figure out what to do. You may notice next things, actually taken ideologically from program manual:

* Wing starts at zero point.
* It has six parts, two for root with false flap, two for aileron, with flap, and two for tip, with false flap. Second ones at all cases have 1 panel at Y - that way program comprehends structure and can calculate effects of flap-nonflap surfaces joint.
* Each pat is defined by things as chord at X, distance from zero axle at Y, offset and so.
* Number of panels is not so big, 8x8 at greater case - by experience I do know that greater takes much more time but don't affect results much.

Save anything and then set wing offsets at main edit window.

Then You do define elevator.

Note that same distributions are set at screen, length and number of panels at Y axis are just same for root part of thing and elevator. That is highly recommended by manual; if length of elevator at Your model is not that same as distance to aileron of wing at Y, and with other similar cases, divide both wing and elevator accordingly, to make it fit panel to panel at Y axis.

Save result, set offsets, then set tail at fin edit window.

== Step third: Defining body ==

[[File:XFLR5 Body.jpg|thumb|XFLR5 body edit window]]

You can use XFLR5 as primitive 3D editor and define body spline by spline. As I already had other one, I preferred other way, and made a Blender exporter plugin. So, make body as half of cylinder at Blender, with 0..positive y's, divided up to ~30 cuts at Y and Z, starting with cone and ending with cone, export it from Blender and import it with "Other/Import Body Definition from text file" at body edition window. Quite easy.

== Step fourth: Defining plane inertia ==

[[File:XFLR5 Inertia.jpg|thumb|XFLR5 inertia edit window]]

Just a bit tricky, and You can omit that step, defining weight and Center of Mass position at analysis window directly instead - if You do know it. I did, anyway, that option was tested.

I knew more or less exact weights of wing, tail, elevator and empty body from documentation, and set these at "Plane Inertia" window. Then I set additional weights to body - two engines at its positions, as I did knew exact weight of engine also.

And then, since I knew point where Center of Mass got to be, I took one tonne from weight of body and defined additional mass there, then shifted it to nose until Center of Mass went to needed position - seems to be that Su have really heavy radar there. At Your case You could do same, knowing that Center of Mass could not be after main gears, and should be at ~third of median chord of wing.

That's it. If You need some Ixx or so then You can take it from here and, if Your XFLR5 model was made at ft/lbs units, put these values directly at needed place of JSBSim FDM xml model file; at case it was made in meters and kilograms, multiply it with 0.453592 prior.

Also, I would add, better to make such calculations with plane defined a bit other way, with surfaces starts not at zero point inside fuselage, but a bit off it, as at one of examples presented with pack below. Then inertia moments are correct more.

== Step fifth: Calculation ==

OK, everything is set.

[[File:XFLR5 Model Aileron Rudder.jpg|thumb|XFLR5 Su-15 model with ailerons and rudder shifted]]

Open "Analysis/Define an Analysis", choose "Type 1 (Fixed Speed)", with speed of 100m/s at first panel, "Ring Vortex (VLM2)" without other options at second - again, some Ctrl-Tab magic could be useful. Do not use "Viscous" and "Tilt. Geom" options - as I can remember, one of these produces wrong values, while other is error making.

Set name for analysis, press OK, then select it above main window. At side panel set alpha angles, from -45deg to 45 for example, with step of 5deg, and press "Analyze" button. At my old PC it calculated such case for some minutes - two maybe, not more than five for sure.

== Step sixth: Data mining ==

Go to "Polars/Current Polar/Export" and export results to text file. Open it at gedit and change multiply spaces to one by Ctrl-H, " " to " ". Then copy text and paste it to Calc.

[[File:XFLR5 Cl.jpg|thumb|XFLR5 and Datcom lift coefficient comparison]]
[[File:XFLR5 Cd.jpg|thumb|XFLR5 and Datcom drag coefficient comparison]]
[[File:XFLR5 Cm.jpg|thumb|XFLR5 and Datcom pitch moment coefficient comparison]]

First of all, if You calculated at m/kg units, multiply lift coefficient, CL, to
:0.453592/(0.3048^2)
to convert it to feet/lbs; same with drag, CD. As of pitch, CM, since it multiplies at chord in calculations, and goes with inversion, conversion coefficient is
:-0.453592/0.3048

Then look at presented graphs. Since it was said at manual that effects of both wing going trough body and wing starting a bit offside it are unknown, I calculate two models - one with wing going trough, and one with wing starting offside, then compared these two with Datcom results.

Seems to be that lift coefficient is better with wing going trough at smaller absolute alphas values; angles near to critical angle of attack is better with wing starting offside. With negative critical angle it's some median between two variants. Resulting integral CL, combining two initial variants that way, is quite near to Datcom results.

For both CD and CM, drag and moment, variant without holes is better. Drag at zero alpha is too small anyway, set it to half of CD at 5deg manually.

== Step seventh: Higher Machs ==

Unfortunately, current version of XFLR5 seems to not care about speed at all. It produces quite same results at VLM2 method for 100m/s and 200m/s. Panel method, which You could set at "Define Analysis (Advance Users)" - don't forget to switch default "Viscous" option off - seems to produce a bit different results, but, again, these are not changing with velocity.

So I made next rough approximation, taken from Datcom data analysis: up to 1Mach CL is more or less same, then it starts to drop, and goes to half of initial values at 2.5Mach. Same with CM. As of drag, it drops to 0.9 to 0.9Mach, jumps to 1.5 at 1.1Mach, and drops to 1 to 2.5Mach.

It's quite rough; anyway, just to add additional tables to functions of coefficients, as at this example, and it would make difference with Datcom model not so notable.

<nowiki><table></nowiki>
<independentVar lookup="row">velocities/mach</independentVar>
<tableData>
0.3000 1.0000
0.4000 1.0112
0.5000 1.0112
0.9000 0.9888
1.1000 0.9775
1.5000 0.8315
2.0000 0.6404
2.5000 0.5281
</tableData>
<nowiki></table></nowiki>

== Step eight: Controlled surfaces ==

[[File:XFLR5 Standalone Elevator.jpg|thumb|XFLR5 Su-15 cut rotated elevator variant]]
[[File:XFLR5 Elevator Cl to Cm.jpg|thumb|XFLR5 elevator moment coefficient converted from elevator lift coefficient]]

Again, it's a bit tricky, since method seems to be not so accurate at moments. At first, You need to calculate change of lift coefficient due to surface shift - of aileron, or, as at example, of fully rotated elevator.

I set internal offsets of it to put axle at zero, then external to make it stay at correct position, then just set its "Tilt Angle" to needed values to rotate it. Secondly, You need to multiply result at distance_from_axle_to_center_of_mass/wing_chord, or some span if that was set as multiplier of that coefficient at xml file. At least on resulted graphs difference at CM caused by elevator shift was lower than CM itself, while CM calculated of CL was greater at needed angles, and model with that variant is controllable, while with pure CM - not.

== Step nine: Experiments ==

As I saw at web, some people do not import some body into XFLR5, but do define it as thick profile at core part of wing. Seems to be that approach produces more or less exact results too. You may try it, while I prefer to make conclusions instead.

== Resume ==

Easy and fast tool for beginners. If You made Your first JSBSim model, especially subsonic one, and do want to step further from initial [[Aeromatic]] made coefficients, that's what You need exactly. But, making better picture, it calculates more, say, scientific results than Datcom, and some additional steps are needed to make it more or less exact with subsonics; at oversonics I went 2.5Mach without reheat at resulted "Su-15" model. Though it was not made for this at all, and would evolve, but at now I would recommend some other approaches to mature developers.

== External links ==
[http://www.xflr5.com/xflr5.htm XFLR5]

[https://sourceforge.net/projects/xflr5/files/Guidelines.pdf/download XFLR5 manual]

[http://autopsi.info/Su-15/Su-15-XFLR5-Tests.zip Su-15 XFLR5 Pack], including Blender export script, .ac, .txt, and .xfl examples

== Author ==

Victor Slavutinsky, vitosnet at mail dot ru

[[Category:Aerodynamic Tools]]

XFLR5

2016-10-23T22:36:21Z

Vitos: /* Step fourth: Defining plane inertia */

<br />
== Polishing FDM with XFLR5 ==

My next attempt to make aerodynamics of [[Su-15]] model realistic more was with [http://www.xflr5.com/xflr5.htm XFLR5]. That Open Source program is included at most of Linux distributions, to install it is not so big deal, and some of developers used it already. Again, let's go calculation process step by step to figure out what it can do.

== First step: Defining profiles ==

Most easy way is to define profiles of surefaces manually, at "File/Direct Foil Design".

[[File:XFLR5 Profiles.jpg|thumb|XFLR5 wing profiles edit window]]

First clone it from default one, then name it, then adjust common thickness by "Scale Camber and Thickness" dropdown menu. Then look at points of profile at "Edit Foil Coordinates". Don't edit these manually, but compare thickness of profile at 0.1 of chord at XFLR5 and Blender, or where You have it, and then use "Set L.E. Radius" to adjust thickness of beginning of wing.

At now program does not allow to import profile points, it can export it only. Anyway, by experience, to achieve needed result is question of minutes. Note that if You mean some flaps or rudder calculations then You need to create profile with turned flap also here, and then to make additional one, with false flap, beginning at same place, but rotated at zero angle - that one will be used for better exactness of calculations later.

At my Fedora with Cinnamon, latest XFLR5 sometimes stops to react at mouse with additional popup windows. So, maybe, knowing of some Tab/Shift-Tab and Space/Esc keyboard magic would be useful to You.

== Second step: Defining surfaces ==

Save project and switch to "Wing and Plane Design". You would want to set metrics at "Options/Units" to feets and lbs prior, as JSBSim uses these - I did not do that, since my initial model was at meters, but preferred to recalculate output later at Libre Office Calc.

So, use "Plane/Define New Plane". Here You go to "Main Wing/Define".

[[File:XFLR5 WIng Profile.jpg|thumb|XFLR5 Su-15 wing model]]
[[File:XFLR5 Elevator.jpg|thumb|XFLR5 Su-15 model solid elevator variant]]

Look at presented screen to figure out what to do. You may notice next things, actually taken ideologically from program manual:

* Wing starts at zero point.
* It has six parts, two for root with false flap, two for aileron, with flap, and two for tip, with false flap. Second ones at all cases have 1 panel at Y - that way program comprehends structure and can calculate effects of flap-nonflap surfaces joint.
* Each pat is defined by things as chord at X, distance from zero axle at Y, offset and so.
* Number of panels is not so big, 8x8 at greater case - by experience I do know that greater takes much more time but don't affect results much.

Save anything and then set wing offsets at main edit window.

Then You do define elevator.

Note that same distributions are set at screen, length and number of panels at Y axis are just same for root part of thing and elevator. That is highly recommended by manual; if length of elevator at Your model is not that same as distance to aileron of wing at Y, and with other similar cases, divide both wing and elevator accordingly, to make it fit panel to panel at Y axis.

Save result, set offsets, then set tail at fin edit window.

== Step third: Defining body ==

[[File:XFLR5 Body.jpg|thumb|XFLR5 body edit window]]

You can use XFLR5 as primitive 3D editor and define body spline by spline. As I already had other one, I preferred other way, and made a Blender exporter plugin. So, make body as half of cylinder at Blender, with 0..positive y's, divided up to ~30 cuts at Y and Z, starting with cone and ending with cone, export it from Blender and import it with "Other/Import Body Definition from text file" at body edition window. Quite easy.

== Step fourth: Defining plane inertia ==

[[File:XFLR5 Inertia.jpg|thumb|XFLR5 inertia edit window]]

Just a bit tricky, and You can omit that step, defining weight and Center of Mass position at analysis window directly instead - if You do know it. I did, anyway, that option was tested.

I knew more or less exact weights of wing, tail, elevator and empty body from documentation, and set these at "Plane Inertia" window. Then I set additional weights to body - two engines at its positions, as I did knew exact weight of engine also.

And then, since I knew point where Center of Mass got to be, I took one tonne from weight of body and defined additional mass there, then shifted it to nose until Center of Mass went to needed position - seems to be that Su have really heavy radar there. At Your case You could do same, knowing that Center of Mass could not be after main gears, and should be at ~third of median chord of wing.

That's it. If You need some Ixx or so then You can take it from here and, if Your XFLR5 model was made at ft/lbs units, put these values directly at needed place of JSBSim FDM xml model file; at case it was made in meters and kilograms, multiply it with 0.453592 prior.

Also, I would add, better to make such calculations with plane defined a bit other way, with surfaces starts not at zero point inside fuselage, but a bit off it, as at one of examples presented with pack below. Then inertia moments are correct more.

== Step fifth: Calculation ==

OK, everything is set.

[[File:XFLR5 Model Aileron Rudder.jpg|thumb|XFLR5 Su-15 model with ailerons and rudder shifted]]

Open "Analysis/Define an Analysis", choose "Type 1 (Fixed Speed)", with speed of 100m/s at first panel, "Ring Vortex (VLM2)" without other options at second - again, some Ctrl-Tab magic could be useful. Do not use "Viscous" and "Tilt. Geom" options - as I can remember, one of these produces wrong values, while other is error making.

Set name for analysis, press OK, then select it above main window. At side panel set alpha angles, from -45deg to 45 for example, with step of 5deg, and press "Analyze" button. At my old PC it calculated such case for some minutes - two maybe, not more than five for sure.

== Step sixth: Data mining ==

Go to "Polars/Current Polar/Export" and export results to text file. Open it at gedit and change multiply spaces to one by Ctrl-H, " " to " ". Then copy text and paste it to Calc.

[[File:XFLR5 Cl.jpg|thumb|XFLR5 and Datcom lift coefficient comparison]]
[[File:XFLR5 Cd.jpg|thumb|XFLR5 and Datcom drag coefficient comparison]]
[[File:XFLR5 Cm.jpg|thumb|XFLR5 and Datcom pitch moment coefficient comparison]]

First of all, if You calculated at m/kg units, multiply lift coefficient, CL, to
:0.453592/(0.3048^2)
to convert it to feet/lbs; same with drag CD. As of pitch CM, since it multiplies at chord in calculations, and goes with inversion, conversion coefficient is
:-0.453592/0.3048.

Then look at presented graphs. Since it was said at manual that effects of both wing going trough body and wing starting a bit offside it are unknown, I calculate two models - one with wing going trough, and one with wing starting offside, then compared these two with Datcom results.

Seems to be that lift coefficient is better with wing going trough at smaller absolute alphas values; angles near to critical angle of attack is better with wing starting offside. With negative critical angle it's some median between two variants. Resulting integral CL, combining two initial variants that way, is quite near to Datcom results.

For both CD and CM, drag and moment, variant without holes is better. Drag at zero alpha is too small anyway, set it to half of CD at 5deg manually.

== Step seventh: Higher Machs ==

Unfortunately, current version of XFLR5 seems to not care about speed at all. It produces quite same results at VLM2 method for 100m/s and 200m/s. Panel method, which You could set at "Define Analysis (Advance Users)" - don't forget to switch default "Viscous" option off - seems to produce a bit different results, but, again, these are not changing with velocity.

So I made next rough approximation, taken from Datcom data analysis: up to 1Mach CL is more or less same, then it starts to drop, and goes to half of initial values at 2.5Mach. Same with CM. As of drag, it drops to 0.9 to 0.9Mach, jumps to 1.5 at 1.1Mach, and drops to 1 to 2.5Mach.

It's quite rough; anyway, just to add additional tables to functions of coefficients, as at this example, and it would make difference with Datcom model not so notable.

<nowiki><table></nowiki>
<independentVar lookup="row">velocities/mach</independentVar>
<tableData>
0.3000 1.0000
0.4000 1.0112
0.5000 1.0112
0.9000 0.9888
1.1000 0.9775
1.5000 0.8315
2.0000 0.6404
2.5000 0.5281
</tableData>
<nowiki></table></nowiki>

== Step eight: Controlled surfaces ==

[[File:XFLR5 Standalone Elevator.jpg|thumb|XFLR5 Su-15 cut rotated elevator variant]]
[[File:XFLR5 Elevator Cl to Cm.jpg|thumb|XFLR5 elevator moment coefficient converted from elevator lift coefficient]]

Again, it's a bit tricky, since method seems to be not so accurate at moments. At first, You need to calculate change of lift coefficient due to surface shift - of aileron, or, as at example, of fully rotated elevator.

I set internal offsets of it to put axle at zero, then external to make it stay at correct position, then just set its "Tilt Angle" to needed values to rotate it. Secondly, You need to multiply result at distance_from_axle_to_center_of_mass/wing_chord, or some span if that was set as multiplier of that coefficient at xml file. At least on resulted graphs difference at CM caused by elevator shift was lower than CM itself, while CM calculated of CL was greater at needed angles, and model with that variant is controllable, while with pure CM - not.

== Step nine: Experiments ==

As I saw at web, some people do not import some body into XFLR5, but do define it as thick profile at core part of wing. Seems to be that approach produces more or less exact results too. You may try it, while I prefer to make conclusions instead.

== Resume ==

Easy and fast tool for beginners. If You made Your first JSBSim model, especially subsonic one, and do want to step further from initial [[Aeromatic]] made coefficients, that's what You need exactly. But, making better picture, it calculates more, say, scientific results than Datcom, and some additional steps are needed to make it more or less exact with subsonics; at oversonics I went 2.5Mach without reheat at resulted "Su-15" model. Though it was not made for this at all, and would evolve, but at now I would recommend some other approaches to mature developers.

== External links ==
[http://www.xflr5.com/xflr5.htm XFLR5]

[https://sourceforge.net/projects/xflr5/files/Guidelines.pdf/download XFLR5 manual]

[http://autopsi.info/Su-15/Su-15-XFLR5-Tests.zip Su-15 XFLR5 Pack], including Blender export script, .ac, .txt, and .xfl examples

== Author ==

Victor Slavutinsky, vitosnet at mail dot ru

[[Category:Aerodynamic Tools]]

XFLR5

2016-10-23T22:33:04Z

Vitos: /* Second step: Defining surfaces */

<br />
== Polishing FDM with XFLR5 ==

My next attempt to make aerodynamics of [[Su-15]] model realistic more was with [http://www.xflr5.com/xflr5.htm XFLR5]. That Open Source program is included at most of Linux distributions, to install it is not so big deal, and some of developers used it already. Again, let's go calculation process step by step to figure out what it can do.

== First step: Defining profiles ==

Most easy way is to define profiles of surefaces manually, at "File/Direct Foil Design".

[[File:XFLR5 Profiles.jpg|thumb|XFLR5 wing profiles edit window]]

First clone it from default one, then name it, then adjust common thickness by "Scale Camber and Thickness" dropdown menu. Then look at points of profile at "Edit Foil Coordinates". Don't edit these manually, but compare thickness of profile at 0.1 of chord at XFLR5 and Blender, or where You have it, and then use "Set L.E. Radius" to adjust thickness of beginning of wing.

At now program does not allow to import profile points, it can export it only. Anyway, by experience, to achieve needed result is question of minutes. Note that if You mean some flaps or rudder calculations then You need to create profile with turned flap also here, and then to make additional one, with false flap, beginning at same place, but rotated at zero angle - that one will be used for better exactness of calculations later.

At my Fedora with Cinnamon, latest XFLR5 sometimes stops to react at mouse with additional popup windows. So, maybe, knowing of some Tab/Shift-Tab and Space/Esc keyboard magic would be useful to You.

== Second step: Defining surfaces ==

Save project and switch to "Wing and Plane Design". You would want to set metrics at "Options/Units" to feets and lbs prior, as JSBSim uses these - I did not do that, since my initial model was at meters, but preferred to recalculate output later at Libre Office Calc.

So, use "Plane/Define New Plane". Here You go to "Main Wing/Define".

[[File:XFLR5 WIng Profile.jpg|thumb|XFLR5 Su-15 wing model]]
[[File:XFLR5 Elevator.jpg|thumb|XFLR5 Su-15 model solid elevator variant]]

Look at presented screen to figure out what to do. You may notice next things, actually taken ideologically from program manual:

* Wing starts at zero point.
* It has six parts, two for root with false flap, two for aileron, with flap, and two for tip, with false flap. Second ones at all cases have 1 panel at Y - that way program comprehends structure and can calculate effects of flap-nonflap surfaces joint.
* Each pat is defined by things as chord at X, distance from zero axle at Y, offset and so.
* Number of panels is not so big, 8x8 at greater case - by experience I do know that greater takes much more time but don't affect results much.

Save anything and then set wing offsets at main edit window.

Then You do define elevator.

Note that same distributions are set at screen, length and number of panels at Y axis are just same for root part of thing and elevator. That is highly recommended by manual; if length of elevator at Your model is not that same as distance to aileron of wing at Y, and with other similar cases, divide both wing and elevator accordingly, to make it fit panel to panel at Y axis.

Save result, set offsets, then set tail at fin edit window.

== Step third: Defining body ==

[[File:XFLR5 Body.jpg|thumb|XFLR5 body edit window]]

You can use XFLR5 as primitive 3D editor and define body spline by spline. As I already had other one, I preferred other way, and made a Blender exporter plugin. So, make body as half of cylinder at Blender, with 0..positive y's, divided up to ~30 cuts at Y and Z, starting with cone and ending with cone, export it from Blender and import it with "Other/Import Body Definition from text file" at body edition window. Quite easy.

== Step fourth: Defining plane inertia ==

[[File:XFLR5 Inertia.jpg|thumb|XFLR5 inertia edit window]]

Just a bit tricky, and You can omit that step, defining weight and Center of Mass position at analysis window instead - if You do know it. I did, anyway, that option was tested.

I knew more or less exact weights of wing, tail, elevator and empty body from documentation, and set these at "Plane Inertia" window. Then I set additional weights to body - two engines at its positions, as I did knew exact weight of engine also.

And then, since I knew point where CM got to be, I took one tonne from weight of body and defined additional mass there, then shifted it to nose until CM went to needed position - seems to be that Su have really heavy radar there$ at Your case You could do same, knowing that Center of Mass could not be after main gears, and should be at ~third of median chord of wing.

That's it. If You need some Ixx or so then You can take it from there and, if Your XFLR5 model was made at ft/lbs units, put these values directly at needed place of JSBSim FDM xml model file; at case it was made in meters and kilograms, multiply it with 0.453592 prior.

Also, I would add, better to make such calculations with plane defined a bit other way, with surfaces starts not at zero point inside fuselage, but a bit off it, as at one of examples presented with pack below. Then inertia moments are correct more.

== Step fifth: Calculation ==

OK, everything is set.

[[File:XFLR5 Model Aileron Rudder.jpg|thumb|XFLR5 Su-15 model with ailerons and rudder shifted]]

Open "Analysis/Define an Analysis", choose "Type 1 (Fixed Speed)", with speed of 100m/s at first panel, "Ring Vortex (VLM2)" without other options at second - again, some Ctrl-Tab magic could be useful. Do not use "Viscous" and "Tilt. Geom" options - as I can remember, one of these produces wrong values, while other is error making.

Set name for analysis, press OK, then select it above main window. At side panel set alpha angles, from -45deg to 45 for example, with step of 5deg, and press "Analyze" button. At my old PC it calculated such case for some minutes - two maybe, not more than five for sure.

== Step sixth: Data mining ==

Go to "Polars/Current Polar/Export" and export results to text file. Open it at gedit and change multiply spaces to one by Ctrl-H, " " to " ". Then copy text and paste it to Calc.

[[File:XFLR5 Cl.jpg|thumb|XFLR5 and Datcom lift coefficient comparison]]
[[File:XFLR5 Cd.jpg|thumb|XFLR5 and Datcom drag coefficient comparison]]
[[File:XFLR5 Cm.jpg|thumb|XFLR5 and Datcom pitch moment coefficient comparison]]

First of all, if You calculated at m/kg units, multiply lift coefficient, CL, to
:0.453592/(0.3048^2)
to convert it to feet/lbs; same with drag CD. As of pitch CM, since it multiplies at chord in calculations, and goes with inversion, conversion coefficient is
:-0.453592/0.3048.

Then look at presented graphs. Since it was said at manual that effects of both wing going trough body and wing starting a bit offside it are unknown, I calculate two models - one with wing going trough, and one with wing starting offside, then compared these two with Datcom results.

Seems to be that lift coefficient is better with wing going trough at smaller absolute alphas values; angles near to critical angle of attack is better with wing starting offside. With negative critical angle it's some median between two variants. Resulting integral CL, combining two initial variants that way, is quite near to Datcom results.

For both CD and CM, drag and moment, variant without holes is better. Drag at zero alpha is too small anyway, set it to half of CD at 5deg manually.

== Step seventh: Higher Machs ==

Unfortunately, current version of XFLR5 seems to not care about speed at all. It produces quite same results at VLM2 method for 100m/s and 200m/s. Panel method, which You could set at "Define Analysis (Advance Users)" - don't forget to switch default "Viscous" option off - seems to produce a bit different results, but, again, these are not changing with velocity.

So I made next rough approximation, taken from Datcom data analysis: up to 1Mach CL is more or less same, then it starts to drop, and goes to half of initial values at 2.5Mach. Same with CM. As of drag, it drops to 0.9 to 0.9Mach, jumps to 1.5 at 1.1Mach, and drops to 1 to 2.5Mach.

It's quite rough; anyway, just to add additional tables to functions of coefficients, as at this example, and it would make difference with Datcom model not so notable.

<nowiki><table></nowiki>
<independentVar lookup="row">velocities/mach</independentVar>
<tableData>
0.3000 1.0000
0.4000 1.0112
0.5000 1.0112
0.9000 0.9888
1.1000 0.9775
1.5000 0.8315
2.0000 0.6404
2.5000 0.5281
</tableData>
<nowiki></table></nowiki>

== Step eight: Controlled surfaces ==

[[File:XFLR5 Standalone Elevator.jpg|thumb|XFLR5 Su-15 cut rotated elevator variant]]
[[File:XFLR5 Elevator Cl to Cm.jpg|thumb|XFLR5 elevator moment coefficient converted from elevator lift coefficient]]

Again, it's a bit tricky, since method seems to be not so accurate at moments. At first, You need to calculate change of lift coefficient due to surface shift - of aileron, or, as at example, of fully rotated elevator.

I set internal offsets of it to put axle at zero, then external to make it stay at correct position, then just set its "Tilt Angle" to needed values to rotate it. Secondly, You need to multiply result at distance_from_axle_to_center_of_mass/wing_chord, or some span if that was set as multiplier of that coefficient at xml file. At least on resulted graphs difference at CM caused by elevator shift was lower than CM itself, while CM calculated of CL was greater at needed angles, and model with that variant is controllable, while with pure CM - not.

== Step nine: Experiments ==

As I saw at web, some people do not import some body into XFLR5, but do define it as thick profile at core part of wing. Seems to be that approach produces more or less exact results too. You may try it, while I prefer to make conclusions instead.

== Resume ==

Easy and fast tool for beginners. If You made Your first JSBSim model, especially subsonic one, and do want to step further from initial [[Aeromatic]] made coefficients, that's what You need exactly. But, making better picture, it calculates more, say, scientific results than Datcom, and some additional steps are needed to make it more or less exact with subsonics; at oversonics I went 2.5Mach without reheat at resulted "Su-15" model. Though it was not made for this at all, and would evolve, but at now I would recommend some other approaches to mature developers.

== External links ==
[http://www.xflr5.com/xflr5.htm XFLR5]

[https://sourceforge.net/projects/xflr5/files/Guidelines.pdf/download XFLR5 manual]

[http://autopsi.info/Su-15/Su-15-XFLR5-Tests.zip Su-15 XFLR5 Pack], including Blender export script, .ac, .txt, and .xfl examples

== Author ==

Victor Slavutinsky, vitosnet at mail dot ru

[[Category:Aerodynamic Tools]]