DSKY hanging during programs

[AliDarwesh]

Hi,
During the Apollo 7 scenario (nassp 8.0, orbiter 2016) I have the following issue:

When trying to run P47 the DSKY will hang with the COMP ACTV light illuminated (illuminated and not blinking). I can only terminate program with V96.
I noticed the same problem when starting R30 by pressing V82. After entering the options and pressing PRO it will also hang with COMP ACTV illuminated and no way of exiting except V96. No data will be shown in r1,2,3 in both cases. No PROG light illuminated either.

I suspect it has to do with a string of restarts I had due to x10 time compression while changing views.

I tried P51, P52 but that won't fix the problem. Nor does restarting by V69.

Uplinking state vector either by MCC or Project Apollo MFD also won't solve it.

Will rebooting the AGC by totally powering it down and then restart it fix the problem? If so, what would be the appropriate procedure?

Or if that's not the solution is there anybody who knows how to fix the problem?

 

[thermocalc]

Hi,
I want to start A7 in NASSP v8 so I will check soon if I have the same issue, anyway here are some possibilities I discovered in V7.
PLEASE I am not a NASSP expert so I cannot guarantees what I am saying is correct but I saw sometimes it helped me...
you can try to go back to P00 by these ways:
V37E 00E - normal way; V96E; V36E V96E
if nothing work you can try to stop the activity light on by V58E
if nothing work you may PULL the CMC cbs in the right panel and put IN again .... you should get the RESTART light on
I am not at home, tonight I can have a look in the AOH operational manual of the CSM if there is a procedure to power down the CMC in another way.
hope it helps.
don't know if you know, but I was told than go to P00 by V96E is not very healthy for the CMC as it may screw up the SV (so I understood) so better use it as less as possible.
sorry but more I can't help.
kind regards, Paolo

 

[AliDarwesh]

Hi,
I want to start A7 in NASSP v8 so I will check soon if I have the same issue, anyway here are some possibilities I discovered in V7.
PLEASE I am not a NASSP expert so I cannot guarantees what I am saying is correct but I saw sometimes it helped me...
you can try to go back to P00 by these ways:
V37E 00E - normal way; V96E; V36E V96E
if nothing work you can try to stop the activity light on by V58E
if nothing work you may PULL the CMC cbs in the right panel and put IN again .... you should get the RESTART light on
I am not at home, tonight I can have a look in the AOH operational manual of the CSM if there is a procedure to power down the CMC in another way.
hope it helps.
don't know if you know, but I was told than go to P00 by V96E is not very healthy for the CMC as it may screw up the SV (so I understood) so better use it as less as possible.
sorry but more I can't help.
kind regards, Paolo

Thanks, I will try as soon as possible and let you know if it solved the issue.

 

[AliDarwesh]

UPDATE:

-I have tried pulling the CMC cbs. I did indeed get the restart light on. Didn't fix the issue, though.
-V58E wont do anything while it is hanging. only V96 will stop the program (I tried program 47)
-After V96 V36 V96, trying to run P47 will yield the error code 220. After doing a P51, I found that the issue isn't solved and DSKY will still hang when trying P47 or some other programs.

I made a save with the scenario editor which I will attach here.

I hope there is a fix for this. I could just restart the Apollo 7 mission from scratch but I would rather learn how to deal with these issues!

 

[indy91]

Your CMC clock (check V16 N65) is showing a very wrong time, negative even. So when you uplink a fresh state vector it will try to propagate that state vector to current time, which will take forever. So the first step is to do a clock update with the Project Apollo MFD, on the telemetry page (TELE button) and then clock update (CLK button twice). I think all other issues can get resolved from there. V82 and P47 are already working fine when I do just the clock update.

Not really sure what caused the clock to be off, but it might have been caused by your initial restarts.

 

[AliDarwesh]

Problem solved. Thanks a lot!