See this Comm Center thread from Don Pray. Look at the activity at Set 68 Repeat 13/13 of the 02006 target. It happily pre-slews to the next target 54501 at 03:04:33, then later at 03:05:58 finishes waiting for the pre-slew and turns around and does a AutoFlipIf() for the current target 02006, and actually slews back to it!



Make sure this flaw is not in AcquireScheduler too!!!

A long-standing obscure target sequencing bug. It occurred when slew overlap is enabled, the "from" and "to" targets are on opposite sides of the mount's flip point (e.g. the meridian), and the last image of the "from" target has enough pointing error to require a recenter. Skip this recenter if the last image of the "from" target.

 

  
SVN Comment
 
 

  
Author
  
rbdenny
 
 

  
Repository
  
svn+ssh://rbdenny@a2_svn_dc3/home/rbdenny/svn/astro/acp
 
 

  
SVN Revision
  
999
 
 

  
Affected files
  
/trunk/ACP Help/relnotes.htm (Modified)
/trunk/Scripts/AcquireImages.js (Modified)

 
 

  
Check-in comment
  
Fix long standing target sequencing bug. When slew overlap is enabled, the "from" and "to" targets are on opposite sides of the mount's flip point (e.g. the meridian), and the last image of the "from" target has enough pointing error to require a recenter. Skip this recenter if the last image of the "from" target.
GEM:932

 

Sounds like Dean Salman ran into it recently! See this post on the Comm Center. It sound like the same damn thing.

Finally looking at this. May not fix it since others haven't reported it, but i need to make sure this isn't a latent bug that will bite others (or has without their knowledge or reporting same).