Date
1 - 20 of 21
slew warning APPM with Mach2
Klaus Völler
Hi,
I've only been a silent reader here since I got my Mach2 (April 2021). No problems everything works. Now I have refined my pole alignment and wanted to create a new model in APPM. Now I also get the "slew warning" at certain points and dash marks on the images. I have attached pictures with the corresponding information. As in the other cases described here in the forum, I first checked all fixings. But there is nothing to complain about. In some failures, the pumping is visible when you look closely. I have not had this before. All points have always been successfully solved so far. Would be happy to receive a description of how this is solvable. regards Klaus |
|
Chris White
Welcome Klaus!
What camera are you using? I had failed solves on my model with IMX455, and when I went to a 50% size frame the problem went away. Or are you saying that those failed solves have bad captures with elongated stars? As far as the dashed lines go, I get that if my mount hits a horizon limit. Despite having APCC set to not track past a horizon limit, it will stop for the exposure that hits the limit and then continue tracking on the next exposure. I wonder if there is a bug in APCC as I dont understand how my capture software can override the mount horizon limit. I havent asked about it yet here as I just found the issue. |
|
Klaus Völler
Hi Chris,
toggle quoted message
Show quoted text
thank you for your answer. I am using a QHY600M with 2x2 binning on a TEC140FL for "plate solving". The green dots have been solved successfully. In case of errors, the image does not really show elongated stars, but looks like star trails.... and as you can see from my attached images (first mail), the faulty points are all within the horizon boundary. Are not on the edge of the boundary but slightly offset inward and can be seen on both sides west/east. Both axes are in balance. All screws checked. Before I called APPM, I also did a polar alignment (deviation 6''). This topic already existed in earlier postings and Rolando mentioned that the mount does not come to rest there, it pumps.... I already made a model half a year ago with the same equipment. No faulty points. Attached is an example picture from the camera where the plate solve failed. regards Klaus Am 20.11.22 um 02:25 schrieb Chris
White:
Welcome Klaus! |
|
Ray Gralak
Hi Chris,
I wonder if there is a bug in APCC as I dont understand how my capture software can override theThis is how the Horizon limit needs to operate. The controlling software needs to restart tracking because ASCOM doesn't allow slewing (e.g., to slew back inside the Horizon limits) and other operations while tracking is disabled. -Ray |
|
Ray Gralak
Hi Klaus,
Would be happy to receive a description of how this is solvable.If you are not running the latest Mach2 firmware (VCP5-P02-15), you should update it. If the firmware is up to date, or still haeve this problem after updating, contact Mike Hanson at Astro-Physics for further instructions. -Ray |
|
Klaus Völler
Hi Ray,
toggle quoted message
Show quoted text
many thanks for your feedback.. Seems i have to update my CP5 first... My Firmware Version is VCP5-P02-08. When that's done and the weather permits another attempt at building a model, I'll report back. regards Klaus Am 20.11.22 um 15:54 schrieb Ray Gralak: Hi Klaus,Would be happy to receive a description of how this is solvable.If you are not running the latest Mach2 firmware (VCP5-P02-15), you should update it. If the firmware is up to date, or still haeve this problem after updating, contact Mike Hanson at Astro-Physics for further instructions. |
|
Chris White
On Sun, Nov 20, 2022 at 09:39 AM, Ray Gralak wrote:
This is how the Horizon limit needs to operate. The controlling software needs to restart tracking because ASCOM doesn't allow slewing (e.g., to slew back inside the Horizon limits) and other operations while tracking is disabled.Gotcha. Thanks Ray. I was thinking that when you check the box to stop tracking past the horizon, that it would actually stop the mount from tracking below a horizon. I woke up the other morning and my scope was very close to crashing into a wall because it had tracked well past what I had intended. Good to know. |
|
Roland Christen
In your picture, which way is N-S and E-W? (RA direction?)
Roland
-----Original Message-----
From: Klaus Völler <Klaus.Voeller@...> To: main@ap-gto.groups.io Sent: Sun, Nov 20, 2022 3:54 am Subject: Re: [ap-gto] slew warning APPM with Mach2
Hi Chris,
thank you for your answer. I am using a QHY600M with 2x2 binning on a TEC140FL for "plate solving". The green dots have been solved successfully. In case of errors, the image does not really show elongated stars, but looks like star trails.... and as you can see from my attached images (first mail), the faulty points are all within the horizon boundary. Are not on the edge of the boundary but slightly offset inward and can be seen on both sides west/east. Both axes are in balance. All screws checked. Before I called APPM, I also did a polar alignment (deviation 6''). This topic already existed in earlier postings and Rolando mentioned that the mount does not come to rest there, it pumps.... I already made a model half a year ago with the same equipment. No faulty points. Attached is an example picture from the camera where the plate solve failed. regards Klaus Am 20.11.22 um 02:25 schrieb Chris
White:
Welcome Klaus!
What camera are you using? I had failed solves on my model with IMX455, and when I went to a 50% size frame the problem went away. Or are you saying that those failed solves have bad captures with elongated stars? As far as the dashed lines go, I get that if my mount hits a horizon limit. Despite having APCC set to not track past a horizon limit, it will stop for the exposure that hits the limit and then continue tracking on the next exposure. I wonder if there is a bug in APCC as I dont understand how my capture software can override the mount horizon limit. I havent asked about it yet here as I just found the issue. -- Roland Christen Astro-Physics |
|
Klaus Völler
RA should be top-down or bottom up... Each fail have the same
startrail direction.. all other had round stars..
toggle quoted message
Show quoted text
One more little thing... The "clutch knobs" of the RA axis are hand-tightened. When I move the counterweight shaft back and forth very slightly, I notice minimal play in the axis. I am not sure if this is important. regards Klaus Am 21.11.22 um 16:48 schrieb Roland
Christen via groups.io:
|
|
Roland Christen
Your capture software is taking pictures while the mount is still slewing to the end point. You will have to set a longer settle time in that software so it takes pictures when the mount has stopped slewing and is beginning to track.
Slewing to a star occurs in several motions. First is a short acceleration mode where the axis goes from zero to 1800x. Then it slews at 1800x to a point where it begins a deceleration phase. At the end of deceleration there is a very short centering move which takes approximately 100 milliseconds. It begins to track immediately without delay.
If you have an eyepiece, look thru it and slew to a star. See how it gets there and starts tracking. Unless one of the pulleys on the motor shaft or on the worm shaft is loose, the tracking will begin right away with no delay after a slew and center move. The pulleys each have 2 set screws, and they must be tight. We have never experienced a Mach2 mount with loose pulleys, so it would be very unusual.
Until you look thru an eyepiece and verify that your mount starts tracking immediately at the end of a slew, you will never be confident in the performance of the mount.
Roland
-----Original Message-----
From: Klaus Völler <Klaus.Voeller@...> To: main@ap-gto.groups.io Sent: Mon, Nov 21, 2022 5:13 pm Subject: Re: [ap-gto] slew warning APPM with Mach2
RA should be top-down or bottom up... Each fail have the same
startrail direction.. all other had round stars..
One more little thing... The "clutch knobs" of the RA axis are hand-tightened. When I move the counterweight shaft back and forth very slightly, I notice minimal play in the axis. I am not sure if this is important. regards Klaus Am 21.11.22 um 16:48 schrieb Roland
Christen via groups.io:
In your picture, which way is N-S and E-W?
(RA direction?)
Roland
-----Original Message-----
From: Klaus Völler <Klaus.Voeller@...> To: main@ap-gto.groups.io Sent: Sun, Nov 20, 2022 3:54 am Subject: Re: [ap-gto] slew warning APPM with Mach2 Hi Chris,
thank you for your answer. I am using a QHY600M with 2x2 binning on a TEC140FL for "plate solving". The green dots have been solved successfully. In case of errors, the image does not really show elongated stars, but looks like star trails.... and as you can see from my attached images (first mail), the faulty points are all within the horizon boundary. Are not on the edge of the boundary but slightly offset inward and can be seen on both sides west/east. Both axes are in balance. All screws checked. Before I called APPM, I also did a polar alignment (deviation 6''). This topic already existed in earlier postings and Rolando mentioned that the mount does not come to rest there, it pumps.... I already made a model half a year ago with the same equipment. No faulty points. Attached is an example picture from the camera where the plate solve failed. regards Klaus Am 20.11.22 um
02:25 schrieb Chris White:
Welcome Klaus!
What camera are you using? I had failed solves on my model with IMX455, and when I went to a 50% size frame the problem went away. Or are you saying that those failed solves have bad captures with elongated stars? As far as the dashed lines go, I get that if my mount hits a horizon limit. Despite having APCC set to not track past a horizon limit, it will stop for the exposure that hits the limit and then continue tracking on the next exposure. I wonder if there is a bug in APCC as I dont understand how my capture software can override the mount horizon limit. I havent asked about it yet here as I just found the issue. -- Roland Christen Astro-Physics -- Roland Christen Astro-Physics |
|
Klaus Völler
Hello Roland,
toggle quoted message
Show quoted text
many thanks for the description... when I first tried to create a model nine days ago, the settle time was set to 2 seconds. For my second try on 11/19, I then set this up to 6 seconds. The difference were marginal... only 3 points more solved (from 86 Points where 60 good and 27 bad in case of 6 sec settle time and 800x slew rate) In my opinion 6 seconds are a long time but maybe i'm wrong. I will have a next try thursday to friday if the weather forcast is correct. The firmware is updated now (VCP5-P02-15). Are there other things i can do? Thanks and regards Klaus Am 22.11.22 um 00:37 schrieb Roland
Christen via groups.io:
|
|
Hi Klaus Have you enabled "require high accuracy slews"? I found that helped me also of course make sure you are on the latest firmware On Mon, Nov 21, 2022 at 11:37 PM Klaus Völler <Klaus.Voeller@...> wrote:
--
Brian Brian Valente astro portfolio https://www.brianvalentephotography.com/astrophotography/ portfolio brianvalentephotography.com |
|
Klaus Völler
Hi Brian,
toggle quoted message
Show quoted text
thanks for your reply.. yes i tried with high accuracy slews. There are minimal less errors but the main problem with slew warning did not disappear. regards Klaus Am 22.11.22 um 08:42 schrieb Brian
Valente:
|
|
Andrea Lucchetti
Hi, I don’t know about the messages but if the problem is tied with plate fails I would check the plate solving software parameters. I use ASTAP and got a huge improvement playing with the parameters, three in particular: - accuracy: choose the fine method - field: use only a portion of the corrected field - ensure you are not double binning: there is a control for this in ASTAP AND niNa for example ( I was binning 4x in total…) Andrea Il giorno mar 22 nov 2022 alle 09:03 Klaus Völler <Klaus.Voeller@...> ha scritto:
|
|
Looking at your plate solve image, I wonder if you have the same issue that I experienced with my Mach2. It was due to encoder settings needing more dampening as sometimes after completion of a goto it would judder back and forth. Here is an example https://www.youtube.com/watch?v=5kTmXjHhtVk
Astro-Physics assisted me in configuring more encoder dampening. |
|
Klaus Völler
Hi Brent,
toggle quoted message
Show quoted text
yes i saw your topic...Was this the case with your mount from the beginning? I own the mount around 1 1/2 year and it works from beginning like a charm. Now i'm a little bit suprised and hope it is (easy) solvable. regards Klaus Am 22.11.22 um 15:59 schrieb Brent
Boshart:
Looking at your plate solve I wonder if you have the same issue that I experienced with my Mach2. It was due to encoder settings needing more dampening as sometimes after completion of a goto it would judder back and forth. Here is an example https://www.youtube.com/watch?v=5kTmXjHhtVk |
|
Roland Christen
Are there other things i can do? Look thru the scope, slew to a star and see what happens at the end of the slew. Use an eyepiece!
Rolando
-----Original Message-----
From: Klaus Völler <Klaus.Voeller@...> To: main@ap-gto.groups.io Sent: Tue, Nov 22, 2022 1:37 am Subject: Re: [ap-gto] slew warning APPM with Mach2
Hello Roland,
many thanks for the description... when I first tried to create a model nine days ago, the settle time was set to 2 seconds. For my second try on 11/19, I then set this up to 6 seconds. The difference were marginal... only 3 points more solved (from 86 Points where 60 good and 27 bad in case of 6 sec settle time and 800x slew rate) In my opinion 6 seconds are a long time but maybe i'm wrong. I will have a next try thursday to friday if the weather forcast is correct. The firmware is updated now (VCP5-P02-15). Are there other things i can do? Thanks and regards Klaus Am 22.11.22 um 00:37 schrieb Roland
Christen via groups.io:
Your capture software is taking pictures
while the mount is still slewing to the end point. You will
have to set a longer settle time in that software so it
takes pictures when the mount has stopped slewing and is
beginning to track.
Slewing to a star occurs in several motions.
First is a short acceleration mode where the axis goes from
zero to 1800x. Then it slews at 1800x to a point where it
begins a deceleration phase. At the end of deceleration
there is a very short centering move which takes
approximately 100 milliseconds. It begins to track
immediately without delay.
If you have an eyepiece, look thru it and
slew to a star. See how it gets there and starts tracking.
Unless one of the pulleys on the motor shaft or on the worm
shaft is loose, the tracking will begin right away with no
delay after a slew and center move. The pulleys each have 2
set screws, and they must be tight. We have never
experienced a Mach2 mount with loose pulleys, so it would be
very unusual.
Until you look thru an eyepiece and verify
that your mount starts tracking immediately at the end of a
slew, you will never be confident in the performance of the
mount.
Roland
-----Original Message-----
From: Klaus Völler <Klaus.Voeller@...> To: main@ap-gto.groups.io Sent: Mon, Nov 21, 2022 5:13 pm Subject: Re: [ap-gto] slew warning APPM with Mach2 RA should be top-down or bottom up... Each fail
have the same startrail direction.. all other had round
stars..
One more little thing... The "clutch knobs" of the RA axis are hand-tightened. When I move the counterweight shaft back and forth very slightly, I notice minimal play in the axis. I am not sure if this is important. regards Klaus Am 21.11.22 um
16:48 schrieb Roland Christen via groups.io:
In your picture, which way is N-S
and E-W? (RA direction?)
Roland
-----Original Message-----
From: Klaus Völler <Klaus.Voeller@...> To: main@ap-gto.groups.io Sent: Sun, Nov 20, 2022 3:54 am Subject: Re: [ap-gto] slew warning APPM with Mach2 Hi Chris,
thank you for your answer. I am using a QHY600M with 2x2 binning on a TEC140FL for "plate solving". The green dots have been solved successfully. In case of errors, the image does not really show elongated stars, but looks like star trails.... and as you can see from my attached images (first mail), the faulty points are all within the horizon boundary. Are not on the edge of the boundary but slightly offset inward and can be seen on both sides west/east. Both axes are in balance. All screws checked. Before I called APPM, I also did a polar alignment (deviation 6''). This topic already existed in earlier postings and Rolando mentioned that the mount does not come to rest there, it pumps.... I already made a model half a year ago with the same equipment. No faulty points. Attached is an example picture from the camera where the plate solve failed. regards Klaus Am
20.11.22 um 02:25 schrieb Chris White:
Welcome Klaus!
What camera are you using? I had failed solves on my model with IMX455, and when I went to a 50% size frame the problem went away. Or are you saying that those failed solves have bad captures with elongated stars? As far as the dashed lines go, I get that if my mount hits a horizon limit. Despite having APCC set to not track past a horizon limit, it will stop for the exposure that hits the limit and then continue tracking on the next exposure. I wonder if there is a bug in APCC as I dont understand how my capture software can override the mount horizon limit. I havent asked about it yet here as I just found the issue. -- Roland Christen Astro-Physics -- Roland Christen Astro-Physics -- Roland Christen Astro-Physics |
|
Brent Boshart
On Tue, Nov 22, 2022 at 11:02 AM, Klaus Völler wrote:
I think it was probably from the beginning but did not really notice it until one time when I did not have the mount well balanced which exacerbated the issue. On further investigation, I found that sometimes despite elongated/streaked stars it plate-solved anyway - although I'm sure with not the same accuracy. I was not getting the results that I hoped for using models and tracking unguided. All is great now after resolving the judder. |
|
Klaus Völler
Thanks for your reply... waiting now for better weather to
investigate further as proposed
toggle quoted message
Show quoted text
Am 23.11.22 um 07:30 schrieb Brent
Boshart:
On Tue, Nov 22, 2022 at 11:02 AM, Klaus Völler wrote: |
|
Klaus Völler
Hi Rolando,
toggle quoted message
Show quoted text
yesterday I had the opportunity to test after my Firmware update. With all stars that I have approached and observed, the mount came to a standstill directly after approaching the target. There were no further movements to observe... I then created another model with 86 points and this time I had "only" 16 points where I got the message "Slew Warning". The behaviour was the same. I get star trails if this message occur. I raised the settletime to 8 seconds. Somehow I am just as smart as before.... It seems that only with certain constellations this message comes. I made second model to be sure, but the number of slew warnings remained the same at 16. The points were only slightly different. On the east side they are at the outer edge and on the west side deep down in the south (see attachments). At the moment I have no more ideas. Hints are welcome. regards Klaus Am 22.11.22 um 17:34 schrieb Roland
Christen via groups.io:
|
|