I have switched to the Simulator to try and get this working.
Now the UI is no longer greyed out (I assume because I did not have my mount attached it was greyed out) and I can start a ASTAP solve but I always get "Solver Failed. Try again".
Is there anything I need to do in ASTAP to get it setup?
2019-11-10T09:50:15 Solver failed. Try again.
2019-11-10T09:50:09 /Applications/ASTAP.app/Contents/MacOS/astap -O --no-plots --no-verify --resort --downsample 2 -L 20.339 -H 25.424 -u aw -3 23.7958 -4 30.7606 -5 30 -f /private/var/folders/kg/s3p7zt0x11z16l_jcq1s8vmr0000gn/T/fitsXptWhn.fits -o /private/var/folders/kg/s3p7zt0x11z16l_jcq1s8vmr0000gn/T/solution
2019-11-10T09:50:09 Starting solver...
2019-11-10T09:50:09 Solver iteration #1
2019-11-10T09:50:09 Image received.
2019-11-10T09:50:05 Capturing image...
Read More...
I just updated to 3.3.7 on OSX.
I had the solver setup but now it seems I have to set it up again. I have installed the ASTAP software and set the correct path in the Solver option menu but the Solver page remains inactive (grayed out).
What steps should I be taking to get it setup?
Read More...
I have been viewing the images from within PI. They were not yet debayered.
I though PI displayed images as gray scale until they are debayered?
Is that the tram line effect I am seeing? Only the red pixels.
Read More...
As usual it turned out to be user error.
Out of the box the driver has the format set to 8 bit (which is I assume to improve the frame rate for lucky imaging).
Once I set it to 16 bit my darks looked normal.
Read More...
As usual it turned out to be user error.
Out of the box the driver has the format set to 8 bit (which is I assume to improve the frame rate for lucky imaging).
Once I set it to 16 bit my darks looked normal.
Read More...
Thanks. That was it! It was still set to 8 bit which I guess is the default to improve frame rate.
Very happy to have this solved. Now I can start collecting data again.
Read More...
I have been using the default (for Indi) offset value of 8 for all my frames.
I am also using the unity level of gain (120).
I am not using any bias frames but Flat Darks. My flats are 4 seconds to avoid short exposures.
The Indi driver does have some settings I don't completely understand.
Default the Format is set to 8 bits with RGB, 16 bit and Luma as options. If I set it to 16 bit my darks immediately look much better. I would have expected 16 bit to be the default unless I was trying to get a high FPS?
Read More...
Hi All
I started a new thread because I am now a step further.
I cannot take good Darks using the Indi driver via Ekos. They show no randomness and do not display the amp glow. We noticed a checkerboard pattern, this doesn't look random, all the "lanes" have the same value, and the black pixels exactly half of that.
Maybe its a setting (I am using the defaults) but I cannot get it right.
So I decided to install APT and use ASCOM to connect. The Darks I get via APT are exactly as I would expect. I can clearly see the amp glow and star burst pattern.
Any idea's why the INDI driver behaves so differently from the Ascom?
I have 2 samples on dropbox which I can share to illustrate what I mean. The examples have both been stretched the same amount using the STF function in PixInsight.
Read More...
Thanks. I have checked all the forums.
I am not taking bias but Flat Darks.
My problem is that my Darks do not have the amp glow.
Indi sets the Offset to 8 per default but it seems most other software uses 40 or 50 so I will try that.
Read More...
Hi All
I have recently started using a 294 OSC camera.
When I take my dark frames I can hardly see any amp glow (even when stretched) but my lights show plenty of amp glow.
This means that when I calibrate the amp glow is not removed.
Are there any settings I should make in Indi to get my darks working correctly. I have left everything on the default settings.
The darks I am trying to create are 180 second, gain 120 everything else default OOTB settings.
Attached is a stretched mast dark. If you zoom in you can just see the amp glow.
Read More...
Exactly. Those are the errors i get. When you look in the camera you see the number of frames left counter flashing.
Read More...
I tried first with the EOS driver this morning and although I tried to follow exactly the same pattern as last night now it works fine (same thing happed yesterday when I tried it in the daytime).
I swapped to the GPhoto driver and that seems to work OK too. I guess I will have to wait for the next clear night to really see if it makes a difference.
Read More...
Hi All
I seem to be having issues with my Canon 6D since I updated to the latest library.
I have tried unsuccessfully to use my Canon 6D over the last 2 evenings.
I get everything setup fine including Auto-Focussing which goes through the Canon.
Taking a few sample pictures usually works too but as soon as I start a sequence the camera hangs. On the camera I see the frame counter flashing and the Indi control panel produces an error message every 20 seconds.
I will try again today in the daytime to see if I can reproduce the error and provide some accurate information but I was curious if anyone has experienced the same?
Cheers
Rishi
Read More...