Hello, I'm going through the same situation. After months of bad weather, finally, a few nights of good conditions arrive. The outcome?
Night 1: While using version 1.7.6 of the mobile app, it had updated automatically. I'm not sure if that's the reason, but the shots weren't updating for polar alignment. I decide to update to the new version through the app. The update stayed stuck at 90.1% indefinitely. By this point, it was already midnight, so I give up and turn off the device with the fear that the update might render the operating system unusable, as it has happened to many people before.
Night 2: I restart the update, and it stops at the same point again. After leaving it for almost an hour, I access it via VNC, but I don't see any update process. After restarting the OS and the app, it seems to be on the latest version now. It took two hours, a bit late, but I start... I find it impossible to align to the pole. It has never happened to me before. After another hour of repeating the process, I go back to VNC and see messages saying "could not estimate mount movement." I give up again.
Night 3: I try again. I manage to align with great difficulty. I notice that the error and correction results for alignment using plate solving are very inconsistent, It goes from 0.0.20 to 1.40.0 at times, and it even asks for absurd corrections on some occasions, so I leave it as it is. Once again, I have lost half of the night, so I just want to try the rest of the things. I assume it's due to the poor resulting alignment that even the guiding is unable to calibrate the tracking.
So I think, let's try in Andromeda with short subs and no guiding. I start the sequence, lock the tablet to turn off the screen, and when I check later, I encounter the same problem with the simulator profiles, it's impossible to do anything except disconnect the profile and start over again . I just simply laughed hard, turned off everything and went to bed frustrated after three nights of struggle and 0 photos.
Read More...
Oooh god what a mess of ""update""!!!
too late for me too, no check the forums before updating... bye new moon weekend, that was a big facepalm.
Im running the 64 bits version from SSD and Rpi4, and for me the copy of boot partition fix not worked, so I flashed a new image, of course loosing all configs...
Without the hassle of reconfiguring everything, now im facing a new problem, before this big fail, for the hard drive to boot using usb 3.0 I used this command in cmdline.txt,
usb-storage.quirks=152d:0578:uBut now if I use this code the SO dont boot, showing the errors of the pic, this force me to use the SSD with the usb 2.0... any hint?
write 100 times: if it works don't update, if it works don't update, if it works don't update....
Read More...
Tonight I tried make Flats... I have added a sequence of Flats calculating the ADU values and then the Darkflats sequence with the specific option.
It calibrates the exposure flats as usual and captures the sequence, but when start the DarkFlats it doesn't warn or wait for cover the telescope as it does with normal Darks sequences... Is this a the correct behavior or a bug?
Cheers.
Read More...
Tonight with all updated I tried make Flats... I have added a sequence of Flats calculating the ADU values and then the Darkflats sequence with the specific option.
It calibrates the exposure flats as usual and captures the sequence, but when start the DarkFlats it doesn't warn or wait for cover the telescope as it does with normal Darks sequences... Is this a the correct behavior or a bug?
Cheers.
Read More...
Tonight I tried make Flats... I have added a sequence of Flats calculating the ADU values and then the Darkflats sequence with the specific option.
It calibrates the exposure flats as usual and captures the sequence, but when start the DarkFlats it doesn't warn or wait for cover the telescope as it does with normal Darks sequences... Is this a the correct behavior or a bug?
Cheers.
Read More...
Tonight I tried make Flats... I have added a sequence of Flats calculating the ADU values and then the Darkflats sequence with the specific option.
It calibrates the exposure flats as usual and captures the sequence, but when start the DarkFlats it doesn't warn or wait for cover the telescope as it does with normal Darks sequences... Is this a the correct behavior or a bug?
Cheers.
Read More...
Hi, I'm new with this software and for now looks great, but I need help with one question (sorry about my English!)
Im running Ekos in raspberry, and using the mount Skywatcher Staradventurer 2i connected via USB, everything seems works fine, except the snap port.
My plan is use this port and the cable shutter for my DSLR but I can't figure the behaviour, and I don't know if is this a bug or simply didn't work.
With all connected and the drivers running, in the Indi control panel, if I turn ON the snap port it open the shutter instantly and never close, even if I try do an exposure with Ekos.
I already tested the snap port and the cable using the mount without software and it works as normal shutter behaviour.
Anyone know how it works?
Thanks Ind advance!!
Read More...
Hi, I'm new with this software and for now looks great, but I need help with one question (sorry about my English!)
Im running Ekos in raspberry, and using the mount Skywatcher Staradventurer 2i connected via USB, everything seems works fine, except the snap port.
My plan is use this port and the cable shutter for my DSLR but I can't figure the behaviour, and I don't know if is this a bug or simply didn't work.
With all connected and the drivers running, in the Indi control panel, if I turn ON the snap port it open the shutter instantly and never close, even if I try do an exposure with Ekos.
I already tested the snap port and the cable using the mount without software and it works as normal shutter behaviour.
Anyone know how it works?
Thanks Ind advance!!
Read More...