I did try to set a backlash and tried different values to no avail. May be a hardware problem but I just tried NINA last night and despite some issues due to my lack of experience with it I was able to get running after 3 hours only. I could not get my laptop to last long enough as I have no power other than batteries at the location and that was my reason to use a Raspberry Pi and EKOS to begin with. It's so much more portable. I may try it again in the future when I have more knowledge.
Read More...
No. I don't think is that but thank you.
After a month of trying INDI/KSTARS/EKOS I think I will move back to the Windows platform. Too many nights trying to make the focus work, the guider work, the sequence to work after already having spend a couple weeks getting the OS loaded and running for someone not familiar with Linux. I find the options in the interface not clear for a new user with not enough knowledge about astronomy and the documentation limited. Too much time and not getting where I want to be which is capturing images without glitches at least most of the time. A bit sad because I really like the idea of using my Raspberry Pi and it simplifies cable management.
Read More...
Hi,
I've been working out autofocus with my ZWO EAF + ZWO ASI183GT + TS 76EDPH scope but I am having some issues.
1. Algorithm: I have tried many combinations. Autoselect start and subframe works fast using SEP and iterative and works well while I am paying attention and manually start from a good rough focus but left alone during an automated sequence it fails. Full field seems to work better when left alone with a step of 25 if focus is close to correct but sometimes it goes off in the wrong direction, loses focus then fails to detect stars (because of going completely out of focus) and it aborts the sequence. Any suggestions as to what algorithm, initial step size, etc.?
2. While watching the curve it looks like the focuser moves further going back than going in. I suspect because the motor has to work against gravity. Will adding some steps to the backlash option help with this?
3. During a sequence the measured HFR with a 5% threshold triggers the autofocus every single frame captured. Should I increase the threshold or there is something else than I am missing? I would like for the autofocus to check every frame for focus but only trigger a focus routine when appropriate and not every time.
4. I have tried to determine an offset for each filter so that I only need to focus using the luminance filter but the values measured for the steps are different every time I run an autofocus sequence. Even for the same filter it will have a different reading every time I perform autofocus. So I can't establish a consistent offset. Is there any work around for this.
Thanks in advance for your help.
Read More...
I would say that the stars look round.
My RMS error looks to be around 1 sometimes 1.5 others 0.8
Read More...
Finally got a clear night to try. I increased the max pulse to 2500 and the number of pulses to 6. Now it calibrates successfully every time. The chart looks like this image. Looks like the DEC reverse is still sluggish but it seems to work.
Am I using to high of a max pulse or number of pulses? Is there a more scientific way to determine the ideal values?
Read More...
I am wondering if I have a problem with the settings of the internal guider or if it is related to my mount. Over several night I have failed calibrations specifically when DEC is drifting in reverse. It gets stuck and does not move. On occasions it does move and it calibrates but I get this calibration chart in the image.
I have a SW EQ6-R Pro which is brand new. Could this be DEC backlash and how to fix it?
Read More...
I figured it out. It was my mistake. I was typing http:/RR.RR.RR.RR/ in the field for the IP address. The way EKOS interprets that is to add the port number to the IP address I typed resulting in: http:/RR.RR.RR.RR/:8624 which could not be interpreted. After typing only RR.RR.RR.RR and nothing else in the filed for the IP address it worked.
Also for some reason port number 7624 was not actually open and both ports 8624 and 7624 (or whatever numbers you want to assign to them) need to be open. Some routers are quite picky about the choice of numbers as it turns out.
Read More...
My problem remains and I would appreciate some clarification as to how to make Indi webmanager work over the internet. I am able to port forward RR.RR.RR.RR:8624 and access the webmanager from my remote Windows PC but I can't get the drivers to connect on port RR.RR.RR.RR:7624 even though I forwarded that port in the same way.
Any step by step guides out there or some instructions would be appreciated. Thanks.
Read More...
Croz wrote: You may have done this already? Try taking the / out of the address. It should look like this RR.RR.RR.RR:8624
Yes. I know this. I was just pointing out that this "typo" is something that EKOS does as part of its programming when I click on the button and likely needs to be corrected so that it will do it correctly but I don't think it has to do with my inability to make indi webmanager work over the internet.
Read More...
I have build a Raspberyy Pi with Raspbian and Indi Webserver. I loaded KSTARS/EKOS and was able to run it remotely over the internet using VNC server but it is too slow on my Raspberry Pi 3 B+. To be able to use the power of my desktop from another physical location I thought to just run IndiWeb server from the Raspberry Pi and run KSTARS/EKOS from my remote laptop over the internet.
I can get IndiWeb manager to load automatically on the Raspberry Pi which I have set to a Static IP address. I successfully port forwarded the Raspberry Pi on the router’s IP address (call it RR.RR.RR.RR) port 8624. From my remote desktop on a different Wi-Fi network I can open a webpage
RR.RR.RR.RR:8624
and see the IndiWeb manager and start and stop the server.
The IndiWeb server is set to port 7624. I also port forwarded this port on the remote router where the Raspberry Pi.
When I start Kstarts and try to connect Indi I get an error “Connection to Indi Server at host
RR.RR.RR.RR/
with port 7624 failed” My networking knowledge is limited. I am just reading guides/tutorials over the internet.
I tried to scan for the Indi WebManager from the EKOS interface and it does not locate it even though I can access it on my Web browser as I explained above. So that I know that it is there and it is started.
As an aside, when I click on the Web manager button (the one with the world icon in it) it takes me to this address on my browser: http//RR.RR.RR.RR/:8624 which does not work because there is a typo in the position of the colon. Could this be the issue?
Thank you in advance for your help.
Read More...