Jerry Gerber:
I am getting advice to delete Solve & Sync from the NINA advanced sequence because I have already built a 99 star model using 10Micron Tools. I am imaging unguided and getting excellent results. Should I follow this advice? Is the model itself already doing what plate solving and sync is doing?
Thanks,
Jerry
Peter Goodhew:
The model is pointing the mount close to the exact coordinates, based on where the nearest model point is to the target. There will always be a small error in this - with a good model it could be around 10-15 arcsecs. Often it is much more. Solve and Sync will correct for such errors. If you're happy with these errors then you can delete Solve and Sync.
AnaTa:
In "10 micron mount configuration" software open "Setting". There is "Sync" domain, un-click "Enable Sync", when model is stablished. It should be clicked in during model building. I use "Model Creator 2".
In NINA, go to "Options", then "Equipment". There is "Mount" domain there, both "Coordinate Sync" and "Time Sync" could be "ON", when model has already been built.
This is a setting that I use. I usually build a model on average once in 3-4 months. My rig is in an observatory.
Clear Skies!
Armen
Peter Goodhew:
I've been using 10micron models for 7 years on two different systems and never heard of that.
I always use solve and sync despite the models.
It tells me how well the model is performing, and brings me within 10 arc secs of the target.
Jerry Gerber:AnaTa:
In "10 micron mount configuration" software open "Setting". There is "Sync" domain, un-click "Enable Sync", when model is stablished. It should be clicked in during model building. I use "Model Creator 2".
In NINA, go to "Options", then "Equipment". There is "Mount" domain there, both "Coordinate Sync" and "Time Sync" could be "ON", when model has already been built.
This is a setting that I use. I usually build a model on average once in 3-4 months. My rig is in an observatory.
Clear Skies!
Armen
When I unclick "Enable Sync" in the 10Micron ASCOM driver, I get a "failed" display in NINA's advanced sequencer, the NINA log shows that plate solving succeeded but sync failed. The only way to resolve this is to turn "Enable Sync" back on in the 10Micron ASCOM driver.
I am using a different model builder, I am using the 10Micron Tools plugin for NINA. This model builder does not need the Enable Sync turned on to build the model, but NINA apparently needs it checked when doing a Solve & Sync in the sequencer. Go figure...
Peter Goodhew:
I've been using 10micron models for 7 years on two different systems and never heard of that.
I always use solve and sync despite the models.
It tells me how well the model is performing, and brings me within 10 arc secs of the target.
Peter Goodhew:
Enable Sync ON
Use Sync as Refine OFF (this is obviously ON when building the model)
Peter Goodhew:
Enable Sync ON
Use Sync as Refine OFF (this is obviously ON when building the model)
Jerry Gerber:Peter Goodhew:
I've been using 10micron models for 7 years on two different systems and never heard of that.
I always use solve and sync despite the models.
It tells me how well the model is performing, and brings me within 10 arc secs of the target.
Hi Peter.
Might you know what Sync settings you are using in the 10Micron ASCOM driver? When I turn off the "enable sync" option, NINA gives an error in the advanced sequencer saying tht sync has failed. When "Enable Sync" is checked, this problem goes away and Solve & Sync is successful. I'm getting a lot of conflicting comments from people over at the 10Micron forum!
Best,
Jerry
Ruediger:
Hello Jerry,
we already discussed this point excessively in 10M forum.
Never ever add a sync to the exiting model after it has been created, since you destroy the model. When ever you have an issue with accuracy (pointing), discard the model and create a new one. Adding a sync point after the model creation, e.g. on another day, will corrupt the model for sure, since the conditions are not identical. Moreover there is no need!
Moreover, if "sync as refine point" is off, you translate the complete model by an offset, to the new sync coords delta. Latest here, your complete model is corrupt. I this case it is better not to use any model and run the mount without a model at all.
Therefore "Sync enabled" should always be disabled in the ASCOM driver. The only exception is if you create a model with "Model Creator" since this is the only tool, which uses ASCOM. All other tools use the native command protocol. It really would have been better, if 10M would have not exposed this feature in ASCOM.
You should use "slew and center" instead..Hi Ruediger,
Jerry Gerber:Ruediger:
Hello Jerry,
we already discussed this point excessively in 10M forum.
Never ever add a sync to the exiting model after it has been created, since you destroy the model. When ever you have an issue with accuracy (pointing), discard the model and create a new one. Adding a sync point after the model creation, e.g. on another day, will corrupt the model for sure, since the conditions are not identical. Moreover there is no need!
Moreover, if "sync as refine point" is off, you translate the complete model by an offset, to the new sync coords delta. Latest here, your complete model is corrupt. I this case it is better not to use any model and run the mount without a model at all.
Therefore "Sync enabled" should always be disabled in the ASCOM driver. The only exception is if you create a model with "Model Creator" since this is the only tool, which uses ASCOM. All other tools use the native command protocol. It really would have been better, if 10M would have not exposed this feature in ASCOM.
You should use "slew and center" instead..Hi Ruediger,
I'm getting completely opposite advice from you and Peter.
My experience has been to build a model, keep Nina sync ON, the ASCOM driver "Enable Sync" ON and keep "Sync as Refine" OFF.
I've had it set like this for a year and unguided tracking has been fine.
Maybe you & Peter can compare notes?
If the model gets corrupted, wouldn't that show up as poor tracking, star trails, etc.? I'm not seeing any of that.
Ruediger:Jerry Gerber:Ruediger:
Hello Jerry,
we already discussed this point excessively in 10M forum.
Never ever add a sync to the exiting model after it has been created, since you destroy the model. When ever you have an issue with accuracy (pointing), discard the model and create a new one. Adding a sync point after the model creation, e.g. on another day, will corrupt the model for sure, since the conditions are not identical. Moreover there is no need!
Moreover, if "sync as refine point" is off, you translate the complete model by an offset, to the new sync coords delta. Latest here, your complete model is corrupt. I this case it is better not to use any model and run the mount without a model at all.
Therefore "Sync enabled" should always be disabled in the ASCOM driver. The only exception is if you create a model with "Model Creator" since this is the only tool, which uses ASCOM. All other tools use the native command protocol. It really would have been better, if 10M would have not exposed this feature in ASCOM.
You should use "slew and center" instead..Hi Ruediger,
I'm getting completely opposite advice from you and Peter.
My experience has been to build a model, keep Nina sync ON, the ASCOM driver "Enable Sync" ON and keep "Sync as Refine" OFF.
I've had it set like this for a year and unguided tracking has been fine.
Maybe you & Peter can compare notes?
If the model gets corrupted, wouldn't that show up as poor tracking, star trails, etc.? I'm not seeing any of that.
The ASCOM settings are not used by the 10M Plugin. So there is no need to switch it on. Only the commands in the sequencer will use ASCOM.
ANY sync beyond modelling corrupts the model. Either by adding an additional point to the model which was taken under different constraints, or it is translating the entire model. Depending on the refine option.
Whether it is noticeable, or not, depends on the error of the additional sync. If you are lucky it is minimal, if not, you are completely messed up. Essay to understand example:
You take an image and heavy wind gust is pushing the scope and then you sync... That is the moment where your model is done for sure. One more? E..g a focuser slip and tilt, a vibration, more and more. One single erroneous snyc will be fatal.
Also it depends on you focal length and exposure times. If you are running short fl e.g. 1000mm, any error is less noticeable, but i can ensure you at more than 4m fl and long exposure you will immediately notice the problem.
Please help me to understand: What should an additional sync be good for, when you have a valid model? What do you want to achieve?