Issue:  Guiding Results were incorrectly reported for Target 2/28 (IC 357)

Description:  Each 180s image from Guide Run 2 (IC 357 w/AT2021fyd) was reported with RMS value of 125.7" (Ra 113.6", Dec 53.9") Av SNR 16.6,  13% guide, Lost 88%. which is identical to the 5th and final 180s frame from Guide Run 1 (UGC 1436).  The total Run stats for Guide Run 2 (RMS 31.3", Ra 23.6" Dec 20.7") is also identical to total stats from Guide Run 1. It seems that Guide Stats data is being initialised to null value before starting new Guide Run and presumably there were no successful guide frames from Guide Run 2 to initiate any new stats.  Guiding Chart for Guide Run 2 shows base graphics only and are devoid of any data or stats results. 

Analysis: 

• After successfully centering IC 357 target,   Guiding operations started at 20:42 with initiation of Guide Run 2 and the taking of a 10s reference image with Cam2 using PHD2 which was converted to JPG ok .
   
• The frames shows plenty of stars. 
   
• Send Guide Request was reported, but there was no reporting of Lock Position, Guiding Started, Guiding settled etc or any sign of the Capture of Guide Frame. 
   
• PHD2 log shows Guide request being made at 20:42:52.53 with a succession of Events thereafter including LockPosition, Settle Begin, and Settle Done at 20:43:26.70.   However the session Log File show Return from StartGuider at 20:42:52.64 (which is barely a fraction of second after Guiding Started) and the expected preceeding Save GuideFrameImage task/result is missing.
     
• The PHD2 log shows a whole series of GuideStep events between 20:43 and 21:00 when guiding was stopped prior to slew to next target.   There are some Star Lost events but most events are successful GuideStep (AllSky pictures show passage of some cloud across the target  during this time.  Guiding therefore took place for the target but somehow AstroMain didn't run Guide Monitoring for the target and appears to exited StartGuiding operations before its normal end.  
   
• Report file shows that a SoftSuspend had been called at 20:42:13 during the final Locate Frame and only cleared at 20:47:13. This meant that SoftSuspend Flag was active during Guiding Initiation.  
   
• After sending Guide Request to PHD2 the StartPHD2Guiding routine enters a loop which waits for Settle Done event or  2 * TimeOut period (which ever comes first). However the loop contains other checks including a check on SoftSuspend state - if the SoftSuspend Flag is raised the routine exits almost immediately without taking the usual 1.5s Guide Frame pictures and without calling StartPHD2GuidingMonitor().  This nicely explains the observations. 

Conclusion:

Action:
AstroMain. Fix code  (Fixed in AstroMain 3.38.11, 2021-03-30)