Same here. No fix with gpsd. Running 1.4.4. on RPI4
DrawsACircle wrote: @AstroNerd, have you had a GPS connected (gpsd driver)? Mine connects, but detects no signal from the gps, no gps fix, it only takes a couple of seconds with 1.4.3.
Derpit, I think a saw you mention in another post that backlash compensation turned up as a setting in the driver. Care to share your experience?
Verstuurd vanaf mijn ONEPLUS A5010 met Tapatalk
Would you know where I could check out the features of the numerous drivers, seems I can only see it when I actually have device connected.
I'm about to upgrade from the standard skywatcher auto focuser combined with the Hitec Astro DC focus to the more robust ZWO ASI EAF.
Would anyone owning the ZWO ASI EAF care to share the experiences you have until now?
One thing that the driver for the Hitec Astro dearly missed was backlash compensation which renders the setup useless.
Does the Indi driver have backlash compensation built into it?
I just tried moving 22GB in older captures from a USB drive to the NanoPi. No issues moving loads of data, CPU heat about the same when capturing.
I ran it again today. Initial CPU temp 32C. I began capturing immediately. Same issue, after about 10 frames, no frames come in anymore. Temp goes up to max 55C.
I also tried the ASI385. It also fails after a while. I think after maybe 30 frames or so.
I even tried it without Fits previews. This does not make a difference at all.
I also run Armbian 5.85 Stable
The NanoPi keeps functioning without freezing, kstarts keeps running, no problems there either.
I love my RPI3+ running Stellarmate, but I wanted something faster. Faster image solving, faster previews (STF and Debayer). And less crashes... I think the RPI3+ is a tad light for all it has to handle and the CPU spikes regulary.
So I got a NanoPi M4 with 4GB ram.
Thus I have tried the Friendly Desktop and Lunbuntu images provided by Friendly Elec (the manufacturer).
After installing KStars I connect just my ASI294MC Pro and run some tests. In all tests I will get 2 max 3 images out of my camera. Then it nothing. I then need to unplug the camera. Restart Kstars and I can do the same again.
I tried just about anything: bandwidth to 40/80/100 Highspeed mode on/off, shorter cables, usb2 cables instead of usb3 (there is a thread here that says this should work). Several power supplies.
Then I saw a thread here that said it should work with Armbian (bionic) running on the NanoPi.
That seemed to work out well... I get in between of 15 to 40 frames out of the camera and then the same unresponsiveness.
So after two days of struggling with this I hope someone can release me from my pain I really want this to work.
Can you elaborate on what this all means.
I only have Stellarmate OS 1.3.1. I have no option to download newer versions. There is no option called licenses in my account.
Does this mean I can not use the new Stellarmate App at all?
Can you point to more information on what the new app establishes? Does it replace ekos live for instance?
Hi Gilles, Dragonlost,
I tried ALS. Good job.
It needs some work but I think you are nearly there.
I'd be happy to test new releases and give feedback.
I have not experienced it on my last session last Sunday. I'm on the nightly builds, although I have not updated in the last 10 days or so. I only update when I come across serious know issues. This prevents me from running into new issues.
I also keep a backup image available so I can always go back if I run into issues.
To all, this issue has been resolved some weeks ago.
It was actually a bug in the ASI camera driver which would leave out some rows of pixels when switching between binning levels.
It was not a Pixinsight issue.
Yes, I have experienced this exactly the same.
Although it is much better than a month or so ago.
I also find it very strange that although ekos should know it was almost there and than it makes a huge step and then stops because it does not recognize a star anymore. You would think that if this happens ekos could just return to where it knew where recognizable stars were visible.
There is something I posted earlier and it might cause problems and that is that I noticed some backlash when zooming is reversed. So the first 10 or so steps do not actually move focus (speed is set to 100 in my case). This would mean that focus shifts a a few steps when reversing. Ekos would make calculations based on a position that is off by 10 steps.
I think we should post some logs from this behavior, so it can be sorted out.
Care to share what bug you are referring to?