Can you fix/undo RIO-input INS errors

[WelshZeCorgi]

While trying to get Navgrid set up, I accidentally put in the YY lat coordinates while the TID was in Aircraft Stabilized mode, which shifted ownship to that lat input, completely screwing up the INS.

 

I've had similar troubles in the past of accidently inputting Navgrid stuff into the INS, such as inputting the heading 180 into ownship, which made us look like we were flying south when we were actually heading north, fun stuff like that.

 

I also did something (not sure how) where we suspect I accidentally made the INS think that there was a 100kt crosswind that caused the pilot's HUD to be half off the glass.

 

I've learned how to set it up consistently without screwing it up, but I wanted to ask if there was a way to undo mistakes like these. Just in case I have a brain-fart in the future. I know about the Radar Fix, Tacan Fix and Vis Fix, but those fixes seem to shift the waypoints around ownship and not the other way around. So I have to ask if there is away to fix ownship position if it gets messed up through bad RIO inputs on the CAP pad.

 

Thanks for your time.

[QuiGon]

AFAIK the fixes should update the ownship position and not the waypoint (with the exception of the Surface Target waypoint, which does update it's own position when a fix is performed on it).

Edited February 4, 2020 by QuiGon

[WelshZeCorgi]

Ok, so fixes do move own ship and not the other way around. Thank you.

 

I was wondering about the other two mistakes, inputting the wrong heading or wrong windspeed (or whatever causes the HUD to shift offcenter.) Can you fix that by just inputting the current heading or setting windspeed to 0?

[QuiGon]

I was wondering about the other two mistakes, inputting the wrong heading or wrong windspeed (or whatever causes the HUD to shift offcenter.) Can you fix that by just inputting the current heading or setting windspeed to 0?

I guess inputting the current heading should work. In regards to wind, the manual input is only getting used in the backup nav modes, so it shouldn't matter as long as you're using the primary INS mode.

[WelshZeCorgi]

I guess inputting the current heading should work. In regards to wind, the manual input is only getting used in the backup nav modes, so it shouldn't matter as long as you're using the primary INS mode.

 

I tried this in several freeflight mission, I intentionally input a bad heading, waited a half minute, then input the correct heading. It does seem to slow down INS degradtion initially, but it still accelerates exponentially into an unusable state.

 

I looked this up in the bugs forum and the explanation is that the INS takes the Earth's rotation into account, so inputting the wrong heading completely messed up the calculations for that part of the equation. As far as I can tell, (though I hope I'm wrong) there is no fix other than switching to a backup mode.

[QuiGon]

I tried this in several freeflight mission, I intentionally input a bad heading, waited a half minute, then input the correct heading. It does seem to slow down INS degradtion initially, but it still accelerates exponentially into an unusable state.

 

I looked this up in the bugs forum and the explanation is that the INS takes the Earth's rotation into account, so inputting the wrong heading completely messed up the calculations for that part of the equation. As far as I can tell, (though I hope I'm wrong) there is no fix other than switching to a backup mode.

Seems legit :thumbup:

So better be careful what you input then ;)