Yes. I don't understand it either, why it's so slow and resource-hungry under SM. In AB it's fine.
Yes. That's what I thought... but had to give it a try.
pch wrote: Forget ST4 if the mount driver support pulse guiding, this is the case for INDI Eqmod.
The interest of ST4 is only for non-computerized mount where it is the only option. For example if you use the HEQ5 only with the handpad without computer connection.
Windows KStars client always crashes on disconnect. This is consistent. I don't even remember when it was not crashing.
I was using Windows 7. Upgraded to Windows 10 not long ago. Same story.
If I just start KStars/Ekos and fiddle for a short time and disconnect - no crash.
But after a full session, when I click Disconnect it dies losing all recent changes.
Not a big deal but annoying.
My first mount didn't have an ST4 port so I was doing pulse guiding.
Then, I got an HEQ5 and was still doing pulse guiding as I didn't want to use an extra cable.
Tonight I tried ST4.
Didn't really see any difference.
Should there be any?
Just wondering if I can forget about ST4.
I had the same yesterday. Not sure what happened but after I restarted the INDI server, the address changed to a correct one by itself.
Funny thing - I did exactly that when travelled to Mexico a couple of years back over New Year : )
I just wanted to try GPS in case I might need to use it some day for some reason.
Coordinates/time can be synced via SM app anyway. I keep forgetting about this app's existence.
El Corazon wrote: You can also set the geographic location where you are going ahead of time in Kstars > Settings > Geographic and save the location. Then all you need to do is set the clock on the Pi4 after firing it up and select that particular location. You should be synchronized then.
That's what I did when I went to a dark site in New Mexico a couple of years back over New Year. Worked like a charm for me then, without a GPS.
It took me over 8 months to get back to this but I got NetGPS working with Ekos!
Will soon be travelling to a remote/dark location 400mi/650km away - will see how it works in the wild.
Thanks for your help!
The workaround is to have the cable disconnected, launch oaCapture and then connect the cable.
The problem cable was made out of this: www.amazon.com/gp/product/B014GZTCC6
The other cable which came with my used HEQ5 doesn't have this issue.
A few weeks ago I reluctantly upgraded my desktop from Windows 7 to 10.
After that I lost the ability to connect to Stellarmate/Astroberry shared folders over my home network.
Found the solution:
Change AllowInsecureGuestAuth from 0 to 1.
Hope this helps someone.
it was possible in Ubuntu Mate builds.
Not possible in Raspbian.
People build from sources to get beta stuff, I guess.
SEP Multistar is great! I am consistently getting rms <0.5 with my HEQ5 now. It used to be between 1 and 2 before.
Big thanks to everyone involved!
Yes. You were right...
oaCapture works with ZWO camera and focuser attached but as soon as I plug-in the mount it wouldn't start again (silently crashes on start).
Mount: AZ-GTi. EQMod with EQDir USB cable.
FTDI chip in the cable is to blame? It was interfering with ZWO cameras not long ago until a fix was issued.
Yes. I did try to run it from a fresh image.
Maybe it's the card? I use Patriot for Astroberry. Will try Samsung.
Kaczorek wrote: Have you tried to run it from fresh image (v2.0.3)? I use it myself for planetary imaging without any issues. If it crashes, it might be unsupported hardware issue and you can consider reporting it to oaCapture developer.
Of course, it was a loose network cable coupler... : )