All electronics locked up

[dfenrick]

This has happened only a couple of times, but today it happened again.    After a rather steep dive and gun run on a ground target, after pulling out of the dive, my HUD was cocked at about 45 degress or so and not active.    The HUD was completely frozen, yet all of the steam gauges were working correctly.    On my way back to the airport, I noticed that all of the other displays were frozen as well.   I could see the buttons being depressed around each of the DDIs, but nothing changed.

I managed to make it home and land safely using the Analog airspeed indicator.   The Hornet flew fine, but none of the displays worked.

I tried shutting down and restarting, but the displays were all still frozen.    I was able to use the radios to get the ground crew to hook up shore power and then after shutting down, I was able to request repair.    After 170 seconds, the repair was complete and I was able to start a fully functioning Hornet.

So, I have a few questions.....

Was it my abrupt pull out of a steep dive that caused this..... it never has before.
Is getting the aircraft repaired the only way to solve this issue, or is there a way to simply reset all of the electronics?    Turning everything off and on again didn't fix it.

 

[Foka]

Did you use G-Limit override on pull up?
Did someone on the ground fired at you?

[Hulkbust44]

Random failures?

That specifically sounds like a failure of the primary flight mission computer, MC 1.

For that issue look to the back left of the cockpit for the MC OFF switch. Select the MC 1 OFF position. This will disable mission computer 1 and prompt back up subroutines for MC 1 stored in MC 2.

I've actually had to utilize this a handful of times in DCS.

[FrostLaufeyson]

It looks like you were hit by ground fire

You can check if the numbers on the bottom center of the DDI and AMPCD are increasing, I remember this is used to confirm that the electronics are working

[Razor18]

Yeah, and somebody in another topic mentioned, that hits on your aircraft have lost sound effect recently. So next time when any system goes south, I would first look at my aircraft from the outside view to confirm.

It happened to me many times recently with both MANPAD and AAA too. I was hit, but no boom, no "knocking on door", no any audio indication of a hit. Just blank displays everywhere.

Edited February 17, 2022 by Razor18

[dfenrick]

10 hours ago, Foka said:

Did you use G-Limit override on pull up?
Did someone on the ground fired at you?

Neither.    But those are good thoughts.   

I know lots of folks have been doing the over G thing by cycling spin recovery, but I haven't done that.   I also didn't use the HOTAS override on this pull either.   I have used it a few times in the past, and it never has caused any electronics misalignment, but I don't make a habit of it.    Seems like if it doesn't cause problems -- it probably should.  Generally, limits are imposed for a reason.

 

6 hours ago, Hulkbust44 said:

Random failures?

That specifically sounds like a failure of the primary flight mission computer, MC 1.

For that issue look to the back left of the cockpit for the MC OFF switch. Select the MC 1 OFF position. This will disable mission computer 1 and prompt back up subroutines for MC 1 stored in MC 2.

I've actually had to  utilize this a handful of times in DCS.

I've never heard of this, nor seen it described.   That is exactly what it sounds like.    Next time I'm in the jet I'll look around to see if I can find that switch and try it on the ground.   I think I'll also go back to the same training mission and see if I can replicate the failure.    It was a fairly aggressive manoeuver, but noething out of limits.

Thanks for the tip.   Where did you find that, and where can I read more???

 

[dfenrick]

6 hours ago, FrostLaufeyson said:

It looks like you were hit by ground fire

You can check if the numbers on the bottom center of the DDI and AMPCD are increasing, I remember this is used to confirm that the electronics are working

I didn't think anything was shooting back, but I may be mistaken.   I certainly didn't hear/feel anything, but according to the next post, there may be a sound problem in the recent update, and I may have missed it.   

3 hours ago, Razor18 said:

Yeah, and somebody in another topic mentioned, that hits on your aircraft have lost sound effect recently. So next time when any system goes south, I would first look at my aircraft from the outside view to confirm.

It happened to me many times recently with both MANPAD and AAA too. I was hit, but no boom, no "knocking on door", no any audio indication of a hit. Just blank displays everywhere.

 

This may be it.    Displays weren't blank, but they were frozen.   I didn't think I had been hit, so I never bothered to do an F2 inspection.    

[WOPR]

Cycling both the left and right generators together often helps with the issues described. Both full off then back on.  It won’t work if you cycle 1 at a time.  

[dfenrick]

3 hours ago, WOPR said:

Cycling both the left and right generators together often helps with the issues described. Both full off then back on.  It won’t work if you cycle 1 at a time.  

Thanks for the suggestion.; if it happens again, I'll try that.   

I would have thought that my complete shut down on the ground and then restart would have effectively done the concurrent generator shut down, but there may be something else that I'm missing.

[WOPR]

19 hours ago, dfenrick said:

Thanks for the suggestion.; if it happens again, I'll try that.   

I would have thought that my complete shut down on the ground and then restart would have effectively done the concurrent generator shut down, but there may be something else that I'm missing.

Logically it should.  But you are dealing with code.  It may not reset any systems just because you shut down the engines.  

[Gierasimov]

On 2/17/2022 at 2:28 AM, dfenrick said:

This has happened only a couple of times, but today it happened again.    After a rather steep dive and gun run on a ground target, after pulling out of the dive, my HUD was cocked at about 45 degress or so and not active.    The HUD was completely frozen, yet all of the steam gauges were working correctly.    On my way back to the airport, I noticed that all of the other displays were frozen as well.   I could see the buttons being depressed around each of the DDIs, but nothing changed.

I managed to make it home and land safely using the Analog airspeed indicator.   The Hornet flew fine, but none of the displays worked.

I tried shutting down and restarting, but the displays were all still frozen.    I was able to use the radios to get the ground crew to hook up shore power and then after shutting down, I was able to request repair.    After 170 seconds, the repair was complete and I was able to start a fully functioning Hornet.

So, I have a few questions.....

Was it my abrupt pull out of a steep dive that caused this..... it never has before.
Is getting the aircraft repaired the only way to solve this issue, or is there a way to simply reset all of the electronics?    Turning everything off and on again didn't fix it.

 

Let me be the first to say this. Track or it didn't happen.