Hi all,
I am using Cloudmakers software, including INDI Server (IS), INDI Control Panel (ICP), and AstroTelescope (AT) with my CGEM DX and home motorized 8' dome. I have been using the Dome Sync Gateway (DSG) in ICP to produce GOTO python commands which drive my dome. The problem is that when DSG is slaved to my dome, only the first (or rarely the first few) dome move commands (all of which are GOTO's) are actually given by the INDI driver.
0) I can reliably get AT to convince ICP to throw a GOTO.py by turning off the DSG, then turning off the INDI link to the telescope, then turning DSG back on, and finally turning the link to the telescope back on. However, this is a very clumsy way to track an object all night!
1) I have tried a range of tolerances from 0.02 degrees to 10 degrees. All result in the same infrequent calling of GOTO's. All other dome measurements are entered in ICP normally.
2) My dome has a tolerance of 0.1 degrees. Meaning, if a goto asks for 165°, the dome might stop anywhere from 164.9° to 165.1°. However, once stopped, it tells INDI via a DSG Status command that it is at 165°, either way. So I don't think it is a tolerance error, or an issue with INDI thinking the dome is still moving (I think - there could still be rounding differences, and possibly output formatting differences that make INDI think the dome is close, but not entirely there).
Does anyone know what might be happening?
Peter Polakovic suggested contacting Jasem - with this post, I am attempting to do just that, as well as crowd-source your wisdom!
Sincerely,
Scott
I am using Cloudmakers software, including INDI Server (IS), INDI Control Panel (ICP), and AstroTelescope (AT) with my CGEM DX and home motorized 8' dome. I have been using the Dome Sync Gateway (DSG) in ICP to produce GOTO python commands which drive my dome. The problem is that when DSG is slaved to my dome, only the first (or rarely the first few) dome move commands (all of which are GOTO's) are actually given by the INDI driver.
0) I can reliably get AT to convince ICP to throw a GOTO.py by turning off the DSG, then turning off the INDI link to the telescope, then turning DSG back on, and finally turning the link to the telescope back on. However, this is a very clumsy way to track an object all night!
1) I have tried a range of tolerances from 0.02 degrees to 10 degrees. All result in the same infrequent calling of GOTO's. All other dome measurements are entered in ICP normally.
2) My dome has a tolerance of 0.1 degrees. Meaning, if a goto asks for 165°, the dome might stop anywhere from 164.9° to 165.1°. However, once stopped, it tells INDI via a DSG Status command that it is at 165°, either way. So I don't think it is a tolerance error, or an issue with INDI thinking the dome is still moving (I think - there could still be rounding differences, and possibly output formatting differences that make INDI think the dome is close, but not entirely there).
Does anyone know what might be happening?
Peter Polakovic suggested contacting Jasem - with this post, I am attempting to do just that, as well as crowd-source your wisdom!
Sincerely,
Scott