Maybe you just need a fresh install of PHD2? +1 And go through a new connection wizard to make sure no typo or something missed. By the way.. All AB's users are waiting for you to say "Solved"  Goodluck
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Hi, I just tried it and reinstalled it but nothing worked…  I'm going to ask on the google group and let you know if I get it running. Luke
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
By the way, I have been able to figure out why it said MountGuidingEnabled = flase.
This message occurs every time I start the guiding assistant. That unfortunately means that it has nothing to do with my problem. In the small text at the top it always says that guiding is enabled.
Let's hope that the google group can find a solution…
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Well, here I am again and I already have one hopefully very good tip. I don't know why - I used the default settings (because of reinstall) - however, my Min-Move was set to 20 (default!). When running the guiding assistant it even said to turn it back to 0.12 and 0.19, but I didn't wanna do something that I don't know what it's doing, so I just left it like it was.
This means, that the mount wouldn't move until the star has drifted 20 pixels.
I hope that that's it, but I'm going to inform you if there are any other issues/solutions.
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Lukas Bauer:
Well, here I am again and I already have one hopefully very good tip. I don't know why - I used the default settings (because of reinstall) - however, my Min-Move was set to 20 (default!). When running the guiding assistant it even said to turn it back to 0.12 and 0.19, but I didn't wanna do something that I don't know what it's doing, so I just left it like it was.
This means, that the mount wouldn't move until the star has drifted 20 pixels.
I hope that that's it, but I'm going to inform you if there are any other issues/solutions. You meant it was set to 0.20 pixels OR 20 pixels ? Default never come with 20, it comes with 0.20 I suppose !
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Yes, you read correctly - 20 pixels. They also said that this is never default, what I also can't imagine.
But i don't remember even touching the advanced settings, so I have no idea why that was set to 20.
And what I also don't understand is, why it was still set to 20 after deinstalling and reinstalling PHD2.
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Lukas Bauer:
Yes, you read correctly - 20 pixels. They also said that this is never default, what I also can't imagine.
But i don't remember even touching the advanced settings, so I have no idea why that was set to 20.
And what I also don't understand is, why it was still set to 20 after deinstalling and reinstalling PHD2. What is the PHD2 version?
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
It's version 2.6.13. (should be the newest one)
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Lukas Bauer:
Well, here I am again and I already have one hopefully very good tip. I don't know why - I used the default settings (because of reinstall) - however, my Min-Move was set to 20 (default!). When running the guiding assistant it even said to turn it back to 0.12 and 0.19, but I didn't wanna do something that I don't know what it's doing, so I just left it like it was.
This means, that the mount wouldn't move until the star has drifted 20 pixels.
I hope that that's it, but I'm going to inform you if there are any other issues/solutions. Well hopefully that's it. I thought of mentioning it to you, but I read fast and thought it was 0.2 pixels too. 20 pixels is huge. So your star will drift and PHD will not correct because it does not have to, each drift sequence is less than this limit.
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Hi, I am not able to say completely solved yet, but partially solved. With the new and correct settings (Min Move) the mount is able to guide. But only for a short amount of time because then there are those huge spikes in Ra and Dec which you can see in my Log files: https://openphdguiding.org/logs/dl/PHD2_logs_Ej79.zipI don't know why this happens because this can't be a mechanical issue because the errors only occur when guiding, but not when just normally tracking. I also noticed that when running APT simultaneously the problem gets much worse and the spikes occur every 1-2 min. I took some test exposures the night before and out of 60 exposures (2 min each) I was only able to use 39. The error mostly occured 10-20 sec before the exposure finished - but of course they also happend randomly during the exposures too. In the guide log you can see that when I closed APT at 0:30 a.m. The spikes only occured every 10-20 min. This supports the fact that this is not a mechanical issue because with APT they occure more frequently and without a lot less frequently. A second strange thing I noticed way that at 22:20 p.m. yesterday the mount just started slowly slewing to somewhere - I still don't know why it did that. By the way, you can ignore the end of the guidelog - that's when a house was in the way of the object, so obiously there is no star to guide on. I also switched back to EQMOD, because with GSS i very often got a error message that the PulseGuide command failed which isn't the case with EQMOD. Although I don't like it because the controls always have a bit of a delay, it's better than nothing. Do any of you know what the cause of this problem could be? Appreciate every bit of help! Lukas
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Can you answer these questions please: 1- What is the PHD2 language ? (sometimes I read English sometimes another language !!) 2- What power source do you use ? how much is your input Voltage?? is it stable?? did you test that? Have you ever change it with another power source? 3- What about your cable managements? is there any Dragging or snags?? can you send a clear image for your setup showing cables routes ? 4- Did you try to change the USB cables? how many times did you change them? Once or twice? 5- Did you try to use another PC or laptop? How old is your pc? Some USB ports getting old or faulty and can be ON/OFF loose connection. 6- How do setup your tripod on the ground? grass, soil or concrete? AND do you use something under the legs or they are directly on the ground? (The tripod is essentially to be stable and one tiny move/hit by you or animals/birds can produce a huge spike in guiding !! and it happened to me and friends  . 7- How loose/tight are the screws? that including: guiding camera rings/adapters ? main camera rings/adapters, the telescope rings/adapters, mount connection to tripod and Az Alt bolts locks, ALL MUST BE TIGHT AND SNUG. 8- Have ever face any disconnection of cameras or mount and you have to reconnect them again? how many times in one session? 9- Do you use any power or USB hub? did you try to change it? Sorry about lots of questions, But we have to diagnose every thing on the way. Please answer them by write your answers by starting with the question number 1,2,3,4,…… Goodluck!
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Hi, no worries, I am glad to answer your questions. 1- I usually set the PHD2 language to English, but I chenged from 2.3.16 dev5 (newest version) to 2.3.16 dev1, because my guide star profile/preview lost a lot of resolution overnight and in the PHD2 google groups I read that this happend to somebody else before and he got it fixed by changing back to the dev1 version. This was also the case with my camera, as soon as I switched back, the star profile looked great (normal) again. But with the dev1 version, I was unable to change the language from German to English (it was grayed out). I just looked again and now I can change it, so from now on everything is in English. 2- I use a common AC adapter - output: 12 V / 5 A. This is the adapter: https://www.amazon.de/LEDMO-Netzteil-Transformator-Ladeger%C3%A4t-lichtband/dp/B07PGLXK4XMy input voltage is the usual 230 V from the power line, converted with the above mentioned adapter to 12 V. I can only assume that the output voltage is stable and electronically stabilized to 12 V, but I have not measured it yet. I have not tried to change the power source, but the power supply I use is not the original power supply, because the original power supply had a cable break and was unusable. Therefore I bought this one with identical specifications. But I don't think that this is related to guiding, because the guide camera is not connected to a external power supply, just with a USB A to USB B cable, by the laptop. 3- Cable management is good, there are no cable drags or snags. I can send you a photo as soon as I set it up again. (Maybe this evening) 4- I did not try to change the cables yet. But tonight I can change out the USB A to USB B cable to the camera. I am unable to change the mount connection cable, but it is also very new, so there shouldn't be any problems with it. It is made by Pegasus and has the according adapter for my mount, so there souldn't be any troubles here. 5- My laptop is now about 3 years old, so also pretty new. I is a Acer Predator helios 300 and should easily be able to do the required tasks. I also read that you have to turn off the energy saving in the device manager for the USB ports, so these settings should also not cause any problems. The baud rate is set to 9600 and is matches with EQMOD and the port setting. 6- My tripod is directly connected to a solid concrete pavement/floor. It is really stable and there are no animals involved because the error also occurs when I am sitting outside and testing it. 7- Thanks for mentioning that, I just checked my guide scope, and it actually has a little bit of free movement, when using the helical focuser. This is my guide scope: https://lacerta-optics.com/Guidescope50_50mm-Helical-GuideScope-mit-20mm-einstellbarerI am going to try and not use the helical focuser tonight and see if I can get into focus because if I thighten it all the way to one end it stays in place. Anywhere between that it is not totally fixed. All the other screws are pretty thight. But I don't know if that's the issue, because it would need a very strong wind to push it out of place, which is not the case. Furthermore the spikes only occur in Ra and Dec separately. With wind there would be another comibnation error every time, and both axis at the same time. Also, the problem gets worse when imaging with my main camera as you will see in my next post. 8- I very rarely need to reconnect my eqiupment during the night. I would even call it unlucky if I had to reconnect my camera just once during the night. 9- No I do not use any power or USB hub. Thanks! Lukas
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Here are the log files from yesterday (at that point PHD2 was still set to German, because language setting was grayed out): https://openphdguiding.org/logs/dl/PHD2_logs_4XmD.zipHere are the different "stages" of the night: 1. The beginning: I ran the calibration as usual and set the mount just a tiny little bit off balance in the Ra axis (east heavy) and planned to stay just in the eastern half of the sky, to reduce Ra backlash, as I found out through a quick research. Immediately after running the calibration assistant I tried guiding with no other software open than PHD2 and EQMOD. That was also my most successful try that night. There were only two spikes for 1.5 hours which I was really happy with. But even these spikes shouldn't be there. However this try was without any camera software open - but to take pictures I need to control the camera. 2. At 22:47 p.m. I slewed the mount via APT to Alpheratz which was quite high in the eastern sky at that time. I left the telescope east heavy, because the first try seemed kind of successful. After slewing to Alpheratz I closed APT and let PHD2 guide for a while - again only EQMOD and PHD2 open. This try also seemed reasonably good, but there were still two huge Ra spikes. 3. At 23:41 p.m. I additionally just opened APT. I didn't connect anything, I just started APT. And at that point the problem started to only get worse. Even with APT just opened, there were now eight spikes instead of two during a shorter period of time. The telescope was still east heavy. 4. At 0:37 a.m. I connected the mount and camera to APT. I didn't control anything nor take pictures, I just connected it. You can already see that despite the short time period of 30 min there were a lot more spikes than usual, even to a point where it just completely lost the star. The telescope was still east heavy. 5. At 1:12 a.m. I slewed to Hamal, because Alpheratz was getting too high and as I said, I wanted to stay in the eastern half. At this point I started guiding again and additionally started to take exposures with my camera. As you can see, despite the short time period there were now a lot more spikes than before. When PHD2 lost the star completely again I stopped and started guiding again, but that didn't help very much. The telescope was still east heavy. 6. At 2:18 a.m. I slewed to Menkar, because Hamal got too high. I also disconnected the camera from APT and only left the mount connected to APT. Immediately there is a big improvement. Despite two huge Dec spikes it pretty much ran without problems. The telescope was still east heavy. 7. At 3:02 a.m. I additionally connected the camera to APT again, but did not take exposures. And at half the guiding time of No. 6 there were more than double the amount of errors just because I connected the camera to APT. The telescope was still east heavy. 8. At 3:28 a.m. I disconnected the camera, slewed to Aldebaran and put my counterweight down, which made the mount pretty west (!!!) heavy. To my surprise and against the explanations of the internet my guiding actually was just a bit better than compared to east heavy. There was only a single error. The mount was connected to APT, the camera not. 9. At 3:54 a.m. I reconnected the camera to APT again. As you can see the problem gets worse again. 10. At 4:35 a.m. the sky started to birhgten again, so I figured that I am just going to try to slew to a target, guide and take some quick exposures. I started with 300 sec (5min), but 30 sec before the exposure finished the mount had the error (Guiding started at 4:44, error occured at 4:48 - this pretty much aligns with the said little less than 5 min). I then thought that maybe this was just a coincidence and tried 120 seconds. But again the error started in the second half of the exposure. Then I tried to go even shorter, 60 sec. But again right before the end the error came in. Then I tried 30 sec and the error came again, just right at the beginning. I tried 30 sec again, but the error returned right before the exposure finished again.  All of this trying indicates that this cannot be a mechanical issue, because the extent of the error depends on the used software and connected devices, or if these devices are doing something or not. Does anybody know what could be the cause of this very strange behaviour? Thanks in advance! Lukas
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
By the way..
How long did you face this issue with the mount? Was it working well before?
What changes did you do?
With chronic issues we can not eliminate something till we tried.. In technical world many things happened even they look no logic.
Power interruption or not enough voltages can make weird things to equipment, One affected wire inside the USB can cause ON/OFF failures although the USB seem to be working.
Anyway.. My suspicions:
1- Cables >> Change them to eliminate them from the game
2- PC software issue >> you can try another PC to eliminate the pc from the game.
Keep in mind in some rare cases there will be double faults or more.. so be sure not to solve one but the other is still.. So you put back the 1st one (cables) and solve the 2nd one .. IT WILL NOT BE SOLVED THE ISSUE..
Goodluck!
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Hi Lukas,
The good thing is that your mount is guiding correctly in between the spikes. I would lower the aggressivity on RA and Dec 50%. It's unclear where the spikes come from, but I don't think they start with a strong correction from Phd2. What you could test is just following the tracking in Phd with the guiding off. See if they repeat. But as you said, with Phd only your guiding looked pretty stable.
Is everything tight on the system? No hanging cables, guiding camera well tightened ? When you change the scope position, everything can shift or tilt and have an effect. Check for latest drivers and com conflicts. Anyway, you made some big progress since the first time.
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Lukas, Is it resolved?
What was the issue?
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Hello,Thanks for asking! No, I have not been able to solve my issue. In the google group ( https://groups.google.com/g/open-phd-guiding/c/0LTcrtHbFr0), which you guys recommended to me, you can see my latest post how everything's going. In the next clear night I will try a second PC to see if the PC is causing the troubles. Lukas
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Hello, I tried to use another laptop #2 for my guiding. I tested it on Oct. 6th (log files are uploaded). With the other laptop #2 everything worked fine as it should. I then compared the settings and the only setting which was different was the search region for the stars, which actually was lower on the other computer #2 (the one which worked). With the now compared and therefore same settings I tried the mount again with my laptop #1 (the one which doesn't work) tonight. As already expected it didn't work. The error still showed up. I also tried to reinstall PHD2. But as I had already found out a few months ago, when deinstalling, downloading and reinstalling it again, not all settings were removed completely. For example my profile was still available after reinstalling it. Do you have any idea what I could try next? I suspect it has something to do with how the computer processes the programm. That's why I would also like to know, how to fully remove every data so that PHD2 can't find it again after reinstalling. That's how I could do a manual "hard" reset to start from 0 again. Log Files: https://openphdguiding.org/logs/dl/PHD2_logs_SH8G.zipAny help is appreciated! Thanks in advance! Lukas
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Hello, I am here to say a big thank you to everyone who supported me and helped me with my problem regarding guiding. I also want to let you know that my problem is finally solved! And for anyone, who might encounter similar problems as I did, here is what I did to get my setup running: After pretty much giving up on using a laptop with PHD2 to control my equipment because it wasn't workingt, I decided to buy a Raspberry Pi 5 to try and control everything with the small computer. I followed this tutorial: https://www.astrofriend.eu/astronomy/projects/project-kstars-raspberrypi5/02-project-kstars-raspberrypi5.html (Many thanks to whoever wrote this) In this tutorial you can find the correct way to install and run Kstars/Ekos/Indi. Since I want to use "Raspberry Pi Connect" to control my Raspberry Pi I did not install anything regarding Real VNC. After installation, I searched for tutorials on how to use the program and found a few on YouTube which showed exactly how to set everything up. Once set up, I tried everything for the first time only to find, that the calibration for guiding failed. I got an error message telling me that my mount may have too much backlash. Since I had already checked my backlash once, I thought that this couldn't be a problem, but after checking it again, I found out that I was able to remove the backlash almost completely (following a YouTube tutorial - https://www.youtube.com/watch?v=1hzAh6ro8YU) - Thanks "Cuiv, the lazy geek"! After adjusting the backlash I tried it again and it finally worked perfectly! I had a constant guide error of about 0.5"-0.6". Sometimes even close to 0.3" (with a relatively light equipment ~6kg). I used the integrated guider in Ekos (not PHD2). Furthermore, I also tried framing an object using PlateSolving, which also worked smoothly. Now I have a better setup than I was aiming for, because I don't even have to put my laptop outside - just the Raspberry Pi 5. I would definitely recommend setting up a Raspberry Pi for astrophotography. There are also complete gadgets like StellarMate which use the same program as my Raspberry Pi, but even there the cheapest model costs 300€. I don't know if the StellarMate has any other special features which justify the price. But I bought a Raspberry Pi 5 set (including case, fan, SD-card) for ~130€ which does everything that I need it to do with excellent performance. Once again, a huge thank you again to everyone who helped me and gave me tips! Lukas
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Lukas Bauer:
Hello,
I am here to say a big thank you to everyone who supported me and helped me with my problem regarding guiding.
I also want to let you know that my problem is finally solved!
And for anyone, who might encounter similar problems as I did, here is what I did to get my setup running:
After pretty much giving up on using a laptop with PHD2 to control my equipment because it wasn't workingt, I decided to buy a Raspberry Pi 5 to try and control everything with the small computer. I followed this tutorial: https://www.astrofriend.eu/astronomy/projects/project-kstars-raspberrypi5/02-project-kstars-raspberrypi5.html (Many thanks to whoever wrote this)
In this tutorial you can find the correct way to install and run Kstars/Ekos/Indi. Since I want to use "Raspberry Pi Connect" to control my Raspberry Pi I did not install anything regarding Real VNC. After installation, I searched for tutorials on how to use the program and found a few on YouTube which showed exactly how to set everything up.
Once set up, I tried everything for the first time only to find, that the calibration for guiding failed. I got an error message telling me that my mount may have too much backlash. Since I had already checked my backlash once, I thought that this couldn't be a problem, but after checking it again, I found out that I was able to remove the backlash almost completely (following a YouTube tutorial - https://www.youtube.com/watch?v=1hzAh6ro8YU) - Thanks "Cuiv, the lazy geek"! After adjusting the backlash I tried it again and it finally worked perfectly!
I had a constant guide error of about 0.5"-0.6". Sometimes even close to 0.3" (with a relatively light equipment ~6kg). I used the integrated guider in Ekos (not PHD2).
Furthermore, I also tried framing an object using PlateSolving, which also worked smoothly.
Now I have a better setup than I was aiming for, because I don't even have to put my laptop outside - just the Raspberry Pi 5. I would definitely recommend setting up a Raspberry Pi for astrophotography. There are also complete gadgets like StellarMate which use the same program as my Raspberry Pi, but even there the cheapest model costs 300€. I don't know if the StellarMate has any other special features which justify the price. But I bought a Raspberry Pi 5 set (including case, fan, SD-card) for ~130€ which does everything that I need it to do with excellent performance.
Once again, a huge thank you again to everyone who helped me and gave me tips!
Lukas very happy for you.. better to check the backlash every 6 months or so.. CS!
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Bogdan Borz:
Second, your declination is not 0. Don't tell me you live at the Equator : ). Put the dec where you image from, if not, it's a false data location for your calibration. Vitis Austria is 48°. So put this in the setting. Your Calibration Declination has nothing to do with your locations Latitude. Calibration Declination is the declination angle at which the telescope is pointed during the calibration, and for best results, you should be pointed to 0° Declination +/- 5° (meaning, exactly East), and near the Meridian. Its important to either have a very good understanding of how all the settings in PHD2 work if you're going to try to assist people to resolve their issues. If you don't know 100%, you may well be causing more harm than good by sharing your unfounded opinion.
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Alex Nicholas:
Bogdan Borz:
Second, your declination is not 0. Don't tell me you live at the Equator : ). Put the dec where you image from, if not, it's a false data location for your calibration. Vitis Austria is 48°. So put this in the setting.
Your Calibration Declination has nothing to do with your locations Latitude.
Calibration Declination is the declination angle at which the telescope is pointed during the calibration, and for best results, you should be pointed to 0° Declination +/- 5° (meaning, exactly East), and near the Meridian.
Its important to either have a very good understanding of how all the settings in PHD2 work if you're going to try to assist people to resolve their issues. If you don't know 100%, you may well be causing more harm than good by sharing your unfounded opinion. Of course declination and latitude are interrelated, the altitude of the ecliptic in the sky (dec 0) varies according to your location latitude. I wonder where were you when we needed you most. Thanks for your smart advice. I was thinking about Latitude not declination in the setting, so it was a confusion from my part when I wrote "dec". Countries or locations do not have declinations. Second, as I told Lukas afterwards, the calibration is best done around the ecliptic (Dec 0) and the southern meridian. Plus, you do not enter the dec in the setting you point wherever you want to calibrate or guide, which determines the dec position or RA position. So before jumping to conclusions, try to reflect a little bit.
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
Lukas Bauer:
Hello,
I am here to say a big thank you to everyone who supported me and helped me with my problem regarding guiding.
I also want to let you know that my problem is finally solved!
And for anyone, who might encounter similar problems as I did, here is what I did to get my setup running:
After pretty much giving up on using a laptop with PHD2 to control my equipment because it wasn't workingt, I decided to buy a Raspberry Pi 5 to try and control everything with the small computer. I followed this tutorial: https://www.astrofriend.eu/astronomy/projects/project-kstars-raspberrypi5/02-project-kstars-raspberrypi5.html (Many thanks to whoever wrote this)
In this tutorial you can find the correct way to install and run Kstars/Ekos/Indi. Since I want to use "Raspberry Pi Connect" to control my Raspberry Pi I did not install anything regarding Real VNC. After installation, I searched for tutorials on how to use the program and found a few on YouTube which showed exactly how to set everything up.
Once set up, I tried everything for the first time only to find, that the calibration for guiding failed. I got an error message telling me that my mount may have too much backlash. Since I had already checked my backlash once, I thought that this couldn't be a problem, but after checking it again, I found out that I was able to remove the backlash almost completely (following a YouTube tutorial - https://www.youtube.com/watch?v=1hzAh6ro8YU) - Thanks "Cuiv, the lazy geek"! After adjusting the backlash I tried it again and it finally worked perfectly!
I had a constant guide error of about 0.5"-0.6". Sometimes even close to 0.3" (with a relatively light equipment ~6kg). I used the integrated guider in Ekos (not PHD2).
Furthermore, I also tried framing an object using PlateSolving, which also worked smoothly.
Now I have a better setup than I was aiming for, because I don't even have to put my laptop outside - just the Raspberry Pi 5. I would definitely recommend setting up a Raspberry Pi for astrophotography. There are also complete gadgets like StellarMate which use the same program as my Raspberry Pi, but even there the cheapest model costs 300€. I don't know if the StellarMate has any other special features which justify the price. But I bought a Raspberry Pi 5 set (including case, fan, SD-card) for ~130€ which does everything that I need it to do with excellent performance.
Once again, a huge thank you again to everyone who helped me and gave me tips!
Lukas That sounds great Lukas. And practical too. So it must have been the interaction of the laptop with mount. CS !
|
You cannot like this item. Reason: "ANONYMOUS".
You cannot remove your like from this item.
Editing a post is only allowed within 24 hours after creating it.
You cannot Like this post because the topic is closed.
Copy the URL below to share a direct link to this post.
This post cannot be edited using the classic forums editor.
To edit this post, please enable the "New forums experience" in your settings.
