search

DanielVanNoord / open-phd-guiding

Automatically exported from code.google.com/p/open-phd-guiding
0 stars 0 forks source link

problem with socket server distance reporting immediately after dither #255

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Immediately after a dither, prior to completion of the next camera frame, 
REQDIST returns the current distance prior to the dither. This can cause an 
application that only takes a single distance sample (Nebulosity) to conclude 
that dither has settled.

19:20:48.867 00.005 3612 Handling exposure in myFrame
19:20:52.095 03.228 5148 read socket command 13                                 

19:20:52.095 00.000 5148 processing socket request MOVEn                        

19:20:52.095 00.000 5148 dither: size=10.00, dRA=6.46 dDec=4.93                 

19:20:52.095 00.000 5148 MountToCamera -- mountTheta (-0.65) + m_xAngle (1.50) 
= xAngle (0.85 = 0.85)                                                   
19:20:52.095 00.000 5148 MountToCamera -- mountX=6.46 mountY=4.93 hyp=8.13 
mountTheta=-0.65 cameraX=5.37, cameraY=6.09 cameraTheta=0.85                 
19:20:52.095 00.000 5148 setting lock position to (532.89, 328.28)              

19:20:52.095 00.000 5148 Status Line 0: Dither by 6.46,4.93                     

19:20:52.096 00.001 5148 Sending socket response 3 (0x3)                        

19:20:58.099 06.003 5148 read socket command 10                                 

19:20:58.099 00.000 5148 processing socket request REQDIST                      

19:20:58.100 00.001 5148 SOCKSVR: Sending pixel error of 0.38                   

19:20:58.100 00.000 5148 Sending socket response 38 (0x26)

Original issue reported on code.google.com by andy.gal...@gmail.com on 6 Feb 2014 at 3:25

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision r716.

Original comment by andy.gal...@gmail.com on 6 Feb 2014 at 6:21