feature tracking - planetary - feedbacks?

Somewhere to ask questions about the best way to use SharpCap
Forum rules


If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
cine
Posts: 18
Joined: Sun May 22, 2022 1:55 pm

Re: feature tracking - planetary - feedbacks?

#11

Post by cine »

Hi Robin

I take it the calibration takes backlash in to account.

Also if a calibration fails then it seem it show a error but then seems to turn my mount tracking off. Every time i am trying to calibrate i have to keep going back in turn enable mount tracking again in CPWI.

Mike
cine
Posts: 18
Joined: Sun May 22, 2022 1:55 pm

Re: feature tracking - planetary - feedbacks?

#12

Post by cine »

Hi Robin

Winds dropped a bit

Here is some log files first one i tried a calibration in center mass full frame view of the sun in frame, it failed and after fail sharpcap turned of my mount tracking can't see why in the log file.

Warning 10:26:55.708564 #7 Measured X scalings of 7.14798520996838 and 18.3323765416299 differ too much in void SharpCap.FeatureTracking.FeatureTrackingModel.DoAppend(LoggingEvent loggingEvent)
Info 10:26:55.709562 #7 Data point log for direction XPositive
Mount: {X=0.5, Y=0}, Image {X=2.969971, Y=-1.751038}
Mount: {X=1, Y=0}, Image {X=4.77002, Y=-1.383057}
Mount: {X=1.5, Y=0}, Image {X=7.459961, Y=-3.683044}
Mount: {X=1.75, Y=0}, Image {X=9.180054, Y=-4.39801}
Mount: {X=2.25, Y=0}, Image {X=10.94995, Y=-7.215027}
Mount: {X=2.75, Y=0}, Image {X=14.56006, Y=-8.392029}
Mount: {X=3.25, Y=0}, Image {X=16.67004, Y=-10.59003}
Mount: {X=3.75, Y=0}, Image {X=20.44006, Y=-12.35602}
Mount: {X=4.25, Y=0}, Image {X=22.93005, Y=-13.69501}
Mount: {X=4.75, Y=0}, Image {X=26.12, Y=-14.91803}
Mount: {X=5.25, Y=0}, Image {X=30.31006, Y=-16.638}
Mount: {X=5.75, Y=0}, Image {X=34.07996, Y=-18.24506}
Mount: {X=6.25, Y=0}, Image {X=37.45996, Y=-19.36902}
Mount: {X=6.75, Y=0}, Image {X=43.39001, Y=-18.52106}
Mount: {X=7.25, Y=0}, Image {X=46.22998, Y=-21.55304}
in void SharpCap.FeatureTracking.PointList.LogData()
Info 10:26:55.709562 #7 Data point log for direction XNegative
Mount: {X=-0.5, Y=0}, Image {X=-8.369995, Y=3.120972}
Mount: {X=-1, Y=0}, Image {X=-15.38, Y=6.238953}
Mount: {X=-1.25, Y=0}, Image {X=-20.15002, Y=8.392944}
Mount: {X=-1.5, Y=0}, Image {X=-24.88, Y=11.42798}
Mount: {X=-1.75, Y=0}, Image {X=-28.94995, Y=13.34198}
Mount: {X=-2, Y=0}, Image {X=-33.43994, Y=16.099}
Mount: {X=-2.25, Y=0}, Image {X=-36.56995, Y=17.00897}
Mount: {X=-2.5, Y=0}, Image {X=-39.16003, Y=18.85095}
Mount: {X=-2.75, Y=0}, Image {X=-43.87, Y=25.09399}
in void SharpCap.FeatureTracking.PointList.LogData()


Here is log file of image feature calibration again after fail mount tracking is off again.


Warning 10:26:55.708564 #7 Measured X scalings of 7.14798520996838 and 18.3323765416299 differ too much in void SharpCap.FeatureTracking.FeatureTrackingModel.DoAppend(LoggingEvent loggingEvent)
Info 10:26:55.709562 #7 Data point log for direction XPositive
Mount: {X=0.5, Y=0}, Image {X=2.969971, Y=-1.751038}
Mount: {X=1, Y=0}, Image {X=4.77002, Y=-1.383057}
Mount: {X=1.5, Y=0}, Image {X=7.459961, Y=-3.683044}
Mount: {X=1.75, Y=0}, Image {X=9.180054, Y=-4.39801}
Mount: {X=2.25, Y=0}, Image {X=10.94995, Y=-7.215027}
Mount: {X=2.75, Y=0}, Image {X=14.56006, Y=-8.392029}
Mount: {X=3.25, Y=0}, Image {X=16.67004, Y=-10.59003}
Mount: {X=3.75, Y=0}, Image {X=20.44006, Y=-12.35602}
Mount: {X=4.25, Y=0}, Image {X=22.93005, Y=-13.69501}
Mount: {X=4.75, Y=0}, Image {X=26.12, Y=-14.91803}
Mount: {X=5.25, Y=0}, Image {X=30.31006, Y=-16.638}
Mount: {X=5.75, Y=0}, Image {X=34.07996, Y=-18.24506}
Mount: {X=6.25, Y=0}, Image {X=37.45996, Y=-19.36902}
Mount: {X=6.75, Y=0}, Image {X=43.39001, Y=-18.52106}
Mount: {X=7.25, Y=0}, Image {X=46.22998, Y=-21.55304}
in void SharpCap.FeatureTracking.PointList.LogData()
Info 10:26:55.709562 #7 Data point log for direction XNegative
Mount: {X=-0.5, Y=0}, Image {X=-8.369995, Y=3.120972}
Mount: {X=-1, Y=0}, Image {X=-15.38, Y=6.238953}
Mount: {X=-1.25, Y=0}, Image {X=-20.15002, Y=8.392944}
Mount: {X=-1.5, Y=0}, Image {X=-24.88, Y=11.42798}
Mount: {X=-1.75, Y=0}, Image {X=-28.94995, Y=13.34198}
Mount: {X=-2, Y=0}, Image {X=-33.43994, Y=16.099}
Mount: {X=-2.25, Y=0}, Image {X=-36.56995, Y=17.00897}
Mount: {X=-2.5, Y=0}, Image {X=-39.16003, Y=18.85095}
Mount: {X=-2.75, Y=0}, Image {X=-43.87, Y=25.09399}
in void SharpCap.FeatureTracking.PointList.LogData()
Warning 10:43:09.221363 #7 Measured X scalings of 11.3071911094146 and 41.0637495877522 differ too much in void SharpCap.FeatureTracking.FeatureTrackingModel.DoAppend(LoggingEvent loggingEvent)
Info 10:43:09.221363 #7 Data point log for direction XPositive
Mount: {X=0.5, Y=0}, Image {X=6.896866, Y=-1.517623}
Mount: {X=1, Y=0}, Image {X=12.84665, Y=-3.092703}
Mount: {X=1.25, Y=0}, Image {X=14.92942, Y=-2.728017}
Mount: {X=1.5, Y=0}, Image {X=17.13911, Y=-3.455645}
Mount: {X=2, Y=0}, Image {X=25.23087, Y=-4.755119}
Mount: {X=2.375, Y=0}, Image {X=28.94646, Y=-2.968056}
Mount: {X=2.75, Y=0}, Image {X=27.81873, Y=-7.441483}
Mount: {X=3.125, Y=0}, Image {X=33.17085, Y=-9.291576}
Mount: {X=3.5, Y=0}, Image {X=38.74908, Y=-5.652367}
Mount: {X=3.875, Y=0}, Image {X=44.09312, Y=-6.478818}
Mount: {X=4.25, Y=0}, Image {X=47.61982, Y=-13.34211}
Mount: {X=4.625, Y=0}, Image {X=55.13602, Y=-10.55996}
in void SharpCap.FeatureTracking.PointList.LogData()
Info 10:43:09.221363 #7 Data point log for direction XNegative
Mount: {X=-0.5, Y=0}, Image {X=-11.54267, Y=-1.245481}
Mount: {X=-1, Y=0}, Image {X=-19.50819, Y=8.875015}
Mount: {X=-1.25, Y=0}, Image {X=-35.09497, Y=4.912156}
Mount: {X=-1.4375, Y=0}, Image {X=-47.28401, Y=8.262241}
Mount: {X=-1.578125, Y=0}, Image {X=-53.85315, Y=11.27758}
in void SharpCap.FeatureTracking.PointList.LogData()

Mike
User avatar
admin
Site Admin
Posts: 13173
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: feature tracking - planetary - feedbacks?

#13

Post by admin »

Hi Mike,

that's interesting... What is happening is that SharpCap is rejecting the data because the mount seems to move faster in one direction than the other. What settings were you using for the movement rate? It could be that the command to move the mount is turning off tracking (ASCOM doesn't define whether that happens or not, so it may vary according to manufacturer and ASCOM driver). Then, if you ask it to move at 3x sidereal in RA, the effective movement rate would be ~2x in one direction and ~4x in the other, due to the fact that the sun is moving at ~1x sidereal rate.

cheers,

Robin
cine
Posts: 18
Joined: Sun May 22, 2022 1:55 pm

Re: feature tracking - planetary - feedbacks?

#14

Post by cine »

Hi Robin

Strange, where would i find those rates, i am using CPWI when i check in there i have just set tracking rate to Solar thats the only change i have made. Been using the mount for DSO for years no tracking issues use NINA.

Also quick question i have been tracking all morning on my ZWO 178mm camera with a POI, just swtiched to me ZWO 174mm set a POI hit monitor but the guide button is greyed out ?? was working all morning would could be stopping the guide button being available.

Mike
cine
Posts: 18
Joined: Sun May 22, 2022 1:55 pm

Re: feature tracking - planetary - feedbacks?

#15

Post by cine »

Hi Robin

I have switched back to the 178mm but still the same the guide button is greyed out. Restarted sharpcap still the same not sure why i have been using POI tracking all morning without a problem.

Mike
cine
Posts: 18
Joined: Sun May 22, 2022 1:55 pm

Re: feature tracking - planetary - feedbacks?

#16

Post by cine »

Hi Robin

Do you need a calibrate in POI mode before guide comes up

Mike
User avatar
admin
Site Admin
Posts: 13173
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: feature tracking - planetary - feedbacks?

#17

Post by admin »

Hi,

no, you shouldn't need to calibrate in ROI mode, since calibration is to work out which way the image moves when the mount is moved in different directions, and that doesn't apply for ROI.

The movement speed dropdown is top-left of the tracking window - You may find that there are various rates including guiding rate and multiples of sidereal rate shown. Guiding rate is more likely to be correctly added onto the current tracking rate than the other movement rates. See https://docs.sharpcap.co.uk/4.0/#Feature%20Tracking

cheers,

Robin
cine
Posts: 18
Joined: Sun May 22, 2022 1:55 pm

Re: feature tracking - planetary - feedbacks?

#18

Post by cine »

Hi Robin

there may be a bug with POI tracking then i tried multiple times and i need to select calibrate before guiding is enabled to select in POI i don't thing calibrate in fact does anything in that mode but as soon as i hit the that button guide changes from grey out to selectable. i will check out about tracking rates, still not sure why one direction rate would be different.

mike
cine
Posts: 18
Joined: Sun May 22, 2022 1:55 pm

Re: feature tracking - planetary - feedbacks?

#19

Post by cine »

hi robin

i can't seem to find this drop down for tracking can you help a little with finding it, i did read the attached manual but again can't find the menu. i can see rate under telescope control menu. there is no drop down i can find on the top left of the feature tracking menu

mike
cine
Posts: 18
Joined: Sun May 22, 2022 1:55 pm

Re: feature tracking - planetary - feedbacks?

#20

Post by cine »

hi robin

i see it now "movement speed" how would that effect speed changes in just one dirrection. i though my log indicated speed is different directions.

mike
Post Reply