INS and Gyro Drift.

[jojo]

How to you realign the INS if the drift is over 15 miles? It is just not possible?

 

With 1Nm/h drift rate, how do you do to reach >15Nm drift ? :D

[zerO_crash]

With 1Nm/h drift rate, how do you do to reach >15Nm drift ? :D

 

1? INS updates to 2nd stage alignment, meaning 2nm/h.

[bones1014]

With 1Nm/h drift rate, how do you do to reach >15Nm drift ? :D

 

I put in the coordinates for the Hoover dam and it put me in the middle of lake mead. I tried to do a flyby update and it was 37 miles off. I let the system fully align before even lighting my engine so I don't know what happened.

[jojo]

1? INS updates to 2nd stage alignment, meaning 2nm/h.

 

Nice, just fly 8h...

[jojo]

I put in the coordinates for the Hoover dam and it put me in the middle of lake mead. I tried to do a flyby update and it was 37 miles off. I let the system fully align before even lighting my engine so I don't know what happened.

 

Is it a mission created with a former version ?

Did you set the coordinates format in "decimal" in the option menu ?

[bones1014]

Is it a mission created with a former version ?

Did you set the coordinates format in "decimal" in the option menu ?

 

Ah it was the decimal view! I forgot to change it like I did in 1.5. Thanks for the thought.

[jojo]

Ah it was the decimal view! I forgot to change it like I did in 1.5. Thanks for the thought.

 

Happy to help :thumbup:

[zerO_crash]

Nice, just fly 8h...

 

I`m just pointing out the difference.

Edited August 1, 2016 by zerO_crash

[Andrei]

How to you realign the INS if the drift is over 15 miles? It is just not possible?

 

Well.. I actually had to do it yesterday over Nevada as "drift" was around 2000 miles. See, I mistyped coordinate during alignment and instead of W115 I had W155. Of course I noticed that only in the air when next WP was 2K miles away instead of two.

 

I noticed it manual that correction was only possible when the difference is <15nm. But I thought that as the plane is not in release yet, that might not be implemented yet. And indeed, coming to WP3, I press REC, get the difference in coordinates, then hit VAL. Voila, INS perfectly updated.

 

Dunno if it's a bug or a feature, but certainly quite useful at that time.

[QuiGon]

Is drift always the same? Shouldn't it depend on the way you fly, meaning more drift when maneuvering, less drift when not?

[zerO_crash]

Max drift is 2nm/h. And yes, the more maneuvering you do, the more error is accumulated.

[Retu81]

Is drift always the same? Shouldn't it depend on the way you fly, meaning more drift when maneuvering, less drift when not?

 

For a mechanical gyro that's true, but I don't think RAZBAM is modeling the internal friction of the gyro as well. So our gyros might be "ideal". For a ring laser gyro, it doesn't matter what the aircraft is doing, since there are no moving parts.

[QuiGon]

For a mechanical gyro that's true, but I don't think RAZBAM is modeling the internal friction of the gyro as well. So our gyros might be "ideal". For a ring laser gyro, it doesn't matter what the aircraft is doing, since there are no moving parts.

 

Good point. Does the M2000 has a ring laser gyro?

 

If not, is maneuver-dependent drift simulated? I guess it is as zerO crash says that.

[ZHeN]

Good point. Does the M2000 has a ring laser gyro?

not 2000C

[QuiGon]

not 2000C

 

Alright, so I guess zerO_crash is right then. Good stuff :thumbup:

[zerO_crash]

Alright, so I guess zerO_crash is right then. Good stuff :thumbup:

 

Well don`t quote me on this, but I have either read or heard Zeus67 mention that drift error will max out at maneuvering. To me that sounds like it`s either implemented or going to be. Haven`t tested it out yet tbh, but when I flew M2000 yesterday though, I did notice that after a dogfight, I had more error accumulated compared to when I flew the day before roughly equally long CAP (no combat, less maneuvering)

 

Zeus67, you there?

[firmek]

Would it be possible to have as an option possibility to select that the correct coordinates are entered at WP00 at mission start.

This would allow to go through the full alignment process but without a necessity to retype the coordinates at mission start.

Normally I strive for as much realistic implementation as possible but in this specific case entering the coordinates is fun for first few times and after a while it becomes a nuisance.

Sorry for deviating from the last topic in the thread.

[RAZBAM_ELMO]

You haven't done the conversions for every parking spot for every airfield yet? Oh....oh just me.

 

Sent from my SM-G900W8 using Tapatalk

[Frederf]

You haven't done the conversions for every parking spot for every airfield yet? Oh....oh just me.

 

Sent from my SM-G900W8 using Tapatalk

 

It can be even easier than this by knowing any spot on an airfield and doing a position update after leaving parking but before takeoff. One can carry a phone book of every parking space in DCS or just 1-2 update spots per airfield.

[IvanK]

It can be even easier than this by knowing any spot on an airfield and doing a position update after leaving parking but before takeoff. One can carry a phone book of every parking space in DCS or just 1-2 update spots per airfield.

 

Though that inherently isn't as accurate as aligning on precise parking co ordinates.

[Frederf]

It actually is if you pick a repeatable spot like a taxiway intersection. You align and taxi to maybe the intersection of A and G and then stop, set the parking brake, and type in that spot's coordinates into 00.

[jojo]

Make sure in DCS option menu to choose "decimal" for coordinates.

[microvax]

BTW, why is the mirage heading different from the f10map headings ? Which heading is what. :D

[jojo]

On HSI, with right wheel select:

- Cv = True Heading (Cap Vrai)

- Cm = Magnetic Heading (Cap Magnétique)

 

But guys, this is in manual.

 

Other explanation is wrong INS alignment...

[Frederf]

For hot start I see coordinates like this N36°36.456 but jet is N36°36.47'.

 

It's always rounded plus 0.01'.